JP7058918B2 - Data update system - Google Patents

Description

The present invention relates to a technique for updating data in a data processing apparatus.

As a technology for updating data in a data processing device, in a mobile device that can be selectively connected to the data processing device via short-range wireless communication, the data is updated via mobile communication during a period when the data is not connected to the data processing device. Update data is downloaded from the server that provides the data and stored, and the updated data stored when the mobile device can connect to the data processing device is transferred to the data processing device and transferred in the data processing device. A technique for updating data in a data processing apparatus using the updated data is known (for example, Patent Document 1).

Japanese Unexamined Patent Publication No. 2006-11717

In the technique of using the above-mentioned mobile device for updating the data of the data processing device, the following problems occur when a plurality of mobile devices are used in combination.
That is, in this case, each mobile device downloads the same update data from the server and stores it. After that, when any of the mobile devices is connected to the data processing device, the update data accumulated in the connected mobile device is transferred to the data processing device to update the data of the data processing device. ..

Then, after that, inefficiency occurs in which other mobile devices continue to accumulate unnecessary update data that has already been used for update.
Therefore, it is an object of the present invention to efficiently update the data of the data processing device in which a plurality of mobile devices are used in combination for downloading and storing the updated data.

In order to achieve the above problems, the present invention comprises, as a data update system for updating data, a data processing device that holds the data to be updated, and a plurality of mobile devices that can be communicated and connected to the data processing device. Provided is a data update system including an update data server to which each mobile device can communicate with each other. Here, the update data server is an update data storage means that stores update data used for updating the data, and an update data providing means that provides the update data stored by the update data storage means to the mobile device. And the update status management means. Further, in the mobile device, the update data surrogate acquisition means for acquiring and accumulating the update data stored in the update data storage means and the update data surrogate acquisition means are accumulated via the update data providing means. Of the updated data, the update data transfer means for transferring the update data used for updating the data held by the data processing device to the data processing device, the update status confirmation means, and the update data proxy acquisition. It is provided with an update data deletion means for deleting the update data accumulated by the means. Then, when the mobile device communicates with the data processing device, the update status confirmation means of the mobile device acquires the update status of the data of the data processing device from the data processing device and sets it as the confirmation update status. At the same time as holding the data, when the mobile device connects to the update data server, the confirmation update status held is notified to the update data server. Further, the update status management means of the update data server manages the update status as a management update status indicating the update status of the data held by the last data processing device that can be confirmed from the confirmation update status notified from each mobile device. do. Further, the update data deletion means of the mobile device acquires the management update status from the update data server when the mobile device connects to the update data server, and the update data proxy acquisition means is accumulated. Among the update data, in the update status of the data indicated by the acquired management update status, the update data unnecessary for updating the data is deleted.

Here, in such a data update system, in the update data deletion means of the mobile device, among the update data accumulated by the update data proxy acquisition means, the update status of the data acquired from the data processing device. In the above, it may be configured to delete the update data that is unnecessary for updating the data.

Further, the above data update system is one of the update data stored in the update data storage means when the mobile device is connected to the update data server in the update data proxy acquisition means of the mobile device. In the update status of the data indicated by the acquired management update status, only the update data that can be used for updating the data may be configured to be acquired and accumulated via the update data providing means.

Further, the above data update system is acquired from the update data server in the update status confirmation means of the mobile device, rather than the confirmation update status held when the mobile device communicates with the update data server. When the update status indicated by the management update status indicates the update status of the data that has been updated more, the confirmed update status held is configured to be updated to the update status indicated by the management update status. You may.

Further, in the above data update system, when the update data transfer means transfers the update data to the data processing device in the update status confirmation means of the mobile device, the update data is updated using the update data. The data update status of the data processing device may be acquired from the data processing device and held as a confirmation update status.

