RegVault

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

UN R171 — Supplement 2 to the 01 series of amendments

Supplement 1 → 2

WP.29 vote: 200th session (17–20 November 2026)
What changed
  • At speeds up to 130 km/h, the system may now also withhold HORs on a “Highway-like” road, which new paragraph 2.28.1. defines.
  • A manoeuvre can start only if, among other conditions, the driver is not deemed disengaged for more than 2 seconds immediately before its start.
  • In Annex 3, the manufacturer must now establish processes to manage safety during the operation phase, including monitoring of DCAS operation.
Why
  • The change to paragraph 5.5.4.2.6.5. allows withholding of hands-on requests for highway-like roads.
  • Other changes clarify the system behaviour when leaving system boundaries and the disengagement requirements before a manoeuvre starts.
  • New paragraph 3.5.5. of Annex 3 clarifies that processes are necessary to manage safety during the operation phase of the vehicle lifecycle.

Q1What changed78 changes

Highway-like roads and withholding of HORs (paras. 2.28.1. and 5.5.4.2.6.5.)

New paragraph 2.28.1. defines a “highway-like road”: a section of non-highway that fulfils five characteristics for a reasonable distance. They include at least two lanes in the driving direction and a designated road speed limit of at least 80 km/h. The system may now withhold HORs on a “Highway” or a “Highway-like” road at a speed up to 130 km/h. When capable of this on highway-like roads, the system must aim to avoid frequent fluctuations between being able and not able to withhold HORs. Before withholding HORs, the system must aim to check at least 500 m or 30 seconds of qualifying road ahead, or use an equivalent strategy. In that case, the manufacturer must demonstrate safe operation with cyclists, by avoiding a collision with a longitudinally travelling cyclist ahead in lane.

“Highway-like road” means a section of non-highway on which all of the following characteristics are fulfilled for a reasonable distance:
Has at least two lanes in the direction the vehicles are driving;
16 more changes in this group — open in Compare

Manoeuvres and driver disengagement (paras. 5.3.7.2.1.1., 5.3.7.2.1.13. and 5.3.7.2.4.3. to 5.3.7.2.4.10.)

A manoeuvre can start only if the driver is not deemed to be disengaged for more than 2 seconds immediately before its start. Before this change, a manoeuvre could only be initiated if the driver was not detected to be disengaged. The description of system behaviour when the driver is detected to be disengaged during a manoeuvre is now paragraph 5.3.7.2.1.13. Its examples are now aborting the manoeuvre, fully executing a manoeuvre or bringing the vehicle to a safe stop. Paragraphs 5.3.7.2.4.4. to 5.3.7.2.4.11. are renumbered as 5.3.7.2.4.3. to 5.3.7.2.4.10. A RegVault Note explains that the proposal also prints “5.3.7.2.4.3. (Reserved)”; this Note is not part of the official text.

A manoeuvre shall only be initiated if the driver is not detected deemed to be disengaged (as specified in paragraphs 5.5.4.2.4. and 5.5.4.2.5.) for more than 2 seconds immediately prior to its start, and
has Has commanded the system to perform the manoeuvre for a driver-initiated manoeuvre; or
13 more changes in this group — open in Compare

Visual disengagement and re-engagement (paras. 5.5.4.2.5.2., 5.5.4.2.5.2.1. and 5.5.4.2.7.1.)

Before this change, the dashboard and instrument panel were not a driving task relevant area for the assessment of visual disengagement. Now they may be one, but only while manoeuvre relevant information is displayed, for a maximum duration of 3 seconds. The EOR warning time must not be extended with the time the driver’s gaze is directed towards the dashboard or instrument panel. For visual reengagement, eye gaze or head posture must be re-directed towards a currently driving task relevant area, except the dashboard and instrument panel. The examples for prolonged periods without driver input now include an assessment of changes in gaze direction (5.5.4.2.7.1.). Paragraph 5.5.4.2.2.3. is renumbered as 5.5.4.2.2.2.

An outline of the driving task relevant areas, and when they are relevant, shall be specified by the manufacturer in the documentation provided to the Type Approval Authority. For the purpose of the assessment of visual disengagement, the dashboard and instrument panel shall not may be considered as a driving task relevant area only while manoeuvre relevant information (as detailed in paragraph 5.5.4.1.8.1.) is displayed for a maximum duration of 3 seconds.
The EOR warning time shall not be extended with the time the drivers gaze is directed towards the dashboard or instrument panel.
3 more changes in this group — open in Compare

Lane change with an approaching vehicle at speeds up to 60 km/h (para. 6.2.4.1.)

At speeds up to 60 km/h, the system may deviate from the assessment for an approaching vehicle in paragraph 6.2.4.1. The manufacturer must then explain to the Type Approval Authority the distances and timings for an approaching vehicle under which a lane change can start. The manufacturer must also provide evidence of those situations being deemed controllable for other road users.

