SAE J 2847-6-2015 Communication between Wireless Charged Vehicles and Wireless EV Chargers.pdf

《SAE J 2847-6-2015 Communication between Wireless Charged Vehicles and Wireless EV Chargers.pdf》由会员分享，可在线阅读，更多相关《SAE J 2847-6-2015 Communication between Wireless Charged Vehicles and Wireless EV Chargers.pdf（96页珍藏版）》请在麦多课文档分享上搜索。

1、 _ SAE Technical Standards Board Rules provide that: “This report is published by SAE to advance the state of technical and engineering sciences. The use of this report is entirely voluntary, and its applicability and suitability for any particular use, including any patent infringement arising ther

2、efrom, is the sole responsibility of the user.” SAE reviews each technical report at least every five years at which time it may be revised, reaffirmed, stabilized, or cancelled. SAE invites your written comments and suggestions. Copyright 2015 SAE International All rights reserved. No part of this

3、publication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of SAE. TO PLACE A DOCUMENT ORDER: Tel: 877-606-7323 (inside USA and Canada) Tel: +1 724-776-49

4、70 (outside USA) Fax: 724-776-0790 Email: CustomerServicesae.org SAE WEB ADDRESS: http:/www.sae.org SAE values your input. To provide feedback on this Technical Report, please visit http:/www.sae.org/technical/standards/J2847/6_201508 SURFACE VEHICLE RECOMMENDED PRACTICE J2847-6 AUG2015 Issued 2015-

5、08 Communication between Wireless Charged Vehicles and Wireless EV Chargers RATIONALE SAE J2847-6 defines abstract messages supporting the wireless transfer of energy between EVs and the Wireless Charger/ (WEVSE). This document is based on the use cases in SAE J2836/6 that established the wireless c

6、harging requirements. TABLE OF CONTENTS 1. SCOPE 3 1.1 Purpose . 3 2. REFERENCES 4 2.1 Applicable Documents 4 2.2 Other Publications . 5 3. DEFINITIONS . 6 4. COMMUNICATIONS SYSTEM ARCHITECTURAL CONFIGURATIONS . 8 4.1 Functional Decomposition of a WPT System 8 4.2 Shared SECC Configuration . 9 4.3 D

7、edicated SECC Configuration 9 5. TECHNICAL REQUIREMENTS 11 5.1 Initialization of V2G Communication Session . 11 5.2 Charging Spot Discovery 11 5.3 Service Discovery and Hardware Compatibility Check . 12 5.4 Vehicle and Charging Spot Alignment 12 5.5 Charging Spot and Vehicle Engagement 12 5.6 Chargi

8、ng Spot and Vehicle Pairing . 13 5.7 Charging Cycle Phases. 14 6. RELATIONSHIP TO INFRASTRUCTURE COMMUNICATIONS . 14 7. EV TO WEVSE COMMUNICATIONS MESSAGES AND PROCEDURES 15 7.1 General information and definitions 15 7.2 Message Sequences . 15 7.3 Wireless Charge Point Discovery . 16 7.4 Protocol Ha

9、ndshake 17 7.5 Message Structure 17 7.6 BodyElement Definitions . 18 8. DATA TYPES 31 8.1 Overview . 31 8.2 Complex Types . 31 SAE INTERNATIONAL J2847-6 Issued AUG2015 Page 2 of 96 8.3 WP Types 33 8.4 Simple data types 40 9. STATE AND SEQUENCE DIAGRAMS 47 9.1 Primary Side State Diagram 47 9.2 Primar

10、y Side State Descriptions . 48 9.3 Secondary Side State Diagram . 50 9.4 Secondary Side State Descriptions 51 9.5 Sequence Diagrams 52 10. SECURITY 59 11. XML SCHEMA 60 11.1 V2G_CI_Beacon.xsd . 60 11.2 V2G_CI_AppProtocol.xsd . 61 11.3 V2G_CI_MsgBody.xsd 62 11.4 V2G_CI_MsgDataTypes.xsd 73 11.5 V2G_CI