Further, in the above data update system, the data processing device may be an in-vehicle data processing device mounted on an automobile.
According to the data update system as described above, when each mobile device is connected to the update data server, the mobile device connected to the update data server in the past is at the timing when the mobile device last connected to the data processing device before the connection. The update status of the data processing device can be acquired from the update data server, and the update data unnecessary in the update status can be deleted from the mobile device.

Therefore, it is possible to efficiently use the storage resources of the mobile device to update the data of the data processing device in which a plurality of mobile devices are used in combination.

As described above, according to the present invention, it is possible to efficiently update the data of the data processing device in which a plurality of mobile devices are used for downloading and storing the updated data.

It is a figure which shows the structure of the data update system which concerns on embodiment of this invention. It is a block diagram which shows the structure of the in-vehicle device, the mobile device, and the update data server which concerns on embodiment of this invention. It is a figure which shows the update management information, confirmation update information, and update management table which concerns on embodiment of this invention. It is a flowchart which shows the process at the time of connecting a mobile device which concerns on embodiment of this invention. It is a flowchart which shows the process at the time of connecting an in-vehicle device which concerns on embodiment of this invention. It is a flowchart which shows the update data server access time processing which concerns on embodiment of this invention. It is a flowchart which shows the process at the time of access of the mobile device which concerns on embodiment of this invention. It is a figure which shows the operation example of the update system which concerns on embodiment of this invention.

Hereinafter, an embodiment of the present invention will be described by taking as an example an application to data update of an in-vehicle device mounted on an automobile.
FIG. 1 shows the configuration of the data update system according to the present embodiment.
As shown in the figure, the data update system is composed of an in-vehicle device 1 arranged in a dashboard of a car, a mobile device 2 carried by a user and brought into the car, and an update data server 3. 3 is connected to WAN 4 such as the Internet.

Then, each mobile device 2 can be connected to the in-vehicle device 1 associated in advance by local wireless communication such as Bluetooth (registered trademark) or Wi-Fi. Here, a plurality of bile devices 2 can be related to one in-vehicle device 1.

The mobile device 2 is, for example, a smartphone, a tablet device, or the like.
Further, the mobile device 2 can access the update data server 3 on the WAN 4 via mobile communication.
Next, FIG. 2 shows the configurations of the in-vehicle device 1, the mobile device 2, and the update data server 3.
As shown in the figure, the vehicle-mounted device 1 includes an input device 101 such as a touch panel, a display device 102, a voice input / output device 103 including a microphone and a speaker, an external interface 104 which is the above-mentioned local wireless communication interface, and a vehicle-mounted device. It includes an operating system 105 of device 1, an application running on the operating system 105, a storage device 106, and other peripheral devices 107 such as a GPS receiver and sensors that detect various states of the vehicle.

Further, the in-vehicle device 1 includes the update processing APP111 and other applications such as the navigation APP112 and the music player APP113 as the above-mentioned applications.

Here, the map data is stored in the storage device 106 of the in-vehicle device 1, and the navigation APP 112 uses the map data and the current position calculated by using a GPS receiver provided as the peripheral device 107. , Performs processing such as displaying a guidance screen showing the current position and the route to the destination on the map on the display device 102.

However, in terms of hardware, the in-vehicle device 1 is configured by using a computer equipped with a CPU, a memory, and the like, and in the operating system 105, an application, and the like, the computer executes a predetermined computer program. It is realized by doing.

Next, the mobile device 2 is an operation unit 201, a display 202, an audio input / output unit 203 provided with a microphone, a speaker, and the like, a communication interface 204 which is the above-mentioned local wireless communication interface, and an OS of the mobile device 2. The mobile operating system 205, a mobile application that is an application running on the mobile operating system 205, a mobile communication device 206 that performs mobile communication, a storage unit 207, and other peripheral devices 208 are provided.

Here, the mobile device 2 is another mobile application such as the update data proxy acquisition APP211 and the mobile telephone APP212 that provides a mobile telephone function using the mobile communication device 206, the voice input / output unit 203, and the operation unit 201. It has a mobile application.

