RegVault

UN R171 Supplement 3 (00 series) · UNECE Regulation No. 171 (ECE R171) — Uniform Provisions Concerning the Approval of Vehicles with regard to Driver Control Assistance Systems.

UN R171 — Supplement 3 to the 00 series of amendments

Supplement 2 → 3

Adopted at the WP.29 197th sessionEntry into force 2026-06-04
What changed
  • Systems that include any feature that performs system-initiated manoeuvres are not permitted to be approved to this Regulation (para. 5.3.7.2.4.).
  • Several provisions and Annex 4 tests on system-initiated manoeuvres and lane changes are deleted or now “(Reserved)”.
  • If the manufacturer is to take remedial action addressing DCAS design, the Type Approval Authority must upload the information to DETA. The upload must be no later than 14 days after receipt, and new Annex 6 gives guidance for it.
Why
  • System-initiated manoeuvres were introduced in a new series of amendments, but some text on them still remained in the original series.
  • The proposal is looking to remove any reference to them, to avoid confusion over whether they are part of the original series.
  • The proposal ECE/TRANS/WP.29/GRVA/2025/30 was created to implement the amended provisions of paragraph 7.2.2.2. on the use of DETA.

Q1What changed55 changes

System-initiated manoeuvres are not permitted (paras. 5.3.7.2.4. and 5.3.7.2.1.1.)

Systems that include any feature that performs system-initiated manoeuvres are not permitted to be approved to this Regulation. Before, paragraph 5.3.7.2.4. said that the requirements of the paragraph and its subparagraphs apply to the feature(s) capable of performing system-initiated manoeuvres. Reserved paragraph 5.3.7.2.4.1. is deleted. In paragraph 5.3.7.2.1.1., item (c) is deleted. It covered sufficient notice to react for a system-initiated manoeuvre.

The requirements of this paragraph and its subparagraphs apply to the feature(s) capable of performing system-initiated manoeuvres.Systems that include any feature that performs system-initiated manoeuvres are not permitted to be approved to this Regulation.
(Reserved)
2 more changes in this group — open in Compare

Proposed manoeuvres and national traffic rules (Introduction, paras. 8. and 9.)

Paragraph 8. of the Introduction now says that some DCAS may be able to propose driving manoeuvres, instead of initiate them. The system must aim not to propose manoeuvres that would violate national traffic rules. Before, when manoeuvres were initiated by the system, the system had to be designed to follow the national traffic rules. Paragraph 9. no longer names system-initiated manoeuvres next to driver-confirmed manoeuvres.

Depending on the use case, some DCAS may be able to initiate propose driving manoeuvres. When manoeuvres are initiated by the system, the The system shall be designed aim not to follow the propose manoeuvres that would violate national traffic rules. However, when When manoeuvres are initiated by the driver, DCAS only assists the driver in operating the vehicle without ensuring compliance with national traffic rules. In either case, the responsibility remains with the driver.
It is recognized that operation in compliance with traffic rules related to driver-confirmed or system-initiated manoeuvres might not be fully achievable due to the complexity and variety of rules across the different countries of operation. The driver’s continued involvement in the driving task is deemed to compensate for this.

System-initiated lane changes and messages in the main text (paras. 5.3.7.3.2., 5.5.4.1.9., 6.2.9.2., 9.1.1. and 9.1.2.)

Paragraph 5.3.7.3.2. now applies where the system is equipped with a driver-confirmed lane change feature. The words “or system-initiated” are removed. Paragraph 5.5.4.1.9. on system messages and signals for system-initiated manoeuvres is now “(Reserved)”, and paragraphs 5.5.4.1.9.1. and 5.5.4.1.9.2. are deleted. Paragraph 6.2.9.2. on additional requirements for system-initiated lane changes is now “(Reserved)”, and paragraph 6.2.9.2.1. is deleted. In the table of paragraphs 9.1.1. and 9.1.2., the row “System-initiated lane change” is deleted.

Where the system is equipped with a driver-confirmed or system-initiated lane change feature, the RMF shall be capable of performing lane changes, in compliance with the technical requirements for systems with the purpose of bringing the vehicle to a safe stop outside its own lane of travel of the 04 or later series of amendments to UN Regulation No. 79, during an intervention on a highway to bring the vehicle towards a target stop area in a slower or emergency lane.
System Messages and Signals for System-Initiated Manoeuvres(Reserved)
6 more changes in this group — open in Compare

