Test method and device for brake-by-wire equipment of vehicle, processor and vehicle

Abstract

The invention discloses a method and a device for testing brake-by-wire equipment of a vehicle, a processor and the vehicle. The method comprises the steps that test demand information of brake-by-wire equipment of a vehicle is acquired, and the test demand information is used for representing test demands of the brake-by-wire equipment in a test scene; test conditions corresponding to the test demand information are determined, and different test demand information corresponds to different test conditions; based on the test condition, a target driving model is determined, and the target driving model is used for representing that the driving mode of the vehicle in the test demand is controlled in the test scene; according to the target driving model, controlling the control braking equipment to generate test case information in the test scene; and testing the brake-by-wire equipment based on the test case information to obtain a test result. According to the invention, the technical problem of low testing efficiency of the brake-by-wire equipment of the vehicle is solved.

Description

Technical Field

[0001] The present invention relates to the field of vehicle technology, and in particular to a testing method, device, processor and vehicle for a vehicle's brake-by-wire device. Background Art

[0002] Currently, a vehicle's brake-by-wire system (brake-by-wire system) can control the vehicle's braking process through an electronic controller and actuator, rather than relying directly on physical connections (such as the connecting rod between the brake pedal and the brake disc), greatly improving vehicle safety. Therefore, it is very important to test a vehicle's brake-by-wire system to ensure safe driving.

[0003] In the related art, the testing method of the vehicle's wire control brake device mainly relies on actual vehicle (real vehicle) road testing. However, since the real vehicle road test is greatly affected by external factors such as weather and traffic conditions, it is difficult to obtain consistent results even if multiple tests are conducted under the same test conditions, which limits the reliability of the test results. In addition, the real vehicle road test requires a lot of manpower, material resources and time resources. Each round of testing requires the arrangement of special vehicles and professionals, and there are also strict requirements for the selection of test sites, which greatly extends the test cycle and increases the test cost. Therefore, there is still a technical problem of low efficiency in testing the vehicle's wire control brake device.

[0004] Currently, no effective solution has been proposed to the above-mentioned technical problem of low efficiency in testing vehicle brake-by-wire equipment. Summary of the Invention

[0005] Embodiments of the present invention provide a method, apparatus, processor, and vehicle for testing a brake-by-wire device of a vehicle, to at least solve the technical problem of low efficiency in testing the brake-by-wire device of the vehicle.

[0006] According to one aspect of an embodiment of the present invention, a method for testing a vehicle's brake-by-wire device is provided. The method may include: obtaining test requirement information for the vehicle's brake-by-wire device, wherein the test requirement information indicates test requirements for the brake-by-wire device in a test scenario; determining test conditions corresponding to the test requirement information, wherein different test requirement information corresponds to different test conditions; determining a target driving model based on the test conditions, wherein the target driving model indicates a driving mode for controlling a vehicle under the test requirements in the test scenario; controlling the brake-by-wire device to generate test case information for the test scenario according to the target driving model, wherein the test case information triggers testing of the brake-by-wire device in the test scenario; and testing the brake-by-wire device based on the test case information to obtain a test result, wherein the test result indicates whether the brake-by-wire device meets the test criteria for the test scenario.

[0007] Optionally, the wire control brake device includes a test management system, a simulation test system, and a wire control brake control system, the test management system is connected to the simulation test system, and the simulation test system is connected to the wire control brake control system, and the wire control brake device is tested based on the test case information to obtain a test result, including: controlling the test management system to obtain a test case sample corresponding to the target driving model from the test case library, wherein the test case sample satisfies the test scenario; determining the similarity between the test case sample and the test case information; based on the similarity, testing the wire control brake device under the test scenario to obtain a test sub-result, wherein the test sub-result is used to indicate whether the wire control brake device passes the test under the test scenario; and determining the test result based on the test sub-result.

[0008] Optionally, based on the similarity, the wire control braking device is tested in the test scenario to obtain a test sub-result, including: in response to the similarity being greater than a similarity threshold, determining that the test sub-result is that the wire control braking device passes the test in the test scenario; in response to the similarity being less than or equal to the similarity threshold, determining that the test sub-result is that the wire control braking device fails the test in the test scenario.

[0009] Optionally, based on the test sub-result corresponding to the test scenario, the test result is determined, including: in response to the test sub-result corresponding to the test scenario being that the wire control brake device fails the test in the test scenario, determining that the test result is that the wire control brake device fails to meet the test standard; in response to the test sub-result corresponding to the test scenario being that the wire control brake device passes the test in the test scenario, determining that the test result is that the wire control brake device meets the test standard.

[0010] Optionally, the method further includes: utilizing a signal acquisition module in a simulation test system to acquire an output signal of the brake-by-wire system; and generating a test report based on the test result.

[0011] Optionally, based on the test conditions, a target driving model is determined, including: determining an initial driving model based on test scenario parameters and test conditions in a test case library; and adjusting the test scenario parameters in the initial driving model based on the test report to determine the target driving model, wherein the test scenario parameters are used to represent parameters that affect the performance of the wire control brake device under the test scenario.

[0012] Optionally, the method further includes: combining the test conditions to obtain a test condition set; based on the test condition set and the test scenario, controlling the brake-by-wire device to generate test case information under the test scenario in accordance with the target driving model.

[0013] According to another aspect of an embodiment of the present invention, a testing apparatus for a vehicle's brake-by-wire device is provided. The apparatus may include: an acquisition unit configured to acquire test requirement information for the vehicle's brake-by-wire device, wherein the test requirement information indicates the test requirements for the brake-by-wire device in a test scenario; a first determination unit configured to determine test conditions corresponding to the test requirement information, wherein different test requirement information corresponds to different test conditions; a second determination unit configured to determine a target driving model based on the test conditions, wherein the target driving model indicates the driving mode for controlling the vehicle under the test requirements in the test scenario; a control unit configured to control the brake-by-wire device to generate test case information for the test scenario according to the target driving model, wherein the test case information triggers testing of the brake-by-wire device in the test scenario; and a testing unit configured to test the brake-by-wire device based on the test case information to obtain a test result, wherein the test result indicates whether the brake-by-wire device meets the test standards for the test scenario.

[0014] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is further provided. The computer-readable storage medium includes a stored program, wherein when the program is executed, the device containing the computer-readable storage medium is controlled to execute the method for testing a vehicle brake-by-wire device according to an embodiment of the present invention.

