SLIDE 1
Interactive Automotive Systems
2
A Paravirtualized Android for Next Generation Interactive - - PowerPoint PPT Presentation
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
SLIDE 2
SLIDE 3
Interactive Automotive Systems
3
SLIDE 4
Interactive Automotive Systems + ADAS services
- ADAS Services
○ Lane detection ○ Cruise control
- Control ADAS confjgurations
in real-time
4
SLIDE 5
Existing Interactive Automotive Systems
5
SLIDE 6
Existing Interactive Automotive Systems
6
SLIDE 7
Advantages of Android in Automotive Systems
- Android Automotive OS
○ Android Auto
- Running Android natively on a
vehicle’s interactive system
7
SLIDE 8
Limitations of Existing Automotive Systems
8
CAN Bus Network
No Real-time I/O
SLIDE 9
Limitations of Existing Automotive Systems
9
Not guarded enough from security attacks
SLIDE 10
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
SLIDE 11
Our Solution: A Paravirtualized Android in Quest-V Hypervisor
11
SLIDE 12
Paravirtualized Android in Quest-V Hypervisor
12
Core 1 Core 2 Memory USB-CAN Serial Port Bluetooth WiFi T
- uchscreen
Hardware
SLIDE 13
Paravirtualized Android in Quest-V Hypervisor
13
Core 1 Core 2 Memory USB-CAN Serial Port Bluetooth WiFi T
- uchscreen
Hardware Memory Quest Real-Time Kernel (ring 0) VMM (ring -1) Android Kernel (ring 0) VMM (ring -1) Real-time Control T asks and Sensor Data Processing (e.g., T
- rque
vectoring, Battery management, ADAS) User Apps Java API Android Runtime and Native Libs HAL ring 3
Secure Shared memory
SLIDE 14
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 T
- uchscreen
Hardware Memory Quest Real-Time Kernel (ring 0) VMM (ring -1) Android Kernel (ring 0) VMM (ring -1) Real-time Control T asks and Sensor Data Processing (e.g., T
- rque
vectoring, Battery management, ADAS) User Apps Java API Android Runtime and Native Libs HAL ring 3
Secure Shared memory
SLIDE 15
Timing Predictable I/O in Android
Android Services Android Kernel Real-time Quest Functional Services Quest Kernel Real-time I/O Devices Core 1 Core 2
Real-time I/O Real-time shared memory communication
Non-RT I/O Devices
Non-Real-time I/O
SLIDE 16
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
SLIDE 17
Timing Predictable I/O in Android
Android Services Real-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
SLIDE 18
Promising Preliminary Evaluation - I/O Performance
18
Synchronous USB-CAN I/O Latency Synchronous USB-CAN I/O Throughput
SLIDE 19
Future Work
- Supporting Automotive APIs for Quest-V design
- Communication timing requirements
- Secure communication interface
- Power Management
19
SLIDE 20
Thank you! Questions?
20