Valid

GB 44721-2026Intelligent and connected vehicles — Safety requirements for automated driving systems (English PDF)

智能网联汽车 自动驾驶系统安全要求

Preview PDF

This is a limited preview

Buy now to download the full PDF (113 pages)

Need quotation for your management?

Get a formal quotation for GB 44721-2026 in 30 minutes.

Issued by

SAMR; SAC

Level / Type

National · Mandatory

Issue date

July 30, 2026

Implementation date

July 1, 2027

Scope

GB 44721-2026 is the English-translated version of 智能网联汽车 自动驾驶系统安全要求.

GB 44721-2026 is the Chinese national standard that sets the safety requirements for the automated driving systems of intelligent and connected vehicles.

It specifies the technical requirements, the safety maintenance requirements and the rules for determining the same type, and describes how those requirements, the safety case and the validation tests are checked.

The technical clauses cover performance of the dynamic driving task in nominal, critical and failure scenarios and outside the operational design conditions, minimal risk manoeuvres and human-machine interaction, with normative annexes on takeover capability monitoring, on level 3 and level 4 features, and on the safety case.

It applies to M-category and N-category vehicles with level 3 or level 4 driving automation, but not to automated parking systems. It replaces GB/T 44721-2024, was issued on 30 July 2026 and applies from 1 July 2027.

Found what you need?

Document preview — GB 44721-2026

National Standard of the People's Republic of China

ICS
43.020
Classification
T 40
Replacing
GB/T 44721-2024

Issued by: State Administration for Market Regulation; Standardization Administration of the PRC

Contents

  • Foreword3
  • 1 Scope5
  • 2 Normative references5
  • 3 Terms and definitions5
  • 4 Abbreviated terms13
  • 5 Technical requirements for ADS14
  • 6 Assurance requirements26
  • 7 Inspection of assurance requirements37
  • 8 Inspection of safety case40
  • 9 Confirmation tests44
  • 10 Determination of the same type44
  • 11 Implementation of the Standard47
  • Appendix A (Normative) Takeover capability monitoring technical requirements48
  • Appendix B (Normative) Specific technical requirements for level 3 ADS features applied to expressways and/or urban expressways50
  • Appendix C (Normative) Specific technical requirements for level 4 ADS features69
  • Appendix D (Normative) Safety case77
  • Bibliography113

1 Scope

This document specifies the technical requirements, safety maintenance requirements and determination of the same type for automated driving systems of intelligent and connected vehicles, and describes the corresponding methods for inspection of safety maintenance requirements, inspection of safety cases and validation tests.

This document applies to M-category and N-category vehicles equipped with level 3 and/or level 4 driving automation systems. This document does not apply to automated parking systems.

2 Normative references

The following referenced documents are indispensable for the application of this document. For dated references, only the version corresponding to that date is applicable to this document; for undated references, the latest version (including all amendments) is applicable to this document.

GB/T 41798, Intelligent and connected vehicles - Track testing methods and requirements for automated driving functions

GB 44497, Intelligent and connected vehicle - Data storage system for automated driving

GB/T 44719, Intelligent and connected vehicle - Methods and requirements of road test for automated driving functions

GB/T 45312, Intelligent and connected vehicles - Operational design condition for automated driving system

GB/T 47025, Intelligent and connected vehicle - Simulation test methods and requirements for automated driving function

3 Terms and definitions

For the purposes of this document, the following terms and definitions apply.

5 Technical requirements for ADS

5.1 DDT performance

5.1.1 General requirements

5.1.1.1 The safety level of ADS shall be at least equivalent to that of a qualified and attentive driver who is currently performing the DDT.

Note: Qualified and attentive refers to the driving level specified by relevant laws and regulations.

5.1.1.2 ADS shall not pose unreasonable safety risks to users and ORUs.

5.1.1.3 ADS shall identify whether the current situation complies with the ODC of the ADS feature.

5.1.1.4 In the active state, ADS shall perform all DDT.

Note: When an occupant sitting in the driver's seat intervenes, the occupant's control of the lateral and/or longitudinal motion of the vehicle may take priority over ADS.

5.1.1.5 ADS shall adopt reasonable control strategies to address performance degradation of the perception system.

5.1.1.6 For a level 3 ADS feature, if its ODD includes roads other than expressways and/or urban expressways, ADS shall at least have the capabilities of lane cruising, lane change and passing through intersections (excluding roundabouts).

Note: A bus rapid transit system operating only in dedicated lanes may not have the capability of lane change.

