Vehicle Data Collection Automation for OTA Update Continuity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing vehicle data management systems require direct access, are costly, and risky due to downtime and version management issues, with limited functionality and increased complexity from growing network demands and regulatory requirements, making it difficult for various entities to implement and interact with vehicle functions.
Innovation Solution
A system with a network of endpoints, including a controller with automation definition, management, and execution circuits, allowing for automated vehicle responses without direct vehicle access, reducing costs and risks by enabling broader access to vehicle functions through automated action plans and data management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If direct vehicle access or OTA software updates are used to update vehicle operational capabilities, then vehicle functionality can be updated, but vehicle downtime increases, reliability decreases, and management expenses increase
Solution Approach 1:
The system performs preliminary actions by preparing update packages offline with complete validation before deployment. The update manager circuits verify update integrity and prepare rollback mechanisms in advance, ensuring that if an update fails, the vehicle can revert to the previous stable state without being stranded.
Solution Approach 2:
The patent introduces an intermediary update management system that acts as a buffer between the update source and the vehicle controller. This intermediary layer handles update validation, staging, and deployment coordination, preventing direct updates that could cause vehicle downtime or reliability issues.
2Adaptability or versatility
If direct vehicle access or OTA updates are used, then vehicle functionality can be updated, but management expenses increase due to maintaining multiple software versions and handling updates
Solution Approach 1:
The update management system implements self-service capabilities where the vehicle's update manager circuits automatically receive, validate, stage, and deploy updates without requiring manual intervention. The system self-manages version control, rollback procedures, and update scheduling, eliminating the need for manufacturers to maintain multiple software versions manually.
Solution Approach 2:
The patent uses copying mechanisms to create staged copies of software updates in a controlled environment before deployment. The update manager circuits maintain copies of previous stable versions and prepared update versions, allowing validation and rollback without requiring the original development environment or multiple physical software repositories.
3Reliability
If full vehicle knowledge and authority are required for updates, then update control is maintained, but accessibility and functionality expansion are limited
Solution Approach 1:
The patent segments vehicle access rights and update authorities into distinct hierarchical levels. Different entities (manufacturers, dealers, service providers, consumers) are assigned specific permission levels that allow them to perform appropriate updates without requiring full vehicle knowledge or root access. This segmentation enables controlled accessibility while maintaining security.
Solution Approach 2:
The update management system implements a universal interface that allows multiple types of entities with different knowledge levels to interact with the vehicle through a common standardized protocol. The system translates high-level update requests from various entities into specific vehicle controller commands, enabling broad accessibility while maintaining proper control and security.
Data Source
AI summary
A system for managing vehicle data collection. The system includes: a vehicle having a network comprising a plurality of end points, and a controller. The controller includes: an automation management circuit structured to provide an automated action plan; an automation execution circuit structured to provide an automation command in response to the automated action plan; and an automation continuity circuit structured to determine whether an automation interruption event has occurred, and to provide an automation continuity command in response to the automation interruption event.