Standard No.:	GB/T 34658-2025
English Name:	Conformance test for communication protocols between off-board conductive charger and battery management system for electric vehicle
Chinese Name:	电动汽车非车载传导式充电机与电池管理系统之间的通信协议一致性测试
Chinese Classification:	K81    AC/DC supply units
Professional Classification:	GB    National Standard
Source Content Issued by:	SAMR; SAC
Issued on:	2025-08-29
Implemented on:	2026-3-1
Status:	to be valid
Superseding:	GB/T 34658-2017 Conformance test for communication protocols between off-board conductive charger and battery management system for electric vehicle
Target Language:	English
File Format:	PDF
Word Count:	105000 words
Translation Price(USD):	3150.0
Delivery:	via email in 1~10 business day

This is a draft translation for reference among interesting stakeholders. The finalized translation (passing through draft translation, self-check, revision and verification) will be delivered upon being ordered. ICS 29.220 CCS K 81 National Standard of the People’s Republic of China GB/T 34658-2025 Replaces GB/T 34658-2017 Conformance test for communication protocols between off-board conductive charger and battery management system for electric vehicle 电动汽车非车载传导式充电机与电池管理系统之间的 通信协议一致性测试 (English Translation) Issue date: 2025-08-29 Implementation date: 2026-03-01 Issued by the State Administration for Market Regulation the Standardization Administration of the People's Republic of China 1 Scope This document specifies the test architecture, test requirements, and test cases for the communication protocol conformance between the electric vehicle supply equipment communication controller (SECC) and the electric vehicle communication controller (EVCC), and defines the test process. This document is applicable to conformance testing of SECCs and EVCCs for systems of Type A and Type B specified in GB/T 27930-2023, and for systems specified in GB/T 27930.2-2024 (hereinafter referred to as "Type C systems"). It is also applicable to conformance testing of communication controllers declared to conform to Type A, Type B, or Type C systems. 2 Normative References The following documents, through their normative citation in the text, constitute indispensable provisions of this document. For dated references, only the edition cited applies. For undated references, the latest edition (including any amendments) applies. GB/T 17178.1-1997 Information technology--Open systems interconnection--Conformance testing methodology and framework--Part 1: General concepts GB/T 18487.1-2023 Electric vehicle conductive charging system--Part 1: General requirements GB/T 18487.5-2024 Electric vehicle conductive charging system--Part 5: DC charging system for GB/T 20234.3 GB/T 27930-2023 Digital communication protocols between off-board conductive charger and electric vehicle GB/T 27930.2-2024 Digital communication protocols between off-board conductive charger and electric vehicle--Part 2: Communication protocols for GB/T 20234.3 3 Terms and Definitions The terms and definitions defined in GB/T 17178.1-1997 and GB/T 27930-2023, as well as the following, apply to this document. 3.1 abstract test case A complete and independent specification of the actions required to achieve a specific test objective, defined at an abstract level for a particular abstract test method, starting and ending in stable test states. [Source: GB/T 17178.1-1997, 3.3.3, modified] 3.2 abstract test suite A test suite composed of abstract test cases. [Source: GB/T 17178.1-1997, 3.3.6] 3.3 implementation under test An implementation of a protocol, having a provider relationship. [Source: GB/T 17178.1-1997, 3.3.43, modified] 3.4 conformance testing Testing the degree to which an implementation under test (IUT) is a conforming implementation. [Source: GB/T 17178.1-1997, 3.3.23] 3.5 executable test case An implementation of an abstract test case. [Source: GB/T 17178.1-1997, 3.3.31] 3.6 executable test suite A test suite composed of executable test cases. [Source: GB/T 17178.1-1997, 3.3.33] 3.7 implementation conformance statement A statement made by the provider of an implementation or system claiming conformance to a given specification, stating which capabilities have been implemented. [Source: GB/T 17178.1-1997, 3.3.39, modified] 3.8 implementation conformance statement proforma A document in the form of a questionnaire which, when completed, is an implementation conformance statement for an implementation or system. [Source: GB/T 17178.1-1997, 3.3.40, modified] 3.9 implementation extra information for testing A statement made by the provider or implementer of the implementation under test (IUT). Note: It contains or references all information (other than that given in the ICS) relevant to the IUT and its test environment, enabling a test laboratory to run the appropriate test suite on the IUT. 3.10 protocol implementation conformance statement An implementation conformance statement for an implementation or system claiming conformance to a given protocol specification. [Source: GB/T 17178.1-1997, 3.3.80] 3.11 protocol implementation extra information for testing Implementation extra information for testing related to conformance testing for a given protocol specification. [Source: GB/T 17178.1-1997, 3.3.81] 3.12 test case An abstract or executable specification. [Source: GB/T 17178.1-1997, 3.3.107, modified] 3.13 test laboratory An organization that performs conformance testing. [Source: GB/T 17178.1-1997, 3.3.113, modified] 4 Abbreviations The following abbreviations apply to this document. BCL: BMS Charging Request Message BCP: BMS Charging Parameter Message BCS: BMS Charging Status Message BEM: BMS Error Message BHM: BMS Handshake Message BMS: Battery Management System BMT: BMS Temperature Information Message BMV: BMS Voltage Information Message BRM: BMS Recognition Message BRO: BMS Readiness Status Message BSD: BMS Statistical Data Message BSM: BMS Status Message BSP: BMS Status Preserved Message BST: BMS Stopping Charging Message CAN: Controller Area Network CCS: Charger Charging Status Message CEM: Charger Error Message CHM: Charger Handshake Message CML: Charger Maximum/Minimum Output Parameter Message CRM: Charger Recognition Message CRO: Charger Readiness Status Message CSD: Charger Statistical Data Message CST: Charger Stopping Charging Message CTS: Charger Time Synchronization Message EVCC: Electric Vehicle Communication Controller ICS: Implementation Conformance Statement IUT: Implementation Under Test PICS: Protocol Implementation Conformance Statement PIXIT: Protocol Implementation Extra Information for Testing SECC: Supply Equipment Communication Controller 5 General Principles 5.1 Test Purpose Protocol conformance testing is conducted to verify whether the IUT meets the requirements of GB/T 27930-2023 or GB/T 27930.2-2024, i.e., to verify the degree of conformity of the IUT's protocol implementation with the standard. 5.2 Test Architecture 5.2.1 Reference Model (Content presumably described elsewhere in original) 5.2.2 Abstract Test Suite The abstract test suite specified in this document is a collection of abstract test cases covering all technical requirements of GB/T 27930-2023 and GB/T 27930.2-2024. 5.2.3 Static Documentation Static documentation includes the PICS and PIXIT. The PICS shall be a statement by the IUT provider of the capabilities implemented by the IUT and the implementation status of options and additional items. The PIXIT shall include all information relevant to the IUT and its test environment (excluding information provided in the PICS). Templates for static documentation for Type A systems are detailed in Appendix A, for Type B systems in Appendix B, and for Type C systems in Appendix C. 5.2.4 Executable Test Suite The test cases specified in this document are abstract test cases. The test laboratory shall, based on the parameters and additional information provided in the static documentation, filter and organize the abstract test cases into executable test cases, and finally combine them into an executable test suite for testing. 5.2.5 Implementation Under Test (IUT) The IUT is a product conforming to the CAN physical layer, data link layer, transport layer (for Type B and Type C systems), and application layer as specified in GB/T 27930-2023 or GB/T 27930.2-2024. The IUTs specified in this document include the SECCs and EVCCs for Type A systems and Type B systems specified in GB/T 27930-2023, and for Type C systems specified in GB/T 27930.2-2024. 5.3 Test Process The protocol conformance testing process is shown in Figure 2. Test preparation includes completing the static documentation and setting up the test system. The PICS and PIXIT documents are completed jointly by the IUT provider and the test laboratory. The test laboratory generates executable test cases based on the content of the static documentation and the abstract test cases specified in this document (see Appendices D, E, F). After test completion, a test report is generated. 5.4 Classification of Test Content Test content includes the following three categories: a) Mandatory Items: Test content declared in the PICS file that the IUT shall possess. Conformance testing shall be performed. b) Optional Items: Test content declared in the PICS file that the IUT may optionally implement. If declared present, conformance testing shall be performed. c) Additional Items: Test content additionally proposed by the IUT provider in the PICS file. Testing is performed upon agreement between the IUT provider and the test laboratory. 5.5 Test Case Numbering Rules The test case number for Type A system protocol conformance testing consists of 4 parts, which shall meet the requirements in Figure 3. The test case number for Type B and Type C system protocol conformance testing consists of 6 parts, connected by "_", and shall meet the rule requirements in Figure 4. Test cases are categorized as: a) Positive Tests: Test cases to verify the IUT's response under ideal communication conditions. b) Negative Tests: Test cases to verify the IUT's response under abnormal communication conditions. Testing should preferably proceed in the order from positive tests to negative tests, and from simple to complex. 5.6 Other Requirements 5.6.1 Communication Message Timing Error Requirements The tolerance requirements for message timeout periods and cycle times in IUT communication shall comply with the specifications in Table 1. Table 1 Communication Message Timing Error Requirements (Content of Table 1 not provided in original text) 5.6.2 Type A System Requirements A Type A system IUT shall meet the following requirements: a) For operations not explicitly specified in GB/T 27930-2023, the IUT's handling method shall meet safety requirements. b) During communication, after the current message meets the stop transmission condition, the IUT shall stop transmitting that message within 500 ms. c) In negative tests, the test system will send messages that do not conform to the definition of a specific message type. The "non-conforming" content shall include message priority, reserved bits, data page, PDU format, destination address, and source address. d) When the IUT receives a message where mandatory parameter values are outside the range defined for the data field, it shall ignore the message content until the message times out. e) When the IUT receives BCP, CML, or BCL messages where the current value is outside the range of -400 A to 0 A, it shall terminate the charging process. 5.6.3 Type B System Requirements A Type B system IUT shall meet the following requirements: a) The charger and vehicle hosting the SECC and EVCC, respectively, shall execute the charging termination process according to the requirements of C.4.9, C.4.10, and C.4.11 in GB/T 18487.1-2023. The termination messages shall comply with the specifications in Table 59 and Table M.3 of GB/T 27930-2023. b) When the IUT receives a message where mandatory parameter values are outside the range defined for the data field, it shall ignore the message content until the message times out. 5.6.4 Type C System Requirements A Type C system IUT shall meet the following requirements: a) During the termination process, the charger and vehicle shall confirm the termination exit method according to Table L.4 in GB/T 27930.2-2024. The corresponding exit method shall be performed according to Appendix K of GB/T 27930.2-2024 and GB/T 18487.5-2024, and shall meet safety requirements. b) During communication, after the current message meets the stop transmission condition, the IUT shall stop transmitting that message within 1 s. 6 Type A System Test Cases 6.1 Physical Layer During information interaction between the test system and the IUT, instruments such as CAN analyzers and oscilloscopes shall be used to capture CAN communication messages. The IUT physical layer shall meet the requirements of Chapter 6 in GB/T 27930-2023. The test cases shall comply with the specifications in Table 2. Table 2 Physical Layer Test Cases 6.2 Data Link Layer During information interaction between the test system and the IUT, the data frame format of messages sent by the IUT shall meet the requirements of Chapter 7 in GB/T 27930-2023. The test cases shall comply with the specifications in Table 3. Table 3 Data Link Layer Test Cases

Contents Foreword ………………………………………………………………………………………………………… Ⅲ Introduction ………………………………………………………………………………………………………… Ⅳ 1 Scope ……………………………………………………………………………………………………… 2 Normative References ………………………………………………………………………………………… 3 Terms and Definitions ……………………………………………………………………………………………… 4 Abbreviations …………………………………………………………………………………………………… 5 General Rules ……………………………………………………………………………………………………… 6 Category A System Test Cases ………………………………………………………………………………………… 7 Category B System Test Cases ………………………………………………………………………………………… 8 Category C System Test Cases ………………………………………………………………………………………… Appendix A (Informative) Static Documentation for Category A System Protocol Conformance Tests ……………………………………………… Appendix B (Informative) Static Documentation for Category B System Protocol Conformance Tests ……………………………………………… Appendix C (Informative) Static Documentation for Category C System Protocol Conformance Tests ……………………………………………… Appendix D (Informative) List of Category A System Test Cases …………………………………………………………… Appendix E (Informative) List of Category B System Test Cases …………………………………………………………… Appendix F (Informative) List of Category C System Test Cases ……………………………………………………………