ANDROID AUTOMOTIVE SIG Monthly All Hands Call 29

ANDROID AUTOMOTIVE SIG Monthly All Hands Call 29 October 2019

Agenda • Update on Reference/Development Platform • Update on Vehicle Data APIs / Vehicle HAL subproject • Update on App Ecosystem • Technical Summit • Any Other Business 29 October 2019 |. Copyright © GENIVI Alliance 2019 2

Android Automotive SIG Reference Platform • Boards & Support • Both NXP & Renesas boards have reached Gunnar for initial set up and testing. (The Google default embedded board Hi. Key 960 also available) • NXP: Needed files for i. MX 8 for Android Pie/9. 0 is available from support site. • Renesas: Files available when the final EULAs have been clarified and signed (soon) • Android 10. 0 was released to AOSP project in September and will be our next target, when BSPs support it. • Lava-based test farm up & running at Renesas, tested with Yocto/Linux builds → We are now considering how to set up our Android tests on the same infrastructure • No further efforts on Qualcomm after they stopped responding • Project Repository is up! → https: //github. com/GENIVI/aasig_dev_platform • The Git. Hub repository is now populated with the initial scripts that help to set up, download AOSP source code, and define a shared development version. • Container setup (using Docker) is included, to get repeatable tests of build scripts in a stable environment • Now is the time for community (AASIG) input – test the scripts, check if the built versions are what you expect, and suggest updates and modifications accordingly. • The project is set up to support Renesas R-Car starter-kit with Kingfisher and NXP i. mx 8 EVK boards, with potentially Hi. Key as a low-cost backup.

Android Automotive SIG Vehicle Data APIs - Vehicle HAL • 3 Vehicle Data API calls on Wed 25 September, Tue 10 October & Tue 22 October • a dozen of participants for each call • Minutes: https: //at. projects. genivi. org/wiki/x/HYVo. Ag • Architectural concepts for the vehicle data capturing have emerged (see next slides) • Will be presented and debated at the Vehicle HAL Design Workshop at the upcoming tech summit • Gap analysis between Android 9 & 10 – work-in-progress • Topics needing further investigation • Secure access control in Some/IP (for interfacing with Adaptive Autosar for instance) • Signal-to-Service translation (should be in the upcoming Adaptive Autosar R 19 -11) Audio HAL • Gathering of interested parties still in progress (Analog Devices, Bosch, Harman) 29 October 2019 |. Copyright © GENIVI Alliance 2019 4

Android Automotive SIG Architecture ideas VISS websocket solution based on VISS server -client model and using VSS data, Jason webtoken used for access control Headunit VHAL VISS clients can read/write predefined car data from/to VISS server CAN decod VISS server holds all car data (static tree in spec. gen 1, dynamic in spec. gen 2? ) VISS server ETH CAN ETH VISS server VCU/Gateway/ Autosar/ other CAN ETH VISS client ECU 1 ECU 2 ETH VISS client? Autosar VISS client ECU 3 ECU 1 ECU 2 ETH CAN Autosar/other ECU 3

Android Automotive SIG Concept : Replace car API VHAL with VISS Headunit Google would need convincing and even so why remove this when it can co-exist? CAR API VISS client VHAL VISS server holds all car data (static tree in spec. gen 1, dynamic in spec. gen 2? ) CAN decod CAN VISS client ECU 1 29 October 2019 |. Copyright © GENIVI Alliance 2019 ETH VISS client ECU 2 ETH VISS client? Autosar ECU 3 6

Android Automotive SIG Concept: Co-existing Car API VHAL with VISS Headunit Proposal on how Android layers match VISS!? HOW IDL can be implemented without breaking treble. What would the impact be when doing update, cts treble other? CAR API VISS client VHAL VISS server holds all car data (static tree in spec. gen 1, dynamic in spec. gen 2? ) CAN decod CAN VISS client ECU 1 29 October 2019 |. Copyright © GENIVI Alliance 2019 ETH VISS client ECU 2 ETH VISS client? Autosar ECU 3 7

Android Automotive SIG Concept: Co-existing car API and VISS Headunit All apps can use CAR api, OEM apps and system apps can use vendor VISS API. APPS CAR API VISS API VHAL VISS client n+x-signals n-signals VISS server Socket comm. CAN decod CAN Socket comm. ETH Remaining question (among other) • • Effect on Android certification (VTS/CTS)? Security access to signals (jason web token? ) Can this be done and still follow treble to make sure OTA compliance Protocols between ECUs? 29 October 2019 |. Copyright © GENIVI Alliance 2019 CAN VISS client ECU 1 ETH VISS client ECU 2 VISS server holds all car data (static tree in spec. gen 1, dynamic in spec. gen 2). Supplies car data to both CAR API and vendor module ”Viss client”. VISS server might hold a bigger number of signals then CAR API uses. Google car api remains. ETH VISS client? Autosar ECU 3 8

Android Automotive SIG Market Survey of Automotive Apps/Services Suppliers 1 October 2019

Survey Results for App/Services Suppliers Amazon (OEMsx 3) Harman (x 3) Bosch (x 2) Aptoide. com (x 2) Parrot (x 2) HERE (x 2) Apkpure. com Elektrobit Inrix Microsoft Panasonic Qualcomm Samsung Sprint SXM Xevo

GENIVI Technical Summit ~ Troy, MI Where: Marriott Hotel – Troy, Michigan When: 12 -13 November 2019 On-line Program: https: //www. eventleaf. com/Tech. Summit 19 3 workshops on Android Automotive SIG • Vehicle HAL design (3 -hour) workshop moderated by BMW and Mercedes-Benz • Additional Challenges to Address when Adopting Android Automotive moderated by Tieto • AASIG activities review & planning (3 -hour) session 29 October 2019 |. Copyright © GENIVI Alliance 2019 11

Thank you! Visit GENIVI: http: //www. genivi. org http: //projects. genivi. org Contact us: help@genivi. org