Vehicle Motion Manager for ADAS Stopped-State Hold Arbitration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing vehicle management systems face complexity in designing electronic control units (ECUs) and interfaces when multiple advanced driver assistance system (ADAS) applications require different modes of stopped state holding.
Innovation Solution
A manager installed in a vehicle that receives kinematic plans and identification information from multiple ADAS applications, arbitrates these plans, and determines the appropriate mode of stopped state holding based on the application identification, without complicating ECU design or interfaces.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If each ECU outputs requests relating to stopped state holding and the mode thereof, then the vehicle can achieve multiple stopped state holding modes for different ADAS applications, but the design of the ECU and the interface will become complicated
Solution Approach 1:
The patent extracts the stopped state holding mode determination function from individual ECUs and concentrates it in the manager. Each ECU only outputs requests relating to stopped state holding without specifying modes, while the manager receives these requests, determines the appropriate holding modes based on application identification information, and outputs the complete control signals. This extraction resolves the contradiction by maintaining adaptability through centralized mode management while simplifying individual ECU design and interfaces.
Solution Approach 2:
The manager acts as an intermediary between the ECUs and the stopped state holding control system. It receives requests from multiple ECUs, uses application identification information to determine which stopped state holding mode to activate, and then outputs the appropriate control signals. This intermediary role allows the system to support multiple holding modes without requiring each ECU to be designed for all possible modes, thus resolving the complexity issue while maintaining versatility.
2Adaptability or versatility
If the manager determines stopped state holding mode based on application identification information, then the system can realize application-specific stopped state holding modes, but additional information processing is required
Solution Approach 1:
The system performs preliminary action by pre-storing correspondence between application identification information and stopped state holding modes in a storage device. When a request is received, the manager simply retrieves the appropriate mode from this pre-established mapping rather than performing complex real-time analysis. This preliminary preparation resolves the contradiction by enabling application-specific mode determination while minimizing the processing complexity during operation.
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.