GB/T 27930-2023 Digital communication protocols between off-board conductive charger and electric vehicle
1 Scope
This document specifies the definitions of and requirements for the physical layer, data link layer, transport layer and application layer of communication based on the controller area network (CAN) between the supply equipment communication controller (SECC) and the electric vehicle communication controller (EVCC) of off-board conductive charger (hereinafter referred to as the "charger").
This document is applicable to the communication between the charger or bi-directional charger in charge mode 4 and the electric vehicle; it is also applicable to the communication between the charger or bi-directional charger and the electronic control unit of the electric vehicle with charging control function. The EVCC includes, but is not limited to, a battery management system (BMS), and an in-vehicle system that is required to communicate with the charger for other special functions.
In this document, Clauses 5–11 are applicable to the charging systems specified in Annex B to GB/T 18487.1-2023 (hereinafter referred to as "Category A systems"), and Clauses 101–106 are applicable to the charging systems specified in Annex C to GB/T 18487.1-2023 as well as the charging and discharging systems defined in Annex E (hereinafter referred to as "Category B systems").
For the purpose of this document, the term "vehicle" refers specifically to "electric vehicle".
2 Normative references
The following documents contain provisions which, through reference in this text, constitute provisions of this document. For dated references, only the edition cited applies. For undated references, the latest edition (including any amendments) applies.
GB/T 18487.1-2023 Electric vehicle conductive charging system - Part 1: General requirements
GB/T 19596 Terminology of electric vehicles
GB/T 29317 Terminology of electric vehicle charging/battery swap infrastructure
GB/T 32960.3-2016 Technical specifications of remote service and management system for electric vehicles - Part 3: Communication protocol and data format
NB/T 10905-2021 Fault classification and code of charging facilities for electric vehicles
SAE J1939-11:2006 Recommended practice for serial control and communication vehicle network - Part 11: Physical layer-250kbits/s, twisted shielded pair
SAE J1939-11:2016 Recommended practice for serial control and communication vehicle network - Part 11: Physical layer-250kbits/s, twisted shielded pair
SAE J1939-15:2018 Recommended practice for serial control and communication vehicle network – Part 15: Physical layer-250kbits/s, un-shielded twisted pair
SAE J1939-21:2006 Recommended practice for serial control and communication vehicle network - Part 21: Data link layer
SAE J1939-21:2021 Recommended practice for serial control and communication vehicle network - Part 21: Data link layer
3 Terms and definitions
For the purposes of this document, the terms and definitions given in GB/T 19596, GB/T 29317 and GB/T 18487.1 and the following apply.
3.1 data link layer
3.1.1
frame
set of data bits constituting a complete message
3.1.2
CAN data frame
ordered bit fields necessary for the CAN protocol for data transport, starting with the start of frame (SOF) and ending with the end of frame (EOF)
3.1.3
CAN message
instance of sending or receiving a parameter group and its parameter data
Note: Sending a message may require interacting with one or more "CAN data frames".
3.1.4
identifier
identity part of the CAN arbitration field
3.1.5
extended frame
CAN data frame that adopts a 29-bit identifier, as defined in the CAN 2.0 B specifications
3.1.6
priority
3-bit field in the identifier that sets the arbitration priority during transport, with Grade 0 as highest priority and Grade 7 as lowest priority
3.1.7
parameter group; PG
set of parameters transported at the application layer
3.1.8
parameter group number; PGN
24-bit value that uniquely identifies a parameter group
Note: A PGN is represented by an extended data page, a data page, the PDU format field, and the PDU specific field.
3.1.9
suspect parameter number; SPN
19-bit value used to identify a specific element, component, or parameter associated with the ECU
3.1.10
protocol data unit; PDU
specific format of the CAN data frame
3.1.11
information frame; IF
CAN data frame used to transmit valid information or data at the data link layer
3.1.12
control frame; CF
CAN data frame at the data link layer for flow control, error management, and acknowledgment of receipt
3.1.13
transport protocol
part of the data link layer, a mechanism for transmitting PGNs with data lengths ranging from 9 bytes to 1785 bytes
3.2 transport layer
3.2.1
multi-information frame transport mode
mode for transporting multiframe data with frame numbers using the automatic repeat request
3.2.2
long message; LM
message with data length greater than 8 bytes, transported by multi-information frame transport mode
3.2.3
short message
message with data length ≤ 8 bytes
3.2.4
reliable message; RM
message transported using the automatic repeat request
Note: Both reliable short and long messages are included.
3.2.5
unreliable message; URM
single frame data without frame number not transmitted using the automatic repeat request
3.3 application layer
3.3.1
parameter group identification; PGI
byte used to uniquely identify a parameter group
3.3.2
function module
business function in the process of energy interaction between the electric vehicle and the charger
3.3.3
mandatory function module
function module necessary for a complete energy interaction process
3.3.4
configurable function module
optional function module in a complete energy interaction process
3.3.5
override function module
function module that can be redefined and replaced
3.3.6
function code; FC
number assigned to the function module
3.3.7
function description code; FDC
number assigned to the function module instance with a specific function
3.3.8
optional item
parameter item can be sent optionally during information interaction
3.3.9
mandatory item
parameter item that must be sent during information interaction
3.4 others
3.4.1
electronic control unit; ECU
control device composed of a microcontroller and a peripheral circuit
Note: An ECU is an on-board computer.
3.4.2
electric vehicle communication controller; EVCC
embedded system inside the electric vehicle for communicating with charging equipment
3.4.3
supply equipment communication controller; SECC
entity for communicating with one or more EVCCs
3.4.4
vehicle adaptor communication controller; VACC
embedded system in a vehicle adapter for communicating with the EVCC and SECC
3.4.5
extended vehicle identification number; EVIN
vehicle identification number (VIN) or a vehicle identification code designed with the letters I, O, or Q to identify the identification information of a vehicle
Foreword I
1 Scope
2 Normative references
3 Terms and definitions
4 Abbreviations
5 General requirements for Category A systems
6 Physical layer of Category A systems
7 Data link layer of Category A systems
8 Application layer of Category A systems
9 General flow of charging for Category A systems
10 Message classification of Category A systems
11 Message format and content of Category A systems
12 General principles for Category B systems
13 Physical layer of Category B systems
14 Data link layer of Category B systems
15 Transport layer of Category B systems
16 Application layer of Category B systems
17 Timeout of Category B systems
Annex A (Normative) Communication flow of Category A systems
Annex B (Informative) Conditions for starting and ending sending messages of Category A systems
Annex C (Normative) Function negotiation function module
Annex D (Normative) Parameter configuration function module
Annex E (Normative) Authentication function module
Annex F (Normative) Schedule function module
Annex G (Normative) System self-check function module
Annex H (Normative) Power supply function module
Annex I (Normative) Precharge and energy transfer function module
Annex J (Normative) Service statistics function module
Annex K (Informative) Implementation of basic charging application scenario
Annex L (Informative) Implementation of bi-directional charging application scenario
Annex M (Normative) Parameter type table
Annex N (Informative) Implementation of adaptor communication
