SOME/IP

The QNX Platform for ADAS supports the Scalable service-Oriented MiddlewarE over IP (SOME/IP) protocol.

SOME/IP is an automotive middleware solution designed to allow disparate operating systems and components to communicate. SOME/IP offers serialization, remote procedure calls, service discovery, and publish/subscribe for sending control messages between different components. SOME/IP allows components in your system to communicate with other systems using SOME/IP. For example, SOME/IP is used to communicate with AUTOSAR components, which are available as a separate experimental package.


Figure 1. SOME/IP on the QNX Platform for ADAS

One way you'll typically use SOME/IP in your applications is to communicate with other applications or services that run remotely on another module. You can also build applications that communicate with AUTOSAR components. With your installation of the QNX Platform for ADAS, you can run SOME/IP tests using the vsomeip implementation. You would run these tests to ensure that your local network settings are correct.

For more about using vsomeip, see the SOME/IP chapter in the System Services guide. For information about running the vsomeip tests on the reference image, see the Run SOME/IP tests chapter in the Getting Started guide.

Network topologies for SOME/IP

On the QNX Platform for ADAS, the primary use for SOME/IP is to allow QNX Neutrino-based processes to communicate with AUTOSAR software components, however, SOME/IP can also be used by QNX Neutrino-based processes (or applications) to communicate amongst themselves. Here are the typical network topologies for using SOME/IP:
  • Processes that run on different modules that communicate with each other using SOME/IP.
    Figure 2. QNX Neutrino-based processes communicating while running on different modules.
  • Processes that run on the same module using SOME/IP. Available as an experimental package, AUTOSAR components can run on the a module built with the QNX Platform for ADAS. Contact your QNX Software Systems representative for more information.
    Figure 3. QNX Neutrino-based processes communicating with each other on the same module.
  • Process that communicates with an AUTOSAR Software component that's not on the same module.
    Figure 4. QNX Neutrino-based process communicating with AUTOSAR Software components.