HOME   Cart(0)   Quotation   About-Us Tax PDFs Standard-List Powered by Google www.ChineseStandard.net Database: 189760 (7 Dec 2024)

GB/T 32960.3-2016 English PDF

GB/T 32960.3-2016 (GB/T32960.3-2016, GBT 32960.3-2016, GBT32960.3-2016)
Standard IDContents [version]USDSTEP2[PDF] delivered inStandard Title (Description)StatusPDF
GB/T 32960.3-2016English145 Add to Cart 0--9 seconds. Auto-delivery Technical specifications of remote service and management system for electric vehicles -- Part 3: Communication protocol and data format Valid GB/T 32960.3-2016
Preview PDF: GB/T 32960.3-2016

BASIC DATA
Standard ID GB/T 32960.3-2016 (GB/T32960.3-2016)
Description (Translated English) Technical specifications of remote service and management system for electric vehicles -- Part 3: Communication protocol and data format
Sector / Industry National Standard (Recommended)
Classification of Chinese Standard T35
Classification of International Standard 43.040.99
Word Count Estimation 32,348
Date of Issue 2016-08-29
Date of Implementation 2016-10-01
Drafting Organization Ltd., Beijing Science and Technology University, China Automotive Technology and Research Center, Shanghai Automotive Group Co., Ltd., Neusoft Group Co., Ltd., Wuhan Intest Electronic Technology Co., Ltd., Beijing Institute of Information Technology Co., Ltd., Shanghai International Automobile City Group Co., Ltd., BYD Auto Industry Co., Ltd., Zhengzhou Yutong Bus Co., Ltd., Nantong Che-hung Hu Information Technology Co., Ltd., Brilliance Automotive Group Holdings Limited, Beijing Product Quality Supervision and Inspection Institute, Shenzhen BYD Dai Ltd., Beijing Automotive Research Institute Co., Ltd., Chongqing Changan New Energy Automobile Co., Ltd., Beijing New Energy Vehicle Co., Ltd., Shanghai Ying Shi Automotive Technology Co., Ltd., Zhejiang Geely Automobile Research Institute Co., Ltd.,
Administrative Organization National Automotive Standardization Technical Committee (SAC/TC 114)
Regulation (derived from) National Standard Announcement 2016 No.14
Proposing organization Ministry of Industry and Information Technology of the People Republic of China
Issuing agency(ies) General Administration of Quality Supervision, Inspection and Quarantine of the People Republic of China, Standardization Administration of the People Republic of China


