GB/T 27930-2023 PDF English
US$1805.00 · In stock · Download in 9 secondsGB/T 27930-2023: Digital communication protocols between off-board conductive charger and electric vehicle Delivery: 9 seconds. True-PDF full-copy in English & invoice will be downloaded + auto-delivered via email. See step-by-step procedureStatus: Valid GB/T 27930: Evolution and historical versions
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivery | Name of Chinese Standard | Status |
| GB/T 27930-2023 | English | 1805 |
Add to Cart
|
0-9 seconds. Auto-delivery
|
Digital communication protocols between off-board conductive charger and electric vehicle
| Valid |
| GB/T 27930-2015 | English | 735 |
Add to Cart
|
0-9 seconds. Auto-delivery
|
Communication protocols between off-board conductive charger and battery management system for electric vehicle
| Obsolete |
| GB/T 27930-2011 | English | 450 |
Add to Cart
|
0-9 seconds. Auto-delivery
|
Communication protocols between off-board conductive charger and battery management system for electric vehicle
| Obsolete |
Excerpted PDFs (Download full copy in 9 seconds upon purchase)PDF Preview: GB/T 27930-2023
GB/T 27930-2023: Digital communication protocols between off-board conductive charger and electric vehicle
---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/GBT27930-2023
GB
NATIONAL STANDARD OF THE
PEOPLE’S REPUBLIC OF CHINA
ICS 29.200
CCS K 81
Replacing GB/T 27930-2015
Digital communication protocols between off-board
conductive charger and electric vehicle
Issued on. SEPTEMBER 07, 2023
Implemented on. APRIL 01, 2024
Issued by. Status Administration for Market Regulation.
Standardization Administration of PRC.
Table of Contents
Foreword... 4
1 Scope... 7
2 Normative references... 7
3 Terms and definitions... 8
4 Abbreviations... 13
5 General principles of category A systems... 13
6 Category A system physical layer... 14
7 Category A system data link layer... 14
8 Category A system application layer... 15
9 Overall charging process of category A system... 16
10 Message classification of category A system... 17
11 Message format and content of category A system... 20
12 General principles of category B systems... 37
13 Physical layer of category B system... 39
14 Data link layer of category B system... 39
15 Transport layer of category B system... 48
16 Application layer of category B system... 62
17 Timeout of category B system... 69
Appendix A (Normative) Communication process of category A system... 70
Appendix B (Informative) Start sending conditions and end sending conditions of
category A system message... 79
Appendix C (Normative) Function negotiation function module... 81
Appendix D (Normative) Parameter configuration function module... 87
Appendix E (Normative) Authentication function module... 93
Appendix F (Normative) Reservation function module... 104
Appendix G (Normative) System self-check function module... 117
Appendix H (Normative) Power supply mode function module... 123
Appendix I (Normative) Precharge and energy transfer function module... 137
Appendix J (Normative) Service statistics function module... 160
Appendix K (Informative) Realization of basic charging application scenarios... 163
Appendix L (Informative) Realization of charging & discharging application scenarios
Digital communication protocols between off-board
conductive charger and electric vehicle
1 Scope
This document specifies the definitions and requirements of the controller area network
(CAN)-based communication physical layer, data link layer, transport layer, application
layer, between the off-board conductive charger's (hereinafter referred to as "charger")
equipment communication controller (SECC) and electric vehicle communication
controller (EVCC).
This document applies to the communication -- between the charger or the charger &
discharger using charging mode 4 and the electric vehicle. It also applies to the
communication -- between the charger or charger & discharger and the electronic
control unit of the electric vehicle with charging control function. Electric vehicle
communication controllers include but are not limited to battery management systems
(BMS), as well as in-vehicle systems that need to communicate with the charger to
achieve other special functions.
Chapters 5 ~ 11 of this document apply to the charging system, which is specified in
Appendix B of GB/T 18487.1-2023 (hereinafter referred to as “category A system").
Chapters 101 ~ 106 apply to the charging system, which is specified in Appendix C of
GB/T 18487.1-2023, as well as the charging & discharging system, which is defined in
Appendix E (hereinafter referred to as "category B system").
"Vehicle" in this document specifically refers to “electric vehicle”.
2 Normative references
The contents of the following documents constitute essential provisions of this
document through normative references in the text. Among them, for dated reference
documents, only the version corresponding to the date applies to this document; for
undated reference documents, the latest version (including all amendments) applies to
this document.
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
3 Terms and definitions
The terms and definitions. as defined in GB/T 19596, GB/T 29317, GB/T 18487.1, as
well as the following terms and definitions, apply to this document.
3.1 Data link layer
3.1.1
Frame
A series of data bits that make up a complete message.
3.1.2
CAN data frame
An ordered bit field, which is necessary for the CAN protocol used to transmit data,
starting with the start of frame (SOF) and ending with the end of the frame (EOF).
3.1.3
CAN message
Sends or receives an instance of a parameter group and its parameter data.
Note. The sending of a message may require the exchange of one or more "CAN data
4 Abbreviations
The following abbreviations apply to this document.
LM_ACK. Long message acknowledgement
LM_EndofACK. Long message end of acknowledge
LM_NACK. Long message negative acknowledge
RM_SM_ACK. Reliable short message acknowledge
5 General principles of category A systems
5.1 The communication network between the charger and the vehicle is based on
CAN2.0B.
5.2 The CAN communication network, between the charger and the vehicle, shall be
composed of two nodes. the charger and the vehicle. In order to achieve the
compatibility solution of Appendix G of GB/T 18487.1-2023, adaptor nodes can be
added to the communication network; however, between each node, there shall be no
conflicts in addresses, PGNs, etc.
5.3 Data information transmission adopts the format of low byte sent first.
5.4 The current value during vehicle charging is negative. In public stations, when the
vehicle/charger receives a charging current value, which is outside the range of -400 A
~ 0 A, the charging process shall be exited. In private stations, the charger and vehicle
can be subject to the negotiation, according to private agreement.
5.5 In public stations, messages not specified in this document shall not appear on the
communication network, between chargers and vehicles. Messages, which are not
specified in this document and received by the charger or vehicle, will not be processed.
5.6 The conversion relationship between the data value and the physical quantity in the
message is. physical quantity = Resolution × Data value + Offset.
5.7 Chargers and vehicles, that implement this document, shall have forward
compatibility.
6 Category A system physical layer
The CAN communication bus network's physical layer, which is used in this document,
shall comply with the requirements in SAE J1939-11.2006 or SAE J1939-15.2018.In
this document, the communication between the charger and the vehicle shall use an
independent CAN bus; the communication rate between the charger and the vehicle
adopts 250 kbit/s. The shielded twisted pair shall meet the requirements of Table 7 in
SAE J1939-11.2006; the unshielded twisted pair shall meet the requirements of Table
2 in SAE J1939-11.2006; the terminal resistance shall meet the requirements of 5.2.3
in SAE J1939-11.2006.
Note. In special occasions with harsh communication environments (such as commercial
vehicle charging stations with long communication distances), the communication rate of 50
kbit/s is adopted, after agreement between the equipment manufacturer and the vehicle
manufacturer.
7 Category A system data link layer
7.1 Frame format
Equipment using this document shall use the 29-bit identifier of the CAN extended
frame; the corresponding definition of each bit allocation shall comply with the relevant
provisions in SAE J1939-21.2006.
7.2 Protocol data unit (PDU)
Each CAN data frame contains a single protocol data unit (PDU), see Table 1.The
protocol data unit consists of seven parts, namely priority, extended data page, data page,
PDU format, PDU specific format, source address, data field.
7.3 Protocol data unit (PDU) format
Use the PDU1 format defined in SAE J1939-21.2006.
7.4 Parameter group number (PGN)
The second byte of PGN is the PDU format (PF) value; the high byte and low byte bits
are both 00H.
7.5 Transport protocol functions
The transmission protocol function is used, when transmitting a parameter group, which
has a length of 9 bytes ~ 1785 bytes, between the vehicle and the charger. Connection
initialization, data transmission, connection closing shall follow the provisions of 5.4.7
and 5.10 message transmission in SAE J1939-21.2006.The sending interval between
data frames is 10 ms. For multi-frame messages, the message period is the sending
period of the entire data packet.
7.6 Allocation of addresses
Network addresses are used to ensure the uniqueness of information identifiers and to
indicate the source of the information. SECC and EVCC are defined as non-
configurable addresses, that is, the address is fixed in the program code of the ECU; its
source address cannot be changed by any means, including service tools. The charger
and vehicle address allocation are as shown in Table 2.
7.7 Types of information
The CAN bus technical specification supports five types of information, namely
command, request, broadcast/response, acknowledgement and group function. The
specific definition shall follow the provisions of 5.4 Information types, in SAE J1939-
21.2006.
8 Category A system application layer
8.1 The application layer takes the form of parameter and parameter group definitions.
8.2 Use PGN to number the parameter group. Each node identifies the content of the
data packet, based on PGN.
8.3 Use periodic sending and event-driven methods to send data.
8.4 If multiple PGN data need to be sent to implement a function, all the defined
multiple PGN messages must be received, to determine whether the function is
successfully sent.
8.5 When defining a new parameter group, try to put parameters with the same function,
parameters with the same or similar transmission cycle, parameters belonging to the
same subsystem in the same parameter group. At the same time, the new parameter
group must make full use of the data width in 8 bytes; try to put related parameters in
the same group; consider extendibility; reserve some bytes or bits for future
modifications.
8.6 When modifying the parameter group defined in Chapter 10, the newly added
parameters must be related to the original parameters in the parameter group. Irrelevant
parameters shall not be added to the defined PGN in order to save the number of PGN.
8.7 Parameter options are divided into mandatory items and optional items. The
mandatory item parameters shall send actual data, according to the format specified in
this document. Optional item parameters can send actual data, according to the format
specified in this document, OR all bits shall be filled with 1 and sent. For all contents
in the same message which are optional. the sender does not need to send the message.
If it is sent, the actual data shall be sent in the format specified in this document. The
optional item parameters that do not send the actual data are filled with 1.
8.8 The message shall be sent according to the length specified in this document; the
undefined bits in the specified length shall be filled with 1.
8.9 "Untrusted status" is content sent in order to maintain the communication link, when
the sender cannot obtain or clarify the current status. The receiver shall ignore and not
process the information.
9 Overall charging process of category A system
The entire charging process includes six phases. physical connection completion, low-
voltage auxiliary power-on, charging handshake phase, charging parameter
configuration phase, charging phase, charging end phase, as shown in Figure 1.After
the physical connection and the low-voltage auxiliary power-on is completed, the two
parties start communication. At each phase of communication, if the charger and the
vehicle do not receive each other's message OR do not receive the correct message
within the specified time, it is determined to be timeout (timeout means that the other
party's complete data packet or correct data packet is not received within the specified
time), the communication process shall comply with the requirements of Appendix A.
When a timeout occurs, the vehicle or charger sends an error message specified in 10.5.
The charging end process shall comply with the relevant provisions of B4.6 and B4.7
in GB/T 18487.1-2023.See Appendix B for the conditions to start sending and end
sending of the message.
10 Message classification of category A system
10.1 Charging handshake phase
The charging handshake phase is divided into a handshake start phase and a handshake
identification phase. After the physical connection of the vehicle interface is completed
AND the charger successfully closes the electronic lock, the low-voltage auxiliary
power supply circuit is turned on, entering the handshake start phase to send handshake
messages and perform self-check of the charger. If the self-check passes, the two parties
enter the handshake identification phase and exchange the identities of the vehicle and
the charger, as well as other necessary information. If the self-check fails, the charger
sends the charger suspension message, which is specified in 10.3.The message at
charging handshake phase shall comply with the requirements of Table 3.
10.2 Charging parameter configuration phase
After the charging handshake phase is completed, the charger and vehicle enter the
charging parameter configuration phase. At this phase, the vehicle sends the current
battery voltage of the power battery to the charger. If the voltage is not within the range
of the charger's output capability, the charger determines that the charging parameters
do not match; the vehicle can also determine whether charging can be performed, based
on the maximum output capability of the charger. If it is determined that the charging
parameters do not match, the charger and the vehicle send a charging suspension
message (if the charger determines that the charging parameters do not match, it shall
send the charging suspension message, after sending the charger's maximum output
capability message). If the charging parameters match, enter the charging readiness
process, which shall comply with the requirements of B.4.4 in GB/T 18487.1-2023.The
message at charging parameter configuration phase shall comply with the requirements
of Table 4.
11 Message format and content of category A system
11.1 Message at charging handshake phase
11.1.1 PGN9728 charger handshake message (CHM)
Message function. The charger shall send the first CHM message, within 1 second after
the low-voltage auxiliary power supply circuit is closed; send it at an interval of 250
ms, until the charger completes the self-check or receives the vehicle's charging
suspension message. The vehicle confirms the communication protocol version number
of the charger, through CHM messages. Therefore, during the periodic sending process,
the CHM message information shall be consistent. The PGN9728 message format is as
shown in Table 8.
11.1.2 PGN9984 Vehicle handshake message (BHM)
Message function. After the vehicle receives the PGN9728 charger handshake message,
it sends the BHM message and sends it periodically, at a time interval of 250 ms.
SPN2601 is only used to output the cable insulation monitoring voltage basis, when the
charger performs insulation self-check (charger self-check shall comply with the
requirements of B.4.3 in GB/T 18487.1-2023). The PGN9984 message format is as
shown in Table 9.
Among them, SPN2601 vehicle end insulation monitoring allowed total voltage (V).
data resolution. 0.1 V/bit, 0 V offset.
12 General principles of category B systems
12.1 The system communication protocol architecture is based on CAN communication
network. It adopts CAN2.0 protocol. The reference OSI layered model is divided into
4 layers. physical layer (see Chapter 13), data link layer (see Chapter 14), transport
layer (see Chapter 15), application layer (see Chapter 16). The definition, requirements,
implementation methods, etc. of each layer are as shown in Figure 2.
12.2 The communication protocol architecture adopts unified version negotiation
principles and processes (see 14.5).
12.3 The communication protocol framework defines the charging communication
process as an ordered collection of multiple functional modules (see 16.1). See
Appendix C ~ Appendix J, for examples of each functional module.
12.4 The communication protocol for basic charging application scenarios can be found
in Appendix K. The communication protocol for charging and discharging application
scenarios can be found in Appendix L.
13 Physical layer of category B system
The communication between the charger and the vehicle should use an independent
CAN bus, which shall support three nodes. SECC, EVCC, VACC; the communication
rate shall be 250 kbit/s. The physical layer of the CAN communication bus network
shall comply with the provisions on the physical layer in SAE J1939-11.2016 or SAE
J1939-15.2018.The shielded twisted pair shall meet the requirements of Table 7 in SAE
J1939-11.2016.The unshielded twisted pair shall meet the requirements of Table 2 in
SAE J1939-11.2016.The terminal resistance shall meet the requirements of 5.2.3 in
SAE J1939-11.2016.
14 Data link layer of category B system
14.1 Frame format
Equipment using this document shall use the 29-bit identifier of the CAN extended
frame. The corresponding definition of each bit allocation shall comply with the
relevant provisions in SAE J1939-21.2021.
14.2 Protocol data unit
Each CAN data frame contains a protocol data unit (PDU), see Table 30.The protocol
data unit consists of seven parts, namely priority, extended data page, data page, PDU
format, PDU specific format, SA, DATA fields.
14.3 Format of protocol data unit (PDU)
Select the PDU1 format, which is defined in SAE J1939-21.2021.
......
Source: Above contents are excerpted from the full-copy PDF -- translated/reviewed by: www.ChineseStandard.net / Wayne Zheng et al.
Tips & Frequently Asked QuestionsQuestion 1: How long will the true-PDF of English version of GB/T 27930-2023 be delivered?Answer: The full copy PDF of English version of GB/T 27930-2023 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 27930-2023_English with my colleagues?Answer: Yes. The purchased PDF of GB/T 27930-2023_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 27930-2023 -- 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 27930-2023?Answer: Yes. Unless special scenarios such as technical constraints or academic study, you should always prioritize to purchase the latest version GB/T 27930-2023 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 27930-2023?A step-by-step guide to download PDF of GB/T 27930-2023_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 27930-2023".
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 |