GB 44496-2024 governs the vehicle software upgrade management system (SUMS). It's completed alongside GB 44495 (vehicle information security national standard) during vehicle type inspection — not submitted as two separate independent proof documents. Both standards officially take effect on January 1, 2026. From that date, the MIIT Equipment Industry Development Center requires all newly developed vehicle models' public announcement applications to meet both standards' requirements. July is just a concentrated deadline for many automakers to wrap up — it's not the statutory effective date. This article walks through every step from initial project decision-making to post-certification annual compliance, with specific operations and pitfalls broken out in detail.
GB 44496 only covers whole vehicles of categories M, N, and O. There is no independent certification channel for components. T-Boxes, MCUs, and domain controllers cannot independently obtain type approval under GB 44496 — the approval ultimately attaches to the vehicle's CCC certificate. However, component manufacturers must still build their internal software version management systems and provide complete version traceability documentation to the OEM. You can't just say "components don't get certified, so we don't need to worry about it."
Step one: Determine whether your vehicle needs it. Vehicles of categories M/N/O with OTA (Over-The-Air) upgrade capability must go through the full process. Vehicle models that only do local USB or OBD offline flashing and have absolutely no OTA functionality are exempt from the full SUMS plus VTA process. Note one boundary condition though: if the automaker's backend can remotely push instructions to trigger OBD upgrades, it's still classified as OTA and cannot be exempted. L-category motorcycles and in-plant special vehicles are exempt.
Step two: Determine whether it's a brand-new platform or an existing model refresh. A brand-new platform starts the SUMS system from scratch, taking 5 to 8 months. An existing model requires hardware modifications plus system documentation backfill, taking 3 to 5 months. If rectification cycles pile up, the timeline stretches significantly — dragging past a year is not uncommon. The figures above are industry average experience values.
Step three: Determine GB 44495 companion progress. The two standards are conducted simultaneously during the type testing phase for the same vehicle, and the results ultimately appear in the same vehicle CCC report — not as two separate independent proof documents.
II. Gap Analysis and System Assessment
This isn't a casual walk-through where you say "looks fine." You need to check against GB 44496 clause by clause and produce a prioritized issue list.
1.Document system check. Type approval impact assessment documents and supplier management procedures are the most commonly missed items. Many manufacturers simply don't have these documents — they push OTA upgrades on a whim with no risk assessment records.
2.Process check. The national standard text states management system requirements. The industry has distilled management elements from software unique identification through upgrade notification to vehicle users. Each element must have written procedures and operational records. No records means you haven't done it.
3.Technical implementation check. Does the upgrade package signature verification mechanism exist? Can rollback cover power-loss and network-loss extreme scenarios? Is the HMI notification interface content complete? Do externally sourced ECUs and middleware suppliers provide supporting materials?
Gap analysis takes 3 to 6 weeks for a new platform, 1 to 3 weeks for an existing model refresh. The output is a gap analysis report — this report is needed later for lab booking and system audit.
III. SUMS System Document Preparation
The SUMS system is the foundation of certification. If the documents don't pass, you can't even get through the door of physical vehicle testing.
Three core deliverables:
First, the software upgrade safety management policy, signed and issued by top management.
Second, the organizational structure and responsibility allocation table — who approves upgrade packages, who assesses type approval impact, who handles emergency incidents. You can't write "relevant department" — it must be assigned to specific positions.
Third, the procedure documents for each management element as distilled by the industry. Each element must have defined inputs/outputs, execution steps, and exception handling plans.
Four security assurance items must be written in: Upgrade package anti-tampering measures, full-process security protection, verification and confirmation procedures, and emergency incident response plans. These four items are audit focus areas — writing them too vaguely will get them sent back.
After documents are written, do an internal trial run: select one or two real upgrades and run the full process, leaving traces as subsequent audit evidence. New platform document preparation takes 4 to 10 weeks; existing model refresh takes 2 to 4 weeks for changed portions.
IV. System Audit and Vehicle Testing
Pre-testing can be done early — submit the gap analysis report, system document draft, and trial run records to reserve a test slot and run preliminary checks in parallel. But formal VTA type testing can only produce a formal VTA report for CCC application after the formal SUMS system audit report is submitted. Draft documents can only be used for preliminary checks, not formal testing. Understand this distinction — don't assume pre-test reports can be submitted directly.
SUMS audit starts with document review (1 to 2 weeks), followed by on-site audit (2 to 3 days) after passing. The audit team checks records, conducts interviews, observes operations, and randomly samples complete record chains from past upgrade activities. Missing any link counts as non-conformity. Minor non-conformities require corrective evidence within 30 to 45 days to close. Major non-conformities pause the process and require a second on-site audit.
VTA vehicle testing covers: upgrade package authenticity and integrity verification, software identification code OBD reading, user notification and confirmation mechanism, power assurance, driving-during upgrade safety blocking, upgrade interruption/failure handling and rollback, upgrade result notification, and more. Note: door anti-lockout falls under GB 48001-2026 "Technical Requirements for Vehicle Door Handle Safety," which takes effect January 1, 2027 — it is NOT a GB 44496 VTA test item. Don't waste money on unnecessary rectification. New platform takes 4 to 8 weeks; existing model refresh with change testing takes 2 to 4 weeks.
V. CCC Certificate Integration Filing
GB 44496's final compliance credential is embedded in the vehicle CCC certificate — it's not a separate national standard certificate. Submit: SUMS system conformity audit report original, VTA test report original, vehicle model technical parameter description, software upgrade-related sections in the manual, and production conformity control plan.
After the certification body reviews, it issues a CCC certificate with GB 44496 conformity records. Document review takes 3 to 8 weeks; filing and public notice take 2 to 4 weeks.
The vehicle CCC certificate has no fixed expiration date — it's maintained through annual supervisory audits. Change triggers aren't limited to hardware swaps and regulatory updates. OTA firmware changes, TCU communication module changes, and SUMS upgrade logic modifications also count as vehicle model changes, requiring a change report submitted to CQC to determine whether it's a document review or partial VTA retest.
VI. Post-Certification Annual Continuous Compliance
Annual factory inspection is conducted every year, with a bundled vehicle review. The focus is on whether the SUMS system is running normally, whether actual upgrades follow the rules, and whether production vehicle configurations and software versions are consistent with those at certification time.
Software upgrade records must be retained for no less than the vehicle's design service life. CCC implementation rules further require retention for 10 years after the vehicle's full lifecycle ends. A model going out of production doesn't mean the vehicle design life has ended — there are still many years of in-use vehicles after production stops. Don't calculate from the production stop date. Not just vehicle-level records — T-Box, MCU, and other component firmware versions and change ledgers must also be retained simultaneously. Changing major component suppliers may trigger change declaration and supplementary testing — you can't just swap without reporting.
If annual supervision finds serious problems, the certificate is suspended or even revoked. The MIIT Equipment Industry Development Center genuinely has no expedited channel. CQC has a special review channel for key projects but doesn't publicly promote expedited services. Lock in testing slots early — the further along, the tighter the scheduling.
For GB 44496 certification steps and related inquiries, contact blueasia Technology Testing & Certification consultant at 13534225140 (Benson).
相关新闻
