Vehicle test compliance management and control method, device, equipment and medium

Abstract

The invention provides a compliance management and control method and device for vehicle testing, equipment and a medium, and the method comprises the steps: obtaining the vehicle position of a tested vehicle and corresponding video road condition information in a testing process; determining a target road corresponding to the test vehicle and a current road type of the target road according to the vehicle position and the video road condition information; determining the test compliance of the test vehicle according to the target road, the current road type, a tested road corresponding to the test vehicle and a target test rule in response to the fact that the current road type is a working condition road or a side road; generating non-compliance alarm information in response to the fact that the test compliance is non-compliance; and if the test compliance is compliance, returning to execute the step of obtaining the vehicle position of the test vehicle and the corresponding video road condition information in the test process. According to the technical scheme of the invention, the management and control efficiency and the management and control effect of vehicle testing are improved.

Description

Technical Field

[0001] This application relates to the field of vehicle road testing technology, specifically to a method, device, equipment, and medium for compliance management of vehicle testing. Background Technology

[0002] In the field of vehicle testing, especially for tests conducted in reliable road environments such as closed tracks, vehicles must travel according to a pre-set sequence of operating conditions and relevant specifications to ensure the accuracy, reliability, and validity of test data, thereby ensuring the validity of test results. Currently, in vehicle road testing, monitoring of vehicle travel paths mainly relies on manual spot checks and post-event analysis, lane line recognition technology to determine the vehicle's travel path, and the use of geofencing technology to set up geofences, triggering alarm events when a vehicle enters or leaves.

[0003] Existing methods have several shortcomings, making it difficult to comprehensively and accurately monitor the compliance of test vehicles. Specifically, relying solely on simple positioning and lane recognition technologies is prone to road inaccuracies, leading to misjudgments about whether the vehicle is traveling on the correct road conditions and making it difficult to accurately determine the vehicle's actual position and compliance. Even with the introduction of visual detection methods, they are susceptible to significant environmental interference, resulting in low accuracy in judging vehicle behavior. Furthermore, they struggle to precisely analyze the spatial relationship between the vehicle and the road, as well as whether the prescribed driving sequence is strictly followed, and cannot comprehensively cover the complex logical judgments required for various abnormal driving conditions during vehicle testing. Summary of the Invention

[0004] In view of the above-mentioned defects or deficiencies in the prior art, this application aims to provide a method, device, equipment and medium for compliance control of vehicle testing, so as to solve the problem of not being able to accurately determine whether test personnel are driving test vehicles to conduct tests in accordance with test rules.

[0005] This application provides a compliance management method for vehicle testing, the method comprising: During the test, the vehicle's location and corresponding video traffic information are obtained. Based on the vehicle location and the video traffic information, determine the target road corresponding to the test vehicle and the current road type of the target road; In response to the current road type being either a working road or an auxiliary road, the test compliance of the test vehicle is determined based on the target road, the current road type, the tested road corresponding to the test vehicle, and the target test rules. If the test compliance is non-compliant, a non-compliance alarm message is generated; if the test compliance is compliant, the process of obtaining the vehicle location and corresponding video traffic information of the test vehicle during the test is returned.

[0006] According to the technical solution provided in the embodiments of this application, optionally, determining the target road corresponding to the test vehicle and the current road type of the target road based on the vehicle location and the video road condition information includes: Based on the video road condition information and the pre-stored test site video information, the current road range corresponding to the test vehicle is determined; Based on the current road range, determine each candidate road within the current road range; Based on the vehicle's location and the centerline location of each candidate road, the target road on which the test vehicle travels and the current road type of the target road are determined.

[0007] According to the technical solution provided in the embodiments of this application, optionally, determining the target road traveled by the test vehicle based on the vehicle position and the road centerline positions of each candidate road includes: For each candidate road, the target distance between the test vehicle and the candidate road is determined based on the vehicle's position and the centerline position of the candidate road. In response to the target distance being less than or equal to the distance threshold corresponding to the candidate road, the candidate road is determined to be the target road traveled by the test vehicle; The distance threshold corresponding to the candidate road is determined based on the road width of the candidate road and a preset error.

[0008] According to the technical solution provided in the embodiments of this application, optionally, determining the test compliance of the test vehicle based on the target road, the current road type, the previously tested road corresponding to the test vehicle, and the target test rules includes: In response to the current road type being an auxiliary road, the test road to be run is determined based on the tested road corresponding to the test vehicle and the target test rules, and it is determined whether the target road is an auxiliary road corresponding to the test road to be run. In response to the auxiliary road corresponding to the road under the required operating conditions, the congestion level of the road under the required operating conditions is determined based on the video traffic information, and the test vehicle is judged to be able to detour in compliance with the congestion level. If the response is a compliant detour, then the test vehicle's testing compliance is determined to be compliant. If the detour is not compliant, then the test compliance of the test vehicle is determined to be non-compliant. If the auxiliary road is not the road corresponding to the required driving condition, then the test vehicle is determined to be compliant.

[0009] According to the technical solution provided in the embodiments of this application, optionally, determining the test compliance of the test vehicle based on the target road, the current road type, the previously tested road corresponding to the test vehicle, and the target test rules includes: In response to the current road type being a working condition road, the working condition road to be run is determined based on the tested road corresponding to the test vehicle and the target test rules, and it is determined whether the target road is a working condition road to be run. If the response is to run on the working road, then it is determined whether the test parameters of the test vehicle meet the test sub-rules corresponding to the target road in the target test rules; wherein, the test sub-rules include the number of cycles and driving parameters; If the condition is met, the test vehicle is determined to be compliant. If the requirement is not met, the test vehicle's testing compliance is determined to be non-compliant.

