Program update system and vehicle management server

Abstract

The present invention relates to a program update system and a vehicle management server for transmitting, to a vehicle, an update program for updating an existing program of an electronic device mounted on the vehicle, the program update system comprising: a communication unit for communicating with the vehicle; and a control unit for controlling the update process, the control unit determining whether or not to present a display relating to the update process of the existing program by the update program to a vehicle user in accordance with the type of the update program, and transmits, to the vehicle via the communication unit, information for causing a predetermined information terminal to display a display related to the update process determined to be presented to the vehicle user.

Description

[0001] This application is a divisional application of the application with application number 202011221484.4 and invention title "Program Update System and Vehicle Management Server", which was filed with the State Intellectual Property Office of China on November 5, 2020. Technical Field

[0002] The present disclosure relates to a program update system and a vehicle management server. Background Art

[0003] A plurality of electronic devices called ECUs (Electronic Control Units) are mounted in a vehicle. In-vehicle devices such as ECUs each include one or more control units such as CPUs and a storage unit that stores one or more programs to be executed by the control unit, and execute respective functions. In order to improve the functions of the electronic devices, a method has been proposed to update the programs stored in the storage unit to updated versions. In particular, a method has been proposed in which a vehicle receives program update data from an external server via wireless communication so that the program can be updated without going to a repair shop or the like.

[0004] Japanese Patent Application Laid-Open No. 2011-148398 discloses a program update system for updating a program installed in an ECU mounted on a vehicle. In this system, since the management device manages version information and update files for each vehicle ID, the update file is sent to the ECU only when the program installed in the ECU based on the vehicle ID sent from the ECU is not the latest version, thereby improving the distribution efficiency.

[0005] If the update status (completion notice, permission request) for vehicle users, occupants, etc. (hereinafter referred to as "vehicle users") is displayed according to the progress of the update process regardless of the content updated by the update program, there is a concern that vehicle users may feel irritated. On the other hand, if the update status for vehicle users is not displayed regardless of the progress of the update process, there is a concern that vehicle users may feel uneasy. Summary of the Invention

[0006] The present disclosure provides a program update system and a vehicle management server that can reduce the irritation and uneasiness felt by vehicle users.

[0007] One aspect of the disclosed technology relates to a vehicle management server that sends an update program for updating an existing program of an electronic device mounted on a vehicle to the vehicle, and includes: a communication unit that communicates with the vehicle; and a control unit that controls the update process. The control unit determines whether to present a display related to the update process of the existing program by the update program to the vehicle user according to the type of the update program, and sends, via the communication unit, information for causing a specified information terminal to display the display related to the update process determined to be presented to the vehicle user to the vehicle.

[0008] In addition, another aspect of the disclosed technology relates to a program update system, including: a vehicle; a vehicle management server that communicates with the vehicle and sends an update program for updating an existing program of an electronic device mounted on the vehicle to the vehicle; and an information terminal that can communicate with the vehicle management server. The vehicle management server determines whether to present a display related to the update process of the existing program by the update program to the vehicle user according to the type of the update program, and sends information for causing the information terminal to display the display related to the update process determined to be presented to the vehicle user to the vehicle.

[0009] According to the program update system and the vehicle management server of the above disclosed technology, it is possible to reduce the irritation and uneasiness felt by vehicle users. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Hereinafter, features, advantages, technology, and industrial importance of exemplary embodiments of the present invention will be described with reference to the drawings, in which the same reference numerals denote the same components, where

[0011] Figure 1 is a diagram showing a configuration example of a program update system according to one embodiment;

[0012] Figure 2 is a diagram showing an example of an update scenario stored in a storage unit of a vehicle management server;

[0013] Figure 3 is a flowchart showing a process of selecting an update scenario associated with an update program performed by a control unit of a vehicle management server. DETAILED DESCRIPTION OF THE INVENTION

[0014] The program update system related to the disclosed technology pre - stores multiple update scenarios in a server. The multiple update scenarios define update events (completion notification, permission request) that cause an information terminal to display a display related to the update status based on the type of the update program, etc. When updating the program, information for causing the information terminal to display a display corresponding to the update event determined in the update scenario associated with the update program is sent from the server to the vehicle. Thereby, the irritation and uneasiness felt by the vehicle user regarding the display of the update status during the update process of the program are reduced.

[0015] <Embodiment>

[0016] Hereinafter, an embodiment of the disclosed technology will be described in detail with reference to the accompanying drawings.

