GB/T 34658: Evolution and historical versions
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/T 34658-2025 | English | RFQ |
ASK
|
3 days [Need to translate]
|
Conformance test for communication protocols between off-board conductive charger and battery management system for electric vehicle
| Valid |
GB/T 34658-2025
|
| GB/T 34658-2017 | English | 285 |
Add to Cart
|
0--9 seconds. Auto-delivery
|
Conformance test for communication protocols between off-board conductive charger and battery management system for electric vehicle
| Valid |
GB/T 34658-2017
|
Basic data | Standard ID | GB/T 34658-2025 (GB/T34658-2025) | | Description (Translated English) | Conformance test for communication protocols between off-board conductive charger and battery management system for electric vehicle | | Sector / Industry | National Standard (Recommended) | | Date of Implementation | 2026-03-01 | | Older Standard (superseded by this standard) | GB/T 34658-2017 | GB/T 34658-2017: Conformance test for communication protocols between off-board conductive charger and battery management system for electric vehicle
---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.
Conformance test for communication protocols between off-board conductive charger and battery management system for electric vehicle
ICS 29.200
K81
National Standards of People's Republic of China
Non-vehicle conduction chargers and battery management for electric vehicles
Communication protocol conformance testing between systems
Published on October 10,.2017
2018-05-01 Implementation
General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China
China National Standardization Administration released
Directory
Preface I
Introduction II
1 Scope 1
2 Normative references 1
3 Terms and Definitions 1
4 Abbreviations 2
5 Conformance Test Requirements 3
6 Conformance Test System 4
7 Conformance test content 5
Appendix A (Normative) Protocol Conformance Test Static Document 30
Foreword
This standard was drafted in accordance with the rules given in GB/T 1.1-2009.
Please note that some of the contents of this document may involve patents. The issuing agency of this document does not assume responsibility for identifying these patents.
This standard is proposed and managed by the China Electricity Council.
This standard is drafted by. State Grid Corporation of China, China Electricity Council, State Grid Electric Power Research Institute, China Automotive Technology Research Institute
Center.
Participated in the drafting of this standard. State Grid Electric Vehicle Service Co., Ltd., XJ Power Co., Ltd., Xuchang Kaipu Detection Technology Co., Ltd.
Division, Shenzhen Aotexun Electric Power Equipment Co., Ltd., China Electric Power Research Institute, Shanghai Electric Apparatus Research Institute, Guangdong Power Grid Co., Ltd.
Company Electric Power Research Institute, Putian New Energy Co., Ltd., Dongfeng Motor Co., Ltd. Dongfeng Nissan Passenger Car Company, State Grid Beijing
Power Company, State Grid Shandong Electric Power Company, BYD Auto Industry Co., Ltd., Nanjing Nengrui Electric Power Technology Co., Ltd., Beijing Qunling Energy
Technology Co., Ltd., Weikai Detection Technology Co., Ltd.
The main drafters of this standard. Shen Jianxin, Liu Yongdong, Li Xuling, Li Xiaoqiang, Yu Bo, Ni Feng, Li Zhiming, Yan Qunfeng, Li Baosen, Xu Wei,
Huang Hao, Ma Jianwei, Ye Jiancheng, Li Hongyan, Lu Guowei, Bai Ou, Wan Xinhang, Li Taoyong, Li Xinqiang, Deng Kai, He Chun, Huang Zhaokun, Zhu Jie, Liu Xiulan,
Li Jianxiang, He Xuefeng, Ma Yanhua, Zhong Yilin, Sun Yibing, Zhang Jinbin.
Introduction
The protocol conformance test is a kind of functional test. It is based on a certain network environment and uses a set of test sequences to implement the tested protocol.
Tests are conducted to determine the degree to which the measured performance is consistent with the description criteria by comparing the actual output with the expected output. by
Protocol conformance testing can reduce the risk of mistakes when the product runs in the field.
During the implementation of the protocol, due to 1) the description of the protocol standard is ambiguous, and there is an ambiguity in the understanding; 2) the programming method and the implementation of the protocol
Different types; 3) Different equipment selection and configuration implemented by protocol, etc. There are certain differences in the implementation of different protocols, so the agreement is consistent.
Sex testing is very necessary.
The protocol conformance test is to detect the existence of errors instead of verifying that there is no error, relying on the consistency test alone does not absolutely guarantee that
The interconnection and interoperability used should be based on this and carry out corresponding interoperability tests.
Protocol conformance testing is the basis of interoperability testing. Only products that pass the protocol conformance test indicate that they meet the relevant protocol targets.
Quasi-required, it makes sense to conduct interoperability testing.
The protocol conformance test does not include the design evaluation of the protocol standard itself, nor does it include the performance and redundancy of the implementation body of the specific protocol.
Degree, robustness and reliability assessment content.
Non-vehicle conduction chargers and battery management for electric vehicles
Communication protocol conformance testing between systems
1 Scope
This standard stipulates non-vehicle conduction type chargers (hereinafter referred to as chargers) and battery management systems (hereinafter referred to as BMS) for electric vehicles.
Communication protocol conformance testing requirements, conformance testing systems, and conformance testing content.
This standard applies to protocol conformance testing of products declared to comply with GB/T 27930-2015.
2 Normative references
The following documents are indispensable for the application of this document. For dated references, only dated versions apply to this article
Pieces. For undated references, the latest version (including all amendments) applies to this document.
GB/T 17178.1-1997 Information technology open system interconnection conformance testing method and framework Part 1. Basic concepts
GB/T 27930-2015 Communication protocol between non-vehicle conduction charger and battery management system for electric vehicles
3 Terms and Definitions
The terms and definitions defined in GB/T 17178.1-1997 and the following terms apply to this document.
3.1
Abstract test case abstracttestcase
Defined at the level of abstraction of a particular abstract test method, a complete and independent action required to obtain special test purposes
The specification. It starts and ends in a stable test state.
[GB/T 17178.1-1997, definition 3.3.3]
3.2
Abstract test suite abstracttestsuite;ATS
A test suite consisting of abstract test cases.
[GB/T 17178.1-1997, definition 3.3.6]
3.3
Measured to achieve implementationundertest;IUT
An implementation of a protocol with a provider relationship.
Note. Rewrite GB/T 17178.1-1997, definition 3.3.43.
3.4
Conformance testing
The test IUT is the degree to which a consistent implementation has been achieved.
[GB/T 17178.1-1997, definition 3.3.23]
3.5
Executable test case executabletestcase
Abstract test case implementation.
[GB/T 17178.1-1997, definition 3.3.31]
3.6
Executable test suite executabletestsuite;ETS
A test suite consisting of executable test cases.
[GB/T 17178.1-1997, definition 3.3.33]
3.7
Implementation Conformance Statement implementationconformancestatement;ICS
Statements made by providers who claim to be in compliance with the given specification or system, state what capabilities have been achieved.
[GB/T 17178.1-1997, definition 3.3.39]
3.8
Implementation Conformance Statement [ICS] Formal Table implementationconformancestatement[ICS]proforma
Documents that appear as questionnaires become ICS when completed for an implementation or system.
[GB/T 17178.1-1997, definition 3.3.40]
3.9
Test implementation additional information implementationextrainformationfortesting;IXIT
Statement made by the provider or implementer of the IUT, which includes or references all information related to the IUT and its test environment
(Except for the information given by the ICS), this statement allows the test laboratory to run the appropriate test suite for the IUT.
[GB/T 17178.1-1997, definition 3.3.41]
3.10
Test Implementation Additional Information [IXIT] Form Table implementation extrainformationfortesting[IXIT]proforma
Documents that appear as questionnaires become IXIT when completed for an IUT.
[GB/T 17178.1-1997, definition 3.3.42]
3.11
Protocol Implementation Conformance Statement protocolimplementationconformancestatement;PICS
ICS that claims an implementation or system consistent with a given protocol specification.
[GB/T 17178.1-1997, definition 3.3.80]
3.12
Test protocol implementation additional information protocolimplementationextrainformationfortesting;PIXIT
IXIT related to conformance testing for a given protocol specification.
[GB/T 17178.1-1997, definition 3.3.81]
3.13
Test case testcase
Abstract or executable test case.
[GB/T 17178.1-1997, definition 3.3.107]
3.14
Test laboratory
Institution performing compliance testing.
4 Abbreviations
The following abbreviations apply to this document.
ATS. abstract testcase
BCL. BMS charging request message (BMS charging request message)
BCP. BMS charging parameter message (BMS charging parameter message)
BCS. BMS charging status message (BMS charging status message)
BEM. BMS error message (BMS error message)
BHM. Vehicle handshake message (BMS handshake message)
BMS. battery management system (battery management system)
BMT. BMS temperature information message
BMV. BMS voltage integration message
BRM.BMS and Vehicle Identification Messages (BMSrecognitionmessage)
BRO. BMSreadiness status message (BMSreadiness status message)
BSD. BMS statistics data message (BMS statistics data message)
BSM. BMS status message (BMS status message)
BSP. BMSstatuspreservedmessage
BST. BMS stopping charging message (BMSstoppingchargingmessage)
CCS. chargerchargingstatusmessage
CEM. Charger error message (charger error message)
CHM. Charger handshake message (charger handshake message)
CML. Charger maximum/minimum output parameter message
CRM. chargerrecognitionmessage
CRO. charger readiness status message (chargerreadiness status message)
CSD. Charger statistics data message (charger statistics data message)
CST. chargers chargingchargingmessage
CTS. charger time synchronization message (chargertimesynchronizationmessage)
ETS. Executable test suite (executable test suite)
ICS. Implementation Conformance Statement
IUT. Implemented under test (implementation undertest)
IXIT. test implementation additional information (implementationextrainformationfortesting)
PICS. Protocol Implementation Conformance Statement (protocol implementation conformance statement)
PIXIT. test protocol implementation additional information (protocolimplementationextrainformationfortesting)
5 Conformance test requirements
5.1 Overview
This standard is to verify whether IUT meets the requirements of GB/T 27930-2015, that is, to verify the conformity of IUT with the standard in the implementation of the protocol.
degree.
5.2 Test Procedure
The entire test process is shown in Figure 1. Preparations for testing include filling in static documents, building test systems, and so on. PICS files and PIXIT
The document was completed by the IUT provider and test lab. After confirming that all devices are normally started, you can turn on the upper computer to test the software.
Parts for follow-up test operations. After the test is completed, a test report is generated and the test conclusion is drawn.
Figure 1 Protocol Conformance Test Procedure
5.3 Test Content Classification
The test content is classified as follows.
a) Must
The mandatory item is to declare the test content that the IUT must possess in the PICS file, and a conformance test should be conducted.
b) Options
The optional option is to declare the IUT optional test content in the PICS file. If there is a statement of the test content, it should be consistent.
Sex test.
c) Additional items
Additional items are additional test content provided by the IUT provider in the PICS file, through IUT providers and test labs
Make a test.
6 Conformance Test System
6.1 Overview
The structure of the communication protocol conformance test system is shown in Figure 2.
Figure 2 Protocol Conformance Test System Architecture
6.2 Abstract Test Suite
Write test objectives according to the technical requirements of the protocol standards, form abstract test cases, and abstract tests covering all technical requirements of the protocol standards
The collection of cases constitutes an abstract test suite.
6.3 Static Documents
Static documents include PICS and PIXIT. PICS shall be provided by the IUT provider stating that the IUT's achieved capabilities and options have been fulfilled
The PIXIT should include all information related to the IUT and its test environment (except for information given by the PICS), as detailed in Table A.1, Table A.2.
6.4 Executable Test Suite
Executable test suites consist of executable test cases. Executable test cases are implementations of abstract test cases. According to the static document provided by the Ministry
With the subparameters and additional information, the test laboratory can sort abstract test cases into executable test cases, and finally combine them into executable test cases.
carry out testing.
6.5 Tested to achieve
The measured implementation is a CAN physical layer, data link layer, and application layer product that meets the requirements of GB/T 27930-2015.
The IUTs referred to in this standard mainly include non-vehicle chargers (or controllers) and BMSs that use conductive charging methods.
Electric control functions of other vehicle control units) etc.
7 Conformance test content
7.1 Test Case Encoding Rules
The coding rules of the communication protocol conformance test items are shown in Figure 3.
Figure 3 coding rules for test cases
The test cases are divided into.
a) Positive test. In order to verify the IUT response under ideal communication conditions;
b) Negative test. In order to verify the response of the IUT in abnormal communication state.
Tests are conducted from simple tests to negative tests, from simple to complex tests.
Note. The IUT receives packets whose message types, message contents, and message lengths do not match the standard definition and does not require immediate downtime.
7.2 Test Message Time Error Requirements
The IUT periodically sends messages during the communication process and receives the other party's messages at the same time. If the IUT receives no messages from the other party within the timeout period,
If the correct message is not received, it will be judged to time out and send an error message. Table 1 shows the packet timeout time and cycle time error requirements.
Table 1 packet time error requirements
Parameter nominal value t Error range
Packet timeout
1s 0.2s
5s 0.5s
≥10s 3s
Packet cycle time
10ms ±3ms
≥50ms ± (t×10%)ms
7.3 Other requirements
Other requirements are as follows.
a) In the operation not specified in GB/T 27930-2015, the IUT's handling should meet the safety requirements;
b) In the process of communication, after the current message reaches the suspension of the transmission condition, the IUT shall stop sending the message within 500ms;
c) In the negative test, the test system will send a message that does not match the definition of a certain message type. The content of the "disagreement" includes message priority.
Level, reserved bit, data page, PDU format, destination address, and source address.
7.4 BMS Test Cases
7.4.1 Low Voltage Auxiliary Power Up and Charge Handshake Phase
The test system simulates the communication logic of the charger and the measured BMS performs the information exchange. Low voltage assisted power-on and charge handshaking phases
The test case is shown in Table 2. The test mainly focuses on the communication logic, BHM message and BRM message at this stage.
Table 2 BMS Test Cases - Low Voltage Auxiliary Power Up and Charge Handshake Phase
Test case number BP.1001
Preconditions
(1) The CAN communication rate of the test system and the BMS is set to 250 kbit/s;
(2) The physical connection between the test system and the BMS is completed and locked;
(3) Test system low-voltage auxiliary power circuit contactor K3K4 closed
Test step expected result
The test system sends CHM messages in a period of 250ms.
The format, content and cycle are in line with GB/T 27930-2015 9.1
And 10.1.1 requirements
After the BMS receives the CHM message, it sends it in a 250ms cycle.
BHM message, SPN2601 is the maximum allowable charge for BMS
Pressure, message format, content and cycle in line with GB/T 27930-2015
In the requirements of 9.1 and 10.1.2, the length of the message is 2 bytes.
Table 2 (continued)
Test Case Number BP.1002
Precondition 1
) Test system and BMS complete handshake confirmation;
2) Test system completes insulation monitoring
Test step expected result
The test system stops sending CHM messages according to a period of 250ms.
Send CRM message, SPN2560=0x00, message format, internal
The volume and cycle are in accordance with 9.1 and 10.1.3 of GB/T 27930-2015
Requirements
1) The BMS received the CRM message with SPN2560=0x00
After that, stop sending BHM messages;
2) The BMS uses the transmission protocol function to send BRM messages.
The format, content and cycle are in line with GB/T 27930-2015 9.1
With the requirement of 10.1.4, the message length is 49 bytes
Test case number BP.1003
Precondition test system receives BRM packets
Test step expected result
The test system sends SPN2560=0xAA in a 250ms cycle
CRM message, format, content and cycle of the message comply with GB/T
Requirements of 9.1 and 10.1.3 in 27930-2015
1) BMS receives CRM message with SPN2560=0xAA
After that, stop sending BRM messages;
2) Enter the configuration stage communication process
Test Case No. BN.1001
Preconditions
1) The CAN communication speed of the test system and BMS is set to 250 kbit/s;
2) The physical connection between the test system and the BMS is completed and locked;
3) Test system low-voltage auxiliary power circuit contactor K3K4 closed
Test step expected result
The test system does not send messages and does not start insulation monitoring. 1) The BMS does not send anything within 60 seconds after it is started from the BMS system.
Message
2) For more than 60s, the BMS sends a BEM report with SPN3901=01
Text, message format, content and period are in line with GB/T 27930-
2015 9.5 and 10.5.1 requirements
Test Case No. BN.1002
Preconditions
1) The CAN communication speed of the test system and BMS is set to 250 kbit/s;
2) The physical connection between the test system and the BMS is completed and locked;
3) Test system low-voltage auxiliary power circuit contactor K3K4 closed
Test step expected result
The test system sends a report that does not match the definition of the CHM message type
Text, and does not start insulation monitoring
1) The BMS does not send anything within 60 seconds from the start of the BMS system
Message
2) For more than 60s, the BMS sends a BEM report with SPN3901=01
Text, message format, content and period are in line with GB/T 27930-
2015 9.5 and 10.5.1 requirements
Table 2 (continued)
Test Case No. BN.1003
Precondition 1
) Test system and BMS complete handshake confirmation;
2) Test system completes insulation monitoring
Test step expected result
The test system stops sending packets. 1) Within 30 s since the first time the CHM packet was received, the BMS presses
Send a BHM message in a period of 250ms.
2) For more than 30s, the BMS sends a BEM report with SPN3901=01
Text, message format, content and period are in line with GB/T 27930-
2015 9.5 and 10.5.1 requirements
Test Case No. BN.1004
Precondition 1
) Test system and BMS complete handshake confirmation;
2) Test system completes insulation monitoring
Test step expected result
The test system sends a CRM message class with a period of 250ms
Type mismatched packets
1) Within 30s after receiving the CHM message for the first time, the BMS presses
Send a BHM message in a period of 250ms.
2) For more than 30s, the BMS sends a BEM report with SPN3901=01
Text, message format, content and period are in line with GB/T 27930-
2015 9.5 and 10.5.1 requirements
Test Case No. BN.1005
Precondition 1
) Test system and BMS complete handshake confirmation;
2) Test system completes insulation monitoring
Test step expected result
The test system sends CRM messages in a 250 ms cycle.
SPN2560 ≠ 0x00
1) Within 30s after receiving the CHM message for the first time, the BMS presses
Send a BHM message in a period of 250ms.
2) For more than 30s, the BMS sends a BEM report with SPN3901=01
Text, message format, content and period are in line with GB/T 27930-
2015 9.5 and 10.5.1 requirements
Test Case No. BN.1006
Precondition 1
) Test system and BMS complete handshake confirmation;
2) Test system completes insulation monitoring
Test step expected result
The test system continues to send CHM messages in a 250ms cycle.
The format, content and cycle of the message comply with GB/T 27930-2015
The requirements of 9.1 and 10.1.1
1) Within 30s after receiving the CHM message for the first time, the BMS presses
Send a BHM message in a period of 250ms.
2) For more than 30s, the BMS sends a BEM report with SPN3901=01
Text, message format, content and period are in line with GB/T 27930-
2015 9.5 and 10.5.1 requirements
Test Case No. BN.1007
Precondition test system receives BRM packets
Table 2 (continued)
Test step expected result
The test system stops sending messages 1) The BMS presses 250ms within 5s from the first BRM message is sent
The period of sending BRM messages;
2) BMS sends BEM report with SPN3902=01 for more than 5s
Text, message format, content and period are in line with GB/T 27930-
2015 9.5 and 10.5.1 requirements
Test Case No. BN.1008
Precondition test system receives BRM packets
Test step expected result
The test system sends a CRM message class with a period of 250ms
Type mismatched packets
1) Within 5s from the first sending of the BRM message, the BMS presses 250ms
The period of sending BRM messages;
2) BMS sends BEM report with SPN3902=01 for more than 5s
Text, message format, content and period are in line with GB/T 27930-
2015 9.5 and 10.5.1 requirements
Test Case No. BN.1009
Precondition test system receives BRM packets
Test step expected result
The test system sends CRM messages in a 250 ms cycle.
SPN2560≠0xAA and SPN2560≠0x00
1) Within 5s from the first sending of the BRM message, the BMS presses 250ms
The period of sending BRM messages;
2) BMS sends BEM report with SPN3902=01 for more than 5s
Text, message format, content and period are in line with GB/T 27930-
2015 9.5 and 10.5.1 requirements
Test Case No. BN.1010
Precondition test system receives BRM packets
Test step expected result
The test system continues to send SPN2560 = 250ms
0x00 CRM messages
1) Within 5s from the first sending of the BRM message, the BMS presses 250ms
The period of sending BRM messages;
2) BMS sends BEM report with SPN3902=01 for more than 5s
Text, message format, content and period are in line with GB/T 27930-
2015 9.5 and 10.5.1 requirements
7.4.2 Charging Parameter Configuration Stage
Table 3 shows the test cases of the charging parameter configuration stage. The test is mainly focused on the communication logic, BCP packets, and BRO packets at this stage.
Table 3 BMS Test Case - Charging Parameters Configuration Phase
Test Case No. BP.2001
Preconditions The charge handshake phase is completed. The test system and BMS enter the charge parameter configuration phase.
Test step expected result
The test system sends SPN2560 = 250 ms period
0xAA CRM messages
1) The BMS receives the CRM message with SPN2560=0xAA.
Stop sending BRM messages.
2) The BMS uses the transmission protocol function to send BCP packets.
The format, content and cycle are in accordance with 9.2 of GB/T 27930-2015
With the requirements of 10.2.1, the message length is 13 bytes
Test Case No. BP.2002
Precondition test system receives completed BCP packets
Test step expected result
The test system sends CML messages in a 250ms cycle.
500 ms period to send CTS packets (optional), packet format
Formula, content and cycle are in accordance with 9.2 of GB/T 27930-2015
And the requirements of 10.2.2 and 10.2.3
1) The BMS stops sending BCP packets;
2) The BMS sends BRO messages in a period of 250ms, K5K6
Before closing, SPN2829=0x00; after K5K6 is closed, SPN2829=
0xAA, and before stopping sending BRO messages SPN2829=
0xAA remains unchanged, the format, content and period of the message comply with GB/T
Requirements of 9.2 and 10.2.4 in 27930-2015, the length of the message is
1 byte
Test case number BP.2003
Precondition test system receives BRO packets with SPN2829=0xAA
Test step expected result
The test system closes K1K2 and sends SPNs in a 250ms cycle
2830=0xAA CRO message, packet format, content, and period
Meet the requirements of 9.2 and 10.2.5 of GB/T 27930-2015
1) The BMS stops sending BRO messages;
2) Into charge phase communication process
Test Case No. BN.2001
Precondition test system receives completed BCP packets
Test step expected result
The test system stops sending packets 1) The BMS presses 500ms ...
|