[0015] According to another aspect of an embodiment of the present invention, a processor is provided, wherein the processor is configured to run a program, wherein when the program is run, the method for testing a vehicle brake-by-wire device according to an embodiment of the present invention is executed.

[0016] According to another aspect of an embodiment of the present invention, a vehicle is provided, which is used to perform the method for testing a brake-by-wire device of a vehicle according to an embodiment of the present invention.

[0017] In an embodiment of the present invention, if it is necessary to test the vehicle's brake-by-wire device, test requirement information of the vehicle's brake-by-wire device can be obtained, wherein the test requirement information is used to represent the test requirements of the brake-by-wire device in a test scenario; test conditions corresponding to the test requirement information are determined, wherein different test requirement information corresponds to different test conditions; based on the test conditions, a target driving model is determined, wherein the target driving model is used to represent the driving mode of controlling the vehicle in the test requirements in the test scenario; according to the target driving model, the brake-by-wire device is controlled to generate test case information in the test scenario, wherein the test case information is used to trigger testing of the brake-by-wire device in the test scenario; based on the test case information, the brake-by-wire device is tested to obtain test results, wherein the test results are used to indicate whether the brake-by-wire device meets the test standards in the test scenario.

[0018] In an embodiment of the present invention, a dynamic driving model (target driving model) can be determined based on the test requirement information of the wire control brake device and the corresponding different test conditions. According to the target driving model, the wire control brake device can be controlled to generate test case information under the test scenario to trigger the test of the wire control brake device under the test scenario. The test results reflect the actual performance of the wire control brake device under specific test conditions and test scenarios, thereby solving the technical problem of low efficiency in testing the vehicle's wire control brake device and achieving the technical effect of improving the efficiency of testing the vehicle's wire control brake device. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0020] Figure 1 is a flow chart of a method for testing a brake-by-wire device of a vehicle according to an embodiment of the present invention;

[0021] Figure 2 is a schematic diagram of a hardware-in-the-loop automated testing platform for a wire control brake system based on abnormal braking scenario reconstruction according to an embodiment of the present invention;

[0022] Figure 3 is a schematic diagram of a test management system according to an embodiment of the present invention;

[0023] Figure 4 is a schematic diagram of a hardware-in-the-loop simulation test system according to an embodiment of the present invention;

[0024] Figure 5 2 is a schematic diagram of a testing device for a vehicle's brake-by-wire device according to an embodiment of the present invention. DETAILED DESCRIPTION

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

[0026] It should be noted that the terms "first," "second," and the like in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or precedence. It should be understood that the numbers used in this way are interchangeable where appropriate so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to these processes, methods, products, or apparatus.

[0027] According to an embodiment of the present invention, an embodiment of a method for testing a vehicle's brake-by-wire device 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.

[0028] Figure 1 FIG. 1 is a flow chart of a method for testing a brake-by-wire device of a vehicle according to an embodiment of the present invention. Figure 1 As shown, the method may include the following steps:

[0029] Step S102 : Acquire test requirement information of the vehicle's brake-by-wire device.

[0030] In the technical solution provided in the above step S102 of the present invention, the test requirement information can be used to indicate the test requirements for the brake-by-wire device in a test scenario.

[0031] In this embodiment, the brake-by-wire device, also known as the brake-by-wire system, is a vehicle braking technology. Unlike related technologies, where a vehicle's braking system uses physical connections (such as hydraulic lines or levers) to transmit the driver's braking commands, the brake-by-wire device uses electrical signals or data links to control the braking process, thereby achieving electronic and intelligent control of the brake-by-wire device. Test requirement information defines the objectives and scope of the test, providing a basis for determining subsequent test conditions. It can include functional verification requirements, performance indicator requirements, fault injection requirements, etc. This is for illustrative purposes only and is not a specific limitation.

[0032] Optionally, obtaining test requirements information for the brake-by-wire system is the starting point for the entire test, providing clear direction for determining subsequent test conditions, establishing the target driving model, and generating test case information. The accuracy and comprehensiveness of this test requirements information ensures that the necessary test scenarios and conditions are covered, enabling a comprehensive assessment of the brake-by-wire system's performance, safety, and reliability. Obtaining test requirements information for a vehicle's brake-by-wire system provides the foundation for more efficient test design and execution, avoiding the omission of important test scenarios or the over-testing of insignificant details, thereby improving test efficiency.

[0033] Optionally, test requirement information can be obtained from existing test data, accident data, and vehicle usage data, or a detailed demand analysis can be conducted based on the functions and safety standards of the vehicle's wire control brake equipment to obtain the expected performance and safety requirements of the wire control brake equipment in different test scenarios, providing a basis for the test requirement information.

[0034] It should be noted that the above-mentioned method for obtaining the test requirement information is only an example and is not specifically limited here. Any method that can be used to obtain the test requirement information of the vehicle's wire control brake device in a test scenario is within the scope of protection of the embodiments of the present invention.

[0035] Step S104: determining the test conditions corresponding to the test requirement information.

[0036] In the technical solution provided in step S104 of the present invention, different test requirement information corresponds to different test conditions, for example, testing the braking response time of a brake-by-wire device under high load conditions, or the emergency braking performance of a brake-by-wire device under a specific fault mode.

[0037] In this embodiment, after obtaining test requirement information for the vehicle's brake-by-wire system, test conditions corresponding to the test requirement information can be determined. The test conditions simulate various real-world driving environments and situations and may include environmental parameters, road and terrain conditions, vehicle status, driver behavior simulation, etc.

[0038] Optionally, environmental parameters may be temperature, humidity, atmospheric pressure, etc., which can be used to simulate the performance of the wire control brake device under different climatic conditions. Road and terrain conditions may be road types (such as straight roads, curves, ramps), road conditions (such as dry, slippery, ice and snow covered), road obstacles (such as sudden pedestrians, animals or obstacles), etc., which can be used to verify the response of the wire control brake device under different driving conditions. Vehicle status may be vehicle speed, acceleration, steering angle, load, etc., which can be used to evaluate the impact of different vehicle status on the braking effect of the wire control brake device. Driver behavior simulation may be braking force, reaction time, operating mode (such as sudden braking, slow braking), etc., to simulate human factors in real driving situations.

[0039] It should be noted that the above test conditions are merely examples and are not specifically limited herein. Any content that can be used to determine the test conditions corresponding to the test requirement information is within the scope of protection of the embodiments of the present invention.

