BMW Group Plug & Charge, first manufacturer to integrate multiple charging contracts

[AndiL]

to my knowledge Taycan only supports a single vendor for plug&charge - no plug&charge support for multiple networks at this time - I'm hoping a software update can address/improve this limitation

I welcome correction - I'm hoping @AndiL might be able to help with factual information.

This is correct. The system (hardware!) can only (safely) store 1 charging certificate, to remove it the PCM has to be reset. The ISO15118-2 standard also doesn't contain support for multiple contracts, this will be coming with ISO15118-20 (which also is incompatible to ISO15118-2! so EVs need both installed).

Update: Just to make sure this is clear, you CAN use other charging providers with the Taycan and Plug & Charge. The Taycan is NOT locked to the Porsche charging service.

Sponsored

 

[AndiL]

The certificate data is stored IN the car, the BMW backend has nothing to do with this. If the data was stored in the backend, then you would have to select the contract you want to use, the car would send an request to the backend, which would send the needed certificate to the car, which would then install the certificate in the OBC and only the you can connect the cable into the car. Does not make any sense, does it?

The certificate is (currently) always installed into the EV via a Plug & Charge compatible station the first time you use the charging card. THIS is the scenario where backends are involved. You present the charging card, the charging station will talk to the Hubject backend, which will check if the card has Plug & Charge enabled. If so, it will create a certificate for that, send it to the charging station which will send it to the EV to be installed. Only from then on, you can use Plug & Charge without the card. This whole process takes time.

 

[daveo4EV]

The certificate data is stored IN the car, the BMW backend has nothing to do with this. If the data was stored in the backend, then you would have to select the contract you want to use, the car would send an request to the backend, which would send the needed certificate to the car, which would then install the certificate in the OBC and only the you can connect the cable into the car. Does not make any sense, does it?

The certificate is (currently) always installed into the EV via a Plug & Charge compatible station the first time you use the charging card. THIS is the scenario where backends are involved. You present the charging card, the charging station will talk to the Hubject backend, which will check if the card has Plug & Charge enabled. If so, it will create a certificate for that, send it to the charging station which will send it to the EV to be installed. Only from then on, you can use Plug & Charge without the card. This whole process takes time.

factual and thorough as always - thank you @AndiL

 

[smoothound]

I have found P&C to be inconsistent in the UK - and yes it is still activated in my PCM (just double checked) -

The first 2 times I charged my car A) at ionity, and B) at Porshe tewkesbury on same road trip - P&C worked perfectly.

Ever since (only 6 times so far cos I mainly charge at home) - at both Ionity or Porsche I have always had to use my RFID card to initiate charging...... P&C simply did not work.

I still get the special Kwh price - but no P&C. Hardly a major problem - 1st world.

 

[simcity]

The certificate is (currently) always installed into the EV via a Plug & Charge compatible station the first time you use the charging card. THIS is the scenario where backends are involved. You present the charging card, the charging station will talk to the Hubject backend, which will check if the card has Plug & Charge enabled. If so, it will create a certificate for that, send it to the charging station which will send it to the EV to be installed. Only from then on, you can use Plug & Charge without the card. This whole process takes time.

Thanks for all the updates. Really helpful ?

 

[simcity]

The ISO15118-2 standard also doesn't contain support for multiple contracts, this will be coming with ISO15118-20 (which also is incompatible to ISO15118-2! so EVs need both installed).

So in theory - both standards could coexist on the vehicle?

Would there be additional hardware required to support 15118-20 (in addition to 15118-2)? Thus possible to upgrade the existing fleet if desired through a software update?

 

[simcity]

Some interesting stuff in this Hubject multi-contract P&C white paper (with VW logo etc all over it)…

https://assets.website-files.com/60...7d1d75e28b9c_Plug&Charge_VW_Multicontract.pdf

 

[AndiL]

So in theory - both standards could coexist on the vehicle?

Would there be additional hardware required to support 15118-20 (in addition to 15118-2)? Thus possible to upgrade the existing fleet if desired through a software update?

They will have to coexist, as this protocol needs to be present on the EV and charging station. And the charging station need to support both as otherwise older EVs couldn't charge there any more.

ISO15518-20 is software only, but if the hardware isn't powerful enough or doesn't have enough storage capacity an upgrade would technically be impossible. I would not bet on EV manufacturers updating the existing fleet. It's more likely to be available in new EVs only. Bi-directional charging also requires ISO15118-20.

 

[WasserGKuehlt]

The certificate data is stored IN the car, the BMW backend has nothing to do with this. If the data was stored in the backend, then you would have to select the contract you want to use, the car would send an request to the backend, which would send the needed certificate to the car, which would then install the certificate in the OBC and only the you can connect the cable into the car. Does not make any sense, does it?

It depends on what the 'certificate' is; the backend absolutely is the identity provider, and it either issues the leaf certificate + private key burnt into the car, or it is able to validate/attest the credentials of the vehicle burnt in by some hardware vendor.

I do agree that this 3-party authentication scheme (car, car id provider/manufacturer, and charging service provider) requires consistent connectivity and is prone to latencies. Still, it's a well-known/solved problem.

In your example, a certificate (or token) would not need be issued on demand; the car can talk directly to the charging service, and the respective backends would simply need to have established mutual trust (the/any charging service provider would need to know and trust a car's credentials as being a Porsche/MB etc.) The problem here is why would the car trust the station - it can carry a set of trusted roots, but a new charging network would require an update (service shop or OTA). Therefore the 3-way, while slower, makes sense.

 

[simcity]

They will have to coexist, as this protocol needs to be present on the EV and charging station. And the charging station need to support both as otherwise older EVs couldn't charge there any more.

ISO15518-20 is software only, but if the hardware isn't powerful enough or doesn't have enough storage capacity an upgrade would technically be impossible. I would not bet on EV manufacturers updating the existing fleet. It's more likely to be available in new EVs only. Bi-directional charging also requires ISO15118-20.

I had a proper read through of the white paper I linked from Hubject and it’s suggesting that both versions of 15118 can technically allow multiple charging contracts - with their platform acting as the Contract Certificate Pool.

I didn’t realise until I read the bumpf at the end:

“Hubject is a joint venture of the BMW Group, Bosch, Mercedes-Benz, EnBW, Enel X, E.ON, Siemens and the Volkswagen Group. “

They state specifically in relation to the Taycan:

VW Group
- Porsche Taycan offers Plug&Charge since 2020 - supports installation of third-party MO/EMP contracts via charging station.
- Volkswagen ID models will offer Plug&Charge in 2022 - supports third-party MO/EMP contracts via OEM Backend

Testimonials
Martin Roemheld
Head of eMobility Services at Volkswagen AG
The Volkswagen ID. family and all future platforms will support Plug&Charge in 2022 – the customer can setup any provider‘s charging contract in his vehicle and therefore charge comfortably and automatically.

Interesting

Sponsored