Vehicle Container Updates With User Data Preservation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional processor-based systems require service interruption for application updates in autonomous vehicles, limiting updates to specific processes and causing issues with real-time updates for web-based services without screen switching.
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 containers during active use, enabling smooth transitions between old and new containers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional processor-based systems are used to update applications, then the system can maintain existing configurations, but service interruption is required and real-time updates are limited
Solution Approach 1:
The system segments the application into a container image portion and a user data commit portion, allowing independent handling of each. The container image can be updated separately from user data, enabling seamless updates without service interruption by loading the new container image while preserving existing user data commits.
Solution Approach 2:
The system performs preliminary actions by pre-loading container images into a local registry before they are needed. When an update is required, the new container image is already available locally, allowing immediate activation without service interruption. The user data commit is also prepared in advance to be combined with the new container image.
2Adaptability or versatility
If container updates are performed by replacing the entire container, then updates can be implemented, but user data is lost and service interruption occurs
Solution Approach 1:
The system extracts user data from the container as a separate commit object that can be independently preserved. When updating, only the container image is replaced while the user data commit remains intact and is combined with the new image, preventing data loss and enabling seamless updates.
Solution Approach 2:
The system merges the user data commit with the new container image to create an updated container. This combining process ensures that user data is preserved and integrated with the updated application code, allowing the system to gain update capability without sacrificing user data.
3Reliability
If web-based services are updated via back end updates, then service continuity is maintained, but real-time functionality is lost when user screens do not switch
Solution Approach 1:
The system implements a feedback mechanism through the container management table that tracks container image versions and user data commits. This allows the system to detect when updates are available and automatically activate new container images, ensuring both service continuity and real-time functionality by providing immediate feedback when updates are ready to be applied.
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.