[0010] According to the technical solution provided in the embodiments of this application, optionally, after determining whether the target road is a road suitable for driving conditions, the method further includes: In response to the fact that the road is not a road that should be used for driving, the congestion level of the road that should be used for driving is determined based on the video traffic information, and the test vehicle is judged to be able to take a detour in compliance with the congestion level. If the response is a compliant detour, then the test vehicle's testing compliance is determined to be compliant. If the detour is not compliant, then the test vehicle's test compliance is determined to be non-compliant.

[0011] According to the technical solution provided in the embodiments of this application, optionally, after determining the target road corresponding to the test vehicle and the current road type of the target road, the method further includes: If the current road type is a connecting road, then the test vehicle is determined to be compliant. If the current road type is unknown, then the test vehicle's testing compliance is determined to be non-compliant.

[0012] This application also provides a compliance control device for vehicle testing, the device comprising: The information acquisition module is used to acquire the vehicle location and corresponding video road condition information of the test vehicle during the test process; The road recognition module is used to determine the target road corresponding to the test vehicle and the current road type of the target road based on the vehicle location and the video road condition information. The compliance judgment module is used to determine the test compliance of the test vehicle based on the target road, the current road type, the tested road corresponding to the test vehicle, and the target test rules when the current road type is a working road or an auxiliary road. The compliance processing module is used to generate a non-compliance alarm message if the test compliance is non-compliant, and to return to the step of obtaining the vehicle location and corresponding video road condition information of the test vehicle during the test if the test compliance is compliant.

[0013] This application also provides an electronic device, the electronic device comprising: Processor and memory; The processor executes the steps of the vehicle testing compliance control method as described in any embodiment by calling programs or instructions stored in the memory.

[0014] This application also provides a computer-readable storage medium storing a program or instructions that cause a computer to perform the steps of the vehicle testing compliance control method as described in any embodiment.

[0015] In summary, this application proposes a compliance control method for vehicle testing. During the testing process, the method acquires the vehicle location and corresponding video road condition information. Based on the vehicle location and video road condition information, it determines the target road and the current road type of the target road for the test vehicle. This data fusion is then used to accurately determine the road the test vehicle is traveling on. If the current road type is a working road or an auxiliary road, the test compliance of the test vehicle is determined based on the target road, the current road type, the previously tested road corresponding to the test vehicle, and the target test rules. If the test compliance is non-compliant, a non-compliance alarm is generated. If the test compliance is compliant, the method returns to the steps of acquiring the vehicle location and corresponding video road condition information during the testing process. This method achieves precise location of the road the vehicle is traveling on and can accurately determine whether the test personnel are driving the test vehicle in accordance with the test rules, thus improving control efficiency and effectiveness. Attached Figure Description

[0016] Figure 1 This is a flowchart of a vehicle testing compliance control method provided in an embodiment of this application; Figure 2 This is a flowchart of another vehicle testing compliance control method provided in the embodiments of this application; Figure 3 This is a hierarchical architecture diagram of a vehicle testing compliance management system provided in an embodiment of this application; Figure 4 This is a flowchart illustrating a test compliance determination method provided in an embodiment of this application; Figure 5 This is a schematic diagram of the structure of a vehicle testing compliance control device provided in an embodiment of this application; Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0017] The present application will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings.

[0018] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. This application will now be described in detail with reference to the accompanying drawings and embodiments.

[0019] Figure 1 This is a flowchart illustrating a compliance control method for vehicle testing provided in an embodiment of this application. See also... Figure 1 The specific compliance control methods for vehicle testing include: S110. During the test, obtain the vehicle location of the test vehicle and the corresponding video road condition information.

[0020] The test vehicle is a vehicle used for testing in a closed, reliable road environment. The test vehicle must travel according to a pre-set sequence of operating conditions and relevant specifications to ensure the accuracy, reliability, and validity of the test data, thereby ensuring the validity of the test results. Vehicle position is the current location of the test vehicle obtained based on a positioning module installed on the vehicle, and may also include the vehicle's attitude. Video road condition information is video information obtained from the environment in which the test vehicle is located, captured by imaging devices such as cameras installed on the test vehicle.

[0021] Specifically, during the test, the vehicle's location and corresponding video road condition information can be obtained in real time based on various sensors on the test vehicle.

[0022] For example, vehicle position can be obtained by fusing GNSS (Global Navigation Satellite System) and IMU (Inertial Measurement Unit) data, outputting the vehicle's six-degree-of-freedom pose information (latitude, longitude, heading angle, etc.), ensuring high-precision real-time acquisition of vehicle position and orientation. Regarding video road condition information, video stream data can be collected and calculated in real time. Video road condition information can be obtained through onboard multi-view cameras (such as a forward 120° wide-angle, a side 60° medium-focus, and a rear 150° ultra-wide-angle, etc.), facilitating subsequent auxiliary determination of the road being traveled, multi-target tracking, and driving intention analysis. This allows for the output of the current road type being traveled by the test vehicle, the number of vehicles ahead, and whether the speed of vehicles ahead is too low, providing data support for subsequent judgments.

[0023] S120. Based on the vehicle location and video road condition information, determine the target road corresponding to the test vehicle and the current road type of the target road.

[0024] The target road is the road on which the test vehicle will travel, and can include road signs, road names, etc. The current road type is the road type in the test site, such as: working road, auxiliary road, connecting road, etc. If the vehicle travels outside the test area, the current road type may be unknown.

[0025] Specifically, information about each road in the test site can be collected in advance, including road location and video footage. Furthermore, the road type can be pre-labeled for each road. By combining the vehicle location and video road condition information from the test vehicle with the pre-collected information, road comparison can be performed using video recognition and location matching to determine the target road the test vehicle is traveling on and to obtain the current road type of that target road.

[0026] S130. In response to the current road type being a working road or an auxiliary road, the test compliance of the test vehicle is determined based on the target road, the current road type, the tested road corresponding to the test vehicle, and the target test rules.