In terms of hardware, the mobile device 2 is configured by using a computer equipped with a CPU, a memory, or the like, and in the mobile operating system 205, a mobile application, or the like, the computer has a predetermined computer program. It is realized by executing it.

In the above configuration, the vehicle-mounted device 1 and the mobile device 2 can be connected to each other via the external interface 104 and the communication interface 204.
Then, through the connection, the mobile application of the mobile device 2 and the application of the in-vehicle device 1 can communicate with each other while utilizing the functions of the mobile operating system 205 and the operating system 105.

Next, the update data server 3 includes an update service providing unit 301, an update data DB 302, and an update management table 303.
Then, the mobile device 2 can connect to the WAN 4 via the mobile communication performed by the mobile communication device 206 and can communicate with the update service providing unit 301 of the update data server 3 on the WAN 4.

Hereinafter, the configuration and operation for updating the data of the vehicle-mounted device 1 performed in the data updating system will be described by taking as an example the case of updating the map data stored in the storage device 106 of the vehicle-mounted device 1.

In this case, the update data DB 302 of the update data server 3 stores update data for updating the map data of the in-vehicle device 1 and upgrading to each version up to the latest version.

Further, the update data downloaded from the update data server 3 is stored in the storage unit 207 of the mobile device 2.
Next, the storage device 106 of the vehicle-mounted device 1 stores the update information shown in FIG. 3a. The update information is information managed by the update process APP111, and is an in-vehicle device ID which is an identifier of the own in-vehicle device 1, an applied version indicating a version of map data stored in the storage device 106, and a map of the applied version. Includes applicable date and time representing the date and time the data was updated, as well as other relevant information.

Next, the update data proxy acquisition APP211 of the mobile device 2 is associated with the specific in-vehicle device 1 in advance.
Then, the confirmation update information shown in FIG. 3b is stored in the storage unit 207 of the mobile device 2. The confirmation update information is information managed by the update data proxy acquisition APP211 and is the update information (vehicle-mounted device ID, applicable version, applicable date / time, related) of the vehicle-mounted device 1 managed by the updated data proxy acquisition APP211 of the mobile device 2. Information) and the confirmation date and time indicating the date and time when the update information was last confirmed are registered.

The procedure for generating this confirmation update information will be described later.
Next, in the update management table 303 of the update data server 3, the confirmation update information (vehicle-mounted device ID, Of the applicable version, applicable date and time, related information, confirmation date and time), the confirmation update information with the latest confirmation date and time is registered as update management information.

The procedure for generating the update management information of the update management table 303 of the update data server 3 will be described later.
Next, the update processing APP111 of the in-vehicle device 1 will explain the mobile device connection time processing performed when the mobile device 2 in which the update data proxy acquisition APP211 is associated with the own in-vehicle device 1 is connected to the own in-vehicle device 1. .. The mobile device 2 in which the update data proxy acquisition APP211 is associated with the own vehicle-mounted device 1 automatically connects to the vehicle-mounted device 1 when the mobile device 2 is in a state where the above-mentioned local wireless communication with the vehicle-mounted device 1 is possible. ..

FIG. 4 shows the procedure of this mobile device connection processing.
As shown in the figure, in the mobile device connection processing, the update process APP111 first notifies the connected mobile device 2 of the update information stored in the storage device 106 (step 402).

Then, the mobile device 2 is inquired to determine whether or not the mobile device 2 has accumulated update data for upgrading the map data to a version newer than the applied version of the update information (step 404). ), If it is not stored, the connection between the mobile device 2 and the in-vehicle device 1 is waited for disconnection (step 406), and the process at the time of connecting the mobile device is terminated.

On the other hand, when the update data for upgrading the map data to a version newer than the application version of the update information is stored in the mobile device 2 (step 404), the update data request requesting the update data is made mobile. By transmitting to the device 2, the update data is acquired from the mobile device 2 (step 408), and the map data of the storage device 106 is updated using the acquired update data (step 410).

