Kanonische Schaubilder & Diagramme (36,908) — Zeige erste 1,000

Vollständiger, inhaltsadressierter Katalog aller aus den AUTOSAR-Spezifikationen extrahierten Vektorgrafiken und Diagramme mit präzisen Seitenausschnitten, OCR-Text und KI-generierten Fachbeschreibungen.

Schaubild & Kennung	Dokumente	Releases	KI-Status
Figure 6.1: SOME/IP Service Insterface Deployment FIG-0213812fa9f7a5c0	AUTOSAR_AP_EXP_ARAComAPI	R25-11	✓ Beschrieben
Figure 7.6: meta-model to Implementation FIG-02ba3900e9f20d06	AUTOSAR_AP_EXP_ARAComAPI, AUTOSAR_EXP_ARAComAPI	R18-10_R4.4.0_R1.5.0R18-10-1R19-03R19-11+6	✓ Beschrieben
Figure 6.1: SOME/IP Service Insterface Deployment FIG-07c541a79eaff051	AUTOSAR_AP_EXP_ARAComAPI	R24-11	✓ Beschrieben
Figure 6.7: DDS Service Interface Deployment FIG-14b386693d05da3b	AUTOSAR_AP_EXP_ARAComAPI	R23-11	✓ Beschrieben
Figure 6.5: Service Discovery FIG-15f71db1fb196760	AUTOSAR_AP_EXP_ARAComAPI, AUTOSAR_EXP_ARAComAPI	R22-11R23-11R24-11	✓ Beschrieben
Figure 7.13: Multiple usage of the same service instance manifest for an abstract binding FIG-1711e373d87bd2e0	AUTOSAR_AP_EXP_ARAComAPI, AUTOSAR_EXP_ARAComAPI	R18-10_R4.4.0_R1.5.0R18-10-1R19-03R19-11+6	✓ Beschrieben
Figure 6.14: CG Client Service Interface Description, example PowerMode FIG-22844be4cf62212c	AUTOSAR_AP_EXP_ARAComAPI, AUTOSAR_AP_SWS_CommunicationManagement (+2)	R20-11R21-11R22-11R23-11+1	✓ Beschrieben
Figure 6.2: Service Instance to Port Prototype Mapping FIG-2c1f37be3ec9f9aa	AUTOSAR_AP_EXP_ARAComAPI	R24-11	✓ Beschrieben
Figure 6.9: DDS Provided Service Instance Deployment FIG-31706bbe1f5ec49f	AUTOSAR_AP_EXP_ARAComAPI	R25-11	✓ Beschrieben
Figure 7.3: Simple Multi-Binding intra AP example FIG-339dfa51f77c8c63	AUTOSAR_AP_EXP_ARAComAPI, AUTOSAR_EXP_ARAComAPI	R18-03_R1.4.0R18-10_R4.4.0_R1.5.0R18-10-1R19-03+7	✓ Beschrieben
Figure 6.7: DDS Service Interface Deployment FIG-3d69200af1719819	AUTOSAR_AP_EXP_ARAComAPI	R24-11	✓ Beschrieben
Figure 7.1: Centralized discovery approach FIG-3f3700acf36ad469	AUTOSAR_AP_EXP_ARAComAPI, AUTOSAR_EXP_ARAComAPI	R18-10_R4.4.0_R1.5.0R18-10-1R19-03R19-11+6	✓ Beschrieben
Figure 6.1: SOME/IP Service Insterface Deployment FIG-40e5cefbb661457e	AUTOSAR_AP_EXP_ARAComAPI	R23-11	✓ Beschrieben
Figure 7.7: Multiple Instantiation in Implementation Contexts FIG-42642e42f482688b	AUTOSAR_AP_EXP_ARAComAPI, AUTOSAR_EXP_ARAComAPI	R18-10_R4.4.0_R1.5.0R18-10-1R19-03R19-11+6	✓ Beschrieben
Figure 6.3: Service InstanceToMachineMapping FIG-431810d7f8d99675	AUTOSAR_AP_EXP_ARAComAPI	R25-11	✓ Beschrieben
Figure 5.2: Event Buffering Approaches FIG-436d47d5ddef3804	AUTOSAR_AP_EXP_ARAComAPI, AUTOSAR_EXP_ARAComAPI	R20-11R21-11R22-11R23-11+2	✓ Beschrieben
Figure 5.1: Auto Updating of Proxy Instance FIG-4458bf8454b62982	AUTOSAR_AP_EXP_ARAComAPI, AUTOSAR_EXP_ARAComAPI	R18-10_R4.4.0_R1.5.0R18-10-1R19-03R22-11+3	✓ Beschrieben
Figure 4.3: ara::com method based communication FIG-4cf7a627ee546cd7	AUTOSAR_AP_EXP_ARAComAPI, AUTOSAR_EXP_ARAComAPI	R22-11R23-11R24-11R25-11	✓ Beschrieben
Figure 6.13: CG Server Service Interface Description, example PowerMode FIG-5ce36384c7b8ffcb	AUTOSAR_AP_EXP_ARAComAPI, AUTOSAR_AP_SWS_CommunicationManagement (+1)	R20-11R21-11R22-11R23-11+1	✓ Beschrieben
Figure 6.9: DDS Provided Service Instance Deployment FIG-6659fd5a7caa2a11	AUTOSAR_AP_EXP_ARAComAPI	R24-11	✓ Beschrieben
Figure 7.2: Distributed discovery approach FIG-70cfee0f187bfb6b	AUTOSAR_AP_EXP_ARAComAPI, AUTOSAR_EXP_ARAComAPI	R18-10_R4.4.0_R1.5.0R18-10-1R19-03R19-11+6	✓ Beschrieben
Figure 7.8: Instantiation of Adaptive Applications in Deployment FIG-717d6e271d54d985	AUTOSAR_AP_EXP_ARAComAPI, AUTOSAR_EXP_ARAComAPI	R18-10_R4.4.0_R1.5.0R18-10-1R19-03R19-11+6	✓ Beschrieben
Figure 6.5: Service Discovery FIG-731aeaabf8b03532	AUTOSAR_AP_EXP_ARAComAPI	R25-11	✓ Beschrieben
Figure 7.5: SOME/IP Bridge FIG-77a52549de915208	AUTOSAR_AP_EXP_ARAComAPI, AUTOSAR_EXP_ARAComAPI	R18-10_R4.4.0_R1.5.0R18-10-1R19-03R19-11+6	✓ Beschrieben
Figure 6.4: Network Connection FIG-7ab3fa9b1d8a79b2	AUTOSAR_AP_EXP_ARAComAPI	R25-11	✓ Beschrieben
Figure 6.6: SOME/IP Required Service Instance Deployment FIG-7bb01ebcac94827c	AUTOSAR_AP_EXP_ARAComAPI	R25-11	✓ Beschrieben
Figure 6.10: CG Template Service Interface Descritpion, example PowerMode FIG-8e3e17175147377d	AUTOSAR_AP_EXP_ARAComAPI	R24-11	✓ Beschrieben
Figure 7.11: Find Service using abstract network binding - ANY FIG-93c3c6bf6a0c7b72	AUTOSAR_AP_EXP_ARAComAPI, AUTOSAR_EXP_ARAComAPI	R18-10_R4.4.0_R1.5.0R18-10-1R19-03R19-11+6	✓ Beschrieben
Figure 6.4: Network Connection FIG-94157b47447c449b	AUTOSAR_AP_EXP_ARAComAPI	R24-11	✓ Beschrieben
Figure 4.1: Proxy Skeleton Pattern FIG-9c319c60ffab4d25	AUTOSAR_AP_EXP_ARAComAPI, AUTOSAR_EXP_ARAComAPI	R22-11R23-11R24-11	✓ Beschrieben
Figure 7.10: Find Service using abstract network binding FIG-9eae3e9834bdccf0	AUTOSAR_AP_EXP_ARAComAPI, AUTOSAR_EXP_ARAComAPI	R18-10_R4.4.0_R1.5.0R18-10-1R19-03R19-11+6	✓ Beschrieben
Figure 6.6: SOME/IP Required Service Instance Deployment FIG-a40d8d34f04c5d2d	AUTOSAR_AP_EXP_ARAComAPI	R23-11	✓ Beschrieben
Figure 6.6: SOME/IP Required Service Instance Deployment FIG-ab3a2621d8c2715a	AUTOSAR_AP_EXP_ARAComAPI	R24-11	✓ Beschrieben
Figure 6.11: Communication Group Service Interfaces Relationship FIG-af50260fe4a6d21f	AUTOSAR_AP_EXP_ARAComAPI	R23-11R24-11	✓ Beschrieben
Figure 4.1: Proxy Skeleton Pattern FIG-b0a1946cfe7c2c83	AUTOSAR_AP_EXP_ARAComAPI	R25-11	✓ Beschrieben
Figure 6.8: SOME/IP Provided Service Instance Deployment FIG-b6f6e35227dfe429	AUTOSAR_AP_EXP_ARAComAPI	R24-11R25-11	✓ Beschrieben
Figure 7.4: Multi-Binding local and network example FIG-bfd18ea992de4c05	AUTOSAR_AP_EXP_ARAComAPI, AUTOSAR_EXP_ARAComAPI	R18-10_R4.4.0_R1.5.0R18-10-1R19-03R19-11+6	✓ Beschrieben
Figure 6.2: Service Instance to Port Prototype Mapping FIG-c186783e5ce87096	AUTOSAR_AP_EXP_ARAComAPI	R25-11	✓ Beschrieben
Figure 7.12: Skeleton creation using abstract network bindings FIG-d02cb273ea3bbe9a	AUTOSAR_AP_EXP_ARAComAPI, AUTOSAR_EXP_ARAComAPI	R18-10_R4.4.0_R1.5.0R18-10-1R19-03R19-11+6	✓ Beschrieben
Figure 6.4: Network Connection FIG-d214b329251bdf2b	AUTOSAR_AP_EXP_ARAComAPI	R23-11	✓ Beschrieben
Figure 7.9: InstanceIds in Deployment FIG-d86543536ce97b47	AUTOSAR_AP_EXP_ARAComAPI, AUTOSAR_EXP_ARAComAPI	R18-10_R4.4.0_R1.5.0R18-10-1R19-03R19-11+6	✓ Beschrieben
Figure 5.3: Communication Group Abstract for State Management FIG-d9093ee7d681574d	AUTOSAR_AP_EXP_ARAComAPI	R23-11R24-11	✓ Beschrieben
Figure 6.10: CG Template Service Interface Descritpion, example PowerMode FIG-e04f5faee4cea8f3	AUTOSAR_AP_EXP_ARAComAPI	R23-11	✓ Beschrieben
Figure 6.9: DDS Provided Service Instance Deployment FIG-e91f502711eb84c3	AUTOSAR_AP_EXP_ARAComAPI	R23-11	✓ Beschrieben
Figure 4.2: ara::com event based communication FIG-eca7682dbb95f27b	AUTOSAR_AP_EXP_ARAComAPI, AUTOSAR_EXP_ARAComAPI	R22-11R23-11R24-11R25-11	✓ Beschrieben
Figure 6.2: Service Instance to Port Prototype Mapping FIG-ef0473d23cd9f99f	AUTOSAR_AP_EXP_ARAComAPI	R23-11	✓ Beschrieben
Figure 6.7: DDS Service Interface Deployment FIG-f284efb795f82d6b	AUTOSAR_AP_EXP_ARAComAPI	R25-11	✓ Beschrieben
Figure 6.3: Service InstanceToMachineMapping FIG-f47547993e1eed6f	AUTOSAR_AP_EXP_ARAComAPI	R24-11	✓ Beschrieben
Figure 6.3: Service InstanceToMachineMapping FIG-fc8d0cf461584413	AUTOSAR_AP_EXP_ARAComAPI	R23-11	✓ Beschrieben
Figure 6.8: SOME/IP Provided Service Instance Deployment FIG-fdd1bfd0e01c350c	AUTOSAR_AP_EXP_ARAComAPI	R23-11	✓ Beschrieben
Figure 1.1: Current AUTOSAR-Rust communication diagram FIG-01de3c9b5d503dec	AUTOSAR_AP_EXP_ARARustApplications	R23-11R24-11	✓ Beschrieben
Figure 6.7: Simple representation of generic trait and implementation FIG-0a43a3ba9a7f00c0	AUTOSAR_AP_EXP_ARARustApplications	R25-11	✓ Beschrieben
Figure 6.12: Slow method invocation FIG-0c5c943de179f7c7	AUTOSAR_AP_EXP_ARARustApplications	R23-11R24-11R25-11	✓ Beschrieben
Figure 6.8: Detailed representation of generic trait and implementation FIG-199b911f6d5f62dd	AUTOSAR_AP_EXP_ARARustApplications	R25-11	✓ Beschrieben
Figure 6.5: Trait and implementation FIG-221e855edb7f7922	AUTOSAR_AP_EXP_ARARustApplications	R23-11R24-11	✓ Beschrieben
Figure 6.7: Simple representation of generic trait and implementation FIG-33ee8788f5e4b3d7	AUTOSAR_AP_EXP_ARARustApplications	R23-11R24-11	✓ Beschrieben
Figure 6.11: Fast method invocation FIG-3642f6df4531357a	AUTOSAR_AP_EXP_ARARustApplications	R23-11R24-11R25-11	✓ Beschrieben
Figure 6.6: Simplified representation of trait and implementation FIG-4f6a4864103b8be6	AUTOSAR_AP_EXP_ARARustApplications	R23-11R24-11R25-11	✓ Beschrieben
Figure 6.3: Enumeration FIG-505387312eb6e89a	AUTOSAR_AP_EXP_ARARustApplications	R23-11R24-11	✓ Beschrieben
Figure 4.1: async function execution FIG-6cc03f7a354d424c	AUTOSAR_AP_EXP_ARARustApplications	R23-11R24-11R25-11	✓ Beschrieben
Figure 6.1: Module FIG-6d560d5f7df085c7	AUTOSAR_AP_EXP_ARARustApplications	R23-11R24-11	✓ Beschrieben
Figure 6.5: Trait and implementation FIG-6e0fd1db89d187a3	AUTOSAR_AP_EXP_ARARustApplications	R25-11	✓ Beschrieben
Figure 6.9: Calling a Method FIG-703630a2019e2d20	AUTOSAR_AP_EXP_ARARustApplications	R23-11R24-11	✓ Beschrieben
Figure 6.1: Module FIG-7fb7288cd7281438	AUTOSAR_AP_EXP_ARARustApplications	R25-11	✓ Beschrieben
Figure 1.1: Current AUTOSAR-Rust communication diagram FIG-99fd7222eea0dcff	AUTOSAR_AP_EXP_ARARustApplications	R25-11	✓ Beschrieben
Figure 6.8: Detailed representation of generic trait and implementation FIG-a6c3ad4b50e0316a	AUTOSAR_AP_EXP_ARARustApplications	R23-11R24-11	✓ Beschrieben
Figure 6.9: Calling a Method FIG-a83123ba78ad3af8	AUTOSAR_AP_EXP_ARARustApplications	R25-11	✓ Beschrieben
Figure 6.4: Type alias FIG-a9e7669da1254646	AUTOSAR_AP_EXP_ARARustApplications	R25-11	✓ Beschrieben
Figure 6.10: Creating a service FIG-ad99fe1d2a813209	AUTOSAR_AP_EXP_ARARustApplications	R23-11R24-11R25-11	✓ Beschrieben
Figure 6.4: Type alias FIG-d33b7bd96c588a8f	AUTOSAR_AP_EXP_ARARustApplications	R23-11R24-11	✓ Beschrieben
Figure 6.2: Struct and inherent implementation FIG-d882559dba464f96	AUTOSAR_AP_EXP_ARARustApplications	R23-11R24-11R25-11	✓ Beschrieben
Figure 6.3: Enumeration FIG-e0485d3d566909e8	AUTOSAR_AP_EXP_ARARustApplications	R25-11	✓ Beschrieben
Figure 7.1: The Abstract protocol flow. (Source: [3]; Colored boxes are added) FIG-2dbf0904ea647868	AUTOSAR_AP_EXP_AutomotiveAPI	R24-11R25-11	✓ Beschrieben
Figure 5.2: Vehicle provides data via the Cloud Service FIG-4a4ec36759b7750d	AUTOSAR_AP_EXP_AutomotiveAPI	R24-11R25-11	✓ Beschrieben
Figure 5.3: In-Vehicle Application Requesting VSS Data FIG-506099fffd3b245e	AUTOSAR_AP_EXP_AutomotiveAPI	R24-11R25-11	✓ Beschrieben
Figure 6.3: Example of Cascaded VISS server deployment FIG-5b8fcde80a6c5807	AUTOSAR_AP_EXP_AutomotiveAPI	R24-11R25-11	✓ Beschrieben
Figure 4.2: Automotive API Gateway. FIG-67761fef374b07ed	AUTOSAR_AP_EXP_AutomotiveAPI	R24-11R25-11	✓ Beschrieben
Figure 6.1: A cloud server requesting VSS data through a web services interface FIG-6ad54c2fed12a6ef	AUTOSAR_AP_EXP_AutomotiveAPI	R24-11R25-11	✓ Beschrieben
Figure 1.1: Automotive API Gateway as a new Vehicle Service Functional Cluster in the Adaptive Platform architecture. FIG-784fc3af99dbb7cf	AUTOSAR_AP_EXP_AutomotiveAPI	R24-11R25-11	✓ Beschrieben
Figure 4.1: Example: VSS Signal Vehicle Speed FIG-7abc075971be5c7e	AUTOSAR_AP_EXP_AutomotiveAPI	R25-11	✓ Beschrieben
Figure 6.2: Multiple Automotive API Gateway deployment FIG-7b41336921542307	AUTOSAR_AP_EXP_AutomotiveAPI	R24-11R25-11	✓ Beschrieben
Figure 5.1: Connectivity of vehicle and remote devices with short-range communication technologies FIG-8b58ca39922486fc	AUTOSAR_AP_EXP_AutomotiveAPI	R24-11R25-11	✓ Beschrieben
Figure 4.1: Example: VSS Signal Vehicle Speed FIG-8dd9495c2cd2d5b4	AUTOSAR_AP_EXP_AutomotiveAPI	R24-11	✓ Beschrieben
Figure 4.3: The Automotive API Gateway Connecting VSS data to in-vehicle services. FIG-f30ec10fc6e13283	AUTOSAR_AP_EXP_AutomotiveAPI	R24-11R25-11	✓ Beschrieben
Figure 4.1: Communication with IPsec in AUTOSAR Adaptive Platform FIG-1bde706da9d35beb	AUTOSAR_AP_EXP_IPsecImplementationGuidelines, AUTOSAR_EXP_IPsecImplementationGuidelines	R18-10_R4.4.0_R1.5.0R18-10-1R19-03R19-11+4	✓ Beschrieben
Figure 4.1: Communication with IPsec in AUTOSAR Adaptive Platform FIG-21af9f5f1f5a475c	AUTOSAR_AP_EXP_IPsecImplementationGuidelines	R24-11R25-11	✓ Beschrieben
Figure 2.3: SA creation with IKE for network traffic protection FIG-30b128d81a0493c6	AUTOSAR_AP_EXP_IPsecImplementationGuidelines, AUTOSAR_EXP_IPsecImplementationGuidelines (+1)	R18-10_R4.4.0_R1.5.0R18-10-1R19-03R19-11+6	✓ Beschrieben
Figure 2.2: Encapsulating Security Payload (ESP) frame FIG-99b43c29687b5672	AUTOSAR_AP_EXP_IPsecImplementationGuidelines	R24-11R25-11	✓ Beschrieben
Figure 2.2: Encapsulating Security Payload (ESP) frame FIG-cbf9ab7a3d997fd5	AUTOSAR_AP_EXP_IPsecImplementationGuidelines, AUTOSAR_EXP_IPsecImplementationGuidelines	R18-10_R4.4.0_R1.5.0R18-10-1R19-03R19-11+4	✓ Beschrieben
Figure 2.1: Authentication Header (AH) frame FIG-d3c828224d2b3b1e	AUTOSAR_AP_EXP_IPsecImplementationGuidelines, AUTOSAR_EXP_IPsecImplementationGuidelines	R18-10_R4.4.0_R1.5.0R18-10-1R19-03R19-11+6	✓ Beschrieben
Figure 3.3: Access Control by Policy Enforcement FIG-8ddb99f75ce1eee7	AUTOSAR_AP_EXP_IdentityAndAccessManagement	R23-11R24-11R25-11	✓ Beschrieben
Figure 3.1: AUTOSAR IAM FIG-f03d0924bbeb068b	AUTOSAR_AP_EXP_IdentityAndAccessManagement	R23-11R24-11R25-11	✓ Beschrieben
Figure 3.2: Access Matrix FIG-f657a2b333ad9bfd	AUTOSAR_AP_EXP_IdentityAndAccessManagement	R23-11R24-11R25-11	✓ Beschrieben
Figure 3.4: IAM Sequence FIG-f990ac5d430002e6	AUTOSAR_AP_EXP_IdentityAndAccessManagement	R23-11R24-11R25-11	✓ Beschrieben
Figure 5.4: StateMachine interactions FIG-00f48139634d3cff	AUTOSAR_AP_EXP_InterfacesGuidelines	R24-11	✓ Beschrieben
Figure 9.2: Client sequence diagram FIG-11815ec592f84b3d	AUTOSAR_AP_EXP_InterfacesGuidelines, AUTOSAR_EXP_ARAComAPI	R20-11R21-11R22-11R23-11+2	✓ Beschrieben
Figure 5.1: StateMachine TransitionRequestTable FIG-18626f1a5310b812	AUTOSAR_AP_EXP_InterfacesGuidelines	R24-11R25-11	✓ Beschrieben
Figure 5.3: StateMachine ErrorTable FIG-1df3280b3c679c07	AUTOSAR_AP_EXP_InterfacesGuidelines	R24-11	✓ Beschrieben
Figure 5.2: StateMachine TransitionRequestTable FIG-3593c85c2dc45bf5	AUTOSAR_AP_EXP_InterfacesGuidelines	R23-11	✓ Beschrieben
Figure 5.2: Extended StateMachine TransitionRequestTable FIG-8e73a09b5413d9dd	AUTOSAR_AP_EXP_InterfacesGuidelines	R24-11R25-11	✓ Beschrieben
Figure 9.1: Client sequence diagram FIG-9c1fe75b0acd93ac	AUTOSAR_AP_EXP_InterfacesGuidelines, AUTOSAR_EXP_ARAComAPI	R20-11R21-11R22-11R23-11+2	✓ Beschrieben
Figure 5.4: StateMachine interactions FIG-aa9d23c13952c189	AUTOSAR_AP_EXP_InterfacesGuidelines	R25-11	✓ Beschrieben
Figure 5.5: StateMachine interactions FIG-b41c95d6d67560c1	AUTOSAR_AP_EXP_InterfacesGuidelines	R23-11	✓ Beschrieben
Figure 5.3: Extended StateMachine TransitionRequestTable FIG-b71232a939d57586	AUTOSAR_AP_EXP_InterfacesGuidelines	R23-11	✓ Beschrieben
Figure 6.1: Persistency functionality overview FIG-c7e154b22178830b	AUTOSAR_AP_EXP_InterfacesGuidelines	R23-11R24-11R25-11	✓ Beschrieben
Figure 5.3: StateMachine ErrorTable FIG-d6f7f02861ede98a	AUTOSAR_AP_EXP_InterfacesGuidelines	R25-11	✓ Beschrieben
Figure 5.4: StateMachine ErrorTable FIG-f8a88e60a086a77a	AUTOSAR_AP_EXP_InterfacesGuidelines	R23-11	✓ Beschrieben
Figure 5.1: A basic application State transition example FIG-fd42f6405075e87d	AUTOSAR_AP_EXP_InterfacesGuidelines	R23-11	✓ Beschrieben
Figure 6.1: Communication with MKA Module in AUTOSAR Adaptive Platform. FIG-6b562a49482bbd5d	AUTOSAR_AP_EXP_MACsec	R23-11R24-11R25-11	✓ Beschrieben
Figure 4.1: Ethernet Frame including MACsec integrity and optionally confidentiality protection. FIG-6ce9b66544690eba	AUTOSAR_AP_EXP_MACsec	R23-11R24-11R25-11	✓ Beschrieben
Figure 4.3: MACsec Key Agreement sequence with pre-shared key. FIG-9f7ac14beefc7a7c	AUTOSAR_AP_EXP_MACsec	R23-11R24-11R25-11	✓ Beschrieben
Figure 4.2: MACsec communication between Peer1 and Peer2, with a switch in between. FIG-d49e7014211cf51f	AUTOSAR_AP_EXP_MACsec	R23-11R24-11R25-11	✓ Beschrieben
Figure 5.3: CPU/co-processor-model example FIG-0f20fb2c19212993	AUTOSAR_AP_EXP_ParallelProcessingGuidelines, AUTOSAR_EXP_ParallelProcessingGuidelines	R21-11R22-11R23-11R24-11+1	✓ Beschrieben
Figure 5.1: Parallel processing consumer-provider layered view example FIG-697dc6eaa3e4bc74	AUTOSAR_AP_EXP_ParallelProcessingGuidelines, AUTOSAR_EXP_ParallelProcessingGuidelines	R21-11R22-11R23-11R24-11+1	✓ Beschrieben
Figure 5.2: Accelerator-model example FIG-d82699558e4ca64c	AUTOSAR_AP_EXP_ParallelProcessingGuidelines, AUTOSAR_EXP_ParallelProcessingGuidelines	R21-11R22-11R23-11R24-11+1	✓ Beschrieben
Figure 7.3: StateMachine concept - Big picture FIG-044f95f33d9940a6	AUTOSAR_AP_EXP_PlatformDesign	R23-11R24-11R25-11	✓ Beschrieben
Figure 17.1: PHM interface with other components FIG-0812d4448e7e28c7	AUTOSAR_AP_EXP_PlatformDesign	R24-11R25-11	✓ Beschrieben
Figure 13.9: V-UCM state machine FIG-09024b0d4f60fc36	AUTOSAR_AP_EXP_PlatformDesign	R25-11	✓ Beschrieben
Figure 13.4: Overview Vehicle Package FIG-0a2bc58fd1d9f585	AUTOSAR_AP_EXP_PlatformDesign	R25-11	✓ Beschrieben
Figure 4.3: Safety features FIG-0bc498c31e33bd5a	AUTOSAR_AP_EXP_PlatformDesign	R25-11	✓ Beschrieben
Figure 7.1: State Management interactions FIG-1241c870c83b74df	AUTOSAR_AP_EXP_PlatformDesign	R25-11	✓ Beschrieben
Figure 17.2: Safe Hardware Acceleration integration to AUTOSAR AP FIG-14077863b9358468	AUTOSAR_AP_EXP_PlatformDesign	R25-11	✓ Beschrieben
Figure 13.10: State Management during an update process FIG-166629c1f00adf68	AUTOSAR_AP_EXP_PlatformDesign, AUTOSAR_EXP_PlatformDesign	R21-11R22-11R23-11	✓ Beschrieben
Figure 4.2: Supported protocols FIG-1f8250adc9913f06	AUTOSAR_AP_EXP_PlatformDesign	R24-11	✓ Beschrieben
Figure 13.6: Packages distribution to vehicle FIG-212a25a3fee1ec26	AUTOSAR_AP_EXP_PlatformDesign, AUTOSAR_EXP_PlatformDesign	R21-11R22-11R23-11R24-11+1	✓ Beschrieben
Figure 3.1: Exemplary deployment of different platforms FIG-224984e466a22160	AUTOSAR_AP_EXP_PlatformDesign	R25-11	✓ Beschrieben
Figure 4.1: AP architecture logical view FIG-2f77eda5f6ed03a6	AUTOSAR_AP_EXP_PlatformDesign	R24-11	✓ Beschrieben
Figure 24.1: Sensor Interfaces Architecture FIG-364cf74c60c8f24c	AUTOSAR_AP_EXP_PlatformDesign	R25-11	✓ Beschrieben
Figure 9.2: Single Diagnostic Address Per Machine FIG-36eb776a2765ccf4	AUTOSAR_AP_EXP_PlatformDesign	R23-11R24-11R25-11	✓ Beschrieben
Figure 9.1: One Diagnostic Address Per SWCL FIG-392d731dfa54cbe1	AUTOSAR_AP_EXP_PlatformDesign	R23-11R24-11R25-11	✓ Beschrieben
Figure 7.7: Platform Health Management and the environment FIG-3f916896ebed8857	AUTOSAR_AP_EXP_PlatformDesign, AUTOSAR_AP_SWS_PlatformHealthManagement (+2)	R21-11R22-11R23-11	✓ Beschrieben
Figure 4.3: Safety features FIG-411bb6c884204884	AUTOSAR_AP_EXP_PlatformDesign	R23-11	✓ Beschrieben
Figure 4.1: AP architecture logical view FIG-43c51c0572bbee89	AUTOSAR_AP_EXP_PlatformDesign	R25-11	✓ Beschrieben
Figure 10.1: Typical usage of Persistency within an Adaptive Application FIG-44434cd85b3d1e50	AUTOSAR_AP_EXP_PlatformDesign	R24-11	✓ Beschrieben
Figure 19.1: Distributed IDS Architecture FIG-4ae7357b99bb35fe	AUTOSAR_AP_EXP_PlatformDesign, AUTOSAR_EXP_PlatformDesign	R21-11R22-11R23-11R24-11+1	✓ Beschrieben
Figure 13.5: Packaging steps FIG-4c816cc65f163333	AUTOSAR_AP_EXP_PlatformDesign, AUTOSAR_EXP_PlatformDesign	R21-11R22-11R23-11R24-11+1	✓ Beschrieben
Figure 15.1: Crypto Stack - Reference Architecture FIG-4d1e3209985b6bae	AUTOSAR_AP_EXP_PlatformDesign, AUTOSAR_EXP_PlatformDesign	R21-11R22-11R23-11R24-11+1	✓ Beschrieben
Figure 4.1: Master/Client example across Classic, Adaptive and Non-AUTOSAR platforms. FIG-4f99a091305f0ed9	AUTOSAR_AP_EXP_PlatformDesign, AUTOSAR_EXP_PlatformDesign (+1)	R21-11R22-11R23-11R25-11	✓ Beschrieben
Figure 8.1: Service-oriented communication FIG-54211d88485f1ac9	AUTOSAR_AP_EXP_PlatformDesign, AUTOSAR_EXP_PlatformDesign	R21-11R22-11R23-11R24-11+1	✓ Beschrieben
Figure 13.8: Overview of Processing and Activation of Software Package FIG-5423a621f11923ac	AUTOSAR_AP_EXP_PlatformDesign	R24-11R25-11	✓ Beschrieben
Figure 4.4: Security features FIG-5f98a23c342bd276	AUTOSAR_AP_EXP_PlatformDesign	R23-11	✓ Beschrieben
Figure 15.2: CKI Key Management Interactions FIG-64d91bb6ae52a86d	AUTOSAR_AP_EXP_PlatformDesign, AUTOSAR_EXP_PlatformDesign	R21-11R22-11R23-11R24-11+1	✓ Beschrieben
Figure 13.3: Overview Backend Package FIG-6972b75a84221cd7	AUTOSAR_AP_EXP_PlatformDesign, AUTOSAR_EXP_PlatformDesign	R21-11R22-11R23-11R24-11+1	✓ Beschrieben
Figure 7.1: State Management interactions FIG-6a6e44465cefceaf	AUTOSAR_AP_EXP_PlatformDesign	R23-11R24-11	✓ Beschrieben
Figure 13.2: Overview Software Package FIG-6c3e34a64c193ed0	AUTOSAR_AP_EXP_PlatformDesign, AUTOSAR_EXP_PlatformDesign	R21-11R22-11R23-11R24-11+1	✓ Beschrieben
Figure 13.9: V-UCM state machine FIG-6ecbddea87a36dbc	AUTOSAR_AP_EXP_PlatformDesign	R23-11	✓ Beschrieben
Figure 4.2: Supported protocols FIG-6fedae82879f81d1	AUTOSAR_AP_EXP_PlatformDesign	R23-11	✓ Beschrieben
Figure 20.1: Firewall pattern matching algorithm FIG-744532f540235970	AUTOSAR_AP_EXP_PlatformDesign, AUTOSAR_EXP_PlatformDesign	R22-11R23-11R24-11R25-11	✓ Beschrieben
Figure 4.2: Supported protocols FIG-74a82a5e356adc01	AUTOSAR_AP_EXP_PlatformDesign	R25-11	✓ Beschrieben
Figure 4.4: Security features FIG-778fe81a41f276c0	AUTOSAR_AP_EXP_PlatformDesign	R25-11	✓ Beschrieben
Figure 3.2: Exemplary interactions of AP and CP FIG-7f07f437b70da592	AUTOSAR_AP_EXP_PlatformDesign, AUTOSAR_EXP_PlatformDesign	R21-11R22-11R23-11R24-11+1	✓ Beschrieben
Figure 13.8: Overview of Processing and Activation of Software Package FIG-7f6e0aab02be3112	AUTOSAR_AP_EXP_PlatformDesign	R23-11	✓ Beschrieben
Figure 13.1: Vehicle Update Architecture FIG-8312839eac5a8e66	AUTOSAR_AP_EXP_PlatformDesign	R25-11	✓ Beschrieben
Figure 7.2: Overview of ’lightweight’ StateMachine concept FIG-83d07987e6012b7b	AUTOSAR_AP_EXP_PlatformDesign	R24-11	✓ Beschrieben
Figure 22.1: The Automotive API Gateway Connecting VSS data to in-vehicle services FIG-86b7a16691dd7e32	AUTOSAR_AP_EXP_PlatformDesign	R24-11R25-11	✓ Beschrieben
Figure 6.1: AP start-up sequence FIG-8af2b819c3b6e6ab	AUTOSAR_AP_EXP_PlatformDesign, AUTOSAR_EXP_PlatformDesign	R21-11R22-11R23-11R24-11+1	✓ Beschrieben
Figure 13.1: Vehicle Update Architecture FIG-8b5baaa82fc9e160	AUTOSAR_AP_EXP_PlatformDesign	R24-11	✓ Beschrieben
Figure 9.3: Deployment Overview of Diagnostics FIG-8d35f191c6f03f0b	AUTOSAR_AP_EXP_PlatformDesign	R25-11	✓ Beschrieben
Figure 4.1: AP architecture logical view FIG-8e4b6f7e8b95f1ec	AUTOSAR_AP_EXP_PlatformDesign	R23-11	✓ Beschrieben
Figure 4.5: Applications FIG-8fc2017ca8979d4f	AUTOSAR_AP_EXP_PlatformDesign	R23-11R24-11	✓ Beschrieben
Figure 13.1: Vehicle Update Architecture FIG-972d16d65d0bf6c4	AUTOSAR_AP_EXP_PlatformDesign	R23-11	✓ Beschrieben
Figure 13.10: State Management during an update process FIG-9ba085fdb2e9d37f	AUTOSAR_AP_EXP_PlatformDesign	R24-11	✓ Beschrieben
Figure 4.5: Applications FIG-9f53edc59c96300d	AUTOSAR_AP_EXP_PlatformDesign, AUTOSAR_EXP_PlatformDesign	R21-11R22-11R25-11	✓ Beschrieben
Figure 4.4: Security features FIG-a934712d993b5f94	AUTOSAR_AP_EXP_PlatformDesign	R24-11	✓ Beschrieben
Figure 13.9: V-UCM state machine FIG-aed7612a40a36901	AUTOSAR_AP_EXP_PlatformDesign	R24-11	✓ Beschrieben
Figure 3.1: Exemplary deployment of different platforms FIG-aeeb1fd86ee571f7	AUTOSAR_AP_EXP_PlatformDesign, AUTOSAR_EXP_PlatformDesign	R21-11R24-11	✓ Beschrieben
Figure 16.1: Overview Log and Trace FIG-b1da200f226fa2c6	AUTOSAR_AP_EXP_PlatformDesign	R23-11R24-11R25-11	✓ Beschrieben
Figure 10.1: Typical usage of Persistency within an Adaptive Application FIG-b25ebdaeda1910ab	AUTOSAR_AP_EXP_PlatformDesign	R23-11	✓ Beschrieben
Figure 20.2: Firewall architecture FIG-bb047d688191b634	AUTOSAR_AP_EXP_PlatformDesign, AUTOSAR_EXP_PlatformDesign	R22-11R23-11R24-11R25-11	✓ Beschrieben
Figure 13.7: Packages distribution to vehicle FIG-bc84a720164ec337	AUTOSAR_AP_EXP_PlatformDesign, AUTOSAR_EXP_PlatformDesign	R21-11R22-11R23-11R24-11+1	✓ Beschrieben
Figure 12.1: Overview NM FIG-bd314a91ffbffccd	AUTOSAR_AP_EXP_PlatformDesign, AUTOSAR_EXP_PlatformDesign	R21-11R22-11R23-11R24-11	✓ Beschrieben
Figure 12.1: Overview NM FIG-cee36c80dce0f29f	AUTOSAR_AP_EXP_PlatformDesign	R25-11	✓ Beschrieben
Figure 14.1: AUTOSAR IAM FIG-d0236275caf32923	AUTOSAR_AP_EXP_PlatformDesign	R23-11R24-11R25-11	✓ Beschrieben
Figure 4.3: Safety features FIG-d1da51fa48aa9bf6	AUTOSAR_AP_EXP_PlatformDesign	R24-11	✓ Beschrieben
Figure 7.2: Overview of ’lightweight’ StateMachine concept FIG-d627a541d02f2051	AUTOSAR_AP_EXP_PlatformDesign	R23-11R25-11	✓ Beschrieben
Figure 23.1: Architecture of Remote Persistency FIG-dad03df66b1688f9	AUTOSAR_AP_EXP_PlatformDesign	R25-11	✓ Beschrieben
Figure 4.6: AP development workflow FIG-e149baf327dfca7a	AUTOSAR_AP_EXP_PlatformDesign, AUTOSAR_EXP_PlatformDesign	R21-11R22-11R23-11R24-11+1	✓ Beschrieben
Figure 10.1: Typical usage of Persistency within an Adaptive Application FIG-e2758f80a65149eb	AUTOSAR_AP_EXP_PlatformDesign	R25-11	✓ Beschrieben
Figure 13.10: State Management during an update process FIG-e6b8981575852030	AUTOSAR_AP_EXP_PlatformDesign	R25-11	✓ Beschrieben
Figure 13.4: Overview Vehicle Package FIG-eb733c53f6cef267	AUTOSAR_AP_EXP_PlatformDesign	R23-11R24-11	✓ Beschrieben
Figure 14.2: IAM sequence FIG-f72cf7ace36cdf5d	AUTOSAR_AP_EXP_PlatformDesign	R23-11R24-11R25-11	✓ Beschrieben
Figure 8.2: Example Language and Network Binding FIG-fb8ee7c503106969	AUTOSAR_AP_EXP_PlatformDesign, AUTOSAR_EXP_PlatformDesign	R21-11R22-11R23-11R24-11+1	✓ Beschrieben
Figure 3.1: Exemplary deployment of different platforms FIG-fd0df0b14d47ba72	AUTOSAR_AP_EXP_PlatformDesign, AUTOSAR_EXP_PlatformDesign	R22-11R23-11	✓ Beschrieben
Figure 2.1: SOVD Reference architecture FIG-2542a696e8f974dc	AUTOSAR_AP_EXP_SOVD	R23-11R24-11R25-11	✓ Beschrieben
Figure 3.1: Solution Approach for SOVD updates FIG-815420487d37b91a	AUTOSAR_AP_EXP_SOVD	R25-11	✓ Beschrieben
Figure 9.63: Cryptographic Object Interfaces FIG-001133fac08c10b8	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 11.23: Scenario: Report Supervision Failure FIG-00f03948ae751d9a	AUTOSAR_AP_EXP_SWArchitecture	R24-11R25-11	✓ Beschrieben
Figure 9.47: Users of the FileStorage interface FIG-013d9984f09b86e8	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.3: Interfaces for state reporting FIG-026c11c35bbd4b3d	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.94: Functional Clusters in category Diagnostics FIG-02772fb9dca3b4fb	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 9.28: Interfaces required by Communication Management FIG-031ca09af26f4d9c	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 10.11: Use case for Report Checkpoint FIG-04cd27e2835fa1c9	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 8.8: Example of Plugin Class Structure FIG-0598d3af3482b18d	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.61: Cryptographic Key Handling Interfaces FIG-05e067e7ab559719	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 9.6: Users of the State Management interfaces FIG-05eb6da2558a5809	AUTOSAR_AP_EXP_SWArchitecture, AUTOSAR_AP_SWS_ExecutionManagement	R25-11	✓ Beschrieben
Figure 9.80: Functional Clusters in category Configuration FIG-067f5db39fc8530a	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 9.35: Functional Clusters in category Storage FIG-073f6c4e3c2aead4	AUTOSAR_AP_EXP_SWArchitecture, AUTOSAR_EXP_SWArchitecture	R22-11R23-11	✓ Beschrieben
Figure 9.64: Taxonomy of Cryptographic Object Interfaces FIG-07592b5094d9ddea	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.43: Interfaces for file storage FIG-0868ee1bef0be8b2	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.22: Interfaces defined by Operating System Interface FIG-086a7761f3470002	AUTOSAR_AP_EXP_SWArchitecture, AUTOSAR_EXP_SWArchitecture	R22-11R24-11	✓ Beschrieben
Figure 9.60: ExtensionService and CryptoContext Interfaces (1 of 2) FIG-08d96388d8a4e92c	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.92: Users of the Registry interfaces FIG-095daafcb4cb1950	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.106: Interfaces for the DoIP API (2 of 2) FIG-099fefbf30242781	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 8.4: Example of Configuration in the Manifest FIG-0a36c25bb1a960ef	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 11.20: Scenario: Switch Firewall State FIG-0a8bb22a36753ced	AUTOSAR_AP_EXP_SWArchitecture	R24-11R25-11	✓ Beschrieben
Figure 11.26: Scenario: Report Checkpoint FIG-0aaa2ebc8b17d424	AUTOSAR_AP_EXP_SWArchitecture	R24-11R25-11	✓ Beschrieben
Figure 9.64: Interfaces of Firewall FIG-0ae668cf932d5a47	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.63: X.509 Certificate Object Interfaces FIG-0b26e20a5bb71e9a	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 9.29: Interfaces required by Communication Management FIG-0b6d8c6d2973ee2b	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.96: Interfaces of Vehicle Update and Configuration Management FIG-0b6e5f22bf20d7e9	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.100: Interfaces of Registry FIG-0c7db60b6e19a28f	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 11.12: Scenario: Store Persistent Data in File FIG-0cace8c1a26f6582	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 12.2: Exemplary deployment of Software Packages on a Machine FIG-0cd16ff1d4927a7c	AUTOSAR_AP_EXP_SWArchitecture, AUTOSAR_EXP_SWArchitecture	R22-11R23-11R24-11	✓ Beschrieben
Figure 8.10: Variants of the Offer/StopOffer Pattern FIG-0dff9b7a0cecaed9	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.102: Interfaces for Managing Multiple Conditions, Events, and Monitors FIG-0e230acf2dcb148d	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 11.10: Scenario: Receive IP Stream FIG-0e9c3a9628a20d2a	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 10.15: Use case Report Checkpoint FIG-0f085bc6c4b3bd42	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.110: Interfaces for security FIG-0f3ce3b04cf4263b	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.4: Interfaces for State Management FIG-1117427dd6b41fb9	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.44: Interfaces for key-value-based data storage FIG-115a9d945489550c	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.37: Interfaces for key-value-based data storage FIG-1163424c1507a5ad	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.51: Interfaces required by Persistency FIG-11b3c01423756b16	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 13.5: Example using one diagnostic address for each Software Cluster FIG-11f8b04c37c196ef	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11R25-11	✓ Beschrieben
Figure 9.18: Interfaces required by LogAndTrace FIG-12068bb8599a6f08	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.65: Users of the Cryptography interfaces FIG-124ebe16d6defae8	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 9.29: Users of Network Management interfaces FIG-13eb484cd922e330	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 11.2: Scenario: Shutdown Adaptive Platform with Supervision of Adaptive Applications FIG-14125caccf7b40f7	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.11: Interface for handling a Power Mode request FIG-1458ed879c841757	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.101: Users of the Registry interfaces FIG-162fae6e72d72e0d	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.39: Interfaces for installation and update of persistent data FIG-1746076f25875b1e	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.4: Interfaces for State Management FIG-178ff2660ed73cf3	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 10.7: Use cases for the Automotive API Gateway FIG-1812e699a3055196	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 8.2: Class Structure of a Plugin FIG-18588526bc70732c	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 8.6: Excerpt of Meta-Model FIG-18d3718ed58dfaef	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.30: Interfaces for raw data streams using IP based protocols FIG-1a12250bc5d48f84	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.93: Interfaces required by Registry FIG-1a19cdbc5fa8899b	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 9.107: Interfaces for request handling FIG-1ab67cd7eedf0a88	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 10.10: Use cases for Firewall FIG-1ae1df00971a310b	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.6: Users of the State Management interfaces FIG-1b247418ef22d3e8	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 8.3: Excerpt of Meta-Model FIG-1b52125e29561450	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.96: Interfaces for the UDS Transportlayer API (1 of 2) FIG-1c35b1d7325cf4b7	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.69: Interface for receiving notifications about qualified security events FIG-1d37e332281e43b1	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.70: Interfaces required by Cryptography FIG-1d98abd90e1b91c7	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.46: Interfaces for key-value-based data storage FIG-1ddeda60e5704dda	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 10.16: Use cases for Safe Hardware Acceleration FIG-1e6e29764ca54863	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.38: Interfaces for general persistency handling FIG-1f0c8ae68a0e7b13	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 8.12: Variant 2 - std::function FIG-20af53a0cf7e464c	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.31: Interfaces required by Raw Data Stream FIG-2205c1be9a41a596	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.51: Common Interfaces of Cryptography FIG-223c1a2660f21110	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 8.8: Example of Plugin Class Structure FIG-22406760d8cd075d	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.8: Interfaces for triggering state changes FIG-234d5a20ae6259e3	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.78: Interfaces required by Firewall FIG-237713263eec7842	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.16: Interfaces of Log and Trace FIG-245a9912030aa804	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 9.32: Interfaces required by Raw Data Stream FIG-249203c327076e88	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.17: Interfaces required by LogAndTrace FIG-26d0db9750670bdc	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 7.2: Overview of the AUTOSAR Adaptive Platform and external systems FIG-26e2f8efae08aaba	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 9.103: Functional Clusters in category Diagnostics FIG-2711146ebe84fed9	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.7: Interfaces required by Execution Management FIG-2711f5c53de7a4bd	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.83: Users of the Update and Configuration Management interfaces FIG-274266402694cc52	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 10.5: Use cases for Time Synchronization Master FIG-2767154df839296e	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 10.5: Use cases for Time Synchronization Slave FIG-283b18123d2a91c1	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 10.21: Use case Activate Campaign and derived use cases FIG-2840f4e1f6d92e8d	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.108: Security-related Interfaces required by Diagnostic Management FIG-28c2b84cdf772200	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.19: Interfaces of Core FIG-2917d524dc7fa392	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 9.25: Generated Skeleton interfaces FIG-29fe47a49b1542ec	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 8.2: Class Structure of a Plugin FIG-2b07fd11809c0f60	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.40: Users of the FileStorage interfaces FIG-2b3783a5f99222e6	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.14: Interfaces required by State Management FIG-2bca2a7909ff2bd4	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.81: General Interfaces of Update and Configuration Management FIG-2bd0004b0a67e694	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.28: Interfaces for time base providers FIG-2bdf04b43562a870	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.46: BlockService and CryptoContext Interfaces FIG-2bf34ebf0c44dacf	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.97: Interfaces required by Vehicle Update and Configuration Management (part 1) FIG-2c3c9fb4b691bf59	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.50: Users of the KeyValueStorage interface FIG-2c46e424dd1eaaa7	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 11.24: Scenario: Recover from Critical Supervision Failure in Execution Management FIG-2d074d50671c69d4	AUTOSAR_AP_EXP_SWArchitecture	R24-11R25-11	✓ Beschrieben
Figure 9.50: ExtensionService and CryptoContext Interfaces (2 of 2) FIG-2d0bfb32ef4f7101	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.122: Interfaces for SOVD record data FIG-2fe015c5e448a9a7	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.8: Interfaces for a SMControlApplication FIG-3048f028a02daf46	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.26: Interfaces for SecOC FIG-30a12ec0b67531c6	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 11.2: Scenario: Shutdown Adaptive Platform with Supervision of Adaptive Applications FIG-311ccf5ecf647805	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.104: Interfaces for the UDS Transportlayer API (2 of 2) FIG-31b4e23530ffd403	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 8.9: Excerpt of Meta-Model FIG-31e4165e90037d47	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 11.3: Scenario: Change Function Group State FIG-324a38c1530a3a9d	AUTOSAR_AP_EXP_SWArchitecture	R24-11R25-11	✓ Beschrieben
Figure 9.73: Interfaces required by Firewall FIG-32bda29d3b576cb0	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 10.23: Provide Vehicle Update Information FIG-337506064b07189d	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.44: Common Interfaces of Cryptography FIG-3382518a3d893df8	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.62: Users of the Intrusion Detection System Manager interfaces FIG-3385240044ff428e	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.60: Taxonomy of Cryptographic Object Interfaces FIG-33b61e646de47928	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 9.91: Interfaces of Registry FIG-33bd21b925913cc1	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 10.3: Use cases for Time Synchronization Master FIG-34803b85dc6204d6	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 10.8: Use cases for Firewall FIG-3613fa61c4c7ef02	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 8.4: Example of Configuration in the Manifest FIG-361a096ada0f17fb	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 11.11: Scenario: Receive IP Stream FIG-361b12ab1e9a36be	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.85: Interfaces for hardware accelerated execution FIG-367c37f6ab6634b6	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.57: BlockService and CryptoContext Interfaces FIG-3704775b99346997	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.10: Interface for software update handling FIG-37e93d26f060e8c2	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 11.22: Scenario: Manage Watchdog FIG-3814eae3ce11a8e3	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 8.7: Example of Configuration in the Manifest FIG-3980a6e2f9d56718	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.7: Interfaces required by Execution Management FIG-39ac57ba13f0292a	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.75: Users of the Intrusion Detection System Manager interfaces FIG-39d710d9ffd0ca9c	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.50: Functional Clusters in category Security FIG-3af3026688562786	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 11.8: Scenario: Send IEEE1722 Stream FIG-3b39455b27363f66	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.98: Interfaces for generic request handling FIG-3b47a49f69caaa2e	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.2: Functional Clusters in category Runtime FIG-3bb185799b78e07a	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.25: Functional Clusters in category Communication FIG-3bbfc4576980545a	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.48: DigestService and CryptoContext Interfaces FIG-3bfd86884599c4f8	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.39: Interfaces for freshness value management FIG-3dddfc7dfa074355	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.33: Internal interfaces required by Raw Data Stream FIG-3de516b9c476064f	AUTOSAR_AP_EXP_SWArchitecture	R24-11R25-11	✓ Beschrieben
Figure 9.31: Interfaces for time base providers FIG-3e6436d0559006e7	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.12: Users of the State Management interfaces FIG-3ee6a7b5a39c1c82	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.74: Functional Clusters in category Safety FIG-3f84ffb548797cd3	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 11.20: Scenario: Get KeyValueStorage Size FIG-3fc295ad4ef2e7c2	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.22: Functional Clusters in category Communication FIG-4030e66056c17695	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.59: DigestService and CryptoContext Interfaces FIG-4190d6bb59667bfc	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 11.5: Scenario: Reject Trigger Input FIG-4200af6edf95f2bb	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 10.20: Use case Cancel Campaign FIG-42a9309431ae254d	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 10.13: Use case Report Supervision Failure FIG-4310a99fdb6e7fd1	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 11.10: Scenario: Read Persistent Data from File FIG-43ba94e83e3b8379	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 11.13: Scenario: Receive Notification FIG-44188359ee6145f9	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 7.1: Overview of AUTOSAR Adaptive Platform and its context FIG-44223525e4ac21fc	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11R25-11	✓ Beschrieben
Figure 9.87: Common interfaces of Safe Hardware Acceleration (1) FIG-442a6c764a9068a5	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 11.18: Scenario: Manage Watchdog FIG-442e2fefebc19b75	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.43: Functional Clusters in category Security FIG-44540462931645b6	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.24: Interfaces required by Operating System Interface FIG-46938226d7398153	AUTOSAR_AP_EXP_SWArchitecture, AUTOSAR_EXP_SWArchitecture	R22-11R24-11	✓ Beschrieben
Figure 12.2: Exemplary deployment of Software Packages on a Machine FIG-46de3c6444ce485c	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.34: Users of Network Management interfaces FIG-48268bb28bf27487	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.31: Interfaces for raw data streams using the IEEE1722 protocol FIG-4828b6338c6fd6ea	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 11.11: Scenario: Read Persistent Data with Unique ID FIG-4927e742d5d704e8	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.41: Interfaces required by Time Synchronization FIG-4975a7f23e5f4a80	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.29: Interfaces for raw data streams using IP based protocols FIG-498e1bce6375bf9f	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.22: Users of the OperatingSystemInterface interfaces FIG-49d32dbe0a8b64bc	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 8.3: Excerpt of Meta-Model FIG-4a316eb1c19c8627	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.7: Interfaces required by Execution Management FIG-4a7804163217ec20	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 10.6: Use Cases for Storing Persistent Data FIG-4abc949f95af0170	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 11.25: Scenario: Recover from Critical Supervision Failure in State Management FIG-4ba21a208de1928f	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 11.23: Scenario: Manage Watchdog FIG-4bca87b097bec626	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.41: Users of the KeyValueStorage interfaces FIG-4d0e7f849e018967	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 10.7: Use Cases for Reading Persistent Data FIG-4f745ec85fc678f7	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 11.6: Scenario: Recover by System State Change FIG-4fba55216efbae96	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.73: General Interfaces of Update and Configuration Management FIG-4ffa29f6cddf0a41	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 11.7: Scenario: Set Value Of Time Base FIG-50d69fbd7742a9c6	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 10.14: Use case Report Checkpoint FIG-514b34fc85a1c552	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.108: Interfaces for generic request handling FIG-5238cf3a39003cda	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.47: Interfaces for general persistency handling FIG-53848449fb9e0668	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 11.20: Scenario: Report Supervision Failure FIG-5398aad1d66b4955	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 10.12: Use case Manage Watchdog FIG-5499c12a6b6d2290	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.23: Interfaces required by Operating System Interface FIG-554d6824649217a7	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.20: Interfaces for memory resources FIG-55a74fe2b6c0be2d	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.15: Interfaces of Execution Management required by State Management FIG-55aeba189ab7aaae	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.13: Users of the State Management interfaces FIG-55d2202bc2dadbc3	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.98: Interfaces for the DoIP API (1 of 2) FIG-564e81c1b3ffe00e	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.65: Cryptographic Key Handling Interfaces FIG-565a1811a361f6c7	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.74: Interface for receiving notifications about qualified security events FIG-56a082f5e5154691	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.35: Interfaces required by Network Management FIG-56a2b26531aa4857	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.46: Interfaces for installation and update of persistent data FIG-579cf5570ea01309	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.83: Interfaces of Registry FIG-58269fa3c6bd057a	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 11.6: Scenario: Recover by Watchdog Reset FIG-58bf7625dd1f86c2	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 13.1: Overview of platform entities and their logical relationships FIG-59477d361857d1a7	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.40: Users of Time Synchronization interfaces FIG-594f7af689201f3b	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 8.12: Variant 2 - std::function FIG-5975a08211ff2028	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 7.2: Overview of the AUTOSAR Adaptive Platform and external systems FIG-59c75c7555d7719b	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.45: General Cryptography Interfaces FIG-59dc3d6b32b05fbe	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.23: Users of the OperatingSystemInterface interfaces FIG-5a137222f0a40341	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.115: Interfaces for the UDS Transportlayer API (1 of 2) FIG-5a2a0f2ed80fbff1	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 11.14: Scenario: Receive Notification FIG-5a41b5809293c9fb	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 10.1: Use cases for Execution Management FIG-5b12829c4e31912d	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.95: Interfaces for State Management FIG-5b9614a1b84c9591	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.32: Interfaces for time base consumers FIG-5bbc08b64c11cf58	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.17: Users of the Log and Trace interfaces FIG-5c0e5b3e4d913381	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 9.70: Users of the SupervisedEntity interface FIG-5cd91e7091b780a9	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.114: Interfaces for File Transfer FIG-5db045ec6bebbf64	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 10.11: Use case Manage Watchdog FIG-5dc38d6976d6221f	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 10.4: Use cases for Communication Management FIG-5dde6731a626db0c	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.62: X.509 Certificate Handling Interfaces FIG-5e772e733eb47c00	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 8.8: Example of Plugin Class Structure FIG-5eae8726f025526b	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.79: Interfaces of Vehicle Update and Configuration Management FIG-60225a9d5ac69dfb	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.97: Interfaces for the UDS Transportlayer API (2 of 2) FIG-614843942fc73c3f	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.111: Interfaces for Upload and Download FIG-62214cb7d0153606	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.71: Interfaces required by Intrusion Detection System Manager FIG-62ba4ff3b32c7868	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.4: Interfaces for State Management FIG-62df51c7c95b36e0	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 10.13: Use case Recover from Critical Supervision Failure FIG-633ab9dcbf3a9112	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 8.11: Variant 1 - Skeleton Approach FIG-633db34ec244396b	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.11: Interfaces for Suspend-to-RAM FIG-63aaae5ac742e4e2	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.38: Interfaces for time base consumers FIG-63ebff2be18301fb	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.100: Interfaces required by Diagnostic Management FIG-64079698f24cd844	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.82: Interfaces required by Vehicle Update and Configuration Management (part 3) FIG-642d46c2c786c61a	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 8.9: Excerpt of Meta-Model FIG-64748ee270ce4b7a	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.5: Users of the ExecutionClient interface FIG-64abadcb90086349	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 8.7: Example of Configuration in the Manifest FIG-64bd715b8cc69675	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 12.1: Exemplary vehicle software update scenario FIG-65440537d39f083c	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.6: Users of the State Management interfaces FIG-6559ca0940ac902a	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.99: Interfaces required by Vehicle Update and Configuration Management (part 3) FIG-65df2a216c311370	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.95: Common interfaces of Diagnostic Management (1 of 2) FIG-67252428cf9a6f4a	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 9.54: CryptoService and CryptoContext Interfaces FIG-672e05f032fe2470	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 9.52: General Cryptography Interfaces FIG-678d56ae53bb5f7c	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 11.4: Scenario: Change System State FIG-6b2632b0cef9991f	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.19: Interfaces for memory resources FIG-6b9c950b30ceeab1	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.13: Interfaces required by State Management FIG-6d1f95cef760a555	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.80: Interfaces required by Vehicle Update and Configuration Management (part 1) FIG-6d46418f455220ec	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.36: Interfaces required by Network Management FIG-6e16fc0575e2830d	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.28: Interfaces required by Communication Management FIG-6e33c93d6739cc9a	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 10.18: Use case Transfer Vehicle Data FIG-6f202ce91df8da78	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 11.14: Scenario: Get FileStorage Size FIG-6f257f695ecee51e	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 11.7: Scenario: Send IEEE1722 Stream FIG-6f51fe889bf36180	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.67: Interfaces for reporting security events FIG-7126de56b9fa299d	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 8.6: Excerpt of Meta-Model FIG-71fc37ab1b0eaf61	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 5.2: Interfaces required by Vehicle Update and Configuration Management from other Functional Clusters FIG-7215e4c041c2edcf	AUTOSAR_AP_EXP_SWArchitecture, AUTOSAR_AP_SWS_VehicleUpdateAndConfigurationManagement	R25-11	✓ Beschrieben
Figure 11.26: Scenario: Recover from Critical Supervision Failure in State Management FIG-745d006354afcce3	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.73: Interfaces for providing additional data for security events FIG-74b9632c1f00400a	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 11.14: Scenario: Read Persistent Data from File FIG-752c5253e01f91f4	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.2: Functional Clusters in category Runtime FIG-75bc8a6290912b9c	AUTOSAR_AP_EXP_SWArchitecture, AUTOSAR_EXP_SWArchitecture	R22-11R23-11	✓ Beschrieben
Figure 9.105: Common interfaces of Diagnostic Management (2 of 3) FIG-763090c91ced4145	AUTOSAR_AP_EXP_SWArchitecture, AUTOSAR_EXP_SWArchitecture	R22-11R25-11	✓ Beschrieben
Figure 9.95: Interfaces required by Update and Configuration Management (part 3) FIG-76e56d9833e5c85b	AUTOSAR_AP_EXP_SWArchitecture	R24-11R25-11	✓ Beschrieben
Figure 11.13: Scenario: Store Persistent Data with Unique ID FIG-77e485cbe4c2b9bb	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.66: Interfaces required by Cryptography FIG-7833d3c0140a4b49	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 10.9: Use Cases for Storing Persistent Data FIG-7891883b4c3cd1a6	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.2: Functional Clusters in category Runtime FIG-78c4cab75e4ee3fd	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.42: Functional Clusters in category Storage FIG-790bd877ca871bbe	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.84: Users of the Registry interfaces FIG-7a3a533382323fcc	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.1: Overview of the AUTOSAR Adaptive Platform and its building block categories FIG-7a9d757ec8d34487	AUTOSAR_AP_EXP_SWArchitecture	R24-11R25-11	✓ Beschrieben
Figure 9.14: Interfaces of Execution Management required by State Management FIG-7b162cf9af5f49b3	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.71: Interfaces required by Cryptography FIG-7c26b00bcc62b16e	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.58: CryptoService and CryptoContext Interfaces FIG-7c9aff6fa816e25c	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.117: Interfaces for the DoIP API (1 of 2) FIG-7d235b508f289343	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.20: Users of the OperatingSystemInterface interfaces FIG-7da547b5a307cfa3	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.45: Interfaces for general persistency handling FIG-7dc27fc2296ac0a1	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 11.1: Scenario: Start Adaptive Platform with Supervision of Adaptive Applications FIG-7dd313278bef6ea5	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.66: Functional Clusters in category Safety FIG-7e6063ba90fba661	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.89: Functional Clusters in category Configuration FIG-7f2b2408e71f8e4b	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 11.3: Scenario: Change Function Group State FIG-7ff72a273f13b64b	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.74: D-PDU-API Interfaces FIG-804c41b84b4f0eb1	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.1: Overview of the AUTOSAR Adaptive Platform and its building block categories FIG-80df8324c3b3840d	AUTOSAR_AP_EXP_SWArchitecture, AUTOSAR_EXP_SWArchitecture	R22-11R23-11	✓ Beschrieben
Figure 11.8: Scenario: Get Value of Time Base FIG-811eafdb4e737c7f	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.68: Interfaces for providing additional data for security events FIG-811f87846ebae9c8	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 11.22: Scenario: Report Security Event FIG-8172b76858ee9e80	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 11.9: Scenario: Receive IEEE1722 Stream FIG-817c9b0c6fa749fd	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 11.15: Scenario: Read Persistent Data from File FIG-81e9ad61e4f05dc7	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 11.8: Scenario: Send IP Stream FIG-82040eee898a3005	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.124: Security-related Interfaces required by Diagnostic Management FIG-8205e5807a361fad	AUTOSAR_AP_EXP_SWArchitecture, AUTOSAR_AP_SWS_Diagnostics	R25-11	✓ Beschrieben
Figure 9.24: Functional Clusters in category Communication FIG-8206c96d6df536fd	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 10.22: Use case Cancel Campaign FIG-830140bcb5d21ee6	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.16: Users of the Log and Trace interfaces FIG-83f4fc6be1538695	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.91: Interfaces for generic request handling FIG-855e0ff10434fca0	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.37: Interfaces for time base consumers FIG-86177367deea286f	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 11.19: Scenario: Get KeyValueStorage Size FIG-8753ba87cac0c47f	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.85: Interfaces required by Update and Configuration Management (part 2) FIG-87d354833478c716	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 11.18: Scenario: Store Persistent Data with Unique ID FIG-884a6a447fcf4783	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.79: Interfaces required by Platform Health Management FIG-8a898cf2f1e87df1	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 9.80: Interfaces for supervision FIG-8aab54847e93bf22	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.30: Interfaces required by Network Management FIG-8abb85ad66b8f315	AUTOSAR_AP_EXP_SWArchitecture, AUTOSAR_EXP_SWArchitecture	R22-11R23-11	✓ Beschrieben
Figure 11.4: Scenario: Change System State FIG-8b5fbf2a5df150a7	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 11.19: Scenario: Report Checkpoint FIG-8ba88db5c3893244	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.33: Users of Time Synchronization interfaces FIG-8c0098082542ec3d	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 10.6: Use cases for the Automotive API Gateway FIG-8e328fd1ac598ae8	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 10.18: Use cases for activating and rolling-back SW packages FIG-8e51664a93046fdb	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.40: Interfaces required by Time Synchronization FIG-9002b7d402773fe9	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.58: SignatureService and CryptoContext Interfaces FIG-9009924c25d74e4c	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 10.9: Use Cases for Monitoring FIG-90acb802ec5107f4	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.55: DigestService and CryptoContext Interfaces FIG-90fa54eef2e17f97	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.34: Interfaces required by Time Synchronization FIG-9230af3e70a5249a	AUTOSAR_AP_EXP_SWArchitecture, AUTOSAR_EXP_SWArchitecture	R22-11R23-11	✓ Beschrieben
Figure 10.19: Use case for providing update related information FIG-924de3ebf3d0080d	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 8.10: Variants of the Offer/StopOffer Pattern FIG-93067f2f95d12b13	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.86: Device and related interfaces of Safe Hardware Acceleration FIG-932a5f5887a47219	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.37: Interfaces for time base providers FIG-94e7755db8144615	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.90: General Interfaces of Update and Configuration Management FIG-95045bd55037c9c6	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.41: Interfaces required by the Automotive API Gateway FIG-959dabbbaec18a3a	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.26: Interfaces for raw data streams FIG-95a69a366175e036	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.20: Interfaces for memory handling FIG-95bf98c5d39fe92d	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 13.4: Example defining a single diagnostic address for the whole Machine FIG-960e9d49d23d65ec	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11R25-11	✓ Beschrieben
Figure 8.5: Example of Plugin Class Structure FIG-962a5b1aa7b69654	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.84: Interfaces required by Update and Configuration Management (part 1) FIG-9714e1188296783f	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.83: Users of the SupervisedEntity interface FIG-974c3104fd60a193	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.24: Interfaces for freshness value management FIG-9802f103ce3cab50	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.120: Interfaces for SOVD data FIG-9a1b028590ef5c2c	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.33: Interfaces for time base providers FIG-9a936b9fd1a1b410	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 10.16: Use cases for activating and rolling-back SW packages FIG-9ac7b2d47cea23df	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.78: Interfaces required by Update and Configuration Management (part 3) FIG-9ccd697ec24ff8e5	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.26: Interfaces for SecOC FIG-9cd6a2b579b475a2	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 11.1: Scenario: Start Adaptive Platform with Supervision of Adaptive Applications FIG-9cf4902e59a4b799	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 8.5: Example of Plugin Class Structure FIG-9e27c537ddce5bdf	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.54: Functional Clusters in category Security FIG-9ee2c1faedbcf1a8	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.67: X.509 Certificate Object Interfaces FIG-a0bdd78e5adf418d	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 10.6: Use cases for Time Synchronization Slave FIG-a0cf86f48f0d2809	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 11.16: Scenario: Read Persistent Data with Unique ID FIG-a10f969cf0a8eceb	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.18: Interfaces of Core FIG-a15bccf4b248814c	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.94: Interfaces required by Update and Configuration Management (part 2) FIG-a1d50174e494d280	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.88: Common interfaces of Safe Hardware Acceleration (2) FIG-a28904fab19d3584	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.97: Interfaces for request handling FIG-a29199e4689dcc3c	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 9.57: ExtensionService and CryptoContext Interfaces (2 of 2) FIG-a317083a11dadbab	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 8.9: Excerpt of Meta-Model FIG-a3e2eafe4f34fab5	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.3: Interfaces for state reporting FIG-a4bdb36228548c05	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.76: Interfaces for recovery FIG-a58784c6f478bc6d	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 11.7: Scenario: Recover by Watchdog Reset FIG-a7e435a14b24eeaf	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.53: Interfaces required by Remote Persistency FIG-a8fa6e1339537fa9	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.48: Interfaces for installation and update of persistent data FIG-aa021c5398d9de6d	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 11.18: Scenario: Get FileStorage Size FIG-aa102024e40b7d7b	AUTOSAR_AP_EXP_SWArchitecture	R24-11R25-11	✓ Beschrieben
Figure 9.36: Interface for time base providers FIG-aaab3974142e242a	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 11.15: Scenario: Read Persistent Data with Unique ID FIG-abd31065e915116c	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 10.1: Use cases for Execution Management FIG-ac540a7cc173e49f	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 9.59: Cryptographic Object Interfaces FIG-ac86d5d6d324bace	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 11.6: Scenario: Recover from Supervision Failure FIG-acee7ed1f8d50512	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.118: Interfaces for the DoIP API (2 of 2) FIG-ad64c255be57bd18	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.48: Users of the KeyValueStorage interface FIG-ad808cdd541d99c9	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.60: Interfaces for reporting security events FIG-ad8535477782c40f	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.113: Interfaces for ECU Reset FIG-ae15044d532e78bf	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.72: Interfaces for reporting security events FIG-b07d62866897deec	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.63: Interfaces required by Intrusion Detection System Manager FIG-b0d3d66251ec0a0e	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.88: Interfaces required by Vehicle Update and Configuration Management (part 1) FIG-b1176358c0c3e9cb	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 11.17: Scenario: Report Security Event FIG-b1273965639f62af	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.49: Users of the FileStorage interface FIG-b1cdeb4ae3281d43	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 10.15: Use cases for transferring and processing SW packages FIG-b261aa5ee7adbb9d	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.56: General Cryptography Interfaces FIG-b2e86633a3e3ee49	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 11.13: Scenario: Get Value of Time Base FIG-b2f2473ecd40a79e	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 11.2: Scenario: Shutdown Adaptive Platform with Supervision of Adaptive Applications FIG-b33d8c310e65facf	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.53: BlockService and CryptoContext Interfaces FIG-b377e39175111810	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.21: Interfaces defined by Operating System Interface FIG-b39355672467ecad	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 10.11: Use cases for Firewall FIG-b3f004d223bbb322	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.99: Generated interfaces for request handling FIG-b483e6692153d392	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 5.2: Interface required by Diagnostic Management from Adaptive Intrustion Detection System Manager FIG-b4889012352c4889	AUTOSAR_AP_EXP_SWArchitecture, AUTOSAR_AP_SWS_Diagnostics	R23-11R24-11	✓ Beschrieben
Figure 11.9: Scenario: Send IP Stream FIG-b4bd393eca733a7c	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 10.17: Use cases for transferring and processing SW packages FIG-b5867fd73f182f05	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.12: Users of the State Management interfaces FIG-b5d3179f91c7ea7f	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.76: Interfaces required by Update and Configuration Management (part 1) FIG-b6c9ce59099a2615	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.49: Interfaces required by Persistency FIG-b6e86875c6195529	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 10.2: Use cases for State Management FIG-b76aa10f8ecd7a0f	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.55: Common Interfaces of Cryptography FIG-b8176d7a5c9c6f89	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 8.1: Type model of building blocks FIG-b8f96421f93b51bf	AUTOSAR_AP_EXP_SWArchitecture, AUTOSAR_EXP_SWArchitecture	R22-11R23-11R24-11R25-11	✓ Beschrieben
Figure 10.19: Use case Activate Campaign and derived use cases FIG-bb08997e97223086	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 8.4: Example of Configuration in the Manifest FIG-bb1fd954b6524c17	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.21: Interfaces required by Operating System Interface FIG-bb9233bc1809b6f5	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.121: Interfaces for SOVD array data FIG-bc368756d2aadda0	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 10.8: Use Cases for Storing Persistent Data FIG-bd19506b6d63774e	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 11.16: Scenario: Switch Firewall State FIG-bd1d9121c3dc5224	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 11.9: Scenario: Receive Notification FIG-bd402b43a8ba7b51	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.21: Interfaces for memory handling FIG-bdf51864fba64128	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.123: Interfaces required by Diagnostic Management FIG-be04a80528d992b2	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.13: Interfaces required by State Management FIG-bf0159626b14668a	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.82: Interfaces for watchdog handling FIG-bf5f26a11d4822ae	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.76: Interfaces required by Intrusion Detection System Manager FIG-bfbb2f631c0e1f2b	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 11.15: Scenario: Get KeyValueStorage Size FIG-bfee550e1c70d778	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 11.12: Scenario: Set Value Of Time Base FIG-c07974c05b89f488	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 11.12: Scenario: Get Value of Time Base FIG-c0a9744e0695be48	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.81: Interfaces for recovery FIG-c1bde4e24dcfadf2	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 10.14: Use case Recover from Critical Supervision Failure FIG-c1dc8a4e81962323	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.27: Interfaces for freshness value management FIG-c24150a71eda1dc3	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.66: X.509 Certificate Handling Interfaces FIG-c3b3ca9e198fdadd	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 11.4: Scenario: Change System State FIG-c50a095789145a64	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.19: Interfaces defined by Operating System Interface FIG-c513eaf9e5c14bcd	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.9: Notification interface for an Adaptive Application FIG-c5450b86426b2d77	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.112: Interfaces for Managing Multiple Conditions, Events, and Monitors FIG-c54e147e1e98940d	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.104: Common interfaces of Diagnostic Management (1 of 3) FIG-c69726a1fa043ef7	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.61: ExtensionService and CryptoContext Interfaces (2 of 2) FIG-c865d3efdeea3cc5	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.102: Interfaces required by Registry FIG-c9bf6ae61c5c0b3b	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.77: Interfaces for watchdog handling FIG-c9f000a8a6f60f96	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 10.2: Use cases for State Management FIG-ca3786ba23c9abec	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 10.17: Use case for providing update related information FIG-ca8b96e970d25315	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 8.2: Class Structure of a Plugin FIG-cb88aeffce0d5c07	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.77: Interfaces of Firewall FIG-cc6735f815148905	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 11.16: Scenario: Store Persistent Data in File FIG-cc738c51774f9abc	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.103: Interfaces required by Diagnostic Management from external components FIG-cd0729826d2de159	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 11.17: Scenario: Store Persistent Data with Unique ID FIG-cd074fec3273c0cb	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.23: Interfaces for SecOC FIG-cda707b12915c498	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.109: Generated interfaces for request handling FIG-cde3deea9bdfbfbd	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.106: Common interfaces of Diagnostic Management (3 of 3) FIG-ce869eaca7549641	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.79: Functional Clusters in category Safety FIG-d0028bd5aae93584	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.5: Users of the ExecutionClient interface FIG-d016c95609982ba0	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.39: Users of Time Synchronization interfaces FIG-d03464a4eeed4db3	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.44: Interfaces for file storage FIG-d06ac69baf5f0968	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.38: Interfaces for freshness value management FIG-d0985b2d386d07f3	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 11.22: Scenario: Critical Supervision Failure in Execution Management FIG-d1248ff54e550ba1	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.14: Interfaces of Execution Management required by State Management FIG-d1a39c57d846b347	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 11.11: Scenario: Set Value Of Time Base FIG-d25aed3e2f2617e4	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.105: Interfaces for the DoIP API (1 of 2) FIG-d269f7847550cf10	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.125: Interfaces required by Diagnostic Management from external components FIG-d48238c62b605fe8	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.36: Interfaces for file storage FIG-d4a285d7fb4a108f	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.27: Interfaces required by Raw Data Stream FIG-d530459f36901905	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.68: Taxonomy of X.509 Certificate Object Interfaces FIG-d5581ae9c693859e	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 10.3: Use cases for Raw Data Stream FIG-d60510cff085a743	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 10.7: Use Cases for Monitoring FIG-d62cd3c7347cc1e1	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 11.21: Scenario: Report Security Event FIG-d6b50cfaff6ed65c	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 10.8: Use Cases for Reading Persistent Data FIG-d6bdcd8c46fb5bb3	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.75: Users of the Update and Configuration Management interfaces FIG-d6c54f9daf55cc46	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.93: Interfaces required by Update and Configuration Management (part 1) FIG-d779caca52159697	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.35: Users of Network Management interfaces FIG-d7ef80c65c369f12	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.92: Users of the Update and Configuration Management interfaces FIG-d8127a7d9db8b376	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 13.2: Exemplary Software Cluster during application design FIG-d8bc1c5be7ef964d	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11R25-11	✓ Beschrieben
Figure 9.9: Interfaces for a SMControlApplication FIG-dacd0e8a38fd77f6	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.42: Interfaces required by the Automotive API Gateway FIG-db3eff456bbd986a	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.100: Interfaces for security FIG-dbe10d5d26d0b330	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.87: Interfaces of Vehicle Update and Configuration Management FIG-dc31a2f63965200c	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 11.10: Scenario: Receive IEEE1722 Stream FIG-dd5addc263c4d6fa	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.61: Interfaces for providing additional data for security events FIG-ddfa8a49650771f4	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.10: Notification interface for an Adaptive Application FIG-de38c94f48235cc3	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.101: Interfaces for Upload and Download FIG-de890f1b491fa351	AUTOSAR_AP_EXP_SWArchitecture, AUTOSAR_EXP_SWArchitecture	R22-11R23-11R24-11	✓ Beschrieben
Figure 9.116: Interfaces for the UDS Transportlayer API (2 of 2) FIG-df24ec6ffd12e87a	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.67: Interfaces for supervision FIG-df738153d9b1aab9	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.34: Interfaces for time base providers FIG-dfe1ad89d8949a87	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 10.12: Use case Report Supervision Failure FIG-e048b9e392c6f248	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 12.1: Exemplary vehicle software update scenario FIG-e0a98a32260d493f	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 9.75: Interfaces for supervision FIG-e0e2d4de9f57b401	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.69: Users of the Cryptography interfaces FIG-e25c9ed35409751a	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 8.6: Excerpt of Meta-Model FIG-e347e90bfc2efd21	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.27: Interfaces for freshness value management FIG-e3c62b12ca4f4fcb	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.56: ExtensionService and CryptoContext Interfaces (1 of 2) FIG-e3d9371d1b4a98b2	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 10.4: Use cases for Time Synchronization Master FIG-e3e373de98b1a765	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.5: Users of the ExecutionClient interface FIG-e461fdfae372d5b4	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.52: Interface for accessing KeyValueStorage FIG-e4774bdc6f707258	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.3: Interfaces for state reporting FIG-e5d4b0c0c9bbff28	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.103: Interfaces for the UDS Transportlayer API (1 of 2) FIG-e64e421a9168ea15	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 10.3: Use cases for Raw Data Stream FIG-e6deb51cd0888b04	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 11.5: Scenario: Reject Trigger Input FIG-e71e81e829d4e5f4	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.90: Interfaces required by Vehicle Update and Configuration Management (part 3) FIG-e8ace08f70677df2	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 10.21: Provide Vehicle Update Information FIG-ea06a65c476d9bb2	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 11.17: Scenario: Store Persistent Data in File FIG-ea393fae4e430d09	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.11: Interface for software update handling FIG-eb368619d39cb66b	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.15: Interfaces of Log and Trace FIG-eb99d00fdbb31ee4	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.90: Interfaces for request handling FIG-ec09af73deef9547	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.82: D-PDU-API Interfaces FIG-ed0e3cb52f74b3f4	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 11.1: Scenario: Start Adaptive Platform with Supervision of Adaptive Applications FIG-ee58851fa2e67447	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 11.21: Scenario: Critical Supervision Failure in State Management FIG-ef53239e9db2b434	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 11.5: Scenario: Recover by System State Change FIG-ef5e74fc4e610ab1	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.17: Interfaces required by LogAndTrace FIG-efa693fed2f64024	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.89: Interfaces required by Vehicle Update and Configuration Management (part 2) FIG-efbec86dbe3925c8	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 9.30: Interfaces for raw data streams using the IEEE1722 protocol FIG-f01b25e4d1fd6a49	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.8: Interfaces for triggering state changes FIG-f06b001fc8dd41af	AUTOSAR_AP_EXP_SWArchitecture, AUTOSAR_EXP_SWArchitecture	R22-11R23-11	✓ Beschrieben
Figure 9.62: SignatureService and CryptoContext Interfaces FIG-f0f8e264c8608490	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.42: Interfaces required by Persistency FIG-f1d8e0421308291f	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 8.5: Example of Plugin Class Structure FIG-f25fad956c0f54b4	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.107: Interfaces required by Diagnostic Management FIG-f27af3f0f7906063	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 10.10: Use Cases for Monitoring FIG-f2fa77517fd39008	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 13.3: Impact of exemplary Software Cluster during runtime FIG-f31e87cb62d7de06	AUTOSAR_AP_EXP_SWArchitecture, AUTOSAR_EXP_SWArchitecture	R22-11R23-11R24-11R25-11	✓ Beschrieben
Figure 8.7: Example of Configuration in the Manifest FIG-f34c6e02a464a933	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 13.1: Overview of platform entities and their logical relationships FIG-f554e449f530eca1	AUTOSAR_AP_EXP_SWArchitecture, AUTOSAR_EXP_SWArchitecture	R22-11R23-11R24-11	✓ Beschrieben
Figure 9.72: Interfaces of Firewall FIG-f5868505cb8a6e21	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.109: Interfaces required by Diagnostic Management from external components FIG-f7c7e0be1836e53e	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 10.2: Use cases for State Management FIG-f7c840a25372785c	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.12: Interface for software update handling FIG-f80412a749129611	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.84: Interfaces required by Platform Health Management FIG-f873b16589833c58	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.102: Interfaces required by Diagnostic Management from State Management FIG-f9449f076c77bf83	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.119: Interfaces for SOVD operations FIG-fa4e082d9a9462d1	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.70: Users of the Intrusion Detection System Manager interfaces FIG-fa670cd342eab016	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 8.11: Variant 1 - Skeleton Approach FIG-fabcd9ce1130345d	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.64: Taxonomy of X.509 Certificate Object Interfaces FIG-faf42718416f0400	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 10.20: Use case Transfer Vehicle Data FIG-fc451fc7215b4f20	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.96: Common interfaces of Diagnostic Management (2 of 2) FIG-fc8be1fd2c3d58e9	AUTOSAR_AP_EXP_SWArchitecture	R23-11R24-11	✓ Beschrieben
Figure 9.45: Interfaces for file access FIG-fc8ffa29099851b0	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.43: Functional Clusters in category Storage FIG-fca17add9d4918c0	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 10.4: Use cases for Time Synchronization Slave FIG-fcb1f75aaa6e07f4	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.65: Interfaces required by Firewall FIG-fce928ed410bb213	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.10: Interface for handling a Power Mode request FIG-fcf8ac8c56d7edb3	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.9: Interfaces for a SMControlApplication FIG-fd1e40f9dc92ea22	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 9.99: Interfaces for the DoIP API (2 of 2) FIG-fdbd1ffb710b4ece	AUTOSAR_AP_EXP_SWArchitecture	R23-11	✓ Beschrieben
Figure 9.78: Users of the SupervisedEntity interface FIG-fea1841e40c672c4	AUTOSAR_AP_EXP_SWArchitecture	R24-11	✓ Beschrieben
Figure 8.3: Excerpt of Meta-Model FIG-fea3e55acc14ed89	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 9.91: D-PDU-API Interfaces FIG-ff50e77c617ff4b7	AUTOSAR_AP_EXP_SWArchitecture	R25-11	✓ Beschrieben
Figure 4.2: High-level SW Architecture FIG-371a03a8171773a8	AUTOSAR_AP_EXP_SafeAPIHardwareAccelerators, AUTOSAR_AP_EXP_SafeHardwareAccelerationAPI	R23-11R24-11	✓ Beschrieben
Figure 4.1: General approach FIG-c5873e1674906c28	AUTOSAR_AP_EXP_SafeAPIHardwareAccelerators, AUTOSAR_AP_EXP_SafeHardwareAccelerationAPI	R23-11R24-11R25-11	✓ Beschrieben
Figure 5.1: Class diagram FIG-cd21ef77d1976c57	AUTOSAR_AP_EXP_SafeAPIHardwareAccelerators, AUTOSAR_AP_EXP_SafeHardwareAccelerationAPI	R23-11R24-11R25-11	✓ Beschrieben
Figure 4.2: High-level SW Architecture FIG-fa8465e106d5b17d	AUTOSAR_AP_EXP_SafeHardwareAccelerationAPI	R25-11	✓ Beschrieben
Figure 5.3: Service Template with Capability vector and service profiles FIG-26fdd60433a0673a	AUTOSAR_AP_EXP_SensorInterfaces	R25-11	✓ Beschrieben
Figure 5.2: ISO mapping to Smart Sensors Services FIG-27c252f53b2aea45	AUTOSAR_AP_EXP_SensorInterfaces, AUTOSAR_EXP_SensorInterfaces	R18-10_R4.4.0_R1.5.0R18-10-1R19-03R19-11+6	✓ Beschrieben
Figure 4.2: AD sensors directly connected to ECU FIG-489b2402634e8506	AUTOSAR_AP_EXP_SensorInterfaces, AUTOSAR_EXP_SensorInterfaces	R19-11R20-11R21-11R22-11+3	✓ Beschrieben
Figure 4.3: AD sensors connected via a second AUTOSAR AP ECU FIG-49f5499ab1f837a6	AUTOSAR_AP_EXP_SensorInterfaces, AUTOSAR_EXP_SensorInterfaces	R18-10_R4.4.0_R1.5.0R18-10-1R19-03R19-11+6	✓ Beschrieben
Figure 1.1: Overall approach for Sensor Interface Standardization considers different Standardization Levels FIG-5930a30b10f72061	AUTOSAR_AP_EXP_SensorInterfaces, AUTOSAR_EXP_SensorInterfaces	R22-11R23-11R24-11	✓ Beschrieben
Figure 5.3: Service Template with Capability vector and service profiles FIG-6f401c13cf9687ec	AUTOSAR_AP_EXP_SensorInterfaces, AUTOSAR_EXP_SensorInterfaces	R22-11R23-11R24-11	✓ Beschrieben
Figure 5.4: Service Registering flow for capability vector checking FIG-b253bffdeee4e015	AUTOSAR_AP_EXP_SensorInterfaces, AUTOSAR_EXP_SensorInterfaces	R22-11R23-11R24-11R25-11	✓ Beschrieben
Figure 4.1: Scope of Sensor Interface Standardization FIG-dd7829e77a2a9bd9	AUTOSAR_AP_EXP_SensorInterfaces, AUTOSAR_EXP_SensorInterfaces	R18-10_R4.4.0_R1.5.0R18-10-1R19-03R22-11+3	✓ Beschrieben
Figure 1.1: Overall approach for Sensor Interface Standardization considers different Standardization Levels FIG-e7b0a1f9b324ffd3	AUTOSAR_AP_EXP_SensorInterfaces	R25-11	✓ Beschrieben
Figure 5.1: Future Architectures for Smart Sensor APIs FIG-fb6bfcf1a52dd1d8	AUTOSAR_AP_EXP_SensorInterfaces, AUTOSAR_EXP_SensorInterfaces	R22-11R23-11R24-11R25-11	✓ Beschrieben
Figure 4.3: Double Access Control for Inter-Platform Communication FIG-10ea56a585edc514	AUTOSAR_AP_RS_IdentityAndAccessManagement, AUTOSAR_RS_IdentityAndAccessManagement	R22-11R23-11R24-11	✓ Beschrieben
Figure 4.1: Access Matrix FIG-1fc102531a68b0f3	AUTOSAR_AP_RS_IdentityAndAccessManagement, AUTOSAR_RS_IdentityAndAccessManagement	R22-11R23-11R24-11	✓ Beschrieben
Figure 4.2: Access Control by Policy Enforcement FIG-6088cde9996c65d3	AUTOSAR_AP_RS_IdentityAndAccessManagement, AUTOSAR_RS_IdentityAndAccessManagement	R22-11R23-11R24-11	✓ Beschrieben
Figure 7.28: Receive a SET Message FIG-015cb12bc81a873f	AUTOSAR_AP_SWS_CommunicationManagement	R24-11R25-11	✓ Beschrieben
Figure 7.29: Receive response to a SET Message FIG-028fa781a517da65	AUTOSAR_AP_SWS_CommunicationManagement	R25-11	✓ Beschrieben
Figure 5.3: Interfaces required by Communication Management from other Functional Clusters FIG-0345f259150769d1	AUTOSAR_AP_SWS_CommunicationManagement	R23-11	✓ Beschrieben
Figure 7.7: One-dimensional arrays (Example) FIG-044eb8551cf30be5	AUTOSAR_AP_SWS_CommunicationManagement	R24-11	✓ Beschrieben
Figure 7.13: Serialization of Structs with Length Fields (Example) FIG-0694a8e62da568eb	AUTOSAR_AP_SWS_CommunicationManagement, AUTOSAR_SWS_CommunicationManagement	R21-11R23-11	✓ Beschrieben
Figure 7.5: Communication Group FIG-069d4b80f9d29ddf	AUTOSAR_AP_SWS_CommunicationManagement	R23-11	✓ Beschrieben
Figure 7.3: Service contract versioning over time FIG-120f06d937600eb8	AUTOSAR_AP_SWS_CommunicationManagement	R23-11	✓ Beschrieben
Figure 7.3: Service contract versioning over time FIG-13754f8d930f7ec3	AUTOSAR_AP_SWS_CommunicationManagement	R24-11R25-11	✓ Beschrieben
Figure 7.19: Interaction of components during E2E protection of the Method request at the client side FIG-1468506c4b30f354	AUTOSAR_AP_SWS_CommunicationManagement, AUTOSAR_SWS_CommunicationManagement	R21-11R22-11R23-11R24-11	✓ Beschrieben
Figure 7.22: Payload covered by SecOC and Signal2Service transport FIG-15eeff415f8542ef	AUTOSAR_AP_SWS_CommunicationManagement	R23-11	✓ Beschrieben
Figure 7.18: E2E Subscriber FIG-1ac0b4daefe02812	AUTOSAR_AP_SWS_CommunicationManagement	R25-11	✓ Beschrieben
Figure 7.14: One-dimensional arrays (Example) FIG-1c86676540cb67d0	AUTOSAR_AP_SWS_CommunicationManagement	R23-11	✓ Beschrieben
Figure 5.1: Interfaces provided by Communication Management to other Functional Clusters FIG-1e90f7277c644d74	AUTOSAR_AP_SWS_CommunicationManagement	R25-11	✓ Beschrieben
Figure 7.9: Example serialization settings FIG-23695156beae721c	AUTOSAR_AP_SWS_CommunicationManagement	R23-11R24-11R25-11	✓ Beschrieben
Figure 7.24: Send a GET Message FIG-28cda9105790850e	AUTOSAR_AP_SWS_CommunicationManagement	R25-11	✓ Beschrieben
Figure 7.1: Technical Architecture of Communication Management FIG-2b2b2032dc17938d	AUTOSAR_AP_SWS_CommunicationManagement, AUTOSAR_SWS_CommunicationManagement	R21-11R22-11R23-11R24-11+1	✓ Beschrieben
Figure 7.37: Send an UPDATE Message FIG-2ef780ac297318fe	AUTOSAR_AP_SWS_CommunicationManagement, AUTOSAR_SWS_CommunicationManagement	R22-11R23-11	✓ Beschrieben
Figure 7.14: Payload covered by SecOC and SOME/IP transport FIG-2fc10aa652109c73	AUTOSAR_AP_SWS_CommunicationManagement	R25-11	✓ Beschrieben
Figure 7.23: Input for for signal based SecOC configuration FIG-3a961675b607e491	AUTOSAR_AP_SWS_CommunicationManagement	R23-11	✓ Beschrieben
Figure 5.1: Interfaces provided by Communication Management to other Functional Clusters FIG-413a0750b1675869	AUTOSAR_AP_SWS_CommunicationManagement	R23-11	✓ Beschrieben
Figure 7.6: Serialization of Structs with Length Fields (Example) FIG-41980e63748c84b0	AUTOSAR_AP_SWS_CommunicationManagement	R25-11	✓ Beschrieben
Figure 7.27: Send a SET Message FIG-498654e3e5472b57	AUTOSAR_AP_SWS_CommunicationManagement	R24-11R25-11	✓ Beschrieben
Figure 7.34: Send a SET Message FIG-4c776f23b6ceb283	AUTOSAR_AP_SWS_CommunicationManagement, AUTOSAR_SWS_CommunicationManagement	R22-11R23-11	✓ Beschrieben
Figure 7.33: Receive response to a GET Message FIG-4f05353e3c8f8b20	AUTOSAR_AP_SWS_CommunicationManagement, AUTOSAR_SWS_CommunicationManagement	R22-11R23-11	✓ Beschrieben
Figure 7.31: Send a GET Message FIG-503a2967bdac8650	AUTOSAR_AP_SWS_CommunicationManagement	R23-11	✓ Beschrieben
Figure 7.4: Service contract versioning flow FIG-5396d479742b7e4d	AUTOSAR_AP_SWS_CommunicationManagement, AUTOSAR_SWS_CommunicationManagement	R19-11R20-11R21-11R22-11+3	✓ Beschrieben
Figure 7.32: Receive a GET Message FIG-53f161e344ef1b9e	AUTOSAR_AP_SWS_CommunicationManagement	R23-11	✓ Beschrieben
Figure 7.15: Payload covered by SecOC and Signal2Service transport FIG-548965b043a31bbd	AUTOSAR_AP_SWS_CommunicationManagement	R25-11	✓ Beschrieben
Figure 7.15: Payload covered by SecOC and Signal2Service transport FIG-5a2ab0fc1dd24e8e	AUTOSAR_AP_SWS_CommunicationManagement	R24-11	✓ Beschrieben
Figure 7.20: Interaction of components during E2E checking of the Method request at the server side - polling FIG-5a75db8a28d5d65e	AUTOSAR_AP_SWS_CommunicationManagement, AUTOSAR_SWS_CommunicationManagement	R20-11R21-11R22-11R23-11+1	✓ Beschrieben
Figure 7.13: Freshness Value Management Pluggable Library FIG-608967a8391be6da	AUTOSAR_AP_SWS_CommunicationManagement, AUTOSAR_SWS_CommunicationManagement	R20-11R22-11R23-11R24-11+1	✓ Beschrieben
Figure 7.5: Serialization of Structs without Length Fields (Example) FIG-646993feb22a770a	AUTOSAR_AP_SWS_CommunicationManagement	R24-11	✓ Beschrieben
Figure 7.18: SecOC embedded in the Adaptive Communication Management FIG-646d1e6057477e17	AUTOSAR_AP_SWS_CommunicationManagement	R23-11	✓ Beschrieben
Figure 7.8: Multi-dimensional arrays (Example) FIG-6bf9d9a6d91d4381	AUTOSAR_AP_SWS_CommunicationManagement	R25-11	✓ Beschrieben
Figure 7.16: Input for for signal based SecOC configuration FIG-6fa43aba7c3e34a8	AUTOSAR_AP_SWS_CommunicationManagement	R24-11	✓ Beschrieben
Figure 7.17: E2E Publisher FIG-73063b4fc89ff346	AUTOSAR_AP_SWS_CommunicationManagement	R24-11	✓ Beschrieben
Figure 5.2: Interfaces required by Communication Management from other Functional Clusters FIG-73b6b6a3a4efeda5	AUTOSAR_AP_SWS_CommunicationManagement	R25-11	✓ Beschrieben
Figure 7.25: Receive a GET Message FIG-80ccb5622b15291c	AUTOSAR_AP_SWS_CommunicationManagement	R24-11	✓ Beschrieben
Figure 7.17: E2E Publisher FIG-83ad51e4a7f78dc9	AUTOSAR_AP_SWS_CommunicationManagement	R25-11	✓ Beschrieben
Figure 7.5: Serialization of Structs without Length Fields (Example) FIG-83d9605f087880fd	AUTOSAR_AP_SWS_CommunicationManagement	R25-11	✓ Beschrieben
Figure 7.20: Interaction of components during E2E checking of the Method request at the server side - polling FIG-8451105d69671ff9	AUTOSAR_AP_SWS_CommunicationManagement	R25-11	✓ Beschrieben
Figure 5.2: Interfaces required by Communication Management from other Functional Clusters FIG-8913c2072a6e4e17	AUTOSAR_AP_SWS_CommunicationManagement	R23-11	✓ Beschrieben
Figure 7.14: Payload covered by SecOC and SOME/IP transport FIG-89503668ed01de1e	AUTOSAR_AP_SWS_CommunicationManagement, AUTOSAR_SWS_CommunicationManagement	R22-11R24-11	✓ Beschrieben
Figure 7.7: One-dimensional arrays (Example) FIG-8eab96c234fa83cd	AUTOSAR_AP_SWS_CommunicationManagement	R25-11	✓ Beschrieben
Figure 7.10: Local and Remote Identity and Access Management FIG-8f0a8cd4a35ae885	AUTOSAR_AP_SWS_CommunicationManagement, AUTOSAR_SWS_CommunicationManagement	R20-11R22-11R24-11R25-11	✓ Beschrieben
Figure 7.19: Interaction of components during E2E protection of the Method request at the client side FIG-8f44c677ff30474f	AUTOSAR_AP_SWS_CommunicationManagement	R25-11	✓ Beschrieben
Figure 7.24: Send a GET Message FIG-903c2b145ceaeec0	AUTOSAR_AP_SWS_CommunicationManagement	R24-11	✓ Beschrieben
Figure 5.3: Interfaces required by Communication Management from other Functional Clusters FIG-906b8308f6bc52bf	AUTOSAR_AP_SWS_CommunicationManagement	R24-11	✓ Beschrieben
Figure 7.8: Multi-dimensional arrays (Example) FIG-963fc0a4f68f9723	AUTOSAR_AP_SWS_CommunicationManagement	R24-11	✓ Beschrieben
Figure 7.11: SecOC embedded in the Adaptive Communication Management FIG-980c957f3dbc796d	AUTOSAR_AP_SWS_CommunicationManagement	R25-11	✓ Beschrieben
Figure 7.31: Receive an UPDATE Message FIG-98e56e205caf7c82	AUTOSAR_AP_SWS_CommunicationManagement	R25-11	✓ Beschrieben
Figure 7.24: E2E Publisher FIG-9d0361c557001d4f	AUTOSAR_AP_SWS_CommunicationManagement, AUTOSAR_SWS_CommunicationManagement	R21-11R22-11R23-11	✓ Beschrieben
Figure 7.11: SecOC embedded in the Adaptive Communication Management FIG-9dd8e1632a5b19da	AUTOSAR_AP_SWS_CommunicationManagement	R24-11	✓ Beschrieben
Figure 7.19: SOME/IP header structure FIG-9f94e02b4d390990	AUTOSAR_AP_SWS_CommunicationManagement	R23-11	✓ Beschrieben
Figure 7.12: Serialization of Structs without Length Fields (Example) FIG-ac993fc77c10464b	AUTOSAR_AP_SWS_CommunicationManagement, AUTOSAR_SWS_CommunicationManagement	R21-11R23-11	✓ Beschrieben
Figure 7.31: Receive an UPDATE Message FIG-ae1e73fa09e768b7	AUTOSAR_AP_SWS_CommunicationManagement	R24-11	✓ Beschrieben
Figure 7.8: Communication Group Template FIG-af313d45c327fc84	AUTOSAR_AP_SWS_CommunicationManagement	R23-11	✓ Beschrieben
Figure 5.1: Interfaces provided by Communication Management to other Functional Clusters FIG-afe91500698b4f67	AUTOSAR_AP_SWS_CommunicationManagement	R24-11	✓ Beschrieben
Figure 7.30: Send an UPDATE Message FIG-b5bf2e5038b30b9e	AUTOSAR_AP_SWS_CommunicationManagement	R24-11R25-11	✓ Beschrieben
Figure 7.21: Payload covered by SecOC and SOME/IP transport FIG-b5c0a1d8f9754a97	AUTOSAR_AP_SWS_CommunicationManagement	R23-11	✓ Beschrieben
Figure 5.2: Interfaces required by Communication Management from other Functional Clusters FIG-b81b078478513361	AUTOSAR_AP_SWS_CommunicationManagement	R24-11	✓ Beschrieben
Figure 7.12: SOME/IP header structure FIG-ba248b9bc2a4b73f	AUTOSAR_AP_SWS_CommunicationManagement	R24-11	✓ Beschrieben
Figure 7.15: Multi-dimensional arrays (Example) FIG-be9c5730050b30fb	AUTOSAR_AP_SWS_CommunicationManagement	R23-11	✓ Beschrieben
Figure 7.29: Receive response to a SET Message FIG-c28ee19fe4aeba7b	AUTOSAR_AP_SWS_CommunicationManagement	R24-11	✓ Beschrieben
Figure 7.23: Interaction of components during E2E checking of the Method response at the client side FIG-c383ad7aeb323c45	AUTOSAR_AP_SWS_CommunicationManagement	R25-11	✓ Beschrieben
Figure 7.36: Receive response to a SET Message FIG-c4be81ea1b09fb81	AUTOSAR_AP_SWS_CommunicationManagement, AUTOSAR_SWS_CommunicationManagement	R22-11R23-11	✓ Beschrieben
Figure 7.5: Serialization of Structs with Length Fields (Example) FIG-c8edc4f01efc6df5	AUTOSAR_AP_SWS_CommunicationManagement, AUTOSAR_CP_SWS_SOMEIPTransformer (+2)	R18-10_R4.4.0_R1.5.0R18-10-1R21-11R22-11+2	✓ Beschrieben
Figure 7.26: Receive response to a GET Message FIG-c9e242bc10acc677	AUTOSAR_AP_SWS_CommunicationManagement	R25-11	✓ Beschrieben
Figure 5.3: Interfaces required by Communication Management from other Functional Clusters FIG-cb7e676283cefced	AUTOSAR_AP_SWS_CommunicationManagement	R25-11	✓ Beschrieben
Figure 7.2: Service-Oriented Communication FIG-cb8f0ea852bec06e	AUTOSAR_AP_SWS_CommunicationManagement, AUTOSAR_SWS_CommunicationManagement	R18-03_R1.4.0R18-10_R4.4.0_R1.5.0R18-10-1R19-03+7	✓ Beschrieben
Figure 7.7: Communication Group service interface categories FIG-cd13f22a21e62e34	AUTOSAR_AP_SWS_CommunicationManagement	R23-11	✓ Beschrieben
Figure 7.18: E2E Subscriber FIG-d0a7f9756c39bd77	AUTOSAR_AP_SWS_CommunicationManagement, AUTOSAR_SWS_CommunicationManagement	R22-11R23-11R24-11	✓ Beschrieben
Figure 7.16: Input for for signal based SecOC configuration FIG-d4b443c92fe31ba3	AUTOSAR_AP_SWS_CommunicationManagement, AUTOSAR_CP_TPS_SystemTemplate	R25-11	✓ Beschrieben
Figure 7.22: Interaction of components during E2E protection of the Method response at the server side FIG-d6125e8a37414cc7	AUTOSAR_AP_SWS_CommunicationManagement	R25-11	✓ Beschrieben
Figure 7.38: Receive an UPDATE Message FIG-dd337b7d09803c56	AUTOSAR_AP_SWS_CommunicationManagement	R23-11	✓ Beschrieben
Figure 7.23: Interaction of components during E2E checking of the Method response at the client side FIG-e215128e484a340b	AUTOSAR_AP_SWS_CommunicationManagement, AUTOSAR_SWS_CommunicationManagement	R20-11R21-11R22-11R23-11+1	✓ Beschrieben
Figure 7.25: Receive a GET Message FIG-eb6d3b5ee018b905	AUTOSAR_AP_SWS_CommunicationManagement	R25-11	✓ Beschrieben
Figure 7.12: SOME/IP header structure FIG-ebd99d7d27262710	AUTOSAR_AP_SWS_CommunicationManagement	R25-11	✓ Beschrieben
Figure 7.17: Local and Remote Identity and Access Management FIG-edc6d18e001fee6c	AUTOSAR_AP_SWS_CommunicationManagement, AUTOSAR_SWS_CommunicationManagement	R21-11R23-11	✓ Beschrieben
Figure 7.21: Interaction of components during E2E checking of the Method request at the server side - event driven FIG-f51da3f6194bebdf	AUTOSAR_AP_SWS_CommunicationManagement	R24-11R25-11	✓ Beschrieben
Figure 7.35: Receive a SET Message FIG-f8354dedb5c29d70	AUTOSAR_AP_SWS_CommunicationManagement, AUTOSAR_SWS_CommunicationManagement	R22-11R23-11	✓ Beschrieben
Figure 7.26: Receive response to a GET Message FIG-ff3a9dbfa23e5837	AUTOSAR_AP_SWS_CommunicationManagement	R24-11	✓ Beschrieben
Figure 7.7: Key deployment FIG-0b89c2611fb97b10	AUTOSAR_AP_SWS_Cryptography	R24-11	✓ Beschrieben
Figure 7.5: Key Slot types and usages FIG-1645707e16e96c7a	AUTOSAR_AP_SWS_Cryptography, AUTOSAR_SWS_Cryptography	R20-11R21-11R22-11R23-11+1	✓ Beschrieben
Figure 7.4: Integration into AUTOSAR FIG-1811e3d3ca36f657	AUTOSAR_AP_SWS_Cryptography, AUTOSAR_SWS_Cryptography	R22-11R23-11R24-11	✓ Beschrieben
Figure 7.3: Concurrent access to a single Key Slot FIG-29c1d438b89bc459	AUTOSAR_AP_SWS_Cryptography, AUTOSAR_SWS_Cryptography	R20-11R21-11R22-11R23-11	✓ Beschrieben
Figure 7.8: Certificate deployment FIG-3039af3d10a88402	AUTOSAR_AP_SWS_Cryptography	R23-11	✓ Beschrieben
Figure 7.1: High-level CryptoAPI architecture FIG-46e28603f60e18ec	AUTOSAR_AP_SWS_Cryptography, AUTOSAR_SWS_Cryptography	R20-11R21-11R22-11R23-11+1	✓ Beschrieben
Figure 7.1: Exemplary High-level FC Crypto architecture FIG-636773f7055a8a48	AUTOSAR_AP_SWS_Cryptography	R25-11	✓ Beschrieben
Figure 7.2: Interaction with IAM FIG-684ac4cd5d6a2edb	AUTOSAR_AP_SWS_Cryptography, AUTOSAR_SWS_Cryptography	R20-11R21-11R22-11R23-11	✓ Beschrieben
Figure 7.3: Concurrent access to a single Key Slot FIG-7672b8a2221a5645	AUTOSAR_AP_SWS_Cryptography	R24-11	✓ Beschrieben
Figure 5.1: Interfaces provided by Cryptography to other Functional Clusters FIG-80ae8ae5d71f1a16	AUTOSAR_AP_SWS_Cryptography	R23-11R24-11	✓ Beschrieben
Figure 7.7: Key deployment FIG-825a0e8ccdc69525	AUTOSAR_AP_SWS_Cryptography	R23-11	✓ Beschrieben
Figure 5.1: Interfaces provided by Cryptography to other Functional Clusters FIG-a704d4d80f20b0b0	AUTOSAR_AP_SWS_Cryptography	R25-11	✓ Beschrieben
Figure 7.6: Application interface FIG-b506c0d91f834c55	AUTOSAR_AP_SWS_Cryptography	R23-11	✓ Beschrieben
Figure 7.6: Application interface FIG-caffa5761c31d86c	AUTOSAR_AP_SWS_Cryptography	R24-11	✓ Beschrieben
Figure 7.2: Interaction with IAM FIG-db4a5826b5bee4f8	AUTOSAR_AP_SWS_Cryptography	R24-11	✓ Beschrieben
Figure 7.8: Certificate deployment FIG-fce068a1539ce5e2	AUTOSAR_AP_SWS_Cryptography	R24-11	✓ Beschrieben
Figure 7.5: Example of diagnostic event usage FIG-0d430b2c380f07b8	AUTOSAR_AP_SWS_Diagnostics	R25-11	✓ Beschrieben
Figure 7.1: Component view on Diagnostic Management FIG-0fd5f46e518bfe28	AUTOSAR_AP_SWS_Diagnostics, AUTOSAR_SWS_Diagnostics	R22-11R23-11R24-11R25-11	✓ Beschrieben
Figure 7.3: UDS request assignment to a Diagnostic Conversation and Prioritization FIG-2ba2ed580ca48cfd	AUTOSAR_AP_SWS_Diagnostics	R24-11R25-11	✓ Beschrieben
Figure 5.1: Interfaces required by Diagnostic Management FIG-59961ac312283cd0	AUTOSAR_AP_SWS_Diagnostics	R24-11	✓ Beschrieben
Figure 1.1: Architecture Diagnostic Communication Management FIG-632d2698937c9f8d	AUTOSAR_AP_SWS_Diagnostics, AUTOSAR_SWS_Diagnostics	R19-03R19-11R20-11R21-11+2	✓ Beschrieben
Figure 7.8: Combined displacement criteria processing FIG-663987a8ae5c47dc	AUTOSAR_AP_SWS_Diagnostics, AUTOSAR_SWS_Diagnostics	R20-11R21-11R22-11R23-11+2	✓ Beschrieben
Figure 1.2: Diagnostic Managers external dependencies FIG-7b21b547b0060e01	AUTOSAR_AP_SWS_Diagnostics, AUTOSAR_SWS_Diagnostics	R18-10_R4.4.0_R1.5.0R18-10-1R19-03R19-11+6	✓ Beschrieben
Figure 7.4: SOVD Software Update API - concept. Figure elobarates on the difference of vehicle level and component level SOVD Software Update API. FIG-7f382d02da0dc4c2	AUTOSAR_AP_SWS_Diagnostics	R23-11R24-11	✓ Beschrieben
Figure 7.2: Example Sequence Diagram for Activation Line and Vehicle Announcement API use case FIG-86c8e0b03bbc6052	AUTOSAR_AP_SWS_Diagnostics, AUTOSAR_SWS_Diagnostics	R20-11R21-11R22-11R24-11+1	✓ Beschrieben
Figure 5.3: Interfaces required by Diagnostic Management from State Management FIG-8e396ba445473944	AUTOSAR_AP_SWS_Diagnostics	R23-11	✓ Beschrieben
Figure 7.4: SOVD Software Update API - concept. Figure elaborates on the difference of vehicle level and component level SOVD Software Update API. FIG-8fd091c1c22fe06c	AUTOSAR_AP_SWS_Diagnostics	R25-11	✓ Beschrieben
Figure 7.5: Example of diagnostic event usage FIG-92f1377488ab8cb7	AUTOSAR_AP_SWS_Diagnostics	R24-11	✓ Beschrieben
Figure 7.3: UDS request assignment to a Diagnostic Conversation and Prioritization FIG-9fb7452dc70a45fd	AUTOSAR_AP_SWS_Diagnostics	R23-11	✓ Beschrieben
Figure 7.5: Example of diagnostic event usage FIG-adfd898528327f83	AUTOSAR_AP_SWS_Diagnostics	R23-11	✓ Beschrieben
Figure 5.1: Interfaces required by Diagnostic Management FIG-c93e956bb4c310ca	AUTOSAR_AP_SWS_Diagnostics	R23-11	✓ Beschrieben
Figure 7.2: Example Sequence Diagram for Activation Line and Vehicle Announcement API use case FIG-cf0a40570a18fd4d	AUTOSAR_AP_SWS_Diagnostics	R23-11	✓ Beschrieben
Figure 5.1: Interfaces required by Diagnostic Management FIG-dd536bac3ead256c	AUTOSAR_AP_SWS_Diagnostics	R25-11	✓ Beschrieben
Figure 1.1: Architecture Diagnostic Communication Management FIG-e1f08839f5b31527	AUTOSAR_AP_SWS_Diagnostics	R24-11R25-11	✓ Beschrieben
Figure 7.3: process Lifecycle FIG-005c3bee22f201ea	AUTOSAR_AP_SWS_ExecutionManagement	R24-11	✓ Beschrieben
Figure 7.17: Authenticated start-up sequence FIG-081f95efb6b478da	AUTOSAR_AP_SWS_ExecutionManagement, AUTOSAR_SWS_ExecutionManagement	R19-11R20-11R21-11R22-11+3	✓ Beschrieben
Figure 7.4: process Lifecycle FIG-0949e82793af1e50	AUTOSAR_AP_SWS_ExecutionManagement	R23-11	✓ Beschrieben
Figure 7.2: Executable Lifecycle from deployment to execution FIG-0eec1bbfd3003378	AUTOSAR_AP_SWS_ExecutionManagement, AUTOSAR_SWS_ExecutionManagement	R19-11R20-11R21-11R22-11+1	✓ Beschrieben
Figure 7.6: AUTOSAR Adaptive Platform Boundary FIG-1a7d041b3f9ace4f	AUTOSAR_AP_SWS_ExecutionManagement	R24-11R25-11	✓ Beschrieben
Figure 7.2: Execution States FIG-1d0d0a5882324e77	AUTOSAR_AP_SWS_ExecutionManagement	R25-11	✓ Beschrieben
Figure 7.18: Worker Pool Usage FIG-217fa3a8c5912055	AUTOSAR_AP_SWS_ExecutionManagement, AUTOSAR_SWS_ExecutionManagement	R21-11R22-11R23-11	✓ Beschrieben
Figure 7.6: Startup sequence FIG-26fca520fc2b271e	AUTOSAR_AP_SWS_ExecutionManagement, AUTOSAR_SWS_ExecutionManagement	R21-11R22-11R23-11	✓ Beschrieben
Figure 7.1: Executable Lifecycle from deployment to execution FIG-28f2b91096363fc3	AUTOSAR_AP_SWS_ExecutionManagement	R25-11	✓ Beschrieben
Figure 7.26: Process Mode with multiple DeterministicSyncMasters FIG-2ff45f67eaef0269	AUTOSAR_AP_SWS_ExecutionManagement, AUTOSAR_SWS_ExecutionManagement	R22-11R23-11	✓ Beschrieben
Figure 7.13: Interaction between states FIG-31e1006113707d77	AUTOSAR_AP_SWS_ExecutionManagement	R23-11	✓ Beschrieben
Figure 7.7: Start-up Sequence – from Startup to initial running state StateXYZ FIG-39e00c33394bcaee	AUTOSAR_AP_SWS_ExecutionManagement	R25-11	✓ Beschrieben
Figure 7.23: An example deployment of DeterministicSyncMaster in a separate process FIG-40369c7cb479b20a	AUTOSAR_AP_SWS_ExecutionManagement, AUTOSAR_SWS_ExecutionManagement	R20-11R21-11R22-11R23-11	✓ Beschrieben
Figure 7.8: State Change Sequence - Success FIG-5ebda63875330476	AUTOSAR_AP_SWS_ExecutionManagement	R23-11R24-11R25-11	✓ Beschrieben
Figure 7.12: State dependent process control FIG-5f5a5175ab2cdb97	AUTOSAR_AP_SWS_ExecutionManagement, AUTOSAR_SWS_ExecutionManagement	R22-11R23-11	✓ Beschrieben
Figure 7.27: Memory Usage. FIG-60d458f270314f8c	AUTOSAR_AP_SWS_ExecutionManagement	R23-11	✓ Beschrieben
Figure 5.2: Interfaces provided by Execution Management to State Management FIG-66aef658b5b6965e	AUTOSAR_AP_SWS_ExecutionManagement	R23-11	✓ Beschrieben
Figure 7.7: Start-up Sequence – from Startup to initial running state StateXYZ FIG-6c839eebde4e6a26	AUTOSAR_AP_SWS_ExecutionManagement, AUTOSAR_AP_SWS_StateManagement	R24-11	✓ Beschrieben
Figure 7.2: Execution States FIG-72659ebc7cbf5ef1	AUTOSAR_AP_SWS_ExecutionManagement, AUTOSAR_SWS_ExecutionManagement	R21-11R22-11R23-11R24-11	✓ Beschrieben
Figure 7.7: AUTOSAR Adaptive Platform Boundary FIG-75676d1783ef89ca	AUTOSAR_AP_SWS_ExecutionManagement, AUTOSAR_SWS_ExecutionManagement	R20-11R21-11R22-11R23-11	✓ Beschrieben
Figure 7.12: Interaction between states FIG-76514b2cecf12762	AUTOSAR_AP_SWS_ExecutionManagement	R24-11R25-11	✓ Beschrieben
Figure 7.25: Library Mode with multiple DeterministicSyncMasters FIG-769e374d1667afe9	AUTOSAR_AP_SWS_ExecutionManagement, AUTOSAR_SWS_ExecutionManagement	R21-11R22-11R23-11	✓ Beschrieben
Figure 7.1: Executable Lifecycle from deployment to execution FIG-79c932aa03f3433d	AUTOSAR_AP_SWS_ExecutionManagement, AUTOSAR_SWS_ExecutionManagement	R17-10_R1.2.0R24-11	✓ Beschrieben
Figure 7.5: Startup sequence FIG-8b15375370b603f6	AUTOSAR_AP_SWS_ExecutionManagement	R24-11R25-11	✓ Beschrieben
Figure 7.9: State Change Sequence - Termination Timeout FIG-8b2cbea8e7a839d0	AUTOSAR_AP_SWS_ExecutionManagement	R23-11R24-11R25-11	✓ Beschrieben
Figure 7.13: Example configuration for state transition FIG-960f6c5d7c82e482	AUTOSAR_AP_SWS_ExecutionManagement	R24-11R25-11	✓ Beschrieben
Figure 7.1: Types of Applications FIG-968bae4d93b28dc8	AUTOSAR_AP_SWS_ExecutionManagement, AUTOSAR_SWS_ExecutionManagement	R22-11R23-11	✓ Beschrieben
Figure 7.11: State dependent Process control FIG-99a84c70dca495a7	AUTOSAR_AP_SWS_ExecutionManagement	R24-11R25-11	✓ Beschrieben
Figure 5.3: Interfaces required by Execution Management from other Functional Clusters FIG-9d407fb564598e4f	AUTOSAR_AP_SWS_ExecutionManagement	R23-11	✓ Beschrieben
Figure 7.5: Execution dependencies on Non-reporting Process FIG-a598ab554dd6def8	AUTOSAR_AP_SWS_ExecutionManagement	R23-11	✓ Beschrieben
Figure 7.3: Process Lifecycle FIG-aec6019ca08781b6	AUTOSAR_AP_SWS_ExecutionManagement	R25-11	✓ Beschrieben
Figure 5.3: Interfaces required by Execution Management from other Functional Clusters FIG-be0df6e661a9114f	AUTOSAR_AP_SWS_ExecutionManagement	R25-11	✓ Beschrieben
Figure 7.22: Sequence Diagram of the Synchronization Control Messages with single DeterministicSyncMaster FIG-c846483916d38c9e	AUTOSAR_AP_SWS_ExecutionManagement, AUTOSAR_SWS_ExecutionManagement	R22-11R23-11	✓ Beschrieben
Figure 7.14: Example configuration for state transition FIG-cddb7208b83f9339	AUTOSAR_AP_SWS_ExecutionManagement	R23-11	✓ Beschrieben
Figure 7.17: Deterministic Execution Interface FIG-d96b0e2a2da5440d	AUTOSAR_AP_SWS_ExecutionManagement, AUTOSAR_SWS_ExecutionManagement	R18-10_R4.4.0_R1.5.0R18-10-1R19-03R19-11+4	✓ Beschrieben
Figure 7.16: General Fault Tolerance scheme. FIG-dce589773e18556c	AUTOSAR_AP_SWS_ExecutionManagement, AUTOSAR_SWS_ExecutionManagement	R18-03_R1.4.0R18-10_R4.4.0_R1.5.0R18-10-1R19-03+7	✓ Beschrieben
Figure 5.3: Interfaces required by Execution Management from other Functional Clusters FIG-de92b4ec298b8b1e	AUTOSAR_AP_SWS_ExecutionManagement	R24-11	✓ Beschrieben
Figure 7.16: Cyclic Deterministic Execution FIG-df77b653573b5825	AUTOSAR_AP_SWS_ExecutionManagement, AUTOSAR_SWS_ExecutionManagement	R22-11R23-11	✓ Beschrieben
Figure 5.1: Interfaces provided by Execution Management to other Functional Clusters FIG-e113b69ca925db45	AUTOSAR_AP_SWS_ExecutionManagement	R25-11	✓ Beschrieben
Figure 7.1: Start-up Sequence – from Startup to initial running state Driving FIG-e4f340069869fc8c	AUTOSAR_AP_SWS_ExecutionManagement, AUTOSAR_AP_SWS_StateManagement (+1)	R21-11R22-11R23-11	✓ Beschrieben
Figure 7.15: Memory Usage. FIG-ed26489460cb3ee2	AUTOSAR_AP_SWS_ExecutionManagement	R24-11R25-11	✓ Beschrieben
Figure 7.4: Execution dependencies on Non-reporting Process FIG-f306f73ab3b88c68	AUTOSAR_AP_SWS_ExecutionManagement	R24-11R25-11	✓ Beschrieben
Figure 5.1: Interfaces provided by Execution Management to other Functional Clusters FIG-f3e781a184c26300	AUTOSAR_AP_SWS_ExecutionManagement	R23-11R24-11	✓ Beschrieben
Figure 7.24: process mode (left) and library mode (right) integration FIG-f409f0a87c2aa9cc	AUTOSAR_AP_SWS_ExecutionManagement, AUTOSAR_SWS_ExecutionManagement	R22-11R23-11	✓ Beschrieben
Figure 5.2: Interfaces provided by Execution Management to State Management FIG-f89e84391d8711ac	AUTOSAR_AP_SWS_ExecutionManagement	R24-11	✓ Beschrieben
Figure 7.10: State Change Sequence - Start-up Timeout FIG-fe9b54c5bad9fdde	AUTOSAR_AP_SWS_ExecutionManagement	R23-11R24-11R25-11	✓ Beschrieben
Figure 7.14: Dependency resolution during state change FIG-ff083daa367d1c38	AUTOSAR_AP_SWS_ExecutionManagement, AUTOSAR_SWS_ExecutionManagement	R22-11R23-11R24-11R25-11	✓ Beschrieben
Figure 7.3: SEV protocol matching process FIG-36954d5de5e355d4	AUTOSAR_AP_SWS_Firewall, AUTOSAR_CP_SWS_Firewall	R23-11R24-11R25-11	✓ Beschrieben
Figure 5.1: Interfaces required by Firewall from other Functional Clusters FIG-581fe21980f174e8	AUTOSAR_AP_SWS_Firewall	R23-11	✓ Beschrieben
Figure 7.1: Pattern matching mechanism FIG-5a5cc1ec71aff78d	AUTOSAR_AP_SWS_Firewall	R25-11	✓ Beschrieben
Figure 7.1: Pattern matching mechanism FIG-6aa5c3f8756b6564	AUTOSAR_AP_SWS_Firewall, AUTOSAR_SWS_AdaptivePlatformFirewall	R22-11R23-11R24-11	✓ Beschrieben
Figure 5.1: Interfaces required by Firewall from other Functional Clusters FIG-93b12a4921a5ef40	AUTOSAR_AP_SWS_Firewall	R25-11	✓ Beschrieben
Figure 7.2: Architecture of the FC Firewall FIG-baddf4c0afa2593b	AUTOSAR_AP_SWS_Firewall	R23-11	✓ Beschrieben
Figure 5.1: Interfaces required by Firewall from other Functional Clusters FIG-baff438035b6c18a	AUTOSAR_AP_SWS_Firewall	R24-11	✓ Beschrieben
Figure 7.2: Architecture of the FC Firewall FIG-c3433766f03dffde	AUTOSAR_AP_SWS_Firewall, AUTOSAR_SWS_AdaptivePlatformFirewall	R22-11R24-11R25-11	✓ Beschrieben
Figure 5.1: Interfaces provided by Intrusion Detection System Mananger to other Functional Clusters FIG-2b75259e9d1b0547	AUTOSAR_AP_SWS_IntrusionDetectionSystemManager	R23-11	✓ Beschrieben
Figure 5.1: Interfaces provided by Intrusion Detection System Mananger to other Functional Clusters FIG-47cae0966305baa9	AUTOSAR_AP_SWS_IntrusionDetectionSystemManager	R24-11	✓ Beschrieben
Figure 5.1: Interfaces provided by Intrusion Detection System Mananger to other Functional Clusters FIG-5a50dfec7c852021	AUTOSAR_AP_SWS_IntrusionDetectionSystemManager	R25-11	✓ Beschrieben
Figure 5.2: Interfaces required by Intrusion Detection System Mananger from other Functional Clusters FIG-6929035885358f1d	AUTOSAR_AP_SWS_IntrusionDetectionSystemManager	R24-11	✓ Beschrieben
Figure 5.2: Interfaces required by Intrusion Detection System Mananger from other Functional Clusters FIG-886e4f5f59ac42aa	AUTOSAR_AP_SWS_IntrusionDetectionSystemManager	R25-11	✓ Beschrieben
Figure 5.2: Interfaces required by Intrusion Detection System Mananger from other Functional Clusters FIG-c5e9482fc89b6f34	AUTOSAR_AP_SWS_IntrusionDetectionSystemManager	R23-11	✓ Beschrieben
Figure 1.1: AUTOSAR data type usage in Adaptive Interfaces FIG-2e1f721b51be751d	AUTOSAR_AP_SWS_LanguageBindingForModeledAPdatatypes	R24-11	✓ Beschrieben
Figure 1.1: AUTOSAR data type usage in Adaptive Interfaces FIG-4869c4fb98efd2d7	AUTOSAR_AP_SWS_LanguageBindingForModeledAPdatatypes, AUTOSAR_SWS_LanguageBindingForModeledAPdatatypes	R22-11R23-11	✓ Beschrieben
Figure 7.2: CppImplementationDataType FIG-573f978a098c19b0	AUTOSAR_AP_SWS_LanguageBindingForModeledAPdatatypes	R24-11	✓ Beschrieben
Figure 7.2: CppImplementationDataType FIG-72743e787c8fa244	AUTOSAR_AP_SWS_LanguageBindingForModeledAPdatatypes	R23-11	✓ Beschrieben
Figure 7.1: Methodology: C++ Language Binding generation FIG-805a4a16371fcf32	AUTOSAR_AP_SWS_LanguageBindingForModeledAPdatatypes, AUTOSAR_SWS_LanguageBindingForModeledAPdatatypes	R21-11R22-11R23-11R24-11+1	✓ Beschrieben
Figure 7.2: CppImplementationDataType FIG-810fcd7a75843273	AUTOSAR_AP_SWS_LanguageBindingForModeledAPdatatypes	R25-11	✓ Beschrieben
Figure 1.1: AUTOSAR data type usage in Adaptive Interfaces FIG-9cd87afb1ad0571b	AUTOSAR_AP_SWS_LanguageBindingForModeledAPdatatypes	R25-11	✓ Beschrieben
Figure 7.3: ApApplicationError - Model View FIG-a9efedb68d6424b7	AUTOSAR_AP_SWS_LanguageBindingForModeledAPdatatypes	R24-11R25-11	✓ Beschrieben
Figure 1.2: Methodology: Generic Language Binding generation FIG-aff388e80d427843	AUTOSAR_AP_SWS_LanguageBindingForModeledAPdatatypes, AUTOSAR_SWS_LanguageBindingForModeledAPdatatypes	R21-11R22-11R23-11R24-11+1	✓ Beschrieben
Figure 7.4: ApApplicationError - Example Language Binding FIG-b0eb78cc5c3daf0c	AUTOSAR_AP_SWS_LanguageBindingForModeledAPdatatypes	R24-11R25-11	✓ Beschrieben
Figure 7.1: Log mode FIG-208e0e4f39469c27	AUTOSAR_AP_SWS_LogAndTrace, AUTOSAR_SWS_LogAndTrace	R18-10_R4.4.0_R1.5.0R18-10-1R24-11R25-11	✓ Beschrieben
Figure 7.2: ara::log Modeled Message Generator FIG-236924649919c822	AUTOSAR_AP_SWS_LogAndTrace	R25-11	✓ Beschrieben
Figure 5.2: Interfaces required by Log and Trace from other Functional Clusters FIG-2aa079613c75c7d3	AUTOSAR_AP_SWS_LogAndTrace	R24-11R25-11	✓ Beschrieben
Figure 5.1: Interfaces provided by Log and Trace to other Functional Clusters FIG-2ae999b1b55c74dc	AUTOSAR_AP_SWS_LogAndTrace	R23-11	✓ Beschrieben
Figure 7.1: Log mode FIG-422e1750577eb1cb	AUTOSAR_AP_SWS_LogAndTrace, AUTOSAR_SWS_LogAndTrace	R21-11R22-11R23-11	✓ Beschrieben
Figure 7.4: Example program flow of ara::log/Trace FIG-4f1899d71f735434	AUTOSAR_AP_SWS_LogAndTrace	R24-11R25-11	✓ Beschrieben
Figure 7.4: Example program flow of ara::log/Trace FIG-5aae5d00cd13c25e	AUTOSAR_AP_SWS_LogAndTrace	R23-11	✓ Beschrieben
Figure 5.1: Interfaces provided by Log and Trace to other Functional Clusters FIG-6b8e0a14adb6d799	AUTOSAR_AP_SWS_LogAndTrace	R25-11	✓ Beschrieben
Figure 1.1: Architecture overview FIG-6d466f9a5042eccd	AUTOSAR_AP_SWS_LogAndTrace, AUTOSAR_SWS_LogAndTrace	R18-10_R4.4.0_R1.5.0R18-10-1R19-03R19-11+5	✓ Beschrieben
Figure 7.3: Overview of Tracing FIG-71d775bd0cf105c2	AUTOSAR_AP_SWS_LogAndTrace	R23-11R25-11	✓ Beschrieben
Figure 7.2: ara::log Modeled Message Generator FIG-7ad6a1eec82a1a98	AUTOSAR_AP_SWS_LogAndTrace	R24-11	✓ Beschrieben
Figure 1.1: Architecture overview FIG-925e90bca06d51ce	AUTOSAR_AP_SWS_LogAndTrace	R25-11	✓ Beschrieben
Figure 7.3: Overview of Tracing FIG-b984cc2eb7581df7	AUTOSAR_AP_SWS_LogAndTrace	R24-11	✓ Beschrieben
Figure 5.2: Interfaces required by Log and Trace from other Functional Clusters FIG-d4c53a77c5e70962	AUTOSAR_AP_SWS_LogAndTrace	R23-11	✓ Beschrieben
Figure 5.1: Interfaces provided by Log and Trace to other Functional Clusters FIG-d7bf0075ebd9cd51	AUTOSAR_AP_SWS_LogAndTrace	R24-11	✓ Beschrieben
Figure 7.2: ara::log Modeled Message Generator FIG-e936b52439fd5ee5	AUTOSAR_AP_SWS_LogAndTrace, AUTOSAR_SWS_LogAndTrace	R22-11R23-11	✓ Beschrieben
Figure 1.1: Architecture overview with example applications FIG-0389039a254e9b0c	AUTOSAR_AP_SWS_NetworkManagement, AUTOSAR_SWS_NetworkManagement	R18-10_R4.4.0_R1.5.0R18-10-1R19-03R19-11+6	✓ Beschrieben
Figure 5.2: Interfaces required by Network Management from other Functional Clusters FIG-0fc642fc5308ae86	AUTOSAR_AP_SWS_NetworkManagement	R25-11	✓ Beschrieben
Figure 7.2: State Chart Diagram FIG-199f2061626311c4	AUTOSAR_AP_SWS_NetworkManagement	R23-11	✓ Beschrieben
Figure 5.2: Interfaces required by Network Management from other Functional Clusters FIG-1b467462e258afae	AUTOSAR_AP_SWS_NetworkManagement	R23-11	✓ Beschrieben
Figure 5.1: Interfaces provided by Network Management to other Functional Clusters FIG-31372499f93da936	AUTOSAR_AP_SWS_NetworkManagement	R25-11	✓ Beschrieben
Figure 5.2: Interfaces required by Network Management from other Functional Clusters FIG-3bac69e2ac52b7d9	AUTOSAR_AP_SWS_NetworkManagement	R24-11	✓ Beschrieben
Figure 7.1: Overview Of Network Management FIG-41bb889bfa4f6004	AUTOSAR_AP_SWS_NetworkManagement	R24-11R25-11	✓ Beschrieben
Figure 7.2: State Chart Diagram FIG-46ffeea1454d66d2	AUTOSAR_AP_SWS_NetworkManagement	R24-11	✓ Beschrieben
Figure 7.1: Overview Of Network Management FIG-71aa8eca229fd7b8	AUTOSAR_AP_SWS_NetworkManagement, AUTOSAR_SWS_NetworkManagement	R19-03R19-11R20-11R21-11+2	✓ Beschrieben
Figure 5.1: Interfaces provided by Network Management to other Functional Clusters FIG-a83a638138b1a3bc	AUTOSAR_AP_SWS_NetworkManagement	R23-11	✓ Beschrieben
Figure 5.1: Interfaces provided by Network Management to other Functional Clusters FIG-c4e2ac4bc86b6a56	AUTOSAR_AP_SWS_NetworkManagement	R24-11	✓ Beschrieben
Figure 7.3: minimal state machine of a task FIG-086a62f2d6202511	AUTOSAR_AP_SWS_OperatingSystemInterface	R24-11	✓ Beschrieben
Figure 5.1: Interfaces provided by Operating System Interface to other Functional Clusters FIG-0b69167224d1af10	AUTOSAR_AP_SWS_OperatingSystemInterface	R23-11R24-11	✓ Beschrieben
Figure 5.1: Interfaces provided by Operating System Interface to other Functional Clusters FIG-0c4dda997ff779c5	AUTOSAR_AP_SWS_OperatingSystemInterface	R25-11	✓ Beschrieben
Figure 7.1: Process - Task/Thread Model FIG-152636b8a5ff078f	AUTOSAR_AP_SWS_OperatingSystemInterface	R24-11	✓ Beschrieben
Figure 4.3: Minimal state machine of a task FIG-1b6cf94b0cce6e43	AUTOSAR_AP_SWS_OperatingSystemInterface, AUTOSAR_AP_TR_OperatingSystemTracingInterface	R25-11	✓ Beschrieben
Figure 4.3: Minimal state machine of a task FIG-22eeb009104cbc4c	AUTOSAR_AP_SWS_OperatingSystemInterface, AUTOSAR_AP_TR_OperatingSystemTracingInterface	R23-11	✓ Beschrieben
Figure 7.2: Example layout of the OS/ara::log Adapter FIG-4f235e8f41b5e9ad	AUTOSAR_AP_SWS_OperatingSystemInterface	R25-11	✓ Beschrieben
Figure 7.1: Process - Task/Thread Model FIG-76e9c76c8bb5878c	AUTOSAR_AP_SWS_OperatingSystemInterface	R23-11	✓ Beschrieben
Figure 7.1: Process - Task/Thread Model FIG-95da84422953794d	AUTOSAR_AP_SWS_OperatingSystemInterface	R25-11	✓ Beschrieben
Figure 5.2: Interfaces required by Operating System Interface FIG-a8699a5cb59e62b4	AUTOSAR_AP_SWS_OperatingSystemInterface	R25-11	✓ Beschrieben
Figure 7.2: Example layout of the OS/ara::log Adapter FIG-c18c59723b00c58e	AUTOSAR_AP_SWS_OperatingSystemInterface	R24-11	✓ Beschrieben
Figure 5.2: Interfaces required by Operating System Interface FIG-c239ca9c35be2563	AUTOSAR_AP_SWS_OperatingSystemInterface	R23-11R24-11	✓ Beschrieben
Figure 7.2: Example layout of the OS/ara::log Adapter FIG-e373fbe47b1f92fb	AUTOSAR_AP_SWS_OperatingSystemInterface	R23-11	✓ Beschrieben
Figure 5.2: Interfaces Provided by Persistency to Other Functional Clusters FIG-4a43463e3f1b2067	AUTOSAR_AP_SWS_Persistency	R24-11	✓ Beschrieben
Figure 10.6: Persistency CryptoKeySlot Configuration FIG-564ced8f50907089	AUTOSAR_AP_SWS_Persistency	R25-11	✓ Beschrieben
Figure 10.2: Persistency General Configuration FIG-5f6e89bef4ad9fb9	AUTOSAR_AP_SWS_Persistency	R25-11	✓ Beschrieben
Figure 5.2: Interfaces Provided by Persistency to Other Functional Clusters FIG-6a41c5394491685f	AUTOSAR_AP_SWS_Persistency	R23-11	✓ Beschrieben
Figure 7.1: Typical usage of Persistency within an Adaptive Application FIG-6ae974a265f9870e	AUTOSAR_AP_SWS_Persistency	R24-11	✓ Beschrieben
Figure 10.8: Persistency Redundancy Handling Configuration FIG-7b6ebbce69842cc2	AUTOSAR_AP_SWS_Persistency	R25-11	✓ Beschrieben
Figure 5.1: Interfaces Provided by Persistency to Other Functional Clusters FIG-82cb45f8e0c16cc0	AUTOSAR_AP_SWS_Persistency	R24-11	✓ Beschrieben
Figure 10.5: Persistency Common Configuration FIG-8ecc059689d60e0a	AUTOSAR_AP_SWS_Persistency	R25-11	✓ Beschrieben
Figure 5.2: Interfaces Provided by Persistency to Other Functional Clusters FIG-8f55c4801def9db7	AUTOSAR_AP_SWS_Persistency	R25-11	✓ Beschrieben
Figure 5.3: Interfaces required by Persistency from other Functional Clusters FIG-9a8a55c3fd77c0c2	AUTOSAR_AP_SWS_Persistency	R24-11R25-11	✓ Beschrieben
Figure 5.1: Interfaces Provided by Persistency to Other Functional Clusters FIG-9c4c62a62e074c38	AUTOSAR_AP_SWS_Persistency	R23-11	✓ Beschrieben
Figure 5.1: Interfaces Provided by Persistency to Other Functional Clusters FIG-9c4eedaae28a5c54	AUTOSAR_AP_SWS_Persistency	R25-11	✓ Beschrieben
Figure 10.4: Persistency Key Value Storage Configuration FIG-9db20c7ef81a3027	AUTOSAR_AP_SWS_Persistency	R25-11	✓ Beschrieben
Figure 10.1: Top-level Persistency Configuration FIG-b25b2ef5d6406ccb	AUTOSAR_AP_SWS_Persistency	R25-11	✓ Beschrieben
Figure 10.3: Persistency File Storage Configuration FIG-d71d6530b4c6db96	AUTOSAR_AP_SWS_Persistency	R25-11	✓ Beschrieben
Figure 10.7: Persistency Logging Configuration FIG-d88b33259f684a61	AUTOSAR_AP_SWS_Persistency	R25-11	✓ Beschrieben
Figure 7.1: Typical usage of Persistency within an Adaptive Application FIG-f040c892db68f6ac	AUTOSAR_AP_SWS_Persistency, AUTOSAR_SWS_Persistency	R21-11R22-11R23-11	✓ Beschrieben
Figure 7.1: Typical usage of Persistency within an Adaptive Application FIG-f14d6d93fe3a5938	AUTOSAR_AP_SWS_Persistency	R25-11	✓ Beschrieben
Figure 5.3: Interfaces required by Persistency from other Functional Clusters FIG-fcf25fd3af9c7692	AUTOSAR_AP_SWS_Persistency	R23-11	✓ Beschrieben
Figure 5.2: Interfaces required by Platform Health Management from other Functional Clusters FIG-2bce48466bb4bedb	AUTOSAR_AP_SWS_PlatformHealthManagement	R23-11	✓ Beschrieben
Figure 7.6: Platform Health Management and the environment FIG-2be2acee6b383b1f	AUTOSAR_AP_SWS_PlatformHealthManagement	R24-11	✓ Beschrieben
Figure 7.7: Example of multiple instance of the same Supervised Entity FIG-2c24c37928c4f465	AUTOSAR_AP_SWS_PlatformHealthManagement	R24-11R25-11	✓ Beschrieben
Figure 7.6: Platform Health Management and the environment FIG-357cf5965ec00735	AUTOSAR_AP_SWS_PlatformHealthManagement	R25-11	✓ Beschrieben
Figure 7.2: Mappings of Elementary Supervisions to Global Supervisions which are not supported FIG-38f95675c0546a72	AUTOSAR_AP_SWS_PlatformHealthManagement	R23-11R24-11	✓ Beschrieben
Figure 7.1: Allowed mappings of Elementary Supervisions to Global Supervisions FIG-40f7049a6bfd8075	AUTOSAR_AP_SWS_PlatformHealthManagement	R24-11	✓ Beschrieben
Figure 7.3: Health Channel configuration FIG-47c0deeb1a16caa4	AUTOSAR_AP_SWS_PlatformHealthManagement, AUTOSAR_SWS_PlatformHealthManagement	R22-11R23-11	✓ Beschrieben
Figure 7.3: Supervision Exclusion and change of Function Group State FIG-68bbc7973ce2b0e3	AUTOSAR_AP_SWS_PlatformHealthManagement, AUTOSAR_SWS_PlatformHealthManagement	R21-11R22-11R23-11R24-11+1	✓ Beschrieben
Figure 7.5: Global Supervision Status FIG-6979f2ebbde49c7c	AUTOSAR_AP_SWS_PlatformHealthManagement	R24-11	✓ Beschrieben
Figure 5.1: Interfaces provided by Platform Health Management to other Functional Clusters FIG-6a62f08d78f1c4c7	AUTOSAR_AP_SWS_PlatformHealthManagement	R23-11	✓ Beschrieben
Figure 5.2: Interfaces required by Platform Health Management from other Functional Clusters FIG-7077eb7037de5a00	AUTOSAR_AP_SWS_PlatformHealthManagement	R25-11	✓ Beschrieben
Figure 7.1: Allowed mappings of Elementary Supervisions to Global Supervisions FIG-755c81ad7f9c1e77	AUTOSAR_AP_SWS_PlatformHealthManagement	R25-11	✓ Beschrieben
Figure 5.1: Interfaces provided by Platform Health Management to other Functional Clusters FIG-7bd3876b5d795907	AUTOSAR_AP_SWS_PlatformHealthManagement	R24-11	✓ Beschrieben
Figure 5.2: Interfaces required by Platform Health Management from other Functional Clusters FIG-81bfab3914e87993	AUTOSAR_AP_SWS_PlatformHealthManagement	R24-11	✓ Beschrieben
Figure 7.1: Allowed mappings of Elementary Supervisions to Global Supervisions FIG-88512f42c26454c4	AUTOSAR_AP_SWS_PlatformHealthManagement	R23-11	✓ Beschrieben
Figure 7.4: Elementary Supervision Status FIG-b97dcef1b57b78dd	AUTOSAR_AP_SWS_PlatformHealthManagement, AUTOSAR_SWS_PlatformHealthManagement	R22-11R23-11R24-11R25-11	✓ Beschrieben
Figure 7.8: Example of multiple instance of the same Supervised Entity FIG-d155c847e51eb97d	AUTOSAR_AP_SWS_PlatformHealthManagement, AUTOSAR_SWS_PlatformHealthManagement	R22-11R23-11	✓ Beschrieben
Figure 7.5: Global Supervision Status FIG-e06124fedc0ba091	AUTOSAR_AP_SWS_PlatformHealthManagement, AUTOSAR_SWS_PlatformHealthManagement	R22-11R23-11R25-11	✓ Beschrieben
Figure 5.1: Interfaces provided by Platform Health Management to other Functional Clusters FIG-ea096371f5a5c338	AUTOSAR_AP_SWS_PlatformHealthManagement	R25-11	✓ Beschrieben
Figure 7.2: Mappings of Elementary Supervisions to Global Supervisions which are not supported FIG-f32a69cce8c2652a	AUTOSAR_AP_SWS_PlatformHealthManagement	R25-11	✓ Beschrieben
Figure 7.2: The currently supported use cases for Raw Data Streams, and which artifacts in the Deployment model that shall be used to configure the different use cases FIG-0e1f8740cef7414a	AUTOSAR_AP_SWS_RawDataStream	R23-11R24-11R25-11	✓ Beschrieben
Figure 7.4: IEEE1722 subtype class inheritance hierarchy. FIG-1bf4046613a0de28	AUTOSAR_AP_SWS_RawDataStream	R24-11R25-11	✓ Beschrieben
Figure 7.1: Raw Data Stream Logical View. FIG-45abfb185a88353b	AUTOSAR_AP_SWS_RawDataStream	R24-11R25-11	✓ Beschrieben
Figure 7.1: Raw Data Stream Logical View. FIG-48ccf2ea646c0afd	AUTOSAR_AP_SWS_RawDataStream	R23-11	✓ Beschrieben
Figure 5.1: Interfaces required by Raw Data Stream from other Functional Clusters FIG-63ce267431c26106	AUTOSAR_AP_SWS_RawDataStream	R24-11R25-11	✓ Beschrieben
Figure 5.1: Interfaces required by Raw Data Stream from other Functional Clusters FIG-7e2361972edb0516	AUTOSAR_AP_SWS_RawDataStream	R23-11	✓ Beschrieben
Figure 7.3: IEEE1722 Raw Data Stream Logical View. FIG-f4642b3d077b728c	AUTOSAR_AP_SWS_RawDataStream	R24-11R25-11	✓ Beschrieben
Figure 7.1: Architecture of the Remote Persistency FIG-4f016278a8e3cd9e	AUTOSAR_AP_SWS_RemotePersistency	R25-11	✓ Beschrieben
Figure 9.1: Service Interface of the Remote Persistency FIG-72ea216c5a2bc87a	AUTOSAR_AP_SWS_RemotePersistency	R25-11	✓ Beschrieben
Figure 5.1: Interfaces required by Remote Persistency from other Functional Clusters FIG-8c86363d871921b2	AUTOSAR_AP_SWS_RemotePersistency	R25-11	✓ Beschrieben
Figure 7.2: Typical usage of Safe Hardware Acceleration within an Adaptive Application FIG-311aa452d619e139	AUTOSAR_AP_SWS_SafeHardwareAcceleration	R25-11	✓ Beschrieben
Figure 5.1: Interfaces Provided by Safe Hardware Acceleration to Other Functional Clusters FIG-dee61da97db79710	AUTOSAR_AP_SWS_SafeHardwareAcceleration	R25-11	✓ Beschrieben
Figure 7.1: High Level Design of Safe Hardware Acceleration in an Adaptive Platform FIG-df162a6aab48ddf0	AUTOSAR_AP_SWS_SafeHardwareAcceleration	R25-11	✓ Beschrieben
Figure 7.1: Functional elements communicating via ADI FIG-0a3ffb8c7f047bcc	AUTOSAR_AP_SWS_SensorInterfaces, AUTOSAR_SWS_SensorInterfaces	R20-11R21-11R22-11R23-11+2	✓ Beschrieben
Figure 7.2: Scope of Standardization FIG-166012027119e23e	AUTOSAR_AP_SWS_SensorInterfaces, AUTOSAR_SWS_SensorInterfaces	R20-11R21-11R22-11R23-11+1	✓ Beschrieben
Figure 5.1: Sensor Interfaces dependencies to other AUTOSAR Adaptive Applications. FIG-4c80b850bf5fc02c	AUTOSAR_AP_SWS_SensorInterfaces	R23-11R24-11R25-11	✓ Beschrieben
Figure 7.2: Scope of Standardization FIG-d9a992144a08da99	AUTOSAR_AP_SWS_SensorInterfaces	R25-11	✓ Beschrieben
Figure 7.29: Overview for the StateMachine ErrorCodes handling FIG-00214fb1a5614426	AUTOSAR_AP_SWS_StateManagement	R25-11	✓ Beschrieben
Figure 7.16: ErrorRecoveryTable FIG-048a6ec2b3fa6174	AUTOSAR_AP_SWS_StateManagement	R23-11	✓ Beschrieben
Figure 7.9: Agent - FunctionGroup relation FIG-058d89432a375797	AUTOSAR_AP_SWS_StateManagement	R24-11	✓ Beschrieben
Figure 7.9: Interactions with StateMachine FIG-09c5f13d830eacb9	AUTOSAR_AP_SWS_StateManagement	R23-11	✓ Beschrieben
Figure 7.32: Requesting update session within StateMachine approach FIG-0ab0391a7629a24b	AUTOSAR_AP_SWS_StateManagement	R24-11R25-11	✓ Beschrieben
Figure 7.12: Error Recovery FIG-0c24ee417b54ec44	AUTOSAR_AP_SWS_StateManagement	R25-11	✓ Beschrieben
Figure 7.4: Virtualized environments FIG-0cb647370e8025cc	AUTOSAR_AP_SWS_StateManagement	R25-11	✓ Beschrieben
Figure 7.30: Overview of update session within StateMachine approach (part 1 of 2) FIG-16579f835524d492	AUTOSAR_AP_SWS_StateManagement	R24-11R25-11	✓ Beschrieben
Figure 7.9: Example for Controller StateMachineStates with MachineFG FIG-16d94ec005ca0a91	AUTOSAR_AP_SWS_StateManagement	R23-11R24-11R25-11	✓ Beschrieben
Figure 7.7: Switching Network State by "Trigger" FIG-1a0132475622b851	AUTOSAR_AP_SWS_StateManagement, AUTOSAR_SWS_StateManagement	R19-03R19-11R20-11R21-11+2	✓ Beschrieben
Figure 7.31: Start-up Sequence to Initial State or ContinueUpdate state FIG-24f70a8a184207bb	AUTOSAR_AP_SWS_StateManagement	R24-11	✓ Beschrieben
Figure 7.4: Interactions with StateMachine FIG-2a96de6c35e509a6	AUTOSAR_AP_SWS_StateManagement	R24-11	✓ Beschrieben
Figure 7.19: Arbitrary order for ActionListItems FIG-38271de85aa27fd2	AUTOSAR_AP_SWS_StateManagement	R23-11	✓ Beschrieben
Figure 7.44: Different types of S2R support in Adaptive Applications FIG-3851babd5d038e7d	AUTOSAR_AP_SWS_StateManagement	R25-11	✓ Beschrieben
Figure 7.2: State Change Sequence – Transition to machine state StateXYZ FIG-3b9d3ffb76b95f80	AUTOSAR_AP_SWS_StateManagement	R24-11R25-11	✓ Beschrieben
Figure 7.15: Example of one NmNetworkHandle influencing multiple StateMachines FIG-49fc46b95cfe0da1	AUTOSAR_AP_SWS_StateManagement	R24-11R25-11	✓ Beschrieben
Figure 7.41: Example for the Controller configuration supporting autonomous wake-up via the LeaveSuspend StateMachine State FIG-4b085ef1d265dde3	AUTOSAR_AP_SWS_StateManagement	R25-11	✓ Beschrieben
Figure 7.4: Non-Synchronized Application State handling FIG-5203d533d69117f5	AUTOSAR_AP_SWS_StateManagement, AUTOSAR_SWS_StateManagement	R19-03R19-11R21-11R22-11+1	✓ Beschrieben
Figure 7.35: Verify and prepare rollback within StateMachine approach - part 2/2 FIG-52d7c70647a20bf4	AUTOSAR_AP_SWS_StateManagement	R24-11R25-11	✓ Beschrieben
Figure 5.1: Interfaces provided by State Management to other Functional Clusters FIG-5394fab9ce388fa5	AUTOSAR_AP_SWS_StateManagement	R23-11	✓ Beschrieben
Figure 5.3: Interfaces required by State Management from Execution Management FIG-53ff797f26ea6bfa	AUTOSAR_AP_SWS_StateManagement	R24-11	✓ Beschrieben
Figure 7.6: SMControlApplication and StateManagement Process started together FIG-571c8f6529a501b2	AUTOSAR_AP_SWS_StateManagement, AUTOSAR_SWS_StateManagement	R22-11R23-11R24-11R25-11	✓ Beschrieben
Figure 7.25: Value of configured StateMachineNotification::CurrentState field FIG-572984a047eba313	AUTOSAR_AP_SWS_StateManagement	R24-11R25-11	✓ Beschrieben
Figure 7.16: Parallel ActionListItem execution and SYNC FIG-5cada4612e926b2e	AUTOSAR_AP_SWS_StateManagement, AUTOSAR_SWS_StateManagement	R22-11R23-11R24-11R25-11	✓ Beschrieben
Figure 7.31: Overview of update session within StateMachine approach (part 2 of 2) FIG-6099f67938efe240	AUTOSAR_AP_SWS_StateManagement	R24-11R25-11	✓ Beschrieben
Figure 7.12: Extended transition request table FIG-61cf71e07dbf73f3	AUTOSAR_AP_SWS_StateManagement	R24-11	✓ Beschrieben
Figure 7.19: Processing ActionListItem StopStateMachine FIG-642e1efbe26763ca	AUTOSAR_AP_SWS_StateManagement	R24-11	✓ Beschrieben
Figure 7.5: Interactions with StateMachine FIG-64b7db6f86f86395	AUTOSAR_AP_SWS_StateManagement	R25-11	✓ Beschrieben
Figure 7.12: TransitionRequestTable FIG-69ca6184356d7977	AUTOSAR_AP_SWS_StateManagement	R23-11	✓ Beschrieben
Figure 7.18: Completeness of controlled Function Groups FIG-6a07cb7c60df0696	AUTOSAR_AP_SWS_StateManagement	R23-11R25-11	✓ Beschrieben
Figure 7.13: StateMachine change FIG-6f60dd7185302f5a	AUTOSAR_AP_SWS_StateManagement	R25-11	✓ Beschrieben
Figure 7.26: ActionList timeout FIG-7069029136275998	AUTOSAR_AP_SWS_StateManagement	R25-11	✓ Beschrieben
Figure 7.34: Verify and prepare rollback within StateMachine approach - part 1/2 FIG-7d9f2c6121f3317e	AUTOSAR_AP_SWS_StateManagement	R24-11R25-11	✓ Beschrieben
Figure 7.17: Arbitrary order for ActionListItems FIG-81070c934aa9d2c7	AUTOSAR_AP_SWS_StateManagement, AUTOSAR_SWS_StateManagement	R22-11R24-11R25-11	✓ Beschrieben
Figure 7.22: Example for an ActionList using ActionListItem Sleep FIG-8a5426d26ce07d91	AUTOSAR_AP_SWS_StateManagement	R23-11R24-11R25-11	✓ Beschrieben
Figure 7.38: Example for the Controller StateMachineStates supporting Suspend-To-RAM. FIG-8e8b72d3bf377830	AUTOSAR_AP_SWS_StateManagement	R25-11	✓ Beschrieben
Figure 7.1: Start-up Sequence – from Startup to initial running state Driving FIG-906bbc8f7a366916	AUTOSAR_AP_SWS_StateManagement	R25-11	✓ Beschrieben
Figure 5.2: Interfaces required by State Management from other Functional Clusters FIG-935179659e745487	AUTOSAR_AP_SWS_StateManagement	R25-11	✓ Beschrieben
Figure 5.2: Interfaces required by State Management from other Functional Clusters FIG-93effc9d7f15f2fc	AUTOSAR_AP_SWS_StateManagement	R23-11	✓ Beschrieben
Figure 7.28: Nested recovery example FIG-979ccefd596b5b9c	AUTOSAR_AP_SWS_StateManagement	R25-11	✓ Beschrieben
Figure 7.25: Example for StateMachineState VerifyUpdate for an Agent FIG-97f6e0476600ef8a	AUTOSAR_AP_SWS_StateManagement	R23-11	✓ Beschrieben
Figure 7.39: Example for entering Suspend-To-RAM mode. FIG-9a871c646c9b5492	AUTOSAR_AP_SWS_StateManagement	R25-11	✓ Beschrieben
Figure 7.3: Switching FunctionGroup State by "Trigger" FIG-9d2b478306ce8ca0	AUTOSAR_AP_SWS_StateManagement	R24-11	✓ Beschrieben
Figure 7.40: Example for leaving Suspend-To-RAM FIG-a11620d5548e7b2e	AUTOSAR_AP_SWS_StateManagement	R25-11	✓ Beschrieben
Figure 7.42: Example for autonomous wake-up due to OS system call FIG-a3564ea91811d55f	AUTOSAR_AP_SWS_StateManagement	R25-11	✓ Beschrieben
Figure 7.36: Reset machine handling within StateMachine approach FIG-a481fd2ca3509290	AUTOSAR_AP_SWS_StateManagement	R24-11R25-11	✓ Beschrieben