Vehicle Control Module Orchestration for Mixed-Criticality Workloads
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing vehicle control systems face challenges in managing mixed criticality applications, where safety critical and non-safety critical applications interfere with each other, leading to complex integration and validation cycles, long delivery times, and complicated failure recovery.
Innovation Solution
A vehicle control method that defines workloads with descriptors specifying safety levels, recovery mechanisms, and resource usage, allocating resources based on criticality, monitoring and managing access, and implementing containerized orchestration to isolate and prioritize critical applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If safety critical and non-safety critical applications are separated to different operating systems, then interference between applications is avoided, but integration and validation cycles become very long
Solution Approach 1:
The system segments applications into safety critical and non-safety critical workloads, each with dedicated resource pools. Safety critical workloads receive guaranteed resources that cannot be accessed by non-safety critical workloads, while non-safety critical workloads can utilize remaining resources. This segmentation prevents interference while allowing unified management within a single operating system, reducing integration and validation complexity.
Solution Approach 2:
An orchestrator module acts as an intermediary between workloads and system resources. It monitors resource usage, enforces resource policies, and dynamically allocates resources based on workload criticality. This intermediary layer enables unified operating system management while maintaining isolation guarantees, avoiding the need for separate operating systems and their associated integration challenges.
2Reliability
If safety critical and non-safety critical applications are separated to different operating systems, then application interference is prevented, but software delivery time becomes very long
Solution Approach 1:
A single operating system is designed to universally manage both safety critical and non-safety critical workloads through containerized execution. The orchestrator provides multi-functional resource management capabilities, handling allocation, monitoring, and policy enforcement for diverse workload types. This universal approach eliminates the need for separate operating systems while maintaining interference prevention, significantly accelerating software delivery.
Solution Approach 2:
The system changes the parameter of system architecture from multiple operating systems to a single operating system with virtualized resource management. By adjusting resource allocation parameters dynamically based on workload criticality and using containerization to isolate execution contexts, the system maintains reliability guarantees while enabling faster integration and deployment cycles.
3Productivity
If system resources are shared among multiple workloads, then resource utilization is optimized, but resource conflicts arise between critical and non-critical applications
Solution Approach 1:
Different resource pools are assigned different quality levels based on workload criticality. Safety critical workloads receive high-quality guaranteed resources with strict access controls, while non-safety critical workloads access best-effort resources from remaining pools. This local quality differentiation enables efficient resource utilization while maintaining reliability, as each workload type receives appropriate resource guarantees without conflict.
Solution Approach 2:
The orchestrator dynamically adjusts resource allocation based on real-time system state and workload requirements. When safety critical workloads require resources, the system dynamically prioritizes their access and restricts non-critical workload usage. This dynamic resource management optimizes overall utilization while preventing conflicts that could compromise critical application reliability.
4Device complexity
If a single operating system manages all workloads, then system complexity is reduced, but failure recovery becomes very complicated
Solution Approach 1:
Workloads are segmented into isolated containers with defined resource boundaries and recovery policies. Each containerized workload can be independently managed, monitored, and recovered without affecting other workloads. This segmentation simplifies failure recovery within a single operating system, as the orchestrator can restart or isolate failed containers without requiring complex system-wide recovery procedures.
Solution Approach 2:
The orchestrator serves as an intermediary that manages failure recovery for all workloads. It monitors workload health, detects failures, and executes recovery actions based on predefined policies. This centralized intermediary simplifies recovery complexity by providing a unified recovery mechanism that handles diverse workload failures consistently, eliminating the need for complex distributed recovery protocols across multiple operating systems.
Data Source
AI summary
A vehicle control method includes defining a set of multiple workloads, each workload including a workload descriptor and at least one containerized image configured to execute at least one vehicle control process, the workload descriptor defining a safety level of the workload, one or more vehicle system resources used by the least one containerized image of the workload, and a vehicle system location for executing the containerized images. The method includes allocating vehicle system resources to each workload according to the workload descriptors, wherein the vehicle system resources include at least one of a central processor utilization, a graphics processor utilization, a memory size, an artificial intelligence accelerator, or a video codec, executing the vehicle control processes of the containerized images of the multiple workloads, and in response to a vehicle system resource conflict, assigning higher priority resource access to workloads having a critical safety level.