5.1.1.7 For a level 4 ADS feature, if its ODD includes only expressways and/or urban expressways, ADS shall at least have the capabilities of lane cruising, lane change and partially or completely entering an adjacent lane to bypass an obstacle ahead; if its ODD also includes roads other than expressways and/or urban expressways, ADS shall at least have the capabilities of lane cruising, lane change, passing through intersections (excluding roundabouts), partially or completely entering an adjacent lane to bypass an obstacle ahead, reversing and making a U-turn.

5.1.2 DDT performance in nominal scenarios

5.1.2.1 The driving behavior of ADS shall not cause a collision.

5.1.2.2 ADS shall not collide with safety-related targets.

Note: Safety-related targets refer to targets that, if collided with, may cause non-minor damage to the vehicle, or may pose safety risks to ORUs, users or infrastructure.

5.1.2.3 According to safety risks, ADS shall adjust its driving behavior, which shall at least include.

a) anticipating risks in the driving environment to reduce the possibility of encountering critical scenarios;

b) adjusting the driving speed according to safety risks;

c) controlling the longitudinal and lateral motion of the vehicle to maintain an appropriate distance from ORUs.

5.1.2.4 ADS shall adopt reasonable control strategies to address safety risks existing in areas that cannot be adequately detected.

Note: Areas that cannot be adequately detected include blind areas caused by occlusion by ORUs or obstacles, blind areas caused by road topology or shape, etc.

5.1.2.5 ADS shall detect and respond to targets and events related to its performance of DDT.

5.1.2.6 ADS shall interact safely with ORUs, which shall at least include.

a) exhibiting expected behavior and maintaining stable driving behavior;

b) conducting effective information interaction (e.g., direction-indicator lamps, stop lamps, etc.).

5.1.2.7 For a level 4 ADS feature, if a passenger requests stopping according to the method specified in C.3.1.2, ADS shall bring the vehicle to a safe stop.

5.1.2.8 According to safety risks, ADS shall not unreasonably disrupt traffic flow and cause a decrease in traffic efficiency.

5.1.2.9 The performance of DDT by ADS shall comply with road traffic regulations.

5.1.2.10 ADS shall detect and respond to vehicles having priority right of way (e.g., police cars, fire engines, ambulances and engineering rescue vehicles performing emergency tasks). When obstructing the passage of vehicles having priority right of way, the following requirements shall at least be met.

a) for a level 3 ADS feature, performing yielding control or performing ADS fallback response;

b) for a level 4 ADS feature, performing yielding control.

5.1.2.11 ADS shall detect and respond to on-site instructions of traffic police, and shall at least meet the following requirements.

a) for a level 3 ADS feature, passing according to the on-site instructions of traffic police or performing ADS fallback response;

b) for a level 4 ADS feature, passing according to the on-site instructions of traffic police.

5.1.3 DDT performance in critical scenarios

5.1.3.1 Where reasonably practicable, ADS performing DDT in critical scenarios shall comply with the requirements of 5.1.2 to minimize the overall safety risk.

5.1.3.2 When the ADS feature is in the active state, if a collision is unavoidable, except when the collision causes ADS to lose control of the vehicle motion, ADS shall reduce the injury or damage caused by the accident.

Note: Whether a collision is avoidable is based on the level of a qualified and attentive driver who is currently performing the DDT.

5.1.3.3 When the ADS feature is in the active state and a collision is detected to have occurred, except when the collision causes ADS to lose control of vehicle braking, ADS shall bring the vehicle to a stop.

5.1.4 DDT performance in failure scenarios

5.1.4.1 Where reasonably practicable, ADS performing DDT in failure scenarios shall comply with the requirements of 5.1.2 to minimize the overall safety risk.

5.1.4.2 ADS shall detect faults and functional abnormalities that affect its capability to perform DDT within the ODD.

5.1.4.3 When a fault occurs, ADS shall meet either of the following requirements.

a) if the fault makes ADS unable to safely perform DDT, perform ADS fallback response and prohibit activation of other affected ADS features; if MRM is performed, the requirements of 5.1.6 shall be met.

b) if ADS can still safely perform DDT, adjust its capability to perform DDT according to the severity of the fault.

5.1.5 DDT performance in scenarios that do not comply with the ODC

5.1.5.1 ADS shall be capable of safely responding to situations that do not comply with the ODC. For foreseeable situations that do not comply with the ODC, ADS shall also be capable of anticipating them.

5.1.5.2 When the ADS feature is not in the active state, if there is a situation that does not comply with the ODC, the corresponding ADS feature shall not be activated.

5.1.5.3 When the ADS feature is in the active state, if there is a situation that does not comply with the ODC, ADS shall perform ADS fallback response. If MRM is performed, the requirements of 5.1.6 shall be met.

