Vehicle Container Updates With User Data Registry Continuity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional processor-based systems require service interruption for updating applications in autonomous vehicles, limiting real-time updates and seamless user experience, especially when no screen switching occurs.
Innovation Solution
A method for updating containers in a container-based vehicle system that allows seamless updates by storing user data in a user data registry and using a container management table to adjust and synchronize interlocked containers, enabling continuous operation during updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional processor-based systems are used to update applications, then the system can maintain stability with established update procedures, but service interruption is required and real-time updates are limited
Solution Approach 1:
The system segments the application update process into separate container instances. Multiple container instances can run simultaneously, allowing one container to be updated while others continue serving requests. This segmentation enables updates without complete service interruption, resolving the contradiction between system stability and service continuity.
Solution Approach 2:
The system performs preliminary actions by preparing updated container images in advance and storing them in a registry. Before switching containers, the updated version is fully prepared and validated. This preliminary preparation allows seamless transitions without service interruption, addressing the time loss issue while maintaining reliability.
2Ease of manufacture
If the system switches between user screens to reflect updates, then the GUI can be updated in real-time, but seamless updates are not achieved when no screen switching occurs
Solution Approach 1:
The system introduces a container management table as an intermediary mechanism that decouples the update process from the user interface. The management table tracks container states and coordinates transitions without requiring screen switches. This intermediary enables seamless updates by managing container lifecycles independently of UI changes, resolving the contradiction between update implementation ease and seamless experience.
3Adaptability or versatility
If user data is stored within the executing container, then the container is self-contained, but user data cannot be seamlessly transferred during container updates
Solution Approach 1:
The system extracts user data from the executing container and stores it in an external user data registry. This separation allows the container to remain portable and self-contained for execution, while user data persists independently in the registry. During container updates, user data is automatically retrieved from the registry, ensuring data continuity without compromising container portability.
Solution Approach 2:
The system moves user data management to another dimension by implementing a separate user data registry layer. Instead of storing data within the container's file system, user data is managed in a dedicated external registry that containers access via standardized interfaces. This dimensional separation enables seamless data transfer during updates while maintaining container versatility.
Data Source
AI summary
A method for updating a container in a container-based vehicle system includes: executing an application included in the container, the application configured to access at least one item included in the container to operate a service related to a vehicle, receiving, from a server, a container image of an update target based on determining an update of the container being needed, the container image including a set of items, storing the received container image of the update target in a system registry, generating a new container by combining a user data item that is generated in the container and the stored container image of the update target, and updating the container by using a container management table on the new container while executing the application. The application reflects the updated container based on items included in the updated container.