SDV uses the scalable service-oriented-middleware (SOME/IP) to control messages. This middleware protocol is used by AAOS SDV as an external communication channel for automotive ECUs. SOME/IP is standardized by the AUTOSAR consortium and supports these features:
- Serialization
- Remote procedure call (RPC) and messaging
- Service discovery (SD)
- Publish/Subscribe (PUB/SUB)
- Segmentation of user datagram protocol (UDP) messages
Use our SOME/IP Broker to integrate new and existing SOME/IP-based external ECUs into your SDV ecosystem. Our production-ready integration of the SOME/IP Broker and sample code for an abstraction layer that works with the COVESA vSomeIP stack mean that all SDV-based services can communicate with SOME/IP-based external ECUs. Our AAOS SDV integration with SOME/IP consists of these elements:
SOME/IP broker. Move and translate messages back and forth between SDV and the external SOME/IP world. Google owns this element, which is delivered with SDV in production quality.
SOME/IP Stack abstraction layer. Layer that adapts a SOME/IP stack to our SDV SOME/IP Stack API. Initially, we'll deliver this element as sample code to work with the COVESA vSomeIP stack. Subsequently, you test and maintain the abstraction layer. You'll need to modify this layer to use another SOME/IP stack.
SOME/IP Stack. You integrate this with the abstraction layer. If we deliver this element to you, it was provided as a reference sample.