SNIP_ADAPTIVE_CRYPTO_FIGURE_Figure_15_2

Figure 15.2: Example for the usage of FunctionalClusterInteractsWithFunctionalClusterMapping In case of an application the model-path to an PortPrototype that is referencing a specific PortInterface defines the InstanceSpecifier that is used as identification towards the functional cluster implementation. In case of a FunctionalCluster interaction the PortPrototype is not available. Therefore the path to a mapping element that is derived from FunctionalClusterInteractsWithFunctionalClusterMapping is used to define the InstanceSpecifier that is used in the API call. The following figure shows the supported FunctionalClusterInteractsWithFunctionalClusterMapping subclasses that are available in the model. The Figure 15.2 shows an example for the usage of FunctionalClusterInteractsWithFunctionalClusterMapping. In this example, the Service Instance Manifest describes a configuration for a ProvidedSomeipServiceInstance that contains an Event that is protected by SecOC. Inside of the Service Instance Manifest the “RadarServiceBrakeEventKeyId” represents the FunctionalClusterInteractsWithFunctionalClusterMapping that is located in the ARPackage “FCInteractions”. These two elements in the manifest define the InstanceSpecifier “/RadarServiceBrakeEventKeyId” (see Figure 15.2) that is used in the Crypto API call from the Communication Management. This InstanceSpecifier is resolved to a concrete CryptoKeySlot with the information that is available in the Crypto target-configuration.