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
  • AUTOSAR: A De Facto Industry Standard
  • COVESA: Vehicle Signal Specification (VSS)
  • SOAFEE: Scalable Open Architecture for Embedded Edge
  • Eclipse SDV: Driving Open-Source Innovation
  • Summary: Standards and Alliances Shaping SDVs
  1. SDV101
  2. Part C: Building Blocks

Standards for Software-Defined Vehicles and E/E Architectures

PreviousCase Study: RivianNextBuilding Blocks of an SDV

Last updated 3 months ago

Standards play a crucial role in shaping the development and interoperability of Software-Defined Vehicles (SDVs) and E/E architectures. In this chapter, we explore three key standards: AUTOSAR, COVESA, and SOAFEE, which have become foundational in modern automotive engineering. In addition, we will be looking at Eclipse SDV as an open source alliance, building on open standards.

AUTOSAR: A De Facto Industry Standard

The AUTOSAR (Automotive Open System Architecture) standard is a widely adopted architecture that has been implemented by numerous OEMs and suppliers across millions of vehicles. Developed by the AUTOSAR partnership, an alliance of OEMs, Tier 1 suppliers, and other industry players, it aims to decouple hardware and software through a standardized layer.

This architecture supports key functionalities such as adaptive cruise control and lane departure warnings, typically in applications with high ASIL ratings. It also provides standardization for communication, diagnostics, and integration with vehicle networks.

  • Advantages:

    • Strong standardization and interoperability.

    • Scalability for diverse systems integration.

    • Proven safety and reliability for critical applications.

  • Challenges:

    • High complexity and a steep learning curve.

    • Limited flexibility for rapid innovation.

    • Potentially higher development costs.

Despite its limitations, AUTOSAR remains a cornerstone in ensuring reliable and scalable automotive systems.

COVESA: Vehicle Signal Specification (VSS)

COVESA (Connected Vehicle Systems Alliance), formerly known as GENIVI, is an open alliance that promotes interoperability in connected vehicle solutions. A key contribution from COVESA is the Vehicle Signal Specification (VSS), a standard for structuring and accessing vehicle data.

COVESA VSS provides a tree-structured data model that organizes vehicle domains and their associated sensors and actuators. This standard essentially realizes the signal-to-service transformation discussed earlier in Service-Oriented Architectures (SOA).

  • Key Features:

    • Standardized vehicle signal definitions.

    • Simplified data access for applications.

    • Strong alignment with modern SOA principles.

The adoption of COVESA VSS ensures seamless data handling and accelerates development for connected and software-defined vehicles.

SOAFEE: Scalable Open Architecture for Embedded Edge

The SOAFEE (Scalable Open Architecture for Embedded Edge) standard, spearheaded by ARM and supported by a wide range of OEMs, Tier 1s, hyperscalers, and other industry players, introduces cloud-native principles to the automotive industry.

SOAFEE integrates both on-board and off-board environments to handle mixed-criticality services efficiently.

  • On-Board Architecture:

    • Differentiates between high-compute CPUs for performance and high-safety CPUs for critical functions.

    • Provides separate QM and ASIL environments.

    • Features a hardware abstraction layer (HAL) to support both high and low-safety services.

  • Off-Board Architecture:

    • Executes cloud-based microservices in a mixed-criticality environment.

    • Ensures seamless interaction with on-board systems via orchestrators.

SOAFEE's mixed-criticality orchestrators and modular design enable greater flexibility and efficiency in managing SDV services. It bridges the gap between automotive-grade safety requirements and the agility of cloud-native architectures.

Eclipse SDV: Driving Open-Source Innovation

The Eclipse SDV Working Group, hosted by the Eclipse Foundation, plays a pivotal role in advancing open-source development for Software-Defined Vehicles (SDVs). Its mission is to create an open-source platform supporting tools, frameworks, and runtime environments that align with modern industry standards such as AUTOSAR, COVESA, and SOAFEE.

Key contributions from Eclipse SDV include reference implementations, open development models, and the promotion of standardized APIs. This enables faster, collaborative development and ensures interoperability between different SDV components. By embracing an open-source approach, Eclipse SDV accelerates the deployment of cutting-edge automotive technologies while fostering a global developer community focused on the future of mobility.

Summary: Standards and Alliances Shaping SDVs

Together, AUTOSAR, COVESA, SOAFEE, and Eclipse SDV address the evolving demands of Software-Defined Vehicles, balancing safety, scalability, and innovation. These standards empower OEMs and suppliers to build interoperable and future-ready vehicle platforms by standardizing hardware-software integration and promoting cloud-native, service-oriented architectures.

Complementing these technical standards, the SDV Alliance serves as a global initiative fostering industry collaboration. By uniting automotive manufacturers, technology companies, and software developers, the alliance defines best practices and standards for SDV ecosystems, ensuring a cohesive and innovative approach across the automotive industry.

Together, these standards and alliances create a solid foundation for the automotive industry’s software-driven transformation, supporting cutting-edge technologies while ensuring functional safety, data-driven intelligence, and service-oriented designs that define the future of mobility.

The reality of AUTOSAR and the way forwardVolvo Cars Engineering
Logo