From MirrorLink to Digital Key The role of the Smartphone in the Connected Car

Size: px

Start display at page:

Download "From MirrorLink to Digital Key The role of the Smartphone in the Connected Car"

Barbra Allen
5 years ago
Views:

Dr. Jörg Brakensiek Dr. Jörg Brakensiek is the Chief Architect within the Car Connectivity Consortium (CCC, www.carconnectivity.org).

He has been the Standardization Director in Microsoft s Devices Compatibility and Industry Collaboration team, responsible for Automotive and held

He started his career in Nokia s Corporate Research Center Germany in 1999 and moved to the Silicon Valley in 2007.

He is the Chair of the Technical Work Group within the Car Connectivity Consortium, and responsible for the further development and enhancement of

Jörg is frequently speaking on conferences, workshops, analyst and media events about MirrorLink around the globe.

1 Dr. Jörg Brakensiek Dr. Jörg Brakensiek is the Chief Architect within the Car Connectivity Consortium (CCC, Jörg has 20+ years of experience in wireless and automotive. He has been the Standardization Director in Microsoft s Devices Compatibility and Industry Collaboration team, responsible for Automotive and held various managing, engineering and research positions within Nokia before. He started his career in Nokia s Corporate Research Center Germany in 1999 and moved to the Silicon Valley in Jörg is the original inventor and main technical architect behind MirrorLink ( He is the Chair of the Technical Work Group within the Car Connectivity Consortium, and responsible for the further development and enhancement of MirrorLink s and other Car Connectivity technical specifications. Jörg is frequently speaking on conferences, workshops, analyst and media events about MirrorLink around the globe. Being in the Silicon Valley, Jörg is also the Chief Architect and Co-founder of an Industrial IoT Start-up ( Jörg received his diploma and doctor degrees in electrical engineering from the Technical University of Dortmund, Germany in 1994 and 1999 respectively. He has a broad research background on SoC architectures, software radio, multiprocessors, mobile virtualization. Jörg had been involved in the definition and execution of multiple German and European funded research projects.

2 From MirrorLink to Digital Key The role of the Smartphone in the Connected Car Dr. Jörg Brakensiek Chief Architect and Chair of Technical WG, Car Connectivity Consortium 2017 Car Connectivity Consortium. All Rights Reserved.

3 Outline Car Connectivity Consortium MirrorLink Today & Tomorrow Digital Car Key

4 Car Connectivity Consortium Developing Global Standards and Solutions for Smartphone and in-vehicle Connectivity

6 Car Connectivity Consortium A Global Consortium To bring car, handset and head-unit industries together Established in February, 2011 To develop smartphone-based connected-car solutions Membership open to any interested company Solutions are platform agnostic Solution are not owned/governed by a single member Runs certification programs to ensure compatibility To jointly work on common Work Items MirrorLink (established) Car Data Market Place (in planning) Digital Car Key (in development)

7 Car Connectivity Consortium Some of Our Members

President (PSA), CFO (Alpine), WG Chairs, VP

Bodies (CCC), Admin Eco-System Working Group

Working Group Certification Working Group

8 Car Connectivity Consortium Our Way of Working Board of Directors President (Samsung) Steering Committee + Staff Officers: Executive Director (CCC), Vice President (PSA), CFO (Alpine), WG Chairs, VP China (CCC), App & Device Certification Bodies (CCC), Admin Eco-System Working Group User Experience Working Group Technical Working Group Certification Working Group (Samsung) (VW) (CCC) (RealVNC) 2017 Car Connectivity Consortium. All Rights Reserved.

9 Car Connectivity Consortium Future Directions Maintenance Existing Features New Service Enablement (Digital Key, Car Data) Application Platform Standard Centric Approach 2017 Car Connectivity Consortium. All Rights Reserved.

10 MirrorLink Giving Consumers Access to their Smartphone, while Driving, in a Responsible Way

11 MirrorLink Experience 3 Simple Steps for Consumers Get Into your Car Plug In your Phone Access Your Apps

13 Connectivity MirrorLink Architecture Detect Device on Physical Layer USB Connectivity USB CDC/NCM interface descriptor Dedicated ML USB command to switch to CDC/NCM device class. Infrastructure Wi-Fi No ML specific information Wi-Fi P2P CCC Information Element in IEEE layer USB Host (Head-Unit) Connect Support for CDC/NCM? ML USB Command Re-Connect Support for CDC/NCM Select CDC/NCM USB Device (Phone)

14 Connectivity MirrorLink Architecture Establish IP Connectivity TCP and UDP over IPv4 DHCP UDP TCP ARP IPv4 CDC/NCM Ethernet Infrastructure Wi-Fi Wi-Fi P2P USB IEEE x CCC IE

15 Server Discovery & Identification Discover Server Identify Server MirrorLink Architecture UPnP based ML Server Discovery & Identification MirrorLink Server Device Device Discovery (SSDP) Server: Periodic SSDP:Alive Client: Individual SSDP:Discover Device Identification (HTTP-Get) Client: Retrieve Server Device XML Provides supported services and event/control URLs SSDP UDP IPv4 HTTP TCP Manufacturer Name/URL Model Name/Number UUID/USN BT/Wi-Fi Connectivity Info MirrorLink Version Supported transports Localization Info Signature

16 Client Discovery & Identification Identify Client MirrorLink Architecture UPnP based ML Client Discovery & Identification MirrorLink Client Control Point Client Profile Service SOAP HTTP Device Identification (SOAP) Server implements a Client Profile service (based on SOAP) Client uploads a Profile. Content similar to Server Device XML. Session Start Client sends SetClientProfile SOAP action (Client Profile). Session Termination Client sends SetClientProfile SOAP action ( ). Server sends SSDP:byebye.

Nonce URL Detect replay Bound Port Public Key Protocol specific Certificates Trust Chain Signed

17 Establish Trust Relationship MirrorLink Architecture Security Architecture Device Attestation Device Attestation Validate Device Integrity ML Server measures ML stack components and returns Nonce URL Detect replay Bound Port Public Key Protocol specific Certificates Trust Chain Signed using RSA PKCS#1 v1.5 Public key is used for validating signature or encrypting data Root CA Sub-Root CA

Phone provides app list with meta information

18 ML Application Managment MirrorLink Architecture Application Control from the Head-Unit 1. Phone contains a set of (certified) ML Apps 2. Head-Unit requests list of available (certified) ML Apps 3. Phone provides app list with meta information 4. Head-Unit presents apps 5. Consumer launches app 6. Head-Unit requests app launch from Phone 7. Phone brings app to foreground

19 User Interface Projection MirrorLink Architecture Project the User Interface & Receive Remote Control VNC HSML (Multi) Touch Steering Weal Rotary Knob 2017 Car Connectivity Consortium. All Rights Reserved.

20 Audio MirrorLink Architecture Stream Audio via Car Stereo / Receive Voice Command Legacy Bluetooth BT HFP & BT A2DP RTP Audio Streaming 48 khz, 16 bit, Stereo RTP header extension Turn Right in 500 m 2017 Car Connectivity Consortium. All Rights Reserved.

21 MirrorLink API MirrorLink Architecture Bringing MirrorLink to Applications Apps need MirrorLink Session Information Application To adapt to provided capabilities To ensure driver distraction To create user experience MirrorLink Phone 1 MirrorLink API MirrorLink Phone 2 MirrorLink Phone 3 Identical on all Phones (Platform specific) Android API specified MirrorLink Car A MirrorLink Car B MirrorLink Car C

Data Access MirrorLink Architecture Framework to Exchange Data between Phone & Car Common Data Bus Data service level Service advertisement Start/Stop service Data Payload, Response

22 Data Access MirrorLink Architecture Framework to Exchange Data between Phone & Car Common Data Bus Data service level Service advertisement Start/Stop service Data Payload, Response Service Binary Protocol Data objects level Object values Object type (Int, Dbl, struct, [ ], ) Data Service 1 Object access (Get, Set, Subscribe) D A B Data Service 2 Data Service Endpoint C

Data Services MirrorLink Architecture Data Service Example STRUCTURE Coordinates { DOUBLE latitude; DOUBLE longitude; DOUBLE altitude; DOUBLE accuracy; DOUBLE

23 Data Services MirrorLink Architecture Data Service Example STRUCTURE Coordinates { DOUBLE latitude; DOUBLE longitude; DOUBLE altitude; DOUBLE accuracy; DOUBLE altitudeaccuracy; DOUBLE heading; DOUBLE speed; }; Object GeoLocation { STRUCTURE Coordinates coord; TIME timestamp; GeoLocation Location Data Service }; Data Service Endpoint

24 MirrorLink Applications Challenges Challenge 1: User is Interacting via the In-Vehicle Controls Different screen size and positions Interaction at arm-length Different controls available Challenge 2: App Must Minimize Driver Distraction Main task is driving Easy to visually process Quick to interact Two Sets of Application Requirements Does the App Work in Automotive Context? Does the App Minimize Distraction?

25 MirrorLink Applications Simple Application Guidelines

MirrorLink Applications Base Park Requirements Basic Interoperability Head Unit Screen Sizes are different Reference client display minimum

00 cm - 90 cm from driver App can adapt to larger screen sizes (optional) Controls in Vehicle are different Touch-screen head units and rotary

26 MirrorLink Applications Base Park Requirements Basic Interoperability Head Unit Screen Sizes are different Reference client display minimum display x 480 pixels (square) cm x 8.00 cm - 90 cm from driver App can adapt to larger screen sizes (optional) Controls in Vehicle are different Touch-screen head units and rotary shift-knob units Variety of steering wheel controls and on-dash buttons No dedicated device hardware keys Head Unit needs to know what is being provided Audio metadata to identify and mix audio Ensures App Works in MirrorLink Environment

27 MirrorLink Applications Drive Requirements Minimizing Driver Distraction Guiding Principals Nothing that demands the driver s attention Quickly comprehensible and accessible Restricted Content No video, incidental animations or flashing No automatic scrolling text Visual Accessibility Color contrast brightness & color differences Text legibility Control Accessibility No two-handed operations Should not use the keyboard Control sizing and spacing Pace of Interaction Input retention and responsiveness Notification dismissal Region-Based Certification Default Certification Subset of EU requirements Regional Certification North America (AAM) European Union (EU) APAC (JAMA) China Global Certification Superset of NA, EU and APAC guidelines

28 MirrorLink Applications Example MirrorLink Application Designs Application Design Principles Developers are given an empty canvas for the UI to fill. Maintain brand identity. Templates are possible, but not required. No Limitations Apps can be of any kind: Navigation, entertainment, social, messaging,

29 MirrorLink Applications RockScout by MirrorLink RockScout powered by MirrorLink CCC Drive-Certified Media Player Enables streaming of audio & native media streams without undergoing formal certification. Leverages Android s Media Browser Service Supported Publisher

Phone downloads matching App Cert from CCC database MirrorLink Phone ID 3.

30 Application Certificates MirrorLink Technology Application Certification App Store CCC Cert Database 1. User installs App from any App Store Self App CCC 2. Phone downloads matching App Cert from CCC database MirrorLink Phone ID 3. Phone validates Certificate 4. Phone regularly checks Cert Revocation Status App Advertisements MirrorLink Head-Unit Developer Mode exists

31 MirrorLink Roadmap Where is MirrorLink right now? MirrorLink 1.0 Provided basic technology enablers for MirrorLink use case. Launched end of 2011 MirrorLink 1.1 Provided basic foundation for 3 rd party application developer Launched 2014 MirrorLink 1.2 Expanded the technology portfolio to enable wireless MirrorLink (WFD) and improved wired MirrorLink (HSML). Launched 2016 MirrorLink 1.3 Focus again on applications.

32 MirrorLink Roadmap Where is MirrorLink heading? Co-operation agreement with ETSI (European Telecommunications Standards Institute) ETSI will formally explore adopting MirrorLink as an ETSI Technical Specification. Will be part of ITS Technical Committee, using PAS process Why a formal Standard Why ETSI? A standard will make it easier to work with government bodies and regulators. ETSI is known very well to many of our members ETSI has the right processes to allow adoption of an industry specification, implemented by millions of devices.

33 Digital Car Key Building Digital Key Solution forautomotive

34 Digital Key Main Activities CCC announcement from June 2016 Smartphone as Key has been on the development horizon for many automakers and handset vendors. The proprietary approaches currently being developed and deployed lack wide adoption made possible by a standardized approach. Initial Contribution on Use Cases Presentation of Work Items at Conferences Reach-out to other Organizations White Paper published in Feb/March Technical Specification work has started

36 Digital Key Use Cases Unlock Door Interact with the Car Proximity User interacts with the car at specific location No user action is required on SmartPhone. Car unlocks doors and signals this with lights/sounds Protect against unauthorized access by range detection 2017 Car Connectivity Consortium. All Rights Reserved.

37 Digital Key Use Cases Unlock Door Interact with a Smartphone App Proximity SmartPhone App may automatically launch, when in communication range User interacts with SmartPhone App Car unlocks doors and signals this with lights/sounds Protect against unauthorized access by range detection 2017 Car Connectivity Consortium. All Rights Reserved.

38 Digital Key Use Cases Unlock Door Touch Vehicle with Smartphone User taps SmartPhone at Car (NFC Tab) SmartPhone needs to touch the car at specific location Car unlocks the doors and signals this with lights/sound 2017 Car Connectivity Consortium. All Rights Reserved.

39 Digital Key Use Cases Lock Door Locking use case are similar to Unlocking use cases. User leaves Proximity of the Vehicle User interact with an App on the Smart Device User touches Vehicle with Smart Device at specific location (NFC touch) Car unlocks doors and signals this with lights or/and sound Car also informs SmartPhone about the status of the Lock operation.

40 Digital Key Use Cases Start the Engine User taps SmartPhone at specific location inside car & presses START button. No other explicit action on SmartPhone To protect against unauthorized access, engine start shall only work when SmartPhone is clearly detected inside the car

41 Digital Key Use Cases Additional Authentication Similar to Unlock use cases, with an additional step for to ensure User Authentication on the Smart Device. Before using Digital Key on the smart device some additional user authentication mechanism may be required. This may be in the form of entering simple passcodes up to biometric authentication mechanisms such as fingerprint or iris scans

42 Digital Key Use Cases Key Provisioning

43 Digital Key Use Cases Key Revocation

44 Digital Key Use Cases Key Management for Car Sharing Agencies & Fleets Similar to Key Provision / Revocation Use Cases Provision Digital Keys to the smart devices of the customer for the duration of the rental. This mechanism works agnostic of the brand of the car or the smart device, so that the rental agency is the single contact point for the customer. Important for Car sharing and rental car agencies

45 Digital Key Use Cases Selling the Vehicle Similar to Key Revocation Use Case All digital Keys shall be revoked from all Smart Devices, which had a digital key provisioned.

46 Digital Key Use Cases Digital Key Life Cycle Key Provision Unlock Car Start Engine Lock Car Key Revocation Digital Key requires all main use cases being supported.

47 Digital Key Use Cases Key Sharing Users are accustomed to sharing or lending their keys to family or friends as well as to repair shops or valets. The Digital Key user experience should enable and support similar usages seamlessly. Proximity Sharing: A user in proximity to the Digital Key owner can be granted temporary access via proximity connectivity connections. Remote Sharing: A user far in range from the Digital Key owner can be granted temporary access via long range communication connections.

48 Digital Key Use Cases Key Properties A Digital Key can have properties or rights and restrictions associated with the key. Example 1: Usage of the key for valet parking. Restrict the validity time Restrict maximum speed when the car is accessed with Digital Key Example 2: Delivery to Trunk Allow opening the trunk of the car and not the car itself, Example 3: Pre-set Comfort Functions Key stores vehicle related personal settings or preferences of the user for a more customized user experience. Mirror settings or seat positioning, head unit settings, climate control settings, driving mode settings,

49 Digital Key Use Cases Other Remote Control/Vehicle Status Remotely access the Vehicle functions & status Not in proximity Service Key Data Store vehicle relevant information Use within dealership, error diagnostic

50 Digital Key Technical Architecture High-level Technical Architecture

Building Digital Key Solution for Automotive

Building Digital Key Solution for Automotive Content Overview Use Cases Unlocking Use Cases Key Provisioning Use Cases Key Sharing Use Cases Key Properties High Level Architecture and Related Standards