Australia proposes to amend para. 2.14. to clarify that the nominal Peak Braking Coefficient value is understood to be the minimum value, and to amend para. 5.2.1.1. to simplify collision warning requirements for vehicles of category M₁. Industry objects the para. 2.14. amendment as unnecessary and potentially subject to misinterpretation as a requirement change. Industry agrees with dropping the 0.8-second prior warning requirement but finds the resulting text difficult to understand and proposes alternative wording that harmonizes para. 5.2.1.1. with paras. 5.2.2.1. and 5.2.3.1., specifying that a collision warning shall be provided no later than the start of emergency braking intervention.

FIA convened a group of interested parties to develop a scoping document on on-board authentication and authorization. Participants expressed support and called for proof of concept built around use cases. Harmonizing access methods was suggested to reduce cybersecurity fragmentation. Key question raised: which authority authenticates and grants access to legitimate parties? Next steps include establishing concrete use cases and providing a recommendation for WP.29 in November. Planned activities prior to the 200th Session of WP.29 in November include finalizing meetings with GR leaderships and other stakeholders, assembling a Group of Core CPs (GCC) to set scope based on use cases, conducting internal work, aligning with the GCC, and updating WP.29 with objective to obtain a mandate for formal work on the topic.

Proposal to amend row 13© of the List of proposed decisions on the documents reviewed during the informal consultations (GRVA-25-04/Rev.2) to specify that GRVA partly included the work on DSSAD within the IWG on ADS remit, with items to be included comprising strategic directions and data elements structured as a separate workstream under an OPI’s coordination, and DSSAD activities related to data format, accessibility, survivability and location becoming part of IWG on EDR activities, with regular online meetings organized to ensure alignment and coordination between the two groups.

The Task Force on Vehicular Communications held a virtual meeting on 11 June where presentations were made by China CAICT with support from CATARC, the European Commission DG MOVE, and SAE International on communications to improve protection of VRUs. No IWG on ITS meetings have been held since the last WP.29 session. Co-chairs are UK, U.S., and Japan; the vice-chair of TF VC is China. The next Future Networked Car Symposium will be held in hybrid format on 9 July 2026 at Palexpo, Geneva, jointly organised by ITU and UNECE, focusing on the new ADS regulation.

Vehicles of categories M₁, N, O, R, S and T may fall out of scope of UN R155 or UN R156 if they lack ECUs or do not permit software updates. Approval authorities currently make individual determinations regarding whether vehicles are in or out of scope, and justification for out-of-scope decisions must be recorded to ensure vehicles remain out of scope during the lifetime of whole vehicle approval. UN Regulation No. 10 provides precedent by allowing approvals for vehicles where certain equipment is not relevant. A similar provision could be incorporated into UN R155 and UN R156 by amending the scope and adding provisions to section 5 allowing manufacturers to obtain approvals for vehicles that do not permit software updates, with requirements of paragraph 7 not applying.

Questions address whether minimum vehicle architecture approval should be required before Part III can be used for additional devices; whether approved ESAs can be incorporated in original vehicle approval or as an extension to Part I approval; whether different terminology should replace CSMS for Part III approvals; whether second Part III approvals are permissible for vehicles already approved to Parts I and III; and what implications arise from end-of-support by ESA manufacturers.

Answers to questions on separate technical unit approvals under UN R155 clarify that a base vehicle must already hold an R155 type approval before an ESA can be added at Part III; approval authorities for different parts may differ with mutual recognition applying; the end of support period for an ESA manufacturer must be communicated to the vehicle manufacturer, with implications to be discussed by the IWG; installation of ESAs must follow vehicle manufacturer instructions without necessarily requiring separate agreement; STU data sharing agreements are required; and after ESA installation, a whole vehicle cyber security risk assessment is not necessary, though Part III must consider risks where ESA and base vehicle interactions occur. A working document is planned for submission to GRVA in January 2027. The IWG will explore whether Part II components may include equipment from certificated base vehicles under UN R155 multi-stage categorization and discuss incorporating STU into original approvals.

This status report summarizes work by expert groups on regulatory fitness for Automated Driving Systems presented to WP.29 at its 198th session. Expert groups screened UN Regulations and GTRs to determine relevance for automated vehicles and drafted amendments. As of June 2026, 92 amendment proposals across 88 Regulations have been submitted. Key closed items include overlap with ADS capabilities, test modes, monitoring passengers, and user roles. Ongoing tasks include crashworthiness regulation for category Y, ADS marker lamps, and EMC refinements. The groups concluded that urban shuttles and delivery robots represent use cases potentially requiring future category consideration based on Contracting Party and stakeholder input.

Agenda items include approval of the agenda and minutes of the previous meeting, feedback and status from GRSP-79, Joint closing meeting in Paris, and WP.29, Y-category Regulatory framework New for N₁, Y-category Pedestrian Protection UN Reg 127, UN Regulation No. 42, UN Regulation No. 134 Y-category exclusion, and any other business. Dates for next meetings are 4th September and 5th October with further meetings in November and December under consideration.