[0040] For example, if the test requirement information mentions the need to test the braking performance of a wire-controlled brake system on a slippery road surface, the corresponding test conditions may include simulating road conditions after rain or covered with ice and snow, while also setting the vehicle's initial speed and the driver's braking force to evaluate the wire-controlled brake system's response time and braking force distribution strategy under the above conditions. For another example, if the wire-controlled brake system's fault tolerance under communication failures needs to be tested, the test conditions may include intentionally interrupting or delaying data transmission on the Controller Area Network (CAN) bus to observe the wire-controlled brake system's fault detection and handling mechanisms.

[0041] Step S106: Determine the target driving model based on the test conditions.

[0042] In the technical solution of step S106 of the present invention, the target driving model represents the driving mode for controlling the vehicle under test requirements in the test scenario. The target driving model can be used to accurately simulate the vehicle's driving behavior and response under specific test scenarios during hardware-in-the-loop (HIL) testing of the vehicle's brake-by-wire equipment. The target driving model can be a vehicle dynamics model, a road model, or a driver model.

[0043] In this embodiment, after determining the test conditions corresponding to the test requirement information, the target driving model can be determined based on the test conditions. If it is necessary to test the vehicle's brake-by-wire device, the brake-by-wire device can be connected to a simulation environment through HIL to test and verify the performance and function of the brake-by-wire device under real-world conditions. During the HIL testing process of the vehicle's brake-by-wire device, the target driving model can provide a virtual (simulated) test environment, allowing the brake-by-wire device to experience various driving conditions and working conditions without the need for actual road testing. Through the simulation of the target driving model, the response speed, stability, safety and functional integrity of the brake-by-wire device can be efficiently tested, while avoiding the safety risks and costs in actual road testing.

[0044] Alternatively, a vehicle dynamics model can be used to describe the vehicle's kinematic characteristics under different operating conditions. For example, to test braking performance on slippery roads, the vehicle dynamics model must accurately reflect the changes in tire-road grip and the vehicle's stability control during braking.

[0045] Optionally, a road model can be used to simulate the actual road environment in which a vehicle travels, including road type (e.g., urban road, highway), road surface conditions (e.g., dry, slippery), and road geometry (e.g., slope, turns, obstacles). For example, to test braking performance in emergency obstacle avoidance situations, the road model can include unexpected obstacles and the vehicle's obstacle avoidance path planning.

[0046] Optionally, a driver model can be used to simulate the behavior and decision-making process of a real driver by taking into account the driver's reaction time, braking force control, steering operation, etc. For example, during the testing of a brake-by-wire system, the driver model can simulate the driver's reaction to suddenly applying maximum braking force in an emergency situation to evaluate the braking system's rapid response and stability.

[0047] In an embodiment of the present invention, based on the test requirement information, the specific test scenarios and working conditions that the driving model needs to cover can be clarified, and appropriate parameters can be set for the vehicle dynamics model, road model, and driver model to reflect the actual situation under the test conditions, thereby integrating the above three models into the HIL test platform to ensure that the above three models can work together to form a closed-loop simulation environment, providing a basis for the subsequent generation of test case information and automated test execution.

[0048] Step S108 : controlling the brake-by-wire device to generate test case information under the test scenario according to the target driving model.

[0049] In the technical solution of step S108 of the present invention, the test case information is used to trigger testing of the brake-by-wire device in a test scenario.

[0050] In this embodiment, after determining the target driving model based on the test conditions, the test scenario can be parameterized according to the target driving model. For example, the vehicle's initial speed, acceleration, driving direction, braking force, fault type, environmental variables (such as weather, road conditions), and actions of other traffic participants can be parameterized to control the wire control braking device to generate test case information under the test scenario to simulate complex driving conditions or fault response processes.

[0051] Optionally, during HIL testing of a vehicle's brake-by-wire system, test case information can provide specific operational instructions and environment settings. This allows brake-by-wire testing to move beyond theoretical evaluation and simulate various real-world driving scenarios, such as normal operation, boundary conditions, and failure scenarios. By executing these test cases, the performance of the brake-by-wire system can be tested under different test conditions.

[0052] Step S110 : testing the brake-by-wire device based on the test case information to obtain a test result.

[0053] In the technical solution of the above step S110 of the present invention, the test result is used to indicate whether the brake-by-wire device meets the test standard under the test scenario.

[0054] In this embodiment, after controlling the brake-by-wire device to generate test case information for the test scenario according to the target driving model, the brake-by-wire device can be tested based on the test case information to obtain test results. This step is the execution phase of the brake-by-wire device HIL testing process. The purpose is to conduct a comprehensive evaluation of the brake-by-wire device by simulating the test conditions of the test scenario to verify whether the brake-by-wire device meets the established test standards and performance indicators.

[0055] Alternatively, if the test results show that the brake-by-wire device can stably and accurately respond to various test scenarios and meet the test standards and safety indicators, then the brake-by-wire device meets the test standards for the test scenario. Conversely, if performance issues or security vulnerabilities are discovered during testing, then the brake-by-wire device does not meet the test standards for the test scenario. In this case, the brake-by-wire device needs to be adjusted, repaired, or optimized as necessary, and then the brake-by-wire device HIL test needs to be repeated until all test case information meets the test standards.

[0056] In embodiments of the present invention, by executing test case information—that is, by having the brake-by-wire device perform predetermined test actions based on the generated test case information, such as simulated driver operation, fault injection, and brake command responses under normal and abnormal operating conditions—test results reflecting the performance and safety of the brake-by-wire device can be obtained. Analysis of these test results ensures that the brake-by-wire device provides reliable and efficient braking performance under various test conditions and potential faults, ensuring driving safety.

[0057] In the above steps S102 to S110 of the present application, if it is necessary to test the vehicle's brake-by-wire device, the test requirement information of the vehicle's brake-by-wire device can be obtained, wherein the test requirement information is used to represent the test requirements of the brake-by-wire device in the test scenario; the test conditions corresponding to the test requirement information are determined, wherein different test requirement information corresponds to different test conditions; based on the test conditions, a target driving model is determined, wherein the target driving model is used to represent the driving mode of controlling the vehicle in the test requirement in the test scenario; according to the target driving model, the brake-by-wire device is controlled to generate test case information in the test scenario, wherein the test case information is used to trigger the test of the brake-by-wire device in the test scenario; based on the test case information, the brake-by-wire device is tested to obtain a test result, wherein the test result is used to indicate whether the brake-by-wire device meets the test standard in the test scenario.

