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
  • Key Elements of the E/E Architecture
  • Components
  • E/E Communication Networks
  1. SDV101
  2. Part C: Building Blocks

Foundation: E/E Architecture

PreviousPart C: Building BlocksNextToday`s E/E Architectures

Last updated 6 months ago

E/E Architecture stands for Electrical and Electronic Architecture, forming the backbone of modern vehicles by integrating power systems with advanced computing.

The electrical components manage the transmission and distribution of power throughout the vehicle. This includes the wiring harness, battery, power distribution units, electrical connectors, and fuses. On the other hand, the electronics process information and execute functions through circuits and microcontrollers, ranging from lower-level endpoint ECUs (Electronic Control Units) to high-performance compute ECUs designed to run complex algorithms for AD (Automated Driving), ADAS (Advanced Driver Assistance Systems), sensors, and actuators.

Key Elements of the E/E Architecture

Traditionally, the E/E Architecture is structured hierarchically:

  1. Domain Level: Encompasses functional areas such as powertrain, chassis, and infotainment.

  2. System Level: Defines individual systems, for example, engine management and brake control systems.

  3. Component Level: Contains specific hardware and software components to form the complete system.

Components

Key components of the E/E Architecture include:

  • Control Units (ECUs): Manage specific vehicle functions. They process data and control various systems.

  • Sensors: Gather real-time data from the vehicle's environment or interior. They provide crucial input for system operations.

  • Actuators: Convert electrical signals into mechanical actions. They execute commands from control units.

  • Communication Networks: They enable seamless communication between components.

E/E Communication Networks

Networks like CAN, LIN, and FlexRay facilitate data exchange and enable seamless communication between components like ECUs, sensors, and actuators.

  • CAN (Controller Area Network): A widely established, robust protocol for high-speed communication, predominantly used in powertrain and chassis systems.

  • LIN (Local Interconnect Network): A cost-effective, efficient solution for non-critical applications, commonly used in body electronics.

  • FlexRay: A high-speed, deterministic protocol used in safety-critical systems like drive-by-wire and brake-by-wire.

  • Automotive Ethernet: Adapted from Internet Ethernet technology, automotive Ethernet is increasingly used for high-bandwidth applications in modern vehicles.

By tying together these components and communication networks, E/E Architecture enables the seamless interaction of mechanical, electrical, and software systems, laying the foundation for the evolution of Software-Defined Vehicles.