[0027] The test road is defined as the road type used in testing, encompassing various test scenarios. The auxiliary road is the road type adjacent to the test road that allows detours. The tested roads are the test roads on which the test vehicle has already completed its journey. The target test rules include the test sequence for each test road and the test rules for each test road, such as the number of cycle tests and vehicle speed. Test compliance is information used to assess whether the test vehicle's driving conforms to the target test rules, and can include both compliant and non-compliant aspects.

[0028] Specifically, if the current road type is a working road or an auxiliary road, the test vehicle's test compliance can be determined by combining the target road and the current road type with the test road and the target test rules.

[0029] Based on the above example, the test compliance of a test vehicle can be determined in the following ways, according to the target road, the current road type, the previously tested roads corresponding to the test vehicle, and the target test rules: In response to the current road type being an auxiliary road, the test road to be run is determined based on the test road corresponding to the test vehicle and the target test rules, and it is determined whether the target road is an auxiliary road corresponding to the test road to be run. In response to the auxiliary road corresponding to the road under the required driving conditions, the congestion level of the road under the required driving conditions is determined based on the video traffic information, and the test vehicle is judged to be able to detour in compliance with the congestion level. If the response is a compliant detour, then the testing of the test vehicle is deemed compliant. If the detour was not compliant, then the test vehicle's testing compliance is determined to be non-compliant. If the auxiliary road is not the road corresponding to the required operating condition, then the test vehicle's test compliance is determined to be compliant.

[0030] Among them, the "required test road" refers to the test road that should be traversed during the current testing phase. The "congestion level" describes the degree to which the test road can continue to be traversed and tested; for example, if there are too many vehicles queuing ahead, the congestion level is considered congested. "Compliant detour" refers to the compliant setting of detouring from the congested test road.

[0031] Specifically, if the current road type is an auxiliary road, the test rules analyze the various road conditions and test order required for testing, comparing them with the roads already tested for the test vehicle. This allows us to determine the next road the test vehicle should test, i.e., the road it should drive on. Furthermore, we can determine if the target road is an auxiliary road corresponding to the road it should drive on. If the target road is an auxiliary road corresponding to the road it should drive on, we need to determine if the test vehicle's detour via the auxiliary road to the road it should drive on is compliant. Therefore, by combining video traffic information, we identify the congestion level on the road it should drive on, specifically the number of vehicles queuing ahead. If the number of vehicles queuing ahead exceeds a preset number, the road it should drive on is considered congested; otherwise, it is not congested. Furthermore, if the road it should drive on is congested, the test vehicle's detour via the corresponding auxiliary road is compliant. In this case, the test vehicle's compliance is confirmed. If the congestion level of the road corresponding to the required test condition is not congested, it indicates that the test vehicle's driving on the corresponding auxiliary road may be a lazy act by the test personnel, constituting an irregular detour. In this case, the test vehicle's testing compliance can be determined as non-compliant. If the target road is not the auxiliary road corresponding to the required test condition road, it is possible that the test vehicle has not yet reached the required test condition road and is en route to it. Therefore, the test vehicle's testing compliance can be determined as compliant.

[0032] Based on the above example, the test compliance of a test vehicle can be determined in the following ways, according to the target road, the current road type, the previously tested roads corresponding to the test vehicle, and the target test rules: In response to the current road type being a working condition road, the system determines the working condition road to be tested based on the tested road corresponding to the test vehicle and the target test rules, and judges whether the target road is a working condition road to be tested. The response should then be to run on the working road, and determine whether the test parameters of the test vehicle meet the test sub-rules corresponding to the target road in the target test rules; If the conditions are met, the test vehicle's testing compliance is determined to be compliant. If the requirement is not met, the test vehicle's testing compliance is determined to be non-compliant.

[0033] The test sub-rules are detailed rules for testing a specific road condition. They may include the number of cycles and driving parameters, such as vehicle speed and acceleration. Test parameters are the relevant parameters of the test vehicle on the target road, including the number of times it travels on the target road, its speed, and its acceleration.

[0034] Specifically, if the current road type is a work condition road, the analysis of the work condition roads and test order required in the target test rules is performed. By comparing the already tested roads corresponding to the test vehicle, the next work condition road the test vehicle should test can be determined, i.e., the work condition road it should run on. Furthermore, it can be determined whether the target road is a work condition road that should be run on. If the target road is a work condition road that should be run on, it means that the test vehicle is testing according to the test order of the work condition roads in the target test rules. Further determination is needed to see if the test vehicle's test parameters meet the test sub-rules corresponding to the target road in the target test rules. If they do, it means that the test vehicle is conducting compliance testing on the target road; therefore, the test vehicle's test compliance is determined to be compliant. If it does not meet the requirements, it means that although the test vehicle is driving on the target road, its test content does not conform to the test sub-rules and cannot be used for the current test; therefore, the test vehicle's test compliance is determined to be non-compliant.

[0035] Based on the above example, after determining whether the target road is a road suitable for the required driving conditions, there may still be cases where the target road is not a road suitable for the required driving conditions, but a road suitable for other driving conditions. In this case, it can be handled in the following way: If the road is not the one that should be used for the test, the congestion level of the road that should be used is determined based on the video traffic information, and the test vehicle is judged to be able to take a detour in compliance with the congestion level. If the response is a compliant detour, then the testing of the test vehicle is deemed compliant. If the detour is not compliant, then the test vehicle's testing compliance is determined to be non-compliant.

[0036] Specifically, if the target road is a working road but not a road that should be used for testing, it's necessary to determine whether the test vehicle's driving on that road is compliant, i.e., whether skipping the required working road is compliant. It's important to note that if the test vehicle is driving on a different working road, it might be because it cannot currently drive on the required working road and needs to detour, or it might be due to an error in the testing sequence of the working roads. Therefore, the congestion level on the required working road is identified by combining previously captured video traffic information. Specifically, the number of vehicles queuing ahead is considered. If the number of vehicles queuing ahead exceeds a preset number, the required working road is considered congested; otherwise, it is not congested. Furthermore, if the required working road is congested, the test vehicle's detour is compliant, and the test compliance can be confirmed. If the required working road is not congested, the test vehicle's driving might be due to a test error by the test personnel, constituting an non-compliant detour, and the test compliance can be confirmed as non-compliant.

