JP2019066926A - Application management method and device of connected car mounted machine - Google Patents

Abstract

To realize resource saving and energy saving, while maintaining fast response and instantaneous characteristic of an application, in a connected car mounted machine having constraints in the hardware resource and the loading quantity of energy, by managing an application by using container technique.SOLUTION: An event detection unit 122 detects a container application start event and a container application end event, based on monitoring data collected by a monitoring data acquisition unit 121. A container selection unit 123 selects a container application which starts or ends. A container image management unit 124 manages acquisition and deletion of container images, based on the selection result. A container application management unit 125 manages starting and stop of the container application, based on the selection result.SELECTED DRAWING: Figure 2

Description

  The present invention relates to an application management method and apparatus for a connected car on-board unit equipped with a function of always connecting to the Internet, and in particular, using container technology saves energy and resources without losing responsiveness and instantaneousness. The present invention relates to an application management method and apparatus of a connected car on-board unit to be realized.

  As a typical example of the Internet of Things (IoT), a connected car equipped with a function to always connect to the Internet has attracted attention. The connected car can provide various services to the driver by mounting an onboard OS on computer resources and executing various applications on the onboard OS.

  Patent Document 1 proposes a vehicular information provision system, a vehicular information provision method, and a program for providing information to at least one of the inside and the outside of a traveling vehicle.

JP, 2006-309664, A

  According to Patent Document 1, the resource saving can be realized by automatically controlling the start and stop of the application, but the following three problems can be observed.

  (1) In order to use a java (registered trademark) application, it is impossible to realize instantaneous activation of a required service while traveling.

  (2) It is not possible to provide flexible services because it specializes in installed application control.

  (3) Since the deletion control mechanism of the application is not included, control of the storage area can not be realized, and efficient use of hardware resources is hindered.

  (4) Since the application is always running, the processing load on the CPU increases and power consumption increases.

  SUMMARY OF THE INVENTION The object of the present invention is to solve the above technical problems and to manage applications using container technology, so that in the connected car on-board unit whose hardware resources and energy loading amount are limited, the responsiveness of the application and instantaneous It is to realize resource saving and energy saving while maintaining the nature.

  In order to achieve the above object, the present invention is characterized in that the following configuration is provided in an application management device of a connected car in-vehicle unit in which a computer is mounted.

  (1) A communication means for constantly connecting a computer to the Internet, and a container control agent operating on the in-vehicle OS, the container control agent acquiring the container image via the Internet, and the acquired container image in-vehicle A means for deploying and activating a container application on the OS is provided.

  (2) The container control agent acquires means for collecting monitoring data related to the connected car, means for detecting a container application start event based on the monitoring data, and an image of the container application for which the start event is detected , And means for deploying and activating a container application on the in-vehicle OS.

  (3) A means for container control agent to collect monitoring data related to connected cars, and a means for detecting a container image acquisition event based on the monitoring data,

  A means for acquiring a container image in which an acquisition event is detected, a means for detecting a container application activation event based on monitoring data, and an image of the container application in which the activation event is detected is expanded on the vehicle application on the container application And means for activating.

  (4) The container control agent further includes means for detecting an end event of the container application based on the monitoring data, and means for stopping execution of the container application for which the end event is detected and deleting the image of the container application. I was equipped.

  (5) The container control agent further detects means for detecting the stop event of the container application based on the monitoring data, means for stopping the execution of the container application for which the stop event is detected, and deleting the container image based on the monitoring data A means for detecting an event and a means for deleting a container image in which a deletion event is detected are provided.

  According to the present invention, the following effects are achieved.

  (1) After the start event of the container application is detected, the image is downloaded, deployed, and activated, so that hardware resources of the on-vehicle hardware, in particular, memory resources and CPU resources can be effectively used.

  (2) The container application takes a very short time to start up compared to Java (registered trademark) applications etc. Therefore, even if the start event is detected, even if it is acquired, expanded, or started, processing according to the start event It will be possible to execute instantly without substantial response delay.

  (3) Since the stop event of the container application and the delete event of the container image are distinguished and the frequency of the delete event is lower than the frequency of the stop event, the waste and collection of the container image is repeated in a short time Can be prevented.

  (4) The container image acquisition event and the container application activation event can be distinguished, and the image can be acquired in advance in preparation for the container application activation event. You will be able to launch the application.

