A continuous testing method and system for vehicle application scenarios

Abstract

The present invention discloses a method and system for continuous testing of vehicle application scenarios. The method comprises the following steps: classifying each application scenario according to the required vehicle speed; driving along a set route, completing the corresponding application scenario test at the same vehicle speed each time; and repeating the set route to complete application scenario tests at all speeds. This application can improve testing efficiency, meet user continuity testing needs, and simultaneously implement short-route, full-scenario continuity testing. This reduces test equipment installation and testing costs.

Description

Technical Field

[0001] The present invention relates to the technical field of vehicle application scenario testing, and in particular to a vehicle application scenario continuous testing method and system. Background Art

[0002] The V2X test standard includes 15 scenarios (CSAE 246, excluding green wave speeds and proximity payment). All scenarios have high requirements for road conditions. Using separate scenario testing, each scenario requires extensive road preparation and braking, resulting in long test times and inability to meet users' needs for continuous testing. Furthermore, existing test sites often employ decentralized testing across scenarios, designing and laying out scenarios based solely on the needs of a single scenario (testing one scenario before moving on to the next), without considering the need for continuous, full-scenario testing.

[0003] Therefore, how to meet the continuous testing requirements for the first-stage application scenarios of vehicles is a technical problem that needs to be solved urgently. Summary of the Invention

[0004] The main purpose of this invention is to provide a vehicle application scenario continuous testing method and system that can improve testing efficiency, meet user continuity testing needs, and simultaneously implement short-route and full-scenario continuity testing, thereby reducing test equipment installation and testing costs.

[0005] In a first aspect, the present application provides a method for continuous testing of vehicle application scenarios, the method comprising the steps of:

[0006] Classify each application scenario according to the required vehicle speed;

[0007] Drive along the set route, completing the corresponding application scenario test at the same vehicle speed each time, and repeat driving along the set route to complete the application scenario test at all types of vehicle speeds.

[0008] In combination with the first aspect above, as an optional implementation,

[0009] In combination with the first aspect above, as an optional implementation method, according to the testing requirements of each application scenario, a customized application scenario test site is provided, and each application scenario use case in the test site is classified from small to large according to speed.

[0010] In combination with the first aspect above, as an optional implementation method, roadside equipment is pre-set according to the test requirements of each scenario, and the roadside equipment includes: cameras, radars, traffic lights and RSUs.

[0011] In combination with the first aspect above, as an optional implementation manner, the road length required for each scenario in the test site is adjusted according to the speed of the test vehicle.

[0012] In combination with the first aspect above, as an optional implementation method, the driving route of the test vehicle is determined by a preset length and a preset width.

[0013] In conjunction with the first aspect above, as an optional implementation, based on real-time calculation of vehicle test scenarios, when the test vehicle reaches the starting point of the pre-preparation area for the next scenario, a test start instruction is issued to the background vehicle;

[0014] The background vehicle determines whether to cooperate with the test vehicle to test the scene according to the scene test standard.

[0015] In combination with the first aspect above, as an optional implementation method, during the test process, the tested scene is configured in advance by issuing virtual road event information, and the configured road event information is sent to the test vehicle, where the configuration content includes the event type and the scope of event impact.

[0016] In a second aspect, the present application provides a vehicle application scenario continuous testing system, the system comprising:

[0017] A data processing unit, which is used to classify each application scenario according to the required vehicle speed;

[0018] The operating unit is used to drive along a set route, complete the corresponding application scenario test at the same vehicle speed each time, and repeatedly drive along the set route to complete the application scenario test at all types of vehicle speeds.

[0019] In conjunction with the second aspect above, as an optional implementation, the processing unit is further configured to calculate the vehicle test scenario in real time and, when the test vehicle reaches the starting point of the pre-preparation area for the next scenario, issue a test start instruction to the background vehicle;

[0020] The background vehicle determines whether to cooperate with the test vehicle to test the scene according to the scene test standard.

[0021] In combination with the second aspect above, as an optional implementation method, it also includes a roadside unit, which is used to configure the tested scene in advance by sending virtual road event information during the test process, and send the configured road event information to the test vehicle, where the configuration content includes the event type and the scope of event impact.

[0022] This application provides a method and system for continuous testing of vehicle application scenarios, wherein the method includes the following steps: classifying each application scenario according to the required vehicle speed; driving along a set route, completing the corresponding application scenario test at the same vehicle speed each time, and repeating the driving along the set route to complete the application scenario test at all vehicle speeds. This application can improve testing efficiency, meet user continuity testing needs, and simultaneously implement short-route, full-scenario continuity testing. It also reduces the installation of test equipment and lowers testing costs.

