UN R79 mandates verification that appropriate warning signals are provided to the driver based on the timing of a system intervention (e.g., in the case of a Risk Mitigation Function). This proposal aims to clarify the moment of initiation of the signals to facilitate the verification of driver warnings, hazard lights, and other indicators in relation to this objectively determined initiation point. The proposal requires manufacturers to define a clear and accessible method for objectively determining the moment of initiation.

Proposal to set clear criteria for manufacturers of transformed vehicles to determine when a given transformed vehicle needs or needs not undergo a more detailed cyber security review according to the processes for transformed vehicles currently being discussed by the GRVA workshop on cybers ecurity and software updates.

The document presents a non-exhaustive list of automotive use cases of AI aligned with WP.29/1182, incorporating contributions from AI-02-04 and AI-02-05. It focuses on use cases regarding the use of artificial intelligence in regulated automotive safety systems. The list is split between driving functions (perception, planning and motion-control) and non-driving functions (driver occupant monitoring systems and monitoring systems for vehicle components or functions), following a risk-based approach.

Proposal to amend UN Regulation No. 39 (Speedometer and odometer) to introduce software update references and identification. New provisions add definitions regarding Software Identification Number, refer to Consolidated Resolution on the Construction of Vehicles (R.E.3), Annex 7, paragraph 2. Modifications address production definitively discontinued, software updates for registered vehicles, hardware and software information provision, vehicle approval for differentiating software versions, and additional information regarding software identification. The proposal references ECE/TRANS/WP.29/1175, paragraph 37, and incorporates provisions from R.E.3 Annex 7 to define R39SWIN as dedicated identifier representing type-approval relevant software information.

Proposal to amend UN R13, 13-H, 79, 89, 130, 131, 139, 140, 152, 155, 156, 157, 171, 175, and 178 by introducing provisions on software identification and software updates. Amendments add new paragraphs referring to Software Identification Number definitions in Consolidated Resolution R.E.3, require manufacturers to provide Technical Services with information on hardware and software influencing performance, permit vehicle manufacturers to apply for new approvals differentiating software versions for registered versus new vehicles while avoiding test duplication, and modify production discontinuation provisions to exclude cases where manufacturers seek approval extensions for software updates of registered vehicles.

Proposal to add work lamp definitions and requirements to UN R48, minimum height of 250 mm above ground, downward orientation, and automatic deactivation within 1 second if vehicle speed exceeds 15 km/h. Work lamps require independent manual controls and a mandatory visual operating tell-tale. Annex 1 adds item 9.32. for work lamp approval documentation.

Proposal to amend para. 8.1.5.1. (ADS UNR) of the audit of the safety policy guidance: Change “may state” to “states,” “may address” to “addresses,” and “may therefore describe” to “therefore describes.” The rationale states that using “may” in the interpretation paragraphs seems inappropriate for explaining regulatory intention, and present tense better suits these requirements.

Proposal to amend para. 5.1.3. of UN R155 to add a refusal ground where the Certificate of Compliance for the Cyber Security Management System has not been issued by the same approval authority granting type approval, and insert new para. 5.4. into UN R156 to provide that approval authorities shall not grant any type approval if the Certificate of Compliance for the Software Update Management System has not been issued by the same approval authority granting type approval. The proposal, based on TFCS-37-02, ensures that Certificates of Compliance and type-approvals for UN R155 and UN R156 are issued by the same approval authority to enable holistic assessment and clarify reporting obligations.

Proposal to account for vehicles of category X and to extend its application to vehicles without driver and manual driving controls. New sections introduce definitions for Automated Driving System features (ADSF-1 and ADSF-2) and establish requirements for door closure warning systems and locking devices for vehicles equipped with ADSF-2. Vehicles of category Y are excluded from scope. Various paragraphs are amended regarding door systems, locking mechanisms, and impact definitions to address automated driving scenarios.

For the purposes of type approval under any UN Regulation requiring the verification of the timing of a system intervention, manufacturers shall provide to the approval authority or its designated technical service information on the method by which the initiation of any system intervention can be objectively identified and retrieved, including specific flags, status bits, event codes on in-vehicle networks, or visual indications on screens; clear instructions and all necessary tools for the Technical Service to extract, access and interpret the signal identifying the initiation; documented procedures including corresponding data sources, resolution, and timing accuracy appended to the type approval test report; and, where a visual indication displayed on a screen is used, documented latency between the earliest internal point at which the system initiates the function and the moment the visual indication becomes visible on the screen, expressed as a fixed value with associated uncertainty, with the documented latency value used to correct the observed timing of the screen indication appended to the type approval test report.