Then, the update information is updated so that the update of the map data performed is reflected (step 412). That is, here, the applied version of the updated information is updated to the updated map data version, and the applied date and time is updated to the current date and time. Also, update related information as needed.

Then, the mobile device 2 is notified of the updated information after the update in step 412 (step 414).
Then, after waiting for the connection between the mobile device 2 and the in-vehicle device 1 to be disconnected (step 406), the process for connecting the mobile device is completed.
As described above, the update processing APP111 of the vehicle-mounted device 1 has described the processing at the time of connecting the mobile device when the mobile device 2 is connected to the vehicle-mounted device 1.
Next, the in-vehicle device connection time processing performed when the own mobile device 2 is connected to the in-vehicle device 1 associated with the update data proxy acquisition APP211 by the update data proxy acquisition APP211 of the mobile device 2 will be described.

FIG. 5 shows a procedure for processing when the in-vehicle device is connected.
As shown in the figure, the update data proxy acquisition APP211 receives the notification of the update information from the in-vehicle device 1 (step 502) and the request for the update data from the in-vehicle device 1 in the process of connecting the in-vehicle device. The occurrence (step 504) and the occurrence of disconnection of the connection between the own mobile device and the in-vehicle device 1 (step 506) are monitored.

Then, when the notification of the update information is received from the vehicle-mounted device 1, the confirmation update information is updated (step 508). Here, in the update in step 508, the current date and time is added as the confirmation date and time to the received update information to obtain the confirmed update information after the update.

Then, with reference to the confirmation update information after the update, it is checked whether or not unnecessary update data is accumulated in the storage unit 207 (step 510), and if it is not accumulated, the process returns to the monitoring of steps 502-506. On the other hand, if unnecessary update data is stored in the storage unit 207, the unnecessary update data is deleted from the storage unit 207 (step 512), and the process returns to the monitoring of steps 502-506.

Here, in step 510, it is determined that the update data for updating the map data to the version (including the applied version) before the version indicated by the applied version of the confirmation update information is unnecessary update data.

Next, when a request for update data is received from the vehicle-mounted device 1 (step 504), the requested update data is transferred to the vehicle-mounted device 1 (step 514), and the process returns to the monitoring of steps 502-506. ..

Further, if the connection between the own mobile device and the vehicle-mounted device 1 is disconnected (step 506), the process for connecting the vehicle-mounted device is terminated.
As described above, the in-vehicle device connection processing performed when the own mobile device is connected to the in-vehicle device 1 associated with the update data proxy acquisition APP211 by the update data proxy acquisition APP211 of the mobile device 2 has been described.

Next, the update data server access time processing performed when the update data proxy acquisition APP211 of the mobile device 2 accesses the update data server 3 will be described. The update data proxy acquisition APP 211 of the mobile device 2 accesses the update data server 3 using the mobile communication device 206 at a predetermined opportunity. Here, as the predetermined trigger, the arrival of a scheduled time, the occurrence of a predetermined user operation, the occurrence of disconnection of the connection with the in-vehicle device 1, and the like can be used.

FIG. 6 shows the procedure of this update data server access time processing.
As shown in the figure, the update data proxy acquisition APP 211 first notifies the update service providing unit 301 of the update data server 3 of the confirmation update information stored in the storage unit 207 in the update data server access time processing (step 602). ).

Then, after waiting for the reception of the notification of the update management information from the update service providing unit 301 of the update data server 3 (step 604), the confirmation update information is updated (step 606). Here, in the update of step 606, the notified update management information is used as the confirmed update information after the update.

Then, with reference to the confirmation update information after the update, it is checked whether or not unnecessary update data is accumulated in the storage unit 207 (step 608), and if it is not accumulated, the process proceeds to step 612, and if it is accumulated, the process proceeds to step 612. After deleting the unnecessary update data from the storage unit 207 (step 610), the process proceeds to step 612.

Here, in step 608, it is determined that the update data for updating the map data to the version (including the applied version) before the version indicated by the applied version of the confirmation update information is unnecessary update data.

