A Paravirtualized Android for Next Generation Interactive - PowerPoint PPT Presentation

A Paravirtualized Android for Next Generation Interactive Automotive Systems Soham Sinha, Ahmad Golchin, Craig Einstein, Richard West Department of Computer Science, Boston University

Interactive Automotive Systems 2

Interactive Automotive Systems 3

Interactive Automotive Systems + ADAS services ● ADAS Services ○ Lane detection ○ Cruise control ● Control ADAS confjgurations in real-time 4

Existing Interactive Automotive Systems 5

Existing Interactive Automotive Systems 6

Advantages of Android in Automotive Systems ● Android Automotive OS ○ Android Auto ● Running Android natively on a vehicle’s interactive system 7

Limitations of Existing Automotive Systems No Real-time I/O CAN Bus Network 8

Limitations of Existing Automotive Systems Not guarded enough from security attacks 9

Requirements of a Next Generation Interactive Automotive Systems Familiar, straightforward and rich user-interface Ability to develop custom apps Real-time, predictable and secure I/O Minimal hardware complexity 10

Our Solution: A Paravirtualized Android in Quest-V Hypervisor 11

Paravirtualized Android in Quest-V Hypervisor Core 1 Core 2 Hardware Memory USB-CAN Bluetooth WiFi Serial Port T ouchscreen 12

Paravirtualized Android in Quest-V Hypervisor User Apps Real-time Control T asks and Sensor Data Processing Java API (e.g., T orque vectoring, Battery Android Runtime and ring 3 management, Native Libs ADAS) Secure HAL Shared memory Quest Real-Time Android Kernel Kernel VMM VMM (ring 0) (ring 0) (ring -1) (ring -1) Core 1 Core 2 Hardware Memory Memory USB-CAN Bluetooth WiFi Serial Port T ouchscreen 13

Advantages of Paravirtualized Android in Quest-V User Apps ● Familiar Android UI Real-time Control ● Large App developer T asks and Sensor ● Real-time and community Data Processing Java API predictable I/O in (e.g., T orque Quest vectoring, Battery Android Runtime and ring 3 management, Native Libs ● Secure I/O data ADAS) Secure transfer through HAL Shared shared memory memory between Android and Quest Real-Time Android Kernel Kernel Quest VMM VMM (ring 0) (ring 0) (ring -1) (ring -1) A single-board Core 1 Core 2 solution Hardware Memory Memory USB-CAN Bluetooth WiFi Serial Port T ouchscreen 14

Timing Predictable I/O in Android Real-time Quest Android Services Functional Services Real-time I/O Quest Kernel Android Kernel Real-time shared memory communication Non-Real-time I/O Real-time I/O Non-RT I/O Devices Devices Core 1 Core 2

Promising Preliminary Evaluation - Cold Startup Time Startup times Vanilla Paravirtualized Android in Android Quest-V Booting Android 16.6 s 23.7 s IVI (HVAC) App 49 s 59.2 s Startup 16

Timing Predictable I/O in Android Real-time Quest Android Services Android Services Functional Services Quest Kernel Android Kernel USB-CAN Interface Non-RT I/O Devices Core 1 Core 2 Core 2 I/O using vanilla I/O using Paravirtualized Android in Quest-V Android

Promising Preliminary Evaluation - I/O Performance Synchronous USB-CAN I/O Synchronous USB-CAN I/O Latency Throughput 18

Future Work ● Supporting Automotive APIs for Quest-V design ● Communication timing requirements ● Secure communication interface ● Power Management 19

Thank you! Questions? 20