[0058] In an embodiment of the present invention, a dynamic driving model (target driving model) can be determined based on the test requirement information of the wire control brake device and the corresponding different test conditions. According to the target driving model, the wire control brake device can be controlled to generate test case information under the test scenario to trigger the test of the wire control brake device under the test scenario. The test results reflect the actual performance of the wire control brake device under specific test conditions and test scenarios, thereby solving the technical problem of low test efficiency of the vehicle's wire control brake device and achieving the technical effect of improving the test efficiency of the vehicle's wire control brake device.

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

[0060] As an optional embodiment, a wire control brake device includes a test management system, a simulation test system, and a wire control brake control system. The test management system is connected to the simulation test system, and the simulation test system is connected to the wire control brake control system. Step S110 tests the wire control brake device based on the test case information to obtain a test result, including: controlling the test management system to obtain a test case sample corresponding to the target driving model from the test case library, wherein the test case sample satisfies the test scenario; determining the similarity between the test case sample and the test case information; based on the similarity, testing the wire control brake device under the test scenario to obtain a test sub-result, wherein the test sub-result is used to indicate whether the wire control brake device passes the test under the test scenario; and determining the test result based on the test sub-result.

[0061] In this embodiment, the brake-by-wire equipment may include a test management system, a simulation test system, and a brake-by-wire control system. The simulation test system may be a HIL simulation test system. The test management system and the simulation test system may be connected via a host computer, allowing test managers to directly control the test process, set test parameters, and monitor test results from the host computer interface. The simulation test system and the brake-by-wire control system may be connected via CAN cables, Ethernet cables, or hardwires to transmit test instructions and provide brake-by-wire equipment feedback.

[0062] Optionally, the test management system serves as the command center for the brake-by-wire system, coordinating and managing the entire testing process. The simulation test system is the core platform for brake-by-wire system testing. By simulating real-world driving conditions and operating scenarios, it enables precise performance evaluation of the brake-by-wire system. The brake-by-wire control system, the core of the brake-by-wire system, is directly responsible for interpreting and executing braking commands. For example, it receives braking signals from the test management system or driver model, interprets them, and executes the corresponding braking strategy.

[0063] Optionally, during the process of testing the brake-by-wire system based on the test case information and obtaining the test results, the test management system can be controlled to obtain a test case sample corresponding to the target driving model from the test case library; determine the similarity between the test case sample and the test case information; based on the similarity, test the brake-by-wire system under the test scenario to obtain a test sub-result; and determine the test result based on the test sub-result. The test case sample can be used to meet the test scenario. The test sub-result can be used to indicate whether the brake-by-wire system passed the test under the test scenario.

[0064] Optionally, the test management system may include a test specification library, a fault matrix library, a functional safety library, a sudden braking / fault test scenario mining module, a test case generation module, a test case evaluation module, a test case optimization module, a test case library, a test case automatic execution module and a test report generation module.

[0065] Optionally, the test management system can select test case samples that match the current test requirements from a stored test case library based on the constructed target driving model. To ensure that the selected test case samples accurately reflect the test requirements, the similarity between the test case samples and the current test case information can be calculated. Based on this similarity, the HIL simulation test system is controlled to execute the test and obtain test sub-results. The test management system can then summarize all test sub-results for comprehensive analysis and comparison to determine the final test result.

[0066] As an optional embodiment, based on the similarity, the wire control braking device is tested in the test scenario to obtain a test sub-result, including: in response to the similarity being greater than the similarity threshold, determining the test sub-result as the wire control braking device passing the test in the test scenario; in response to the similarity being less than or equal to the similarity threshold, determining the test sub-result as the wire control braking device failing the test in the test scenario.

[0067] In this embodiment, in the process of testing the wire control braking device in the test scenario based on similarity and obtaining the test sub-results, when the similarity is greater than the similarity threshold, the test sub-result can be determined as the wire control braking device passing the test in the test scenario; when the similarity is less than or equal to the similarity threshold, the test sub-result can be determined as the wire control braking device failing the test in the test scenario.

[0068] Optionally, by comparing the similarity between the test case sample and the test case information with a set similarity threshold, it is possible to determine whether the performance of the brake-by-wire device in the simulated test scenario meets the requirements. The similarity threshold may be 85%, which is for illustrative purposes only and is not a specific limitation.

[0069] Optionally, when the similarity between the test case sample and the test case information exceeds a preset threshold, the test management system deems the brake-by-wire device to have accurately simulated the expected operating conditions and behavior in the current test scenario. This means that the brake-by-wire device demonstrated consistent or better performance than the test requirements in terms of processing braking commands, responding to fault injection, and maintaining braking performance. In this case, the test management system will determine the test sub-result as indicating that the brake-by-wire device passed the test in the test scenario.

[0070] Optionally, when the similarity between the test case sample and the test case information is less than or equal to a preset similarity threshold, the test management system may determine that there are significant differences between the test case sample and the actual test situation, indicating that the performance of the brake-by-wire device fails to fully reflect the requirements of the test case. This may be due to factors such as excessively long response time, braking distance exceeding a safe range, uneven braking force distribution, or failure of the fault recovery mechanism to activate in a timely manner. In this case, the test management system will determine that the test sub-result is that the brake-by-wire device failed in the test scenario.

[0071] As an optional embodiment, the test result is determined based on the test sub-result corresponding to the test scenario, including: in response to the test sub-result corresponding to the test scenario being that the wire control brake device fails the test in the test scenario, determining that the test result is that the wire control brake device does not meet the test standard; in response to the test sub-result corresponding to the test scenario being that the wire control brake device passes the test in the test scenario, determining that the test result is that the wire control brake device meets the test standard.

[0072] In this embodiment, in the process of determining the test result based on the test sub-result corresponding to the test scenario, when the test sub-result corresponding to the test scenario is that the wire control brake device fails the test in the test scenario, the test result can be determined as that the wire control brake device fails the test standard; when the test sub-result corresponding to the test scenario is that the wire control brake device passes the test in the test scenario, the test result can be determined as that the wire control brake device meets the test standard.

[0073] Optionally, after each test scenario is completed, a test sub-result can be generated to evaluate the performance of the wire control brake device in the test scenario. The test sub-results can be specifically manifested as whether the braking distance of the wire control brake device meets the requirements under specific test conditions, whether the fault response time meets the standard, whether the braking force distribution is appropriate, etc. If there are test sub-results in one or more test scenarios, the wire control brake device fails the test in the test scenario, which means that the wire control brake device fails to meet the test standard, and the test result is that the wire control brake device fails to meet the test standard. When the test sub-results in the test scenario are all passed, it means that the wire control brake device has shown performance that meets or exceeds the test standard in each test scenario, that is, the test result is that the wire control brake device meets the test standard.

