Scalable service-Oriented MiddlewarE over IP (SOME/IP)

Overview

SOME/IP is an automotive middleware solution that can be used for control messages. It was designed from beginning on to fit devices of different sizes and different operating systems perfectly. This includes small devices like cameras, AUTOSAR devices, and up to head units or telematics devices. It was also made sure that SOME/IP supports features of the Infotainment domain as well as that of other domains in the vehicle, allowing SOME/IP to be used for MOST replacement scenarios as well as more traditional CAN scenarios.

While IT solutions often only support single middleware features (e.g. RPC or Publish/Subscribe), SOME/IP supports a wide range of middleware features:

• Serialization – transforming into and from on-wire representation.
• Remote Procedure Call (RPC) – implementing remote invocation of functions.
• Service Discovery (SD) – dynamically finding and functionality and configuring its access.
• Publish/Subscribe (Pub/Sub) – dynamically configuring which data is needed and shall be sent to the client.
• Segmentation of UDP messages – allowing the transport of large SOME/IP messages over UDP without the need of fragmentation.

AUTOSAR support

SOME/IP is the only known middleware that was designed to be integrated into AUTOSAR 4.x releases:

• AUTOSAR 4.0 – basic support for SOME/IP messages already existing.
• AUTOSAR 4.1 – support for SOME/IP-SD and Publish/Subscribe was added.
• AUTOSAR 4.2 – the transformer was added for serialization as well as other optimizations.
• AUTOSAR 4.3 – fixing some transformer bugs, adding support for large UDP messages with SOME/IP-TP as well as SOME/IP-SD optimizations.

For AUTOSAR specifications see publications.