Bidirectional power transfer in ISO 15118-20, message by message
A DC_BPT session from service discovery to SessionStop: how car and charger agree on bidirectional transfer, which discharge limits each side sets, how the charge loop runs in both directions under scheduled and dynamic control, and how it ends.
Where BPT starts
Everything up to the service discovery runs as in any ISO 15118-20 session: SLAC, SDP, TLS 1.3, the app handshake, SessionSetup and the authorization. ISO 15118-20: the second generation covers that part. This page starts where bidirectional transfer is decided and follows a DC session to its end; Bidirectional charging: V2G, V2H, V2L explains vehicle to home and vehicle to grid, and ISO 15118-20: control modes, BPT and power profiles the two control modes.
Nothing about BPT is negotiated before ServiceDiscovery. Neither SDP nor the app handshake tells the car whether the charger can take power back.
Choosing the service
- EV: ServiceDiscoveryReq, optionally SupportedServiceIDs, the services the car can use
- EVSE: ServiceDiscoveryRes, EnergyTransferServiceList, for example DC (2) and DC_BPT (6); ServiceRenegotiationSupported
- EV: ServiceDetailReq, ServiceID 6
- EVSE: ServiceDetailRes, ServiceParameterList: the parameter sets of the service, each a list of named parameters
- EV: ServiceSelectionReq, SelectedEnergyTransferService: ServiceID 6 and one ParameterSetID
- EVSE: ServiceSelectionRes
- A charger that offers DC_BPT usually offers DC as well, so a car that cannot discharge still charges. The iso20 demo does exactly that: the charger lists DC and DC_BPT, and the car selects DC.
- ServiceDetail is where a BPT parameter set says how the charger works: the control mode, who provides the mobility needs, and parameters of its own for bidirectional operation. The car picks one ParameterSetID in ServiceSelectionReq, and IS20-08 checks that the service and the set were offered.
- From ServiceSelectionRes on, the energy messages carry their BPT variants. IS20-01 checks that the messages on the wire match the selected service.
- The choice holds for the session. To move between DC and DC_BPT without unplugging, the car ends with SessionStopReq ChargingSession ServiceRenegotiation and goes back to the service discovery, which ServiceRenegotiationSupported allows or not. A charger that does not support it answers FAILED_NoServiceRenegotiationSupported.
The service identifiers 5 (AC_BPT) and 6 (DC_BPT), the names of the BPT parameters (for example the channel arrangement, unified or separated, and grid following or grid forming operation) and the exact steps of a service renegotiation are taken from implementations; check them against clause 8 of ISO 15118-20.
Discharge limits
DC_ChargeParameterDiscoveryReq carries BPT_DC_CPDReqEnergyTransferMode instead of DC_CPDReqEnergyTransferMode. It holds everything the one directional variant has and adds four discharge limits; the response mirrors it for the charger in BPT_DC_CPDResEnergyTransferMode.
| Car (request) | Charger (response) | Meaning |
|---|---|---|
| EVMaximumChargePower, EVMinimumChargePower | EVSEMaximumChargePower, EVSEMinimumChargePower | The power window for charging |
| EVMaximumChargeCurrent, EVMinimumChargeCurrent | EVSEMaximumChargeCurrent, EVSEMinimumChargeCurrent | The current window for charging |
| EVMaximumVoltage, EVMinimumVoltage | EVSEMaximumVoltage, EVSEMinimumVoltage | The voltage range both directions stay in |
| EVMaximumDischargePower, EVMinimumDischargePower | EVSEMaximumDischargePower, EVSEMinimumDischargePower | The power window for discharging |
| EVMaximumDischargeCurrent, EVMinimumDischargeCurrent | EVSEMaximumDischargeCurrent, EVSEMinimumDischargeCurrent | The current window for discharging |
| TargetSOC (optional) | EVSEPowerRampLimitation (optional) | The state of charge the car aims for; how fast the charger can change its power |
- Every value is a RationalNumber, a Value with a decimal Exponent; see Physical values: how numbers travel in V2G messages.
- The car sets its discharge limits from the battery, as it does its charge limits: temperature, state of charge and cell voltages. How the car sets its limits explains where these numbers come from.
- The discharge limits have no check of their own. IS20-03 compares EVSEPresentCurrent with the maximum charge current only.
Schedules and energy requests
- ScheduleExchangeReq carries MaximumSupportingPoints and either Scheduled_SEReqControlMode or Dynamic_SEReqControlMode. These have no BPT variant: the same elements serve both directions.
- Scheduled: the car may give DepartureTime and its energy requests (EVTargetEnergyRequest, EVMaximumEnergyRequest, EVMinimumEnergyRequest), and an EVEnergyOffer: an EVPowerSchedule of the power it offers to give back over time, with an EVAbsolutePriceSchedule of what it asks for that energy.
- The charger answers with up to three ScheduleTuple entries. Each has a ChargingSchedule and, optionally, a DischargingSchedule, each made of a PowerSchedule and an optional price schedule.
- Dynamic: the car gives DepartureTime, optionally MinimumSOC and TargetSOC, the three energy requests and, for bidirectional use, EVMaximumV2XEnergyRequest and EVMinimumV2XEnergyRequest. The charger may answer with its own DepartureTime, MinimumSOC and TargetSOC when it provides the mobility needs, and with a price schedule.
- ScheduleExchangeRes can also set GoToPause, and IS20-06 then checks that the session ends as a pause.
How a schedule marks discharge (in the DischargingSchedule, as negative power, or both) and the exact definitions of the energy requests and the V2X energy requests are described here from the schema and secondary sources. Check them against the ScheduleExchange requirements of ISO 15118-20.
Starting energy transfer
- EV: DC_CableCheckReq, repeats while the charger answers Ongoing, as in any DC session
- EV: DC_PreChargeReq, EVTargetVoltage: the charger matches the battery before the contactors close
- EV: PowerDeliveryReq, ChargeProgress Start; in scheduled mode an EVPowerProfile naming the SelectedScheduleTupleID; optionally BPT_ChannelSelection Charge or Discharge
- EVSE: PowerDeliveryRes, EVSEStatus with a notification, if any
- Cable check and pre-charge do not change for BPT: the car still closes its contactors only when the charger output matches its battery. A DC session, message by message and DC session stalls in CableCheck or PreCharge cover both steps.
- The EVPowerProfile is the plan the car commits to in scheduled mode, as EVPowerProfileEntries of a Duration and a Power each.
- BPT_ChannelSelection is optional. It concerns chargers whose parameter set keeps the charge and the discharge path apart, and tells the charger which one the car starts with.
The charge loop in both directions
The loop is DC_ChargeLoopReq and DC_ChargeLoopRes, repeated for the whole transfer. The request always carries EVPresentVoltage and MeterInfoRequested, optionally DisplayParameters, and one control mode element, BPT_Scheduled_DC_CLReqControlMode or BPT_Dynamic_DC_CLReqControlMode. The response carries EVSEPresentVoltage, EVSEPresentCurrent, the three limit flags and the matching BPT_Scheduled_DC_CLResControlMode or BPT_Dynamic_DC_CLResControlMode.
| Scheduled control mode | Dynamic control mode | |
|---|---|---|
| Who sets the operating point | The car, with EVTargetCurrent and EVTargetVoltage in every request | The charger, within the windows both sides send |
| What the car sends | EVTargetCurrent and EVTargetVoltage; optionally its energy requests and updated charge and discharge limits | The three energy requests and its charge and discharge limits in every request; optionally DepartureTime and the two V2X energy requests |
| What the charger sends back | Optionally its updated charge and discharge limits | Its charge and discharge limits; optionally DepartureTime, MinimumSOC, TargetSOC and AckMaxDelay |
| When the direction changes | When the car's target moves from charging to discharging, following the profile it committed to | Whenever the charger moves its setpoint across zero, inside both windows |
- The direction shows in EVSEPresentCurrent. The analyzer reads a negative value as current flowing out of the car, which is what IS20-05 looks for.
- A reversal passes through zero. EVSEPowerRampLimitation from the parameter discovery says how fast the charger can change its power.
- The energy requests follow the battery: the energy still needed to reach the target shrinks while the car charges and grows while it discharges. A charger in dynamic mode uses them, with the departure time, to leave the car able to reach its target in time.
- MeterInfo in the response has two counters: ChargedEnergyReadingWh for energy into the car and BPT_DischargedEnergyReadingWh for energy out of it. PW-04 follows ChargedEnergyReadingWh; the discharge counter shows in the message detail but no check reads it.
- EVSEStatus in the response carries the charger's notifications, among them ScheduleRenegotiation, MeteringConfirmation, Pause and Terminate, each with NotificationMaxDelay, the time the car has to react.
The sign convention of EVTargetCurrent and EVSEPresentCurrent in BPT, the meaning of AckMaxDelay and the use of BPT_ChannelSelection are described from the schema and implementations. Check them against ISO 15118-20 before you rely on them.
How it ends
- EV: PowerDeliveryReq, ChargeProgress Stop; the charger brings the current to zero from whichever direction it was flowing
- EVSE: PowerDeliveryRes
- EV: DC_WeldingDetectionReq, repeated while the car checks that its contactors opened
- EVSE: DC_WeldingDetectionRes, EVSEPresentVoltage falling
- EV: SessionStopReq, ChargingSession Terminate, Pause or ServiceRenegotiation; optionally EVTerminationCode and EVTerminationExplanation
- EVSE: SessionStopRes
- A charger that wants to end sets EVSENotification Terminate in a loop response, and the car runs the same sequence.
- ChargeProgress Standby holds the transfer without ending the session; EVSENotification ExitStandby asks the car to go on. A charger that does not allow standby answers WARNING_StandbyNotAllowed.
- A pause keeps the SessionID for a later resume. The session does not end cleanly shows what a pause looks like in a capture.
- Where the charger needs a signed reading, it sets EVSENotification MeteringConfirmation, and the car answers with MeteringConfirmationReq carrying SignedMeteringData: the SessionID and the MeterInfo with both counters.
How the notifications Terminate, ExitStandby and MeteringConfirmation, ChargeProgress Standby and the code WARNING_StandbyNotAllowed are used is described from the schema; check the rules for each against ISO 15118-20.
What the analyzer checks
| Check | In a BPT session |
|---|---|
| IS20-08 | The selected service and parameter set were offered |
| IS20-01 | The energy messages match the selected service |
| IS20-02 | The control mode stays the same; BPT Dynamic and Dynamic count as the same mode |
| IS20-05 | Passes when a BPT service was selected. In a DC or AC session, a maximum discharge power above zero or a negative EVSEPresentCurrent fails it |
| IS20-03, IS20-04 | The charge side only: the present current against the maximum charge current, and in scheduled mode against EVTargetCurrent |
| PW-04 | ChargedEnergyReadingWh never goes backwards; the discharge counter is not checked |
No demo discharges a car yet. In the iso20 demo the charger offers DC_BPT, the car selects DC, and IS20-05 passes because no power flows back.
Sources
- ISO 15118-20:2022, energy transfer services DC_BPT and AC_BPT, the BPT variants of the DC and AC messages, control modes
- EVerest libcbv2g, the ISO 15118-20 schemas as the analyzer decodes them; the field names on this page follow them
- ChargeX Consortium: ev-charge-seq-state, Argonne National Laboratory, Apache-2.0: PlantUML sequence diagrams of ISO 15118-20 DC and AC bidirectional power transfer with OCPP 2.1, next to those of SAE J1772 and ISO 15118-2 with OCPP 1.6J and 2.0.1