can the e-mobility charging infrastructure be a blueprint for other iot projects?
TRANSCRIPT
Achim Friedland | GraphDefiend GmbH
Can the e-Mobility Charging Infrastructure
be a Blueprint for other IoT Projects?
1. Motivation
2. Bits, Bytes and Protocols
3. Improving the service via Blockchains?
e-Mobility is the future…
…and a real pleasure!
Charging your car…
…still a real pain!
Finding a parking spot…
…still a real pain!
Real time navigation…
…still a real pain!
Open Data is coming!
And will be more than just „free“ data.
Maybe more a bug pattern than
a success story!
Can‘t we do e-mobility somehow smarter?
1. Motivation
2. Bits, Bytes and Protocols
3. Improving the service via Blockchains?
Internet of e-Mobility Things
Charging via Local Authentication
Charging via Local Authentication
Flat RFID Card Ids for User Authentication
→ Flooding, High Latency, Bad Scaling, Privacy?
Problem:
Charging via Remote Start
DE*GEF*E12345678*1
DE*GEF*E12345678*2
EVSE Id = Power Socket Id
Communication Patterns
CS
• Reservations & Remote Start/Stop
• Firmware Updates
• Local Authentication (RFID, NFC, …)
• Current Status, Events, Sensor Data
Internet of e-Mobility Things
Challenged Networking• High latency & error rate, low throughput
• NAT instead of global routable IPv4 Addressing (no IPv6)
• Operational expensive workarounds (Private APNs, VPNs, …)
OCPP’s 1st Approach
CS
• HTTPS/SOAP Server
• Requires public IP Addresses or Private APN
in mobile networks (~VPN)– Expensive in operations
• HTTPS/SOAP Client
• Often no reuse of TCP/TLS sessions– High latency
Open Charge Point Protocol - http://www.openchargealliance.org
OCPP’s 2nd Approach
CS
• HTTPS/WebSockets Client
• Symmetric Remote Procedure Calls (WAMP)
• JSON data representation
• Solves a lot of problems of the 1st approach
• Slow and redundant HTTP/WebSockets
connection setup
• Still no state-machines defined
Open Charge Point Protocol - http://www.openchargealliance.org
When not to use HTTP in IoT?
• Bidirectional communication via a single
connection and single data representationesp. when using SOAP (as it has its own reliable transport features!)
• Multiple replies for a single request or server-
sent-(priority)-events
• Neither CoAP, nor HTTP/2 are better
• ~for any M2M communication (ex. discoverability)
When to use HTTP in IoT?
• Real client-2-server communication over
multiple (virtual) connections
• Multiple data representations (HTML, XML,
JSON, CSV, …), encodings…
• Multiple human languages
• Data caching
• ~for any H2M communication
Lessons learned
• No matter what, build your protocol bottom up
• Do not try to work around HTTP issues!
• On wireless: Overall Air time matters much
more than plain packet size
• Steal context idea from JSON-LD for
versioning and protocol diversity/dialects(Maybe a talk for next year…)
1. Motivation
2. Bits, Bytes and Protocols
3. Improving the service via Blockchains?
e-Mobility Characteristics
• Selling energy is still highly regulated
• Selling energy is close to micro payments
• Digitalization benefits are mostly unattended
“Horses 3.0”
• Highly data-driven, but unclear how to
incentivize data providers and data quality
Charge my electric vehicle (now)
Route me from A to B* with (electric)
constraints
vs.
e-Mobility Mission Statement
• Data (access) marketplaces do not work
and do not solve data quality issues
• (Government) Open Data is already
payed and maintained
• What are business models for data-
driven companies in the new Open Data
Age?
Blockchains and Open Data
• Both are open
• Both try hard to
respect privacy
• Smart Contracts
define rules which
are enforced by the
system
Open e-Mobility Data on
Blockchains
Smart Contracts define…
• Data quality (e.g. correct static data, fast dynamic
data updates)
• Service-Level-Agreements of your backend
• Which protocol features do you support?
• Reservations and Remote Start/Stop
• Construction sites and traffic jams
• Taxes, Tolls and charges
Routing Example (1)
• EV driver starts a routing process from A to B*
• Companies use Open Data to calculate
possible routes and publish the results and
which data they used encrypted for the driver
on the Blockchain
• EV driver chooses a route and publishes the
data used on the Blockchain( Maybe delayed for higher privacy )
Routing Example (2)
• Possible reservations are made
• Competitors can verify wether the provided
information on the used data for the routing
process make sense or not
→ They accept the transaction or not
• Data providers and the routing service are
refunded
Open Data on Blockchains
• Recording any data coming from billions of
data providers (everyone is a prosumer) on
blockchains
• Incentivize high data quality and services
• Refund only data that is actually useful:
“IoT Rank” ;)
1. Motivation
2. Bits, Bytes and Protocols
3. Improving the service via Blockchains?
https://open.charging.cloud
http://m6jonkyse2xyk7nd.onion
Q&A