Virtual AUTOSAR ECU Partitions for Multi-Core Resource Sharing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The AUTOSAR standard fails to leverage the benefits of parallel execution on multiple electronic control unit (ECU) cores, leading to complexity in memory management, communication, and testing due to the need for multiple operating systems and shared resources, especially when implementing high parallelism in modern vehicles with numerous ECUs.
Innovation Solution
An electronic control unit (ECU) is designed with multiple partitions, where one partition runs the AUTOSAR basic software services, and others run software components, with a partition interface coupling them to share resources efficiently, reducing the need for multiple AUTOSAR architecture platform instances and simplifying memory management and communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Power
If multiple operating systems are run in parallel on multiple cores to enable parallel execution, then computational power and software function capabilities are enhanced, but memory consumption and system complexity increase significantly
Solution Approach 1:
The patent merges multiple AUTOSAR architecture platform instances into a single shared instance that serves multiple cores. Instead of each core having its own independent AUTOSAR stack, the basic software services are consolidated into one instance that can be accessed by multiple cores, thereby reducing memory consumption and system complexity while maintaining parallel execution capabilities.
Solution Approach 2:
The single AUTOSAR architecture platform instance is designed to be universal, serving multiple cores simultaneously. The basic software services are made multi-functional, allowing them to be shared and accessed by different cores for different software components, eliminating the need for duplicate instances and reducing overall system complexity.
2Productivity
If multiple independent AUTOSAR architecture platform instances are created for each core, then parallel execution is enabled, but memory overhead and resource management complexity increase
Solution Approach 1:
The patent combines multiple AUTOSAR architecture platform instances into a single shared instance. The basic software services are merged so that instead of each core having its own copy of the AUTOSAR stack, they all share a common instance, significantly reducing memory consumption while enabling parallel execution through the partition interface mechanism.
3Adaptability or versatility
If the Inter OS-Application Communicator is used for communication across cores, then parallel communication is enabled, but scheduling complexity and time-critical transmission handling become challenging
Solution Approach 1:
The patent introduces a partition interface as an intermediary mechanism between cores running different AUTOSAR instances. This partition interface acts as a mediator that simplifies communication by providing a standardized interface for time-critical data transmissions, reducing the scheduling complexity that would otherwise be required when using the Inter OS-Application Communicator directly.
4Adaptability or versatility
If virtualization is used to consolidate multiple AUTOSAR ECU configurations, then hardware platform utilization is improved, but the hypervisor must abstract the hardware platform and run multiple operating systems in parallel increasing overhead
Solution Approach 1:
The patent merges multiple AUTOSAR architecture platform instances into a single shared instance that can be accessed by multiple cores, eliminating the need for a hypervisor to manage multiple independent operating systems. This approach consolidates the basic software services into one instance, reducing ROM and RAM overhead while maintaining the ability to run multiple software components in parallel.
Data Source
AI summary
An electronic control unit includes a plurality of cores. The electronic control unit hosts, by virtualization, a plurality of partitions including a first and a second partition. Each of the partitions is assigned to at least one of the cores. The first partition is implemented to run, on its at least one core, an AUTOSAR architecture platform instance providing AUTOSAR basic software services. The second partition is implemented to run, on its at least one core, AUTOSAR software components. A partition interface couples the first and second partitions such that the AUTOSAR software components are run as part of said AUTOSAR architecture platform instance implemented in the first partition.