[0074] In this embodiment, by performing test scenario-by-test scenario judgment on the test results based on each test sub-result, comprehensive quality control of the wire control brake device can be performed to ensure that the wire control brake device can meet safety and performance requirements under various expected operating conditions.

[0075] As an optional embodiment, the method further includes: utilizing a signal acquisition module in a simulation test system to acquire an output signal of the brake-by-wire control system; and generating a test report based on the test results.

[0076] In this embodiment, the signal acquisition module in the simulation test system can be used to obtain the output signals of the wire control brake system, such as the brake pressure signal, the wheel speed signal, the fault response signal, and the wire control brake control system status signal; the output signals are analyzed, and the test results are automatically generated into a test report to indicate whether the wire control brake equipment meets the test standards and the specific reasons for passing or failing.

[0077] Optionally, in addition to the signal acquisition module, the simulation test system may further include a sudden braking scenario simulation platform, a fault acquisition module, an intelligent fault injection module and a signal processing board.

[0078] Optionally, a sudden braking scenario simulation platform can simulate real driving environments and sudden braking scenarios, including vehicle dynamics models, road models, and driver models, and can reproduce complex road conditions, sudden braking events, and driver behavior.

[0079] Optionally, the fault collection module can monitor and record fault information occurring in the brake-by-wire equipment in real time, such as electrical signal anomalies, hydraulic pressure changes, and abnormal sensor readings. Electrical signal anomalies can manifest as CAN bus faults or Local Interconnect Network (LIN) bus faults.

[0080] Optionally, the intelligent fault injection module can inject various types of faults into the wire control brake equipment according to preset test cases and fault matrices, such as electrical signal faults, hydraulic system faults, sensor faults, etc., to simulate fault scenarios that may be encountered in actual driving.

[0081] Optionally, the signal processing board may include a CAN board, a LIN board, an input / output board, and an Ethernet board, etc., which are used to process driver operation signals, vehicle status information, sensor information, and actuator information, and convert the driver operation signals, vehicle status information, sensor information, and actuator information into a signal format recognizable by the wire control brake device.

[0082] In the embodiment of the present invention, the signal acquisition module, the sudden braking scenario simulation platform, the fault acquisition module, the intelligent fault injection module, and the signal processing board and other modules work together to ensure the comprehensiveness and accuracy of the test and ultimately generate a test report.

[0083] Optionally, the test report may include: test overview, test conditions, test data, test analysis and test conclusions. The test overview may include a brief description of the test purpose, test scenario, test object and test method. The test conditions may include the specific test conditions for each test scenario, including test scenario parameters, fault type, etc., to facilitate tracking and reproduction. The test data may include presenting key output signal data during the test process. For example, the performance of the wire control brake device under different working conditions can be intuitively displayed in the form of tables, charts, etc. The test analysis may include an in-depth analysis of the test data to identify the advantages and disadvantages of the wire control brake device, as well as potential areas for improvement. The test conclusion may include the test results to clarify whether the wire control brake device meets the predetermined performance standards.

[0084] As an optional embodiment, step S106 determines the target driving model based on the test conditions, including: determining the initial driving model based on the test scenario parameters and test conditions in the test case library; adjusting the test scenario parameters in the initial driving model based on the test report to determine the target driving model, wherein the test scenario parameters are used to represent parameters that affect the performance of the wire control brake device in the test scenario.

[0085] In this embodiment, when determining a target driving model based on test conditions, an initial driving model can be determined based on test scenario parameters and test conditions in a test case library. Based on the test report, the test scenario parameters in the initial driving model can be adjusted to determine the target driving model. The test scenario parameters represent parameters that affect the performance of the brake-by-wire system in the test scenario.

[0086] Optionally, based on the collected test scenario parameters (such as vehicle speed, road conditions, vehicle load, braking intensity, and fault injection type), an initial driving model can be constructed to simulate actual driving conditions in the HIL simulation test system. This step is fundamental to ensuring that the test reflects real-world driving situations. The test management system can then analyze the test reports to identify test scenarios that failed the test and any deficiencies in the brake-by-wire system's performance.

[0087] Optionally, the test scenario parameters in the initial driving model can be adjusted based on the performance issues identified in the test report. For example, if the braking distance of the wire control device on a slippery road is too long, the road friction coefficient can be increased or the vehicle load can be adjusted to simulate more stringent test conditions. Through repeated testing and adjustment of test scenario parameters, a target driving model that fully reflects the performance of the wire control device and covers the test requirements can be determined. Multiple iterations can be performed until the iterated initial driving model can produce stable and expected test results in the test scenario, thus obtaining the target driving model.

[0088] As an optional embodiment, the method further includes: combining the test conditions to obtain a test condition set; based on the test condition set and the test scenario, controlling the wire control brake device to generate test case information under the test scenario in accordance with the target driving model.

[0089] In this embodiment, test conditions can be combined to form a test condition set. A test condition set is a combination of one or more test conditions that covers variables under different operating conditions, such as vehicle speed, road friction coefficient, weather conditions, and fault type. Based on the test condition set and test scenario, and in accordance with the target driving model, the brake-by-wire device can be controlled to generate test case information for the test scenario.

[0090] Optionally, the test conditions are combined to generate a test condition set, and the wire control brake equipment is controlled based on the target driving model to generate test case information under the test scenario. This can improve the comprehensiveness of the test, accelerate the test execution, and improve the test efficiency through automated and intelligent test processes.

[0091] In an embodiment of the present invention, if it is necessary to test the vehicle's brake-by-wire device, test requirement information of the vehicle's brake-by-wire device can be obtained, wherein the test requirement information is used to represent the test requirements of the brake-by-wire device in a test scenario; test conditions corresponding to the test requirement information are determined, wherein different test requirement information corresponds to different test conditions; based on the test conditions, a target driving model is determined, wherein the target driving model is used to represent the driving mode of controlling the vehicle in the test requirements in the test scenario; according to the target driving model, the brake-by-wire device is controlled to generate test case information in the test scenario, wherein the test case information is used to trigger testing of the brake-by-wire device in the test scenario; based on the test case information, the brake-by-wire device is tested to obtain test results, wherein the test results are used to indicate whether the brake-by-wire device meets the test standards in the test scenario.