[0037] S140. If the test compliance is non-compliant, generate a non-compliance alarm message; if the test compliance is compliant, return to the steps of obtaining the vehicle location and corresponding video road condition information of the test vehicle during the test process.

[0038] Among them, non-compliance alerts are messages that alert testers to various situations where testing compliance is non-compliant.

[0039] Specifically, if the test compliance is non-compliant, the reason for non-compliance can be further determined, and a non-compliance alarm message can be generated based on the reason. For example, if the test vehicle is traveling on the corresponding auxiliary road when the required driving road is not congested, the generated non-compliance alarm message could be "suspected detour" or "suspected route deviation," etc.; if the test vehicle is traveling on other driving roads when the required driving road is not congested, the generated non-compliance alarm message could be "suspected route sequence error," etc. If the test compliance is compliant, it means that the next round of information collection and judgment can proceed, specifically by returning to the steps taken during the test to obtain the test vehicle's location and corresponding video traffic information.

[0040] The vehicle testing compliance control method provided in this application embodiment acquires the vehicle location and corresponding video road condition information of the test vehicle during the testing process. Based on the vehicle location and video road condition information, it determines the target road and the current road type of the target road corresponding to the test vehicle, so as to perform data fusion to accurately determine the road on which the test vehicle is traveling. In response to the current road type being a working road or an auxiliary road, the test compliance of the test vehicle is determined based on the target road, the current road type, the tested road corresponding to the test vehicle, and the target test rules. In response to the test compliance being non-compliant, a non-compliance alarm message is generated. In response to the test compliance being compliant, the process returns to the step of acquiring the vehicle location and corresponding video road condition information during the testing process. This achieves accurate location of the road on which the vehicle is traveling and can accurately determine whether the test personnel are driving the test vehicle in accordance with the test rules, thereby improving control efficiency and control effectiveness.

[0041] Figure 2 This is a flowchart of another vehicle testing compliance control method provided in this application embodiment. Based on the above embodiments, the process of determining the target road corresponding to the test vehicle and the current road type of the target road by fusing vehicle location and video road condition information is illustrated, and a test compliance determination process is added when the current road type is a connecting road or unknown. See also Figure 2 The specific compliance control methods for vehicle testing include: S210. During the test, obtain the vehicle location of the test vehicle and the corresponding video road condition information.

[0042] S220. Based on video road condition information and pre-stored test site video information, determine the current road range corresponding to the test vehicle.

[0043] The test site video information is information obtained in advance through video collection of the test site, including video information corresponding to each road in the test site. The current road range is the road range involved in the video traffic information collected in the current period, specifically the road where the test vehicle is currently traveling and the range of surrounding roads.

[0044] Specifically, the video traffic information is compared with the pre-stored test site video information. This comparison can be done through a pre-built model to obtain the road range involved in the video traffic information, and this road range is used as the current road range corresponding to the test vehicle.

[0045] S230. Based on the current road area, determine each candidate road within the current road area.

[0046] Among them, candidate roads are all roads within the current road area, which can be represented by road signs.

[0047] Specifically, the current road area is analyzed, and each road within the current road area is selected as a candidate road.

[0048] Optionally, a road-level topology network can be pre-built, and the current road range can be used to compare the candidate roads within the current road range.

[0049] S240. Based on the vehicle's location and the centerline location of each candidate road, determine the target road that the test vehicle is traveling on and the current road type of the target road. If the current road type is a working road or an auxiliary road, execute S250; if the current road type is a connecting road, execute S260; if the current road type is unknown, execute S270.

[0050] The location of the road centerline is the position of each collection point on the road centerline according to the preset collection interval, which can be latitude and longitude coordinates, etc.

[0051] Specifically, the vehicle's position is matched with the centerline position of each candidate road to determine which candidate road the test vehicle's position falls on. This candidate road is then designated as the target road for the test vehicle. Furthermore, since each road is pre-labeled with its type, the current road type of the target road can be further determined.

[0052] Based on the above example, the target road for the test vehicle can be determined according to the vehicle's position and the centerline position of each candidate road in the following way: For each candidate road, the target distance between the test vehicle and the candidate road is determined based on the vehicle's position and the position of the centerline of the candidate road. If the target distance is less than or equal to the distance threshold corresponding to the candidate road, then the candidate road is determined to be the target road traveled by the test vehicle.

[0053] The target distance is the minimum distance between the vehicle's position and all data collection points along the centerline of the candidate road, or the minimum distance between the vehicle's position and all centerline segments along the centerline of the candidate road. The distance threshold is used to determine whether the test vehicle is on the corresponding candidate road. The distance threshold for a candidate road is determined based on the road width and a preset error. The preset error is the pre-set minimum distance between the test vehicle and the road edge on the candidate road.

[0054] Specifically, for each candidate road, the distances between the vehicle's position and each data collection point or centerline segment of the candidate road's centerline are calculated. The minimum of these distances is determined as the target distance between the test vehicle and the candidate road. If the target distance is less than or equal to the distance threshold corresponding to the candidate road, it indicates that the vehicle's position is within the candidate road, and therefore, the candidate road is determined to be the target road for the test vehicle. Otherwise, the candidate road is considered not to be the target road for the test vehicle, and the next candidate road can be processed.

[0055] For example, the distance between the test vehicle and each centerline segment of the candidate road can be calculated using the following formula:

[0056] Among them, (x) i y i ) and (x i+1 y i+1 (x) represents the coordinates of the endpoints of the centerline segment of the candidate road. t y t ) represents the vehicle's position, d i This is to test the vertical distance between the vehicle and the i-th centerline segment of the candidate road.

