Contents
RegulationSAC (China)

GB 44496-2024

General technical requirements for software update of vehicles

GB 44496-2024 is China's mandatory national standard for how a vehicle software update must behave so the change stays controlled, explained to the user, and safe.

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.

What it means for your discipline

  • Software update & OTACore

    You own the vehicle-level update function and the evidence that each released package meets this standard. Day to day you decide who may start an update, what the user is told, which preconditions apply, and how a failed attempt is recorded.

  • Functional safetyCore

    A software update can change safety-related behavior or stop while a controller is only partly programmed. You assess the safe condition during the attempt and after a loss of power, and you join the release when the package touches a safety-related system.

  • CybersecurityCore

    The update path is a route for new code onto the vehicle. You define authenticity, integrity, and authorization for packages and keys, and you review tampering, unauthorized sources, and exposure of the update credentials.

  • HPC & application softwarePartial

    You own version identity, compatibility, and the behavior the user is promised once the update completes. You need a clear rule for which of your modules are field-updatable and what your feature does if the write does not finish.

  • E/E architecturePartial

    You place the update master, choose which controllers are updateable, and coordinate a change across domains. The architecture has to make preconditions, a safe interrupted update, and a readable software identity possible on every path the vehicle offers.

  • Base softwarePartial

    Basic software provides the bootloader, memory access, and the stored version data the update agent uses. Your task is an image that can be checked, written, and either completed or returned to a safe image after an interruption.

  • Networks & communicationPartial

    In-vehicle networks carry the image from the update master to each target, and the external connection carries an online package. The transfer has to let the update policy finish or abort cleanly so a controller is not left undefined.

  • Diagnostics & lifecyclePartial

    Workshop updates and inspections usually depend on diagnostic reprogramming and version readout. You align tester sequences and identifiers with the same software identity and failure behavior used by the online path.

  • Hardware & siliconPartial

    Each updated controller needs non-volatile storage, a trustworthy boot path, and a power arrangement that matches the recovery strategy. You confirm the hardware can hold the images the update concept relies on and can tolerate an interruption in that way.