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.
This example shows SOME/IP discovery and request/response; event subscriptions and DDS publish/subscribe use different exchanges.
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.