[0023] It should be understood that the foregoing general description and the following detailed description are exemplary only and are not restrictive of the invention. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0025] Figure 1 This is a flow chart of a continuous testing method for vehicle application scenarios provided in an embodiment of the present application;

[0026] Figure 2 This is a schematic diagram of a continuous testing system for vehicle application scenarios provided in an embodiment of the present application. DETAILED DESCRIPTION

[0027] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. In the following description, when referring to the drawings, like numbers in different figures represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all possible embodiments consistent with the present invention. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present invention, as detailed in the appended claims.

[0028] Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. Some of the blocks shown in the drawings are functional entities that do not necessarily correspond to physically or logically separate entities.

[0029] The embodiments of the present application provide a method and system for continuous testing of vehicle application scenarios, which can improve testing efficiency, meet user continuity testing needs, and implement short-route and full-scenario continuity testing, reduce test equipment installation, and lower testing costs.

[0030] To achieve the above technical effects, the general ideas of this application are as follows:

[0031] A method for continuous testing of vehicle application scenarios, the method comprising the steps of:

[0032] S101: Classify each application scenario according to the required vehicle speed.

[0033] S102: driving along a set route, completing the corresponding application scenario test at the same vehicle speed each time, and repeatedly driving along the set route to complete the application scenario test at all types of vehicle speeds.

[0034] The embodiments of the present application are further described in detail below with reference to the accompanying drawings.

[0035] Reference Figure 1 , Figure 1 The figure shows a flow chart of a continuous testing method for vehicle application scenarios provided by the present invention. Figure 1 As shown, the method includes the steps of:

[0036] Step S101: Classify each application scenario according to the required vehicle speed.

[0037] Specifically, according to the testing requirements of each application scenario, a customized application scenario test site is defined. It can be understood that the customized test site is closed, and the test site contains all the scenarios of the first phase of V2X, that is, 16 application scenarios. All application scenario use cases in the test site are classified from small to large according to speed. It should be noted that each application scenario has many use cases. For example, the forward collision warning scenario test cases include: test cases 1, 2, 3, 4, 5, 6 and 7, where the speed of the vehicle under test corresponding to test case 1 is 20 km / h, the background vehicle speed is 0, and the overlap rate is 100%; the speed of the vehicle under test corresponding to test case 2 is 40 km / h, the background vehicle speed is 0, and the overlap rate is 50%; the speed of the vehicle under test corresponding to test case 3 is 40 km / h, the background vehicle speed is 0, and the overlap rate is 100%; the speed of the vehicle under test corresponding to test case 4 is 60 km / h, the background vehicle speed is 0, and the overlap rate is 50%; the speed of the vehicle under test corresponding to test case 5 is 60 km / h, the background vehicle speed is 0, and the overlap rate is 100%; the speed of the vehicle under test corresponding to test case 6 is 90 km / h, the background vehicle speed is 0, and the overlap rate is 100%; the speed of the vehicle under test corresponding to test case 7 is 120 km / h, the background vehicle speed is 0, and the overlap rate is 100%. It's understandable that the use cases for each application scenario are similar to the above examples, meaning each use case has a corresponding test speed. It's important to note that any number of test cases can be selected for a single application scenario based on test requirements. For example, for a forward collision warning scenario, one test case can be selected, i.e., a test case at 20 km / h. For an emergency brake warning scenario, three test cases can be selected, i.e., at 20, 40, and 60 km / h.

[0038] It should also be noted that the 16 application scenarios tested include: emergency vehicle, forward congestion, left turn assist, collision warning for vulnerable traffic participants, speed limit warning, road hazard warning, abnormal vehicle warning, out-of-control vehicle warning, red light running warning, green wave speed guidance, forward collision warning, emergency braking warning, intersection collision, road signage, wrong-way overtaking warning, and blind spot lane change warning. It should be noted that each application scenario has a scenario scope, pre-preparation distance, total scenario road length, test site road length, and maximum test speed. Furthermore, roadside equipment and background vehicles / individuals are arranged for the application scenario based on test requirements. For example, in the emergency vehicle scenario, the test does not require the deployment of roadside equipment, but does require the setup of background vehicles / people. The scenario range is 200m, the pre-preparation distance is 300m, the total length of the road scene is 500m, and the maximum test speed is 40km / h. In the forward congestion scenario, the deployment of roadside equipment (RSU) is required, but no background vehicles / people are required. The scenario range is 100m, the pre-preparation distance is 100m, the total length of the road scene is 200m, and the maximum test speed is 60km / h. The left turn assist scenario requires the deployment of roadside equipment (RSU, radar, camera) and also requires the setup of background vehicles / people. The scenario range is 200m, the pre-preparation distance is 100m, the total length of the scenario road is 300m, and the maximum test speed is 30km / h.

