Contents

Service-oriented architecture (SOA) in vehicles

Why vehicle functions are increasingly offered as services instead of fixed signals, how that enables software-defined features, and what it costs.

Why it exists

In signal-based architectures, a new feature often means changing message definitions on several ECUs. With services, a new feature can use existing services (e.g. “door lock”, “seat position”) without touching the providers.

What it is

Functions expose services with methods, events and fields. Consumers discover and use them at runtime. Interfaces are versioned contracts.

How it works in practice

Zone controllers offer services for their I/O; central compute composes them into features; the cloud or apps may use selected services through gateways.

Discovering and using a service
Offer serviceProvider makes its service available
Find serviceConsumer discovers an available provider
SubscribeFor desired events only
Exchange dataReceive events or call methods

Event delivery requires subscription; method calls can follow discovery without subscribing.

Best practices

  • Design services around stable capabilities, not around today’s ECUs.
  • Version and govern interfaces centrally.
  • Apply access control per service and consumer.

Common pitfalls

  • “Chatty” services that flood the network or add latency to control loops.

What it means for your discipline

  • HPC & application software Core

    Designs service interfaces, deployment and lifecycle of services across HPCs and zones.

  • E/E architecture Core

    Service catalogues and interface contracts become the vehicle's architecture backbone.

  • Networks & communication Partial

    Service discovery and communication run over Ethernet with SOME/IP or DDS.

  • Cybersecurity Partial

    Every service is an interface; access control and authentication are required.

  • Base software Partial

    Zone controllers expose their I/O as services or translate between signals and services.

  • Software update & OTA Partial

    Uses service interface versions and provider–consumer dependencies to define compatible update sets and rollback combinations.

No direct stake: Functional safety · Hardware & silicon · Diagnostics & lifecycle

Where it sits in the software stack

Generic layered software of a central HPC (application processor with hypervisor, plus a safety island) and of a classic MCU-based ECU (AUTOSAR Classic). Highlighted modules matter for this topic. Click any module to open its page.

HPC · application processor (MPU) and safety island (MCU)
  • Vehicle services — Composes vehicle features from services with versioned interfaces and explicit provider–consumer dependencies.
  • AUTOSAR Adaptive — Provides ara::com APIs for service discovery, methods, events and fields.
  • SOME/IP · DDS — Carries service discovery and exchanges between providers and consumers using SOME/IP or DDS.
  • Security services — Enforces access policies so only authorised consumers can use exposed vehicle services.
MCU-based ECU · AUTOSAR Classic
  • Application layer — Implements service capabilities or translates local signals and I/O into service interfaces.
  • Communication — Supports service communication on Ethernet-equipped Classic ECUs through configured communication paths and SOME/IP support.