The 20th session of the Task Force on Vehicle Sound convened on 14 April 2026. The session adopted the draft agenda and reviewed the 19th session report with a minor correction. The cross-matrix, defined in 2021 to assess traffic noise reduction policies through traffic scenarios and models, was rediscussed. A model based on RD-ASEP monitoring data was presented, showing significant deviations from EU-CNOSSOS predictions. Additional data are needed for M3/N3 and L-category vehicles. Extension of the cross-matrix to L-categories was proposed, utilising data from UN R41-06 RD-ASEP. A subgroup was established to develop scenarios, particularly for L-categories, and review available models. The next meeting is scheduled for 9 June 2026.
Proposal to establish uniform provisions concerning the approval of M2 and M3 vehicles to assist in the prevention of children being left inside. This regulation applies to vehicles of categories M2 and M3 class B and III designed or equipped primarily for the carriage of children, or special purpose vehicles of categories M2 and M3 class B and III designed specifically for the carriage of children. Vehicles shall be equipped with a physical inspection system which satisfies the requirements, including that the system shall be engaged when the vehicle master control switch is turned off and shall generate an external visual and audible warning if not disarmed within three minutes for buses not exceeding 22 passenger seats, or within five minutes for buses exceeding 22 passenger seats. The audible warning shall be greater than 60 dB(A).
The document reports on ASEAN workshops held in March 2025 and January 2026 regarding vehicle type approval systems under the 1958 Agreement and UN Regulations. The Philippines raised concerns that not all UNR type approval certificates are available in the DETA database, with no prescribed timeline for uploading newly issued approvals or removing withdrawn certificates, and that access to DETA is limited to Contracting Parties to the 1958 Agreement. The Philippines proposes designating a national DETA focal point, securing official access for all regulatory authorities, requiring complete type approval certificate packages, and relaying concerns to WP.29/UN ECE Secretariat. Singapore and Thailand expressed interest in understanding DETA obligations and minimum commitments for Contracting Parties, and requested practical guidance on UN Regulations compliance.
IWVTA is an internationally recognised whole vehicle type approval scheme within the revised 1958 Agreement framework. It establishes mutual recognition of vehicle type approvals at the whole vehicle level across Contracting Parties, eliminating requirements for further testing, documentation, or certification for safety, environment, energy, and anti-theft. IWVTA comprises two approaches: U-IWVTA applies the highest stringency of latest UN Regulations, while L-IWVTA permits omissions or lower stringency versions. The scope is limited to passenger cars. Merits include simplified type approval systems, reduced testing and administrative costs, and shortened processing times.
The 1st DETA/IWVTA Joint Workshop is scheduled for June 17, 2026, 9:30–12:30 (CEST) as a hybrid meeting in Flensburg. The provisional agenda includes opening remarks from the DETA Chair, IWVTA Chair, and President of KBA. Part 1 covers DETA topics: what DETA is, a demonstration, ASEAN countries’ expectations, and ways to make DETA more attractive. Part 2 covers IWVTA topics: what IWVTA is, industry’s expectations, issuance and acceptance of IWVTA certificates in the EU, and ways to make IWVTA more attractive. The workshop concludes with any other business.
This document updates terminology and definitions for the WP.29 Informal Working Group on Artificial Intelligence, amending AI-01-02/rev.2 as presented at the IWG’s second session. It compiles technical terms for AI in regulated automotive safety systems across four sections: Fundamental AI Concepts & Terminology, AI Methods & Models, AI Characteristics, and Data-Related Concepts & Terminology. Definitions draw from ECE/TRANS/WP.29/1182 and ECE/TRANS/WP.29/1186, among other sources, and are arranged as a living reference document supporting harmonization of AI practices for road vehicles. The document introduces new terms including Convolutional Neural Network, Neural Network, and Transformer, alongside established definitions such as Machine Learning, Generative AI, and Trustworthiness.
This document provides a consolidated list of contributions by the IWG on AI experts to the literature review activity. References are organized by type: Standards including ASPICE 4.0, IEEE standards on robustness testing, algorithmic bias, and organizational governance of AI, ISO standards on safety of intended functionality, functional safety, AI concepts and terminology, ethical considerations, AI management systems, functional safety and AI systems, road vehicle safety and AI, cybersecurity engineering, and safety for automated driving systems, SAE standards on levels of driving automation, AI data, and AI use cases, and UL4600; Policy Papers and Research Articles addressing testing autonomous vehicles, trustworthy AI, ethics of connected and automated vehicles, and safety effectiveness; Terminology Databases including IEC Electropedia and ISO Online Browsing Platform; and Regulations including Council of Europe Framework Convention on AI, EU AI Act, UN Regulation No. 155 on cybersecurity, and UN Regulation No. 156 on software updates.
The document presents a consolidated list of artificial intelligence use cases in regulated automotive safety systems, aligning with ECE/TRANS/WP.29/1182 and incorporating input from IWG on AI sessions 2–8, including contributions AI-02-04, AI-02-05, AI-06-06, AI-09-03, and AI-09-06. High priority driving function use cases include perception, planning and motion-control systems. Non-driving function use cases include driver and occupant assessment systems, and vehicle component monitoring systems. Lower priority use cases address AI in periodic technical inspection and cybersecurity, as discussed in sessions referencing AI-06-09 and AI-06-12.
29. No issues were considered under this item.