[0039] To facilitate understanding of the distance description, a closed test site was designed based on the application scenario testing requirements. The test site included 16 application scenarios in the first phase, with test cases for each application scenario. For example, test speeds of 20, 40, 60, 90, and 120 km / h were used. The speeds of each application scenario were ranked in ascending order. It should be noted that for custom application scenarios, roadside equipment and background vehicles / individuals are pre-deployed. The roadside equipment includes RSUs, radars, cameras, and traffic lights. During testing, the speeds are tested in ascending order. For example, all 16 application scenarios were tested using a 20 km / h speed case. After the test was completed, each scenario was tested using a 40 km / h speed case until the ranked speed cases were tested. If the speed of the vulnerable traffic participant collision warning scenario was 60 km / h, and the maximum speed of the second scenario was 40 km / h, the 40 km / h application scenario would be skipped and the third scenario would be tested.

[0040] It is understandable that the reference CSAE 246 speed classification is 20, 40, 60, 90, 120 levels (basically every scene). The same speed is tested in one round, and the speed is tested from small to large.

[0041] In one embodiment, the use case speeds of various scenarios are generally divided into 20, 40, 60, 90 and 120 km / h. Basically, they are all 20, 40, and 60 (except for speed limit warnings). However, the test scenarios are different. Some scenarios have a maximum speed of 40, and some have 120. The speed limit scenario test speeds are: 45 70 90 125 35 40 60 90. The overall difference is not large. You can also test according to the close speed (for example, in the same round, other scenarios are all 40, and the speed limit scenario can be accelerated to 45).

[0042] It should be noted that the test speed in the existing technology is a single test, that is, the use of scenario-based testing requires a long pre-preparation road and braking road for each scenario (vehicle speed from 0 to target speed, from target speed to 0), the test time is long, and it cannot meet the user's continuous testing needs.

[0043] It is understandable that roadside equipment and background vehicles / people will be arranged in advance according to the test requirements of each application scenario. By setting the route, 16 V2X scenarios can be tested continuously. The test vehicle does not need to stop for preparation in the middle, which improves the test efficiency and can meet the user's continuity testing needs.

[0044] In one embodiment, roadside equipment is pre-set according to the test requirements of each scenario, and the roadside equipment includes: cameras, radars, traffic lights and RSUs.

[0045] It is understandable that when testing application scenarios, cameras, radars, traffic lights and RSUs are deployed in advance according to the test requirements of each scenario (V2I scenario). Some application scenarios do not require roadside equipment and therefore do not need to be deployed.

[0046] In one embodiment, the road length required for each scenario in the test site is adjusted based on the speed of the test vehicle. It is understood that when designing a test site based on test requirements, the road length for each application scenario in the test site can be adjusted based on the speed of the test vehicle. For example, if the maximum test speed for an emergency vehicle scenario is 40 km / h, the scenario range can be set to 200 meters.

[0047] Step S102: driving along the set route, completing the corresponding application scenario test at the same vehicle speed each time, and repeatedly driving along the set route to complete the application scenario test at all types of vehicle speeds.

[0048] Specifically, after defining the test site, the test vehicle will be driven along the set route, testing each application scenario in ascending speed order. This means that all 16 application scenarios in a single round of testing will be tested at the same speed. Repeat along the set route to complete application scenario testing at all speeds.

[0049] In one embodiment, an operating unit selects a V2X test scenario and designs a scenario use case, which is then sent to a data processing unit. The data processing unit, based on the V2X test scenario selected by the operating unit, activates the roadside equipment corresponding to the scenario, recording the currently completed use case and the start and completion times of each use case. When all use cases at a particular location are tested, the roadside equipment at that location is deactivated. The use cases are then sorted in ascending speed order to schedule the test tasks for each round. Within the same test round, the target speed of the vehicles tested in each scenario remains the same.

[0050] In one embodiment, during the test process, the tested scene is configured in advance by sending virtual road event information, and the configured road event information is sent to the test vehicle, wherein the configuration content includes the event type and the event impact range (100m longitudinally of a single lane). It is understandable that it is necessary to arrange real road events (congestion, road anomalies, in-vehicle signs, speed limits) on the road, and directly configure the RSI message sent by the RSU in advance, and the configuration content includes: event type, event impact range (can be accurate to the lane), and then the RSU directly sends the road event information to the tested vehicle. It should be noted that the purpose of sending virtual road events is to reduce the test cost (no need to set up a real event site) and to improve test accuracy. The sent event area can be accurate to a single lane. If a real event is used, the event impact area needs to be determined after perception by the sensing equipment installed on the road side, and there is a certain error.

