What it is
GB 44496-2024 is China’s mandatory national standard on general technical requirements for vehicle software updates. It treats the upgrade as a regulated vehicle function: the manufacturer controls which software is installed, informs the user about the change, keeps the vehicle safe while the change is applied, and accepts a package only after its protection checks succeed.
Who it applies to
The duty rests with the manufacturer that offers an upgrade-capable vehicle on the Chinese market, and with an importer who takes that role. Suppliers of control units, domain controllers, update agents, and the release backend contribute, because the requirement applies to the vehicle as a whole. Workshop organizations that install software are covered where an offline or service installation is a software upgrade. Vehicle categories, exclusions, and the timing for a given approval are defined in the official scope and implementation requirements. Check that text before calling a model out of scope.
What it covers
Explanations of GB 44496 group the technical requirements around the outcomes below. Treat the table as a map and confirm each row in the current text.
| Topic | What you need to show |
|---|---|
| Version identity | Upgraded systems are identifiable, and the software present after the attempt is traceable |
| User information | The user is told what will change and what the upgrade requires before it starts |
| Preconditions | The upgrade starts only in a vehicle state that is suitable for that change |
| Safe failure | A failed or interrupted upgrade is detected, and the vehicle remains in a safe condition |
| Package protection | The package is protected against tampering and accepted only from an authorized source |
| Result and record | Success or failure is reported, and the attempt can be reconstructed later |
Online delivery outside a workshop, including over-the-air update, is a central case. An offline or service upgrade is still a change to vehicle software and needs a defined, protected procedure. Where the change can alter behavior covered by an existing approval, conformity assessment and any required filing continue to apply.
How it fits with other documents
GB 44495, China’s mandatory vehicle cybersecurity standard, is the companion. It protects the vehicle as a system. GB 44496 sets upgrade behavior: user information, preconditions, package acceptance, and safe failure. Each standard needs its own evidence.
UN Regulation No. 156 covers software updates and a software update management system for type approval in many other markets. A UN R156 dossier still needs its own check against GB 44496: terminology, evidence, and the split between online and service updates are different.
ISO 24089 is voluntary guidance for organizing software-update engineering. Chinese market access is judged against GB 44496. ISO 14229 covers diagnostic transfer and version readout, network specifications cover the buses, and AUTOSAR platforms are a common way to build bootloaders and update clients. Compliance is judged on the vehicle’s behavior.
In practice
Anchor the work on the path a driver or a workshop can actually run. For each path, record who may start it, which conditions block it, what the user is told, and which software identity is stored on success and on failure. Review loss of power and a half-written image with safety, and agree the safe condition that follows. Cybersecurity defines authentication, authorized sources, and key handling. Software and basic software deliver the agent on each controller and the version it reports.
File the release evidence with the package: targets, user text, preconditions, identity, and a failed-update test. Bring safety and homologation in before offering a change to braking, steering, occupant protection, or any other approved system. Plan the administrative filing for an online upgrade together with conformance to this technical standard. Where a clause is unclear, check the current edition and the implementation requirements.