[0017] [Structure]

[0018] Figure 1 It is a diagram showing a configuration example of a program update system according to an embodiment. Figure 1 The illustrated program update system 10 includes a vehicle 100, a vehicle management server 200, and a mobile device 300. The vehicle 100 includes a communication device 110, a plurality of electronic devices 120, and a display device 130. Among them, the number of the electronic devices 120 is not limited.

[0019] The communication device 110, the plurality of electronic devices 120, and the display device 130 are connected via an in - vehicle network such as CAN (Controller Area Network) so as to be able to communicate. In addition, the communication device 110 is a data communication module (DCM), etc., and is connected via a wireless network such as 4G, Wi - Fi to external devices such as the vehicle management server 200 and the mobile device 300 so as to be able to communicate.

[0020] The vehicle management server 200 is a server that manages update programs required to update the existing programs of the electronic device 120 mounted on the vehicle 100. The vehicle management server 200 includes a communication unit 210, a storage unit 220, and a control unit 230. The communication unit 210 performs wireless communication with the communication device 110 of the vehicle 100, and accepts inquiries for updates from the vehicle 100, downloads update programs to the vehicle 100, and so on. The storage unit 220 stores update programs and update schemes required for updating the existing programs of the electronic device 120. The update scheme is information such as an update event (i.e., a notification or a request (described later)) displayed regarding the update process that determines an update status indicating the progress of the program update process, and is associated with the update program according to the type of the update program. The control unit 230 controls the vehicle management server 200 including the update process. For example, the control unit 230 can determine whether to display a display related to each update status to the vehicle user for each of a plurality of update statuses according to the type of the update program. In the present embodiment, the control unit 230 determines the display related to the update status to be presented to the vehicle user by selecting an update scheme corresponding to the type of the update program from the storage unit 220.

[0021] Figure 2 It is a diagram showing an example of an update scheme stored in the storage unit 220 of the vehicle management server 200. In Figure 2 this example, nine update schemes that define update events are defined based on the type of the update program, that is, the content to be updated (update content) by the update program, the urgency (urgency of the update) predetermined according to the content and importance of the update program, and the presence or absence of the vehicle user's setting for automatic update (automatic update setting).

[0022] An update event is used to cause an information terminal with a display screen to display information corresponding to the event. The information terminals in the present embodiment are the display device 130 and the mobile device 300. As an example of such an update event, the following can be cited: (1) an update start notification notifying the start of an update process for updating a program; (2) a data DL permission request requesting permission from a vehicle user for downloading an update program from the vehicle management server 200 to the electronic device 120; (3) a data DL completion notification notifying the completion of downloading an update program from the vehicle management server 200 to the electronic device 120; (4) a start preparation completion notification notifying the completion of start preparation for starting an update process of an existing program using the update program; (5) a start permission request requesting permission from a vehicle user for starting an update process of an existing program using the update program (i.e., control switching content); and (6) an update completion notification notifying the completion of an update process of an existing program using the update program. In addition, the update event may appropriately determine notifications and permission requests other than those described above. For example, information indicating the progress of the update process such as a notification shown before the update start notification, which conveys the existence of a program that should be updated, and a permission request for starting the update related to the update program can be cited.

[0023] As an example, one type of update program, that is, the update content, is classified into content that changes the control specifications of the actuators provided in the vehicle 100 (update scenarios 1 to 8) and content that does not change the control specifications of the actuators provided in the vehicle 100 (update scenario 9).

[0024] The content that changes the control specifications of the actuators provided in the vehicle 100 (update scenarios 1 to 8) is, for example, content that changes the actions of devices related to the behavior of the vehicle (the inter-vehicle distance between the own vehicle and the preceding vehicle in driving assistance, the operation timing and workload of automatic braking, etc.), content that changes the actions of devices installed in the vehicle (the opening and closing speed of the automatic sliding door, the lighting start time / lighting end time of the automatic headlamp, etc.), and other content that the vehicle user can recognize the change before and after the update program. The content that changes the control specifications of the actuators provided in the vehicle 100 can be classified into content that adds a new function not previously installed in the vehicle 100 and generally requires permission from the vehicle user of the vehicle 100 during the update (update scenarios 1 to 4); and content that improves the functions already installed in the vehicle 100, adds processing and countermeasures for the existing functions, and does not require permission from the vehicle user of the vehicle 100 during the update (update scenarios 5 to 8).