[0092] In an embodiment of the present invention, a corresponding dynamic driving model (target driving model) can be generated based on the test requirement information of the wire control brake device and the corresponding different test conditions, and test case information is generated based on the target driving model and the test conditions. The test case information is applied to the wire control brake device, triggering the test of the wire control brake device under the test scenario. The test results reflect the actual performance of the wire control brake device under specific test conditions and test scenarios, thereby solving the technical problem of low efficiency in testing the vehicle's wire control brake device and achieving the technical effect of improving the efficiency of testing the vehicle's wire control brake device.

[0093] The technical solutions of the embodiments of the present invention are described below with reference to preferred implementation methods.

[0094] Currently, the testing methods for wire-controlled brake systems mainly rely on actual vehicle road testing, which has disadvantages such as long testing cycles, high costs, poor repeatability, difficulty simulating extreme operating conditions, and inability to verify the real-time and safety of electronic control logic. Furthermore, existing wire-controlled brake system HIL test platforms have a single scenario and are unable to simulate complex road conditions (such as sudden changes in low-adhesion road surfaces, emergency obstacle avoidance, and other dynamic coupling scenarios). Fault testing relies on manually preset cases and is unable to adaptively generate boundary condition test cases. Therefore, the technical problem of low efficiency in vehicle wire-controlled brake equipment testing still exists.

[0095] An embodiment of the present invention proposes a HIL automated testing method for a wire control brake system based on reconstruction of an abnormal braking scenario. The method comprises the following steps: obtaining test requirement information of a vehicle's wire control brake device, wherein the test requirement information is used to indicate the test requirements for the wire control brake device in a test scenario; determining test conditions corresponding to the test requirement information, wherein different test requirement information corresponds to different test conditions; determining a target driving model based on the test conditions, wherein the target driving model is used to indicate a driving mode for controlling a vehicle in a test requirement in a test scenario; controlling the wire control brake device to generate test case information in a test scenario according to the target driving model, wherein the test case information is used to trigger testing of the wire control brake device in the test scenario; and testing the wire control brake device based on the test case information to obtain test results, wherein the test results are used to indicate whether the wire control brake device meets the test standards in the test scenario.

[0096] In an embodiment of the present invention, a dynamic driving model (target driving model) can be determined based on the test requirement information of the wire control brake device and the corresponding different test conditions. According to the target driving model, the wire control brake device can be controlled to generate test case information under the test scenario to trigger the test of the wire control brake device under the test scenario. The test results reflect the actual performance of the wire control brake device under specific test conditions and test scenarios, thereby solving the technical problem of low efficiency in testing the vehicle's wire control brake device and achieving the technical effect of improving the efficiency of testing the vehicle's wire control brake device.

[0097] The following is a further introduction to the embodiments of the present invention.

[0098] Figure 2 is a schematic diagram of a hardware-in-the-loop automated test platform for a wire control brake system based on abnormal braking scenario reconstruction according to an embodiment of the present invention, such as Figure 2 As shown, it includes: a test management system 202 , a HIL simulation test system 204 and a brake-by-wire control system 206 .

[0099] Optionally, the test management system 202 and the HIL simulation test system 204 may be connected via a host computer; the HIL simulation test system 204 and the brake-by-wire control system 206 may be connected via a CAN line, an Ethernet line, or a hard line.

[0100] Optionally, the host computer plays a core coordination and control role in the HIL automated test platform for the wire control brake system based on abnormal braking scenario reconstruction. It can serve as a bridge between the test management system 202 and the HIL simulation test system 204, ensuring efficient communication and data exchange between the test management system 202 and the HIL simulation test system 204.

[0101] Alternatively, CAN cables can be used to send and receive high-speed control signals and status information, serving as the primary channel for rapidly transmitting braking commands. Ethernet cables offer high bandwidth and are suitable for transmitting large amounts of data, such as simulation model parameters and test results. Hardwires can serve as auxiliary communication channels when necessary, ensuring that basic interaction between the HIL simulation test system and the brake-by-wire control system is maintained even if other communication methods fail.

[0102] Figure 3 Schematic diagram of a test management system according to an embodiment of the present invention. Figure 3 As shown, it includes: a test specification library 301, a fault matrix library 302, a functional safety library 303, a sudden braking / fault test scenario mining module 304, a test case generation module 305, a test case evaluation module 306, a test case optimization module 307, a test case library 308, a test case automatic execution module 309 and a test report generation module 310.

[0103] The test specification library 301 can be used to store test specifications and standards for the brake-by-wire control system. The test specifications and standards for the brake-by-wire control system define the performance indicators and compliance requirements that the brake-by-wire control system should meet, and are the basis for test design.

[0104] The fault matrix library 302 may include matrices of various possible fault types and their impacts, and is used to test the response and recovery capabilities of the brake-by-wire system under different fault types.

[0105] The functional safety library 303 can be used to store brake functional safety standard documents.

[0106] The sudden braking / fault test scenario mining module 304 can generate the required initial scenario parameters. According to the test effect feedback during the test process, the dynamic continuity optimization algorithm and the boundary benefit optimization algorithm can be used to update the test scenario parameters in real time to ensure that the test scenario can meet the corresponding test conditions.

[0107] The test case generation module 305 can be used to select or generate test cases based on existing test cases and test specifications, and store the test cases. The generated test cases may include test steps, expected results, boundary conditions, etc.

[0108] The test case evaluation module 306 can be used to evaluate each generated or selected test case. Unqualified test cases need to be regenerated by the test case optimization module 307, and qualified test cases can be added to the test case library 308.

[0109] The test case automatic execution module 309 can automatically select test cases from the test case library according to the test plan, and automatically execute the test through the interface with the HIL simulation test system without human intervention, thereby realizing the automatic execution of test case steps.

[0110] The test report generation module 310 can track and record unexpected results that occur during the test process, analyze and record them according to the result evaluation criteria, and generate and store a standard test report document.

[0111] In an embodiment of the present invention, ten modules, namely, a test specification library 301, a fault matrix library 302, a functional safety library 303, a sudden braking / fault test scenario mining module 304, a test case generation module 305, a test case evaluation module 306, a test case optimization module 307, a test case library 308, a test case automatic execution module 309 and a test report generation module 310, work together to form a cyclic iterative testing process. Starting from the mining of test scenarios, to the generation of test cases, and then to the execution of tests and the generation of test reports, each step is responsible for an independent functional module, and at the same time, they are also interdependent, together forming a test management system. Thus, the automation and efficiency of the test are guaranteed, as well as the comprehensiveness and safety of the test, which is the key to the successful testing of the HIL automated test platform of the wire control brake system.

