Vehicle Drive History Path Attribute Communication Protocol

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for communicating drive history path attributes to controllers in vehicles are inefficient, as they rely on one-to-one communication protocols and different formats, making it difficult to share detailed information about previously traveled routes effectively.

Innovation Solution

Implementing a common protocol for broadcasting drive history path attributes over a controller bus, such as a CAN bus, allowing multiple controllers to access and process this information in a standardized format, and using a path projection component to determine and project future driving paths based on both electronic map data and drive history, enabling efficient data sharing and utilization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If one-to-one communication protocols are used to communicate drive history path attributes to controllers, then each controller can receive customized information, but the system complexity and development time increase significantly

Engineering Contradiction:
Improvecustomized information deliveryVSAvoidcommunication protocol complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal broadcast communication protocol that allows a single communication mechanism to serve multiple controllers simultaneously. The drive history path attributes are transmitted once to the bus and automatically received by all subscribed controllers, eliminating the need for separate one-to-one communication channels while maintaining the ability to deliver customized information to each controller based on their specific needs

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If different formats are used for communicating drive history path attributes to different controllers, then each controller receives optimized data, but the resource usage and processing overhead increase

Engineering Contradiction:
Improvecontroller-specific data optimizationVSAvoidprocessing overhead
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent employs a copy-based approach where the drive history path attributes are transmitted once in a standardized format to the communication bus, and each controller creates its own customized copy or interpretation of the data based on its specific requirements. This eliminates the need for multiple format conversions and reduces processing overhead while still allowing each controller to receive optimized data for its particular function

Inventive Principle:
Principle #26Copying

3Reliability

If detailed drive history information is shared across multiple controllers, then driver safety and navigation improve, but the communication bandwidth and processing resources are consumed

Engineering Contradiction:
Improvedriver safetyVSAvoidcommunication resource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent merges the communication resources by implementing a shared broadcast bus where all controllers access drive history path attributes through a single communication channel rather than requiring separate dedicated channels for each controller. This consolidation reduces overall communication bandwidth consumption and processing resources while still providing detailed drive history information to all controllers that need it for safety and navigation functions

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS10228259B2Systems, methods, and devices for communicating drive history path attributes
Publication Date: 2019.03.12 FORD GLOBAL TECH LLC
  • US10228259B2 patent drawing
  • US10228259B2 patent drawing
  • US10228259B2 patent drawing

AI summary

A method for providing path attributes to controllers in a vehicle includes receiving drive history data for a future driving path of the vehicle, wherein the drive history data comprises a first data format. The method includes generating a message for a controller comprising path attributes from the drive history data according to a subscription list, wherein the message comprises a controller data format based on an indication by the subscription list. The method further includes providing one or more data packets comprising the message to the controller.