SNIP_ADAPTIVE_CRYPTO_FIGURE_Figure_3_58

Figure 3.58: CryptoInterfaces for modeling of the interaction of the Application with the Crypto software In contrast to the conventions on the AUTOSAR classic Platform, these CryptoInterfaces are only used on the application side of this communication relation. The Crypto API is described in [13]. The model-path to an RPortPrototype that is referencing a CryptoInterface is provided by the ara::core::InstanceSpecifier that defines the logical local name used by the application developer in the API call. This local ara::core::InstanceSpecifier is translated at runtime with the information from the deployment model to a specific crypto object, e.g. CryptoKeySlot in a CryptoKeyStorage.