Vehicle ADAS Arbitration for Stopped-State Holding Modes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing vehicle systems implementing advanced driver assistance systems (ADAS) face complexity in designing electronic control units (ECUs) and interfaces when managing different modes of stopped state holding, as each ECU must output requests for stopped state holding and mode control, leading to potential complications.
Innovation Solution
A manager system installed in vehicles, comprising processors that receive kinematic plans and identification information from ADAS applications, arbitrates these requests to determine the appropriate mode of stopped state holding, distributing motion requests to actuator systems, and stores information associating application IDs with stopped state holding modes, thereby simplifying ECU design and interface management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If each ECU outputs requests relating to stopped state holding and mode control for ADAS applications, then the vehicle can implement multiple ADAS functions with different stopped state holding modes, but the design of the ECU and its interfaces becomes complicated
Solution Approach 1:
The patent extracts the stopped state holding control logic from individual ECUs and concentrates it in a central manager. Each ECU only needs to output simple motion requests without embedded mode control logic, while the manager handles the complex arbitration and mode determination based on application identification information.
Solution Approach 2:
The manager acts as an intermediary between ECUs and actuators. It receives motion requests from multiple ECUs, determines the appropriate stopped state holding mode based on application identification information, and outputs unified control signals to actuators, thereby simplifying ECU design while maintaining adaptability.
2Reliability
If each ECU outputs detailed requests for stopped state holding control, then precise control can be achieved, but the communication load and functional interference among ADAS applications increase
Solution Approach 1:
The patent extracts detailed control logic from ECU communications and relocates it to the manager. ECUs communicate only essential motion requests, while the manager performs complex arbitration and mode determination, thereby reducing communication load while maintaining control precision through centralized intelligent processing.
3Adaptability or versatility
If the system supports multiple stopped state holding modes for different ADAS applications, then the system becomes more versatile, but the interface design becomes more complicated
Solution Approach 1:
The manager serves as a universal interface that handles multiple ADAS applications and their different stopped state holding mode requirements through a single standardized arbitration mechanism. This multi-functional approach allows the system to support diverse applications without complicating individual ECU interfaces.
Data Source
AI summary
A manager installed in a vehicle includes one or more processors. The one or more processors are configured to receive, from a plurality of advanced driver assistance system (ADAS) applications, a plurality of kinematic plans and identification information of the ADAS applications. The one or more processors are configured to arbitrate the kinematic plans, and calculate a motion request based on arbitration results. The one or more processors are configured to distribute the motion request to at least one actuator system. The one or more processors are configured to determine, when the kinematic plans include a request relating to stopped state holding of the vehicle, a mode of stopped state holding of the vehicle in accordance with the identification information of the ADAS applications.