5.1.5.4 During the performance of ADS fallback response, where reasonably practicable, the following requirements shall be met.

a) in nominal scenarios, the requirements of 5.1.2 shall continue to apply;

b) in critical scenarios, the requirements of 5.1.3 shall continue to apply;

c) in failure scenarios, the requirements of 5.1.4 shall continue to apply.

5.1.6 Minimal risk maneuver

5.1.6.1 For a level 3 ADS feature, if the fallback user has not completed the takeover or a situation described in the safety case that requires direct performance of MRM occurs, ADS shall perform MRM to bring the vehicle to the MRC, and shall meet the following requirements.

a) have the capability to perform lane change;

b) minimize safety risks to users and ORUs;

c) aim to move the vehicle to a safe stop at the side of the road where it does not obstruct traffic; when a severe vehicle failure or severe ADS failure makes it impossible to safely move the vehicle to the side of the road, at least bring the vehicle to a safe stop in the current lane; during the performance of MRM and after bringing the vehicle to the MRC, ADS shall not prohibit intervention and deactivation by the fallback user;

d) reasonably use hazard warning signals during the performance of MRM by ADS and after bringing the vehicle to the MRC;

e) after ADS brings the vehicle to the MRC, ADS can be activated only after the vehicle's power system is restarted (excluding automatic engine start-stop).

5.1.6.2 For a level 4 ADS feature, if a situation described in the safety case that requires performance of MRM occurs, ADS shall perform MRM to bring the vehicle to the MRC, and shall meet the following requirements.

a) have the capability to perform lane change;

b) minimize safety risks to users and ORUs;

c) aim to move the vehicle to a safe area where it does not obstruct traffic and bring the vehicle to a stop, and at least move the vehicle to the side of the road where it does not obstruct traffic and bring the vehicle to a safe stop;

d) when a severe vehicle failure makes it impossible to safely move the vehicle to the side of the road, at least bring the vehicle to a safe stop in the current lane;

e) reasonably use hazard warning signals during the performance of MRM by ADS and after bringing the vehicle to the MRC.

5.2 Human-machine interaction

5.2.1 General requirements

5.2.1.1 ADS shall ensure that ADS features are safely activated and deactivated.

5.2.1.2 After each start-up of the vehicle power system (excluding automatic engine start-stop), ADS shall not be automatically activated.

5.2.1.3 Safety-related indications of ADS shall meet the following requirements.

a) be noticeable by the intended occupants in all ADS operating states;

b) be easy to understand and unambiguous;

c) adopt multiple indication modes where necessary (e.g., visual, audible and tactile).

5.2.1.4 When performing an ADS fallback response, ADS shall continuously provide occupants with an indication that an ADS fallback response is being performed.

5.2.1.5 Where ADS affects door control, ADS shall ensure that the operation of doors by occupants takes priority over ADS.

5.2.1.6 When an ADS feature is in the active state and a collision is detected to have occurred, ADS shall provide an indication to occupants; the indication shall continue at least until ADS deactivation is completed or confirmed by a user.

5.2.1.7 Where an automated parking feature and an ADS feature (other than an automated parking feature) share human-machine interaction means, the relevant human-machine interaction means and their rationality shall be described in the safety case.

Note: Shared human-machine interaction means may include dedicated control means, system status indications, etc.

......
This preview omits tables, figures, formulas and parts of the technical clauses. The complete document — 113 pages — is available in the English PDF.

Referenced standards

Editions of GB 44721

EditionTitleRevisionStatus
GB 44721-2026Intelligent and connected vehicles — Safety requirements for automated driving systemscurrent editionCurrent
GB/T 44721-2024Intelligent and connected vehicles — Safety requirements for automated driving systemsprevious editionIn force until 1 July 2027

This page sells the current edition, GB 44721-2026. Earlier editions are listed for reference only.

How to Download GB 44721-2026

  1. 1

    Add to cart

    Click "Download PDF" on this page and choose "Buy this standard". You can add more standards before checkout.

  2. 2

    Checkout

    Enter your email and billing details. Payment is processed securely by Stripe (cards or bank transfer). Prefer bank details? Request a quotation (min. order $300).

  3. 3

    Instant delivery (0–9 sec)

    Delivery is automatic: within seconds of payment you'll receive an email with a secure download link. The link stays valid for 72 hours.

  4. 4

    Invoice included

    A tax invoice is attached to the confirmation email. Need a custom invoice? Contact us.

Related Standards

English PDF
113 pages
Instant delivery (0–9 sec)
Invoice included
View Cart

Secure payment via Stripe

Payments accepted

VisaMastercardAmerican ExpressApple PayGoogle PayStripe

GB 44721-2026

$830.00