Current RD-ASEP derives the regulatory level based on the certified value without accounting for margin against regulatory values of the certified value. RD-ASEP additionally regulates partial acceleration, unlike current ASEP which only stipulates full-throttle acceleration. It is proposed that RD-ASEP should take into account a margin against the regulatory values of the certification values, similar to current ASEP, to prevent quiet vehicles such as BEVs from being unfairly deemed NG.

In vehicles with automatic transmissions, upshifts during testing cause SEM expected values to be exceeded. The proposal addresses three cases: vehicles with non-locked gear ratios, vehicles with locked gear ratios, and vehicles with only one gear ratio. For Case 1, such data does not meet conditions in R51-03 Annex 9 “4.5.2. Non-locked transmissions” and require no SEM correction. For Case 2, the proposal adds text to Annex 9 (7), Appendix 1, paragraphs 3.4. and 3.5., permitting substitution of maximum engine speed nMAX(AA-BB)TEST for nBBTEST when the maximum engine speed between AA’ and BB’ exceeds the engine speed at BB’.

A Universal International Whole Vehicle Type Approval issued for vehicles of category M₁ under UN R0 that includes type-approval under the UN Regulations concerned shall be considered equivalent to an EU type-approval granted under Framework Regulation (EU) 2018/858. The approval authority granting EU-WVTA must confirm for all variants and versions within the EU-WVTA vehicle type the equivalence of the Part III list and that the EU-WVTA type is covered by the IWVTA class and IWVTA type.

Presentation on technology and application validation of VRU protection services across three parts. Part 1 validates functional and process validation; Part 2 tests performance under low-density scenarios; Part 3 tests performance under high-density scenarios with three sub-scenarios: sensing multi-VRUs, multi-services concurrency, and multi-VRUs transmitting PSMs concurrently. Validation encompasses three communication approaches: vehicle-to-vehicle, infrastructure-to-vehicle, and vehicle-to-pedestrian, assessing protocol conformance, communication performance, sensing performance, and service logic triggering mechanisms.

The agenda includes a review of the schedule with next meetings on 7th July and 24th August, continuation of database analysis presentation from RDW, review of decisions and work for the next meeting, report to IWG RD-ASEP.

Task Force Data Analysis (Sub Group to IWG RD-ASEP) held its 13th meeting on Wednesday, 3rd June 2026. The group reviewed database analysis including statistical analysis of differences between expected and measured sound levels, sub-model construction, and optimization calculations for parameter tables. Discussion addressed model construction concerns, vehicle failure differentiation, and data collection requirements including approval values according to UN R117. Next meetings are scheduled for Tuesday, 7th July and Monday, 24th August 2026.

Proposal to amend UN R160:

• Amend definitions 2.8., 2.10., and 2.11. to clarify that automatically commanded steering function categories B2, D, and E are not part of a DCAS
• Delete definition 2.25.
• Amend definition 2.35. to simplify non-volatile memory
• Amend para. 2.45. to change service brake terminology
• Amend para. 2.51. to clarify time interval between events
• Amend para. 2.65. to abbreviate vulnerable road user
• Insert new definitions 2.71.–2.83. for rollover protection system, advanced emergency braking system, trigger activated, pre-event synchronization timer, blind spot monitoring system, emergency stop signal, turn signal, acceleration control for pedal error, advanced driver distraction warning system, driver drowsiness and attention warning system, driver control assistance system, and time to collision
• Restructure para. 5.3.1. to distinguish planar, VRU, and rollover events from AEBS events with specified triggers
• Amend para. 5.3.2. to clarify data locking conditions
• Restructure para. 5.3.3. to establish time zero for planar, VRU, rollover, and AEBS events
• Amend para. 5.4.3. to specify side and frontal collision tests
• Amend para. 6.1. to clarify post-crash acceleration measurement
• Insert transitional provisions 12.12.–12.16. providing that as from the official date of entry into force Contracting Parties shall not refuse type-approvals under the 03 series, as from 1 September 2031 or 2029 [date TBD] shall not accept type-approvals to preceding series first issued after that date, until 1 September 2033 shall continue accepting preceding series approvals first issued before 1 September 2031 or 2029 [date TBD], may grant approvals to preceding series, and shall grant extensions of existing approvals
• Amend Annex 4 Table 1 to split engine throttle and accelerator pedal data elements, increase sampling rates to 10 Hz, extend recording intervals for rollover events, add pre-event synchronization timer, trigger activated, ACPE status, ADDW status, DDAW status, blind spot monitoring status, turn signal status, DCAS status, DCAS driver monitoring system warnings, emergency stop signal status, and time to collision data elements, and modify footnotes accordingly