Standard No.:	GB 44721-2026
English Name:	Intelligent and connected vehicle—Safety requirements for automated driving system
Chinese Name:	智能网联汽车 自动驾驶系统安全要求
Chinese Classification:	T40    Automobiles in general
Professional Classification:	GB    National Standard
ICS Classification:	43.02 43.02    Road vehicles in general 43.02
Source Content Issued by:	SAMR, SAC
Issued on:	2026-7-30
Implemented on:	2027-7-1
Status:	to be valid
Superseding:	GB/T 44721-2024 Intelligent and connected vehicle—General technical requirements for automated driving system
Target Language:	English
File Format:	PDF
Word Count:	31000 words
Translation Price(USD):	930.0
Delivery:	via email in 1~5 business day

GB 44721-2026 Intelligent and connected vehicle—Safety requirements for automated driving system English, Anglais, Englisch, Inglés, えいご This is a draft translation for reference among interesting stakeholders. The finalized translation (passing through draft translation, self-check, revision and verification) will be delivered upon being ordered. ICS CCS National Standard of the People's Republic of China ‌GB 44721-2026 Intelligent and connected vehicle - Safety requirements for automated driving system 智能网联汽车 自动驾驶系统安全要求 Issue date: 2026-08-27 Implementation date: 2027-09-01 Issued by the General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China the Standardization Administration of the People's Republic of China Contents Foreword 1 Scope 2 Normative References 3 Terms and Definitions 4 Abbreviated Terms 5 ADS Technical Requirements 6 Assurance Requirements 7 Inspection of Assurance Requirements 8 Safety File Inspection 9 Confirmation Test 10 Determination of the Same Type 11 Implementation of the Standard Annex A (Normative) Technical Requirements for Takeover Capability Monitoring Annex B (Normative) Specific Technical Requirements for Level 3 ADS Functions Applied to Highways and/or Urban Expressways Annex C (Normative) Specific Technical Requirements for Level 4 ADS Functions Annex D (Normative) Safety File Bibliography Safety Requirements for Automated Driving Systems of Intelligent and Connected Vehicles 1 Scope This document specifies the technical requirements, assurance requirements and criteria for determining the same type for automated driving systems of intelligent and connected vehicles, and describes the corresponding test methods including assurance requirement inspection, safety file inspection and confirmation test. This document applies to Category M and Category N vehicles equipped with Level 3 and/or Level 4 driving automation systems. This document is not applicable to automatic parking systems. 2 Normative References The following documents contain provisions which, through normative reference in this text, constitute indispensable provisions of this document. For dated references, only the edition cited applies. For undated references, the latest edition (including any amendments) applies. GB/T 41798 Intelligent and connected vehicles — Field test methods and requirements for automated driving functions GB 44497 Intelligent and connected vehicles — Automated driving data recording system GB/T 44719 Intelligent and connected vehicles — Road test methods and requirements for automated driving functions GB/T 45312 Intelligent and connected vehicles — Operational design conditions for automated driving systems GB/T 47025 Intelligent and connected vehicles — Simulation test methods and requirements for automated driving functions 3 Terms and Definitions The following terms and definitions apply to this document. 3.1 automated driving system Hardware and software of a vehicle that together form a system capable of continuously performing the entire dynamic driving task. 3.2 dynamic driving task (DDT) Behaviours such as perception, decision-making and executive control required for vehicle driving. Note: The dynamic driving task generally includes control of vehicle motion, lighting and signalling devices, etc. 3.3 ADS feature A function of an ADS that performs the entire DDT under specific operational design conditions. 3.4 Level 3 ADS feature An L3 ADS feature ADS feature subject to operational design domain limitations and requiring a fallback user. Note: It corresponds to Level 3 driving automation specified in GB/T 40429-2021. 3.5 Level 4 ADS feature An L4 ADS feature ADS feature subject to operational design domain limitations and not requiring a fallback user. Note: It corresponds to Level 4 driving automation specified in GB/T 40429-2021. 3.6 active state A state in which the ADS performs the DDT to control the vehicle. 3.7 available state A state where the operational design conditions for the automated driving function are met but the ADS has not yet taken control. 3.8 activation The action of transitioning the automated driving function from the available state to the active state. 3.9 deactivation The action of transitioning the automated driving function from the active state to a state where it no longer exercises control. 3.10 operational design domain (ODD) External environmental conditions defined at the design stage of a driving automation system for the function to operate. Note: Typical external environmental conditions include road, traffic, weather, illumination, etc. 3.11 operational design condition (ODC) A general term for all conditions defined at the design stage of a driving automation system for the function to operate, including operational design domain, vehicle state, occupant state and other necessary conditions. 3.12 planned takeover event An event that is known in advance by the ADS and requires issuance of a request to intervene. 3.13 user A person using a vehicle equipped with an ADS. 3.14 occupant A user inside a vehicle equipped with an ADS. 3.15 fallback user An occupant in the vehicle designated to perform takeover when the automated driving function is in the active state. 3.16 passenger An occupant other than the driver or fallback user. 3.17 intervention An action by which a user actively influences the ADS performance of the DDT through a defined and effective means. 3.18 ADS fallback response ADS issuance of a request to intervene and/or execution of a minimal risk manoeuvre. 3.19 request to intervene Prompt issued by the ADS requesting the fallback user to perform takeover. 3.20