Domestic and international in‑vehicle software compliance are independent – they cannot substitute for each other.
·GB 44495: vehicle cybersecurity – aligned with UN R155.
·GB 44496: vehicle OTA software upgrades – aligned with UN R156.
The two frameworks are broadly similar – but implementation and test details differ. Export models must meet both – completing only one leaves compliance gaps – blocking vehicle type approval.
2. OTA Regulation Core: SUMS
2.1 Seven system elements
OEMs must establish a full Software Update Management System (SUMS):
·Software identification.
·Change control.
·Configuration management.
·Risk assessment.
·Release approval.
·Deployment monitoring.
·Fault rollback.
This is an operational management system – not something you can satisfy with a few test reports. Audits include on‑site checks – process records, sign‑offs, and drill logs must be fully traceable.
2.2 Responsibility and audit requirements
The OEM is the primary responsible party – component suppliers provide supporting technical documentation. SUMS is a hard market‑access threshold – non‑compliance blocks type approval.
On‑site audits do not only review paper documents – auditors check actual execution records and interview staff. Missing records = non‑compliance.
3. China‑Specific Differences
3.1 Whole‑vehicle verification items
GB 44496 requires 14 vehicle‑level tests – 8 for local upgrades, 6 for OTA – in addition to system audit.
UN R156 does not have detailed vehicle‑test rules – this is the largest workload difference in China projects – book lab slots early.
3.2 Three China‑only mandatory clauses
·During OTA upgrades, doors must not auto‑lock – interior unlock must remain available.
·Upgrade notifications must be prioritised on the head‑unit display – mobile‑app/SMS are supplementary only.
·OTA installation is prohibited while the vehicle is in motion.
These are one‑vote veto items in China reviews – overseas regulations do not have equivalent hard constraints – project teams must focus on these.
4. Cybersecurity and OTA – Complementary
OTA remote upgrades are high‑risk attack surfaces – package tampering, communication hijacking, and malicious rollback are real‑world threats.
Under GB 44495, the entire chain (cloud, communication link, vehicle‑side flashing) must be protected – with authentication, data‑integrity verification, and anti‑rollback mechanisms.
The two standards are complementary:
·One: hardware/software security capability.
·The other: end‑to‑end process management.
Missing either creates compliance gaps.
5. Core Technical Compliance – Alignment
5.1 Pre‑upgrade assessment
Both domestic and international regulations require risk assessment before pushing upgrades – covering impact scope, security risks, rollback feasibility, and vehicle‑operation constraints. If assessment fails – the upgrade cannot be pushed. Assessment materials must be archived for audit.
5.2 Transmission and interruption protection
Upgrade packages must include digital signatures – flashing only after vehicle verification. Communication links must be encrypted.
If the upgrade is interrupted – the vehicle must remain drivable – no system lock‑up. Partition backup is the mainstream implementation.
6. Record Retention and Documentation
Both systems require upgrade records to be retained for 10 years after the model is discontinued – archived data must be complete and verifiable. Migration without re‑verification creates audit findings.
Documents submitted for domestic approval (manuals, process files) must be in Simplified Chinese. We recommend producing bilingual documentation during R&D – avoiding last‑minute translation bottlenecks.
7. Practical Implementation Recommendations
At project definition, map domestic vs. international regulatory differences – identify reusable test results vs. additional items – don't blindly run both standards in parallel – reducing later rework.
Firmware versions, upgrade branches, and configuration lists must be fully traceable – use toolchains – don't rely on manual spreadsheets – mass production will cause version chaos.
Software management, security design, and version control should be built into the R&D workflow – don't wait until announcement submission.
BlueAsia can perform domestic‑international gap analysis and provide OTA compliance technical support.
For OTA compliance, contact BlueAsia at 13534225140 (King) or email king.guo@cblueasia.com.
相关新闻
