Update of seamless container in vehicles system based on container
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.
1 . A method for updating a container in a container-based vehicle system, comprising:
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; and
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,
wherein the container is a lightweight virtualization instance that is executed in a computer system instance including a program, data, and system libraries.
2 . The method of claim 1 , further comprising:
updating the container by using a container management table on the new container, the container management table configured to map a container name to a source location,
wherein the application reflects the updated container based on items included in the updated container.
3 . The method claim 2 , wherein
updating the container is performed while executing the application.
4 . The method of claim 1 , wherein
the user data item is required to be maintained while the application is executed.
5 . The method of claim 1 , wherein
the update of container is determined, based on recognizing at least one of an addition of a new device to the vehicle, a removal of an existing device from the vehicle, a detection of a request for a specific version of application or a specific version of firmware for a device mounted in the vehicle, an addition of an updated application or updated firmware for the device mounted in the vehicle and associated with a cloud environment, or an addition of an application with a new function using at least two or more devices associated with the cloud environment, to be needed.
6 . The method of claim 1 , further comprising:
detecting a predetermined event satisfying a container update condition while executing the application;
sending, to the server, a request for a container update list based on the detection; and
determining whether the container needs to be updated by analyzing the container update list received from the server in response to the request.
7 . The method of claim 6 , further comprising:
transmitting, to the server, a type of item used by the container based on determining a replacement of the container being needed for the update;
receiving, from the server, a replaceable second container; and
controlling to switch an approach path of vehicle data from the container to the second container.
8 . The method of claim 7 , further comprising:
generating, by the container, the user data item in response to a request for data used by the container from the second container.
9 . The method of claim 1 , further comprising:
requesting the container to prepare for an update;
generating the user data item via the container; and
storing the generated user data item in a user data registry.
10 . The method of claim 2 , further comprising:
interlocking the executed application for controlling the execution of the container
and the new container;
synchronizing runtime data associated with the executed application via the user data item included in the new container; and
executing the application from the new container.
11 . The method of claim 10 , further comprising:
updating, based on the interlocking of the executed application being complete, the container management table to match a source address of the new container to a name of the container.
12 . The method of claim 11 , wherein
updating the container management table includes:
deleting a name of the new container and a source address matched to a name of the new container.
13 . The method of claim 11 , further comprising:
deleting the container before the container is updated; and
deleting the user data item stored in a user data registry.
14 . A vehicle system, comprising:
a processor functionally connected to a container storage unit, a system registry, and a user data registry,
wherein the container storage unit configured to store a container including data and a system library, and at least one program for controlling an execution of an application executable in a vehicle, the system registry configured to store a system container image, and the user data registry configured to store user data generated while executing the container,
wherein the processor is configured to control an update of the container by performing operations including:
executing the application included in the stored container, the application configured to access at least one item included in the container to operate a service related to the vehicle,
receiving, from a server, a container image of an update target based on determining an update of the container being needed,
storing the received container image of the update target in the system registry, and
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
wherein the container is a lightweight virtualization instance that is executed in a computer system instance including a program, data, and system libraries.
15 . The vehicle system of claim 14 , wherein
the operations further include:
updating the container by using a container management table on the new container, the container management table configured to map a container name to a source location, and
wherein the application reflects the updated container based on items included in the updated container.
16 . The vehicle system of claim 15 , wherein
wherein updating the container is performed while executing the application.
17 . The vehicle system of claim 14 , wherein
the operations further include:
detecting a predetermined event satisfying a container update condition while executing the application;
sending, to the server, a request for a container update list based on the detection; and
determining whether the container needs to be updated by analyzing the container update list received from the server.
18 . The vehicle system of claim 14 , wherein
the operations further include:
requesting the container to prepare for an update;
generating the user data item via the container; and
storing the generated user data item in the user data registry.
19 . The vehicle system of claim 15 , wherein
the operations further include:
interlocking the executed application for controlling the execution of the container and the new container; and
synchronizing runtime data associated with the executed application via the user data item included in the new container; and
executing the application from the new container.
20 . The vehicle system of claim 19 , wherein the operations further include:
updating, based on the interlocking of the application being complete, the container management table to match a source address of the new container to a name of the container.