Vehicle Data Collection Automation for Secure Remote Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing vehicle data management systems require direct vehicle access for updates, leading to downtime, risk of operational failure, and high management costs, with limited functionality and increased complexity due to multiple network configurations and regulatory requirements, making it costly and risky to implement new vehicle functionalities.
Innovation Solution
A system with a network of end points, including a controller with automation definition, management, and execution circuits, allowing for automated vehicle responses without direct vehicle access, enabling broader entity access to implement features and manage data securely, reducing costs and risks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If direct vehicle access is required for updates and functionality changes, then vehicle control and security are maintained, but downtime, operational failure risk, and management costs increase
Solution Approach 1:
The patent introduces an intermediary system that acts as a mediator between external entities and the vehicle controller. This intermediary handles update delivery and execution coordination, allowing updates to be applied without requiring direct physical access to the vehicle. The intermediary manages the update process remotely, reducing downtime while maintaining security through controlled access mechanisms.
Solution Approach 2:
The system performs preliminary actions by preparing and validating update packages before they are applied to the vehicle. The intermediary system pre-processes update content, verifies integrity, and stages updates for execution during optimal times (e.g., when the vehicle is parked), thereby minimizing operational disruption and downtime.
2Reliability
If full vehicle knowledge and authority are required for updates, then security and control are maintained, but functionality is limited and costs increase
Solution Approach 1:
The patent implements local quality by providing different levels of access and authority to different entities based on their specific needs and permissions. The system allows manufacturers, dealers, and service providers to access specific vehicle functions and data relevant to their roles without requiring full vehicle knowledge or root access. This granular permission structure enhances adaptability while maintaining security.
Solution Approach 2:
The intermediary system serves multiple functions: it manages updates, coordinates data collection, handles authentication, and provides a universal interface for various entities (manufacturers, dealers, service providers) to interact with the vehicle. This multi-functional approach enables broader entity access and improved adaptability without compromising security.
3Adaptability or versatility
If multiple network configurations and regulatory requirements are accommodated, then system compatibility is improved, but complexity and management costs increase
Solution Approach 1:
The intermediary system acts as a standardized interface layer between diverse network configurations and the vehicle controller. It handles protocol translation, data formatting, and communication coordination, allowing the system to accommodate multiple network types (CAN, LIN, Ethernet) and regulatory requirements without increasing the complexity of the core vehicle control architecture.
4Ease of operation
If OTA software updates are used, then direct vehicle access is eliminated, but risk of update failure and operational disruption increases
Solution Approach 1:
The system implements beforehand cushioning by creating backup mechanisms and validation checks before executing OTA updates. The intermediary system verifies update integrity, maintains backup software versions, and prepares rollback procedures in advance. If an update fails or causes issues, the system can revert to the previous stable version, thereby cushioning against operational disruption and maintaining reliability.
Data Source
AI summary
A system for managing vehicle data collection. The system includes a vehicle and a controller. The vehicle has a network that includes a plurality of end points. The controller includes: an automation definition circuit structured to interpret an automation description; an automation management circuit structured to provide an automated action plan in response to the automation description, and to store the automated action plan as a data file on a data storage communicatively coupled to the controller; and an automation execution circuit structured to provide an automation command in response to the automated action plan. An end point of the plurality of end points is responsive to the automation command to implement an automated vehicle response.