SOME/IP stands for Scalable service-Oriented MiddlewarE over IP and is a commonly used middleware solution in the automotive industry.
In MICROSAR QuickCom SOME/IP acts as the transport layer and can be used for both local communication as well as networked communication, including Ethernet connections.
NOTE: All SOME/IP services communicate via IP sockets. This means that even if two local applications (same ECU and using the same SOME/IP daemon) are configured to use the SOME/IP binding, the SOME/IP daemon will use the complete network stack for communication.
For networked communication SOME/IP is required and should be set in the deployment configuration.
SOME/IP Binding
The SOME/IP Binding sets up the communication channel of the service (IP address, port etc.). All SOME/IP services communicate via IP sockets.
SOME/IP Daemon
The SOME/IP daemon manages network communication, ensuring reliable message transmission and reception. The daemon is used as an ECU-specific broker for all SOME/IP-related communication and service discovery.
The connection between application and the local SOME/IP daemon is handled via IPC. IPC manages data flow between processes. Using this IPC channel, applications can offer, provide, and find service interfaces.
A single communication channel is used between the SOME/IP binding and the SOME/IP daemon for sending both SOME/IP messages (i.e. event/field notifications, method requests/responses) and control messages (e.g: OfferService).
