Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
SAE J2847/6: Communication Protocols for Wireless EV Charging
Why Communication Protocols Matter for Wireless Power Transfer
Wireless power transfer (WPT) for electric vehicles offers convenience and automation, but safe and efficient charging depends on robust communication between the vehicle (VA) and the ground assembly (GA). SAE J2847/6 defines abstract messages that support the wireless transfer of energy, based on use cases from SAE J2836/6. This recommended practice ensures that different manufacturers’ EVs and chargers can interoperate seamlessly, handling parameters such as coil type, power class, and alignment status. Without standardized communication, mismatched power levels or misaligned coils could lead to inefficiency or safety risks.
🛠️ Engineering Design Insight: SAE J2847/6 adopts a layered architecture consistent with the OSI model, leveraging widely used standards like IEEE 802.11 and IP protocols. This approach reduces the need for custom hardware and allows the messaging to remain abstract, so it can work with various physical and data link layers. The state machines for VA and GA are defined separately, with clear transitions to manage charging sessions safely.
Architectural Overview and OSI Layer Implementation
The standard specifies technical requirements across all seven OSI layers. This layered approach simplifies integration and future-proofs the communication system. The following table summarizes the protocols used at each layer:
| OSI Layer | Protocol / Standard |
|---|---|
| Physical | IEEE 802.11 |
| Data Link | IEEE 802.11 + WLAN Security |
| Network | IPv4 |
| Transport | UDP / TCP |
| Session | HTTP |
| Presentation | Not specified (abstract encoding) |
| Application | DHCP + SAE J2847/6 Messages (e.g., InitialRequest, InitialResponse) |
The physical and data link layers rely on IEEE 802.11, with Wi-Fi WLAN security recommended to protect the wireless channel. At the network layer, IPv4 is mandatory, while transport layer options include UDP for low-latency exchange or TCP for reliable communication. The session layer uses HTTP to structure request/response interactions. For network configuration, the standard mandates DHCP, and the application layer delivers the core control messages.
Key Messages and System States for Safe Charging
The application layer defines a set of abstract messages that manage the entire charging session. Two of the most important are InitialRequest and InitialResponse:
- InitialRequest: Sent by the vehicle assembly (VA) to initiate a session. It includes fields for VA coil type, natural frequency, and status code. For example, a VA might signal that it is ready and provide its resonant frequency so the charger can adapt.
- InitialResponse: Sent by the ground assembly (GA) in reply, conveying the power class it can supply, the coil type it uses, and whether it supports a z-range (vertical alignment) check. This handshake ensures both sides agree on parameters before energy transfer begins.
- FinePositioningRequest/Response: These messages allow the VA and GA to negotiate alignment methods and exchange data for precise positioning, which is critical for efficient power transfer.
The standard defines separate system states for the VA and GA. The VA transitions through states such as “Idle,” “Positioning,” “Negotiation,” and “Power Transfer.” The GA follows a complementary state machine, with transitions that depend on messages received from the VA. This separation allows each side to manage its status independently while synchronizing the overall session.
⚠️ Common Pitfall: Overlooking the separate state machines for VA and GA can cause synchronization issues. Developers must ensure that state transitions on both sides are correctly paired and that optional fields in messages are not treated as mandatory.
The standard also addresses scheduling of power transfer, enabling utilities and charging stations to manage load. Through the abstract messaging approach, J2847/6 remains flexible enough to support different coil types and power classes, with parameters clearly defined for each message.
Frequently Asked Questions
What does the InitialRequest message do?
The InitialRequest is sent by the electric vehicle (VA) to start a charging session. It includes key parameters like the vehicle’s coil type, its natural frequency, and a status code indicating readiness. This message lets the charger know how to configure itself for efficient wireless power transfer.
How does SAE J2847/6 ensure interoperability between different manufacturers?
Interoperability is achieved through the use of abstract messages that do not rely on a single vendor’s implementation. The standard specifies the fields, valid ranges, and expected responses in the application layer, while the underlying communication layers use widely adopted protocols (IEEE 802.11, IPv4, HTTP). This allows different components to be independently designed yet still communicate correctly.
What security measures are recommended for the wireless communication link?
For the data link layer, the standard recommends Wi-Fi WLAN protections (e.g., WPA2). Additionally, network-layer encryption (such as TLS) can be applied to safeguard sensitive information. Since the wireless channel is open, these measures help prevent unauthorized access or tampering during the charging session.
Can the standard support different coil types and power levels?
Yes. The application messages include fields like VACoilType, GACoilType, and GAPowerClass. These allow the vehicle and charger to advertise their capabilities and negotiate a common working point. The abstract nature of the messages means that new coil designs and power classes can be added without disrupting the overall communication protocol.