GB/T 32960.3-2016 GB NATIONAL STANDARD OF THE PEOPLE’S REPUBLIC OF CHINA ICS 43.040.99 T 35 Technical specifications of remote service and management system for electric vehicles - Part 3. Communication protocol and data format ISSUED ON. AUGUST 29, 2016 IMPLEMENTED ON. OCTOBER 1, 2016 Issued by. General Administration of Quality Supervision, Inspection and Quarantine; Standardization Administration Committee. Table of Contents Foreword ... 3  1 Scope ... 5  2 Normative references ... 5  3 Terms and definitions ... 5  4 General requirements ... 7  5 Communication connection ... 7  6 Structure and definition of data packet ... 10  7 Format and definition of data unit ... 12  Annex A (Normative) Definitions of some fields ... 24  Annex B (Informative) Vehicle-to-platform communication protocol ... 26  Foreword GB/T 32960 Technical specifications of remote service and management system for electric vehicles - Part 3. Communication protocol and data format consists of three parts. - Part 1. General Principle; - Part 2. On-board Terminal; - Part 3. Communication protocol and data format. This Part is the third part of GB/T 32960. This Part was drafted in accordance with the rules given in GB/T 1.1-2009. This Part was proposed by Ministry of Industry and Information Technology of China. This Part shall be under the jurisdiction of National Technical Committee on Automobile of Standardization Administration of China (SAC/TC114). The drafting organizations of this Part. Beijing Institute of Technology, China Automotive Technology and Research Center, Shanghai Automotive Group Co., Ltd., Neusoft Group Co., Ltd., Wuhan Intest Electronic Technology Co., Ltd., Beijing Institute of Technology New Source Information Technology Co., Ltd., Shanghai International Automobile City Group Co., Ltd., Putian New Energy Co., Ltd., Huawei Technologies Co., Ltd., BYD Auto Industry Co., Ltd., Zhengzhou Yutong Bus Co., Ltd., Nantong Honghu Information Technology Co., Ltd., Brilliance Automotive Group Holdings Limited, Beijing Product Quality Supervision and Inspection Institute, Shenzhen BYD Daimler New Technology Co., Ltd., Beijing Automotive Research Institute Co., Ltd., Chongqing Changan New Energy Automobile Co., Ltd., Beijing New Energy Vehicle Co., Ltd., Shanghai Ying Shi Automotive Technology Co., Ltd., Zhejiang Geely Automobile Research Institute Co., Ltd., Wuhan Electric Vehicle Technology Development Co., Ltd., Pan Asia Automotive Technology Center Co., Ltd., SAIC-GM-Wuling Automobile Co., Ltd., Guangzhou Toyota Motor Co., Ltd., SAIC Volkswagen Automotive Company Limited, FAW-Volkswagen Automotive Company Limited, Southeast (Fujian) Automotive Industry Co., Ltd. Main Drafters of this Part. Wang Zhenpo, Zhou Rong, Liu Peng, Pu Jinhuan, Long Chaohua, Lu Chun, Hou Yi, Meng Xiangfeng, Chen Hanjun, Wang Lei, Mi Feng, Ding Xiaohua, Wu Zhiqiang, Fu Jing, Liu Kai, Liu Yongjun, Jiang Feng, Lv Shujun, Wu Lihua, Zhao Yatao, Shan Chong, Zhang Wenjie, Guan Pengshu, Wang Xu, Zhu Junjun, Wang Wenyang, Yang Xiantao, Xu Duo, Gao Xianfeng, Peng Yonglun, Hu Fangfang, Yang Yang, Xiong Xiaofei, Huang Zhicheng, Yu Technical specifications of remote service and management system for electric vehicles - Part 3. Communication protocol and data format 1 Scope This Part of GB/T 32960 specifies the protocol structure, communication connection, data packet structure and definition, data unit format and definition in the electric vehicle remote service and management system. This Part is applicable to communication between platforms in electric vehicle remote service and management system. Car-borne terminal to platform transmission should refer to the implementation. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. GB/T 1988, Information technology - 7-bit Coded character set for information interchange; GB 16735, Road vehicles - Vehicle identification number(VIN) - Location and attachment; GB 18030, Information technology - Chinese coded character set; GB/T 19596, Terminology of electric vehicles; GB/T 32960.1, Technical specification for electric vehicle remote service and management system - Part 1. General. 3 Terms and definitions For the purposes of this document, the terms and definitions defined in GB/T 19596, GB/T 32960.1 AND the following ones apply. 3.1 client platform used as remote service and management platform of vehicle data sender during data exchange between platforms 3.2 server platform used as remote service and management platform of vehicle data receiver during data exchange between platforms 3.3 register the process of which the client platform provides platform and vehicle static information to the server platform, used for platform and vehicle identification NOTE See A.2 of Annex A for the definition of vehicle static information. 3.4 upstream data transmission direction from the client to the server 3.5 downstream data transmission direction from the server to the client 3.6 vehicle login login authentication before the client reports the vehicle status information to the server 3.7 vehicle logout the client confirms to the server that the vehicle data normally stops transmitting and logs out from the platform 3.8 platform login safety certification before the client platform reports the vehicle status information to the server platform 3.9 platform logout the client platform stops data transmission and logs out from the server platform for some reason 3.10 encryption the process of data transmission to encode the password 3.11 deciphering the process of deciphering after the platform receives data server platform should check the received data. When the check is correct, the server platform shall do the correct response. When the check is wrong, the server platform shall do the wrong response. When the information response of the server platform is wrong, the client should re-send the real-time information of the vehicle. It shall re-send every 1 min interval but shall not send after three times of failure. 5.2.3 When the client platform reports information to the server platform, it shall complete the assembly of the following data in accordance with 7.2.3. drive motor data, vehicle data, fuel cell data, engine data, vehicle position data, extreme data, alarm data before reporting. When there are platform exchange data and user-defined data, it shall also report the platform exchange data and user-defined data. 5.2.4 The time period in which the client platform reports information to the server platform should be adjustable. The maximum time period of vehicle information report shall not exceed 30s. When vehicle has the three-level alarm of Table 17, it shall report the data 30s before and after the time point of failure. And the information sampling period shall not exceed 1s. The data should be transmitted in the form of re-reporting before the fault occurs. 5.2.5 When the data sent by terminal is encrypted, the client platform shall conduct data deciphering first then re-encrypt it and send to the server platform. There shall be no need to re-encrypt for inter-platform transmission if there is no encryption requirement. 5.3 Report of statistics information The statistics information should be transmitted to the server platform in the form of FTP, HTTP, or HTTPS. 5.4 Connection disconnected The server platform should disconnect the session with the client platform based on the following conditions. - TCP connection is interrupted. The client platform should disconnect the session with the server platform based on the following conditions. - TCP connection is interrupted; - TCP connection is normal. After the number of retries is reached, no response is received. 5.5 Replacement mechanism is transmitted, it shall use the unique self-defined encoding. 21 Data unit encryption mode BYTE 0x01. data is not encrypted; 0x02. data is encrypted by the RSA algorithm; 0x03. data is encrypted by the AES128 bit algorithm; "0xFE" for exception, "0xFF" for invalid, others are reserved 22 Data unit length WORD The data unit length is the total number of bytes of the data unit of which the valid value range is 0 ~ 24 Data unit - See Clause 7 for the format and definition of data unit The penultimate bit Verification code BYTE Use the BCC (XOR) method. The verification range starts from the first byte of the command unit and is exclusive with the next byte until the previous byte of the verification code. The verification code occupies one byte. When the data unit is encrypted, it should be encrypted before verification, decryption after verification. 6.3 Command unit 6.3.1 Command marks The command marks shall be the unique identifier of the initiator. The definitions o... ......