GB/T 32960.3-2025Technical specifications for remote service and management system for electric vehicles — Part 3: Communication protocol and data format (English PDF)
电动汽车远程服务与管理系统技术规范 第3部分:通信协议及数据格式
Open the GB/T 32960.3-2025 preview as PDF
This is a limited preview
Buy now to download the full PDF (33 pages)
Issued by
SAMR; SAC
Level / Type
National · Recommended
Issue date
April 25, 2025
Implementation date
November 1, 2025
Scope
GB/T 32960.3-2025 is the English-translated version of 电动汽车远程服务与管理系统技术规范 第3部分:通信协议及数据格式.
GB/T 32960.3-2025 is the Chinese national standard covering the protocol by which an electric vehicle's data reaches a monitoring platform — the login, reporting and logout sequence between platforms, the packet structure with its command unit, encryption method and checksum, the data units for vehicle, drive motor, fuel cell, location and alarm data, the battery voltage and temperature now reported for an hour after the vehicle is powered down, and the thermal event alarm added in this edition. Reporting no longer stops when the vehicle is switched off. Part 3 of the series. It replaces GB/T 32960.3-2016, under the Ministry of Industry and Information Technology. In force from 1 November 2025. Issued on 25 April 2025, it has been in force since 1 November 2025, replacing GB/T 32960.3-2016.
Document preview — GB/T 32960.3-2025
National Standard of the People's Republic of China
- ICS
- 43.040
- Classification
- T 35
- Replacing
- GB/T 32960.3-2016
Issued by: State Administration for Market Regulation; Standardization Administration of the PRC
Contents
- Foreword3
- Introduction6
- 1 Scope7
- 2 Normative references7
- 3 Terms and definitions8
- 4 General requirements10
- 5 Communication connection10
- 5.1 Connection establishment10
- 5.2 Information transmission11
- 5.3 Disconnection12
- 5.4 Retransmission mechanism12
- 6 Data packet structure and definition13
- 6.1 Data description13
- 6.2 Data packet structure13
- 6.3 Command unit14
- 6.4 Time15
- 7 Data unit format and definition16
- 7.1 Vehicle login16
- 7.2 Real-time information reporting16
- 7.3 Vehicle logout28
- 7.4 Platform login28
- 7.5 Platform logout29
- 7.6 Data unit encryption key exchange29
- Appendix A (Normative) Partial field definition30
- A.1 Gear status definition30
- A.2 Vehicle static information30
- Appendix B (Informative) Communication protocol from onboard terminal to platform34
- B.2 Information transmission34
- B.3 Data packet structure and definition39
Foreword
This document was drafted in accordance with the provisions of GB/T 1.1-2020 "Directives for standardization - Part 1: Rules for the structure and drafting of standardizing documents".
This document is Part 3 of GB/T 32960 "Technical specifications for remote service and management system for electric vehicles". GB/T 32960 has published the following parts. - Part 1: General principle; - Part 2: On-board terminal;
- Part 3: Communication protocol and data format; - Part 4: Conformance test.
This document replaces GB/T 32960.3-2016 "Technical specifications for remote service and management system for electric vehicles - Part 3: Communication protocol and data format". Compared with GB/T 32960.3-2016, in addition to structural adjustments and editorial changes, the main technical changes are as follows.
a) ADD communication security requirements between platforms and between onboard terminals and platforms (see 5.1 and B.2.1 of Appendix B);
b) ADD the definition of terms for the minimum parallel unit of power batteries and the transmission requirements of voltage data, power battery temperature data, fuel cell stack data, supercapacitor data, supercapacitor extreme value data (see 5.2.3, 5.2.4, B.2.1 of Appendix B);
c) ADD the vehicle data transmission requirements after the vehicle is under high voltage after driving or charging is completed and during the thermal event alarm (see 5.2.4 and B.2.1 of Appendix B);
d) ADD the distinction of protocol version numbers (see 6.2);
e) ADD the definition of the response error flag (see 6.3.2);
f) ADD the data transmission format and definition of "Number of battery management systems", "Number of power battery packs corresponding to the battery management system", "Power battery pack coding"; DELETE the definition of the rechargeable energy storage device subsystem, changing it into distinguishing and collection of the number of BMS systems; DELETE the data transmission format and definition of "Number of rechargeable energy storage subsystems", "Rechargeable energy storage system coding length", "Rechargeable energy storage system coding" (see 7.1; 7.1 of the 2016 edition);
g) ADD the transmission format and definition of signature information (see 7.2.1, 7.2.2, B.3.5.2.1, B.3.5.2.2 of Appendix B), activation information, activation result response information (see B.3.5.5; B.3.5.6 of Appendix B);
h) ADD the power battery minimum parallel unit voltage data, power battery temperature data, fuel cell stack data, supercapacitor data, supercapacitor extreme value information type flag (see 7.2.3 and B.3.5.2.3 of Appendix B);
i) ADD the transmission format and definition of power battery minimum parallel unit voltage data (see 7.2.4.2 and B.3.5.3.2 of Appendix B), power battery temperature data (see 7.2.4.3 and B.3.5.3.3 of Appendix B), fuel cell stack data (see 7.2.4.6 and B.3.5.3.6 of Appendix B), supercapacitor data (see 7.2.4.10 and B.3.5.3.10 of Appendix B), supercapacitor extreme value data (see 7.2.4.11 and B.3.5.3.11 of Appendix B);
j) CHANGE the description of "rechargeable energy storage device voltage data" to "power battery minimum parallel unit voltage data" (see 7.2.4.2 and B.3.5.3.2 of
Appendix B ; B.3.5.3.8 of Appendix B of the 2016 edition); CHANGE the
description of "rechargeable energy storage device temperature data" to "power battery temperature data" (see 7.2.4.3 and B.3.5.3.3 of Appendix B; B.3.5.3.9 of
Appendix B of the 2016 edition);
k) DELETE the data format and definition of power battery extreme value (see 7.2.3.6 of the 2016 edition);
l) DELETE the rechargeable energy storage device voltage data (see B.3.5.3.8 of
Appendix B of the 2016 edition); DELETE the rechargeable energy storage
device temperature data (see B.3.5.3.9 of Appendix B of the 2016 edition);
m) CHANGE the vehicle speed, total voltage, total current range, insulation resistance value definition in vehicle data (see 7.2.4.1; 7.2.3.1 of the 2016 edition);
n) DELETE the format and definition of motor controller input voltage and motor controller DC bus current (see 7.2.3.2 of the 2016 edition); CHANGE the drive motor speed and drive motor torque range in the drive motor data (see 7.2.4.4; 7.2.3.2 of the 2016 edition);
o) CHANGE the "Fuel cell data" to "Fuel cell engine and onboard hydrogen system data"; CHANGE the definition of probe temperature value (see 7.2.4.5; 7.2.3.3 of the 2016 edition); ADD the format and definition of the remaining hydrogen percentage, high-voltage DC/DC controller temperature (see 7.2.4.5); DELETE the fuel cell voltage and fuel cell current data (see 7.2.3.3 of the 2016 edition);
p) DELETE the format and definition of the average fuel consumption rate per 100 kilometers in the engine state (see 7.2.3.4 of the 2016 edition);
q) CHANGE the vehicle position data transmission requirements (see 7.2.4.8; 7.2.3.5 of the 2016 edition);
r) ADD the "thermal event alarm" level and alarm identification bit; ADD the relevant alarm identification bits involved in the fuel cell engine and the on-board hydrogen system, fuel cell stack, supercapacitor system, drive motor; ADD the format and definition of alarm level data transmission (see 7.2.4.9);
s) ADD the gear state invalid/valid state identification (see A.1 of Appendix A);
t) CHANGE the vehicle static information list (see A.2 of Appendix A; A.2 of
Appendix A of the 2016 edition).
Please note that some of the contents of this document may involve patents. The issuing agency of this document does not assume the responsibility for identifying patents.
This document was proposed by the Ministry of Industry and Information Technology of the People's Republic of China.
This document shall be under the jurisdiction of the National Technical Committee for Automobile Standardization (SAC/TC 114).
The drafting organizations of this document. China Automotive Technology and Research Center Co., Ltd., China Automotive Research and Inspection Center (Tianjin) Co., Ltd., China Automotive Data (Tianjin) Co., Ltd., Beijing Institute of Technology, Mercedes-Benz (China) Investment Co., Ltd., NIO Technology (Anhui) Co., Ltd., BYD Auto Industry Co., Ltd., Tsinghua University, Deep Blue Automotive Technology Co., Ltd., China National Heavy Duty Truck Group Co., Ltd., Seres Automotive Co., Ltd., Beijing Yicheng High-tech Technology Development Co., Ltd., Beijing National New Energy Vehicle Technology Innovation Center Co., Ltd., Tesla (Shanghai) Co., Ltd., General Motors (China) Investment Co., Ltd., China First Automobile Co., Ltd., Great Wall Motor Co., Ltd., Volkswagen (China) Investment Co., Ltd., Toyota Motor China Investment Co., Ltd., Honda Motor (China) Investment Co., Ltd., Nissan (China) Investment Co., Ltd., BMW (China) Service Co., Ltd.
The main drafters of this document. Zhang Zhaosheng, Zheng Tianlei, Yu Yang, Liu Shaohui, Dou Rupeng, Sun Wenjun, Zhang Kaiming, Li Gang, Zhu Hao, Jin Xiulian, Jiang Feng, Liang Qun, Wu Feng, Xu Jianbo, Wang Xu, Wang Zhenpo, Qian Li, Liu Peng, Wang Jia, Guo Xiaomeng, Zhou Lin, Ding Jie, Zheng Guangzhou, Ma Qizhen, Yan Jing, Li Xue, Wu Shaohua, Cheng Xuefeng, Zhang Qian, Zhen Jie, Zhu Pingqing, Zhu Tie.
This document was first published in 2016.This is the first revision.
Introduction
With the encouragement and support of a series of national policies, electric vehicle technology has developed rapidly and the scale of the industry has expanded rapidly. In order to improve the remote monitoring capabilities of electric vehicles, strengthen the supervision of electric vehicle operation safety, promote the technological progress and promotion and application of the electric vehicle industry, it is necessary to formulate a national unified standard for electric vehicle remote monitoring communication protocol. GB/T 32960 "Technical specifications for remote service and management system for electric vehicles" aims to establish a unified technical specification for electric vehicle remote service and management system, which is intended to consist of four parts.
- Part 1: General principles. The purpose is to establish the monitoring system of "onboard terminal-enterprise platform-public platform" in general and clarify the corresponding definitions.
- Part 2: On-board terminal. The purpose is to specify the functional requirements and performance requirements of the onboard terminal, to support the collection and upload of monitoring data.
- Part 3: Communication protocol and data format. The purpose is to specify the data upload protocol, unify the data packet structure and definition, data unit format and definition.
- Part 4: Conformance test. The purpose is to verify the consistency of the data protocol uploaded by the vehicle with the data protocol specified in the standard.
Technical specifications for remote service and management system for electric vehicles - Part 3: Communication protocol and data format
1 Scope
This document specifies the protocol structure, communication connection, data packet structure and definition, data unit format and definition in the remote service and management system for electric vehicles.
This document applies to the connection and communication between platforms and between onboard terminals and platforms in the remote service and management system for electric vehicles.
2 Normative references
GB/T 1988
GB 16735
GB 18030
GB/T 19596
GB/T 24548
GB/T 28816
GB/T 32960.1
GB/T 34014
GB 38031
GB/T 40855-2021
3 Terms and definitions
The terms and definitions defined in GB/T 19596, GB/T 24548, GB/T 28816, GB/T 32960.1, as well as the following terms and definitions, apply to this document.
3.1 Client platform
The remote service and management platform that acts as the data sender during data interaction.
3.2 Server platform
The remote service and management platform that acts as the data receiver during data interaction.
3.3 Register
The process in which the client platform provides the platform and vehicle static information to the server platform, for the platform and vehicle identity authentication.
3.4 Upstream
The direction of data transmission from the client to the server.
3.5 Downstream
The direction of data transmission from the server to the client.
3.6 Vehicle login
The authentication performed before the client reports the vehicle status information to the server.
3.7 Vehicle logout
The authentication performed before the client confirms to the server that the vehicle data transmission stops normally.
4 General requirements
4.1 The protocol structure shall use the Transmission Control Protocol/Internet Protocol
(TCP/IP) network control protocol, as the underlying communication bearer protocol, see Figure 1.
Figure 1 -- Communication protocol stack for remote service and management system of electric vehicle
4.2 The connection and communication protocol between platforms shall meet the
provisions of Chapters 5 ~ 7.
4.3 The vehicle shall be registered on the service platform and upload the vehicle static information. The vehicle static information is shown in A.2 of Appendix A.
5 Communication connection
5.1 Connection establishment
Communication between platforms shall comply with the security requirements of 5.3 inter-platform communication in GB/T 40855-2021.The client platform initiates a communication connection request to the server platform. When the communication link connection is established, the client platform shall automatically send login information to the server platform for identity identification; the server platform shall verify the received data. When the verification is correct, the server platform shall return a successful response; when the verification is wrong, the server platform shall store the error data record and notify the client platform. The login process is shown in Figure 2.
5.2 Information transmission
5.2.1 After the client platform successfully logs in, it shall report the real-time
information of the electric vehicle to the server platform. The real-time information reporting process is shown in Figure 3.
5.2.2 When the client platform reports information to the server platform, the server
platform shall verify the received data. When the verification is correct, the server platform makes a correct response; when the verification is wrong, the server platform makes an incorrect response. When the response information of the server platform is wrong, the client shall resend the real-time information of the vehicle; it shall resend it once every 1 minute; it shall not send it again after 3 failures.
5.2.3 When the client platform reports information to the server platform, it shall
assemble and report the vehicle data, power battery minimum parallel unit voltage data, power battery temperature data, drive motor data, fuel cell engine and onboard hydrogen system data, fuel cell stack data, engine data, vehicle location data, alarm data, 5.2.4 After the vehicle is driven or charged and the high voltage is removed, the power battery related data specified in 7.2.4.2 and 7.2.4.3 shall continue to be monitored and reported. Within 1 hour after power off, the monitoring frequency shall be not less than 1 Hz; the power battery related data specified in 7.2.4.2 and 7.2.4.3 within 59 min 30 s ~ 1 h shall be reported (at least 1 data). The enterprise should monitor the wake-up method customized by the enterprise later; report the data after abnormality is found.
5.2.5 The time period for the client platform to report information to the server platform shall be adjustable. The maximum time period for vehicle information reporting shall not exceed 30 s; when the vehicle has a level 3 or 4 alarm in Table 23, it shall report all data items included in the vehicle model specified in 7.2.4 within the period from 30 s before the fault occurs to the alarm release time period, the information sampling period shall not exceed 1s, the data before the fault occurs shall be transmitted in the form of re-issuance. When the vehicle has a level 3 or 4 alarm in Table 23 in the monitoring state after driving or charging is completed and high voltage removed, the first frame after the onboard terminal is started shall be used as the fault alarm time point; all data items included in the vehicle model specified in 7.2.4 within the period of 30 s after the fault alarm time point shall be reported; the information sampling period shall not exceed 1 s.
5.3 Disconnection
5.3.1 The server platform shall disconnect the session connection with the client
platform according to the following situations. TCP connection interruption.
5.3.2 The client platform shall disconnect the session connection with the server
platform according to the following situations.
- TCP connection is interrupted;
- TCP connection is normal, meanwhile no response is received after reaching the number of retransmissions.
5.4 Retransmission mechanism
When the data communication link is abnormal, the client platform shall store the real- time reporting data locally. After the data communication link is restored to normal, the stored reporting data shall be retransmitted during the idle time of sending the real-time reporting data. The retransmitted reporting data shall be the data stored during the abnormal communication link within 7 days. The data format is the same as the real- time reporting data, which is marked as retransmission information reporting (0x03), see Table 3.
6 Data packet structure and definition
6.1 Data description
6.1.1 Data type
The data type transmitted in the protocol is shown in Table 1.
6.1.2 Transmission rules
The protocol shall use the big-endian network byte order to transmit words and double words.
6.2 Data packet structure
A complete data packet shall consist of a start character, a command unit, an identification code, a data encryption method, a data unit length, a data unit, a checksum.
The data packet structure and definition are shown in Table 2.
6.3 Command unit
6.3.1 Command identifier
The command identifier shall be the unique identifier of the initiator. The definition of command identifier is shown in Table 3.
6.3.2 Response flag
The response flag of the active initiator of the command is 0xFE, indicating that this packet is a command packet; when the response flag is not 0xFE, the passive receiver shall not respond. When the passive receiver response flag of the command is not 0xFE, this packet is indicated as a response packet.
When the server sends a response, the response flag shall be changed, the message time shall be retained, the remaining message content shall be deleted, the check bit shall be recalculated.
7 Data unit format and definition
7.1 Vehicle login
For the format and definition of vehicle login data, see Table 6.
7.2.2 Vehicle-side signature information
The vehicle-side digital signature format and definition of real-time information are shown in Table 8.
7.2.3 Information type flag
The definition of information type flag is shown in Table 9.
7.2.4 Information body
7.2.4.1 Vehicle data
For the vehicle data format and definition, see Table 10.
7.2.4.2 Power battery minimum parallel unit voltage data
The format and definition of power battery minimum parallel unit voltage data are shown in Table 11 and Table 12.
7.2.4.3 Power battery temperature data
The format and definition of power battery temperature data are shown in Table 13 and Table 14. ......
......
This preview omits tables, figures, formulas and parts of the technical clauses. The complete document — 33 pages — is available in the English PDF.
Referenced standards
Normative references
- GB 16735Road vehicle - Vehicle identification number (VIN)
- GB 18030Information technology - Chinese coded character set
- GB/T 19596Terminology of electric vehicles
- GB/T 24548Fuel cell electric vehicles - Terminology
- GB/T 32960.1Technical specifications for remote service and management system for electric vehicles — Part 1: General principle
- GB/T 34014Coding regulation for automotive traction battery (including National Amendment No. 1 of 2026)
GB/T 1988 · GB/T 28816
Cited by
- GB/T 47136-2026Specification for the assessment of the health and safety state of traction batteries for battery electric vehicles
- GB/T 47283-2026Specification for the defect monitoring and analysis of traction batteries in battery swap scenarios
- GB/T 32960.1-2025Technical specifications for remote service and management system for electric vehicles — Part 1: General principle
- GB/T 32960.4-2025Technical specifications for remote service and management system for electric vehicles — Part 4: Conformance test
- GB/T 34015.5-2025Recovery of traction battery used in electric vehicle - Echelon use - Part 5: Battery design guide for echelon use
- GB/T 45688-2025Technical requirements for dynamic monitoring and early warning of new energy vehicle safety operation
Editions of GB/T 32960.3
| Edition | Title | Revision | Status |
|---|---|---|---|
| GB/T 32960.3-2025 | Technical specifications for remote service and management system for lectric vehicles - Part 3: Communication protocol and data format | current edition | Current |
| GB/T 32960.3-2016 | Technical specifications of remote service and management system for electric vehicles - Part 3: Communication protocol and data format | previous edition | In force |
This page sells the current edition, GB/T 32960.3-2025. Earlier editions are listed for reference only.
How to Buy GB/T 32960.3-2025
- 1Add to cart. Click the "Buy GB/T 32960.3-2025" button on this page. You can add more standards before checkout.
- 2Checkout. Enter your email and billing details. Payment is processed securely by Stripe (cards, Apple Pay, Google Pay supported).
- 3Instant delivery (0–9 sec). Delivery is automatic: within seconds of payment you'll receive an email with a secure download link. The link stays valid for 72 hours.
- 4Invoice included. A tax invoice is attached to the confirmation email. Need a custom invoice? Contact us.
Related Standards
GB 16735-2019 — Road vehicle - Vehicle identification number (VIN)
GB 18030-2022 — Information technology - Chinese coded character set
GB 38031-2025 — Electric vehicles traction battery safety requirements
Secure payment via Stripe
Payments accepted
GB/T 32960.3-2025
$590.00