Vehicle Longitudinal Motion Profiles for Multi-Requestor Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current vehicle motion request systems are inefficient, complex, and costly due to duplicative conversions from acceleration to torque, leading to inconsistent performance and high engineering resource consumption, especially when handling multiple requestors like cruise control and hands-free driving systems.
Innovation Solution
A vehicle longitudinal motion request architecture that generates velocity, acceleration, and jerk profiles based on speed requests, eliminating duplicative conversions by using a supervisory control layer and a profile generation module that minimizes RAM, ROM, and throughput consumption, while ensuring consistent performance across different request types.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If duplicative conversions from acceleration to torque are performed for each requestor, then each requestor can independently control vehicle motion, but system complexity and engineering resource consumption increase significantly
Solution Approach 1:
The patent merges multiple independent conversion paths into a single centralized conversion process. The arbitration module consolidates velocity and acceleration requests from multiple requestors, and a single profile generation module converts the arbitrated acceleration request to torque, eliminating duplicative conversions while maintaining requestor independence through the arbitration mechanism.
Solution Approach 2:
The arbitration module serves as a universal interface that handles requests from multiple different requestors (cruise control, hands-free driving, driver input) and translates them into a standardized acceleration request format. This universal module eliminates the need for each requestor to have its own conversion logic.
2Measurement precision
If each requestor performs independent acceleration to torque conversion, then requestor-specific control precision is maintained, but hardware resource consumption (RAM, ROM, throughput) increases
Solution Approach 1:
The patent combines multiple conversion operations into a single execution. By merging the conversion logic into one profile generation module that processes arbitrated requests, the system maintains the precision needed for control while reducing redundant computational operations that consume hardware resources.
Solution Approach 2:
Instead of each requestor maintaining its own conversion logic (copying the same functionality multiple times), the system uses a single conversion module that serves all requestors. This eliminates redundant code and data storage requirements in RAM and ROM.
3Stability of the object's composition
If a single global vehicle model is used for all requestors, then consistency across different request types is achieved, but adaptability to requestor-specific requirements decreases
Solution Approach 1:
The patent segments the control architecture into distinct functional layers: requestor-specific modules that understand individual requestor requirements, an arbitration module that standardizes requests, and a profile generation module that executes the conversion. This segmentation allows each layer to specialize, maintaining both consistency in the conversion process and adaptability to different requestor needs.
Solution Approach 2:
The arbitration module acts as an intermediary between diverse requestors and the single profile generation module. It translates requestor-specific requirements into a standardized acceleration request format, allowing the global vehicle model to maintain consistency while the intermediary preserves adaptability to different requestor characteristics.
Data Source
AI summary
A motion system for a vehicle includes: a profile generation module configured to obtain a current reference velocity, a current reference acceleration, a target velocity and a target acceleration for the vehicle, and based on the current reference velocity, current reference acceleration, target velocity and target acceleration, to generate a speed profile including determining a first nonlinear section and second nonlinear section of the speed profile, where the first nonlinear section is associated with acceleration, where the second nonlinear section is associated with deceleration, and where the speed profile includes acceleration of the vehicle from the current reference velocity to the target velocity; and a vehicle motion control module configured, based on the speed profile, to control one or more actuators of the vehicle.