[0057] S250. Based on the target road, current road type, the tested road corresponding to the test vehicle, and the target test rules, determine the test compliance of the test vehicle and execute S280.

[0058] S260: Determine that the test vehicle is compliant and proceed with S280.

[0059] Specifically, if the current road type is a connecting road, it means that the test vehicle is traveling on a transitional road between working roads. In this case, no judgment is required, and the test vehicle's test compliance is assumed to be compliant, so as to facilitate the next detection and judgment cycle.

[0060] S270: Determine that the test vehicle's testing compliance is non-compliant, and proceed with S280.

[0061] Specifically, if the current road type is unknown, it means that the test vehicle has left the test site. Subsequently, a non-compliance alarm message of "driving out of the road" can be triggered, and the strongest test anomaly alarm (such as audible and visual prompts and console pop-ups) can be triggered. At this time, in addition to continuing to collect vehicle location data, the collection of other test data is suspended until the test vehicle returns to the working road and the data collection and judgment process is resumed.

[0062] S280. If the test compliance is non-compliant, generate a non-compliance alarm message; if the test compliance is compliant, return to the steps of obtaining the vehicle location and corresponding video road condition information of the test vehicle during the test process.

[0063] To address the compliance monitoring needs of vehicle reliability and durability testing in closed environments, this example constructs a four-layer architecture system of "basic management - multi-source perception - fusion decision-making - application". Through multi-source data fusion and scenario-based rule judgment, it achieves accurate compliance monitoring of the entire testing process, ensuring the accuracy and comprehensiveness of test compliance judgment.

[0064] The vehicle testing compliance control method provided in this application determines the current road range corresponding to the test vehicle based on video road condition information and pre-stored test site video information. Based on the current road range, it determines each candidate road within that range. Then, based on the vehicle's position and the centerline position of each candidate road, it determines the target road the test vehicle will travel on. This method integrates positioning and vision solutions to improve the matching effect between the vehicle and the road. Furthermore, in response to the current road type being a working road or auxiliary road, the test compliance of the test vehicle is determined based on the target road, the current road type, the previously tested road corresponding to the test vehicle, and the target test rules. In response to the current road type being a connecting road, the test compliance of the test vehicle is determined to be compliant. In response to the current road type being unknown, the test compliance of the test vehicle is determined to be non-compliant. This achieves precise matching between the vehicle and the road, covers multiple judgment scenarios, and improves the test control effect.

[0065] Figure 3 This is a hierarchical architecture diagram of a vehicle testing compliance management system provided in this application embodiment.

[0066] Among them, the basic management layer, as the "digital foundation" of the system, provides the benchmark data of test field roads and test rules, which can support the upper-level perception and decision-making: (1) Road basic data: road-level topology network (including the connection relationship of various working condition roads, auxiliary roads, connecting roads, etc.), lane-level geometric information (including the coordinate sequence of road centerline, boundary polygons), dynamic tolerance threshold (distance threshold, etc.), to provide the accuracy basis for subsequent "spatial geometric matching"; (2) Test rule data: test cycle and working condition requirements, such as: driving order of working condition roads, number of cycles, etc.; test outline, including compliance judgment standards (such as test sub-rules), such as how many laps should be run on the figure-eight road, and when there are 2 or more vehicles queuing on the main road, they can legally detour to the subsequent working condition road, to provide the rule basis for the fusion decision layer. The multi-source perception layer collects real-time data of vehicles and environment through multiple types of sensors and transforms it into information that the decision layer can parse: (1) Positioning and pose perception: GNSS and IMU data are fused to output the vehicle's six degrees of freedom pose information (latitude and longitude, heading angle, etc.) to ensure high-precision real-time acquisition of vehicle position and direction; (2) Visual perception: video stream data (video road condition information) is collected and calculated in real time. Through the vehicle-mounted multi-view camera (120° wide-angle forward, 60° medium-focus side, 150° ultra-wide-angle backward), the auxiliary judgment of the road (target road) being driven, multi-target tracking and driving intention analysis are realized, and the working condition road being driven by the vehicle is output, such as: whether the number of vehicles in front is ≥2, whether the speed of the vehicles in front is too low, etc., to provide data support for the fusion decision layer. The fusion decision layer is used to integrate multi-source perception data, complete vehicle road matching and compliance logic judgment, and is the "core brain" of the system: (1) Vehicle-road matching: the distance d from the vehicle positioning point (vehicle position) to the road centerline is calculated by the vertical projection method. i Then calculate and obtain the minimum d. i That is, d minCombined with the dynamic tolerance threshold Dtolerance, such as the Dtolerance of the working road = road width / 2 – 20cm, where 20cm is the preset error, which can be modified according to the needs, and then determine whether the test vehicle is on the target road. (2) Test state management: The test process is managed by a finite state machine, including states such as "initialization, road driving, pause, test completion, and abnormality". The state is intelligently switched according to the test state returned by the driver through the system function and the information input by the perception layer (such as road matching results). (3) Rule judgment: Multiple types of scenario-based compliance rules are built in, namely target test rules (working roads that should / should not be driven, auxiliary roads, detour roads, multiple driving working roads, etc.). The compliance conclusion is output by combining "spatial geometric matching results + visual auxiliary data" for test reports and alarm decisions. The application layer is used to implement the output of monitoring results and the management of test data: (1) Real-time interaction: Provide test anomaly alarms (audio-visual prompts + console pop-ups) and test alarm handling (supports manual single-item and batch confirmation / ignore); (2) Test anomaly alarms: Generate alarm data based on calculation results and alarm rules and notify relevant responsible persons in real time via mobile terminal; (3) Data management: Record the data of the entire test process (location, vision, judgment results), and automatically generate a compliance report after the test, including "alarm statistics, work condition completion rate, and anomaly cause analysis". The work condition completion rate statistics can provide data support and basis for subsequent test decisions.