[0112] Figure 4 is a schematic diagram of a hardware-in-the-loop simulation test system according to an embodiment of the present invention. Figure 4 As shown, it includes: a sudden braking scenario simulation platform 421, a signal acquisition module 422, a fault acquisition module 423, an intelligent fault injection module 424 and a signal processing board 425.

[0113] In this embodiment, the sudden braking scenario simulation platform 421 may include a vehicle dynamics model 4211, a road model 4212, and a driver model 4213. The sudden braking scenario simulation platform 421 can model the vehicle dynamics parameters, road model parameters, and driver model parameters input from the test case library, providing a virtual testing environment. During testing, it can track vehicle status information in real time and modify the model in real time based on feedback.

[0114] Optionally, the vehicle dynamics model 4211 can be used to execute relevant commands of the vehicle's intelligent driving controller, and can simulate the operating status of the vehicle (whole vehicle) based on the status information of the road model 4212 and related dynamic information, and provide real-time feedback on the vehicle status information. The road model 4212 can be used to simulate real vehicle road scenes and dynamic simulation roads according to the working conditions involved in the test, including information describing the road type, road grade, road surface structure, infrastructure, dynamic driving scenes, and natural environment information. The driver model 4213 can output signals such as braking, throttle, and steering wheel angle in real time according to the current test requirements to simulate real driver operations.

[0115] In this embodiment, the signal acquisition module 422 can collect the feedback signal of the wire control brake control system, and the sudden braking scenario simulation platform 421 can provide data support for updating the simulation scenario parameters. The sudden braking scenario simulation platform 421 adjusts the road and vehicle status information in real time through the feedback signal to form a closed loop.

[0116] In this embodiment, the fault collection module 423 can collect fault information of the brake-by-wire control system in real time.

[0117] In this embodiment, the intelligent fault injection module 424 can implement various fault injection steps input by the test case library.

[0118] In this embodiment, the signal processing board 425 may include a CAN board, a LIN board, an IO board, and an Ethernet board, which is used to output driver operation signals, vehicle status information, sensor and actuator information to the wire control brake control system.

[0119] In this embodiment of the present invention, the sudden braking scenario simulation platform can generate a corresponding dynamic driving model for the test task requirements of the brake-by-wire control system. According to the test case steps, the automatic execution module controls the simulation board to issue the corresponding control signal, which is transmitted to the brake-by-wire control system. The brake-by-wire control system makes corresponding decisions based on the received vehicle driving information and control signal request, and then feeds the result signal back to the test report generation module through the signal acquisition module for analysis and evaluation, ultimately generating a test report.

[0120] Optionally, to meet the test task requirements of the wire control system, the intelligent fault injection module can generate a programmable fault matrix based on the Field-Programmable Gate Array (FPGA), supporting millisecond-level dynamic injection of 16 types of faults, such as electrical signals (CAN / LIN), hydraulic pressure, and wheel speed sensors. According to the test case steps, the module can automatically execute the control simulation board to send the corresponding fault injection information to the wire control system. The wire control system will generate corresponding feedback information based on the received fault information, and feedback the result signal to the test report generation module through the fault acquisition module for result analysis and evaluation, and finally generate a test report.

[0121] Optionally, the HIL simulation system's real-time processor can utilize a distributed simulation framework with a time synchronization accuracy of ≤100 microseconds (μs) to ensure temporal consistency across the mechanical, hydraulic, and electrical systems. Controlled by a host computer, the brake-by-wire control system can be comprehensively and systematically tested.

[0122] According to an embodiment of the present invention, a test device for a vehicle's brake-by-wire device is also provided. It should be noted that the test device for a vehicle's brake-by-wire device can be used to execute the test method for a vehicle's brake-by-wire device in the embodiment.

[0123] Figure 5 FIG. 1 is a schematic diagram of a test device for a vehicle's brake-by-wire device according to an embodiment of the present invention. Figure 5 As shown, the testing device 500 for the vehicle's brake-by-wire device may include: an acquisition unit 502 , a first determination unit 504 , a second determination unit 506 , a control unit 508 , and a testing unit 510 .

[0124] The acquiring unit 502 is configured to acquire test requirement information of a brake-by-wire device of a vehicle, wherein the test requirement information is used to indicate test requirements for the brake-by-wire device in a test scenario.

[0125] The first determining unit 504 is configured to determine a test condition corresponding to the test requirement information, wherein different test requirement information corresponds to different test conditions.

[0126] The second determining unit 506 is configured to determine a target driving model based on the test conditions, wherein the target driving model is used to represent a driving mode for controlling a vehicle under test requirements in a test scenario.

[0127] The control unit 508 is used to control the brake-by-wire device to generate test case information under the test scenario according to the target driving model, wherein the test case information is used to trigger the test of the brake-by-wire device under the test scenario.

[0128] The testing unit 510 is configured to test the brake-by-wire device based on the test case information to obtain a test result, wherein the test result is used to indicate whether the brake-by-wire device meets the test standard under the test scenario.

[0129] Optionally, the test unit 510 includes: a first acquisition module, used to control the test management system to obtain test case samples corresponding to the target driving model from the test case library, wherein the test case samples satisfy the test scenario; a first determination module, used to determine the similarity between the test case samples and the test case information; a first testing module, used to test the wire control brake device in the test scenario based on the similarity to obtain a test sub-result, wherein the test sub-result is used to indicate whether the wire control brake device passes the test in the test scenario; and a second determination module, used to determine the test result based on the test sub-result.

[0130] Optionally, the first test module includes: a first determination submodule, used to determine, in response to the similarity being greater than a similarity threshold, that the test sub-result is that the wire control braking device passes the test in the test scenario; and a second determination submodule, used to determine, in response to the similarity being less than or equal to the similarity threshold, that the test sub-result is that the wire control braking device fails the test in the test scenario.

[0131] Optionally, the second determination module includes: a third determination sub-module, for determining that the test result is that the wire control brake device does not meet the test standard in response to the test sub-result corresponding to the test scenario being that the wire control brake device fails the test in the test scenario; and a fourth determination sub-module, for determining that the test result is that the wire control brake device meets the test standard in response to the test sub-result corresponding to the test scenario being that the wire control brake device passes the test in the test scenario.

[0132] Optionally, the test device 500 for the vehicle's wire control brake device further includes: a second acquisition module, used to obtain the output signal of the wire control brake system using the signal acquisition module in the simulation test system; and a generation module, used to generate a test report based on the test results.

