Maintenance system for in-vehicle information equipment

Abstract

To provide a maintenance system for in-vehicle information equipment that reduces a burden relating to updates.SOLUTION: An IVI system 1 issues a maintenance request including OS version information to a maintenance system 3 (S421) when a trigger occurs (S401). The maintenance system 3 transmits a test program to the IVI system 1 (S422). The IVI system 1 obtains a model and OS version of a connected mobile terminal 4 through the test program, and transmits them to the maintenance system 3 as mobile terminal information (S423). According to a measure procedure registered for a combination of the mobile terminal information and the OS version of the IVI system 1 (S431), the maintenance system 3 transmits an update program for resolving a cause for generating a defect caused by the combination (S424) to execute the program, and updates the IVI system 1 (S412).SELECTED DRAWING: Figure 4

Description

Technical Field

[0001] The present invention relates to a technique for maintaining in-vehicle information devices.

Background Art

[0002] As a technique for maintaining in-vehicle information devices, there is known a technique for predicting the timing when maintenance of an IVI system (in-vehicle infotainment system) is required from the driving history of an automobile and data measured during past maintenance, etc., and scheduling a maintenance reservation by a maintenance provider (for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Maintenance such as software update of the IVI system has generally been performed by bringing the automobile to a service center. Here, the IVI system is generally configured to connect local communication with a user's mobile terminal and perform operations in cooperation with the mobile terminal. For example, the IVI system may be configured to perform hands-free calls using the mobile communication function of the mobile terminal, use cloud services using the mobile communication function of the mobile terminal, or play music transferred from the mobile terminal.

[0005] Also, in an IVI system that cooperates with such a mobile terminal, when the version of the OS of the IVI system is not the latest, etc., problems may occur in the cooperative operation depending on the combination of the version and the mobile terminal. In such a case, if the vehicle is taken to the service center to perform maintenance to update the software that causes the problem in the IVI system, until the vehicle is taken to the service center, the user who uses the mobile terminal that may have problems will be in a state where the problem is not resolved, or in a state where a problem may occur even if no problem actually occurs. Also, it is a heavy burden on the user to take the vehicle to the service center.

[0006] On the other hand, such maintenance of the IVI system is not essential for users who use a combination of an IVI system and a mobile terminal that does not have problems. Also, it is a heavy burden on the service center to maintain all IVI systems that may have problems depending on the combination with the mobile terminal.

[0007] Therefore, an object of the present invention is to perform maintenance for updating in-vehicle information devices such as IVI systems to a state where no problems occur with an appropriate and low burden.

Means for Solving the Problem

[0008] To achieve the above object, the present invention provides a maintenance system for updating an in-vehicle information device mounted on an automobile and connectable to a mobile terminal, the maintenance system including a maintenance database and a maintenance server. Here, in the maintenance database, for each combination of an in-vehicle information device type which is a type of the in-vehicle information device and a mobile terminal type which is a type of the mobile terminal, an update program for updating the in-vehicle information device to eliminate a defect that is predicted to occur when the in-vehicle information device of the in-vehicle information device type included in the combination is connected to and used with the mobile terminal of the mobile terminal type included in the combination is registered. Further, the maintenance server includes an information acquisition unit that acquires, via a communication network, the in-vehicle information device type of the in-vehicle information device and the mobile terminal type of the mobile terminal connected to and used with the in-vehicle information device from the in-vehicle information device, and an update program providing unit that, when an update program is registered in the maintenance database in association with the combination of the in-vehicle information device type and the mobile terminal type acquired by the information acquisition unit, provides the update program to the in-vehicle information device via the communication network.

[0009] Here, this maintenance system may be configured such that, in the update program providing unit, when an update program is registered in the maintenance database in association with the combination of the in-vehicle information device type and the mobile terminal type acquired by the information acquisition unit, a defect occurrence test program, which is a program for causing the in-vehicle information device to conduct an investigation and report on whether a defect eliminated by the update of the in-vehicle information device by the update program actually occurs, is transmitted to and executed by the in-vehicle information device, and when a defect occurrence is reported from the in-vehicle information device, the update program is provided to the in-vehicle information device via the communication network.

[0010] Further, in the above maintenance system, in the update program providing means, the update program may be transmitted to the in-vehicle information device via a communication network in a form that is automatically executed by the in-vehicle information device. In order to achieve the above object, the present invention provides a maintenance system for updating an in-vehicle information device mounted on an automobile and connectable to a mobile terminal, the maintenance system having a different configuration including a maintenance database and a maintenance server. In this configuration, in the maintenance database, for each combination of an in-vehicle information device type which is a type of the in-vehicle information device and a mobile terminal type which is a type of the mobile terminal, countermeasure information indicating countermeasures to be taken by the user of the in-vehicle information device is registered in order to eliminate malfunctions that are predicted to occur when the in-vehicle information device of the in-vehicle information device type included in the combination and the mobile terminal of the mobile terminal type included in the combination are connected and used. Then, the maintenance server includes: information acquisition means for acquiring, via a communication network, the in-vehicle information device type of the in-vehicle information device and the mobile terminal type of the mobile terminal connected and used with the in-vehicle information device from the in-vehicle information device; and countermeasure support means for transmitting, via the communication network, the registered countermeasure information to the in-vehicle information device and presenting it to the user of the in-vehicle information device when countermeasure information is registered in the maintenance database in association with the combination of the in-vehicle information device type and the mobile terminal type acquired by the information acquisition means.

[0011] Here, in the above maintenance system, as the in-vehicle information device type, at least one of the model of the in-vehicle information device, the type of the operating system of the in-vehicle information device, and the version of the operating system of the in-vehicle information device can be used.

[0012] In addition, as the mobile terminal type, those representing at least one of the model of the mobile terminal, the type of the operating system of the mobile terminal, and the version of the operating system of the mobile terminal can be used, etc. In addition, the above maintenance system may be configured such that, in the information acquisition means, by receiving, from the in-vehicle information device, a maintenance request including the in-vehicle information device type of the in-vehicle information device transmitted when a predetermined trigger occurs, the in-vehicle information device type of the in-vehicle information device is acquired, and the mobile terminal type is acquired from the in-vehicle information device that is the transmission source of the maintenance request.

[0013] In addition, the above maintenance system may be configured such that, in the information acquisition means, the mobile terminal type is acquired by transmitting and executing a test program, which is a program for causing the in-vehicle information device to investigate and report the mobile terminal type of the mobile terminal connected to the in-vehicle information device.

[0014] Here, in the maintenance system, the in-vehicle information device can be an in-vehicle infotainment system. According to the maintenance system as described above, with respect to the problems caused by a specific combination of the type of the in-vehicle information device and the type of the mobile terminal, countermeasures such as updating the in-vehicle information device and presenting countermeasure information are taken only for the in-vehicle information devices using the mobile terminal in that combination. Therefore, while surely taking countermeasures for the in-vehicle information devices that may have problems, it is possible to reduce the burden on the user, the in-vehicle information device, the maintenance system, and the service center for taking countermeasures for other in-vehicle information devices as well.

[0015] In addition, when taking measures for updating in-vehicle information devices by an update program, since the measures are completed through the communication between the in-vehicle information device and the maintenance system, the burden on the user and the service center that occurs when bringing the automobile to the service center for measures is not generated.

Effect of the Invention

[0016] As described above, according to the present invention, maintenance for updating an in-vehicle information device such as an IVI system to a state where no malfunction occurs can be performed with an appropriate amount and a low burden.

Brief Description of the Drawings

[0017]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Mode for Carrying Out the Invention

[0018] Hereinafter, embodiments of the present invention will be described. Fig. 1 shows the configuration of the remote maintenance system according to this embodiment. As shown in the figure, the remote maintenance system includes an IVI system (in-vehicle infotainment system) 1 mounted on each automobile, a service center system 2 arranged in each service center that provides automobile maintenance services such as a car dealership and a repair shop, and a maintenance system 3.

[0019] Here, the IVI system 1 is a computer that executes an operating system (OS) and an application that operates based on the OS. In this embodiment, the OS of each IVI system 1 is of the same type (lineage) of OS, and the difference is only in the version (build).

[0020] In addition, the IVI system 1 is equipped with a function of connecting to a mobile terminal 4 such as a user's smartphone via local wireless communication such as Wi-Fi or Bluetooth (registered trademark) or wired communication such as USB, and performing cooperative operations with the mobile terminal 4. Further, the IVI system 1 is equipped with a mobile communication function and can be connected to a WAN 5 such as the Internet via mobile communication.

[0021] In addition, the IVI system 1, the service center system 2, and the maintenance system 3 can communicate with each other via the WAN 5. Next, FIG. 2 shows the configuration of the maintenance system 3. The maintenance system 3 is a system that remotely maintains the IVI system 1 via the WAN 5. As shown in the figure, it includes a maintenance server 31, a maintenance information management system 32, and a maintenance DB 33. To the maintenance information management system 32, information on malfunctions of the IVI system 1 experienced at the service center and claims information regarding the IVI system 1 sent from users to the service center are reported via the WAN 5 from the service center system 2.

[0022] The malfunction information includes mobile terminal system malfunction information that is a malfunction related to the connection with the mobile terminal 4. The mobile terminal system malfunction information includes information on the IVI system 1 in which the malfunction occurred, information on the mobile terminal 4, the content of the malfunction, and correspondence information indicating the correspondence taken for the malfunction.

[0023] The information of the IVI system 1 included in the mobile terminal system defect information includes the model of the IVI system 1 and the version of the OS of the IVI system 1, and the information of the mobile terminal 4 includes the model of the mobile terminal 4 and the version of the OS of the mobile terminal 4. In addition, the corresponding information includes whether the defect has been resolved, whether the measure to resolve the defect is an update of the IVI system 1, information on the update program that was able to perform the update of the IVI system 1 to resolve the defect, and the like. In addition, among the claim information, there is mobile terminal system claim information which is a defect related to the connection with the mobile terminal 4, and the mobile terminal system claim information includes the information of the IVI system 1 to which the claim was made, the information of the mobile terminal 4, and the content of the claim. And the maintenance DB 33 stores maintenance data which is data used for remote maintenance of the IVI system 1, and the maintenance information management system 32 analyzes the defect information and claim information of the IVI system 1 reported from the service center system 2, and creates maintenance data to be registered in the maintenance DB 33 and performs maintenance data management such as updating of the maintenance data.

[0024] The maintenance data of the maintenance DB 33 has OS-specific data corresponding to each version of the OS of the IVI system 1. In the OS-specific data, the version of the corresponding OS (IVI OS Ver. in the figure), the test program packaged as an application, and mobile terminal-specific data are registered. The test program is an application for investigating the status of the IVI system 1 of the corresponding version of the OS, and is an application that causes the IVI system 1 to perform processes such as investigating the model and OS version of the mobile terminal 4 connected to the IVI system 1 and reporting it to the maintenance server 31 as mobile terminal information. When the same test program can be commonly used regardless of the version of the OS of the IVI system 1, it is not necessary to register the test program in each OS-specific data, and it is sufficient if the test program to be commonly used is registered in the maintenance data.

[0025] In addition, for the data per OS, for each combination of the model of the mobile terminal 4 and the version of the OS of the mobile terminal 4 for which a defect or claim has been reported from the maintenance information management system 32 regarding the combination with the version of the OS of the corresponding IVI system 1, the data per mobile terminal is registered accordingly. And for the data per mobile terminal, mobile terminal information indicating the model of the corresponding mobile terminal 4 and the version of the OS of the mobile terminal 4 is registered.

[0026] In addition, for the data per mobile terminal, for each event for which a defect or claim has been reported from the maintenance information management system 32 regarding the combination of the mobile terminal information of the corresponding mobile terminal 4 and the version of the OS of the IVI system 1 corresponding to the data per OS included in the data per mobile terminal, the data per event is registered accordingly.

[0027] And for the data per event, the corresponding event (for example, occurrence of an irregular reset, inability to perform voice communication, etc.), the probability of occurrence of the event estimated from the number of reports and frequency of defects or claims of the event for the combination of the type of the corresponding mobile terminal 4 and the version of the OS of the IVI system 1, countermeasure procedures, an update program (patch program) for updating the IVI system 1, etc. are registered.

[0028] The countermeasure procedures describe the procedures of the measures to be taken to avoid the occurrence of the corresponding event for the IVI system 1 used in the combination of the type of the corresponding mobile terminal 4 and the version of the OS of the IVI system 1. Examples of the countermeasure procedures can include a procedure of sending an update program for updating the IVI system 1 to a state where the occurrence of the event can be avoided and having the IVI system 1 execute it, and a procedure of having the IVI system 1 display a work procedure for avoiding the occurrence of the defect indicated by the event when the occurrence of the event cannot be avoided by sending the update program (for example, a procedure of having the IVI system 1 display a message prompting to contact the service center).

[0029] The update program is the update program to be transmitted, which is stored when the transmission of the update program is described in the countermeasure procedure. Further, the update program can be, for example, a program for updating a driver responsible for controlling wireless communication between the IVI system 1 and the mobile terminal 4, a program for updating a driver responsible for controlling data transfer between the IVI system 1 and the mobile terminal 4, etc., software responsible for processing related to the cooperative operation between the IVI system 1 and the mobile terminal 4, or a program for updating other software of the IVI system 1. Further, the update program can also be a program for updating settings related to the cooperative operation between the IVI system 1 and the mobile terminal 4.

[0030] Next, the IVI maintenance process performed by the maintenance server 31 of the maintenance system 3 will be described. Fig. 3 shows the procedure of this IVI maintenance process. The maintenance server 31 monitors the reception of a maintenance request from the IVI system 1 (step 302). Here, when a predetermined trigger occurs, the IVI system 1 issues a maintenance request including information on its own ID, model, and OS version to the maintenance server 31. This predetermined trigger can use the occurrence of initial operation, the completion of a predetermined travel distance (for example, 5000 km) since the previous maintenance request was issued, the elapse of a predetermined time (for example, three months) since the previous maintenance request was issued, the occurrence of a maintenance instruction by the user, etc.

[0031] If the maintenance server 31 receives a maintenance request from the IVI system 1 (step 302), it transmits the test program of the OS-by-OS data of the maintenance DB 33 corresponding to the OS version of the IVI system 1 that is the request issuer to the IVI system 1 and causes it to execute (step 304).

[0032] The IVI system 1 executes the received test program, investigates the model of the mobile terminal 4 connected to the IVI system 1 and the version of the OS of the mobile terminal 4 according to the test program, and as a test result, transmits the mobile terminal information to the maintenance server 31.

[0033] On the other hand, the maintenance server 31 waits to receive the mobile terminal information from the IVI system 1 (step 306). If it receives the mobile terminal information, it checks whether there is event-by-event data registered in the per-mobile-terminal data corresponding to the combination of the received mobile terminal information and the version of the OS of the IVI system 1 in the maintenance DB 33 (step 308). Here, step 308 may be a process of checking whether there is event-by-event data that is registered in the corresponding per-mobile-terminal data and the registered occurrence probability is equal to or greater than a predetermined threshold value.

[0034] If there is no event-by-event data, the process returns to the process from step 302. On the other hand, if there is event-by-event data (step 308), the countermeasure procedure described in the existing event-by-event data is executed (step 310). That is, in step 310, if the countermeasure procedure is a procedure for transmitting an update program and causing the IVI system 1 to execute it, the update program of the event-by-event data is transmitted to the IVI system 1 and executed, and the IVI system 1 is updated to a state where the event that causes a malfunction does not occur. Also, if the countermeasure procedure is a procedure for causing the IVI system 1 to display a work procedure for avoiding the occurrence of a malfunction, a process of causing the IVI system 1 to display the work procedure is performed.

[0035] When the execution of the countermeasure procedure (step 310) is completed, the content of the remote maintenance performed on the service center system 2 and the IVI system 1 is shared (step 312), such as registering the ID of the IVI system 1, the executed countermeasure procedure, and its execution result in a predetermined information sharing server or the like, and the process returns to the process from step 302.

[0036] The above describes the IVI maintenance process performed by the maintenance server 31. Hereinafter, an operation example of the remote maintenance system by such IVI maintenance processing will be shown. As shown in FIG. 4, in the IVI system 1, when a predetermined trigger such as traveling a predetermined travel distance occurs (S401), a maintenance request including information on the version of the OS of the IVI system 1 is issued to the maintenance system 3 (S421). The maintenance system 3 that has received the maintenance request transmits a test program to the IVI system 1 (S422), and the IVI system 1 executes the received test program (S411).

[0037] The IVI system 1 acquires the model of the mobile terminal 4 and the version of the OS of the mobile terminal 4 by executing the test program, and transmits mobile terminal information as a test result to the maintenance system 3 (S423). Here, the IVI system 1 may display the test result to the user according to the test program (S402). The maintenance system 3 searches for a countermeasure procedure corresponding to the combination of the received mobile terminal information and the version of the OS of the IVI system 1, and executes the searched countermeasure procedure (S431). Here, if the searched countermeasure procedure is a procedure for transmitting an update program and causing the IVI system 1 to execute it, the maintenance system 3 transmits the update program to the IVI system 1 (S424). The IVI system 1 executes the received update program, and updates the software, settings, etc. of the IVI system 1 to a state where an event that causes a problem does not occur (S412). However, the update program is not updated if the update to be performed has already been performed.

[0038] Then, the IVI system 1 displays the update result to the user according to the update program (S403). The display of the update result can be, for example, the display of the updated content when the update is performed, or the display of a message indicating that the content has already been updated when the update is not performed.

[0039] On the other hand, if the maintenance system 3 has executed the countermeasure procedure (S431), it shares the content of the remote maintenance performed on the IVI system 1 with the service center system 2 (S441). The embodiments of the present invention have been described above. As described above, according to this embodiment, the countermeasure for the problem caused by the combination of the OS version of the specific IVI system 1, the model of the specific mobile terminal 4, and the OS version is performed only for the IVI system 1 using the mobile terminal 4 in that combination. Therefore, it is possible to surely take countermeasures for the IVI system 1 in which problems may occur, and reduce the burden on the user, the remote maintenance system, and the service center of taking countermeasures for other IVI systems as well.

[0040] In addition, when the update of the IVI system 1 by the update program is taken as a countermeasure, the countermeasure is completed through the communication between the IVI system 1 and the maintenance system 3, so the burden on the user and the service center that occurs when the vehicle is brought into the service center for countermeasures does not occur.

[0041] Here, in the above embodiment, when the update program corresponding to the combination of the OS version of the IVI system 1 and the mobile terminal information is registered in the event-by-event data, the update program is unconditionally transmitted to the IVI system 1 and executed to update the IVI system 1. However, this may be to investigate whether a problem caused by the combination of the OS version of the IVI system 1 and the mobile terminal information has occurred in the IVI system 1, and when a problem has occurred, the update program may be transmitted to the IVI system 1 and executed to update the IVI system 1.

[0042] For example, in this case, the IVI system 1 is made to execute a defect occurrence test that tests whether a defect registered as an event in the per-event data of the maintenance DB 33 of the maintenance system 3 exists in the per-event data and reports the test result to the maintenance system 3, and a procedure for updating the software, settings, etc. of the IVI system 1 by an update program when a defect occurs are registered in the countermeasure procedure for the per-event data of the maintenance DB 33 of the maintenance system 3.

[0043] FIG. 5 shows an operation example of a remote maintenance system that can be applied when testing whether such a defect exists and updating the IVI system 1 when a defect occurs. As shown in the figure, in the IVI system 1, when a predetermined trigger such as traveling a predetermined mileage occurs (S401), a maintenance request including information on the version of the OS of the IVI system 1 is issued to the maintenance system 3 (S421). The maintenance system 3 that has received the maintenance request transmits a test program to the IVI system 1 (S422), and the IVI system 1 executes the received test program (S411), obtains the model of the mobile terminal 4 and the version of the OS of the mobile terminal 4, and transmits mobile terminal information as a test result to the maintenance system 3 (S423). Here, the IVI system 1 may display the test result to the user (S402) according to the test program.

[0044] Here, the operations up to this point are the same as the operations in FIG. 4. Next, the maintenance system 3 searches for a countermeasure procedure corresponding to the combination of the received mobile terminal information and the version of the OS of the IVI system 1, and executes the searched countermeasure procedure (S531). Here, the maintenance system 3 transmits the malfunction occurrence test program to the IVI system 1 according to the countermeasure procedure (S521). Here, the malfunction occurrence test program is, for example, a program that causes the IVI system 1 to execute a malfunction occurrence test that reproduces a situation where a malfunction has occurred in a combination of the corresponding mobile terminal information and the version of the OS of the IVI system 1, and detects and reports the presence or absence of the occurrence of a malfunction.

[0045] Then, the IVI system 1 executes the received malfunction occurrence test program (S511), tests the presence or absence of the occurrence of a malfunction, and displays the test result to the user (S501), and reports the malfunction occurrence test result to the maintenance system 3 as the malfunction occurrence test result (S522).

[0046] If the received malfunction occurrence test result of the maintenance system 3 requires the execution of an additional malfunction occurrence test, the maintenance system 3 transmits an additional malfunction occurrence test program to the IVI system 1 according to the countermeasure procedure (S523). The IVI system 1 executes the received additional malfunction occurrence test program (S512), displays the result of the malfunction occurrence test to the user (S502), and reports the malfunction occurrence test result to the maintenance system 3 as the malfunction occurrence test result (S524).

[0047] Then, if the occurrence of a malfunction is confirmed from the malfunction occurrence test result of S522 or S524, the maintenance system 3 transmits an update program to the IVI system 1 according to the countermeasure procedure (S525). The IVI system 1 executes the received update program to update the software, settings, etc. of the IVI system 1 to a state where an event that causes a malfunction does not occur (S513). Then, the IVI system 1 displays the update result to the user according to the update program (S503). The display of the update result can be, for example, the display of the updated content. On the other hand, if the maintenance system 3 has executed the countermeasure procedure (S531), it shares the content of the remote maintenance performed on the IVI system 1 with the service center system 2 (S541). By thus testing the presence or absence of a malfunction and updating the IVI system 1 when a malfunction has occurred, it is possible to reduce the burden on the user, the remote maintenance system, and the service center of taking countermeasures for the IVI system 1 in which no malfunction has occurred and thus the need for countermeasures is low.

[0048] Next, in the above embodiment, with the test program transmitted from the maintenance system 3 to the IVI system 1, the model of the connected mobile terminal 4 and the version of the OS of the mobile terminal 4 are investigated, and the mobile terminal information is provided to the maintenance system 3. However, this may be provided to the maintenance system 3 in such a form that a program resident in the IVI system 1 acquires the model of the mobile terminal 4 connected to the IVI system 1 and the version of the OS of the mobile terminal 4, stores it as mobile terminal information, and transmits it including the mobile terminal information stored in the maintenance request, or transmits the mobile terminal information stored in response to a request from the maintenance system 3.

[0049] Also, in the above embodiment, for each combination of the version of the OS of the IVI system 1 and the mobile terminal information representing the model and the version of the OS of the mobile terminal 4, countermeasure procedures and update programs are provided by event-by-event data, and countermeasures for malfunctions are taken for the IVI system 1 using the mobile terminal 4 in that combination. However, as long as this combination is a combination of an attribute related to the configuration of the IVI system 1 and an attribute related to the configuration of the mobile terminal 4, other combinations may be used.

[0050] For example, for each combination of any one of the model, OS type, and OS version attributes of the IVI system 1, or a combination of two or more attributes, and any one of the model, OS type, and OS version attributes of the mobile terminal 4, or a combination of two or more attributes, a countermeasure procedure or update program may be provided to take countermeasures against malfunctions for the IVI system 1 using the combination and the IVI system 1 using the mobile terminal 4.

Explanation of Signs

[0051] 1…IVI system, 2…Service center system, 3…Maintenance system, 4…Mobile terminal, 5…WAN, 31…Maintenance server, 32…Maintenance information management system, 33…Maintenance DB.

Claims

1. A maintenance system for updating an in-vehicle information device mounted on an automobile and connectable to a mobile terminal, the maintenance system comprising: the maintenance system includes a maintenance database and a maintenance server; in the maintenance database, for each combination of an in-vehicle information device type which is a type of the in-vehicle information device and a mobile terminal type which is a type of the mobile terminal, an update program for updating the in-vehicle information device to eliminate a defect that is predicted to occur when the in-vehicle information device of the in-vehicle information device type included in the combination is connected to and used with the mobile terminal of the mobile terminal type included in the combination is registered; the maintenance server includes an information acquisition means for acquiring, via a communication network, the in-vehicle information device type of the in-vehicle information device and the mobile terminal type of the mobile terminal connected to and used by the in-vehicle information device; an update program providing means for providing, via the communication network, the update program to the in-vehicle information device when an update program is registered in the maintenance database in association with the combination of the in-vehicle information device type and the mobile terminal type acquired by the information acquisition means. A maintenance system characterized by having this.

2. The maintenance system according to claim 1, wherein the update program providing means when an update program is registered in the maintenance database in association with the combination of the in-vehicle information device type and the mobile terminal type acquired by the information acquisition means, transmits to the in-vehicle information device and causes it to execute a malfunction occurrence test program which is a program for causing the in-vehicle information device to conduct an investigation and report on whether a malfunction eliminated by the update of the in-vehicle information device by the update program actually occurs, and when a malfunction occurrence is reported from the in-vehicle information device, provides the update program to the in-vehicle information device via the communication network. A maintenance system characterized by this.

3. The maintenance system according to claim 1 or 2, wherein the update program providing means transmits the update program to the in-vehicle information device via a communication network in a form that is automatically executed in the in-vehicle information device. A maintenance system characterized by this.

4. A maintenance system for updating in-vehicle information devices mounted on a motor vehicle and connectable to a mobile terminal, wherein the maintenance system includes a maintenance database and a maintenance server, in the maintenance database, for each combination of an in-vehicle information device type which is a type of the in-vehicle information device and a mobile terminal type which is a type of the mobile terminal, countermeasure information indicating measures to be taken by the user of the in-vehicle information device to eliminate malfunctions predicted to occur when the in-vehicle information device of the in-vehicle information device type included in the combination is connected to and used with the mobile terminal of the mobile terminal type included in the combination is registered, the maintenance server includes information acquisition means for acquiring, via a communication network, the in-vehicle information device type of the in-vehicle information device and the mobile terminal type of the mobile terminal connected to and used with the in-vehicle information device from the in-vehicle information device, and countermeasure support means for, when countermeasure information is registered in the maintenance database in association with the combination of the in-vehicle information device type and the mobile terminal type acquired by the information acquisition means, transmitting the registered countermeasure information to the in-vehicle information device via the communication network and causing the user of the in-vehicle information device to be presented with the countermeasure information. The maintenance system is characterized by this.

5. The maintenance system according to claim 1, 2 or 4, wherein the in-vehicle information device type represents at least one of the model of the in-vehicle information device, the type of the operating system of the in-vehicle information device, and the version of the operating system of the in-vehicle information device. The maintenance system is characterized by this.

6. The maintenance system according to claim 1, 2 or 4, wherein the mobile terminal type represents at least one of the model of the mobile terminal, the type of the operating system of the mobile terminal, and the version of the operating system of the mobile terminal. The maintenance system is characterized by this.

7. The maintenance system according to claim 1, 2 or 4, wherein the information acquisition means By receiving, from the in-vehicle information device, a maintenance request including the in-vehicle information device type of the in-vehicle information device, which is transmitted when a predetermined trigger occurs, the in-vehicle information device type of the in-vehicle information device is obtained, and the mobile terminal type is obtained from the in-vehicle information device that is the transmission source of the maintenance request. A maintenance system characterized by this.

8. The maintenance system according to claim 1, 2 or 4, The information acquisition means transmits and executes a test program, which is a program for causing the in-vehicle information device to investigate and report the mobile terminal type of the mobile terminal connected to the in-vehicle information device, to obtain the mobile terminal type. A maintenance system characterized by this.

9. The maintenance system according to claim 1, 2 or 4, The in-vehicle information device is an in-vehicle infotainment system. A maintenance system characterized by this.

Images