GB 44496-2024General technical requirements for software update of vehicles (English PDF)

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.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.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.

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.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.