GB 44496-2024 PDF English
US$215.00 · In stock · Download in 9 secondsGB 44496-2024: General technical requirements for software update of vehicles Delivery: 9 seconds. True-PDF full-copy in English & invoice will be downloaded + auto-delivered via email. See step-by-step procedureStatus: Valid
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivery | Name of Chinese Standard | Status |
| GB 44496-2024 | English | 215 |
Add to Cart
|
0-9 seconds. Auto-delivery
|
General technical requirements for software update of vehicles
| Valid |
Excerpted PDFs (Download full copy in 9 seconds upon purchase)PDF Preview: GB 44496-2024
GB 44496-2024: General technical requirements for software update of vehicles---This is an excerpt. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.), auto-downloaded/delivered in 9 seconds, can be purchased online: https://www.ChineseStandard.net/PDF.aspx/GB44496-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
Foreword
This document was drafted in accordance with the rules provided in GB/T 1.1-2020 Directives
for Standardization - Part 1.Rules for the Structure and Drafting of Standardizing Documents.
Please be noted that certain content of this document may involve patents. The institution
issuing this document does not undertake the responsibility of identifying these patents.
This document was proposed by and shall be under the jurisdiction of Ministry of Industry and
Information Technology.
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).
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.
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.
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.
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.
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.
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.2 When a software identification number is ava, the following processes shall be in place.
4.2.3 A process shall be in place to identify target vehicles for software update.
4.2.4 A process shall be in place to confirm the compatibility of software update with target
vehicle configurations. At a minimum, this process shall include confirming the compatibility
with the latest known hardware and software configurations of the target vehicle before
releasing a software update.
4.2.5 A process shall be in place to identify the pertinence between the vehicle system being
updated and other vehicle systems.
4.2.6 A process shall be in place to evaluate, identify and record whether the software update
will affect type approval-related vehicle systems before releasing the software update, and shall
at least include whether the software update will affect relevant parameters.
4.2.7 A process shall be in place to evaluate, identify and record whether the software update
will add, change or enable any functions that do not exist or are not enabled at the time of type
approval, or whether it will change or disable any other parameters or functions defined in the
standards and regulations related to type approval before releasing the software update. The
evaluation shall at least include.
4.2.8 A process shall be in place to evaluate, identify and record whether the software update
will affect any other systems other than 4.2.6 and 4.2.7 (this system may be related to vehicle
safety and continuous operation) before releasing the software update, or whether it will add or
change the functions at the time of vehicle registration.
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.
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.
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.
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.
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.
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.
5.2.9 When over-the-air update fails, the vehicle shall ensure that the vehicle system is restored
to the previous available version in a timely manner or the vehicle is placed in a safe state.
5.2.10 For 5.2.1 and 5.2.8, the vehicle shall notify the vehicle user of the information through
the vehicle system. If the vehicle user cannot be informed through the vehicle system due to
hardware reasons of the vehicle, the vehicle manufacturer shall prove that it has reasonable
technical measures to achieve information notification.
6 Test Methods
6.1 General Requirements
For vehicles with the function of software update, the tests shall be carried out in accordance
with the following requirements.
6.2 Authenticity and Integrity Test of Update Packages
In terms of 5.1.1, for vehicles that only have the function of offline update, in accordance with
8.3.4.3 in GB 44495-2024, carry out the test.
In terms of 5.1.1, for vehicles that only have the function of over-the-air update, in accordance
with 8.3.4.2.2 in GB 44495-2024, carry out the test.
6.3 Software Identification Number / Software Version Number Update and Reading Test
In terms of 5.1.2, when the vehicle stores the software identification number, before executing
the software update, read the software identification number in the vehicle 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, check and record the technical
measures adopted by the vehicle, the result of the executed over-the-air update and the vehicle
state.
6.10 Driving Safety Test
In terms of 5.2.6 a), in accordance with the list of over-the-air update activities that may affect
driving safety, carry out corresponding over-the-air update. During the execution of over-the-
air update, try to bring the vehicle in a driving state, check and record the result of the executed
over-the-air update and the driving state of the vehicle.
6.11 Door Anti-lock Test
In terms of 5.2.7, on the premise of locking the doors of the vehicle, execute over-the-air update.
During the execution of over-the-air update, unlock the doors from inside the vehicle and record
the door unlocking result.
6.12 Result Notification Test
In terms of 5.2.8 a), 5.2.8 b) and 5.2.10, after the over-the-air update is successful, check and
record the result notification information, check and record the on-board electronic version of
the motor vehicle product instruction manual (if any).
In terms of 5.2.8 a), 5.2.8 c) and 5.2.10, after the over-the-air update fails, check and record the
result notification information and handling suggestions for the vehicle user.
6.13 Update Failure Handling Test
In terms of 5.2.9, during the execution of over-the-air update, trigger over-the-air update failure,
check and record the vehicle state.
7 Same Type Determination
7.1.1 For vehicles without the function of over-the-air update, if they comply with the following
provisions, then, they shall be regarded as the same type.
7.1.2 For vehicles with the function of over-the-air update, if they comply with the following
provisions, then, they shall be regarded as the same type.
a) The complete-vehicle manufacturers are the same;
b) The content related to Chapter 4 in the software update management system used has
not changed;
c) If there is an on-board software update system, then, the controller software version,
hardware model and manufacturer are the same, but the software versions are allowed
to be different, as long as it does not affect the control strategy of the software update;
d) The electronic control systems that can be updated by software have not been added;
e) The technical measures of protecting the integrity and authenticity of the update
packages are the same;
f) The situation of whether the software identification number is stored is the same;
g) The software identification number and / or software version number are stored in the
same location on the vehicle;
8 Motor Vehicle Product Instruction Manual
For vehicles with the function of software update, the product instruction manual shall at least
include.
9 Implementation of the Standard
For vehicle models newly applying for type approval, it shall be implemented from the date of
implementation of this document.
......
Source: Above contents are excerpted from the full-copy PDF -- translated/reviewed by: www.ChineseStandard.net / Wayne Zheng et al.
Tips & Frequently Asked QuestionsQuestion 1: How long will the true-PDF of English version of GB 44496-2024 be delivered?Answer: The full copy PDF of English version of GB 44496-2024 can be downloaded in 9 seconds, and it will also be emailed to you in 9 seconds (double mechanisms to ensure the delivery reliably), with PDF-invoice. Question 2: Can I share the purchased PDF of GB 44496-2024_English with my colleagues?Answer: Yes. The purchased PDF of GB 44496-2024_English will be deemed to be sold to your employer/organization who actually paid for it, including your colleagues and your employer's intranet. Question 3: Does the price include tax/VAT?Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countriesQuestion 4: Do you accept my currency other than USD?Answer: Yes. www.ChineseStandard.us -- GB 44496-2024 -- Click this link and select your country/currency to pay, the exact amount in your currency will be printed on the invoice. Full PDF will also be downloaded/emailed in 9 seconds. How to buy and download a true PDF of English version of GB 44496-2024?A step-by-step guide to download PDF of GB 44496-2024_EnglishStep 1: Visit website https://www.ChineseStandard.net (Pay in USD), or https://www.ChineseStandard.us (Pay in any currencies such as Euro, KRW, JPY, AUD).
Step 2: Search keyword "GB 44496-2024".
Step 3: Click "Add to Cart". If multiple PDFs are required, repeat steps 2 and 3 to add up to 12 PDFs to cart.
Step 4: Select payment option (Via payment agents Stripe or PayPal).
Step 5: Customize Tax Invoice -- Fill up your email etc.
Step 6: Click "Checkout".
Step 7: Make payment by credit card, PayPal, Google Pay etc. After the payment is completed and in 9 seconds, you will receive 2 emails attached with the purchased PDFs and PDF-invoice, respectively.
Step 8: Optional -- Go to download PDF.
Step 9: Optional -- Click Open/Download PDF to download PDFs and invoice.
See screenshots for above steps: Steps 1~3 Steps 4~6 Step 7 Step 8 Step 9
|