[0067] Figure 4 This is a flowchart of a test compliance determination method provided in an embodiment of this application.

[0068] The determination of test compliance follows a cyclical logic of “data collection → road matching → status and rule determination → result output”. First, the test is started and data is collected. After the test is started, the “start determination of offset” stage is entered: (1) the multi-source perception layer collects vehicle location and video stream data simultaneously; (2) the basic management layer loads the “road-level topology network, test cycle and working condition requirements, and test outline” of the current test. Then, road matching and scenario branch determination are carried out. Specifically, the branch logic of “whether the test is in progress → determine which road the vehicle is on” is used to cover four core scenarios (auxiliary road, working condition road, connecting road, not on any road, i.e. unknown).

[0069] Scenario 1: Test vehicle on auxiliary road: Determine whether "the auxiliary road is the auxiliary road of the driving condition road": When it is determined that the test vehicle is on the auxiliary road corresponding to the driving condition road, it is determined again whether the test vehicle is taking an illegal detour, that is, it is determined by visual perception that "the driving intention deviates from the driving condition road". At this time, "route deviation alarm" is triggered; otherwise, no alarm is triggered.

[0070] Scenario 2: Vehicle on working road: When it is determined that the test vehicle is driving on a working road and does not conform to the sequence set by the loop (i.e., does not match the expected path sequence) and does not meet the compliance detour rules, "suspected route sequence error" is triggered; in other cases, no alarm is triggered. Data can be provided to the test report based on the results calculated by the algorithm, such as: further "determining the working condition type" (such as working condition A, working condition B), and executing the corresponding verification rules (such as "whether the figure-eight road has been completed 3 times").

[0071] Scenario 3: Vehicles on connecting roads: Connecting roads are transitional roads between working roads. No judgment is made, and the vehicle directly enters the next cycle.

[0072] Scenario 4: Vehicle not on any road: Trigger the "Out of Road" alarm, triggering the strongest test anomaly alarm (audio-visual prompt + console pop-up). In addition to continuing to collect the test vehicle's location data, pause other test data collection. After the vehicle returns to the working road, resume the data collection and judgment process.

[0073] Other situations besides the above scenarios are explained as follows: (1) If the experiment is not started (the "Whether the experiment is in progress" is determined to be no), no alarm will be issued and the process will end; (2) If each scenario is determined to be "compliant", no alarm will be issued and the loop will continue until the experiment is completed; (3) Data that triggers alarms will be included in the compliance report analysis after the experiment ends.

[0074] The positioning technology in the above examples could consider using a high-precision map matching-based positioning method to replace part of the current spatial geometric matching positioning logic. By matching the vehicle's real-time location with the road layer in a high-precision map, the rich road attributes and topological relationships in the map are utilized to determine the vehicle's road and location. However, this approach may rely on the accuracy and timeliness of high-precision map data, and has higher requirements for data processing and matching algorithms, resulting in relatively higher costs. Visual assistance can use other sensors such as LiDAR to replace visual sensors for vehicle and road condition monitoring. LiDAR can construct a 3D point cloud map of the surrounding environment by emitting laser beams and receiving reflected signals. Based on this, the relative position of the vehicle to the road and the vehicle situation within the area can be analyzed. However, LiDAR equipment is expensive, and the complexity of data processing and analysis is also high, requiring specialized algorithms and powerful computing resources to support its effective judgment of vehicle compliance. A comprehensive judgment logic can be constructed using a rule engine. Driving rules and compliance requirements for various road conditions are written into rule scripts, and the rule engine analyzes the vehicle's positioning and visual data in real time, making judgments according to the rules. However, the configuration and maintenance of rule engines are relatively complex, and their flexibility may be somewhat insufficient when dealing with complex and ever-changing test scenarios.

[0075] The technical solution described above, based on the core architecture and layered design of spatial geometric matching and vehicle vision assistance, achieves significant optimization in four dimensions—positioning accuracy, coverage, environmental adaptability, and process efficiency—compared to existing vehicle testing monitoring technologies. It solves the problems of positioning drift (error > 30m) in existing pure GNSS positioning solutions under signal obstruction (such as tree shade) and misjudgment (such as misidentifying roadside debris as vehicles) in pure vision solutions under strong light / low illumination (< 0.1 lux). Ultimately, it controls the misjudgment rate of test vehicle compliance judgment to within 1%, which is far superior to existing technologies and can ensure the accuracy of test data. Moreover, the technical solutions described above achieve comprehensive coverage of all abnormal scenarios, leaving no monitoring gaps. They can address various typical driving anomaly scenarios in vehicle testing (including complex auxiliary roads, detour routes, and repeated routes—scenarios easily missed by existing technologies) through scenario-based rules and multi-source data complementarity. This completely overcomes the limitations of existing technologies, which can only monitor simple scenarios such as main road errors. It achieves full scenario coverage from basic main roads to complex auxiliary roads / detour routes / special repeated routes, providing comprehensive assurance for test quality control and ensuring that no driving anomaly scenario is missed, significantly improving the effectiveness of test results. Finally, the efficiency of the testing process is effectively improved, and the system has strong maintainability. Through automated management and dynamic optimization, manual intervention is reduced, maintenance costs are lowered, and testing efficiency is improved. Specifically, the manual intervention time in the testing process is reduced by more than 30%, and the overall testing efficiency is improved by 20%.

[0076] Figure 5 This is a schematic diagram of a compliance control device for vehicle testing provided in an embodiment of this application. The device includes: an information collection module 510, a road recognition module 520, a compliance judgment module 530, and a compliance processing module 540.

