Contents

SOME/IP and DDS — service communication

The middleware protocols that let software components offer and use services over Ethernet — the communication backbone of service-oriented vehicle software.

Why it exists

Signal-based communication (fixed CAN messages) does not scale to software that is updated and redeployed often. Services — “give me the vehicle speed”, “lock the doors” — decouple who provides a function from who uses it.

What it is

  • SOME/IP (Scalable service-Oriented MiddlewarE over IP): automotive protocol for remote procedure calls, events and fields, with SOME/IP-SD for service discovery. Widely used with AUTOSAR.
  • DDS (Data Distribution Service): data-centric publish/subscribe with rich quality-of-service options, popular for ADAS and robotics (e.g. ROS 2).

How it works

A provider announces a service via discovery; consumers subscribe to events or call methods. Interfaces are described in ARXML (SOME/IP) or IDL (DDS) and code is generated.

SOME/IP method call example
Offer serviceProvider announces availability through SOME/IP-SD
Discover serviceConsumer learns the provider's endpoint
Send requestConsumer calls a provider method
Return responseProvider sends the result to the consumer

This example shows SOME/IP discovery and request/response; event subscriptions and DDS publish/subscribe use different exchanges.

SOME/IP discovery and service use
Provideroffers the service
Consumeruses the service
OfferServiceSOME/IP-SD announces availability
SubscribeEventgroupSOME/IP-SD requests event subscription
SubscribeEventgroupAckSOME/IP-SD accepts subscription with positive TTL
EventsSOME/IP notifications for subscribed events
Method requestSOME/IP calls a method
Method responseSOME/IP returns the result

This example shows successful subscription; method calls do not require event subscription, and events may occur independently of calls.

Best practices

  • Version service interfaces and keep backward compatibility rules.
  • Restrict who may offer which service — otherwise a compromised node can impersonate one.
  • Budget discovery traffic and startup time.

Common pitfalls

  • Using services for hard real-time control loops without timing analysis.

What it means for your discipline

  • HPC & application software Core

    Defines service interfaces, versions and deployment; most HPC application communication uses these protocols.

  • Networks & communication Core

    Plans service discovery traffic, multicast, QoS and bandwidth on the Ethernet backbone.

  • Cybersecurity Core

    SOME/IP has no built-in authentication; man-in-the-middle and spoofing of services are known risks. Protect with SecOC, TLS/DTLS, MACsec and access control.

  • Base software Partial

    AUTOSAR Classic and Adaptive provide SOME/IP stacks; ara::com maps services to SOME/IP or DDS.

  • E/E architecture Partial

    Service interfaces become the contracts between zones, central compute and the cloud.

  • Software update & OTA Partial

    Checks service-interface compatibility between updated applications and their providers and consumers; uses these dependencies to define coordinated installation and rollback groups.

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)
  • SOME/IP · DDS — Implements SOME/IP discovery and service messaging or DDS publish/subscribe with configured quality of service.
  • AUTOSAR Adaptive — Exposes service interfaces through ara::com and maps communication to configured SOME/IP or DDS bindings.
  • Security services — Restricts service access and supplies authentication and cryptographic protection where supported by the communication stack.
MCU-based ECU · AUTOSAR Classic
  • Communication — Provides Classic SOME/IP communication and service discovery for Ethernet services.
  • Application layer — Provides or consumes service interfaces whose versions and dependencies must remain compatible across updates.