11、_MsgDef.xsd 89 11.6 V2G_CI_MsgHeader.xsd 89 11.7 xmldsig-core-schema.xsd . 90 12. NOTES 94 12.1 Marginal Indicia . 94 12.2 Patent Statement 94 Appendix A 95 Figure 1 Functional decomposition of a WPT system . 8 Figure 2 WPT systems with shared SECC . 9 Figure 3 WPT systems with dedicated SECCs . 10

12、Figure 4 Typical high level message flow . 11 Figure 5 Example of pairing ambiguity 12 Figure 6 Schema diagram - V2G_BEACON . 17 Figure 7 Schema diagram - ChargeParameterDiscoveryReq 19 Figure 8 Schema diagram - ChargeParameterDiscoveryRes . 20 Figure 9 Schema diagram PowerDeliveryReq . 21 Figure 10

13、 Schema diagram - PowerDeliveryRes 21 Figure 11 Schema diagram - StartAlignmentReq . 22 Figure 12 Schema diagram - StartAlignmentRes 23 Figure 13 Schema diagram - AlignmentCompleteReq 23 Figure 14 Schema diagram - AlignmentCompleteRes 23 Figure 15 Schema diagram - HeartbeatReq . 24 Figure 16 Schema

14、diagram - HeartbeatRes . 24 Figure 17 Schema diagram PowerDemandReq 25 Figure 18 Schema diagram PowerDemandRes . 27 Figure 19 Schema diagram StartAlignmentCheckReq 28 Figure 20 Schema diagram - StartAlignmentCheckRes . 28 Figure 21 Schema diagram - EndAlignmentCheckReq 29 Figure 22 Schema diagram -

15、EndAlignmentRes . 29 Figure 23 Schema diagram WP_PreChargeReq . 30 Figure 24 Schema diagram WP_PreChargeRes . 30 Figure 25 Schema diagram ServiceProvider . 32 Figure 26 Schema diagram ServiceProviderList 32 Figure 27 Schema diagram WP_EVChargeParameterType . 33 Figure 28 Schema diagram WP_EVPowerDel

16、iveryParameterType 34 Figure 29 Schema diagram WP_EVSEChargeParameterType . 35 Figure 30 Schema diagram WP_EVSEStatusType . 36 Figure 31 Schema diagram WP_EVStatusType 37 Figure 32 Schema diagram WP_PrimaryType . 38 Figure 33 Schema diagram WP_PrimaryListType . 39 SAE INTERNATIONAL J2847-6 Issued AU

17、G2015 Page 3 of 96 Figure 34 Primary side state diagram . 47 Figure 35 Secondary side state diagram 50 Figure 36 Overall WPT message flows . 53 Figure 37 Successful initiation of charging 54 Figure 38 Message flow for delayed start of power transfer . 55 Figure 39 Example message flow for active pow

18、er transfer . 56 Figure 40 Message flow for EV initiated power transfer termination . 57 Figure 41 Suspension of power transfer . 58 Table 1 Semantics and type definition for V2G_BEACON message elements . 17 Table 2 Semantics and type definition for PowerDemandReq 26 Table 3 Semantics and type defin

19、ition for PowerDemandRes 27 Table 4 Semantics and type definition for ServiceProvider type . 32 Table 5 Semantics and type definition for ServiceProviderList type 32 Table 6 Semantics and type definition for WP_EVChargeParameterType . 34 Table 7 Semantics and type definition for WP_EVPowerDeliveryPa

20、rameterType 35 Table 8 Semantics and type definition for WP_EVSEChargeParameterType 36 Table 9 Semantics and type definition for WP_ EVSEStatusType 37 Table 10 Semantics and type definition for WP_EVStatusType 38 Table 11 Semantics and type definition for WP_PrimaryType 39 Table 12 Semantics and typ

