You can integrate the software defined vehicle (SDV) with the scalable service-oriented middleware over IP (SOME/IP) protocol. This integration lets SDV communicate with Automotive Open System Architecture (AUTOSAR) services using built-in SDV CommStack primitives.
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. For example, the Connected Vehicle Systems Alliance (COVESA) provides the COVESA someip 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.