Proposal from the informal working group on Cyber Security and OTA issues (CS/OTA) to update the text:

1. Use of “802.11p” to refer to V2X communications is out of date: 802.11p is properly referred to as 802.11-OCB and other direct communication methods are in use. “V2X” is the preferred term.
2. Platooning is a niche V2X operation and not widely used: The proposal suggests to use more mainstream examples such as cooperative awareness or manoeuvre coordination.

International Telecommunication Union – Radiocommunication sector (ITU-R) Working Party (WP) 5A would like to introduce itself to UNECE WP on Automated/Autonomous Connected Vehicles (GRVA). ITU-R WP 5A addresses the radio communication issue of Land Mobile Service and is responsible for studies related to the Land Mobile Service and wireless access including RLANs (Radio Local Area Networks). Within WP 5A, Working Group (WG) 5A-5 addresses the issues pertinent to new technology, such as ITS (Intelligent Transport Systems), CAV (Connected Automated Vehicles) and MTC (Machine Type Communications).

Proposal from the informal group on on Cyber Security and OTA issues for amendments:

1. To reflect updates and the most current version of relevant standards, notably ISO/SAE 21434:2021 and ISO/PAS 5112, and
2. To update the text in line with Supplement 1 to UN R155 (WP.29/2022/54).

This liaison statement aims to inform ITU-T Study Group 16 on the publication of the Technical Reports FGAI4AD-01 and FG-AI4AD-03 concerning an automated driving safety data protocol.

Input from the GRVA task force on the screening of WP.29 regulations for their fitness in application to Automated Driving Systems and ADS vehicles (FADS).

Proposal from the ADAS task force chair on validation of Driver-Control Assistance Systems.

Proposal from the EDR/DSSAD informal group to revise and clarify the acceleration data accuracy for the lateral and longitudinal acceleration data elements and introduce procedures to verify compliance of the acceleration data with the acceleration sensor accuracy specifications. The proposal is based on the following considerations:

1. There are multiple ways in which the acceleration data accuracy tolerance can be applied. This can potentially lead to different interpretations when applied by type-approval authorities. For clarity, the accuracy tolerance is specified as “+/- 10 per cent of the full range of the accelerometer used in the ECU containing the EDR function”.
2. The proposal enables a component test (including a time-shifting algorithm to address differences in sampling rates between an EDR and bench test) to address difficulties in verifying acceleration sensor accuracy under vehicle crash tests.
3. The proposal adds a footnote to clarify that the manufacturer has discretion (option) over the format for lateral acceleration data in rollover event because such data is not recorded using the lateral airbag deployment sensors.
4. The proposal adds Annex 6 on the verification procedure with an illustration of the tolerance corridor for lateral and longitudinal acceleration.

Proposal from the EDR/DSSAD informal group to revise and clarify the acceleration data accuracy for the lateral and longitudinal acceleration data elements and introduce procedures to verify compliance of the acceleration data with the acceleration sensor accuracy specifications. The proposal is based on the following considerations:

1. There are multiple ways in which the acceleration data accuracy tolerance can be applied. This can potentially lead to different interpretations when applied by type-approval authorities. For clarity, the accuracy tolerance is specified as “+/- 10 per cent of the full range of the accelerometer used in the ECU containing the EDR function”.
2. The proposal enables a component test (including a time-shifting algorithm to address differences in sampling rates between an EDR and bench test) to address difficulties in verifying acceleration sensor accuracy under vehicle crash tests.
3. The proposal adds a footnote to clarify that the manufacturer has discretion (option) over the format for lateral acceleration data in rollover event because such data is not recorded using the lateral airbag deployment sensors.
4. The proposal adds Annex 6 on the verification procedure with an illustration of the tolerance corridor for lateral and longitudinal acceleration.

Password protected. Please contact the GRVA secretariat for more information.

Presentation (accompanied by supporting documents) to show how this subject is being addressed by other parties outside WP.29/GRVA. The materials are not submitted for as proposals for consideration or adoption.