GB 44496-2024 English PDF

Delivery: 2 working-hours manually (Sales@ChineseStandard.net)
Need delivered in 3-second? USA-Site: GB 44496-2024
Get Quotation: Click GB 44496-2024 (Self-service in 1-minute)
Historical versions (Master-website): GB 44496-2024
Preview True-PDF (Reload/Scroll-down if blank)

GB 44496-2024: General technical requirements for software update of vehicles
GB 44496-2024
GB
NATIONAL STANDARD OF THE
PEOPLE’S REPUBLIC OF CHINA
ICS 43.020
CCS T 40
General Technical Requirements for Software Update of
Vehicles
ISSUED ON: AUGUST 23, 2024
IMPLEMENTED ON: JANUARY 1, 2026
Issued by: State Administration for Market Regulation;
Standardization Administration of the People’s Republic of China.
Table of Contents
Foreword ... 3
1 Scope ... 4
2 Normative References ... 4
3 Terms and Definitions ... 4
4 Requirements for Software Update Management System ... 6
5 Vehicle Requirements ... 9
6 Test Methods ... 11
7 Same Type Determination ... 13
8 Motor Vehicle Product Instruction Manual ... 14
9 Implementation of the Standard ... 15
General Technical Requirements for Software Update of
Vehicles
1 Scope
This document specifies the management system requirements and vehicle requirements for
software update of vehicles, as well as same type determination and motor vehicle product
instructions, and describes the corresponding test methods.
This document is applicable to Category-M, Category-N and Category-O vehicles with
software update functions.
2 Normative References
The contents of the following documents constitute indispensable clauses of this document
through the normative references in the text. In terms of references with a specified date, only
versions with a specified date are applicable to this document. In terms of references without a
specified date, the latest version (including all the modifications) is applicable to this document.
GB 44495-2024 Technical Requirements for Vehicle Cybersecurity
3 Terms and Definitions
The terms and definitions defined in GB 44495-2024, and the following are applicable to this
document.
3.1 software
The part of an electronic control system that consists of digital data and commands.
3.2 software update
The process of updating a certain version of software to a new version through an upgrade
package (including changing the configuration parameters of the software).
NOTE 1: “software update” is also called “software upgrade”.
NOTE 2: “software update” includes online update and offline update.
3.3 over-the-air update; OTA update
Software update that wirelessly transmits the update package to the vehicle rather than using
cables or other local connections.
NOTE 1: “over-the-air update” is also called “remote update”.
NOTE 2: “local connection” generally refers to the physical connection mode through the on-board
diagnostic (OBD) interface and universal serial bus (USB) interface, etc.
3.4 software identification number; SWIN
A unique identifier defined by the vehicle manufacturer and used to represent software
information of a vehicle system related to type approval.
NOTE: the software identification number is not the same as the software version number.
3.5 software update management system; SUMS
A systematic method developed to standardize the processes and procedures for completing
software updates in relevant organizations.
3.6 update package
A software package used for software updates.
3.7 execution
The process of installing and activating downloaded update packages.
3.8 safe state
A mode of vehicle operation that is free of unreasonable risks.
3.9 integrity validation data
Data value that is used to verify data integrity.
EXAMPLE: hash values, etc.
3.10 vehicle system
A set of components and / or subsystems used to implement vehicle functions.
3.11 vehicle user
A person who operates, drives, owns or manages a vehicle.
EXAMPLE: an authorized representative or employee of the vehicle owner and vehicle operator,
an authorized representative or employee of the vehicle manufacturer.
3.12 on-board software update system
Software and hardware installed on the vehicle end and capable of directly receiving,
distributing and verifying update packages from outside the vehicle to implement software
update functions.
3.13 offline update
Software updates other than over-the-air updates.
4 Requirements for Software Update Management System
4.1 General Requirements
4.1.1 When producing vehicles with software update functions, the vehicle manufacturer shall
have a software update management system.
4.1.2 For each software update, the vehicle manufacturer shall record and securely store the
relevant information required in 4.3 for at least 10 years after the production of the vehicle
model is suspended.
4.1.3 When a software identification number is available, regardless of whether the software
identification number is stored on the vehicle, the vehicle manufacturer shall at least ensure
that:
a) Each software identification number is unique and identifiable;
b) Each software identification number establishes a clarified correspondence with the
software version information of all electronic control units (ECU) in the vehicle
system related to type approval;
c) When the vehicle type is expanded or a new vehicle type is generated, all information
of the corresponding software identification number is simultaneously updated.
4.1.4 When the software identification number is not available or the software identification
number is present but not stored on the vehicle, the vehicle manufacturer shall at least ensure
that:
a) Declare to the authorized institution the software version information of all electronic
control units (ECU) in the vehicle system related to type approval;
b) When performing software update on the declared software version, simultaneously
update the declaration information in a).
4.2 Process Requirements
4.2.1 There shall be a process that can uniquely identify all initial and updated software version
information and related hardware component information in vehicle systems related to type
approval or recall. The software version information shall at least include the software version
number and the integrity validation data of the corresponding update package.
4.2.9 A process shall be in place to notify vehicle users of the information of each software
update.
4.3 Requirements for Documents and Records
4.3.1 There shall be relevant documents describing the process of software update performed
by the vehicle manufacturer and demonstrating compliance with this document.
4.3.2 There shall be a document describing the vehicle system configuration related to type
approval. This document shall at least record the software and hardware information of the
vehicle system and relevant vehicle or vehicle system parameters.
4.3.3 When software identification numbers are available, each software identification number
shall have an auditable record. This record shall include at least:
a) Describe the compiling rules for the software identification number;
b) Describe the correspondence between the software identification number and the
vehicle system related to type approval;
c) Describe the correspondence between the software identification number and all
software version numbers of the vehicle system related to type approval;
d) Integrity validation data of all relevant update packages.
4.3.4 There shall be a document recording the target vehicle and confirming its configuration
and software update compatibility.
4.3.5 There shall be a document describing the information of each software update. The
document shall at least record:
a) The purpose, time and main content of software update;
b) Vehicle systems or functions that may be affected by software update;
c) Whether the vehicle systems or functions in b) are related to type approval;
d) For vehicle systems or functions related to type approval in c), whether software
update will affect their compliance;
e) Whether software update will affect any type approval-related parameters of the
vehicle system;
f) Obtain internal and / or external approval records from the vehicle manufacturer;
g) Methods and pre-requisites for performing software updates;
h) Proof that the software update can be securely and reliably executed;
i) Proof that software update has successfully passed validation and confirmation
procedures.
4.4 Requirements for Security Assurance
4.4.1 A process shall be in place to protect the update package and reasonably prevent it from
being tampered with before execution.
4.4.2 The entire software update process, including the process of releasing software update,
shall be protected to reasonably protect it from damage.
4.4.3 A process shall be in place to validate and confirm the functions of the updated software
and the rationality of the code.
4.4.4 An emergency management mechanism shall be in place to handle software update
emergencies.
NOTE: emergencies refer to all abnormal situations that may occur during the software update
process, including information security incidents, for example, releasing the update
package to non-target vehicles.
4.5 Additional Requirements for Over-the-air Update
4.5.1 For over-the-air update that may be performed while the vehicle is in motion, the vehicle
manufacturer shall demonstrate that it has relevant processes and procedures to ensure that the
over-the-air update will not affect vehicle safety.
4.5.2 For over-the-air update that requires specific skills or complex operations, the vehicle
manufacturer shall demonstrate that it has relevant processes and procedures to ensure that
over-the-air update can only be performed when professionals are present or when performing
the operation.
5 Vehicle Requirements
5.1 General Requirements
5.1.1 The vehicle shall protect the authenticity and integrity of the update package and
reasonably protect it from damage and invalid updates.
5.1.2 When the vehicle stores software identification numbers, it shall have the function of
updating the software identification numbers, and each software identification number shall be
readable with a standard interface (for example, OBD interface) using commercially available
tools.
5.1.3 When the vehicle does not store software identification numbers, the vehicle shall have
the function of updating the software version numbers, and the software version numbers of the
vehicle system related to type approval shall be readable in a standardized mode through an
electronic communication interface, including at least a standard interface (for example, OBD
interface).
5.1.4 The vehicle shall protect the stored software identification numbers and / or software
version numbers from tampering.
5.2 Additional Requirements for Over-the-air Update
5.2.1 Before executing over-the-air update, the vehicle shall inform the vehicle user of the
information regarding over-the-air update, which shall at least include:
a) Purposes (such as: importance of over-the-air update, and whether related to recalls
and security, etc.);
b) Any changes to vehicle functions;
c) Expected length of time to complete over-the-air update;
d) During the execution of over-the-air update, any vehicle functions that may not be
available;
e) Any instructions conducive to the secure execution of over-the-air update.
5.2.2 Before executing over-the-air update, the vehicle shall be confirmed by the vehicle user.
5.2.3 Before executing over-the-air update, the vehicle shall ensure that it satisfies the
prerequisites.
5.2.4 Before executing over-the-air update, the vehicle shall at least ensure that it has enough
power to complete over-the-air update (including possibly reverting to a previous version or
bringing the vehicle into a safe state).
5.2.5 If the execution of over-the-air update may affect vehicle safety, when executing over-
the-air update, the vehicle shall ensure safety through technical measures.
5.2.6 If the execution of over-the-air update may affect driving safety, when executing over-
the-air update, the vehicle shall at least:
a) Ensure that the vehicle cannot be driven by the vehicle user;
b) Ensure that any vehicle functions that affect the successful execution of over-the-air
update or affect vehicle safety cannot be used by the vehicle user.
5.2.7 When executing over-the-air update, the vehicle shall not prohibit the vehicle user from
unlocking the doors from inside the vehicle.
5.2.8 After executing over-the-air update, the vehicle shall:
a) Inform the vehicle user of the result of over-the-air update (success or failure);
executing the software update, read the software version number in the vehicle and record it.
After successfully executing software update using an update package related to type approval
and different from the current software version number of the test vehicle, read the updated
software version number and record it.
6.4 Software Identification Number / Software Version Number Anti-tamper Test
In terms of 5.1.4, in accordance with 8.3.5.4 in GB 44495-2024, carry out the test.
6.5 User Notification Test
In terms of 5.2.1 and 5.2.10, before executing over-the-air update, check and record the
information content, of which, the vehicle user is informed.
6.6 User Confirmation Test
In terms of 5.2.2, before executing over-the-air update, check and record the provided vehicle
user confirmation operation options and corresponding operation results.
6.7 Pre-requisite Test
In terms of 5.2.3, bring the vehicle in a state that satisfies the pre-requisites and does not satisfy
any of the pre-requisites (each condition that does not satisfy the pre-requisites needs to be
tested), respectively execute over-the-air update, check and record the result of the executed
over-the-air update on the vehicle.
6.8 Power Guarantee Test
In terms of 5.2.4, when other pre-requisites are satisfied, bring the vehicle in a state that satisfies
the power guarantee or does not satisfy the power guarantee, respectively execute over-the-air
update, check and record the result of the executed over-the-air update on the vehicle.
6.9 Vehicle Safety Test
In terms of 5.2.5, in accordance with the list of over-the-air update activities that may affect
vehicle safety, carry out corresponding over-the-air update,...