GB/T 32960.3-2025 PDF EnglishUS$605.00 · In stock · Download in 9 seconds
GB/T 32960.3-2025: Technical specifications for remote service and management system for lectric vehicles - Part 3: Communication protocol and data format Delivery: 9 seconds. True-PDF full-copy in English & invoice will be downloaded + auto-delivered via email. See step-by-step procedure Status: Valid GB/T 32960.3: Historical versions
Similar standardsGB/T 32960.3-2025: Technical specifications for remote service and management system for lectric vehicles - Part 3: Communication protocol and data format---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/GBT32960.3-2025 GB NATIONAL STANDARD OF THE PEOPLE’S REPUBLIC OF CHINA ICS 43.040 CCS T 35 Replacing GB/T 32960.3-2016 Technical specifications for remote service and management system for electric vehicles - Part 3.Communication protocol and data format Issued on: APRIL 25, 2025 Implemented on: NOVEMBER 01, 2025 Issued by. Status Administration for Market Regulation; National Standardization Administration. Table of ContentsForeword... 3 Introduction... 6 1 Scope... 7 2 Normative references... 7 3 Terms and definitions... 8 4 General requirements... 10 5 Communication connection... 10 5.1 Connection establishment... 10 5.2 Information transmission... 11 5.3 Disconnection... 12 5.4 Retransmission mechanism... 12 6 Data packet structure and definition... 13 6.1 Data description... 13 6.2 Data packet structure... 13 6.3 Command unit... 14 6.4 Time... 15 7 Data unit format and definition... 16 7.1 Vehicle login... 16 7.2 Real-time information reporting... 16 7.3 Vehicle logout... 28 7.4 Platform login... 28 7.5 Platform logout... 29 7.6 Data unit encryption key exchange... 29 Appendix A (Normative) Partial field definition... 30 A.1 Gear status definition... 30 A.2 Vehicle static information... 30 Appendix B (Informative) Communication protocol from onboard terminal to platform ... 34 B.2 Information transmission... 34 B.3 Data packet structure and definition... 39ForewordThis 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.IntroductionWith 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 format1 ScopeThis 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 referencesThe contents of the following documents constitute the essential terms of this document through normative references in the text. Among them, for the referenced documents with dates, only the version corresponding to the date applies to this document; for the referenced documents without dates, the latest version (including all amendments) applies to this document. GB/T 1988 Information technology - 7-bit Coded character set for information interchange GB 16735 Road vehicle - Vehicle identification number (VIN) GB 18030 Information technology - Chinese coded character set GB/T 19596 Terminology of electric vehicles GB/T 24548 Fuel cell electric vehicles - Terminology GB/T 28816 Fuel cell - Terminology GB/T 32960.1 Technical specifications of remote service and management system for electric vehicles - Part 1.General principle GB/T 34014 Coding regulation for automotive traction battery GB 38031 Electric vehicles traction battery safety requirements GB/T 40855-2021 Technical requirements and test methods for cybersecurity of remote service and management system for electric vehicles3 Terms and definitionsThe 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 requirements4.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 connection5.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 definition6.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 definition7.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. ......Source: Above contents are excerpted from the full-copy PDF -- translated/reviewed by: www.ChineseStandard.net / Wayne Zheng et al. Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of English version of GB/T 32960.3-2025 be delivered?Answer: The full copy PDF of English version of GB/T 32960.3-2025 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/T 32960.3-2025_English with my colleagues?Answer: Yes. The purchased PDF of GB/T 32960.3-2025_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/T 32960.3-2025 -- 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.Question 5: Should I purchase the latest version GB/T 32960.3-2025?Answer: Yes. Unless special scenarios such as technical constraints or academic study, you should always prioritize to purchase the latest version GB/T 32960.3-2025 even if the enforcement date is in future. Complying with the latest version means that, by default, it also complies with all the earlier versions, technically.How to buy and download a true PDF of English version of GB/T 32960.3-2025?A step-by-step guide to download PDF of GB/T 32960.3-2025_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/T 32960.3-2025". 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 |
