SDV Guide
digital.auto
  • Welcome
  • SDV101
    • Part A: Essentials
      • Smart Phone? No: Habitat on Wheels!
      • Basics: What is a Software-defined Vehicle
      • MHP: Expert Opinion
      • Challenges: What sets automotive software development apart?
      • SDV Domains and Two-Speed Delivery
    • Part B: Lessons Learned
      • Learnings from the Internet Folks
        • Innovation Management
        • Cloud Native Principles
          • DevOps and Continuous Delivery
          • Loose Coupling
            • Microservices & APIs
            • Containerization
            • Building Robust and Resilient Systems
      • Learnings from the Smart Phone Folks
    • Part C: Building Blocks
      • Foundation: E/E Architecture
        • Today`s E/E Architectures
        • Evolving Trends in E/E Architectur
        • Case Study: Rivian
      • Standards for Software-Defined Vehicles and E/E Architectures
      • Building Blocks of an SDV
        • Service-Oriented Architecture
          • The SOA Framework for SDVs
          • Container Runtimes
          • Vehicle APIs
          • Example: Real-World Application of SDV Concepts
          • Ensuring Functional Safety
          • Event Chains in Vehicle SOAs
          • Vehicle SOA Tech Stack
        • Over-the-Air Updates: The Backbone of Software-Defined Vehicles
        • Vehicle App Store: The Holy Grail of Software-Defined Vehicles
      • Summary: Building Blocks for Software-Defined Vehicles
    • Part D: Implementation Strategies
      • #DigitalFirst
      • Hardware vs Software Engineering
        • The Traditional V-Model in Automotive Development
        • Agile V-Model, anybody?
        • Key: Loosely Coupled, Automated Development Pipelines
        • The SDV Software Factory
      • Implementing the Shift Left
        • Simulation and Digital Prototyping
          • Early Validation: Cloud-based SDV Prototyping
          • Detailed Validation: SDVs and Simulation
        • Towards the Virtual Vehicle
          • Case Study: Multi-Supplier Collaboration on Virtual Platform
          • Long-Term Vision
        • Physical test system
        • De-Coupled, Multi-Speed System Evolution
        • Continuous Homologation
        • Summary and Outlook
      • Enterprise Topics
        • Variant Management
        • Engineering Intelligence
        • Enterprise Organization, Processes, and Architecture
        • Incumbent OEMs vs EV Start-ups
  • SDV201
  • ./pulse
    • SDV Culture
    • Lean Sourcing
      • LeanRM
        • Why so many Requirements?
      • SCM for SDVs
    • SDV Systems Engineering
      • LeanSE
      • SDVxMBSE
    • Digital First
    • Loose Coupling
      • API-first
      • Freeze Points
    • Automation and Engineering Intelligence
    • Continuous Homologation
    • Build / Measure / Learn
  • Glossary
Powered by GitBook

SDV Guide

  • Legal Notice
  • Disclaimer
  • Privacy Policy

(c) 2025 Dirk Slama

On this page
  • Why Vehicle APIs Matter
  • Key API Standards in the Automotive Domain
  • Example: digital.auto VSS Browser
  1. SDV101
  2. Part C: Building Blocks
  3. Building Blocks of an SDV
  4. Service-Oriented Architecture

Vehicle APIs

Vehicle APIs play a central role in modern Software-Defined Vehicles (SDVs) by enabling standardized access to vehicle data and functions. They simplify development, enhance interoperability, and support new services, driving innovation within the automotive ecosystem.

Why Vehicle APIs Matter

Vehicle APIs matter because the offer Standardized Data and Function Access, Seamless Developer Integration, and Service Enablement and New Business Models:

  1. Standardized Data and Function Access: Vehicle APIs allow developers to access essential vehicle data, such as sensor readings (e.g., vehicle speed or battery state of charge) and control actuators (e.g., moving mirrors, opening windows) in a consistent and standardized way.

  2. Seamless Developer Integration: APIs abstract the complexities of underlying E/E architectures and automotive networks, enabling application developers to focus on creating features without requiring in-depth automotive engineering expertise.

  3. Service Enablement and New Business Models: By facilitating easy access to vehicle functions, APIs unlock opportunities for on-board and off-board services, enhancing the vehicle experience and enabling ecosystem-driven business models such as personalized apps, remote diagnostics, and connected services.

Key API Standards in the Automotive Domain

There are a number of key API standards emerging in the automotive domain, including:

  1. COVESA VSS (Vehicle Signal Specification): A signal-to-service API standard defining how vehicle signals are structured, enabling seamless data access and control through a tree-structured model.

  2. Android Automotive HAL (Hardware Abstraction Layer): Developed by Google, this API standard defines hardware abstraction for Android-based infotainment systems, ensuring consistent integration across different automotive hardware platforms.

  3. ISO 23150: An international standard aimed at standardizing interfaces for automated driving functions, ensuring reliable communication between systems in the context of autonomous vehicle development.

Vehicle APIs are a key enabler for connected services, software-defined platforms, and automotive innovation, bridging the gap between complex vehicle systems and application developers while supporting scalable and interoperable automotive ecosystems.

Example: digital.auto VSS Browser

The digital.auto VSS Browser is an open source, free to use tool to explore the COVESA VSS API catalogue. For example, in the following we show a part of the API catalogue in its original tree structure.

The VSS browser also allows for navigation of the COVESA VSS tree along the VSS catalogue structure. The following shows the catalogue root:

When selecting a particular VSS signal, the details will be shown as follows:

Use the following link to try it out yourself:

PreviousContainer RuntimesNextExample: Real-World Application of SDV Concepts

Last updated 6 months ago

playground.digital.auto