FIG. 1 is a functional block diagram showing an example of a network configuration suitable for a connected car 2 on which the connected car in-vehicle unit 1 according to an embodiment of the present invention is mounted. It is a functional block diagram of a first embodiment of the container control agent (12). It is the flowchart which showed the operation | movement of 1st Embodiment. It is a figure showing an example of start event and end event. It is a figure showing other examples of start event and end event. It is a flowchart of container application start processing. It is a flowchart of container application end processing. It is a functional block diagram of a second embodiment of the container control agent (12). It is the flowchart which showed the operation | movement of 2nd Embodiment. It is a figure showing an example of each event of acquisition, start, stop, and deletion. It is a figure showing other examples of acquisition, start, stop, and each event of deletion. It is a flowchart of container image acquisition processing. It is a flowchart of container image starting processing. It is a flowchart of container image stop processing. It is a flowchart of container image deletion processing. It is a functional block diagram showing composition of a 3rd embodiment of the present invention. It is a functional block diagram showing the composition of a 7th embodiment of the present invention.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. FIG. 1 is a functional block diagram showing an example of a network configuration suitable for a connected car 2 on which the connected car in-vehicle unit 1 according to an embodiment of the present invention is mounted.

  The connected car in-vehicle apparatus 1 is mounted on the connected car 2 and constantly connected to the Internet, and can acquire various container images from a plurality of server resources 3 that are also constantly connected to the Internet. In each server resource 3, various container images are stored and managed in advance by the worker operating the worker terminal 4.

  In the connected car in-vehicle apparatus 1, the in-vehicle apparatus hardware 10 is configured by a dedicated or general-purpose computer hardware, and stores a basic program including an operating system (OS) and various basic data, a basic program and various containers. It includes a CPU 102 for executing applications, a RAM 103 for providing a work area to the CPU 102, a wireless interface IF 104 for securing a constant connection with the Internet, and a user interface UI 105 such as a display or touch panel, etc. An on-vehicle device storage 14 for temporary storage is connected.

  The vehicle-mounted device OS 11 operates on the in-vehicle device hardware 10, and the container control agent 12 operates on the vehicle-mounted device OS 11. The container image 13a is downloaded from each server resource 3 onto the vehicle-mounted device storage 14 and temporarily stored, and then expanded into the container application 13b on the vehicle-mounted device OS 11 to be activated and executed.

  The container control agent 12 selects a container application to be executed / stopped based on monitoring data on the connected car 2 status, road surface condition, position or environment etc, and further executes / stops the container application and its container image Control acquisition / deletion of

  FIG. 2 is a functional block diagram of the first embodiment of the container control agent 12. The monitoring data acquisition unit 121 is monitoring data regarding latitude, longitude, altitude and time output by GPS (not shown) mounted on the connected car 2, and vehicle speed, engine speed, acceleration, fuel consumption, detected by the on-vehicle sensor. Collects various monitoring data output by road surface condition, traveling distance, traveling time, maintenance, temperature, humidity, illuminance, wireless signal, calendar.

  The event detection unit 122 detects a container application start event serving as a container application start trigger based on the monitoring data, and a container application end event serving as a container application termination trigger. 122 b.

  The container selection unit 123 selects a container application to start or end based on the start event or the end event of the container application.

  The container image management unit 124 downloads the corresponding container image from the server resource 3 based on the selection result of the container selection unit 123 and stores the downloaded container image in the vehicle storage 14 or the container application list corresponding to the container application. Delete the container image on the storage 14

  The container application management unit 125 expands the container image on the on-vehicle device storage 14 into the container application on the on-vehicle device OS and starts up or starts on the on-vehicle device OS based on the selection result by the container selection unit 123 Stop the container application inside.

  In the present embodiment, for example, when it is detected that the connected car 2 has entered a predetermined tourist area based on positional information of the connected car 2, a tourist guidance application specific to the tourist area is selected, and the container By automatically acquiring, deploying, and activating an image from the corresponding server resource 3, it is possible to provide a tourist guidance service to the driver.

  In addition, when it is detected that the connected car 2 has escaped from the tourist area, the acquired tourist information application is automatically terminated and deleted, whereby CPU resources and memory resources are not imposed on the driver. It can be opened, and not only resource saving but energy saving is realized.

  FIG. 3 is a flow chart showing the operation of the first embodiment of the present invention, mainly showing the operation of the container control agent 12.

  In step S11, the monitoring data acquisition unit 121 acquires monitoring data from the GPS, each sensor, and the like. In step S12, based on the monitoring data, the event detection unit 122 determines whether a start event of the container application has occurred. If the start event has occurred, the process proceeds to step S13 and the container application start process (FIG. 6) is executed.

  In the present embodiment, for example, as shown on the right side of FIG. 4, the traveling position of the connected car 2 approaches or reaches a predetermined application start area A1 based on monitoring data (latitude, longitude) acquired from GPS If determined, this is determined to be a container application start event.

  Alternatively, as shown on the right side of FIG. 5, if it is determined that the traveling altitude of the connected car 2 approaches or reaches the predetermined application start altitude H1 based on the monitoring data (altitude) acquired by the GPS, this is It is determined that this is a container application start event.

  FIG. 6 is a flow chart showing the procedure of container application start processing executed in step S13.

  In step S21, the container selection unit 123 selects a container application to be newly activated based on the container application start event. In step S22, the container image management unit 124 requests an image of the application to the server resource 3 that manages the selected container application.

  In step S23, the container image management unit 124 acquires the requested container image from the server resource 3 and temporarily stores the acquired container image in the on-vehicle device storage 14. In step S24, the container application management unit 125 deploys the temporarily stored container image into a container application on the vehicle-mounted device OS, and starts and executes the container application.

  Returning to FIG. 3, if it is determined in step S12 that a container start event has not occurred, the process proceeds to step S14, and it is determined whether a container application end event has occurred. When an end event is detected, the process proceeds to step S15, and a container application end process (FIG. 7) is executed.

  In the present embodiment, as shown on the left side of FIG. 4, when the traveling position of the connected car 2 detected based on the monitoring data acquired from the GPS is out of the predetermined application start area A1, this is a container. It is judged as an application end event.

  Alternatively, as shown on the left side of FIG. 5, when the traveling height of the connected car 2 detected based on the monitoring data acquired by the GPS is lower than the predetermined application start height H1, this is a container application It is judged as an end event of.

  FIG. 7 is a flowchart showing the procedure of the container application termination process. In step S31, the container selection unit 123 selects a container application to be newly terminated based on the container application termination event. In step S32, the container application management unit 125 stops the selected container application. In step S 33, the container image management unit 124 deletes the image of the stopped container application from the on-vehicle device storage 14.

  According to the present embodiment, since the container image is downloaded and activated after the start event of the container application is detected, effective utilization of the hardware resources of the on-vehicle hardware 10, in particular, the memory resource and the CPU resource is achieved. It will be possible.

  Also, since the container application takes a very short time to start up compared to Java (registered trademark) applications etc., even if acquisition, deployment, and activation are performed after the start event is detected, processing according to the start event is performed. It becomes possible to execute instantaneously without a substantial response delay.

  FIG. 8 is a functional block diagram showing the configuration of the container control agent 12 according to the second embodiment of the present invention, and the same reference numerals as FIG. 2 represent the same or equivalent parts, and therefore the description thereof is omitted. .

  In the first embodiment described above, the container image acquired immediately in response to the start event of the container application is immediately expanded to start the container application, and the image of the stopped container application is immediately responded to the termination event of the container application. Described as deleting.

  According to the first embodiment, the hardware resources of the on-vehicle apparatus hardware 10 can be extremely effectively used. However, in a situation where the connected car 2 repeatedly approaches and leaves the application start area A1 in a short time, acquisition and deletion of container images may be repeated, which may waste radio resources. Therefore, in the second embodiment, not only hardware resources of the on-vehicle apparatus hardware 10 but also effective utilization of radio resources are enabled.

  In this embodiment, the event detection unit 122 is a container that acquires a container image from each server resource 3 and temporarily stores it on the on-vehicle device storage 14 instead of the container application start event detection unit 122 a of the first embodiment. A detection unit 122c that detects an image acquisition event, and a detection unit 122d that detects a container application activation event that develops and activates the acquired container image on a vehicle application on the vehicle-mounted device OS 11.

  The event detection unit 122 further detects a container application stop event for stopping a container application being activated, instead of the container application end event detection unit 122b in the first embodiment, and the stopped container The detection unit 122 f is configured to detect a container image deletion event for deleting an application image from the on-vehicle device storage 14.

  The container selection unit 123 selects container images to be acquired or deleted based on the container image acquisition event or the container image deletion event. The container selection unit 123 further selects a container application to be started or stopped based on the container application start event or the container application stop event.

  FIG. 9 is a flowchart showing the operation of the second embodiment of the present invention. In step S41, the monitoring data acquisition unit 121 acquires monitoring data from each sensor or the like. In step S42, it is determined based on each of the monitoring data whether a container image acquisition event has occurred. If an acquisition event has occurred, the process proceeds to step S43 and container image acquisition processing (FIG. 12) is executed.

  In step S44, it is determined based on each of the monitoring data whether or not a container image activation event has occurred. If the start event has occurred, the process proceeds to step S45, and the container application start process (FIG. 13) is executed.

  In this embodiment, for example, as shown on the right side of FIG. 10, when it is detected that the traveling position of the connected car 2 approaches or reaches a predetermined application acquisition area A2 based on the monitoring data acquired from the GPS It is determined that this is a container image acquisition event, and the corresponding container image is acquired from the server resource 3 and stored in the on-vehicle device storage 14.

  Furthermore, when it is detected that the traveling position of the connected car 2 approaches or reaches a predetermined application activation area A3 set inside the application acquisition area A2, it is determined that this is a container application activation event.

  Alternatively, as shown on the right side of FIG. 11, when it is detected that the traveling altitude of the connected car 2 has reached a predetermined application acquisition altitude H2 based on monitoring data acquired by GPS, this is a container application acquisition It is judged as an event.

  Furthermore, when it is detected that the traveling altitude of the connected car 2 approaches or reaches a predetermined application activation altitude H3 set higher than the application acquisition altitude A2, it is determined that this is a container application activation event.

  FIG. 12 is a flowchart showing the procedure of the container image acquisition process. In step S51, the container selection unit 123 selects a container application to be acquired based on the container application acquisition event. In step S52, the container image management unit 124 requests an image of the container application from the server resource 3 that manages the selected container application. In step S53, the container image management unit 124 acquires the requested container image from the server resource 3 and temporarily stores the acquired container image in the on-vehicle device storage 14.

  FIG. 13 is a flowchart showing the procedure of the container application activation process. In step S61, a container application to be newly activated is selected by the container selection unit 123 based on the container application activation event. In step S62, it is determined whether the image of the selected application has been acquired. If not acquired, the process proceeds to step S63, and the corresponding container image is acquired from the server resource 3 and stored in the on-vehicle device storage 14.

  In step S64, the container image management unit 124 deploys the container image on the vehicle-mounted device storage 14 corresponding to the selected container application into a container application on the vehicle-mounted device OS and executes it.

  Referring back to FIG. 9, in step S46, it is determined whether a container application stop event has occurred based on the acquired monitoring data. If the stop event has occurred, the process proceeds to step S47 and the container application stop process (FIG. 14) is executed.

  In step S48, it is determined based on each of the monitoring data whether a container image deletion event has occurred. If a delete event has occurred, the process proceeds to step S49, and a container image delete process (FIG. 15) is executed.

  In this embodiment, as shown on the left side of FIG. 10, when it is detected that the traveling position of the connected car 2 has left the predetermined application activation area A3 based on the monitoring data acquired from the GPS, It is determined that the container application stop event.

  Furthermore, when it is detected that the traveling position of the connected car 2 has also left the application acquisition area A2, it is determined that this is a container image deletion event.

  Alternatively, as shown on the left side of FIG. 11, when it is detected that the traveling height of the connected car 2 has decreased to the predetermined application stopping height H4 based on the monitoring data acquired by the GPS, this is a container application It is judged as a stop event.

  Further, when it is detected that the traveling height of the connected car 2 has dropped to the container image deletion height H5 set lower than the application stop height H4, it is determined that this is a container application deletion event.

  FIG. 14 is a flowchart showing the procedure of the container application stop process. In step S71, the container selection unit 123 selects a container application to be stopped based on the container application stop event. In step S72, the container application management unit 125 stops the selected container application.

  FIG. 15 is a flowchart showing the procedure of the container image deletion process. In step S81, the container selection unit 123 selects a container image to be deleted based on the container application deletion event. In step S82, the container application management unit 125 determines whether the container application corresponding to the selected container image has been stopped. If not stopped, the process proceeds to step S83 to stop the application. In step S84, the selected container image is deleted from the vehicle-mounted device storage 14.

  According to the present embodiment, the stop event of the container application and the delete event of the container image are distinguished, and the frequency of the delete event is lower than the frequency of the stop event, so deletion and acquisition of the container image can be performed in a short time. Can prevent repeated wastes.

  Further, according to the present embodiment, the container image acquisition event and the container application activation event can be distinguished, and in preparation for the container application activation event, the image can be acquired in advance. It will be possible to launch container applications in a short time.

  In each of the above embodiments, the connected car 2 selects and processes the container application to be started or ended based on the monitoring data acquired by itself, or the container application / container image to be acquired, started, stopped, or deleted. It has been described as selective treatment.

  However, the present invention is not limited to this, and as in the third embodiment shown in FIG. 16, when the connected car 2 transmits the monitoring data acquired by itself to the monitoring server 5 via the Internet, the monitoring The server 5 may detect each event in the same procedure as described above.

  Alternatively, as in the fourth embodiment illustrated in FIG. 17, the connected car 2 transmits the monitoring data acquired by itself to the monitoring server 5 via the Internet, and the monitoring server 5 itself is unique to each connected car such as temperature and humidity. Otherwise, monitoring data may be separately acquired, and each event may be detected according to the same procedure as described above based on the monitoring data.

  In that case, when the monitoring server 5 detects a start event (first embodiment) or an acquisition event (second embodiment), the monitoring server 5 selects a container application in response to this, and selects the container image from the corresponding server resource 3 It can be provided to the connected car 2 and processed by the server push method.

  Similarly, the container application is selected in response to the end event (first embodiment) or the deletion event (second embodiment), and the result is notified to the connected car 2 by server push, and in response, the connected application is connected. The car 2 may handle stopping of the container application and deletion of the container image.

  Furthermore, although each of the above embodiments has been described as detecting each event based on the position and height of the connected car 2, the present invention is not limited to this, for example, a predetermined reference value Is detected as a sudden braking of the connected car 2 when it detects a negative acceleration exceeding 50%, and this is used as a start / acquisition event to acquire, deploy, and start the shooting application of the drive recorder, while ending or stopping an elapse of a predetermined time It may be determined that the shooting of the drive recorder is ended.

  Alternatively, when a wireless signal emitted by the ETC system is received, this may be determined as a start / acquisition event, and an application for ETC processing may be acquired, deployed, and activated.

  Alternatively, for reproduction of content such as map, music, video, etc. whose use area or use time is limited by copyright, acquire the reproduction application as start / acquisition event of entering the use area or time zone, It may be determined that the user has left the area of use or the time zone as an end / delete event and may delete the event.

  Alternatively, start / acquire an application that supports safe driving with the start / acquisition event that the amount of rainfall or snowfall exceeds a predetermined reference value, start it, and end / delete it when the amount of rainfall falls below the reference value. It may be determined as an event and the application may be deleted.

  DESCRIPTION OF SYMBOLS 1 ... connected car in-vehicle machine, 2 ... connected car, 3 ... server resource, 4 ... worker terminal, 5 ... monitoring server, 10 ... in-vehicle machine hardware, 11 ... in-vehicle device OS, 12 ... container control agent, 13 a ... container Image, 13b ... container application, 14 ... onboard storage

