SNIP_ADAPTIVE_CRYPTO_FIGURE_Figure_13_2

Figure 13.2: Modeling of the SecOC secure communication deployment Class SecOcDeployment Package M2::AUTOSART emplates::AdaptivePlatform::Deployment::SecureCommunication Note The meta-class represents the ability to define a deployment of the SecOc communication protocol configuration settings to crypto module entities. Tags: atp.ManifestKind=MachineManifest; atp.Status=draft Base ARObject, Identifiable, MultilanguageReferrable, Referrable, SecureCommunication Deployment Attribute Type Mul. Kind Note secOcJobM apping SecOcJobMap ping * aggr Mapping of the JobRequirement to a concrete crypto job. Tags: atp.Status=draft Table 13.2: SecOcDeployment [TPS_MANI_03141] Mapping between SecOcJobRequirement and CryptoJob⌈ It is necessary to create a formal relation between a SecOcJobRequirement that is formulated in most cases by an OEM to a CryptoJob (which is typically defined in the domain of a supplier). The formalization of this relation is the SecOcJobMapping.⌋ (RS_MANI_00036, RS_MANI_00031) 411 of 602 — AUTOSAR CONFIDENTIAL — Document ID 713: AUTOSAR_TPS_ManifestSpecification