Proposal to amend para. 6.1.5. to state that sensors, cameras, radar devices, etc. being part of driver assist systems and automated driving systems may become damaged, disoriented or broken due to an impact as long as basic braking and steering performance remain intact. The amendment enables application of UN R42 to vehicles equipped with an Automated Driving System.

The agenda includes GRVA decision to refer GRVA-2026-21 and GRVA-25-36 to the IWG on AEBS, proposals to amend UN R152 paragraphs 2.14, 5.2.1.1 and 5.2.1.2 per documents ECE/TRANS/WP.29/GRVA/2026/21 and GRVA-25-36, other business, action items and next meetings scheduled 24–25 September 2026 and 2–4 November 2026.

A comprehensive cyber security risk assessment without gaps between Parts I, II, and III is required for component or separate technical unit approval. Risk assessment is difficult for manufacturers alone; contracts are required to share vulnerability information. Identification of realistic installation use cases, information sharing between approval authorities, and clarification of responsibilities are necessary. Components with no communication to the vehicle or only mechanical and power connection do not require new approval. Components sending data to the vehicle or controlling it require Part II approval and joint risk analysis by the original equipment manufacturer and installer.

The document clarifies two interpretation points regarding UN R156-01. First, software updates to registered vehicles require that an RXSWIN be assigned to every Regulation No. X type approval assessed during the update process, unless the manufacturer does not plan software updates for that particular system Regulation. Second, regarding para. 7.2.1.2.2., it is proposed to delete the requirement that software version changes be declared each time they are updated, since software versions are declared for each regulation subject to software updates following amendments to RE.3 Annex 7.

The agenda includes review of proposals for amendments to R155 concerning multistage vehicles, separate technical units and component approval, approval-authority requirements for CSMS CoC and vehicle type approval, and remote operation for ADS; review of cyber and software requirements in the ADS Regulation based on WP.29/2022/60 as amended by WP.29/2023/87; discussion of RXWIN application amendments; and consideration of terms of reference renewal ahead of mandate expiration in November 2026.

Proposal to add para. 3.2.3.1. requiring manufacturers to provide additional information on the Cyber Security Management System at request of the Approval Authority when the Certificate of Compliance for CSMS is issued by a different Approval Authority, add para. 5.1.5. allowing the Approval Authority to refuse type approval if insufficient information on the CSMS and its implementation was provided, and add para. 7.4.1.1. requiring all granting Approval Authorities to be included in reporting when different Approval Authorities are used for the Certificate of Compliance for CSMS and type approval of the vehicle type.

CLEPA welcomes questions raised by Japanese experts under doc TFCS-37-06 and identifies points requiring further clarification regarding component and STU type approval scope, technical integration, STU definition, implementation, risk assessment, impact and benefit, and post-market monitoring. CLEPA proposes that components or STUs required for initial vehicle type approval under Part I should not be subject to separate approval under Part II, noting that vehicle cybersecurity depends on vehicle-level system interactions and E/E architecture, the OEM has full visibility of system architecture, and Part I approval ensures integrated assessment.

Amend para. AI to replace the heading “Examples of documents/evidence that could be provided” with “Explanation of the requirement” and insert text stating that Part C of this document provides further guidance on the application of the Regulation to vehicles which have been modified by carrying out a transformation of the vehicle.

The Informal Working Group on Cyber Security and Software Updates will continue to consider how cyber security and software updates have a bearing on automotive safety and security, and whether any changes are necessary to the Regulations and guidance it has produced under WP.29. In particular, the IWG shall maintain official documents regarding UN R155, UN R156, and Recommendations on uniform provisions concerning cyber security and software updates; develop amendments to relevant documents; develop a proposal to amend UN Regulations under the responsibility of GRVA to record details of an RXSWIN where applicable which have been mandated by the 01 series of UN Regulation No. 156; develop proposals to amend UN Regulation No. 155 and its interpretation document to support application in national/regional frameworks for aspects such as multi-stage manufacturing; consider and develop deliverables regarding software updates after registration potentially creating a proposal for modification to the type approval numbering or a classification of update categories; support and review the application of cyber security and software update provisions across GRs notably for the Global Technical Regulation on Automated Driving Systems; and provide opportunities to participants to share knowledge, experience and ideas from implementation of national regulation/standards regarding CS/OTA as well as UN R155 and R156. The IWG will continue its activities until November 2029.

Minutes of the 26th meeting of GRSP TF on AVRS held on Tuesday 22nd of May 2026 online. The agenda and previous minutes were approved. Status reports were received from other groups, with a closing meeting on ADS fitness expected in June. GRSP reviewed consistency of ADS fitness work and UN Regulation 137 sensor updates. EC presented updates on UN Regulation N₁Y and UN Regulation 127 pedestrian protection. OICA raised discussion on frontal test procedures in Annex 3 referencing UN Regulation No. 94 for vehicles with maximum mass not exceeding 2,500 kg and UN Regulation No. 137 for vehicles with maximum mass exceeding 2,500 kg and not exceeding 3,500 kg. No comments were received on passive safety requirements for ADS steering systems. Future meetings are scheduled for 1–5 June, 1st July, 4th September, 5th October, 27th November, 1st December, and 7–11 December.