Claims (14)

In the application management device of the connected car on-board unit equipped with a computer,
Communication means for constantly connecting a computer to the Internet,
Equipped with a container control agent that runs on the in-vehicle operating system,
The container control agent
A means for acquiring container images via the Internet,
An application management device for a connected car in-vehicle unit, comprising: means for expanding the acquired container image into a container application on the in-vehicle OS and activating the container application. The container control agent
Means for collecting surveillance data related to connected cars,
A means for detecting a container application start event based on monitoring data;
The apparatus according to claim 1, further comprising: means for acquiring an image of the container application in which the start event has been detected, and deploying the container application on the in-vehicle OS and activating the container application. . The container control agent
Means for collecting surveillance data related to connected cars,
A means for detecting a container image acquisition event based on monitoring data;
A means for acquiring a container image in which an acquisition event is detected;
A means for detecting a container application activation event based on the monitoring data;
The apparatus according to claim 1, further comprising: means for deploying the image of the container application in which the start event has been detected into the container application on the in-vehicle OS and activating the container application. The container control agent
Means for collecting surveillance data related to connected cars,
Means for transmitting the monitoring data to a monitoring server on a network;
The connected car in-vehicle unit application according to claim 1, further comprising: means for acquiring an image of a container application in which the monitoring server has detected the start event and deploying the container application on the in-vehicle OS and launching the container application. Management device. The container control agent
Means for collecting surveillance data related to connected cars,
Means for transmitting the monitoring data to a monitoring server on a network;
A means for acquiring a container image in which the monitoring server has detected an acquisition event;
The apparatus according to claim 1, further comprising: means for deploying an image of a container application whose detection event has been detected by the monitoring server into the container application on the in-vehicle OS and activating the container application. The container control agent further
A means for detecting an end event of a container application based on monitoring data;
The apparatus according to claim 2, further comprising: means for stopping the execution of the container application whose end event is detected and deleting the image of the container application. The container control agent further
A means for detecting container application stop events based on monitoring data;
A means for stopping the execution of the container application whose stop event is detected;
A means for detecting a container image deletion event based on monitoring data;
4. The application management device for a connected car in-vehicle unit according to claim 3, further comprising: means for deleting a container image in which a deletion event has been detected. The container control agent further
The apparatus according to claim 4, further comprising: means for stopping execution of the container application that has detected the end event by the monitoring server and deleting the image of the container application. The container control agent further
A means for stopping the execution of the container application for which the monitoring server has detected a stop event;
6. The application management device for a connected car in-vehicle unit according to claim 5, further comprising: means for deleting a container image in which the monitoring server has detected a deletion event.   The application management device of a connected car in-vehicle unit according to any one of claims 1 to 9, wherein the monitoring data is at least one of a position, an altitude, and a time detected by an in-vehicle GPS.   The monitoring data is at least one of vehicle speed, engine speed, acceleration, fuel consumption, road surface condition, traveling distance, maintenance time, temperature, humidity, illuminance, wireless signal, and calendar detected by the on-vehicle sensor The application management device of a connected car on-board unit according to any one of claims 1 to 10. In an application management method of a connected car OBE equipped with a computer constantly connected to the Internet,
Get container image via internet,
Deploy acquired container image to container application on in-vehicle OS,
An application management method of a connected car on-board unit, characterized by starting the container application. Collect surveillance data related to connected cars,
Detect container application start event based on monitoring data,
Get an image of the container application where the start event was detected,
The application management method of a connected car in-vehicle unit according to claim 12, wherein the acquired image is developed into a container application on the in-vehicle OS and started. Collect surveillance data related to connected cars,
Send monitoring data to the monitoring server on the network,
Acquires the image of the container application that the monitoring server detected the start event,
The application management method of a connected car in-vehicle unit according to claim 12, wherein the acquired image is developed into a container application on the in-vehicle OS and started.

Images