System-initiated manoeuvres in Annex 3 and Annex 4 (Annex 4, paras. 4.2.5.1.3. and 4.3.3.)

In Appendix 4 to Annex 3, paragraphs 3 and 4 now name driver-initiated lane changes and other driver-initiated manoeuvres, without system-initiated ones. Paragraph 2.1.8. of Appendix 2 to Annex 3, on informing the driver about system-initiated manoeuvres, is deleted. In Annex 4, paragraph 4.2.5.1.3. on system-initiated lane changes is now “(Reserved)”, and its base test and extended testing are deleted. The heading of paragraph 4.3.3. now refers to other driver-initiated manoeuvres. The rows of the category “Other system-initiated manoeuvres” are deleted from the table of paragraph 4.3.3.2. In Table A4/1, the rows for system-initiated manoeuvres and system-initiated lane change are deleted.

System’s ability to ensure safe operation when assisting lane changes (applicable to both driver- and system-initiated driver-initiated lane changes)
The system’s ability to safely perform other driver-initiated or system-initiated manoeuvres in non-highway environments without driver intervention, alternatively indicated as “Not Applicable”:
18 more changes in this group — open in Compare

Upload to DETA within 14 days (para. 7.2.2.2.)

If remedial action addressing DCAS design is to be taken by the manufacturer, the Type Approval Authority must upload the information to “DETA”. The upload must be made without undue delay but no later than 14 days after receipt. Before, paragraph 7.2.2.2. said “without undue delay” and gave no number of days. The paragraph now also says that Annex 6 contains the guidance for uploading the information to “DETA”. A footnote web address changes from “https://unece.org/data-sharing” to “https://www.unece.org/trans/main/wp29/datasharing.html”.

If remedial action addressing DCAS design is to be taken by the manufacturer, the Type Approval Authority shall upload the information received from the manufacturer in the English language to the secure internet database "DETA", established by the United Nations Economic Commission for Europe, without undue delay but no later than 14 days after receipt, to communicate this information to all Type Approval Authorities. The information shall be sufficient to understand the incident, the cause of it and the remedial action. Annex 6 contains the guidance for uploading the information to "DETA".
https://unece.org/data-sharingwww.unece.org/trans/main/wp29/datasharing.html

New Annex 6: Guidance for data exchange via DETA

New Annex 6 gives guidance to the approval authorities of Contracting Parties to the 1958 Agreement on the use of DETA for paragraph 7.2.2.2. The approval authority that granted the type approval is the “notifying authority”. It must communicate with the manufacturer, upload the required information as pdf files and enter a notification in the tab “News”. It must complete paragraph 6(b) and (c) as soon as possible but at least within 14 days on receiving the remedial action information. These actions do not absolve it from the requirement to report non-conformities, as outlined in Article 4 and Schedule 6 of the 1958 Agreement. The guidance recommends the approval authorities to check the “News” section of DETA on a daily basis.

Guidance for data exchange via DETA in accordance with paragraph 7.2.2.2.
Introduction
17 more changes in this group — open in Compare
See every change side by side in Compare

Q2Why it changed

Proposed by
Expert from United Kingdom of Great Britain and Northern Ireland, and Germany (system-initiated manoeuvres); experts from the Task Force on Advanced Driver Assistance System (DETA guidance)
Working party
GRVA, 22nd session (June 2025)

