This page provides an entry point to the platform integration guides for deploying and connecting Android Automotive OS (AAOS) Software Defined Vehicle (SDV) virtual machines (VMs), hardware targets, and middleware transports.
SDV Core
Figure 1. SDV Core architecture.
SDV Core is a minimal headless Android system without a Java virtual machine (JVM), designed for running vehicle service bundles. For bootloader, guest VM image, and APEX signing requirements, see SDV Core integration guide.
SDV Media
SDV Media powers cockpit displays, graphics rendering, and camera pipelines. For integration details, see SDV Media integration overview.
SDV on hardware and QNX Hypervisor
AAOS SDV guest VMs support deployment on automotive Type-1 hypervisors using VirtIO device virtualization. For QNX Hypervisor deployment instructions and sample quantum virtual machine (QVM) configurations for SDV Core, SDV Media, and In-Vehicle Infotainment (IVI), see SDV on QNX and QVM sample configuration for SDV Core.
Middleware, SOME/IP, and IVI integration
To connect AAOS SDV instances with external electronic control units (ECUs), In-Vehicle Infotainment (IVI) systems, and secure vehicle meshes, see the following integration guides:
- SOME/IP integration overview: Connect SDV service bundles to external ECUs over Scalable service-Oriented MiddlewarE over IP (SOME/IP).
- Use the SDV Gateway on IVI: Bridge IVI Java apps and native vehicle hardware abstraction layer (VHAL) implementations with remote SDV services.
- VM identity and attestation: Configure Device Identifier Composition Engine (DICE) attestation and trust stores across the SDV mesh.