Vehicle Container Updates With User Data Registry Switching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing container-based vehicle systems face challenges in seamless updates while maintaining user data integrity, requiring service interruption and lacking real-time updates during screen transitions.
Innovation Solution
A method for updating containers in a container-based vehicle system that involves storing user data in a user data registry, generating a new container by combining user data commits with update target images, and using a container management table to facilitate seamless transitions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional processor-based systems are used to update applications, then the system structure is simple, but service interruption occurs during updates and real-time updates are not possible
Solution Approach 1:
The system segments the application into a container image and user data, storing them in separate registries. This allows the container image to be updated independently while preserving user data, enabling seamless updates without service interruption.
Solution Approach 2:
A container management table acts as an intermediary between the container image registry and user data registry, coordinating the update process by mapping container names to their respective storage locations and managing the synchronization between old and new containers.
2Reliability
If user data is stored within the container, then data access is simple, but data loss occurs during container updates
Solution Approach 1:
User data is extracted from the container and stored separately in a user data registry. This extraction ensures that user data is preserved during container updates, as the data remains independent of the container image lifecycle.
Solution Approach 2:
The system merges the updated container image with the preserved user data from the user data registry to create a new container instance, combining the benefits of updated functionality with retained user information.
3Productivity
If the container is updated by replacing the entire container image, then the update process is simple, but user data is lost and service interruption occurs
Solution Approach 1:
The system performs preliminary actions by downloading and validating the new container image before updating, while simultaneously preparing the user data migration. This ensures that if the update fails, the system can rollback without data loss or service interruption.
Solution Approach 2:
The container management table maintains continuous mapping between container names and their storage locations throughout the update process, ensuring that the application remains accessible and functional even during the transition from old to new container images.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A container update method in a container-based vehicle system, and a vehicle system are disclosed. According to one embodiment of the present specification, when it is determined that an update is required while a container is running, user data generated while the container is running is stored in a user data registry, and a container image to be updated is received from a cloud server and stored in a system registry. Then, a new container is created by combining the user data with the container image to be updated. In addition, by changing the matching relationship of a management table, a seamless update from an existing container to a new container is possible.