Proposal to amend GRVA/2026/26, based on GRVA-25-18, insert new para. 3.2.2. requiring manufacturers of Automated Lane Keeping Systems active in multiple Contracting Parties to provide summaries of how traffic rules were identified and assessed, specific testing carried out, and a single point of contact, insert new paras. 4.8. to 4.8.6. establishing approval procedures requiring the granting approval authority to inform receiving approval authorities at least 30 days before approval with manufacturer information and safety statements, permit receiving authorities 30 days to provide comments, require disputes to be settled under the 1958 Agreement, and apply these requirements mutatis mutandis to extension approvals, and insert footnotes [Y] and [X] providing for periodic review and specifying contact methods via WP.29/343 online platform or document.

Proposal to insert new para. 3.2.2. requiring manufacturers of Automated Lane Keeping Systems active in multiple Contracting Parties to provide information on traffic rules identification, territory-specific testing, and contact details, insert new paras. 4.8. to 4.8.6. establishing procedures for multi-territory approvals including notification of receiving approval authorities within 30 days, review and dispute resolution processes, and extension requirements, insert footnote [X] specifying communication via UNECE online platform or ECE/TRANS/WP.29/343 document, and insert footnote [Y] noting periodic review by GRVA.

Proposal to insert new para. 3.3. requiring that the use of non-durable protection shields (e.g., non-integral ferrite blocks, aluminium foil) shall be prevented, and if used, shall be duly described in the information document and test report.

Proposal to amend Table 2 in Annex 4, paragraph 4.3. to add “Scanning receiver parameters” as heading and add footnote b to minimum dwell time columns stating the selected dwell time shall, in addition, consider the cycle time of certain vehicle functions, e.g. the wiper system, amend Table 2 in Annex 5, paragraph 4.3. to add “Scanning receiver parameters” as heading and add footnote a with identical language, and amend Annex 6, paragraph 4.1. to add language that the selected dwell time shall, in addition, be sufficient for the observer(s) to assess all related vehicle functions, while also considering the cycle time of certain vehicle functions, e.g., the wiper system.

Proposal to insert a new definition of functional test configuration, amend para. 2.1.1.2. to clarify that test conditions are agreed between manufacturer and technical service and that tables provide guidance which may be extended or amended depending on vehicle characteristics, add tables specifying basic vehicle test conditions for “50 km/h mode,” “Brake mode,” and “Active ADS Mode,” add an alternative “Brake mode” with active ADS for vehicles where braking mode cannot be applied with ADS operational without ADS feature(s) activated, add AECS and AVAS test condition tables, and insert a new table cross-referencing UN Regulations with specific provisions and test configurations to demonstrate compliance with UN R10.

Proposal to require test reports provided by manufacturers to comply with paragraph 3.3. and to be attached to the test report of the technical service.

Proposal for conducting the ADS Active Test Specified in Annex 6 to clarify ADS Active Mode, clarify methods to activate ADS using test equipment or by modifying in-vehicle ADS-related ECU software, clarify test objects for ESA at component-level or system-level, and clarify test methods when ADS cannot be activated in an anechoic chamber, including testing in a non-active state using warning indicators and diagnostic functions, and testing when errors occur upon ADS activation. The proposal defines ADS Active Mode as representative ADS functions remaining operational using sensors whose inputs can be simulated within the anechoic chamber environment, with alternative test methods including application based on ESA or subsystem test results, testing with ADS not activated using steady-state driving conditions with pass/fail criteria verifying no communication errors, ECU malfunction, freeze, shutdown, or ADS system malfunctions occur, and testing with simulated sensor outputs using data from real-world driving or representative driving scenarios.