SNIP_ADAPTIVE_CAN_FIGURE_Figure_7_9_COMMUNICATIONMANAGEMENT

Figure 7.9: Example serialization settings The modeling of the signal-based communication and the mapping between the individual elements of a ServiceInterface to the corresponding ISignalTriggerings is defined in the chapter “Signal-based communication” in [5]. [SWS_CM_10174] Mix of signal-based and SOME/IP communication Upstream requirements: RS_CM_00204 ⌈A combination of signal-based network binding and SOME/IP network binding shall be possible in a way to support the reception of a mix of signal-based communication and SOME/IP communication within a single UDP datagram or a single TCP stream on one UDP/TCP socket. Such a mix can occur when using [19] with enabled PDU-header option on the sender side. ⌋ This allows to define the transport of messages from several services on the same socket, regardless of the serialization setting. Thus messages using the pure SOME/IP network binding can be transported together with messages using the signal-based network binding on the same socket. Also one service - which consists of events with different serialization technologies (i.e. someip and signalBased) - shall be able to be transported on the same socket (this is covered by the signal-based network binding). Based on [SWS_CM_10000]: