Executive Summary
China published GB 47955-2026, Intelligent and Connected Vehicle – Safety Requirements of Combined Driver Assistance System, on 27 June 2026. The mandatory national standard is scheduled to take effect on 1 January 2027. It applies to combined driver-assistance systems and establishes safety requirements across system function, data recording, manufacturer controls, human-machine interaction, user information and testing.
The standard distinguishes three product forms: basic single-lane assistance, basic multi-lane assistance and navigation-assisted driving. It should not be summarized as a rule for SAE Levels 2, 2+ and 3. The official MIIT description emphasizes that the driver must continue to observe traffic and control the vehicle; the standard is directed at assistance, not a general authorization for conditional automated driving. Foreign suppliers should map each component and software function to the vehicle manufacturer’s compliance evidence before the 2027 implementation date.
Why the Standard Matters
MIIT reported that in 2026 the penetration rate of combined driving-assistance functions in new passenger vehicles had reached 70%, with navigation-assisted functions above 30%. The scale means the standard affects not only vehicle manufacturers but also suppliers of cameras, radar, computing platforms, controllers, driver-monitoring systems, maps, data recorders, human-machine interfaces and software updates.
A component may meet its own specification and still fail at vehicle level if system boundaries, warnings, degradation behavior or data interfaces do not support the complete safety case. Foreign suppliers therefore need an evidence plan that connects requirements, design, validation, change control and field performance. Waiting for a customer to send a final test request can leave insufficient time for redesign or local testing.
Regulatory Background and Scope
GB 47955-2026 was issued by the State Administration for Market Regulation and the Standardization Administration, with MIIT as the responsible and organizing department. The official standards platform lists it as a mandatory national standard with an implementation date of 1 January 2027. MIIT began the development process in 2024 and published the approval draft and explanatory materials for comment in April 2026.
The standard builds on recommended standards for single-lane and multi-lane control and sits alongside requirements for information security, software upgrading and automated-driving data recording. MIIT also compared the standard with UN Regulation No. 171 on Driver Control Assistance Systems, noting greater detail in areas such as operating boundaries, functions, driver-state monitoring, user information and test conditions for China’s road environment.
Key Requirements for Foreign Suppliers
1. Product Classification and System Boundary
Confirm whether the supplied function supports basic single-lane, basic multi-lane or navigation-assisted driving. Document what the system can and cannot do, its design operating conditions, the driver role, dependencies and the conditions that trigger degradation or exit. Marketing descriptions must not imply capabilities beyond the approved boundary.
2. Functional and Failure Behavior
The safety case should address motion control, object and lane detection, driver intervention, fault response and safe degradation. A supplier needs traceability from the vehicle-level hazard analysis to component requirements, diagnostics and verification results. Interfaces between perception, planning, control and driver monitoring require particular attention.
3. Driver Monitoring and Human-Machine Interaction
The standard maintains the driver’s responsibility to observe traffic and control the vehicle. Warnings, status displays, takeover expectations and misuse prevention must be understandable and consistent. A strong technical function can still create risk if the driver cannot recognize its state or operating boundary.
4. Data Recording and Evidence
Data records support type approval, incident analysis and regulatory supervision. Suppliers should agree with the vehicle manufacturer which events, signals, timestamps, versions and fault states must be recorded, how data integrity is protected and how records can be retrieved. Data-recording work should also be aligned with applicable privacy, cybersecurity and automotive-data rules.
5. Software and Change Control
Over-the-air updates, calibration changes and model revisions can alter safety performance. Configuration management should connect each release to requirements, validation evidence, cybersecurity review and customer approval. A supplier must be able to identify which vehicles and software versions are affected by a defect.
Step-by-Step Compliance Roadmap
- Obtain the official standard and customer interpretation. Work from GB 47955-2026, not a news summary.
- Classify the product form. Map the function to the three categories used by the standard.
- Create a clause matrix. Assign every applicable requirement to vehicle manufacturer, Tier 1 or sub-supplier ownership.
- Update the safety analysis. Review hazards, operating boundaries, driver interaction, fault handling and misuse.
- Identify evidence gaps. Compare current tests, simulations, track results and documentation with the mandatory requirements.
- Plan China-specific validation. Include field, road, document and system-level tests required for the target vehicle.
- Align data and software controls. Confirm recording, version management, cybersecurity and update evidence.
- Control supplier changes. Require notice and revalidation for hardware, firmware, model or calibration changes.
- Support vehicle approval and post-market monitoring. Prepare technical files, issue response and recall cooperation before launch.
Options and Readiness Comparison
| Supplier Position | Main Responsibility | Evidence Priority |
|---|---|---|
| Sensor or component supplier | Performance limits, diagnostics, failure modes and interface specifications | Environmental tests, fault injection, tolerances and traceability |
| Computing or controller supplier | Functional safety, timing, cybersecurity and configuration control | Architecture, verification, software version and security records |
| ADAS software supplier | Operating boundary, perception and control behavior, update effects | Scenario coverage, model validation, regression tests and release governance |
| Tier 1 system integrator | End-to-end function, HMI, degradation and vehicle interfaces | System safety case, integrated testing and customer compliance matrix |
Costs and Timeline
Cost depends on the gap between the current global design and the China vehicle program. Typical work includes standards analysis, engineering changes, additional sensors or diagnostics, HMI localization, data-recording development, scenario testing, track testing, documentation and customer support. A mature platform may need mainly evidence alignment; a product whose operating boundary or warnings conflict with the standard may need redesign.
The transition period ends when the standard takes effect on 1 January 2027. Suppliers should work backward from the vehicle manufacturer’s approval and production schedule, not from the national effective date. Design freeze, prototype build, test capacity, software release and vehicle integration create earlier internal deadlines. Change requests after vehicle validation can have disproportionate cost.
Supplier Evidence Package
A complete delivery should contain more than test reports. The vehicle manufacturer needs a requirements-compliance matrix, system and component specifications, interface-control documents, hazard and failure analyses, software and calibration identifiers, verification plans, test results, known limitations and change history. Each record should identify the product version and approval status so that evidence from an earlier release is not applied to a later configuration without review.
Responsibility boundaries should be written into the development agreement. The supplier should state which vehicle-level assumptions its evidence depends on, including sensor installation, power supply, network timing, driver-monitoring inputs, braking authority and HMI behavior. The customer should confirm integration conditions and report deviations. Joint issue management is particularly important where several suppliers contribute to perception, planning, control and warning functions.
Post-market support also belongs in the compliance plan. Contracts should define incident notification, log preservation, root-cause analysis, software correction, field monitoring and recall cooperation. Engineering teams need a secure method to reproduce the released configuration and determine whether a reported event falls within the approved operating boundary. These capabilities reduce both regulatory response time and commercial disagreement after launch.
Risks and Challenges
- Mapping the standard to SAE labels rather than the three official product forms.
- Treating component validation as sufficient for vehicle-level safety.
- Using marketing terms that overstate automation and confuse the driver role.
- Leaving data-recording and HMI requirements until late integration.
- Failing to revalidate software, model or calibration changes.
- Assuming a global UN R171 evidence package automatically covers all China-specific requirements.
Common Mistakes Foreign Companies Make
The most common mistake is waiting for the Chinese vehicle manufacturer to own every compliance task. The manufacturer holds the vehicle-level responsibility, but suppliers control critical design assumptions and evidence. Another mistake is relying on a draft or media interpretation after the final mandatory standard has been published. Teams also underestimate the lead time needed to reserve local testing, translate technical records and resolve cross-company interface gaps.
Best Practices and Recommendations
Appoint a China standard owner and maintain a bilingual clause matrix. Connect each clause to a responsible engineer, evidence file, customer requirement and open gap. Hold joint reviews with the vehicle manufacturer for operating boundaries, driver monitoring, HMI, data recording and software updates. Freeze the compliance baseline before final vehicle validation and require formal impact assessment for every later change.
FAQ
When does GB 47955-2026 take effect?
The official national standards platform lists 1 January 2027 as the implementation date.
Does the standard cover Level 3 automated driving?
The official description addresses combined driver-assistance systems in which the driver continues to observe traffic and control the vehicle. It uses three assistance-product forms rather than SAE Level 2, 2+ and 3 labels.
What are the three product forms?
MIIT identifies basic single-lane assistance, basic multi-lane assistance and navigation-assisted driving.
Can a supplier rely only on UN R171 compliance?
No automatic equivalence should be assumed. MIIT states that GB 47955-2026 contains additional detail tailored to China’s road environment and regulatory needs.
What should a supplier do first?
Obtain the final standard, classify the function, build a clause-ownership matrix and compare the existing evidence package with the Chinese vehicle program’s approval schedule.
Conclusion
GB 47955-2026 turns combined driving-assistance safety into a mandatory national baseline. Foreign suppliers should treat it as a vehicle-system program, not a document check. Early ownership of interfaces, evidence, change control and customer coordination is the best protection against late redesign and launch delay.
