Centralized Vehicle Device Updates via OTA Coordination
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing vehicle systems face challenges in managing device updates due to the increasing complexity and fragmentation of software components, lack of centralized management, inconsistent update processes, and difficulties in coordinating updates across multiple users and devices, particularly with temporary updates and compatibility issues.
Innovation Solution
A centralized device management system that utilizes Over-the-Air (OTA) communication to efficiently manage updates, providing standardized processes, and coordinating updates across devices, including temporary and non-temporary updates, while ensuring compatibility and user coordination.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual individual device updates are performed, then each device can be updated, but the process becomes time-consuming and error-prone especially when multiple devices require simultaneous updates
Solution Approach 1:
The patent merges multiple individual device update operations into a single centralized update process. The server manages updates for multiple devices simultaneously by coordinating update messages and tracking update states across all devices, transforming numerous separate manual operations into one unified automated process that reduces both time and error risk.
Solution Approach 2:
The system enables self-service updates where devices automatically receive and apply updates without manual intervention. The server pushes update messages to devices, and devices autonomously execute the update process, eliminating the need for technicians to physically visit each device and perform manual updates.
2Adaptability or versatility
If each device has its own unique update mechanism, then device-specific requirements are met, but fragmentation leads to inconsistencies and compatibility issues across different devices
Solution Approach 1:
The patent implements a universal update management system where a single server and standardized message protocol can manage updates across diverse device types. The server handles multiple device categories (ECUs, infotainment systems, sensors) through a unified interface, while devices receive updates in a standardized format that ensures compatibility across the entire vehicle system.
Solution Approach 2:
The server acts as an intermediary between update sources and various devices. It standardizes update messages into a common format that all devices can understand, translating between different device requirements and a universal update protocol, thereby ensuring consistency and compatibility across the heterogeneous device ecosystem.
3Adaptability or versatility
If temporary updates are made on the root software file, then specific operational requirements are met, but the system image drifts from known states making restoration difficult and time-consuming
Solution Approach 1:
The system prepares restoration capabilities in advance by maintaining version information and update history. Before applying temporary updates that could cause drift, the system records the original state, enabling quick restoration if needed. This pre-prepared cushioning mechanism ensures that temporary updates can be reversed without time-consuming manual restoration processes.
Solution Approach 2:
The server implements feedback mechanisms by tracking update states and maintaining version information for all devices. When temporary updates are applied, the system monitors their impact and maintains records that enable restoration to known good states. This feedback loop ensures that temporary updates do not permanently drift the system from its baseline configuration.
Data Source
AI summary
Provided are a method, a system and a device for managing one or more updates for one or more devices in a vehicle system. According to embodiments, the method may be implemented by at least one processor of a system and may include: obtaining information associated with the update; generating a message including information of the update; and configuring deployment of the update, wherein the update comprises one of: a temporary update and a non-temporary update.