Cross-Domain Control Synchronization for Deterministic ADAS Processing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Modern advanced driver assistance systems (ADAS) and centralized vehicle computer architectures require highly integrated single-chip systems with real-time and application processing domains to operate efficiently, but existing systems face challenges in synchronizing deterministic behavior between these domains, especially due to differences in programming paradigms and safety requirements.
Innovation Solution
A method that distributes applications across both real-time and application domains, using a basic synchronization event to achieve deterministic synchronization between them, allowing each domain to retain its inherent properties while enabling communication and event determinism, thereby supporting flexible and high-performance applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If applications are distributed across real-time and application domains, then processing performance and flexibility are improved, but synchronization complexity between domains increases
Solution Approach 1:
An event synchronization mechanism is introduced as an intermediary between the real-time domain and application domain. This mechanism receives events from both domains and establishes deterministic synchronization relationships, thereby mediating the interaction between the two domains without requiring complex direct synchronization logic in each domain.
Solution Approach 2:
The system is segmented into distinct real-time domain and application domain components, each handling specific processing tasks. The real-time domain handles safety-critical deterministic processing while the application domain handles flexible event-driven processing, with the event synchronization mechanism coordinating between these segmented components.
2Adaptability or versatility
If POSIX-based operating systems are used in the application domain, then system flexibility and functionality are improved, but deterministic execution behavior deteriorates
Solution Approach 1:
Different quality characteristics are applied to different domains: the real-time domain maintains strict deterministic execution behavior for safety-critical tasks, while the application domain uses POSIX-based operating systems for flexible event-driven processing. The event synchronization mechanism ensures that deterministic requirements are met at the synchronization points while allowing flexibility within the application domain.
3Reliability
If real-time domain uses cyclical task scheduling, then deterministic execution is improved, but system flexibility deteriorates
Solution Approach 1:
The system merges two different execution paradigms: cyclical task scheduling from the real-time domain and event-based scheduling from the application domain. The event synchronization mechanism combines these approaches by using cyclical synchronization events to coordinate between the deterministic real-time tasks and the flexible application events, achieving both determinism and flexibility in the integrated system.
Data Source
AI summary
A method for operating a control device, which has at least one arithmetic logic unit in which at least one real-time domain and at least one application domain are provided. An application is distributed over the at least one real-time domain and the at least one application domain. A basic synchronization event is generated in the at least one real-time domain and is transmitted to the at least one application domain such that synchronization is achieved between the at least one real-time domain and the at least one application domain