GB 44497-2024 English PDF

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

GB 44497-2024: Intelligent and connected vehicle - Data storage system for automated driving
GB 44497-2024
GB
NATIONAL STANDARD OF THE
PEOPLE’S REPUBLIC OF CHINA
ICS 43.040.10
CCS T 36
Intelligent and connected vehicle - Data storage system for
automated driving
ISSUED ON: AUGUST 23, 2024
IMPLEMENTED ON: JANUARY 01, 2026
Issued by: State Administration for Market Regulation;
National Standardization Administration.
Table of Contents
Foreword ... 3
1 Scope ... 4
2 Normative references ... 4
3 Terms and definitions ... 5
4 Technical requirements ... 8
4.1 General... 8
4.2 Data recording requirements for type I system ... 8
4.3 Data recording requirements for type II system ... 10
4.4 Data element requirements ... 11
4.6 Data reading requirements ... 21
4.7 Information security requirements ... 25
4.8 Collission-resistance requirements ... 26
4.9 Environmental evaluation requirements ... 26
5 Test conditions ... 31
5.1 Test field and test environment requirements ... 31
5.2 Test equipment and data recording requirements ... 31
5.3 Test vehicle requirements ... 32
6 Test method ... 32
6.1 Trigger test ... 32
6.2 Continuous recording trigger test ... 35
6.3 Collision test ... 36
6.4 Data accuracy verification test ... 36
6.5 Data storage mechanism test ... 36
6.6 Environmental evaluation test ... 38
6.7 Information security test ... 45
7 Determination of the same type ... 45
7.1 Directly deemed conditions ... 45
7.2 Deemed conditions after test verification ... 45
8 Implementation of the standard ... 46
Appendix A (Normative) Definition of data extraction symbols ... 47
Appendix B (Normative) Export file format of automatic driving data recording system
... 49
References ... 52
Intelligent and connected vehicle - Data storage system for
automated driving
1 Scope
This document specifies the technical requirements, test methods, same type
determination of the automatic driving data recording system of intelligent and
connected vehicles.
This document applies to the automatic driving data recording system equipped on
Category M and Category N vehicles.
2 Normative references
The contents of the following documents constitute the essential terms of this document
through normative references in the text. Among them, for dated references, only the
version corresponding to that date applies to this document; for undated references, the
latest version (including all amendments) applies to this document.
GB/T 1865-2009 Paints and varnishes - Artificial weathering and exposure to
artificial radiation - Exposure to filtered xenon-arc radiation
GB 11551 The protection of the occupants in the event of a frontal collision for
motor vehicle
GB 16735 Road vehicle - Vehicle identification number (VIN)
GB/T 19951-2019 Road vehicles - Disturbances test methods for
electrical/electronic component from electrostatic discharge
GB 20071 The protection of the occupants in the event of a lateral collision
GB/T 20913 The protection of the occupants in the event of an off-set frontal
collision for passenger car
GB/T 21437.3-2021 Road vehicles - Test method of electrical disturbances from
conduction and coupling - Part 3: Electrical transient transmission by capacitive and
inductive coupling via lines other than supply lines
GB/T 28046.1-2011 Road vehicles - Environmental conditions and testing for
electrical and electronic equipment - Part 1: General Your
or the user operates the ADS to exit device, the automated driving data recording
system shall record data elements that meet the requirements of Table 1.
4.2.1.2 When the current time sequence event data recording is in progress, if a time
sequence event occurs during this period, the relevant data of the subsequent time
sequence events may not be fully recorded; however, it shall be ensured that the relevant
data of the subsequent time sequence events are recorded at least in accordance with
the requirements of Table 1.
4.2.1.3 When data cannot be obtained due to failure, the automated driving data
recording system is allowed to record incomplete event-related data.
4.2.2 Impact event
4.2.2.1 Triggering conditions
When the vehicle meets the requirements of 4.1.1 in GB 39732-2020, the event shall
be recorded.
4.2.2.2 Starting point of event and end point of event
The start and end of the impact event shall meet the following requirements:
a) The event starting point shall meet the requirements of 4.1.3 in GB 39732-2020;
b) The event ending point shall meet the requirements of 4.1.4 in GB 39732-2020.
4.2.2.3 Starting and ending point of event record
The starting and ending point of the impact event record shall at least meet the following
requirements:
a) Starting point of event record: 15 s before the starting point of event or the moment
the automated driving system is activated, whichever is later;
b) Ending point of event record: 5 s after the starting point of event, the moment the
automated driving system is exited, or the ending point of event, whichever is
earlier.
4.2.2.4 Event lock conditions
The impact event lock conditions shall at least meet the requirements of 4.1.2 of GB
39732-2020.
Note: Allowing the deployment of pedestrian protection devices is not defined as a lock event.
4.2.3 Events with collision risk
4.2.3.1 Trigger conditions
When the longitudinal deceleration requested by the automated driving system is
greater than 5 m/s2, the event shall be recorded.
Note: The automated driving data recording system is allowed to add other conditions as trigger
conditions for events with collision risk, such as a lower requested longitudinal deceleration.
4.2.3.2 Starting and ending point of event
The starting and ending point of event with collision risk shall meet the following
requirements:
a) Starting point of event: The moment when the longitudinal deceleration requested
by the automated driving system is greater than 5 m/s2;
b) Ending point of event: The moment when the longitudinal deceleration requested
by the automated driving system is no greater than 5 m/s2 after the start of this
event.
4.2.3.3 Starting and ending point of event record
The starting and ending point of events with collision risk shall at least meet the
following requirements:
a) Starting point of event recording: 15 s before the starting point of event or the
time when the automated driving system is activated, whichever is later;
b) Ending point of event recording: 5 s after the starting point of event, the time
when the automated driving system exits, or the ending point of event, whichever
is earlier.
4.3 Data recording requirements for type II system
During the activation of the automated driving system, the type II system shall record
at least the following data:
a) Record data elements that meet the requirements of Table 1 at the real-time
recording start point;
b) Real-time continuous recording of data elements that meet the requirements of
Tables 2 ~ 5;
c) Timestamp events: When the automated driving system enters the activation state,
exits, issues an intervention request, starts to execute the minimum risk strategy,
ADS serious failure and vehicle serious failure occur, or the user operates the
ADS to exits device in accordance with the provisions of GB/T 44721, the
The data recorded by the automated driving data recording system shall be stored in the
vehicle-side non-volatile memory.
4.5.2 Storage capacity
The automated driving data recording system shall meet the following requirements:
a) The total number of impact events and collision risk events that can be stored by
the Type I system shall not be less than 5; the number of timestamp events that
can be stored shall not be less than 2500;
b) The continuous data that can be stored by the Type II system shall not be less than
8 hours; the number of timestamp events that can be stored shall not be less than
2500.
4.5.3 Storage overwrite mechanism
4.5.3.1 Type I system
When the storage area of a Type I system is full, the following storage overwrite
requirements shall be met:
a) Time sequence event data and timestamp event data shall not overwrite each other;
b) For time sequence events, impact event data shall not be overwritten by collision
risk event data;
c) Impact event data that meets the locking conditions shall not be overwritten by
subsequent event data;
d) Other situations shall be overwritten in chronological order;
e) When the storage area of a Type I system is full and the stored time sequence data
are all locked event data, the time sequence event data of the automated driving
data recording system is allowed to be overwritten, if the vehicle manufacturer
stores all locked event data securely on the enterprise platform or server.
4.5.3.2 Type II system
When the storage area of a Type II system is full, the following storage overwrite
requirements shall be met:
a) Real-time continuously recorded data and timestamp event data shall not
overwrite each other;
b) Other situations shall be overwritten in chronological order.
4.5.3.3 Multiple automated driving data recording systems
If the vehicle has both Type I and Type II systems, the data recorded by Type I and Type
II systems shall not overwrite each other.
4.5.4 Power-off storage
During the activation of the automated driving system, if the automated driving data
recording system cannot be powered normally due to an impact event, the automated
driving data recording system shall at least record the data from the event recording
start point to the event starting point.
Example:
Unable to be powered normally: The automated driving data recording system with redundant
power supply cannot continue to be powered by a non-redundant power supply.
4.6 Data reading requirements
4.6.1 General
The data recorded by the automated driving data recording system shall be able to be
read and correctly parsed, including vehicle and component level reading. The vehicle-
level data reading method shall comply with the requirements of 4.6.2 ~ 4.6.4.
4.6.2 Vehicle-level data reading port requirements
The data recorded by the automated driving data recording system shall implement the
vehicle-level data reading port, in accordance with the relevant definition of the
Ethernet pin allocation scheme in GB/T 43258.4.
4.6.3 Data reading protocol requirements
4.6.3.1 Ethernet communication parameters
The Ethernet communication parameters shall be described in the manual of the motor
vehicle product. The description shall at least include the on-board diagnostic (OBD)
port pin type, the Internet Protocol (IP) address and logical address of the data reading
tool, the IP-based diagnostic communication (DoIP) established by the data reading
tool.
4.6.3.2 Reading data from the automated driving data recording system based on
DoIP
4.6.3.2.1 General requirements
Reading data based on DoIP shall meet the DoIP application requirements in GB/T
43258.2.
connection between the data reading tool and the vehicle is normal.
The data reading process shall maintain the session through the tester online (3E16)
service specified in GB/T 40822; the sending cycle shall be 2 s.
The data reading process shall meet the following requirements (see Figure 1 for a
flowchart).
a) Prompt to enter the date or serial number of the data to be read: This step is to
drive the ECU that implements the automatic driving data recording function to
integrate the timestamp event data, according to the time interval by the user
entering the date interval of the timestamp event requested to be read in the data
reading tool; or to drive the ECU to integrate the time sequence event data,
according to the serial number by the user entering the serial number of the time
sequence event to be read in the data reading tool. The serial numbers of the time
sequence events shall be arranged in chronological order from 0116 to the largest.
If the ECU that implements the automatic driving data recording function does
not contain the event data within the date interval, a negative response code (NRC)
shall be returned in accordance with the provisions of GB/T 40822.
b) Entering extended mode: This step uses the diagnostic session control (1016)
service specified in GB/T 40822, to drive the ECU that implements the automated
driving data recording function to enter the extended session mode.
Note: The execution order of steps a) and b) in the data reading process can be adjusted
as needed.
c) Data integration: This step uses the routine control (3116) service specified in
GB/T 40822, to drive the ECU that implements the automated driving data
recording function according to user needs. According to the requirements of the
data reading tool, the time sequence event or timestamp event data is integrated
and saved. The data extraction symbol definition related to this service shall
comply with the requirements of Appendix A.
d) Request file transfer: This step uses the request file transfer (3816) service
specified in GB/T 40822. The file path parameter carried by the request
instruction shall be "/var/DSSAD/< file name>"; the file identifier parameter shall
be 1016. Among them, the file name shall comply with the requirements of B.1.4
in Appendix B.
e) Data transmission: This step uses the data transmission (3616) service specified in
GB/T 40822, to transmit the data stream of the read file.
f) Exit data transmission: This step uses the request transmission termination (3716)
service specified in GB/T 40822, to end the file data stream transmission.
g) Verify file integrity: This step uses the routine control (3116) service specified in
shall meet the requirements of 4.9.1.
4.9.2.4 Slow drop and rise of supply voltage
Perform the test in accordance with 6.6.1.4. After the test, the product functional status
shall meet the requirements of 4.9.1.
4.9.2.5 Transient change of supply voltage
4.9.2.5.1 Transient voltage drop
Perform the test in accordance with 6.6.1.5.1. After the t...