Reasons

  • System-initiated manoeuvres were considered for the original series until the 17th session of GRVA. When they were delayed till another phase, some placeholders for provisions were already in place. The system-initiated manoeuvres were then introduced in a new series of amendments, so some text on them still remained in the original series.

    Sources (3)
    “the inclusion of system-initiated manoeuvres was being considered as part of the proposal until the penultimate session of GRVA (17th session).”
    “When it was agreed to delay system-initiated manoeuvres till another phase some placeholders for provisions were already in place”
    “However, the system-initiated manoeuvres were introduced in a new series of amendments which has meant that some of the text concerning system-initiated manoeuvres still remains in the original series.”
  • A lack of requirements may not be interpreted as a prohibition. To avoid any confusion over whether system-initiated manoeuvres are part of the original series, the proposal is looking to remove any reference to them. It also states explicitly that any system with a feature that includes such behaviour is not able to be type approved under the original series. This does not affect those approved to the 01 series of amendments.

    Sources (3)
    “To avoid any confusion over whether system-initiated manoeuvres are considered part of the original series, given that a lack of requirements may not be interpreted as a prohibition, this proposal is looking to remove any reference to system-initiated manoeuvres.”
    “It also explicitly states that any system which has a feature that includes such behaviour is not able to be type approved under the original series of amendments.”
    “This does not affect those approved to the 01 series of amendments since the provision introduced here does not reside in that version.”
  • The proposal ECE/TRANS/WP.29/GRVA/2025/30 was created to implement the amended provisions of paragraph 7.2.2.2. These provisions involve the use of the secure internet database “DETA” to exchange information on incidents with DCAS operation between type approval authorities. The initial proposal was based on the guidelines that WP.29 adopted for UN Regulation No. 155 on cybersecurity. The IWG on DETA then modified it at its fifty-second session.

    Sources (4)
    “This proposal was created to implement the amended provisions of UN Regulation No. 171, paragraph 7.2.2.2., which involve the use of the secure internet database "DETA"”
    “for the purpose of exchanging the information regarding incidents with DCAS operation between type approval authorities of the Contracting Parties.”
    “The initial proposal was based on the guidelines adopted by WP.29 (document ECE/TRANS/WP.29/2022/61) provided for implementation of UN Regulation No. 155 on cybersecurity.”
    “Further on, the proposal was modified by the IWG on DETA at its fifty-second session (document DETA-52-03-Rev.3).”
  • Proposer's reason (informal document GRVA-22-18)

    The period of 14 days is a backstop to make sure that all authorities upload the information in DETA in a timely manner. Any non-conformity found still needs to be notified as per the 1958 Agreement, and the notification in DETA does not substitute that.

    Submitted by Task Force on ADAS. Working party adoption: ECE/TRANS/WP.29/GRVA/22, para. 49.

    Sources (2)
    “Sets a specific period [14 days] that need to be included as a backstop to ensure that the information is uploaded in DETA in a timely manner by all authorities.”
    “clarifies that any non-conformity found still needs to be notified as per the’58 Agreement and the notification in DETA does not substitute that.”

Document trail

  1. —ProposalGRVA-21-53Proposal by the expert from the United Kingdom of Great Britain and Northern Ireland, presented at the twenty-first GRVA session
  2. 2025-04ProposalECE/TRANS/WP.29/GRVA/2025/31Proposal by the expert from United Kingdom of Great Britain and Northern Ireland, and Germany
  3. 2025-04ProposalECE/TRANS/WP.29/GRVA/2025/30Proposal by the experts from the Task Force on Advanced Driver Assistance System
  4. —RevisedGRVA-22-18Task Force on ADAS amendments to GRVA/2025/30
  5. —Working party adoptsECE/TRANS/WP.29/GRVA/22GRVA session report, para. 49
  6. 2025-08Sent to WP.29ECE/TRANS/WP.29/2025/143Text that GRVA sent to WP.29 and AC.1
  7. 2025-11WP.29 adoptsECE/TRANS/WP.29/1188Adopted at the 197th session (session report, para. 110)
  8. 2026-06-04In forceC.N.238.2026.TREATIES-XI.B.16.171UN depositary notification

Q3Who is affected

Vehicle manufacturer

  • Make sure that a system for approval to this Regulation has no feature that performs system-initiated manoeuvres.

Component supplier

  • No direct action for this role.

Technical service / Approval authority

  • As Type Approval Authority, upload remedial action information on DCAS design to DETA no later than 14 days after receipt.
  • As notifying authority, follow Annex 6: upload pdf files and enter the standard notification in the DETA tab “News”.
  • Check the “News” section of DETA on a daily basis, as the guidance in Annex 6 recommends.

See every change side by side

RegVault customers compare every version of UN regulations, read the consolidated text and download the PDF.

ⓘ This report gives advice only. It is not legal or type-approval advice.

More UN R171 change reports

All UN R171 change reports