Then, if the process proceeds to step 612, the update data for upgrading the map data to a version newer than the applied version of the confirmation update information, and the update data not accumulated in the storage unit 207 is stored in the update data DB 302. Whether or not it is stored is determined by inquiring to the update service providing unit 301 of the update data server 3, and if it is stored, the update data request requesting the update data is sent to the update service providing unit 301 of the update data server 3. By transmitting, the update data is acquired from the update data server 3 (step 614) and stored in the storage unit 207. Then, the connection with the update data server 3 is disconnected (step 616), and the update data server access time processing is terminated.

On the other hand, if the update data for upgrading the map data to a version newer than the applied version of the confirmation update information is not stored in the update data DB 302 (step 612), the connection with the update data server 3 is established as it is. Disconnect (step 616) and end the update data server access time processing.

The update data server access time processing performed when the update data proxy acquisition APP211 of the mobile device 2 accesses the update data server 3 has been described above.
Here, the update data proxy acquisition APP 211 of the mobile device 2 responds to the inquiry from the in-vehicle device 1 in addition to the above-mentioned in-vehicle device connection processing and update data server access processing, and stores the data in the storage unit 207. It also performs processing such as notifying the in-vehicle device 1 of information such as the version of the map data corresponding to each updated data.

Next, the mobile device access time processing performed when the update service providing unit 301 of the update data server 3 accesses the update data server 3 of the mobile device 2 will be described.

FIG. 7 shows the procedure of this mobile device access time processing.
As shown in the figure, the update service providing unit 301 of the update data server 3 generates a notification of confirmation update information from the mobile device 2 (step 702) and a request for update data (step 704) in the mobile device access time processing. ) And the occurrence of disconnection of the connection with the mobile device 2 (step 706).

Then, when the notification of the confirmation update information occurs (step 702), it is checked whether or not the update management information needs to be updated (step 708). Here, in step 704, the confirmation date and time of the update management information of the update management table 303 in which the same in-vehicle device ID as the in-vehicle device ID of the notified confirmation update information is registered is the confirmation date and time of the notified confirmation update information. If it is older than, it is determined that an update is necessary.

Then, when it is determined that the update of the update management information is not necessary (step 708), the update management of the update management table 303 in which the same in-vehicle device ID as the in-vehicle device ID of the notified confirmation update information is registered. The information is notified to the mobile device 2 (step 712), and the process returns to the monitoring of steps 702-706.

On the other hand, when it is determined that the update management information needs to be updated (step 708), in the update management table 303, the same in-vehicle device ID as the in-vehicle device ID of the notified confirmation update information is registered. The update management information is updated (step 710), and the updated update management information is notified to the mobile device 2 (step 712).

Here, in the update of step 710, the update management information of the update management table 303 in which the same in-vehicle device ID as the in-vehicle device ID of the notified confirmation update information is registered is replaced with the notified confirmation update information. It is done by.

Then, the process returns to the monitoring of steps 702-706.
On the other hand, when a request for update data occurs (step 704), the requested update data is transferred to the mobile device 2 (step 714), and the process returns to the monitoring of steps 702-706.

Then, when the connection with the mobile device 2 is disconnected (step 706), the process at the time of accessing the mobile device is terminated.
The mobile device access time processing performed when the update service providing unit 301 of the update data server 3 has accessed the update data server 3 of the mobile device 2 has been described above.

By the way, here, in addition to the above mobile device access time processing, the update service providing unit 301 of the update data server 3 responds to the inquiry from the mobile device 2 and corresponds to each update data stored in the update DB. It also performs processing such as notifying the mobile device 2 of information such as the version of the map data to be performed.

Hereinafter, regarding the update example of the map data of the in-vehicle device 1 by each of the above processes, "map data ver.i" represents the map data of version i, and "ver.i data" represents the map data of the in-vehicle device 1. The update data to be updated to version i is represented, and "(ver.i)" is described as indicating that the version indicated by the applied version of the update information / confirmation update information / update management information is i.