At speeds up to 60 km/h the system may deviate from this assessment. In these cases, the manufacturer shall explain the distances and timings for an approaching vehicle under which a lane change manoeuvre can be started to the Type Approval Authority, and provide evidence of those situations being deemed controllable for other road users.

Annex 3: safety during the operation phase, documentation and definitions

The manufacturer must now establish processes to manage safety in the operation phase, including DCAS operation monitoring and remedial actions when necessary (3.5.5.). The former paragraphs 3.5.5. and 3.5.6. become 3.5.6. and 3.5.7., and their references change. Paragraph 3.5.7. becomes paragraph 3.4.5., after paragraph 3.4.4.2., and now says “proposing” instead of “inviting”. The definitions of “Highway” and “Non-Highway” in paragraphs 2.15. and 2.16. are deleted. New paragraph 1.1.1. of Appendix 2 defines “Evidence” as material pertinent to demonstrating the validity of a claim, for example physical test or simulation results. Paragraph 2.3.2. of Appendix 2 now refers to paragraph 5.5.3.2.3.

The manufacturer shall establish processes to manage safety during the operation phase of the product lifecycle, including carrying out monitoring of DCAS operation and taking remedial actions when necessary.
The manufacturer shall demonstrate that periodic independent internal process audits are carried out to ensure that the processes established in accordance with paragraphs 3.5.1 . to 3.5.43.5.5. are implemented consistently.
10 more changes in this group — open in Compare

Annex 4: base and extended tests, repeatable outcomes and a bicycle target test

The Type Approval Authority or the Technical Service acting on its behalf must perform or witness all of the relevant base tests during approval. At least one extended test associated with each applicable base test must also be performed or witnessed during the approval process. Under new paragraph 4.2.2.2., the manufacturer must explain when identical initial conditions may not always give a repeatable outcome to the Type Approval Authority. They must agree on test parameter ranges that do not modify the objective of the test scenario and diverge from other requirements of this Regulation. New paragraph 4.2.5.2.16. adds a test with a longitudinally moving bicycle target ahead in lane, at 20 (+1/-1) km/h in the base test. The extended test uses different offsets, a different VUT speed and a different bicycle target speed within 10-25 km/h.

This Annex defines physical tests with the purpose to verify the technical requirements applicable to the system and the declaration made by the manufacturer according to Appendix 4 to Annex 3. All of the relevant base tests in this annex shall be performed or witnessed by the Type Approval Authority or the Technical Service acting on its behalf (hereafter referred as “Type Approval Authority”) during the approval process.
At least one extended test associated with each applicable base test shall be performed or witnessed during the approval process. Further extended tests shall be performed or witnessed during the approval process at the request of the Type Approval Authority. For those extended tests that are not performed during the approval process, the manufacturer shall provide evidence of the required system behaviour in those scenarios.
16 more changes in this group — open in Compare

System boundaries and other changes in the main text and Annex 5

If the system identifies an exceeded system or feature boundary, the system or applicable feature must leave ‘active’ mode, except for the driver unavailability response. Before this change, the system had to transition into ‘stand-by’ mode. Paragraphs 5.3.7.3.1. and 5.3.7.3.3. now refer to the system’s driver unavailability response. Introduction paragraph 17. and paragraphs 2.11., 5.3.7.1.4. and 14.2. and Annex 5 have small wording changes.

The system shall aim to detect the applicable system boundaries when DCAS or a feature of DCAS is in ‘on’ mode. If the system identifies that the system or feature boundary is exceeded, it the system or the applicable feature shall transition into ‘stand-byleave the ‘active’ mode , with the exception of the driver unavailability response, and immediately notify the driver in accordance to with the strategies described by the manufacturer as outlined in paragraph 5.3.5.2. and according to the HMI requirements defined in paragraph 5.5.4.1.
The system system’s driver unavailability response shall comply with the technical requirements and transitional provisions of the 04 or later series of amendments to UN Regulation No. 79 with respect to the Risk Mitigation Function (RMF). In the event that the driver has been determined to be unavailable following a driver disengagement warning escalation sequence as defined in paragraph 5.5.4.2.6., the system shall appropriately activate the Risk Mitigation Function in order to come to a safe stop in accordance with the RMF requirements.
7 more changes in this group — open in Compare
See every change side by side in Compare

Q2Why it changed

Proposed by
Task Force on Advanced Driver Assistance Systems
Working party
GRVA, 25th session (June 2026)