[0025] On the other hand, the content that does not change the control specifications of the actuator provided in the vehicle 100 (update scenario 9) is, for example, the content that changes the behavior of the function of automatically collecting the driving data of the vehicle and sending it to a specified data center (the type of data collected, the timing of uploading the collected data, etc.), and the vehicle user cannot recognize this change before and after the update program. Since the program that does not change the content of the control specifications of the actuator provided in the vehicle 100 (update scenario 9) does not affect the vehicle user or the driving of the vehicle, it is defined that, regardless of the state of the automatic update setting and the urgency of the update, an update can be implemented without displaying either a notification or a permission request to the vehicle user as an update event.

[0026] As an example, one type of update program, that is, the urgency of the update, is divided into an update scenario with a relatively low urgency of the update (update scenarios 1 and 5) and an update scenario with a relatively high urgency of the update (update scenarios 2, 3, 6, and 7). The update scenario with a relatively low urgency of the update is defined as being able to perform the update while displaying all notifications to the vehicle user during the update process of the program. On the other hand, as an example, the update scenario with a relatively high urgency of the update is further divided into two types according to which process in the update process the information of the update event is displayed to the vehicle user.

[0027] The first division with a relatively high urgency of the update is an update scenario (update scenarios 2 and 6) that displays the information of the update event for allowing the request and / or notifying the download process of the update program. The update event of this first division can be applied to, for example, an update program that wants to confirm with the vehicle user in advance whether data can be written to the vehicle 100 or wants to notify the vehicle user that the download of the update program has been completed. For example, an update program with a large amount of data and high communication costs and communication time can be exemplified.

[0028] The second division with a relatively high urgency of the update is an update scenario (update scenarios 3 and 7) that displays the information of the update event for allowing the request and / or notifying the start process of the downloaded update program. The update event of this second division can be applied to, for example, an update program that wants to notify the vehicle user that the vehicle control will be changed from now on or wants to confirm with the vehicle user in advance whether the vehicle control can be changed. For example, an update program related to the change in the behavior and riding feeling of the vehicle can be exemplified.

[0029] The automatic update setting is an item that is pre - equipped in the vehicle 100 and can be arbitrarily set by the vehicle user. When the automatic update is set to off, in the update process of the program during the period from the update start notification to the update completion notification, the update is implemented based on the update scheme defined according to the above - mentioned update urgency (update schemes 1 - 3, 5 - 7). On the other hand, when the automatic update is set to on, it is defined that in the update process of the program during the period from the update start notification to the update completion notification, regardless of the update urgency, the update can be implemented without displaying to the vehicle user the information corresponding to the update event (update schemes 4, 8).

[0030] As an example, the electronic device 120 is a device that controls various functions of the vehicle 100 and is called an ECU (Electronic Control Unit). The electronic device 120 stores one or more programs executed by a control unit (not shown) such as a CPU in a storage unit (not shown) such as a RAM. The electronic device 120 communicates with the vehicle management server 200 using the wireless communication function of the communication device 110. The electronic device 120 updates the currently stored program based on the update program received from the vehicle management server 200. In addition, not all of the electronic devices 120 in the vehicle 100 need to be devices capable of program updates in this way.

[0031] The display device 130 is an information terminal having a display screen for displaying information on update events related to the program update process in the electronic device 120. The display device 130 displays a prescribed notification or a permission request screen based on an instruction to display corresponding to an update event transmitted via the in - vehicle network from the electronic device 120 or an instruction to display corresponding to an update event transmitted via the wireless network from the vehicle management server 200. As the display device 130, a multi - information display or a vehicle navigation device mounted on the vehicle 100 can be exemplified.

[0032] The mobile device 300 is an information terminal having a display screen for receiving and displaying information on update events related to the program update process in the electronic device 120 via the communication device 110. The mobile device 300 displays a prescribed notification or a permission request screen based on an instruction to display corresponding to an update event transmitted via the wireless network from the electronic device 120 or an instruction to display corresponding to an update event transmitted via the wireless network from the vehicle management server 200. As the mobile device 300, general devices such as a smart phone, a tablet device, or a personal computer owned by the vehicle user of the vehicle 100 can be exemplified.

[0033] In addition, in Figure 1In the program update system 10, as an information terminal for displaying information on update events related to the program update process in the electronic device 120, although it structurally includes the display device 130 and the mobile device 300, it may also be the structure of only one of them. Additionally, as long as it can display the information on update events to prompt the vehicle user, it may also include a structure other than the display device 130 and the mobile device 300 as the information terminal. Moreover, the display instruction for the information on update events to the display device 130 and the mobile device 300 can be performed by the electronic device 120 implementing the update, or the vehicle management server 200 can appropriately receive the update status from the electronic device 120 implementing the update and perform it.