Now, as shown in FIG. 8, the mobile device A and the mobile device B are associated with the in-vehicle device 1, the map data of the in-vehicle device 1 is the map data ver.1, the update information of the in-vehicle device 1, the mobile device, and so on. It is assumed that the applicable version of the confirmation update information of A, the confirmation update information of the mobile device B, and the update management information in which the vehicle-mounted device ID of the vehicle-mounted device 1 of the update data server 3 is registered is all (ver.1).

In this state, when the mobile device A connects to the update data server 3 after the ver.2 data is accumulated (81) in the update data DB 302 of the update data server 3, the ver.2 data of the update data server 3 becomes mobile. Since the update data is not stored in the mobile device A for the map data of the version newer than the application version (ver.1) of the confirmation update information of the device A, it is downloaded to the mobile device A and stored in the mobile device A (61). ..

Similarly, when the mobile device B connects to the update data server 3, the ver.2 data of the update data server 3 is a map data of a version newer than the applied version (ver.1) of the confirmation update information of the mobile device B. Since the updated data is not stored in the mobile device B, it is downloaded to the mobile device B and stored in the mobile device B (71).

After that, when the mobile device B is connected to the in-vehicle device 1, the ver.2 data stored in the mobile device B is map data of a version newer than the applied version (ver.1) of the update information of the in-vehicle device 1. Because it is the update data for the in-vehicle device 1, it is transferred to the in-vehicle device 1, the map data of the in-vehicle device 1 is updated to the map data ver.2 (51), and the applied version of the update information of the in-vehicle device 1 is changed to (ver.2). It is updated (52). In addition, the updated information after the update of the in-vehicle device 1 is notified to the mobile device B, the applied version of the confirmation update information of the mobile device B is updated to (ver.2) (72), and the version of the mobile device B is changed. 2 Data is deleted (73).

After that, after the ver.3 data is accumulated (82) in the update data DB 302 of the update data server 3, when the mobile device A connects to the update data server 3, the ver.3 data of the update data server 3 becomes available. Since the update data has not been accumulated in the mobile device A for the map data of the version newer than the application version (ver.1) of the confirmation update information of the mobile device A, it is downloaded to the mobile device A and stored in the mobile device A (62). To.

Then, when the mobile device B connects to the update data server 3, the confirmation update information of the mobile device B is notified to the update data server 3, and the application version of the update management information of the update data server 3 has an application date and time. It is updated (83) to the applied version (ver.2) of the confirmed update information that is newer than the update management information. Further, since the ver.3 data of the update data server 3 is the update data that is not accumulated in the mobile device B for the map data of the version newer than the application version (ver.2) of the confirmation update information of the mobile device A, the mobile device. It is downloaded to B and stored in mobile device B (74).

Then, when the mobile device A connects to the update data server 3, the application version of the confirmation update information of the mobile device A is notified from the update data server 3, and the application date and time is the application of the update management information newer than the confirmation update information. Updated (63) to version (ver.2). In addition, the applied version (ver.2) of the confirmation update information after the update indicates that the map data has already been updated by the ver.2 data accumulated in the mobile device A, so that the mobile device has been updated. A deletes (64) the accumulated ver.2 data. Further, here, the update data not accumulated in the mobile device A for the map data of the version newer than the application version (ver.2) of the confirmation update information after the update of the mobile device A does not exist in the update data server 3. Therefore, the update data will not be downloaded.

Next, when the mobile device B connects to the update data server 3, the confirmed update information of the mobile device B and the applied version of the mobile device B are equal to each other, which is newer than the applied version (ver.2) of the confirmed update information of the mobile device B. Since the update data that has not been accumulated in the mobile device B for the map data of the version does not exist in the update data server 3, the applied version of the confirmation update information of the mobile device B is maintained as it is, and the update data is not downloaded. ..

