SoC ECU Safe Designation for Dynamic Power Budget Allocation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current software architectures for system-on-chip (SoC) technology do not support the distinction between safety critical and non-safety critical electronic control units (ECUs) under flex operation, nor do they facilitate re-classification of ECUs at drive mode or SoC operation stage boundaries, leading to inefficiencies in power management.
Innovation Solution
A software architecture that dynamically distinguishes between safety critical and non-safety critical ECUs on an SoC, allowing for flexible power and limit management by identifying and configuring each ECU with respective safe designations based on OEM policies and workload, and reallocating ECUs at drive mode or operation stage boundaries.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a static configuration of either all safety critical ECUs or all non-safety critical ECUs is supported, then safety management is simplified, but power management efficiency deteriorates
Solution Approach 1:
The patent implements dynamic classification of ECUs that can change between safety critical and non-safety critical designations based on operational context. The controller dynamically updates safe designations at drive mode boundaries and operation stage transitions, allowing the system to adapt power management strategies in real-time while maintaining safety requirements. This resolves the contradiction by enabling both simplified safety management through structured classification and improved power efficiency through context-aware dynamic reconfiguration.
Solution Approach 2:
The system changes the safe designation parameter of ECUs based on drive mode and operation stage. By modifying the safety classification parameter dynamically, the controller can apply different power management configurations to the same ECU under different operating conditions, thereby improving power management efficiency without compromising safety management simplicity.
2Adaptability or versatility
If flex operation supporting both safety critical and non-safety critical ECUs is implemented, then power management flexibility is improved, but software architecture complexity worsens
Solution Approach 1:
The patent segments the software architecture into distinct modules: a classifier that determines safe designations, a configuration manager that loads appropriate power and limit features, and a controller that coordinates operations. This segmentation allows the complex flex operation to be managed through organized, modular components, reducing perceived software architecture complexity while maintaining power management flexibility.
Solution Approach 2:
The controller acts as an intermediary between the classifier and the ECU configuration system. It receives safe designation classifications, determines appropriate power and limit feature configurations, and loads them into ECUs. This intermediary layer simplifies the software architecture by centralizing the decision-making logic and providing a clear interface between classification and configuration functions.
3Stability of the object's composition
If ECU re-classification at drive mode boundaries is not supported, then system stability is improved, but power efficiency worsens
Solution Approach 1:
The system performs preliminary classification of ECUs at drive mode boundaries before transitioning to the new mode. The controller proactively updates safe designations and loads appropriate power and limit feature configurations in advance, ensuring system stability is maintained through controlled transitions while enabling power efficiency improvements by applying the correct configuration for the upcoming operational state.
Solution Approach 2:
The system monitors drive mode transitions and operation stage changes, providing feedback to the controller which then adjusts ECU safe designations and configurations accordingly. This feedback mechanism ensures system stability by responding to actual operational conditions while reducing leakage power through context-appropriate power management configurations.
4Loss of energy
If dynamic safe designation and configuration loading is implemented, then power efficiency is improved, but processing time worsens
Solution Approach 1:
The classifier determines safe designations and the configuration manager prepares appropriate power and limit feature configurations in advance, before they are needed for ECU operation. This preliminary action reduces processing time during actual ECU configuration by having configurations ready to load, while still enabling dynamic power efficiency optimizations based on operational context.
Data Source
AI summary
Aspects relate to mechanisms for supporting the identification of a respective safe designation for each of a plurality of electronic control units (ECUs) on a system-on-chip (SoC) of a vehicle. Based on the respective safe designations, a respective configuration of at least one of a power feature or a limit feature can be loaded into each of the ECUs. Safe designations can include safety critical and non-safety critical designations based on the corresponding original equipment manufacturer configurations for each of the ECUs. The safe designations and corresponding configurations can further be modified based on at least one of a vehicle drive mode of the vehicle or an SoC operation stage of the SoC.