[0034] [Control]

[0035] Further refer to Figure 3 The processing performed by the vehicle management server 200 in the above-mentioned program update system 10 will be described. Figure 3 It is a flowchart showing the steps of the process of the control unit 230 of the vehicle management server 200 according to the present embodiment for selecting an update plan associated with the update program.

[0036] For example, regarding the update program stored in the storage unit 220 of the vehicle management server 200, if there is an inquiry from the vehicle 100 to the vehicle management server 200 about whether there is a program update, the Figure 3 processing shown will start.

[0037] Step S301: The control unit 230 of the vehicle management server 200 determines whether the update program of the vehicle 100 for which the inquiry exists is content that changes the control specification of the actuator equipped in the vehicle 100. If the update program is content that changes the control specification of the actuator (step S301, yes), the process proceeds to step S302. If the update program is not content that changes the control specification of the actuator (step S301, no), the process proceeds to step S307.

[0038] Step S302: The control unit 230 of the vehicle management server 200 determines whether automatic update has been set by the vehicle user in the vehicle 100. Information on whether automatic update has been set can be included in the inquiry about whether there is a program update and sent by the vehicle 100 to the vehicle management server 200, or can be obtained by the vehicle management server 200 requesting it from the vehicle 100 after receiving the inquiry. If automatic update has been set (step S302, yes), the process proceeds to step S306. If automatic update has not been set (step S302, no), the process proceeds to step S303.

[0039] Step S303: The control unit 230 of the vehicle management server 200 determines whether the update content of the update program is content for adding a new function to the vehicle. When the update content is a function addition (Step S303, Yes), the process proceeds to Step S304. When the update content is not a function addition (Step S303, No), the process proceeds to Step S305.

[0040] Step S304: The control unit 230 of the vehicle management server 200 selects an update plan according to the urgency of the update of the update program. In the present embodiment, one is selected from the update plans 1, 2, and 3 where the update event is "there is a notification and there is a permission request". By this selection, it is determined what content of at least one of the data DL permission request and the start permission request is to be presented to the vehicle user as the update status. If an update plan is selected, the update plan selected in this Step S304 is associated with the update program, and this process ends. Figure 2 Step S305: The control unit 230 of the vehicle management server 200 selects an update plan according to the urgency of the update of the update program. In the present embodiment, one is selected from the update plans 5, 6, and 7 where the update event is "there is a notification and there is no permission request". By this selection, it is determined that the content of neither the data DL permission request nor the start permission request is to be presented to the vehicle user as the update status. If an update plan is selected, the update plan selected in this Step S305 is associated with the update program, and this process ends.

[0041] Step S306: The control unit 230 of the vehicle management server 200 selects the update plan 4 or 8 where the update event is only "update start notification and update completion notification". By this selection, it is determined that only the update start notification and the update completion notification are to be presented to the vehicle user as the update status. If an update plan is selected, the update plan selected in this Step S306 is associated with the update program, and this process ends. Figure 2 Step S307: The control unit 230 of the vehicle management server 200 selects the update plan 9 where the update event is "no notification and no permission request". By this selection, it is determined that no notification and permission request are to be presented to the vehicle user as the update status. If an update plan is selected, the update plan selected in this Step S307 is associated with the update program, and this process ends.

[0042] Step S306: The control unit 230 of the vehicle management server 200 selects the update plan 4 or 8 where the update event is only "update start notification and update completion notification". By this selection, it is determined that only the update start notification and the update completion notification are to be presented to the vehicle user as the update status. If an update plan is selected, the update plan selected in this Step S306 is associated with the update program, and this process ends. Figure 2 Step S307: The control unit 230 of the vehicle management server 200 selects the update plan 9 where the update event is "no notification and no permission request". By this selection, it is determined that no notification and permission request are to be presented to the vehicle user as the update status. If an update plan is selected, the update plan selected in this Step S307 is associated with the update program, and this process ends.

