SOME/IP integration overview

You can integrate the Android Automotive OS (AAOS) Software-Defined Vehicle (SDV) with any implementation of the Scalable service-Oriented MiddlewarE over IP (SOME/IP) protocol, including custom partner stacks and the open-source COVESA vsomeip reference implementation. This integration lets AAOS SDV communicate seamlessly with AUTOSAR (Classic and Adaptive) electronic control units (ECUs) using built-in SDV CommStack primitives and VSIDL service definitions mapped from AUTOSAR ARXML or Franca IDL.

Key components and interactions with SDV include:

  • SOME/IP broker agent: Central component of an SDV and SOME/IP integration.

  • SOME/IP stack: Low-level SOME/IP transport logic abstracted in the Android interface definition language (AIDL) interface. Partners can plug in their own custom SOME/IP stack implementation, or use the open-source Connected Vehicle Systems Alliance (COVESA) vsomeip reference project.

  • VSIDL catalog provider: Supplies the required run-time type information (RTTI) for type translation. It also provides information about interfaces, topics, and their mappings, including the SOME/IP deployment configuration.

SOME/IP broker agent

The SDV SOME/IP broker agent (the broker) integrates the SOME/IP protocol into the software-defined vehicle (SDV) ecosystem. To enable cross-protocol communication, the broker serves primarily as a proxy for traffic between the SDV and AUTOSAR systems.

One or several instances of the broker create gateways for SOME/IP traffic. For more information, see Integrate SOME/IP with SDV.

The broker uses archetypes, including remote procedure calls (RPC) and data tunnel to facilitate communication. The broker handles service-specific data unknown at compile time. The broker relies on RTTI to communicate services. For more information, see Write a SOME/IP mapping file.