SNIP_ADAPTIVE_CAN_FIGURE_Figure_11_2

Figure 11.2: Deployment-related modeling of ServiceInterface Note that transport layer specific constraints on the uniqueness of protocol credentials still have to be respected, e.g. [constr_1723]. In figure 11.3, the use-case of having one PPortPrototype typed by one ServiceInterface and having several ProvidedSomeipServiceInstances on several VLANs is illustrated. It is possible to have different serviceInterfaceId, serviceInstanceId, and majorVersion values on each individual VLAN. But also the use-case of providing both service instances on the same VLAN would be supported, as long as their SOME/IP credentials are unique (see [constr_1723]). On different VLANs the service instance may also use the same SOME/IP credentials. But only in case that all service instance specific configuration settings (e.g. IP Multicast Address, SD Timing Properties) are exactly the same on both VLANs the same AdaptivePlatformServiceInstance can be used to model the communication on both VLANs. If, for example, the serviceInterfaceId, serviceInstanceId, and majorVersion values of a service instance on each VLAN are the same, but different IP Multicast Addresses are used on the different VLANs for the EventGroup transmission, then an individual VLAN specific modeling of AdaptivePlatformServiceInstance is necessary as shown in figure 11.3.