21、e definition for WP_PrimaryListType . 39 Table 13 Semantics for EVSERequestedEnergyTransferType . 41 Table 14 Semantics for EVSESupportedEnergyTransferType 42 1. SCOPE This SAE Recommended Practice SAE J2847-6 establishes requirements and specifications for communications messages between wirelessly

22、 charged electric vehicles and the wireless charger. Where relevant, this document notes, but does not formally specify, interactions between the vehicle and vehicle operator. This is the 1st version of this document and captures the initial objectives of the SAE task force. The intent of step 1 is

23、to record as much information on “what we think works” and publish. The effort continues however, to step 2 that allows public review for additional comments and viewpoints, while the task force also continues additional testing and early implementation. Results of step 2 effort will then be incorpo

24、rated into updates of this document and lead to a republished version. The next revision will address the harmonization between SAE J2847-6 and ISO/IEC 15118-7 to ensure interoperability. 1.1 Purpose The primary purpose of SAE J2847-6 is to provide the communication to achieve wireless charging cont

25、rol irrespective of variations in the wireless charging technology employed. SAE J2847-1 identifies the functional messaging for the Plug-In Electric Vehicle (PEV) to connect to the utility for Level 1 the number 0x0C represents the decimal equivalent of 12. 3.12 HOME AREA NETWORK (HAN) A HAN is a n

26、etwork contained within a users home that connects a persons digital devices, from multiple computers and their peripheral devices to telephones, VCRs, televisions, video games, home security systems, “smart“ appliances, fax machines and other digital devices that are wired into the network. SAE INT

27、ERNATIONAL J2847-6 Issued AUG2015 Page 7 of 96 3.13 MESSAGE A message may include several parameters packaged together in a group such that the entire group can be sent together over a physical layer interface. The physical layer will be defined in J2931 documents. 3.14 PLUG-IN ELECTRIC VEHICLE Any

28、class of vehicle BEV, PHEV, Electric Tug, etc., that can conductively receive power from the Electrical Grid where this power is then used to apply traction to the vehicle wheels. 3.15 RECHARGEABLE ENERGY STORAGE SYSTEM (RESS) Means a system that stores energy for delivery of electric energy and whi

29、ch is rechargeable. See also Electric Vehicle Storage. See also subsclause 3.6. 3.16 REVERSE POWER FLOW (RPF) Reverse Power Flow means the direction of energy for discharging a battery from the vehicle to the load. 3.17 POWER FLOW See Forward Power Flow and Reverse Power Flow. 3.18 POWER TRANSFER CO

30、MPONENTS (PTC) Power Transfer Components consist of all elements of the system involved in the actual power transfer (such as power electronics, rectifiers, coils, etc.). 3.19 SIGNAL UPDATE RATE This defines the expected frequency at which a periodic signal must be received over the communications b

31、us for proper system control 3.20 SECC Supply Equipment Communication Controller 3.21 SECCC Supply Equipment Common Communication Controller 3.22 WIRELESS ELECTRIC VEHICLE SUPPLY EQUIPMENT (WEVSE) The equipment from the branch circuit to, and including, the connector that couples to the electric veh

32、icle inlet, the purpose of which is to wirelessly transfer electric energy to an EV. This equipment is located off-board the vehicle. SAE INTERNATIONAL J2847-6 Issued AUG2015 Page 8 of 96 4. COMMUNICATIONS SYSTEM ARCHITECTURAL CONFIGURATIONS 4.1 Functional Decomposition of a WPT System This section

33、describes a simple decomposition of the WPT system into communications and PTC. The PTC consists of all elements of the system involved in the actual power transfer (such as power electronics, rectifiers, coils, etc.). The Off-board PTC is associated with the Infrastructure side and the Onboard PTC

34、are the components installed on the EV. The communications function that supports and controls the power transfer is referred to as the Communications Controller. On the infrastructure side this is referred to as the Supply Equipment Communications Controller (SECC) and on the EV side as the Electri

35、c Vehicle Communications Controller (EVCC). On the infrastructure side a single SECC may control multiple off-board PTCs, may be dedicated to a single PTC or may have a distributed architecture where some of the control functions are centralized and others are controlled on a per PTC basis. Figure 1

36、 - Functional decomposition of a WPT system SAE INTERNATIONAL J2847-6 Issued AUG2015 Page 9 of 96 4.2 Shared SECC Configuration Figure 2 - WPT systems with shared SECC In a shared SECC configuration a single SECC has visibility and (partial) control of multiple Off-board PTC. Such architecture facil

37、itates the management and assignments of various parking slots, as well as allowing the SECC to optimize the grid load across multiple EVs in an active charging session. The control capabilities may be shared between the SECC and the Off-board PTC, e.g. foreign object detection and corresponding cor

38、rective/protective action can be performed by the off-board PTC and/or vehicle without intervention by the SECC. The division of the split of such functionality is beyond the scope of this specification. Similarly, the communications interface between the SECC and the off-board PTC is beyond the sco

39、pe of this specification and may be vendor specific. 4.3 Dedicated SECC Configuration In a dedicated SECC configuration each off-board PTC has its own controller that acts autonomously. Such a configuration has the advantage of isolating SECC failure modes to a single charging spot. SAE INTERNATIONA

40、L J2847-6 Issued AUG2015 Page 10 of 96 Figure 3 - WPT Systems with dedicated SECCs SAE INTERNATIONAL J2847-6 Issued AUG2015 Page 11 of 96 5. TECHNICAL REQUIREMENTS The wireless charging process differs in a number of aspects from the conductive process. In conductive charging the EVSE pylon is visib

41、le and the operator objective is to position and park the vehicle close enough to the EVSE that the vehicle power inlet is within reach of the plug at the end of the cable. The EVSE remains visible while the operator is positioning the vehicle. For the case of wireless charging the vehicle must be p

42、ositioned with greater precision with respect to the primary pad. In public areas, the precise charging pad location may not be visible and will certainly not be visible as the vehicle positions itself over the pad. This difference dictates that the vehicle and operator rely on communications to ach

43、ieve alignment between the primary and secondary pads. An overview of the overall wireless charging process can be found in J2836/6. Figure 4 - Typical high level message flow 5.1 Initialization of V2G Communication Session This phase begins when the EV is within communication range of the charging-

44、spot in which it will park. The EVCC connects to the WEVSEs SECC (Association) this connection will be used for messages for the charging process. Once the connection is working, the EVCC and the SECC will negotiate the protocol to be used (appProtocolRequest/Response). 5.2 Charging Spot Discovery C

45、harging Spot and Service Discovery may be supported in either a centralized, distributed or per charge-spot configuration. Charging Spot Discovery is an optional feature where a system would “advertise” the infrastructure providers, and the availability of charging spots as well as their characteris

46、tics for a number of geographically proximate charging spots (e.g. multiple WEVSE enabled spots in a parking garage). Charging Spot discovery may be performed by means other than the vehicles communications system (e.g. smartphone, tablet, or PC) SAE INTERNATIONAL J2847-6 Issued AUG2015 Page 12 of 9

47、6 Figure 5 - Example of pairing ambiguity 5.3 Service Discovery and Hardware Compatibility Check Once the protocol has been agreed, the EVCC and SECC exchange hardware compatibility information, service and payment information, and contract authentication (if needed). Note that this exchange can be

48、as simple as an exchange of pre-defined tokens, or a list of strings. The EVCC will send its capabilities to the SECC, and the SECC will determine if there is enough compatibility for power transfer. The hardware compatibility is needed first, as there is no point in determining if one can pay for a

49、 service but not use the hardware. The service discovery is necessary as there is no point in parking if one cannot pay for the charging. 5.4 Vehicle and Charging Spot Alignment Alignment is the process where the EV moves over the charging spot and stops when the primary and secondary devices are positioned to allow for efficient power transfer. Editors Note: The alignment methods available a