[0043] Step S307: The control unit 230 of the vehicle management server 200 selects the update plan 9 where the update event is "no notification and no permission request". By this selection, it is determined that no notification and permission request are to be presented to the vehicle user as the update status. If an update plan is selected, the update plan selected in this Step S307 is associated with the update program, and this process ends. Figure 2 Step S307: The control unit 230 of the vehicle management server 200 selects the update plan 9 where the update event is "no notification and no permission request". By this selection, it is determined that no notification and permission request are to be presented to the vehicle user as the update status. If an update plan is selected, the update plan selected in this Step S307 is associated with the update program, and this process ends.

[0044] In the update process of the update program associated with the update plan, the vehicle management server 200 sends information related to the update status, which is used to prompt the vehicle user to make the display device 130 and / or the mobile device 300 display a display corresponding to the update event determined in the update plan associated with the update program, to the vehicle 100. For example, the vehicle management server 200 sends the update plan and the update program to the vehicle 100 together. The electronic device 120 that receives the update plan can make the display device 130 and / or, via the communication device 110 and the vehicle management server 200, make the mobile device 300 display notifications and / or permission requests in accordance with the provisions of the update plan as the update process of the update program progresses. Alternatively, the vehicle management server 200 can obtain the progress status of the update process of the update program from the electronic device 120 at any time, and via the communication device 110, make the display device 130 and / or make the mobile device 300 display notifications and / or permission requests in accordance with the progress in accordance with the provisions of the update plan.

[0045] In addition, in the present embodiment, an update plan is defined for the case of updating the existing program by downloading the update program from the vehicle management server 200 to the vehicle 100 through wireless communication. However, an update plan can also be further defined for the case of updating the existing program using an update program that needs to be updated at a repair shop such as a dealership. In such a case, since the update process is carried out by the staff of the repair shop, etc., it is generally not necessary for the vehicle user to grasp the progress status of the update process every time. Therefore, as the update plan, for example, only the update start notification or only the update completion notification can be defined as the update event.

[0046] In addition, in the present embodiment, the control unit 230 can select the update plan for the update program not only based on the characteristics of the update program but also based on the individual conditions of the vehicle such as the driving distance of the vehicle obtained from the vehicle and the manufacturing date of the components.

[0047] In addition, in the present embodiment, the control unit 230 can further control various displays based on the characteristics of the update program in association with or independently of the above-described update scheme. For example, when the update program is a program having characteristics as described in (1) to (3) below, the control unit 230 can acquire information indicating the characteristics from the vehicle management server 200 and display it on the information terminal (display device 130, mobile device 300). In this case, for example, it is desired that the information terminal (display device 130, mobile device 300) display the information in a manner that gives priority to notifying the user before the update process, so that the user can reliably recognize the information. (1) A program that is legally obligated to notify the user of the program update. (2) A program in which individual setting values in the vehicle such as the user's custom settings are reset and the impact on convenience is relatively large. (3) An update program that is relatively large in size and the required time for the update process is more than a certain time, and requires long-term parking in a garage or the like for the update process, and has a relatively large impact on convenience.

[0048] In addition, in the present embodiment, for example, in update schemes 4, 8, etc. of the update scheme, the update start notification may include a notification indicating that the update is forcibly executed regardless of the user's consent. In this case, for example, it is desired that the information terminal (display device 130, mobile device 300) display the information in a manner that gives priority to notifying the user, so that the user can reliably recognize the information. In addition, such a display for notifying the forced execution of the update process can be performed independently of the display for the update start notification.

[0049] [Function / Effect]

[0050] As described above, according to the program update system 10 according to an embodiment of the present disclosure technology, a plurality of update schemes that define the content of the update of the update program, update events (completion notification, permission request) displayed based on the urgency of the update, and the presence or absence of the automatic update setting of the vehicle user are pre-stored in the vehicle management server 200. Moreover, when updating the existing program of the update electronic device 120, information for causing the information terminal (display device 130, mobile device 300) to display a display related to the update state that prompts the vehicle user determined according to the type of the update program, that is, a display corresponding to the update event determined in the update scheme associated with the update program, is transmitted from the vehicle management server 200 to the vehicle 100.

[0051] Through this process, it is possible to appropriately set the update state displayed on the information terminals such as the display device 130 and the mobile device 300 according to the type of the update program and the like. Therefore, it is possible to reduce the irritation and anxiety felt by the vehicle user regarding the display of the update state during the update process of the program.

[0052] As described above, one embodiment of the disclosed technology has been described. However, the disclosed technology can be implemented not only as a program update system and a vehicle management server, but also as a method for sending an update program, a control program for the method, a computer-readable non-transitory storage medium storing the control program, a vehicle equipped with the program update system, and the like.

