Voertuigconstructeurs en data economie

Transcription

1 Voertuigconstructeurs en data economie STUDIEDAG VERKEERSVEILIGHEID VLAAMS HUIS VOOR DE VERKEERSVEILIGHEID DEPT MOW VLAAMS PARLEMENT, BRUSSEL 11 DECEMBER 2017 Saturday, 30 December 2017

2 AGENDA 1. Context of Cooperative, Connected and Automated Mobility 2. Data Economy Initiative 3. Access to Vehicle Data 4. ACEA Position on Access to Data 5. Q & A 2

3 1. Context of CCAM

4 CONNECTIVITY SERVICES 4

5 TOWARDS COOPERATIVE, CONNECTED AND AUTOMATED MOBILITY Day 1 Awareness Starts Day 2 Automation Starts Day 3 Cooperation Starts Day 4 Future Mobility Cooperative Connected Automated I share where I am and what I hear Hybrid Connectivity ITS G5+LTE V Advanced Driver Assistance System I share what I see Hybrid +5G Some Roads Human Back up We share our intentions Hybrid + New technologies Most Roads No Human Back up We coordinate all manoeuvres Hybrid + new technologies Fully Automated Cooperative, Connected and Automated

6 2. Data Economy Initiative

7 BUILDING A EUROPEAN DATA ECONOMY EC Communication of 10 January 2017 Communication Building a European Data Economy Data localisation restriction Data access, re use and transfer Liability Portability, interoperability and standards Public Consultation Purpose: To help shape the Commission s policy agenda Report available online Reference to the Automotive Sector CCAM could be considered as testbed for data economy issues Trialto be carried out it partnership with stakeholders 7

8 BUILDING A EUROPEAN DATA ECONOMY Expectations following the consultation Some Commission initiatives are to be expected following this consultation: September 2017: Proposal for Regulation on a framework for the free flow of non personal data in the EU Spring 2018: EC will Launch an initiative on accessibility and re use of public and publicly funded data EC will further explore the issue of privately held data of public interest (reverse PSI) Commission intends to continue to assess the need for action concerning emerging data issues, notably regarding data access rights. 8

9 3. Access to Vehicle Data

10 VEHICLE DATA: SAFE AND SECURE ACCESS 10

11 ACCESS TO VEHICLE DATA Why is vehicle data of interest? There are different reasons to use vehicle data Ad hoc communication for driver assistance systems Diagnostic and maintenance Data based services 11

12 A VEHICLE IS NOT A SMARTPHONE 12

13 A CAR IS NOT A SMARTPHONE 13

14 DATA AND USAGE Clear distinction between data and purpose/use case Access to data depends on: o The use case (e.g. traffic related data) o The nature of usage (public interest versus commercial) o The type of data (personal or non personal data) Balancing and safeguarding multiple interests: o Vehicle integrity, safety, security, liability o Public interest versus commercial interests o Privacy and data protection o Fair competition o IPR and trade secrets 14

15 4 CATEGORIES OF DATA/USE CASES 1. Public interest data > Reciprocity Data relevant to traffic safety (e.g. local hazard warning, ITS related services) 2. Data triggered by the vehicle > B2B Services available across brands: non differentiating vehicle data (e.g. ambient temperature, traffic flows, road sign recognition, street parking) 3. Vehicle specific technical data > N/A Brand specific services & component analysis/product improvement: link to suppliers, IP protected (e.g. ECU monitoring, chassis sensor data) 4. Data triggered by driver > Consent + B2B Personalised services (e.g. vehicle position, speed, insurance, fleet, roadside assistance, diagnostic) 15

16 DATA SHARING AND DATA PROTECTION Vehicle owner decides with whom they share their personal data and for what purposes Personal data of vehicle users is only made available in accordance with EU data protection legislation (GDPR) Manufacturers share personal data with third parties only: o On the basis of a contract with the customer o With the prior consent of the customer o To comply with legal obligations 16

17 THE SIX INTERFACES OF A FULLY CONNECTED VEHICLE E Call interface Far field over the air communication used to send regulated data from a vehicle involved in a road traffic accident Charging interface Communication with charging station to enable the charging of electric vehicles Infotainment interface Near field over the air communication between a customer mobile device and the vehicle infotainment system e.g. hands free telephony, terminal mode to vehicle HMI Ad hoc interface Real time near field over the air communication between vehicles or a vehicle and the traffic infrastructure for traffic safety / efficiency use cases Point to point Low latency (real time) Safety critical Low bandwidth On Board Diagnostics interface (OBD) Wired communication with test / inspection equipment. Used by trained technicians to gain access to regulated data for emissions, diagnosis, repair and maintenance purposes Extended Vehicle server interface Standardized server communication used to enable 3 rd parties and neutral servers to access vehicle generated data and predefined in vehicle routines in a secure manner. ISO Extended Vehicle 17

18 SAFE AND SECURE ACCESS TO VEHICLE DATA Extended Vehicle and Neutral Server Ad hoc communication Under responsibility of the VM (no data transmission to neutral server) User OBD Only for regulated emissions, diagnostics, repair and maintenance (no data transmission to neutral server) Notification Is provided by the vehicle manufacturer Connects to multiple service providers and neutral server(s) Contains rule engine to send authorised data (customer consent) to a specific service provider or neutral server Tier 1 supplier e.g. data for quality control Tier 1 supplier VM server B2B neutral server Extended Vehicle ISO ISO Extended Vehicle Web Service (draft) Access for service providers & neutral server(s) Services Provider B2B Consent Is provided by a third party Connects to multiple VM servers Contains a separate rule engine to send authorized data (customer consent) to a specific service provider Respects purpose of data Visualisation Service provider Service provider is not visible to the VM 18

19 ACCESS TO VEHICLE DATA OBD Interface Diagnosis and maintenance Open gate for hacking OBD interface is a well defined interface for diagnosis and maintenance in a defined service station Using the OBD interface with a connected dongle can cause serious security/safety problems 19

20 4. ACEA Position on Access to Data

21 ACEA POSITION ON ACCESS TO DATA Conclusion OEMs prepared to make data available, but only when the following principles are respected: o o o o o o Safety, security, vehicle integrity and liability Customer choice (repair and maintenance, as well as mobility services) Fair competition Privacy and data protection Interoperability (standardised approach, cfr ISO) Return on investment Direct access to data inside the vehicle poses a threat to: safety, security and integrity of the vehicle Dongles connected to an OBD interface pose a risk to the vehicle Focus on providing off board access to data through Extended Vehicle model 21

22 ACEA POSITION ON ACCESS TO DATA Position Paper, Video and Website

23 5. Q&A

24 OTHER USEFUL LINKS

25 STAY CONNECTED Joost Vantomme, Smart Mobility Director 25

26 THANK YOU FOR YOUR Next