| Cooperative Intelligent Transport Systems for VRU |
| Reference Number: VCTF-14-05 |
|
Cooperative intelligent transport systems (C-ITS) enable ITS users to interact and cooperate by exchanging secured and trusted messages without prior knowledge of each other and in a non-discriminatory manner. The EU C-ITS security credential management system has three central roles that the Commission shall be responsible for ensuring are executed. Priority area IV is dedicated to ITS services for Connected and Automated Mobility (CCAM). Work on specifications under the ITS Directive will restart in 2026, covering the EU C-ITS security credential management system, harmonised C-ITS services, and fostering development and implementation of C-ITS. Currently, 2.5 million vehicles are sold and 20,000 km of roads are equipped with C-ITS, with 100,000 km covered by C-ITS services across more than 50 European cities in 21 European countries. |
| Submitted by: EC |
| Meeting Sessions: 14th VCTF session (11 Jun) |
| Document date: 11 Jun 26 |
| Relevant to: WP.29 Discussion Topic | Vehicular Communications and Connectivity |
| Click here to view the full document file |
| Automated Driving Systems : Wrap-up of the 20th (April 2026) session |
| Reference Number: ADS-21-01 |
|
The 20th ADS IWG and 17th GRVA Workshop on ADS convened in Bangkok from April 27 to May 1, 2026. OPIs consolidated draft text for the Guidance and Interpretation document (GID) on ADS, addressing DDT performance, application for approval, user interactions, SMS, ISMR, safety case, and assessment provisions. The GID would be submitted to GRVA in May and WP.29 in June as an informal document, then officially in September and November. Numerous amendment proposals were discussed, including clarifications on crash causation, priority vehicles, road safety agents, MRC requirements, remote assistance, and scenario testing. The next session in Brussels (July 14-17) aims to finalize the GID, with Phase 2 work items to be considered thereafter. |
| Meeting Sessions: 21st ADS session (14-17 Jul) and 17th GRVA-WS-ADS session (27 Apr-1 May) |
| Document date: 15 Jun 26 |
| Relevant to: WP.29 Regulatory Project | Automated Driving Systems and WP.29 Regulatory Project | Data Storage Systems for Automated Driving |
| Click here to view the full document file |
| Information on the amendments introduced in the draft a new United Nations Regulation on Automated Driving Systems |
| Reference Number: WP.29-199-07 |
|
GRVA reviewed the advance copy of ECE/TRANS/WP.29/2026/137 circulated in April 2026 and proposed modifications integrated in the final version in June 2026. The amendments replace [ADS], [This Regulation], [XXX], and [number of this Regulation] with [185]; amend Contents, paragraph references, and numbered paragraphs; add periods and remove brackets; renumber paragraphs 1.4.11.5, 1.4.11.5.1., and 1.4.11.5.2. as 1.4.12., 1.4.12.1., and 1.4.12.2.; replace square brackets with parentheses and examples in tables; and amend fallback requirements and data recording specifications. |
| Submitted by: GRVA |
| Meeting Sessions: 199th WP.29 session (22-26 Jun) |
| Document date: 15 Jun 26 |
| Document status: Adopted by WP.29 |
| Relevant to: WP.29 Regulatory Project | Automated Driving Systems and UN Regulation No. 185 | Approval of vehicles with regard to their Automated Driving Systems |
| Click here to view the full document file |
| UN R152: Comments on GRVA/2026/21 |
| Reference Number: AEBS2-02-02 |
|
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 M1. 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. |
| Submitted by: OICA and CLEPA |
| Meeting Sessions: 2nd AEBS2 session (18 Jun) |
| Document date: 18 Jun 26 |
| Relevant to: UN Regulation No. 152 | Automatic Emergency Braking for M1/N1 vehicles |
| Click here to view the full document file |
| On-Board Authentication/Authorisation |
| Reference Number: WP.29-199-14 |
|
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. |
| Submitted by: FIA Foundation |
| Meeting Sessions: 199th WP.29 session (22-26 Jun) |
| Document date: 18 Jun 26 |
| Document status: Informal WP.29 review |
| Relevant to: WP.29 Discussion Topic | Vehicle data access and protection |
| Click here to view the full document file |
| Proposal to amend the list of decisions from the 25th GRVA session |
| Reference Number: GRVA-25-60 |
|
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. |
| Submitted by: EC |
| Meeting Sessions: 25th GRVA session (18-22 May) |
| Document date: 22 Jun 26 |
| Relevant to: WP.29 Regulatory Project | Data Storage Systems for Automated Driving |
| Click here to view the full document file |
| VCTF status report to WP.29 |
| Reference Number: WP.29-199-18 |
|
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. |
| Submitted by: VCTF |
| Meeting Sessions: 199th WP.29 session (22-26 Jun) |
| Document date: 22 Jun 26 |
| Document status: Informal WP.29 review |
| Relevant to: WP.29 Discussion Topic | Vehicular Communications and Connectivity |
| Click here to view the full document file |
| UN R155 and R156: Approvals for ‘out-of-scope’ vehicles |
| Reference Number: TFCS-38-03 |
|
Vehicles of categories M1, 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. |
| Submitted by: VCA |
| Meeting Sessions: 38th TFCS session (30 Jun-1 Jul) |
| Document date: 23 Jun 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management and UN Regulation No. 156 | Software Update Processes and Management Systems |
| Click here to view the full document file |
| UN R155: Questions concerning separate technical units |
| Reference Number: TFCS-38-04 |
|
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. |
| Submitted by: UK |
| Meeting Sessions: 38th TFCS session (30 Jun-1 Jul) |
| Document date: 23 Jun 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management |
| Click here to view the full document file |
| UN R155: Response to questions concerning separate technical unit approvals |
| Reference Number: TFCS-38-05 |
|
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. |
| Submitted by: UK |
| Meeting Sessions: 38th TFCS session (30 Jun-1 Jul) |
| Document date: 23 Jun 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management |
| Click here to view the full document file |
| Regulatory fitness for Automated Driving Systems: Status report |
| Reference Number: WP.29-199-19 |
|
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. |
| Meeting Sessions: 199th WP.29 session (22-26 Jun) |
| Document date: 22 Jun 26 |
| Document status: Informal WP.29 review |
| Relevant to: WP.29 Regulatory Project | Review of Regulations for Applicability to ADS Vehicles |
| Click here to view the full document file |
| UN R42: Proposal for a Supplement 3 |
| Reference Number: GRSP-TF-AVRS-27-02 |
|
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. |
| Meeting Sessions: 27th GRSP-TF-AVRS session (1 Jul) |
| Document date: 24 Jun 26 |
| Relevant to: UN Regulation No. 42 | Front and Rear Protective Devices and WP.29 Regulatory Project | Review of Regulations for Applicability to ADS Vehicles |
| Click here to view the full document file |
| GRSP AV Screening: Agenda for the 27th (July 2026) session |
| Reference Number: GRSP-TF-AVRS-27-01 |
|
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 N1, 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. |
| Meeting Sessions: 27th GRSP-TF-AVRS session (1 Jul) |
| Document date: 24 Jun 26 |
| Relevant to: WP.29 Regulatory Project | Review of Regulations for Applicability to ADS Vehicles |
| Click here to view the full document file |
| Automatic Emergency Braking: Agenda for the 2nd (June 2026) session |
| Reference Number: AEBS2-02-01/Rev.1 |
|
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. |
| Meeting Sessions: 2nd AEBS2 session (18 Jun) |
| Document date: 25 Jun 26 |
| Relevant to: UN Regulation No. 152 | Automatic Emergency Braking for M1/N1 vehicles |
| Click here to view the full document file |
| UN R155: Review of points for approval of separate technical units |
| Reference Number: TFCS-38-06 |
|
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. |
| Submitted by: NTSEL |
| Meeting Sessions: 38th TFCS session (30 Jun-1 Jul) |
| Document date: 26 Jun 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management |
| Click here to view the full document file |
| UN R156: Question on 01 series of amendments interpretation |
| Reference Number: TFCS-38-07 |
|
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. |
| Submitted by: NTSEL |
| Meeting Sessions: 38th TFCS session (30 Jun-1 Jul) |
| Document date: 26 Jun 26 |
| Relevant to: UN Regulation No. 156 | Software Update Processes and Management Systems |
| Click here to view the full document file |
| CS/OTA Task Force: Agenda for the 38th (June 2026) session |
| Reference Number: TFCS-38-01/Rev.3 |
|
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. |
| Meeting Sessions: 38th TFCS session (30 Jun-1 Jul) |
| Document date: 29 Jun 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management and UN Regulation No. 156 | Software Update Processes and Management Systems |
| Click here to view the full document file |
| UN R155: Proposal to address approvals by one or more authorities |
| Reference Number: TFCS-38-08 |
|
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. |
| Submitted by: OICA and CLEPA |
| Meeting Sessions: 38th TFCS session (30 Jun-1 Jul) |
| Document date: 29 Jun 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management |
| Click here to view the full document file |
| Component/STU type approval under UN R155 |
| Reference Number: TFCS-38-09 |
|
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. |
| Submitted by: CLEPA |
| Meeting Sessions: 38th TFCS session (30 Jun-1 Jul) |
| Document date: 29 Jun 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management |
| Click here to view the full document file |
| UN R155: Proposal to amend GRVA-25-32 |
| Reference Number: TFCS-38-10 |
|
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. |
| Submitted by: UK |
| Meeting Sessions: 38th TFCS session (30 Jun-1 Jul) |
| Document date: 29 Jun 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management |
| Click here to view the full document file |
| Cyber security: Modifications to GRVA-25-30 |
| Reference Number: TFCS-38-12 |
|
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. |
| Meeting Sessions: 38th TFCS session (30 Jun-1 Jul) |
| Document date: 30 Jun 26 |
| Relevant to: UN Regulation No. 13 | Heavy-Duty Vehicle Braking, UN Regulation No. 13-H | Light-Duty Vehicle Braking, UN Regulation No. 79 | Steering Equipment, UN Regulation No. 89 | Speed Limitation Devices, UN Regulation No. 131 | Advanced Emergency Braking Systems, UN Regulation No. 130 | Lane Departure Warning Systems, UN Regulation No. 178 | Emergency Lane-Keeping Systems, UN Regulation No. 155 | Cyber Security and Cyber Security Management, UN Regulation No. 156 | Software Update Processes and Management Systems, UN Regulation No. 152 | Automatic Emergency Braking for M1/N1 vehicles, UN Regulation No. 157 | Automated Lane-Keeping Systems (ALKS), UN Regulation No. 171 | Driver-Control Assistance Systems (DCAS), and UN Regulation No. 175 | Acceleration Control for Pedal Error |
| Click here to view the full document file |
| CS/OTA: Draft updated terms of reference |
| Reference Number: TFCS-38-02/Rev.1 |
|
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. |
| Meeting Sessions: 38th TFCS session (30 Jun-1 Jul) |
| Document date: 30 Jun 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management and UN Regulation No. 156 | Software Update Processes and Management Systems |
| Click here to view the full document file |
| UN R94: Compatibility assessment proposal for Y-category vehicles |
| Reference Number: GRSP-TF-AVRS-27-07 |
|
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. |
| Submitted by: BASt |
| Meeting Sessions: 27th GRSP-TF-AVRS session (1 Jul) |
| Document date: 30 Jun 26 |
| Relevant to: UN Regulation No. 94 | Occupant Protection in Frontal Collisions and WP.29 Regulatory Project | Review of Regulations for Applicability to ADS Vehicles |
| Click here to view the full document file |
| GRSP AV Screening: Minutes of the 26th (May 2026) session |
| Reference Number: GRSP-TF-AVRS-26-27 |
|
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 N1Y 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. |
| Meeting Sessions: 26th GRSP-TF-AVRS session (22 May) |
| Document date: 30 Jun 26 |
| Relevant to: UN Regulation No. 94 | Occupant Protection in Frontal Collisions, UN Regulation No. 127 | Pedestrian Safety, UN Regulation No. 137 | Restraint System in Frontal Impact, WP.29 Regulatory Project | Review of Regulations for Applicability to ADS Vehicles, and WP.29 Regulatory Project | Approval of vehicles of category Y (without occupants) with regard to their crash safety |
| Click here to view the full document file |
| UN R127: Status of work on application to Y-category vehicles |
| Reference Number: GRSP-TF-AVRS-27-06 |
|
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. |
| Submitted by: EC |
| Meeting Sessions: 27th GRSP-TF-AVRS session (1 Jul) |
| Document date: 30 Jun 26 |
| Relevant to: UN Regulation No. 127 | Pedestrian Safety and WP.29 Regulatory Project | Review of Regulations for Applicability to ADS Vehicles |
| Click here to view the full document file |