[0053] The disclosed technology is useful in a program update system for an electronic device mounted on a vehicle or the like and a vehicle management server included in the system.

Claims

1. A vehicle management server configured to send an update program for updating an existing program of an electronic device mounted on a vehicle to the vehicle, the vehicle management server comprises: a communication unit configured to communicate with the vehicle; and a control unit configured that when information indicating that a vehicle user has set permission for automatic update is received from the vehicle via the communication unit, and when the type of the update program is a type having content for improving an existing function of the vehicle: (i) send information to notify only the vehicle user of a start notification of an update process and a completion notification of the update process; and (ii) do not send information to notify the vehicle user of a permission request for executing the update process.

2. The vehicle management server according to claim 1, wherein the control unit is configured to determine information to be provided to the vehicle user based on the urgency of the update when information indicating that the vehicle user has set permission for automatic update is not received from the vehicle via the communication unit.

3. The vehicle management server according to claim 1, wherein the control unit is configured to determine information to be provided to the vehicle user based on the type of the update program when information indicating that the vehicle user has set permission for automatic update is not received from the vehicle via the communication unit.

4. The vehicle management server according to claim 3, wherein the type of the update program is determined according to the update content and the urgency of the update.

5. The vehicle management server according to claim 4, wherein the update content includes content for changing a control specification of an actuator of the vehicle and content for not changing the control specification of the actuator of the vehicle.

6. The vehicle management server according to claim 5, wherein the content for changing the control specification of the actuator of the vehicle is classified into: content for adding a new function not previously mounted on the vehicle and requiring permission of the vehicle user for the update at the time of update; and content for improving an existing function already mounted on the vehicle, adding measures and countermeasures for the existing function, and not requiring permission of the vehicle user for the update at the time of update.

7. The vehicle management server according to claim 2, wherein the urgency of the update is classified into at least two groups according to the content of the update program.

8. The vehicle management server according to claim 1, wherein the type of the update program is a type having content for changing a control specification of an actuator of the vehicle.

9. The vehicle management server according to claim 1, wherein the type of the update program is a type having content for not changing a control specification of an actuator of the vehicle.

10. A vehicle management system, comprises: a user terminal configured to display information; and a vehicle management server configured to send an update program for updating an existing program of an electronic device mounted on a vehicle to the vehicle, the vehicle management server comprising: A communication unit configured to communicate with the vehicle; and A control unit configured to, when information indicating that the vehicle user has set permission for automatic update is received from the vehicle via the communication unit, and when the type of the update program is a type having content that improves the existing functions of the vehicle: (i) Send information to notify the vehicle user of the start notification and the completion notification of the update process only via the user terminal; and (ii) Do not send information to notify the vehicle user of the permission request for executing the update process via the user terminal.

11. The vehicle management system according to claim 10, wherein, The control unit is configured to determine the information to be provided to the vehicle user based on the urgency of the update when information indicating that the vehicle user has set permission for automatic update is not received from the vehicle via the communication unit.

12. The vehicle management system according to claim 10, wherein, The control unit is configured to determine the information to be provided to the vehicle user based on the type of the update program when information indicating that the vehicle user has set permission for automatic update is not received from the vehicle via the communication unit.

13. The vehicle management system according to claim 12, wherein, The type of the update program is determined according to the update content and the urgency of the update.

14. The vehicle management system according to claim 13, wherein, The update content includes content for changing the control specifications of the actuators of the vehicle and content for not changing the control specifications of the actuators of the vehicle.

15. The vehicle management system according to claim 14, wherein, The content for changing the control specifications of the actuators of the vehicle is classified as: Content for adding new functions not previously installed on the vehicle and requiring the vehicle user to permit the update during the update; and Content for improving the existing functions already installed on the vehicle, adding measures and countermeasures for the existing functions, and not requiring the vehicle user to permit the update during the update.

16. The vehicle management system according to claim 11, wherein, The urgency of the update is classified into at least two groups according to the content of the update program.

17. The vehicle management system according to claim 10, wherein, The user terminal is a multi-information display connected to the control unit via a controller area network.

18. The vehicle management system according to claim 10, wherein, The user terminal is a mobile device.

19. The vehicle management system according to claim 10, wherein, The type of the update program is a type having content for changing the control specifications of the actuators of the vehicle.

20. The vehicle management system according to claim 10, wherein, The type of the update program is a type having content for not changing the control specifications of the actuators of the vehicle.

Images