[0077] The system includes the following components: an information acquisition module 510, used to acquire the vehicle location and corresponding video road condition information of the test vehicle during the testing process; a road recognition module 520, used to determine the target road and the current road type of the target road based on the vehicle location and the video road condition information; a compliance judgment module 530, used to determine the test compliance of the test vehicle based on the target road, the current road type, the tested road corresponding to the test vehicle, and the target test rules if the current road type is a working road or an auxiliary road; and a compliance processing module 540, used to generate a non-compliance alarm message if the test compliance is non-compliant, and return to the step of acquiring the vehicle location and corresponding video road condition information during the testing process if the test compliance is compliant.

[0078] Based on the above example, optionally, the road recognition module 520 is further configured to determine the current road range corresponding to the test vehicle based on the video road condition information and the pre-stored test site video information; determine each candidate road within the current road range based on the current road range; and determine the target road traveled by the test vehicle and the current road type of the target road based on the vehicle position and the road centerline position of each candidate road.

[0079] Based on the above example, optionally, the road recognition module 520 is further configured to, for each candidate road, determine the target distance between the test vehicle and the candidate road based on the vehicle position and the centerline road position of the candidate road; in response to the target distance being less than or equal to the distance threshold corresponding to the candidate road, determine the candidate road as the target road traveled by the test vehicle; wherein, the distance threshold corresponding to the candidate road is determined based on the road width of the candidate road and a preset error.

[0080] Based on the above example, optionally, the compliance judgment module 530 is further configured to, in response to the current road type being an auxiliary road, determine the required test road based on the tested road corresponding to the test vehicle and the target test rules, and determine whether the target road is an auxiliary road corresponding to the required test road; in response to the target road being an auxiliary road corresponding to the required test road, determine the congestion level of the required test road based on the video traffic information, and determine whether the test vehicle should compliantly detour based on the congestion level; in response to the target road being a compliant detour, determine that the test vehicle's test compliance is compliant; in response to the target road not being a compliant detour, determine that the test vehicle's test compliance is non-compliant; in response to the target road not being an auxiliary road corresponding to the required test road, determine that the test vehicle's test compliance is compliant.

[0081] Based on the above example, optionally, the compliance judgment module 530 is further configured to, in response to the current road type being a working condition road, determine the working condition road to be driven according to the tested road corresponding to the test vehicle and the target test rule, and determine whether the target road is a working condition road to be driven; in response to the requirement that the working condition road should be driven, determine whether the test parameters of the test vehicle meet the test sub-rules corresponding to the target road in the target test rule; wherein, the test sub-rules include the number of cycles and driving parameters; in response to the requirement that the requirements are met, determine that the test compliance of the test vehicle is compliant; in response to the requirement that the requirements are not met, determine that the test compliance of the test vehicle is non-compliant.

[0082] Based on the above example, optionally, after determining whether the target road is a road suitable for driving conditions, the method further includes: a first determination module, configured to, in response to the road not being a road suitable for driving conditions, determine the congestion level corresponding to the road suitable for driving conditions based on the video traffic information, and determine whether the test vehicle should compliantly detour based on the congestion level; in response to the compliant detour, determine that the test vehicle's testing compliance is compliant; in response to the non-compliant detour, determine that the test vehicle's testing compliance is non-compliant.

[0083] Based on the above example, optionally, after determining the target road corresponding to the test vehicle and the current road type of the target road, the method further includes: a second judgment module, used to determine that the test compliance of the test vehicle is compliant if the current road type is a connecting road; and to determine that the test compliance of the test vehicle is non-compliant if the current road type is unknown.

[0084] The vehicle testing compliance control device provided in this application can execute the vehicle testing compliance control method of any embodiment of this application and can have the same technical effect as the vehicle testing compliance control method in the above embodiments.

[0085] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 6 As shown, the electronic device 600 includes one or more processors 601 and memory 602.

[0086] The processor 601 may be a central processing unit (CPU) or other form of processing unit with data processing capabilities and / or instruction execution capabilities, and may control other components in the electronic device 600 to perform desired functions.

[0087] The memory 602 may include one or more computer program products, which may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The volatile memory may include, for example, random access memory (RAM) and / or cache memory. The non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, etc. One or more computer program instructions may be stored on the computer-readable storage medium, and the processor 601 may execute the program instructions to implement the vehicle testing compliance control method and / or other desired functions described above in any embodiment of this application. Various contents such as initial external parameters and thresholds may also be stored in the computer-readable storage medium.

[0088] In one example, the electronic device 600 may further include an input device 603 and an output device 604, these components being interconnected via a bus system and / or other forms of connection mechanisms (not shown). The input device 603 may include, for example, a keyboard, a mouse, etc. The output device 604 may output various information to the outside, including warning messages, braking force, etc. The output device 604 may include, for example, a display, a speaker, a printer, and a communication network and its connected remote output devices, etc.

[0089] Of course, for the sake of simplicity, Figure 6 Only some of the components of the electronic device 600 relevant to this application are shown in this illustration; components such as buses, input / output interfaces, etc., are omitted. In addition, the electronic device 600 may include any other suitable components depending on the specific application.

[0090] In addition to the methods and devices described above, embodiments of this application may also be computer program products, which include computer program instructions that, when executed by a processor, cause the processor to perform the steps of the vehicle testing compliance control method provided in any embodiment of this application.

[0091] The computer program product can be written in any combination of one or more programming languages ​​to perform the operations of the embodiments of this application. The programming languages ​​include object-oriented programming languages ​​such as Java and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computing device, partially on the user's computing device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0092] Furthermore, embodiments of this application may also be computer-readable storage media storing computer program instructions thereon, which, when executed by a processor, cause the processor to perform the steps of the vehicle testing compliance control method provided in any embodiment of this application.

[0093] The computer-readable storage medium may be any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof.