[0133] Optionally, the second determination unit 506 includes: a third determination module, used to determine the initial driving model based on the test scenario parameters and test conditions in the test case library; and a fourth determination module, used to adjust the test scenario parameters in the initial driving model based on the test report to determine the target driving model, wherein the test scenario parameters are used to represent parameters that affect the performance of the wire control brake device under the test scenario.

[0134] Optionally, the testing device 500 for the vehicle's brake-by-wire device may further include: a combining unit for combining test conditions to obtain a test condition set; and a second control unit for controlling the brake-by-wire device to generate test case information under the test scenario based on the test condition set and the test scenario and in accordance with the target driving model.

[0135] In an embodiment of the present invention, an acquisition unit 502 may acquire test requirement information for a vehicle's brake-by-wire device, where the test requirement information indicates test requirements for the brake-by-wire device under a test scenario. A first determination unit 504 may determine test conditions corresponding to the test requirement information, where different test requirement information corresponds to different test conditions. A second determination unit 506 may determine a target driving model based on the test conditions, where the target driving model indicates a driving mode for controlling the vehicle under the test requirements under the test scenario. A control unit 508 may control the brake-by-wire device to generate test case information for the test scenario based on the target driving model, where the test case information triggers testing of the brake-by-wire device under the test scenario. A testing unit 510 may test the brake-by-wire device based on the test case information and obtain a test result indicating whether the brake-by-wire device meets the test criteria under the test scenario. This resolves the technical issue of low test efficiency for vehicle brake-by-wire devices and improves the efficiency of vehicle brake-by-wire device testing.

[0136] According to an embodiment of the present invention, a computer-readable storage medium is further provided. The storage medium includes a stored program, wherein the program executes the testing method of the vehicle's brake-by-wire device in the embodiment.

[0137] According to an embodiment of the present invention, a processor is further provided. The processor is configured to run a program. When the program is run, the method for testing a brake-by-wire device of a vehicle in the embodiment is executed.

[0138] According to an embodiment of the present invention, a vehicle is further provided. The vehicle is used to execute the method for testing a brake-by-wire device of a vehicle according to an embodiment of the present invention.

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

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

[0141] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only exemplary. For example, the division of the 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.

[0142] The units described as separate components may or may not be physically separate, and the 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 according to actual needs to achieve the purpose of the present embodiment.

[0143] In addition, the functional units in the various embodiments of the present invention may be integrated into a single processing unit, 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.

[0144] 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 invention, 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. The computer software product 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 invention. 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 code.

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

Claims

1. A method for testing a vehicle's brake-by-wire device, characterized in that: include: Acquiring test requirement information of a brake-by-wire device of a vehicle, wherein the test requirement information is used to indicate test requirements for the brake-by-wire device in a test scenario; Determining a test condition corresponding to the test requirement information, wherein different test requirement information corresponds to different test conditions; Determining a target driving model based on the test conditions, wherein the target driving model is used to represent a driving mode for controlling the vehicle under the test requirements in the test scenario; controlling the brake-by-wire device to generate test case information for the test scenario according to the target driving model, wherein the test case information is used to trigger testing of the brake-by-wire device in the test scenario; Based on the test case information, the brake-by-wire device is tested to obtain a test result, wherein the test result is used to indicate whether the brake-by-wire device meets the test standard under the test scenario.

2. The method according to claim 1, characterized in that The brake-by-wire device includes a test management system, a simulation test system, and a brake-by-wire control system, wherein the test management system is connected to the simulation test system, and the simulation test system is connected to the brake-by-wire control system. The brake-by-wire device is tested based on the test case information to obtain test results, including: Controlling the test management system to obtain a test case sample corresponding to the target driving model from a test case library, wherein the test case sample satisfies the test scenario; Determining the similarity between the test case sample and the test case information; Based on the similarity, testing the brake-by-wire device in the test scenario to obtain a test sub-result, wherein the test sub-result is used to indicate whether the brake-by-wire device passes the test in the test scenario; Based on the test sub-results, the test result is determined.

3. The method according to claim 2, characterized in that Based on the similarity, the brake-by-wire device is tested in the test scenario to obtain test sub-results, including: In response to the similarity being greater than a similarity threshold, determining the test sub-result as the brake-by-wire device passing the test in the test scenario; In response to the similarity being less than or equal to the similarity threshold, determining the test sub-result as a test failure of the brake-by-wire device under the test scenario.

4. The method according to claim 3, characterized in that Determining the test result based on the test sub-result corresponding to the test scenario includes: In response to the test sub-result corresponding to the test scenario being that the brake-by-wire device fails the test under the test scenario, determining that the test result is that the brake-by-wire device fails the test standard; In response to the test sub-result corresponding to the test scenario being that the brake-by-wire device passes the test under the test scenario, it is determined that the test result is that the brake-by-wire device meets the test standard.

5. The method according to claim 4, characterized in that The method further comprises: Using a signal acquisition module in the simulation test system, obtaining an output signal of the brake-by-wire control system; Based on the output signal, a test report is generated based on the test result.

6. The method according to claim 5, characterized in that Based on the test conditions, determining a target driving model includes: Determining an initial driving model based on the test scenario parameters in the test case library and the test conditions; Based on the test report, test scenario parameters in the initial driving model are adjusted to determine the target driving model, wherein the test scenario parameters are used to represent parameters that affect the performance of the wire control brake device in the test scenario.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: Combining the test conditions to obtain a test condition set; Based on the test condition set and the test scenario, and in accordance with the target driving model, the brake-by-wire device is controlled to generate test case information under the test scenario.

8. A test device for a vehicle's brake-by-wire device, characterized in that: include: an acquiring unit, configured to acquire test requirement information of a brake-by-wire device of a vehicle, wherein the test requirement information is used to indicate test requirements for the brake-by-wire device in a test scenario; A first determining unit, configured to determine a test condition corresponding to the test requirement information, wherein different test requirement information corresponds to different test conditions; a second determining unit, configured to determine a target driving model based on the test condition, wherein the target driving model is used to represent a driving mode for controlling the vehicle under the test requirement in the test scenario; a control unit, configured to control the brake-by-wire device to generate test case information for the test scenario according to the target driving model, wherein the test case information is used to trigger testing of the brake-by-wire device in the test scenario; A testing unit is used to test the wire control brake device based on the test case information to obtain a test result, wherein the test result is used to indicate whether the wire control brake device meets the test standard under the test scenario.

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

10. A vehicle, characterized in that: The vehicle is used to perform the method according to any one of claims 1 to 7.

Images