Reasons

  • Paragraph 2.28.1. defines highway-like road, a road type which relates to withholding of hands-off requests. Paragraph 5.5.4.2.6.5. is amended to allow withholding of hands-on requests for highway-like roads.

    Sources (2)
    “Paragraph 2.28.1. is added to define highway-like road, a road-type which relates to withholding of hands-off requests.”
    “Paragraph 5.5.4.2.6.5. is amended to allow for withholding of hands-on requests for highway-like roads.”
  • Paragraph 5.3.5.1. is amended to clarify system behaviour when leaving system boundaries. Paragraph 5.3.7.2.1.1. is amended to clarify the disengagement requirements before a manoeuvre is initiated. Paragraph 5.3.7.2.1.13. is former paragraph 5.3.7.2.4.3., moved to a more appropriate position.

    Sources (3)
    “Paragraph 5.3.5.1. is amended to clarify system behaviour when leaving system boundaries.”
    “Paragraph 5.3.7.2.1.1. is amended to clarify disengagement requirements prior to a manoeuvre being initiated.”
    “Paragraph 5.3.7.2.1.13. is former paragraph 5.3.7.2.4.3. moved to more appropriate position.”
  • Paragraph 6.2.4.1. is amended to allow alternative strategies for lane changes at lower speed.

    Source
    “Paragraph 6.2.4.1. is amended to allow for alternative strategies to be used for lower speed lane changes.”
  • New paragraph 3.5.5. of Annex 3 clarifies that processes are necessary to manage safety during the operation phase. New paragraphs 1.1. and 1.1.1. of Annex 3, Appendix 2 define “Evidence” in alignment with the definition used by the IWG ADS. The Annex 4 introduction now makes clear which tests must be conducted and which the Type Approval Authority can request. New paragraph 4.2.2.2. takes into account challenges with track testing of complex systems.

    Sources (4)
    “Paragraph 3.5.5. is added to clarify the necessity of establishment of processes to manage safety during the operation phase of the vehicle lifecycle.”
    “New subparagraphs 1.1. and 1.1.1. are added to define the term ‘Evidence’ in alignment with the definition used by the IWG ADS.”
    “Introduction is amended to clarify which base/extended tests are required to be conducted and which can be further requested by the Type Approval Authority.”
    “Paragraph 4.2.2.2. is inserted to take into account challenges with track testing complex systems.”
  • The amendments to Introduction paragraph 17. and paragraph 2.11. are grammatical corrections. Paragraphs 2.15. and 2.16. of Annex 3 are deleted due to duplication. Other changes clarify the terminology for the driver unavailability response, eliminate redundancy or fix a numbering error.

    Sources (5)
    “Amendments to the introduction paragraph 17. and paragraph 2.11. are grammatical corrections.”
    “Paragraphs 2.15. and 2.16. are deleted due to duplication.”
    “Paragraphs 5.3.7.3.1. and 5.3.7.3.3. are amended to clarify the terminology for the system’s driver unavailability response and references to the Risk Mitigation Function (RMF).”
    “Paragraph 5.3.7.2.3.1. is amended to eliminate redundancy.”
    “Paragraph 5.5.4.2.2.3 is amended for a numbering error.”

Document trail

  1. 2026-04ProposalECE/TRANS/WP.29/GRVA/2026/18Proposal by the Task Force on Advanced Driver Assistance Systems
  2. —Amended in sessionGRVA-25-57Consolidated text prepared by the experts of GRVA
  3. —Working party adoptsECE/TRANS/WP.29/GRVA/25Session report, para. 43
  4. 2026-09Sent to WP.29ECE/TRANS/WP.29/2026/194Text that GRVA sent to WP.29 and AC.1
  5. PendingWP.29 voteScheduled for the 200th session (17–20 November 2026)
  6. PendingIn forceDate not yet known

Q3Who is affected

Vehicle manufacturer

  • Make sure manoeuvres start only if the driver was not deemed disengaged for more than 2 seconds immediately before (5.3.7.2.1.1.).
  • If the system can withhold HORs on highway-like roads, demonstrate safe operation with a cyclist ahead (Annex 4, 4.2.5.2.16.).
  • Update the description of the boundary conditions for withholding HORs to cover highway-like roads.
  • If you use another strategy for the HOR withholding duration, document it and demonstrate it to the Type Approval Authority.
  • If the system deviates at speeds up to 60 km/h, explain the distances and timings to the Type Approval Authority.
  • In these cases, provide evidence that those situations are deemed controllable for other road users.
  • Establish processes to manage safety in the operation phase, including DCAS operation monitoring and remedial actions when necessary (3.5.5.).
  • If identical initial conditions may not give a repeatable outcome, explain and agree parameter ranges with the Type Approval Authority.

Component supplier

  • Update driver monitoring logic for the new dashboard and instrument panel rules (5.5.4.2.5.2.1.).
  • Do not extend the EOR warning time with the time the driver’s gaze is on the dashboard or instrument panel.

Technical service / Approval authority

  • Perform or witness all of the relevant base tests and at least one extended test for each applicable base test.
  • Run the bicycle target test of paragraph 4.2.5.2.16. for systems capable of withholding HORs on highway-like roads.
  • As Type Approval Authority, agree test parameter ranges for systems whose outcome may not be repeatable from identical initial conditions.
  • As Type Approval Authority, be ready for explanations and evidence on lane changes deviating at speeds up to 60 km/h.

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