[0094] It should be noted that the terminology used in this application is for the purpose of describing specific embodiments only and is not intended to limit the scope of this application. As shown in the specification and claims of this application, unless the context clearly indicates otherwise, words such as "a," "an," "an," and / or "the" do not specifically refer to the singular and may also include the plural. The terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, or apparatus. Without further limitations, an element defined by the phrase "comprising an..." does not exclude the presence of other identical elements in the process, method, or apparatus that includes said element.

[0095] It should also be noted that the terms "center," "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings, and are only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation on this application. Unless otherwise expressly specified and limited, the terms "installed," "connected," "linked," etc., should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication between two elements. For those skilled in the art, the specific meaning of the above terms in this application can be understood according to the specific circumstances.

[0096] This document uses specific examples to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the methods and core ideas of this application. The above descriptions are only preferred embodiments of this application. It should be noted that due to the limitations of written expression, while there are objectively infinite specific structures, those skilled in the art can make several improvements, modifications, or changes without departing from the principles of this invention, and can also combine the above technical features in an appropriate manner. These improvements, modifications, changes, or combinations, or the direct application of the inventive concept and technical solution to other situations without modification, should all be considered within the scope of protection of this application.

Claims

1. A compliance control method for vehicle testing, characterized in that, include: During the test, the vehicle's location and corresponding video traffic information are obtained. Based on the vehicle location and the video traffic information, determine the target road corresponding to the test vehicle and the current road type of the target road; In response to the current road type being either a working road or an auxiliary road, the test compliance of the test vehicle is determined based on the target road, the current road type, the tested road corresponding to the test vehicle, and the target test rules. If the test compliance is non-compliant, a non-compliance alarm message is generated; if the test compliance is compliant, the process of obtaining the vehicle location and corresponding video traffic information of the test vehicle during the test is returned.

2. The method according to claim 1, characterized in that, The step of determining the target road corresponding to the test vehicle and the current road type of the target road based on the vehicle location and the video traffic information includes: Based on the video road condition information and the pre-stored test site video information, the current road range corresponding to the test vehicle is determined; Based on the current road range, determine each candidate road within the current road range; Based on the vehicle's location and the centerline location of each candidate road, the target road on which the test vehicle travels and the current road type of the target road are determined.

3. The method according to claim 2, characterized in that, The step of determining the target road traveled by the test vehicle based on the vehicle's position and the centerline positions of each candidate road includes: For each candidate road, the target distance between the test vehicle and the candidate road is determined based on the vehicle's position and the centerline position of the candidate road. In response to the target distance being less than or equal to the distance threshold corresponding to the candidate road, the candidate road is determined to be the target road traveled by the test vehicle; The distance threshold corresponding to the candidate road is determined based on the road width of the candidate road and a preset error.

4. The method according to claim 1, characterized in that, The step of determining the test compliance of the test vehicle based on the target road, the current road type, the previously tested road corresponding to the test vehicle, and the target test rules includes: In response to the current road type being an auxiliary road, the test road to be run is determined based on the tested road corresponding to the test vehicle and the target test rules, and it is determined whether the target road is an auxiliary road corresponding to the test road to be run. In response to the auxiliary road corresponding to the road under the required operating conditions, the congestion level of the road under the required operating conditions is determined based on the video traffic information, and the test vehicle is judged to be able to detour in compliance with the congestion level. If the response is a compliant detour, then the test vehicle's testing compliance is determined to be compliant. If the detour is not compliant, then the test compliance of the test vehicle is determined to be non-compliant. If the auxiliary road is not the road corresponding to the required driving condition, then the test vehicle is determined to be compliant.

5. The method according to claim 1, characterized in that, The step of determining the test compliance of the test vehicle based on the target road, the current road type, the previously tested road corresponding to the test vehicle, and the target test rules includes: In response to the current road type being a working condition road, the working condition road to be run is determined based on the tested road corresponding to the test vehicle and the target test rules, and it is determined whether the target road is a working condition road to be run. If the response is to run on the working road, then it is determined whether the test parameters of the test vehicle meet the test sub-rules corresponding to the target road in the target test rules; wherein, the test sub-rules include the number of cycles and driving parameters; If the condition is met, the test vehicle is determined to be compliant. If the requirement is not met, the test vehicle's testing compliance is determined to be non-compliant.

6. The method according to claim 5, characterized in that, After determining whether the target road is a road suitable for the required driving conditions, the method further includes: In response to the fact that the road is not a road that should be used for driving, the congestion level of the road that should be used for driving is determined based on the video traffic information, and the test vehicle is judged to be able to take a detour in compliance with the congestion level. If the response is a compliant detour, then the test vehicle's testing compliance is determined to be compliant. If the detour is not compliant, then the test vehicle's test compliance is determined to be non-compliant.

7. The method according to claim 1, characterized in that, After determining the target road corresponding to the test vehicle and the current road type of the target road, the method further includes: If the current road type is a connecting road, then the test vehicle is determined to be compliant. If the current road type is unknown, then the test vehicle's testing compliance is determined to be non-compliant.

8. A compliance control device for vehicle testing, characterized in that, include: The information acquisition module is used to acquire the vehicle location and corresponding video road condition information of the test vehicle during the test process; The road recognition module is used to determine the target road corresponding to the test vehicle and the current road type of the target road based on the vehicle location and the video road condition information. The compliance judgment module is used to determine the test compliance of the test vehicle based on the target road, the current road type, the tested road corresponding to the test vehicle, and the target test rules when the current road type is a working road or an auxiliary road. The compliance processing module is used to generate a non-compliance alarm message if the test compliance is non-compliant, and to return to the step of obtaining the vehicle location and corresponding video road condition information of the test vehicle during the test if the test compliance is compliant.

9. An electronic device, characterized in that, The electronic device includes: Processor and memory; The processor executes the steps of the vehicle testing compliance control method as described in any one of claims 1 to 7 by calling the program or instructions stored in the memory.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a program or instructions that cause a computer to perform the steps of the compliance control method for vehicle testing as described in any one of claims 1 to 7.

Images