Whole vehicle Automatic Emergency Braking (AEB) testing verifies the ability of a finished production vehicle to detect imminent collisions and apply the brakes autonomously without driver input. Performed by accredited third-party laboratories in accordance with standards such as GB/T 39901, UN ECE R152, ISO 22839, and NCAP protocols, this testing covers car-to-car and vulnerable road user scenarios that directly determine regulatory approval and safety ratings. This article explains the technical principles, sample requirements, test items, methodologies, and applications of complete vehicle AEB testing.
Technical Overview
Automatic Emergency Braking (AEB) is an advanced driver assistance function that combines forward-looking sensors—typically 77 GHz millimeter-wave radar, monocular or stereo cameras, and increasingly lidar—with electronic brake actuation to detect an imminent collision, issue a forward collision warning (FCW), and apply braking automatically when the driver fails to react in time. Whole vehicle AEB testing validates this function on the complete, production-representative vehicle rather than on individual components or bench rigs, because real-world performance depends on the integration of sensing, perception logic, chassis control, braking hardware, and tire-road interaction.
Testing is typically conducted on closed proving grounds under strictly controlled environmental conditions. The principal reference frameworks include GB/T 39901 for passenger car AEB systems, UN ECE Regulation No. 152 for M1 category vehicles, UN ECE Regulation No. 131 for heavy commercial vehicles, ISO 22839 for forward vehicle collision mitigation systems, FMVSS No. 127 requirements, and the AEB test protocols published by new car assessment programs (NCAP). Because AEB performance is a key factor in both regulatory type approval and consumer safety ratings, vehicle-level testing has become one of the most extensive and technically demanding validation activities in modern vehicle development.
Testing Samples
Passenger Cars and Light Vehicles (Categories M1 and N1)
Complete production or production-intent passenger vehicles, including sedans, hatchbacks, SUVs, MPVs, and light commercial vans. The test vehicle must be in series production configuration with correctly calibrated sensor alignment, specified tire pressures, and a defined load condition (typically a driver plus instrumentation, with no additional payload). Software versions must be frozen and documented to ensure traceability of results.
Heavy Commercial Vehicles (Categories N2, N3, M2, and M3)
Trucks, tractors, and buses equipped with advanced emergency braking systems. These vehicles are evaluated against dedicated heavy-vehicle protocols that use lower speed ranges, longer stopping distances, and target objects proportioned to the sensor height and detection geometry of commercial platforms.
Test Targets and Dummies
Crashable soft vehicle targets that replicate the radar cross-section, visual appearance, and infrared signature of a real passenger car, mounted on low-profile robotic carrier platforms. Vulnerable road user testing additionally requires articulated adult and child pedestrian dummies and bicycle targets, all propelled by programmable motion systems so that impact timing and speed are repeatable within tight tolerances.
Testing Items
The complete vehicle AEB test matrix is built around standardized scenarios that represent the most common real-world collision types:
- Car-to-Car Rear stationary (CCRs): the subject vehicle approaches a stationary target at speeds typically ranging from 10 to 80 km/h.
- Car-to-Car Rear moving (CCRm): the subject vehicle closes on a target traveling at a constant lower speed.
- Car-to-Car Rear braking (CCRb): both vehicles travel at matched speed before the target decelerates at a defined rate from a specified time-to-collision value.
- Crossing pedestrian scenarios, including adults and children crossing at 50 percent and 75 percent overlap, and a child emerging from behind parked vehicles.
- Stationary and walking pedestrian scenarios in the vehicle path, including longitudinal approaches.
- Cyclist scenarios, including crossing, near-side and far-side approaches, and stationary bicycles ahead.
- Forward collision warning timing and modalities (acoustic, visual, haptic).
- Impact speed reduction, peak deceleration, and braking stability when a collision cannot be fully avoided.
- False positive response, verifying that the system does not brake spuriously when passing stationary vehicles, metal road plates, drainage covers, or roadside furniture.
- Human-machine interface verification, system status indication, malfunction detection, and manual deactivation behavior.
Testing Methods
All dynamic tests are performed on a straight, level lane of dry, high-friction asphalt with documented surface conditions. Ambient temperature, wind speed, precipitation, and illumination are controlled within protocol limits; daytime tests require minimum illumination levels, and vulnerable road user protocols include standardized night scenarios using low-beam headlamps under specified artificial or ambient lighting.
The subject vehicle is instrumented with a robotic driving system that controls steering, throttle, and braking to achieve test speed tolerances within approximately plus or minus 1 to 2 km/h and lateral placement within centimeters. Real-time kinematic (RTK) satellite positioning combined with inertial measurement units provides centimeter-level accuracy of both vehicle and target trajectories, while a high-frequency data acquisition system records warning onset, brake intervention timing, deceleration profiles, separation distance, and impact speed.
In a typical run, the target is positioned or set in motion, the subject vehicle accelerates to the specified speed, and the driver robot holds a steady course until the AEB system reacts. Each scenario is repeated across multiple valid runs to demonstrate statistical consistency. Scoring assigns full credit for complete collision avoidance, partial credit proportional to the achieved speed reduction where impact is permitted, and penalties for late warnings, insufficient braking, or unstable interventions. The complete matrix for a full vehicle commonly comprises several hundred individual runs executed over multiple test days.
Applications
Whole vehicle AEB testing serves several distinct purposes across the automotive value chain:
- Regulatory type approval and market access, demonstrating conformity with national and international requirements before a vehicle can be sold.
- NCAP safety rating submissions, where AEB scores are a decisive factor in the overall star rating presented to consumers.
- Engineering development and sign-off, enabling original equipment manufacturers to validate software releases, sensor calibrations, and hardware variants.
- Competitive benchmarking of AEB performance against market rivals.
- Quality assurance, root cause analysis for field issues, and post-market surveillance supporting recall and remediation decisions.
- Foundation validation for higher-level automated driving functions, since AEB perception and braking control form the safety baseline for combined L2 and L3 systems.
FAQ
Which standards govern whole vehicle AEB testing?
The most widely applied references are GB/T 39901 for passenger car AEB systems, UN ECE Regulation No. 152 for M1 vehicles, UN ECE Regulation No. 131 for heavy vehicles, ISO 22839 for collision mitigation systems, FMVSS No. 127, and the AEB protocols defined by new car assessment programs. The applicable framework depends on the target market and vehicle category.
What speed ranges are covered?
Car-to-car scenarios typically span roughly 10 to 80 km/h depending on the protocol, while vulnerable road user scenarios generally operate at lower speeds, commonly up to 60 km/h, reflecting typical urban collision conditions.
What are the pass criteria?
The primary criterion is complete avoidance of contact with the target. Where a protocol permits unavoidable impacts, credit is awarded for the magnitude of speed reduction before impact. Warning timing, braking stability, and run-to-run consistency are also evaluated and scored.
Is night testing required?
Yes. Pedestrian and cyclist protocols include dedicated night runs performed with low-beam headlamps under standardized lighting, verifying that camera-based perception functions reliably in low-illumination conditions.
Can test results be used for certification?
Yes. Reports issued by accredited third-party laboratories are accepted as objective evidence for regulatory type approval, NCAP rating submissions, and internal release decisions, provided the tests follow the governing protocol with full documentation of vehicle configuration, environmental conditions, and measurement traceability.