[0051] In one embodiment, a first display installed inside the background vehicle displays the test content and test path of the current vehicle by receiving instructions from the data center, and the data transmission unit can transmit the vehicle positioning information back to the data processing unit.

[0052] In one embodiment, a second display is also included in the test vehicle, which displays the current test path and test cases, including test speed, acceleration, test lane, etc.; displays the test completion status and the test time of each case, and the data transmission unit can transmit the vehicle positioning information back to the data processing unit.

[0053] It is understandable that the test vehicle and the background vehicle perform relevant test operations according to the content displayed on the display screen and transmit their own positioning information back to the data processing unit.

[0054] In one embodiment, based on real-time calculation of vehicle test scenarios, when the test vehicle reaches the starting point of the pre-preparation area for the next scenario, a test start instruction is issued to the background vehicle;

[0055] The background vehicle determines whether to cooperate with the test vehicle to test the scene according to the scene test standard.

[0056] It can be understood that the vehicle test scenario is calculated in real time by obtaining the position information of the test vehicle transmitted by the data transmission unit. When the starting point of the pre-preparation area for the next scenario is reached, the test start instruction is sent to the background vehicle. The background vehicle determines whether to cooperate with the test vehicle to test the scenario based on the scenario test standards.

[0057] It should be noted that during the test, the vehicle under test only needs to follow the prescribed route and does not need to stop. However, background vehicles and pedestrians must be arranged to cooperate with the vehicle under test at appropriate times. (Based on the test vehicle's positioning information, the data processing system sends a signal to notify the background vehicles / pedestrians when they reach the required background vehicle / pedestrian scene.) V2V scenarios require background vehicles, and vulnerable traffic participant collision warning scenarios require pedestrians / test dummies.

[0058] In summary, the vehicle application scenario continuous testing method and system provided in this application meet the CSAE 246 standard test content requirements by designing a V2X test site, while also enabling short-route, full-scenario continuity testing, reducing test equipment installation and lowering testing costs.

[0059] Reference Figure 2 , Figure 2 The figure shows a schematic diagram of a vehicle application scenario continuous testing system provided by the present invention, such as Figure 2 As shown, the system includes:

[0060] The data processing unit 201 is used to classify each application scenario according to the required vehicle speed.

[0061] The operating unit 202 is used to drive along a set route, complete the corresponding application scenario test at the same vehicle speed each time, and repeatedly drive along the set route to complete the application scenario test at all types of vehicle speeds.

[0062] Furthermore, the data processing unit 201 is further configured to customize an application scenario test route according to the test requirements of each application scenario, and classify each application scenario use case in the test site from small to large according to speed.

[0063] Furthermore, the operating unit 202 is also used to pre-set roadside equipment according to the test requirements of each scenario, and the roadside equipment includes: cameras, radars, traffic lights and RSUs.

[0064] Furthermore, the data processing unit 201 is also used to adjust the road length required for each scene in the test site according to the speed of the test vehicle. Furthermore, the data processing unit 201 is also used to determine the driving route of the test vehicle by presetting the length and the width.

[0065] Furthermore, the data processing unit is further configured to calculate the vehicle test scenario in real time and, when the test vehicle reaches the starting point of the pre-preparation area for the next scenario, issue a test start instruction to the background vehicle;

[0066] The background vehicle determines whether to cooperate with the test vehicle to test the scene according to the scene test standard.

[0067] Furthermore, it also includes a roadside device 203, which is used to obtain the position, speed, acceleration, and heading angle information of background vehicles / people, and send it to the vehicle under test through the roadside unit to cooperate in completing the V2I type scenario.

[0068] Furthermore, the roadside equipment 203 also includes a roadside unit 2031, which is used to configure the tested scene in advance by issuing virtual road event information during the test, and send the configured road event information to the test vehicle, where the configuration content includes event type and event impact range.

[0069] It should be noted that the roadside equipment includes: a roadside unit (RSU) 2031, a camera 2032, a radar 2033, and a traffic light 2034. The RSU in the roadside equipment is also used to broadcast information sent by the data processing unit / fused perception information and signal light status information sent by the signal light. The camera and radar are used to perceive roadside traffic participants and send data processing unit reports to the RSU for broadcast. The traffic light has a network connection function for displaying traffic signal status and transmitting signal light information to the RSU. A first display 204, installed inside the background vehicle, is used to receive commands issued by the data center and display the current vehicle's test content and test path. The data transmission unit can transmit vehicle positioning information back to the data processing unit.

[0070] The second display 205 is installed inside the test vehicle and is used to display the current test path and test cases, including test speed, acceleration, test lane, etc.; it displays the test completion status and the test time of each case, and the data transmission unit can transmit the vehicle positioning information back to the data processing unit.

[0071] It is understood that after the test site road and scene design is completed, the operating unit selects the test scene and sends each scenario use case to the data processing unit. The data processing unit sorts the scenes from the smallest to the largest speed and arranges the order of each test task. The target speed of the vehicles tested in each scene in the same test round is the same. During the test, the data processing unit controls the roadside equipment (including: whether the equipment is turned on or off - recording the current completed use case and the start and completion time of each use case, turning off the roadside equipment at a certain point after all use cases in the scene are tested, and controlling the phase of traffic information lights) and sends the virtual data to the RSU. That is, the traffic participant information is fused and sent to the RSU. The current test path and test cases, including test speed, acceleration, test lane, etc., are displayed on the second display. Real-time data such as test completion status and test time of each use case are displayed. When the starting point of the pre-preparation area for the next scene is reached, the data processing unit sends a test start command to the background vehicle. The first display installed in the background vehicle receives the command issued by the data center and displays the current vehicle's test content and test path. It also transmits the vehicle positioning information back to the data processing unit.

[0072] In summary, the present application provides a method and system for continuous testing of vehicle application scenarios, wherein the method includes the following steps: classifying each application scenario according to the required vehicle speed; driving along a set route, completing the corresponding application scenario test at the same vehicle speed each time, and repeating the set route to complete application scenario tests at all speeds. This can improve testing efficiency, meet user continuity testing needs, and simultaneously implement short-route, full-scenario continuity testing. This method reduces test equipment installation and testing costs.

[0073] The foregoing is merely a list of specific embodiments of the present application, intended to enable those skilled in the art to understand or implement the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application is not limited to the embodiments shown herein, but is intended to conform to the broadest scope consistent with the principles and novel features of the present application.

Claims

1. A vehicle application scenario continuous testing method, characterized in that: include: Classify each application scenario according to the required vehicle speed; Drive along the set route, completing the corresponding application scenario test at the same vehicle speed each time, and repeat driving along the set route to complete the application scenario test at all speeds; During the test, the tested scene is configured in advance by issuing virtual road event information, and the configured road event information is sent to the test vehicle. The configuration content includes the event type and the scope of event impact.

2. The method according to claim 1, characterized in that The application scenarios are classified according to the required vehicle speed, including: Customize the application scenario test site based on the testing requirements of each application scenario, and classify the use cases of each application scenario in the test site from small to large according to speed.

3. The method according to claim 2, characterized in that Before classifying each application scenario according to the required vehicle speed, the method further includes: According to the test requirements of each scenario, roadside equipment is pre-set, including: cameras, radars, traffic lights and RSUs.

4. The method according to claim 3, characterized in that Also includes: The road length required for each scenario in the test site is adjusted according to the speed of the test vehicle.

5. The method according to claim 1, wherein The traveling along the set route includes: The driving route of the test vehicle is determined by the preset length and preset width.

6. The method according to claim 1, characterized in that Also includes: Based on the real-time calculation of the vehicle test scenario, when the test vehicle reaches the starting point of the pre-preparation area for the next scenario, the test start command is sent to the background vehicle; The background vehicle determines whether to cooperate with the test vehicle to test the scene according to the scene test standard.

7. A vehicle application scenario continuous testing system, characterized in that: include: A data processing unit, which is used to classify each application scenario according to the required vehicle speed; An operating unit is used to drive along a set route, complete the corresponding application scenario test at the same vehicle speed each time, and repeatedly drive along the set route to complete the application scenario test at all types of vehicle speeds; The roadside unit is used to configure the tested scenario in advance by issuing virtual road event information during the test process, and send the configured road event information to the test vehicle, where the configuration content includes the event type and the scope of the event impact.

8. The system according to claim 7, characterized in that: The data processing unit is further configured to calculate the vehicle test scenario in real time and, when the test vehicle reaches the starting point of the pre-preparation area for the next scenario, issue a test start instruction to the background vehicle; The background vehicle determines whether to cooperate with the test vehicle to test the scene according to the scene test standard.

Images