W3C Vehicle Data Access with Eclipse KUKSA - Blueprint for Vehicle Data Oriented Strategy - Return of Experience - GENIVI ...
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
W3C Vehicle Data Access with Eclipse KUKSA Blueprint for Vehicle Data Oriented Strategy - Return of Experience Sebastian Schildt | 16.05.2019
The World is Changing Team Things Team Data Thing Data Connected! 16 May 2019 |. Copyright © GENIVI Alliance 2019 3
A challenging playing field Established OEMs and Large Suppliers • Value creation moves to digital services • Domain knowledge • Much faster innovation cycles • Access to in-car data • Protect existing business • Extend existing business Large Cloud Players • No direct access to in-vehicle data • Experience in generating value from data • Software-focussed • Experience to handle millions of users Newcomers, SMEs • Require open systems and low market entry • Innovative business ideas barriers 16 May 2019 |. Copyright © GENIVI Alliance 2019 4
Eclipse KUKSA – A solid technical foundation Providing a solid technical foundation routed in Open Standards and proven software will benefit everybody + = Create a cross-vendor connected vehicle platform that relies on Mission open standards and uses open source software to leverage the potential of a large developer community! 16 May 2019 |. Copyright © GENIVI Alliance 2019 5
Eclipse KUKSA Ecosystem Eclipse Kuksa is not trying to reinvent the wheel, We use and foster Open Source solutions to create a harmonized composition of existing Open Source projects enriched with specific KUKSA components Using proven IoT technologies such as Hono, Hawkbit, Ditto, …. … Can be deployed on existing Linux distributions such as Linux Automotive grade Linux, Apertis, Ubuntu,… … 16 May 2019 |. Copyright © GENIVI Alliance 2019 6
KUKSA: Some ingredients back-end framework for rolling out Automotive Grade Linux software updates https://www.automotivelinux.org/ https://www.eclipse.org/hawkbit/ Connecting large numbers of IoT Apertis, Debian/Ubuntu based devices to a back end Linux for Autmotive https://www.eclipse.org/hono/ https://wiki.apertis.org/Main_Page Access and ID management Eclipse Cloud IDE https://www.keycloak.org/ https://www.eclipse.org/che/ Container Platform https://www.docker.com/ … 16 May 2019 |. Copyright © GENIVI Alliance 2019 7
Eclipse KUKSA Deployment Core Services Big Data Report Select Analysis Visualization Generation Data Apps 3rd Party Data App Store Management Vehicle Owner 3rd Party Install Data / App IDE Publish Apps Commands & Plug-In Apps Use Interaction Need open APIs / App 1 App 2 standards here! In-Vehicle Platform W3C API layer In-Vehicle Platform Linux OS 16 May 2019 |. Copyright © GENIVI Alliance 2019 9
Data Access Hello-World in KUKSA cloud In-vehicle Datalogger App W3C Vis Server https://www.w3.org/TR/vehicle-information-service/ ELM327 VIS Feeder OBD Adapter 16 May 2019 |. Copyright © GENIVI Alliance 2019 10
Enabling more use cases with KUKSA KUSA retrofit prototyping platform Combines Compute+LTE+OBD access Will be released as open-source soon 16 May 2019 |. Copyright © GENIVI Alliance 2019 11
Experiences with W3C VISS V1 • No concept for different network transports ⁃ Specification is websocket only not a good choice for cellular connections • No security whatsoever ⁃ Maybe it was “out-of-scope”, but this is a must • The provided abstraction is key to enable fleet-wide use cases • Current VSS data model might need some standardized extensions ⁃ The data structure allows this https://www.w3.org/TR/vehicle-information-service/ 16 May 2019 |. Copyright © GENIVI Alliance 2019 12
KUKSA Security for W3C VISS Request is authorized by a token JSON Web Token (JWT) encodes permissions JWT is issued by Authorization Server KUKSA In-Vehicle Platform Transport Security (TLS) * (Keycloak) request In-Vehicle APP request for data KUKSA Vehicle API Tokens must be stored and transmitted sign Backend (VISS) data data data securely to protect against token stealing data verify signature * Alternatives to TLS: Datagramm TLS (DTLS), QUIC, IPsec (network layer security) signed object: optionally(?) signed object: 16 May 2019 |. Copyright © GENIVI Alliance 2019 13
KUKSA Permission Model for Vehicle API Support for different vehicle APIs Proposal: List of APIs with permissions W3C VSS (JWT claim in token) Permissions for “subtrees” Simple read / write permissions (get / set): r, w, rw Flexibel: fine- or coarse-grained, as needed More complex “logic” seems unnecessary “wildcard”: * (top level), a.*.door (intermediate) Default: forbidden (white list) “api-permissions” : { “w3c-vss” : { “drivetrain.fuelsystem” : “r”, “infotainment.media.action” : “rw”, “cabin.door.*.islocked”: “r” }, Direct Access API “can-raw” : { “3A” : “r”, “1E” : “w”}, (raw can frames) Permission for CAN IDs “sensoris” : { ... } } 16 May 2019 |. Copyright © GENIVI Alliance 2019 14
Summary • Data-based business requires open standards • A single use case can not pay for the infrastructure needed • A large ecosystem enables economies of scale and allows to monetize more use cases • Eclipse KUKSA provides technical solutions for a connected car ecosystem • Regarding data access the extensible VSS data structure and W3C VIS is a good start • More work is needed 16 May 2019 |. Copyright © GENIVI Alliance 2019 15
Thank you! https://www.eclipse.org/kuksa/ Dr.-Ing. Robert Bosch GmbH, CR/AEX1 Sebastian Schildt Renningen 70465 Stuttgart Corporate Sector Research and GERMANY Advanced Engineering Visitors: Robert-Bosch-Campus 1 Communication and Network Technologies 71272 Renningen Phone +49 711 811-43902 sebastian.schildt@de.bosch.com www.bosch.com https://github.com/eclipse?q=kuksa
You can also read