A Paravirtualized Android for Next Generation Interactive Automotive Systems Soham Sinha, Ahmad Golchin, Craig Einstein, Richard West Department of Computer Science, Boston University
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
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 configurations 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
8
CAN Bus Network
No Real-time I/O
Limitations of Existing Automotive Systems
9
Not guarded enough from security attacks
Requirements of a Next Generation Interactive Automotive Systems
10
Real-time, predictable and secure I/O
Familiar, straightforward and rich user-interface
Minimal hardware complexity
Ability to develop custom apps
Our Solution:
A Paravirtualized Android in Quest-V Hypervisor
11
Paravirtualized Android in Quest-V Hypervisor
12
Core 1 Core 2
Memory
USB-CAN
Serial Port
Bluetooth WiFi
Touchscreen
Hard
ware
Paravirtualized Android in Quest-V Hypervisor
13
Core 1 Core 2
Memory
USB-CAN
Serial Port
Bluetooth WiFi
Touchscreen
Hard
wareMemory
Quest Real-Time Kernel(ring 0)
VMM (ring -1)
Android Kernel(ring 0)
VMM (ring -1)
Real-time Control Tasks and Sensor Data Processing
(e.g., Torque vectoring, Battery
management, ADAS)
User Apps
Java API
Android Runtime and Native Libs
HAL
ring
3
SecureShared memory
Advantages of Paravirtualized Android in Quest-V
14
● Familiar Android UI● Large App developer
community● Real-time and
predictable I/O in Quest
● Secure I/O data transfer through shared memory between Android and Quest
A single-board solution
Core 1 Core 2
Memory
USB-CAN
Serial Port
Bluetooth WiFi
Touchscreen
Hard
wareMemory
Quest Real-Time Kernel(ring 0)
VMM (ring -1)
Android Kernel(ring 0)
VMM (ring -1)
Real-time Control Tasks and Sensor Data Processing
(e.g., Torque vectoring, Battery
management, ADAS)
User Apps
Java API
Android Runtime and Native Libs
HAL
ring
3
SecureShared memory
Timing Predictable I/O in Android
Android Services
Android Kernel
Real-time Quest Functional Services
Quest Kernel
Real-time I/ODevices
Core 1 Core 2
Real-time I/O
Real-time shared memory communication
Non-RT I/O DevicesNon-Real-time I/O
Promising Preliminary Evaluation - Cold Startup Time
16
Vanilla Android
Paravirtualized Android in Quest-V
Booting Android 16.6 s 23.7 s
IVI (HVAC) App Startup
49 s 59.2 s
Startup times
Timing Predictable I/O in Android
Android ServicesReal-time Quest
Functional Services
Quest Kernel
USB-CAN Interface
Core 1 Core 2
I/O using Paravirtualized Android in Quest-V
Android Services
Android Kernel
Core 2
Non-RT I/O Devices
I/O using vanilla Android
Promising Preliminary Evaluation - I/O Performance
18
Synchronous USB-CAN I/O Latency
Synchronous USB-CAN I/O Throughput
Future Work
● Supporting Automotive APIs for Quest-V design● Communication timing requirements● Secure communication interface● Power Management
19
Thank you!Questions?
20
Related Documents