Then, when the mobile device A is connected to the in-vehicle device 1, the ver.3 data stored in the mobile device B is a map of a version newer than the applied version (ver.2) of the update information of the in-vehicle device 1. Since it is updated data for data, it is transferred to the in-vehicle device 1, the map data of the in-vehicle device 1 is updated to the map data ver.3 (53), and the applied version of the updated information of the in-vehicle device 1 is (ver.3). Is updated (54). Further, the updated information after the update of the in-vehicle device 1 is notified to the mobile device A, the applied version of the confirmation update information of the mobile device A is updated to (ver.3) (65), and the version of the mobile device A is changed. 3 Data is deleted (66).

After that, when the mobile device B connects to the vehicle-mounted device 1, the updated information of the vehicle-mounted device 1 is notified to the mobile device B. Then, the mobile device B updates (75) the applied version of the confirmation update information to the applied version (ver.3) of the notified update information. In addition, the applied version (ver.3) of the confirmation update information after the update indicates that the map data has already been updated by the ver.3 data accumulated in the mobile device B, so that the mobile device has been updated. B deletes (76) the accumulated ver.3 data.

After that, when the mobile device A connects to the update data server 3, the confirmation update information of the mobile device A is notified to the update data server 3, and the application version of the update management information of the update data server 3 is notified. It is updated (84) to the applicable version of the information (ver.3).

As described above, according to the update operation of the data update system, when each mobile device 2 is connected to the update data server 3, the mobile device 2 previously connected to the update data server 3 is connected to the in-vehicle device 1 before the connection. It is possible to acquire the update status of the data of the in-vehicle device 1 at the timing of the last connection from the update data server 3 and delete the update data unnecessary in the update status from the mobile device 2.

Further, when the mobile device 2 disconnects from the in-vehicle device 1 as described above, or at least when the connection with the in-vehicle device 1 is disconnected after the update data is transferred from the mobile device 2 to the in-vehicle device 1. If the mobile device 2 always accesses the data update server 3, each mobile device 2 updates the current data update status of the in-vehicle device 1 when the mobile device 2 connects to the update data server 3. It becomes possible to delete the update data that is unnecessary in the update status from the mobile device 2 by acquiring from.

Therefore, it is possible to efficiently use the storage resources of the mobile device 2 to update the data of the in-vehicle device 1 in which a plurality of mobile devices 2 are used in combination.
The embodiment of the present invention has been described above.
Here, in the above embodiment, the update of the map data of the in-vehicle device 1 has been described as an example, but the present embodiment can be similarly applied to the update of software and other arbitrary data.

Further, the above embodiment can be similarly applied to the case of updating a plurality of data of the in-vehicle device 1. That is, in this case, the operation of the above embodiment may be performed for each data.

Further, in the above embodiment, the case where the updated data that does not need to be stored in the mobile device 2 can be identified by the version has been described, but it is not necessary to store the updated data in the mobile device 2 only by the version. The present invention can be similarly applied to cases where the updated data cannot be identified. That is, in this case, the information necessary for identifying the update data that does not need to be stored in the mobile device 2 is stored in the update information-related information, and the update information-related information is reflected. It is sufficient to identify the update data that does not need to be stored in the mobile device 2 in the mobile device 2 from the confirmation update information and the information related to the update management information. Here, as the information to be included in the related information in this case, the identification information such as the file name of the update data applied in the in-vehicle device 1, the number of updates performed in the in-vehicle device 1, and the information received in the in-vehicle device 1 are received. The number of updated data is assumed.

Further, in the above embodiment, the total number of updates may be used instead of the application date and time of the update information, the confirmation update information, and the update management information. That is, in this case, the vehicle-mounted device 1 is provided with a counter that increments each time the data is updated, and when the data is updated in the vehicle-mounted device 1, this count value is added to the update information instead of the application date and time. Is included as the total number of updates. In this case, when the total number of updates is larger, the above embodiment is applied assuming that the application date and time is newer.

