Vehicle Path Projection via Common Protocol
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems for communicating drive history path attributes in vehicles are inefficient, as they rely on one-to-one communication protocols, requiring separate messages in different formats for each controller, which hinders the effective dissemination of detailed drive history information for enhanced driver safety and automated driving systems.
Innovation Solution
A method and system that utilize a common protocol to broadcast drive history path attributes over a controller area network (CAN) bus, allowing multiple controllers to access and process this information efficiently, with the path projection component determining and publishing attributes based on both electronic map data and drive history, enabling adaptive cruise control, energy management, and other driver assistance systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If one-to-one communication protocols are used to communicate drive history path attributes to each controller, then each controller can receive the information, but the communication efficiency decreases and resource usage increases due to requiring separate messages for each controller
Solution Approach 1:
The system segments the communication task by having each controller subscribe to specific path attribute types it needs, rather than broadcasting all attributes to all controllers. This allows selective information delivery where the path projection component publishes different subsets of path attributes to different controllers based on their specific requirements, improving communication efficiency while ensuring each controller receives necessary information.
Solution Approach 2:
The controller bus is designed with universal communication capabilities that allow a single publication of path attributes to be accessed by multiple controllers simultaneously. The system creates a multi-functional communication infrastructure where the same bus and publishing mechanism serves multiple controllers, eliminating the need for separate one-to-one communication channels while ensuring reliable information delivery to all subscribed controllers.
2Adaptability or versatility
If separate messages in different formats are sent to each controller, then each controller receives customized information, but the device complexity and development time increase
Solution Approach 1:
Each controller is configured with local quality requirements by subscribing to specific path attribute types relevant to its function. The path projection component responds by publishing customized subsets of path attributes to each controller based on their individual subscriptions. This approach maintains controller-specific information delivery while simplifying the overall system architecture through a standardized publishing mechanism that automatically adapts to each controller's needs.
Solution Approach 2:
The system implements a feedback mechanism where controllers express their information needs through subscriptions, and the path projection component uses this feedback to determine what path attributes to publish to each controller. This feedback loop enables automatic adaptation of information delivery without requiring complex pre-configured message formats for each controller, reducing development complexity while maintaining versatility.
3Measurement precision
If detailed drive history information is stored and recalled, then driver safety and navigation accuracy improve, but the data processing requirements and energy consumption increase
Solution Approach 1:
The system extracts only the specific path attribute types needed by each controller from the complete drive history data set. Rather than processing and transmitting all available detailed information, the path projection component selectively extracts and publishes only the relevant subsets of path attributes that each controller requires for its specific function. This extraction approach maintains measurement precision for necessary attributes while significantly reducing overall data processing requirements and energy consumption.
Solution Approach 2:
Each controller receives a partial set of path attributes tailored to its specific needs rather than the complete data set. This partial action approach ensures that each controller processes only the minimum necessary information to perform its function accurately, avoiding the excessive processing of irrelevant data. The system applies this principle by having controllers subscribe only to the path attribute types they require, thereby reducing cumulative energy consumption across all controllers while maintaining sufficient precision for each specific application.
Data Source
AI summary
A method for providing path attributes to controllers in a vehicle includes managing a subscription list that indicates what type of messages or data to which each of a plurality of controllers of a vehicle are subscribed. The method includes determining a future driving path for the vehicle and determining forward path attributes for the future driving path based on a drive history. The method includes selecting one or more controllers from the plurality of controllers to receive each of the forward path attributes based on the subscription list. The method includes providing each of the forward path attributes to the selected one or more controllers. The forward path attributes are provided using a common protocol for each of the plurality of controllers and two or more of the plurality of controllers receive a specific path attribute via a single message.