A decision was taken in mid-2025 to start drafting a new regulation collecting relevant safety requirements for Category Y vehicles. UN R127 on pedestrian safety performance could be directly amended to include Y-category vehicles instead of including requirements in a new regulation. TF AVRS agreed to amend UN R127 to include Y-category vehicles. A draft regulation (v4) is available proposing supplement 5 to the 04 series of amendments, including amendment suggestions in scope to determine exemptions for Y-category vehicles based on front structural geometry dimensions rather than R-point criteria.

Y-category vehicles are equipped with an Automated Driving System and not designed to carry occupants. They may develop aggressive front structures that could harm passenger cars in accidents. The proposal introduces the Occupant Load Criterium (OLC), derived from velocity-time graphs in crash tests, as a compatibility assessment criterion. OLC multiplied by vehicle mass indicates impact aggressivity. Data from ODB tests show OLC values range from approximately 22 to 35 g across various vehicles. The proposal suggests using a maximum OLC × mass value to prevent excessively aggressive vehicle front structures while keeping current passenger car designs unaffected.

Proposal to insert provisions on software identification and software updates into UN R13, UN R13-H, UN R79, UN R89, UN R130, UN R131, UN R152, UN R156, UN R157, UN R171, UN R175, and UN R178 by adding definitions referencing Consolidated Resolution R.E.3 Annex 7, requiring manufacturers to provide Technical Services with information on hardware and software influencing performance, permitting vehicle manufacturers to apply for new approvals differentiating software versions for registered versus new vehicles, clarifying that production discontinuation does not apply when manufacturers seek approval extensions for software updates of registered vehicles, and amending communication forms to include software identification numbers and related information.

The document presents vehicle modification use cases categorized into four cases and additional scenarios. Case 1 covers components with negligible risk or cyber-relevant non-automotive devices. Case 2 addresses cyber-relevant automotive devices approved to specific regulatory requirements, requiring installation approval and vehicle type re-approval. Case 3a addresses cyber-relevant devices not approved to specific requirements, requiring component or STU approval. Case 3b covers devices controlling vehicle functions, also requiring component or STU approval. Case 4 encompasses invasive modifications or complex interactions not covered by other cases.

Proposal to amend definitions, recording triggering conditions, time zero establishment, crash test requirements, post-crash acceleration measurement, and data recording parameters:

• Amend definitions of automatically commanded steering function categories A, B1, B2, C, D, and E to clarify they are not part of a DCAS,
• Amend definition of “End of event time” to specify conditions for planar and other events,
• Amend definitions of “Engine throttle, percent full,” “Service brake status,” “Time interval between current event and previous event,” “Volatile memory,” and “VRU secondary safety system,”,
• Delete definition of “If recorded,”,
• Amend definition of “Non-volatile memory” to remove redundant text,
• Renumber “Accident Emergency Call System” from paragraph 2.2. to paragraph 2.25.,
• Insert new definitions for rollover protection system, AEBS, trigger activated, pre-event synchronization timer, blind spot monitoring system, emergency stop signal, turn signal, ACPE, ADDW, DCAS, and DDAW,
• Amend paragraph 5.3.1. on conditions for triggering recording to distinguish planar/VRU/rollover events from AEBS events and clarify that vehicles not fitted with certain systems are not required to trigger recording according to those paragraphs,
• Restructure paragraph 5.3.3. on time zero establishment to separately address planar/VRU/rollover events and AEBS events,
• Amend paragraph 5.4.3. to clarify crash test requirements,
• Amend paragraph 6.1. to clarify measurement of post-crash acceleration,
• Insert transitional provisions in paragraphs 12.12. through 12.16. establishing that as from entry into force no Contracting Party shall refuse to grant type-approvals under the 03 series of amendments, as from 1 September 2031/2029 Contracting Parties shall not be obliged to accept approvals to preceding series first issued after that date, until 1 September 2033 Contracting Parties shall continue to accept approvals issued according to preceding series first issued before 1 September 2031/2029, Contracting Parties may grant approvals according to any preceding series, and Contracting Parties shall continue to grant extensions of existing approvals to any preceding series,
• Amend Annex 1 to correct typo,
• Amend Annex 4 Table 1 to separate engine throttle and accelerator pedal data elements, increase recording intervals for rollover data, adjust recording intervals for AEBS events to −2.5 to 2.5 seconds, increase sample rates to 10 Hz for multiple data elements, add data elements for pre-event synchronization timer, trigger activated, ACPE status, ADDW status and time since warning, blind spot monitoring system status, turn signal status, DCAS status and driver monitoring system data, DDAW status and time since warning, and emergency stop signal status, and add time to collision data element for AEBS events.

Proposal for a recording interval of 600 seconds prior to collision for driver drowsiness and attention warnings (DDAW), 240 seconds for advanced driver distraction warnings (ADDW), 240 seconds prior to collision for driver monitoring warnings from the driver-control assistance system (DCAS), triggers planar, VRU, Rollover, AEBS, AEBS for pedestrian, AEBS for bicycle, and AEBS for motor vehicle, and event data recording time-to-collision (TTC) range of 0 s to 5.0 s and resolution 0.1 s for AEBS events.