Further, in the above embodiment, the update of the data of the in-vehicle device 1 has been described as an example, but this embodiment can be similarly applied to the data update of any data processing device other than the in-vehicle device 1.

1 ... In-vehicle device, 2 ... Mobile device, 3 ... Update data server, 4 ... WAN, 101 ... Input device, 102 ... Display device, 103 ... Voice input / output device, 104 ... External interface, 105 ... Operating system, 106 ... Storage Device, 107 ... Peripheral device, 111 ... Update processing APP, 112 ... Navigation APP, 113 ... Music player APP, 201 ... Operation unit, 202 ... Display, 203 ... Audio input / output unit, 204 ... Communication interface, 205 ... Mobile operating system , 206 ... Mobile communication device, 207 ... Storage unit, 208 ... Peripheral device, 211 ... Update data proxy acquisition APP, 212 ... Mobile telephone APP, 301 ... Update service providing unit, 302 ... Update data DB, 303 ... Update management table.

Claims (6)

A data update system that updates data
A data processing device that holds the data to be updated, and
A plurality of mobile devices capable of communicating with the data processing device,
Each of the mobile devices is provided with an update data server to which communication connection is possible.
The update data server
An update data storage means for storing update data used for updating the data, and an update data storage means.
An update data providing means for providing the update data stored in the update data storage means to the mobile device, and an update data providing means.
Has an update status management means,
The mobile device is
When the mobile device communicates with the update data server without being connected to the data processing device, the update data stored in the update data storage means is acquired via the update data providing means. As a proxy acquisition method for updated data to be accumulated
When the mobile device communicates with the data processing device, the update data used for updating the data held by the data processing device among the update data accumulated by the update data proxy acquisition means is used. The update data transfer means to be transferred to the data processing device, and
Update status confirmation means and
The update data proxy acquisition means has an update data deletion means for deleting the accumulated update data.
The update status confirmation means of the mobile device acquires the update status of the data of the data processing device from the data processing device and holds it as the confirmation update status when the mobile device communicates with the data processing device. At the same time, when the mobile device connects to the update data server, the update data server is notified of the confirmed update status held.
The update status management means of the update data server manages the update status as a management update status indicating the update status of the data held by the last data processing device that can be confirmed from the confirmation update status notified from each mobile device.
The update data deleting means of the mobile device acquires the management update status from the update data server when the mobile device connects to the update data server in a state where the mobile device is not connected to the data processing device by communication . Data update characterized by deleting update data that is unnecessary for updating the data in the update status of the data indicated by the acquired management update status among the update data accumulated by the update data proxy acquisition means. system. The data update system according to claim 1.
The update data deleting means of the mobile device is an update that is unnecessary for updating the data in the update status of the data acquired from the data processing device among the update data accumulated by the update data proxy acquisition means. A data update system characterized by deleting data. The data update system according to claim 1 or 2.
The update data proxy acquisition means of the mobile device is the update data stored in the update data storage means when the mobile device is connected to the update data server in a state where the mobile device is not connected to the data processing device by communication . Of these, in the update status of the data indicated by the acquired management update status, only the update data that can be used for updating the data is acquired and accumulated through the update data providing means. Update system. The data update system according to claim 1, 2 or 3.
The update status confirmation means of the mobile device is not the confirmation update status held when the mobile device communicates with the update data server, but the update status indicated by the management update status acquired from the update data server. However, when the update status of the more advanced data is indicated, the data update system is characterized in that the confirmed update status held is updated to the update status indicated by the management update status. The data update system according to claim 1, 2, 3 or 4.
When the update data transfer means transfers the update data to the data processing device, the update status confirmation means of the mobile device updates the data of the data processing device after the update using the update data. A data update system characterized in that the data is acquired from the data processing device and held as a confirmation update status. The data update system according to claim 1, 2, 3, 4 or 5.
The data processing device is a data update system characterized by being an in-vehicle data processing device mounted on an automobile.

Images