Control device, vehicle, control method, program, and non-transitory computer-readable storage medium

Abstract

This invention relates to a control device, a vehicle, a control method, a program, and a non-transitory computer-readable storage medium. The control device controls a display unit that displays information related to software updates of onboard equipment installed in a vehicle having multiple power modes. The software update includes an activation process. When performing a software update in a first update step that implements activation processing by switching between multiple power modes according to a first switching type, the control device displays a first confirmation image on the display unit before the activation process begins. When performing a software update in a second update step that implements activation processing by switching between multiple power modes according to a second switching type, the control device displays a second confirmation image on the display unit before the activation process begins.

Description

Technical Field

[0001] This disclosure relates to a control device for displaying information related to software updates of in-vehicle equipment. Furthermore, this disclosure relates to vehicles, control methods, programs, and non-transitory computer-readable storage media related to this display control. Background Technology

[0002] Vehicles are equipped with various in-vehicle devices that operate through software execution. An OTA (Over-The-Air) technology is known that updates the software of in-vehicle devices by downloading software from outside the vehicle via wireless communication. As described in Patent Document 1, the software update is performed through an installation process that writes the downloaded update software into the storage module of the in-vehicle device, and an activation process that makes the installed update software effective.

[0003] Patent Document 1: Japanese Patent Application Publication No. 2022-163396

[0004] Since some vehicle functions are sometimes restricted during activation, it is desirable to confirm with the user before starting the activation process. On the other hand, it is possible to implement the activation process at different times depending on the type of in-vehicle device and software. In such cases, the timing of the vehicle's functional restrictions changes depending on the timing of the activation process. Therefore, it is desirable to display an appropriate confirmation screen corresponding to the timing of the activation process. Summary of the Invention

[0005] According to one aspect of this disclosure, a control device is provided. The control device includes a processing circuit configured to control a display unit that displays information related to software updates of an in-vehicle device installed in a vehicle. The vehicle is configured to selectively switch between multiple power modes. The software update includes an activation process that activates the updated software installed in the in-vehicle device. When the software update is performed in a first update step, the processing circuit is configured to display a first confirmation image on the display unit before the start of the activation process. The first update step is a step that performs the activation process based on switching between the multiple power modes under a first switching type. When the software update is performed in a second update step, the processing circuit is configured to display a second confirmation image on the display unit before the start of the activation process. The second update step is a step that performs the activation process based on switching between the multiple power modes under a second switching type. The first switching type and the second switching type are different from each other, and the first confirmation image and the second confirmation image are different from each other.

[0006] According to one aspect of this disclosure, a vehicle equipped with the aforementioned control device is provided.

[0007] According to one aspect of this disclosure, a control method is provided. The control method includes: controlling a display unit that displays progress information of a software update for an on-board device installed in a vehicle, the vehicle being configured to selectively switch to any one of multiple power modes, the software update including an activation process that activates the updated software installed in the on-board device; when the software update is performed in a first update step that performs the activation process by switching between the multiple power modes according to a first switching type, displaying a first confirmation image on the display unit before the start of the activation process; and when the software update is performed in a second update step that performs the activation process by switching between the multiple power modes according to a second switching type, displaying a second confirmation image on the display unit before the start of the activation process, the first switching type and the second switching type being different from each other, and the first confirmation image and the second confirmation image being different from each other.

[0008] According to one aspect of this disclosure, a program is provided. When executed by a control device, the control device performs: a control process that controls a display unit displaying progress information of a software update for an on-board device mounted in a vehicle, the vehicle being configured to selectively switch to any one of multiple power modes, the software update including an activation process that validates the updated software installed in the on-board device; a first display process that, when the software update is performed using a first update step that performs the activation process by switching between the multiple power modes according to a first switching type, displays a first confirmation image on the display unit before the start of the activation process; and a second display process that, when the software update is performed using a second update step that performs the activation process by switching between the multiple power modes according to a second switching type, displays a second confirmation image on the display unit before the start of the activation process, the first switching type and the second switching type being different from each other, and the first confirmation image and the second confirmation image being different from each other.

[0009] According to one aspect of this disclosure, a non-transitory computer-readable storage medium storing the above-described program can be provided. Attached Figure Description

[0010] Figure 1 This is a schematic diagram illustrating the configuration of the control device and the vehicle according to the first embodiment.

[0011] Figure 2 This is a schematic diagram illustrating the configuration of an in-vehicle device equipped with a Single Bank storage module.

[0012] Figure 3 This is a schematic diagram illustrating the configuration of an in-vehicle device equipped with a dual-bank storage module.

[0013] Figure 4 This is a timing diagram illustrating the process flow of the activation phase in the case of a software update performed in the first update step according to the first embodiment.

[0014] Figure 5 This is a diagram showing an example of a first pre-confirmed image.

[0015] Figure 6 This is a diagram showing an example of the first final confirmed image.

[0016] Figure 7 This is a diagram showing an example of the display of the first guide image.

[0017] Figure 8 This is a diagram showing an example of the display of the first completion notification image.

[0018] Figure 9 This is a timing diagram illustrating the process flow of the activation phase in the case of software update performed in the second update step in the first embodiment.

[0019] Figure 10 This is a diagram showing an example of a second pre-confirmed image.

[0020] Figure 11 This is a diagram showing an example of a second, final confirmed image.

[0021] Figure 12 This is a diagram showing an example of a second guide image.

[0022] Figure 13 This is a diagram showing an example of the display of the second completion notification image.

[0023] Figure 14 This is a timing diagram illustrating the process flow of the activation phase in the second embodiment when a software update is performed using the first update step.

[0024] Figure 15 This is a timing diagram illustrating the process flow of the activation phase in the second embodiment when the software is updated using the second update step. Detailed Implementation

[0025] (First Implementation)

[0026] The following is for reference Figures 1 to 13A first embodiment of the control device, a vehicle equipped with the control device, a control method, a program (program product), and a non-transitory computer-readable storage medium will be described in detail. Here, the control method refers to a method executed by the control device. The program causes the control device to execute the control method. The non-transitory computer-readable storage medium stores the program.

[0027] <Control device and vehicle composition>

[0028] First, refer to Figure 1 The control device and vehicle configuration of this embodiment will be described. Figure 1As shown, vehicle 10 is equipped with in-vehicle devices such as an OTA (Over-The-Air) manager 11, a DCM (Data Communication Module) 12, an ADAS (Advanced Driving Assistant System) 13, a PCU (Power Control Unit) 14, an engine ECU (Electronic Control Unit) 15, a transmission ECU 16, a brake ECU 17, and an HMI (Human Machine Interface) 18. These in-vehicle devices are connected to each other via an in-vehicle network 19 in a manner that enables them to communicate with each other. The OTA manager 11 is responsible for managing software updates for its own in-vehicle devices. The DCM 12 is a data communication module that provides wireless communication with the outside world via a mobile communication network 20. In this embodiment, the DCM 12 is responsible for recording the self-diagnostic results performed by each in-vehicle device of vehicle 10 and sending them to an external data center, etc. The ADAS 13 is an advanced driving assistance system that provides advanced driving assistance functions such as automatic braking devices and emergency start prevention devices. PCU14 is the Power Control Unit for in-vehicle electrical control. Engine ECU15 is the Electronic Control Unit for engine control. Transmission ECU16 is the Electronic Control Unit for transmission control. Brake ECU17 is the Electronic Control Unit for brake control. HMI18 is the Human Machine Interface. HMI18 has input devices for receiving occupant inputs and display devices for displaying information to occupants via images and voice. HMI18 can also be configured to provide navigation functions for guiding driving routes and entertainment functions for playing music and videos. These in-vehicle devices each have a storage module 21 storing software and a processor 22 for executing the software. OTA Manager 11 also has a data storage unit 23 for storing updated software obtained from outside the vehicle.

[0029] Vehicle 10 has multiple power modes. These power modes include a driving power mode and a parking power mode. Each power mode specifies which on-board equipment is powered on. When the driving power mode is set, the on-board equipment required for driving and providing services while in motion is powered on. In this embodiment, when the driving power mode is set... Figure 1 All the vehicle-mounted devices shown are powered on. In the parking power mode setting, only the vehicle-mounted devices that need to operate while the vehicle 10 is parked are powered on. The vehicle-mounted devices powered on in each power mode can be changed according to the environment and user settings.

[0030] The vehicle 10 is equipped with a power switch 24 for switching between the power mode for driving and the power mode for parking. Switching from the driving power mode to the parking power mode is performed by switching the power switch 24 from on to off. Switching from the parking power mode to the driving power mode is performed by switching the power switch 24 from off to on. In conventional vehicles that use only the engine as a power source, the power switch 24 is sometimes referred to as the ignition switch. Additionally, in vehicles capable of electric driving, such as BEVs (Battery Electric Vehicles) and PHEVs (Plug-in Hybrid Electric Vehicles), the power switch 24 is sometimes referred to as the ready switch.

[0031] Vehicle 10 is connected to OTA server 30 via mobile communication network 20. OTA server 30 is a server device for distributing update software for on-board equipment. OTA server 30 has a storage device 31 for storing programs for distributing update software, data, and a processor 32 for executing the distribution program.

[0032] The OTA server 30 can communicate with the user's information terminal 40 of the vehicle 10 via the mobile communication network 20. Examples of the information terminal 40 include smartphones. The information terminal 40 can also be a tablet or PC. The information terminal 40 includes a storage device 41, a processor 42, and an HMI 43. The processor 42 reads and executes the software stored in the storage device 41. The HMI 43 includes an input device for accepting user operations and a display device for displaying information to the user. The software stored in the storage device 41 includes software that provides functions such as information confirmation and remote operation of the user's vehicle 10.

[0033] <Summary of Software Updates>

[0034] Next, an overview of the software updates for the in-vehicle equipment in vehicle 10 will be provided. The in-vehicle equipment subject to software updates includes the OTA manager 11, DCM 12, ADAS 13, PCU 14, engine ECU 15, transmission ECU 16, brake ECU 17, and HMI 18. Software updates are performed through a download phase, an installation phase, and an activation phase.

[0035] During the download phase, the update software from the OTA server 30 is sent to the vehicle 10. The OTA manager 11 stores the update software received from the OTA server 30 into the data storage 23. The download phase includes a series of download-related processes such as determining whether the download can be executed and verifying the update data. The update software can be sent from the OTA server 30 to the OTA manager 11 by sending compressed data containing the update software, or by sending segmented data containing the update software or compressed data. Alternatively, update software from multiple vehicle devices can be aggregated and sent together.

[0036] During the installation phase, the update software is installed on the target vehicle device. In this phase, the OTA manager 11 installs the update software onto the storage module 21 of the target vehicle device based on the update data downloaded to the data storage 23. The installation phase includes a series of installation-related processes such as determining whether installation can be performed, transmitting update data, and verifying the update software. If the update data includes the update software itself, the OTA manager 11 transmits the update data to the target vehicle device during the installation phase. If the update data includes compressed, differential, or segmented data of the update software, processing is performed to generate the update software based on the update data. This generation process can be performed by the OTA manager 11 or by the target vehicle device. The update software can be generated by decompressing compressed data and assembling differential or segmented data. Upon completion of the installation phase, the update software is invalidated.

[0037] During the activation phase, the updated software is activated in the on-board equipment of the target device, i.e., the updated software is made valid. The activation phase includes a series of processes related to activation, such as determining whether activation can be performed, checking the compatibility of the updated software, and verifying the activation results.

[0038] <Two software update steps>

[0039] The software update process for in-vehicle devices involves two steps: a first update step and a second update step. Regardless of whether it's the first or second update step, the software update is performed using the same steps before the installation phase is completed. The timing of the activation process at the start of the activation phase differs between the first and second update steps. The activation process is the process of validating the updated software installed on the storage module 21 of the in-vehicle device being updated.

[0040] In the case of the first update step, activation is performed based on switching the power switch 24 from on to off. That is, in the first update step, activation is performed based on switching from a driving power mode to a parking power mode. When the software update is performed in the first update step, switching the power switch 24 to on again is prohibited from the start to the completion of the activation process. In other words, when the software update is performed in the first update step, switching to a driving power mode is prohibited from the start to the completion of the activation process.

[0041] In contrast, in the second update step, activation is performed based on the switching of the power switch 24 from off to on. That is, in the second update step, activation is performed based on the switching from a parking power mode to a driving power mode. Specifically, in the second update step, activation begins when the power switch 24 switches from off to on. Then, after the activation process is completed, the power mode is switched from a parking power mode to a driving power mode.

[0042] For example, the software update process can be categorized based on the type of in-vehicle device, its hardware configuration, and the type of software. Alternatively, the choice between the first and second update steps can be determined based on environmental conditions, user settings, and the combination of other in-vehicle devices undergoing activation simultaneously.

[0043] When a software update is performed using the first update step, power needs to be supplied to the on-board equipment undergoing activation even when the vehicle 10 is parked. Therefore, a dedicated power cable is required to connect the on-board equipment undergoing the software update using the first update step for power supply even when parked. In contrast, by performing the software update of the on-board equipment using the second update step, the necessity of a dedicated power cable can be eliminated.

[0044] However, some in-vehicle devices may prefer the first update step over the second update step. In the case of the first update step, the activation process is completed when the power switch 24 is switched on again after being switched off. Therefore, in this case, the in-vehicle device to be updated can start operating immediately after the power switch 24 is switched on. In contrast, in the case of the second update step, the activation process begins after the power switch 24 is switched on. Therefore, even if the user switches the power switch 24 on to start driving the vehicle 10, the in-vehicle device to be updated cannot start operating until the activation process is completed. In contrast, by performing a software update for the in-vehicle device in the first update step, the in-vehicle device can start operating immediately after the power switch 24 of the vehicle 10 is switched on.

[0045] In this embodiment, DCM12, ADAS13, and PCU14 are classified as vehicle-mounted devices that undergo software updates in the first update step. The communication function provided by DCM12 is used to notify external parties of any anomalies occurring in vehicle 10. Furthermore, in this embodiment, DCM12 is responsible for recording the self-diagnostic results of each vehicle-mounted device. It is desirable that the functions of DCM12, such as anomaly notification and self-diagnostic result recording, can be used immediately after the power switch 24 is switched from off to on. Additionally, ADAS13 needs to provide driving assistance from the moment vehicle 10 begins to move. Furthermore, since power cannot be supplied to the drive system during the period when PCU14 is not operating, vehicle 10 cannot begin to move. Therefore, DCM12, ADAS13, and PCU14 are required to be vehicle-mounted devices that begin operation immediately after the power switch 24 is switched from off to on.

[0046] Additionally, software updates via a first update step are sometimes required depending on the hardware configuration of the storage module 21 installed in the vehicle-mounted device. In this embodiment, vehicle-mounted devices equipped with a single-database storage module 21, other than the DCM12, ADAS13, and PCU14, are classified as vehicle-mounted devices undergoing software updates via the first update step. Furthermore, vehicle-mounted devices equipped with a dual-database storage module 21, other than the DCM12, ADAS13, and PCU14, are classified as vehicle-mounted devices undergoing software updates via a second update step.

[0047] Figure 2 The diagram shows the configuration of an in-vehicle device D1 equipped with a single-library storage module 21A. This in-vehicle device D1's storage module 21A has only one storage area B for storing software executed by the processor 32. In this case, the updated software is installed in the same storage area B as the storage area B where the previous software was stored. Therefore, the operation of the in-vehicle device D1 needs to be stopped during the installation process. Furthermore, recovery in the event of activation failure requires reinstalling the previous software in storage area B. Such reinstallation for recovery takes a long time. Also, if the previous software has not been backed up, it needs to be re-downloaded. Thus, in the case of the in-vehicle device D1 equipped with a single-library storage module 21A, considering recovery in case of failure, there is a possibility that it will take a very long time from the start of activation to the point where operation can begin. Therefore, in this embodiment, the in-vehicle device D1 equipped with a single-library storage module 21A performs a software update in a first update step. In addition, in this embodiment, the on-board device that performs software updates in the first update step switches the power on / off in conjunction with the power switch 24 of the vehicle 10.

[0048] Figure 3 The configuration of an in-vehicle device D2 equipped with a dual-library storage module 21B is shown. The dual-library storage module 21B has two storage areas B1 and B2. One of the two storage areas B1 and B2 is invalidated, and the other is validated. The processor 22 reads software from the validated storage area and executes it. In this case of the in-vehicle device D2, the updated software is installed in the invalidated storage area, that is, a storage area different from the storage area storing the software before the update. Moreover, after installation, activation is performed by switching the validated storage area. In the event of activation failure, the state before the update can be restored in a short time by switching the validated storage area again. Therefore, in the case of the in-vehicle device D2 equipped with the dual-library storage module 21B, even considering recovery in case of failure, the time from the start of activation to the ability to start operation is not too long. Therefore, in this embodiment, the software update based on the second update step is limited to the in-vehicle device D2 equipped with the dual-library storage module 21B.

[0049] Sometimes, multiple software programs providing different functions are installed in various in-vehicle devices. Furthermore, these multiple software programs sometimes include software that needs to execute immediately after the power switch 24 is switched from off to on, and software that does not need to execute immediately. In the case of software that needs to execute immediately after the power switch 24 is switched from off to on, if the update is performed in the second update step, execution may not be timely. Therefore, even for the same in-vehicle device, the update method (first update step or second update step) can be distinguished based on the type of software to be updated.

[0050] The OTA manager 11 determines, at least before the start of the activation phase, whether to perform a software update using the first update step or the second update step. For example, the OTA manager 11 makes this determination based on activity information. In this case, the activity information includes information indicating whether the software update step is the first or the second update step. Alternatively, the determination can be performed as follows: First, classification information regarding the types of vehicle devices and software updated using the first update step and the types of vehicle devices and software updated using the second update step is pre-stored in the storage module 21 of the OTA manager 11. During a software update, the OTA manager 11 retrieves the types of vehicle devices and software to be updated from the activity information or the vehicle devices to be updated. Then, the OTA manager 11 refers to the classification information stored in the storage module 21 to determine which update step the retrieved type is classified as for software updates.

[0051] <Activation process under the first update step>

[0052] Next, refer to Figures 4-8 The details of the activation process under the first update step are explained below. The storage module 21 of the OTA manager 11 stores programs for managing software updates and programs for displaying and controlling information related to software updates. Figure 4 And the following Figure 9 The processing of the OTA manager 11 shown is performed by reading these programs into the processor 22 of the OTA manager 11 and executing them.

[0053] Figure 4 This illustrates the process flow of the activation phase in the case of a software update performed in the first update step. If the installation phase is complete, the OTA manager 11 instructs the HMI 18 to display a first pre-confirmation image to confirm the execution of the activation process to the user (S10). The HMI 18 displays the image according to the instruction. Figure 5 The first pre-confirmation image as illustrated (S11).

[0054] Figure 5 The image shows an example of a first pre-confirmation image. The first pre-confirmation image includes a display indicating whether an activation process can be performed. Specifically, the first pre-confirmation image displays buttons for selecting to allow the activation process and for selecting to postpone the activation process. These buttons are disabled while the vehicle 10 is in motion and are only enabled when the vehicle is parked.

[0055] Additionally, the first pre-confirmation image displays information about functional limitations of the vehicle 10 accompanying the activation process. Specifically, during the activation process, the inability to switch the power switch 24 back to the ON position is displayed as a functional limitation. This functional limitation indicates that the vehicle cannot switch to the driving power mode. Furthermore, the first pre-confirmation image displays information about the estimated time of the activation process. This estimated time is the estimated value of the time required from when the power switch 24 is switched from ON to OFF until the activation process is completed and the power switch 24 can be switched back to ON. The OTA manager 11 obtains the estimated time, for example, based on activity information. Alternatively, the OTA manager 11 may calculate the estimated time based on the data size of the updated software, the type of vehicle equipment being updated, etc.

[0056] The first pre-confirmation image also displays information such as reminders to the user corresponding to the execution of the activation process. Such reminders may include, for example, that the power switch 24 needs to be turned off for software updates, activation should be performed in a safe location, and that some functions of the vehicle 10 are disabled when the power switch 24 is turned on again.

[0057] If the user selects to allow activation processing in the HMI 18 displaying the first pre-confirmation image (S12), the HMI 18 notifies the OTA manager 11 that activation processing is permitted (S13). If the OTA manager 11 confirms permission for activation processing, it instructs the HMI 18 to display the first final confirmation image when the power switch 24 can be switched from on to off (S14). The HMI 18 displays the image according to the instruction. Figure 6 The first final confirmation image shown is S15. The OTA manager 11 determines, for example, that the vehicle 10 is stopped, the parking gear is being operated, and the parking brake is engaged, that it is in a state where the power switch 24 can be switched from on to off.

[0058] Figure 6 The following shows an example of the first final confirmation image. Similar to the first preliminary confirmation image, the first final confirmation image displays information regarding the functional limitations of the vehicle 10 accompanying the activation process. Specifically, the first final confirmation image displays information indicating that if the power switch 24 is switched off, the vehicle 10 cannot be driven by switching the power switch 24 back on until the activation process is complete. Additionally, the first final confirmation image displays information about the estimated time for the activation process. The first final confirmation image also displays information indicating that if the power switch 24 is switched off after confirming a safe position, driving can resume, and in this case, the software update will restart based on the display of the first final confirmation image at the next stop. Furthermore, the first final confirmation image also displays an acceptance display for temporarily suspending the software update. The activation phase continues if the user does not select to temporarily suspend the software update in the first final confirmation image. On the other hand, if the user selects to temporarily suspend the software update in the first final confirmation image, the activation phase is temporarily suspended. Moreover, the activation phase restarts when the power to the vehicle 10 can be switched off.

[0059] If, during the continued activation process, the user subsequently switches the power switch 24 from on to off (S16), the OTA manager 11 begins activation processing (S17). Simultaneously, the OTA manager 11 instructs the HMI 18 to perform... Figure 7 The first boot image is displayed as illustrated (S18). The HMI18 displays the first boot image according to the instruction (S19).

[0060] like Figure 7As shown, the first boot image displays information indicating that the power switch 24 cannot be switched on, and an estimated time until the power switch 24 can be switched on. The OTA manager 11 calculates the estimated time for displaying the information in the first boot image by subtracting the elapsed time from the start of the activation process from the predicted time required from the start to the completion of the activation process. The HMI 18 temporarily turns off the screen based on the locking of the vehicle 10 or the elapsed time, but displays the first boot image again based on the unlocking of the vehicle 10 or the operation of the HMI 18.

[0061] If the activation process is complete, OTA Manager 11 instructs HMI 18 to proceed. Figure 8 The first completion notification image is displayed as illustrated (S20). The HMI18 displays the first completion notification image according to the instruction (S21). For example... Figure 8 As shown, the first completion notification image displays information indicating that the software update is complete and information indicating that the power switch 24 can be switched on.

[0062] <Activation process under the second update step>

[0063] Next, refer to Figures 9-11 The details of the activation process under the second update step are explained. Figure 9 The diagram illustrates the process flow for the activation phase in the case of a software update performed in the second update step.

[0064] In this case, when the installation phase is complete, the OTA manager 11 instructs the HMI 18 to display a second pre-confirmation image to confirm the execution of the activation process to the user (S30). The HMI 18 displays the image according to the instruction. Figure 10 The second pre-confirmation image as illustrated (S31).

[0065] Figure 10 The image shows an example of a second pre-confirmation image. Like the first pre-confirmation image, the second pre-confirmation image includes a display indicating whether an activation process can be performed. Furthermore, the second pre-confirmation image shows that the activation process will proceed when the power switch 24 is switched to the on position. The second pre-confirmation image also displays information about the estimated time from when the power switch 24 is switched from off to on until the activation process is completed.

[0066] If the user selects "permission allowed" for the activation process in the HMI 18 displaying the second pre-confirmation image (S32), the HMI 18 notifies the OTA manager 11 that the activation process is permitted (S33). If the OTA manager 11 confirms that the activation process is permitted, it instructs the HMI 18 to display the second final confirmation image when the vehicle 10 subsequently becomes capable of switching its power from on to off (S34). The HMI 18 displays the image according to the instruction. Figure 11 The second final confirmation image as illustrated (S35).

[0067] Figure 11 The image shown is an example of a second final confirmation image. The second final confirmation image displays information indicating that the activation process is complete, and information indicating that the software update will restart when the power switch 24 is switched from off to on.

[0068] Subsequently, if the power switch 24 switches from on to off and then back to on, the OTA manager 11 begins activation processing (S36). In addition, the OTA manager 11 instructs the HMI 18 to perform... Figure 12 The second boot image is displayed as illustrated (S37). HMI18 displays the second boot image according to the instruction (S38).

[0069] like Figure 12 As shown, the second boot image displays information indicating that a software update is in progress, and the estimated time until the update is completed. The OTA manager 11 calculates the estimated time for the information displayed in the second boot image by subtracting the elapsed time from the start of the activation process to the present from the predicted time required from the start to the completion of the activation process.

[0070] If the activation process is complete, OTA Manager 11 instructs HMI 18 to proceed. Figure 13 The second completion notification image is displayed as illustrated (S39). HMI18 displays the second completion notification image according to the instruction (S40). For example... Figure 13 As shown, the second completion notification image displays information indicating that the software update is complete. Additionally, the second completion notification image displays information indicating that functional restrictions accompanying the activation process have been lifted. For example, if the vehicle 10 was prohibited from driving during the activation process, the second completion notification image displays information indicating that the vehicle 10 is now capable of driving.

[0071] <The role and effects of the implementation method>

[0072] The OTA manager 11 controls the display of the HMI 18, which displays information related to software updates of the in-vehicle equipment installed in the vehicle 10. The software update of the in-vehicle equipment is performed in either a first update step or a second update step. In the first update step, an activation process is performed to activate the updated software installed in the in-vehicle equipment by switching from a power mode for driving to a power mode for parking. In the second update step, an activation process is performed by switching from a power mode for parking to a power mode for driving. When performing a software update in the first update step, the OTA manager 11 displays a first pre-confirmation image and a first final confirmation image on the HMI 18 before the activation process begins. Conversely, when performing a software update in the second update step, the OTA manager 11 displays a second pre-confirmation image and a second final confirmation image that are different from the first pre-confirmation image and the first final confirmation image before the activation process begins.

[0073] In the cases where a software update is performed using the first update step and the software update is performed using the second update step, the timing and content of the functional restrictions imposed on vehicle 10 during the activation process differ. Therefore, if the user is only informed of the activation process in advance, unexpected functional restrictions may occur, causing confusion for the user. In this embodiment, the user can determine whether the software update is performed using the first or second update step based on the difference in the confirmation image displayed on HMI 18 before the start of the activation process.

[0074] The control device, vehicle, control method, program, and non-transitory computer-readable storage medium according to the above embodiments can achieve the following effects.

[0075] (1) When the software update is performed in the first update step and in the second update step, the confirmation image displayed on the HMI18 before the start of the activation process is different. Therefore, this embodiment has the effect of being able to display an appropriate confirmation screen corresponding to the execution timing of the activation process.

[0076] (2) Users can determine whether to perform activation processing based on the confirmed implementation time. Therefore, user convenience is improved.

[0077] (3) If the timing of the activation process is different, the timing and content of the functional limitations of the vehicle 10 accompanying the activation process will be different. In this regard, the OTA manager 11 displays information about the functional limitations of the vehicle 10 accompanying the activation process in the first advance / final confirmation image. In addition, the OTA manager 11 displays information that is different from the information displayed in the first advance / final confirmation image as functional limitation information in the second advance / final confirmation image. Therefore, the functional limitations of the vehicle 10 accompanying the activation process can be accurately notified to the user.

[0078] (4) The OTA manager 11 displays information about the period during which the function of the vehicle 10 is restricted during the activation process in the first pre-confirmation / final confirmation image. Additionally, the OTA manager 11 displays information about a period different from the period displayed in the first pre-confirmation / final confirmation image as information about the period during which the function of the vehicle 10 is restricted in the second pre-confirmation image. Therefore, it is possible to accurately notify the user of the period during which the function of the vehicle 10 is restricted during the activation process.

[0079] (5) The OTA manager 11 displays information about the estimated time from when the power switch 24 is switched on to when it is switched off until it can be switched on again in the first pre- / final confirmation image. Therefore, the user can determine whether to perform the activation process based on the confirmation of the period during which the power switch 24 cannot be turned on due to the implementation of the activation process.

[0080] (6) The OTA manager 11 displays information about the estimated time from when the power switch 24 is switched from off to on until the activation process is completed in the second pre-confirmation image. Therefore, when the user drives the vehicle 10 next, he / she can determine whether to perform the activation process based on the confirmation of the period during which the function is limited due to the activation process.

[0081] (7) The first pre-confirmation / final confirmation image and the second pre-confirmation image contain an acceptance display of the selection operation to allow the start of the activation process. Therefore, the user can determine whether to perform the activation process while confirming the timing of the activation process, the content of the functional restrictions that are implemented, and the timing.

[0082] (8) The functional limitations of the vehicle 10 caused by the activation process in the first update step and the activation process in the second update step are different. Therefore, there is a situation where the user only knows that the activation process is in progress but cannot grasp the situation. In this regard, when the OTA manager 11 performs a software update in the first update step, it displays a first boot image on the HMI 18 during the activation process. In addition, when the OTA manager 11 performs a software update in the second update step, it displays a second boot image on the HMI 18 that is different from the first boot image during the activation process. Therefore, the user can easily grasp the impact of the activation process.

[0083] (9) The OTA manager 11 displays information indicating that the power switch 24 cannot be switched to the on position, i.e., the power mode for driving cannot be switched, in the first boot image. Furthermore, the OTA manager 11 displays information about the estimated time until the power switch 24 can be switched to the on position in the first boot image. This makes it easier for the user to understand the situation.

[0084] (10) The OTA manager 11 displays information about the estimated time until the activation process is complete within the second boot image. Thus, the user can know when the software update function can be used.

[0085] (11) The functions of the vehicle 10 that are restricted and de-restricted differ depending on whether the software update is performed using the first update step or the second update step. In the case of a software update using the first update step, the OTA manager 11 displays a first completion notification image on the HMI 18 after the activation process is completed. Conversely, in the case of a software update using the second update step, the OTA manager 11 displays a second completion notification image on the HMI 18 after the activation process is completed, which is different from the first completion notification image. Specifically, the OTA manager 11 displays the first completion notification image indicating that the power switch 24 can be switched on, while the second completion notification image indicates that the functions of the in-vehicle equipment that were restricted during the activation process can be used. Therefore, the user can easily understand the functions of the vehicle 10 that are restricted and de-restricted based on the completion of the activation process.

[0086] (12) DCM12, ADAS13, and PCU14 are required to start operating immediately after the power switch 24 is switched from off to on. In this embodiment, the software update of DCM12, ADAS13, and PCU14 is performed in a first update step, which is activated during the period when the power switch 24 is off. Therefore, it is possible to avoid the situation where the time from the power switch 24 being switched from off to on until DCM12, ADAS13, and PCU14 start operating is prolonged due to the activation process. Thus, in this embodiment, the vehicle devices that are updated with software in the first update step and the vehicle devices that are updated with software in the second update step are classified according to the function of the vehicle devices.

[0087] (13) The activation process of the vehicle-mounted device D1 with a single-database storage module 21A takes longer than that of the vehicle-mounted device D2 with a dual-database storage module 21B. Therefore, if the activation process begins after the power switch 24 is switched from off to on, the functions of the vehicle-mounted device D1 may be unavailable for a long period of time until it is completed. In this embodiment, the vehicle-mounted device D1 with a single-database storage module 21A, other than the DCM12, ADAS13, and PCU14, undergoes a software update in the first update step. In contrast, the vehicle-mounted device D2 with a dual-database storage module 21B, other than the aforementioned vehicle-mounted devices, undergoes a software update in the second update step. Therefore, the situation where the functionality of the vehicle-mounted device is limited for a long time after the power switch 24 is switched from off to on due to the implementation of the activation process can be avoided.

[0088] (14) When the OTA manager 11 performs a software update in the first update step, the activation process of the vehicle device is initiated by switching the power switch 24 from on to off. Similarly, when the OTA manager 11 performs a software update in the second update step, the activation process of the vehicle device is initiated by switching the power switch 24 from off to on. Thus, in this embodiment, the OTA manager 11, which manages the software update, controls the display of information. Therefore, it is possible to accurately display information corresponding to the progress of the software update.

[0089] (15) When the installation phase is completed, the OTA manager 11 displays the first pre-confirmation / second confirmation image on the HMI 18. Furthermore, the OTA manager 11 displays the first / second final confirmation image on the HMI 18 when the vehicle 10 is subsequently able to switch the power switch 24 from on to off. Therefore, the user can easily confirm that activation processing will be performed subsequently.

[0090] <Correspondence>

[0091] In this embodiment, the first pre-confirmation image and the first final confirmation image correspond to the first confirmation image, and the second pre-confirmation image and the second final confirmation image correspond to the second confirmation image. Furthermore, in this embodiment, the HMI 18 installed in the vehicle 10 corresponds to the display unit, and the OTA manager 11 mounted in the vehicle 10 corresponds to the control device.

[0092] Furthermore, in this embodiment, the power mode for driving corresponds to the first power mode and the power mode that enables the vehicle 10 to drive. The power mode for parking corresponds to the second power mode and the power mode that prevents the vehicle 10 from driving. Moreover, the switching from the power mode for driving to the power mode for parking corresponds to a switching of the first switching type of power mode, and the switching from the power mode for parking to the power mode for driving corresponds to a switching of the second switching type of power mode. Figure 4 The processes S10 and S14 correspond to the first display process of displaying a first confirmation image on the display unit before the activation process begins. The process S18 corresponds to the third display process of displaying a first guide image on the display unit during the implementation of the activation process. The process S20 corresponds to the fifth display process of displaying a first completion notification image on the display unit after the activation process is completed. Furthermore, Figure 9 The processes S30 and S34 correspond to the second display process, which displays a second confirmation image different from the first confirmation image on the display unit before the activation process begins. The process S37 corresponds to the fourth display process, which displays a second guide image different from the first guide image on the display unit during the implementation of the activation process. The process S39 corresponds to the sixth display process, which displays a second completion notification image different from the first completion notification image on the display unit after the activation process is completed.

[0093] (Second Implementation)

[0094] Next, refer to Figure 14 as well as Figure 15 A second embodiment of the control device, control method, program (program product), and non-transitory computer-readable storage medium will be described in detail below. In the second embodiment, the same reference numerals are used for components identical to those in the first embodiment, and detailed descriptions thereof are omitted.

[0095] In the first embodiment, the OTA manager 11 installed in the vehicle 10 controls the display of software update-related information on the HMI 18 installed in the same vehicle 10. In the second embodiment, the software update-related information is displayed on the HMI 43 of the information terminal 40 held by the user of the vehicle 10. Moreover, the display is controlled by the OTA server 30 of the data center.

[0096] <Activation process under the first update step>

[0097] Figure 14 The flowchart illustrates the activation phase processing during a software update performed in the first update step under the second embodiment. For example... Figure 14 As shown, if the installation phase is complete, the OTA manager 11 notifies the OTA server 30 (S50). If the OTA server 30 confirms the completion of the installation phase, it instructs the information terminal 40 to display the first pre-confirmation image (S51). The information terminal 40 displays the first pre-confirmation image on its own HMI 43 according to the instruction (S52). The first pre-confirmation image displayed on the HMI 43 of the information terminal 40 refers to... Figure 5 .

[0098] If the user selects to allow the execution of the activation process in the information terminal 40 (S53), the information terminal 40 notifies the OTA server 30 that the execution of the activation process is allowed (S54). Furthermore, the OTA server 30 notifies the OTA manager 11 of the vehicle 10 that the execution of the activation process is allowed (S55).

[0099] If the power switch 24 can subsequently be switched from on to off, the OTA manager 11 notifies the OTA server 30 of this status (S56). The OTA server 30, based on this notification, instructs the information terminal 40 to display the first final confirmation image (S57). The information terminal 40, based on the instruction, displays the first final confirmation image on its own HMI 43 (S58). The first final confirmation image displayed on the HMI 43 of the information terminal 40 is referenced... Figure 6 .

[0100] Subsequently, if the power switch 24 switches from on to off, the OTA manager 11 begins the activation process (S59). Additionally, the OTA manager 11 notifies the OTA server 30 of the start of the activation process (S60). If the OTA server 30 confirms the start of the activation process, it instructs the information terminal 40 to display the first boot image (S61). The information terminal 40 displays the first boot image on its own HMI 43 according to the instruction (S62). The first boot image displayed on the HMI 43 of the information terminal 40 is referenced... Figure 7 .

[0101] If the activation process is complete, the OTA manager 11 notifies the OTA server 30 of this status (S63). If the OTA server 30 confirms the completion of the activation process, it instructs the information terminal 40 to display the first completion notification image (S64). The information terminal 40 displays the first completion notification image on its own HMI 43 according to the instruction (S65). The first completion notification image displayed on the HMI 43 of the information terminal 40 is referenced... Figure 8 .

[0102] <Activation process under the second update step>

[0103] Figure 15 The flowchart illustrates the activation phase processing during a software update performed in the second update step, according to the second embodiment. For example... Figure 15 As shown, if the installation phase is complete, the OTA manager 11 notifies the OTA server 30 of this status (S70). If the OTA server 30 confirms the completion of the installation phase, it instructs the information terminal 40 to display the second pre-confirmation image (S71). The information terminal 40 displays the second pre-confirmation image on its own HMI 43 according to the instruction (S72). The second pre-confirmation image displayed on the HMI 43 of the information terminal 40 refers to... Figure 10 .

[0104] If the user selects to allow the execution of activation processing in the information terminal 40 (S73), the information terminal 40 notifies the OTA server 30 that the execution of activation processing is allowed (S74). The OTA server 30 notifies the OTA manager 11 of the vehicle 10 that the execution of activation processing is allowed (S75).

[0105] If the power switch 24 can subsequently be switched from on to off, the OTA manager 11 notifies the OTA server 30 of this situation (S76). The OTA server 30 instructs the information terminal 40 to display the second final confirmation image based on the notification (S77). The information terminal 40 displays the second final confirmation image on its own HMI 43 according to the instruction (S78). The second final confirmation image displayed on the HMI 43 of the information terminal 40 is referenced... Figure 11 .

[0106] Subsequently, if the power switch 24 switches from on to off and then back to on, the OTA manager 11 begins activation processing (S79). Additionally, the OTA manager 11 notifies the OTA server 30 of the start of activation processing (S80). If the OTA server 30 confirms the start of activation processing, it instructs the information terminal 40 to display the second boot image (S81). The information terminal 40 displays the second boot image on its own HMI 43 according to the instruction (S82). The second boot image displayed on the HMI 43 of the information terminal 40 is referenced... Figure 12 .

[0107] If the activation process is complete, the OTA manager 11 sends a completion notification to the OTA server 30 (S83). If the OTA server 30 confirms the completion of the activation process, it instructs the information terminal 40 to display a second completion notification image (S84). The information terminal 40 displays the second completion notification image on its own HMI 43 according to the instruction (S85). The second completion notification image displayed on the HMI 43 of the information terminal 40 is referenced... Figure 13 .

[0108] In the second embodiment, the HMI43 of the information terminal 40 corresponds to the display unit, and the OTA server 30 corresponds to the control device. The second embodiment has the same function and effect as, or is based on, the first embodiment.

[0109] (Other implementation methods)

[0110] The above-described embodiments can be implemented by modification as follows. The above-described embodiments and the following modifications can be combined and implemented within a technically compatible scope.

[0111] Alternatively, the OTA server 30 can control the display of the information terminal 40 in the second embodiment, in conjunction with the OTA manager 11 controlling the display of the vehicle 10's HMI 18 in the first embodiment. In this case, both the OTA manager 11 and the OTA server 30 correspond to the control device.

[0112] The display control of the HMI18 of the vehicle 10 in the first embodiment can also be implemented by the OTA server 30.

[0113] The OTA manager 11 can also implement the display control of the information terminal 40 in the second embodiment.

[0114] The display and control of information related to software updates can also be performed by the in-vehicle equipment that is the subject of the software update.

[0115] Figures 5-8 as well as Figures 10-13The examples shown depict information displayed using characters within the images. Information can also be displayed within these images using methods other than characters, such as static images or videos.

[0116] First completion notification image ( Figure 8 ) and the second completion notification image ( Figure 13 The composition of each image can be appropriately changed. In the above embodiment, information indicating that the power switch 24 can be switched on is displayed in the first completion notification image, but this information can also be omitted. Additionally, in the above embodiment, information indicating that the functions of the vehicle equipment restricted by the activation process can be used, specifically information indicating that the vehicle 10 can be driven, is displayed in the second completion notification image, but this display can also be omitted. Assume the user is aware of the functional restrictions in the activation process in both the case where a software update was performed in the first update step and the case where a software update was performed in the second update step. In this case, if the user knows the order in which the software update was performed (first update step and second update step), they can know the functions of the vehicle 10 that are unrestricted and usable upon completion of the activation process. Therefore, the first completion notification image and the second completion notification image should be configured such that the user can understand them as notifications of the completion of the activation process and can distinguish between the two images. If the first completion notification image and the second completion notification image are configured in this way, it is unlikely that the user will be confused by unexpected functional restrictions arising with the activation process.

[0117] The same completion image can be displayed after the activation process is completed, regardless of whether the software update is performed in the first or second update step.

[0118] Alternatively, the completed image can be displayed without activation processing.

[0119] First guiding image ( Figure 7 ) and the second guiding image ( Figure 12 The composition of each image can be appropriately changed. For example, the display of the estimated time until the activation process is completed in the first / second guide image can be omitted, or the display of the information indicating that the power switch 24 cannot be switched on in the first guide image can be omitted. The first and second guide images only need to be configured so that the user can understand that the activation process is in progress and the user can distinguish between the two images.

[0120] The same boot image can be displayed during the activation process regardless of whether the software update is performed in the first or second update step.

[0121] Alternatively, the boot image can be hidden during the activation process.

[0122] First pre-confirmed image ( Figure 5 ) and the second pre-confirmed image ( Figure 10 The configuration of each image can be appropriately modified. For example, the display of information about the estimated time of activation processing in the first / second pre-confirmation images can be omitted. Alternatively, information different from the illustrated information can be displayed as functional limitations accompanying the implementation of activation processing, or the display of functional limitation information can be omitted. Furthermore, the acceptance display of the selection operation for whether to allow the start of activation processing can be omitted if activation processing is performed automatically without user permission, or if user permission is obtained before the completion of the installation phase. In short, it is acceptable as long as the image is configured such that the user can recognize it as an image that pre-notifies the execution of activation processing, and the first pre-confirmation image and the second pre-confirmation image are different so that the user can distinguish them. The above applies to the first final confirmation image (…). Figure 6 ) and the second final confirmed image ( Figure 11 The same applies.

[0123] In the above embodiment, a first / second pre-confirmation image is displayed upon completion of the installation phase, and a first / second final confirmation image is displayed when the power switch 24 can be switched from on to off. Alternatively, only either the first / second pre-confirmation image or the first / second final confirmation image may be displayed.

[0124] The OTA manager 11, which manages software updates, controls the display of information related to software updates. Software updates and the display of related information can also be managed by different in-vehicle devices.

[0125] In the above embodiments, activation processing is performed during either the switch from a driving power mode to a parking power mode or the switch from a parking power mode to a driving power mode. If the vehicle 10's power mode includes power modes other than the two described above, activation processing can also be performed based on the switching of power modes under other switching types. If the switching type of the power mode for which activation processing is performed is different, the timing and content of the functional limitations of the vehicle 10 implemented will differ due to the different timing of the activation processing. Therefore, it is desirable to display different confirmation images for each switching type of the power mode for which activation processing is performed. Power modes other than driving and parking power modes can include, for example, power modes that provide entertainment functions and external power supply functions that cannot be provided by the normal parking power mode. Furthermore, as multiple power modes, power modes may also include those corresponding to the IG (ignition) on state, ACC (accessory power) on state, and vehicle power off state, respectively. The IG on state is the state where the vehicle's engine is running and the power to multiple ECUs is on. The ACC-on state is a state where only a portion of the ECUs are powered on, compared to the IG-on state. The vehicle power-off state is a state where almost all ECUs are powered off.

[0126] The control device can be configured as one or more processors that operate according to a computer program, one or more dedicated hardware circuits that perform at least some of the various processes, or a processing circuitry comprising combinations thereof. Examples of dedicated hardware include application-specific integrated circuits (ASICs). The processor includes a CPU (Central Processing Unit), and memories such as RAM (Random-Access Memory) and ROM (Read-Only Memory), which store program code or instructions configured to cause the CPU to perform processes. Memory, i.e., storage medium, includes all available media accessible by a general-purpose or special-purpose computer.

Claims

1. A control device, wherein, Equipped with processing circuitry, The aforementioned processing circuit is configured to control the display unit, which is configured to display information related to software updates of the vehicle-mounted equipment installed in the vehicle. The vehicle is configured to selectively switch to any one of multiple power modes. The software update includes an activation process that enables the activation of the update software installed in the vehicle-mounted equipment. The processing circuit described above is configured to display a first confirmation image on the display unit before the activation process begins, in the case of performing the software update in the first update step. The first update step is the activation process performed by switching between the plurality of power modes under the first switching type. The processing circuit described above is configured to display a second confirmation image on the display unit before the activation process begins, in the case of performing the software update in the second update step. The second update step is a step of performing the activation process based on switching between the plurality of power modes under the second switching type. The first switching type and the second switching type are different from each other, and the first confirmation image and the second confirmation image are different from each other.

2. The control device according to claim 1, wherein, The processing circuit described above is configured to display information about the functional limitations of the vehicle that accompanies the activation process described above in the first confirmation image, and to display information that is different from the information displayed in the first confirmation image as information about the functional limitations in the second confirmation image.

3. The control device according to claim 1 or claim 2, wherein, The processing circuit is configured to display information about the period during which the vehicle's function is restricted during the activation process in the first confirmation image, and to display information about the period during which the vehicle's function is restricted in the second confirmation image, which is different from the period during which the information is displayed in the first confirmation image.

4. The control device according to any one of claims 1 to 3, wherein, The aforementioned first confirmation image and the aforementioned second confirmation image contain an acceptance display of whether the selection operation to start the aforementioned activation process is allowed.

5. The control device according to any one of claims 1 to 4, wherein, The processing circuit described above is configured to determine whether to perform the software update using the first update step or the second update step based on the type of the vehicle-mounted device that is the target of the software update.

6. The control device according to any one of claims 1 to 5, wherein, The processing circuit described above is configured to determine whether to perform the software update using the first update step or the second update step based on the type of software that is the target of the software update.

7. The control device according to any one of claims 1 to 6, wherein, Based on the functions of the aforementioned in-vehicle devices, the in-vehicle devices that undergo the software update in the first update step and the in-vehicle devices that undergo the software update in the second update step are classified.

8. The control device according to any one of claims 1 to 7, wherein, The aforementioned processing circuit is configured to, when performing the aforementioned software update in the first update step, initiate the activation process of the vehicle-mounted device by switching between the plurality of power modes under the aforementioned first switching type. The aforementioned processing circuit is configured to initiate the activation process of the vehicle-mounted device by switching between the plurality of power modes under the second switching type when the software update is performed in the second update step.

9. The control device according to any one of claims 1 to 8, wherein, The switching between the aforementioned multiple power modes of the first switching type is a switching from a first power mode that makes the vehicle capable of driving to a second power mode that makes the vehicle incapable of driving. The switching between the multiple power modes of the second switching type is a switching from the second power mode to the first power mode.

10. The control device according to claim 9, wherein, The switching between the multiple power modes under the first switching type is performed based on the switching of the vehicle's power switch from on to off. The switching between the multiple power modes under the second switching type is performed based on the switching of the power switch from off to on.

11. The control device according to claim 9 or claim 10, wherein, The processing circuit described above is configured to display information about the estimated time from when the vehicle is switched to the second power mode until it can be switched back to the first power mode in the first confirmation image.

12. The control device according to any one of claims 9 to 11, wherein, The aforementioned processing circuit is configured to display information about the estimated time from when the device is instructed to switch from the second power mode to the first power mode until the activation process is completed in the second confirmation image.

13. The control device according to any one of claims 9 to 12, wherein, The processing circuit described above is configured to, during the activation process, display a first guide image on the display unit when the software update is performed using the first update step described above. The processing circuit described above is configured such that, when the software update is performed in the second update step described above, the display unit displays a second guide image that is different from the first guide image during the implementation of the activation process described above.

14. The control device according to claim 13, wherein, The aforementioned processing circuit is configured to display information indicating that the vehicle cannot be switched to the first power mode in the first guidance image.

15. The control device according to claim 13 or claim 14, wherein, The processing circuit described above is configured to display information about the estimated time until the vehicle can be switched to the first power mode in the first guide image.

16. The control device according to any one of claims 13 to 15, wherein, The aforementioned processing circuit is configured to display information about the estimated time until the completion of the aforementioned activation process in the aforementioned second guide image.

17. The control device according to any one of claims 9 to 16, wherein, The processing circuit described above is configured to, when performing the software update in the first update step described above, display a first completion notification image on the display unit after the activation process is completed. The processing circuit described above is configured such that, when the software update is performed using the second update step described above, the display unit displays a second completion notification image that is different from the first completion notification image after the activation process is completed.

18. The control device according to claim 17, wherein, The processing circuit described above is configured to display information indicating that the vehicle can be switched to the first power mode in the first completion notification image.

19. The control device according to claim 17 or claim 18, wherein, The aforementioned processing circuit is configured to display information indicating that the functions of the vehicle-mounted device, which are restricted due to the implementation of the aforementioned activation process, are now available in the aforementioned second completion notification image.

20. The control device according to any one of claims 9 to 19, wherein, The aforementioned vehicle-mounted device is one of several vehicle-mounted devices. One of the aforementioned vehicle-mounted devices that performs the software update using the first update step described above has a storage module that has a single library of updated software installed in a storage area that stores the software before the update. Another of the aforementioned vehicle-mounted devices that performs the aforementioned software update using the second update step has a dual-library storage module that has the updated software installed in a storage area different from the storage area that stores the software before the update.

21. The control device according to any one of claims 9 to 20, wherein, The data communication module used for external vehicle communication is the vehicle-mounted device for which the software has been updated in the second update step described above.

22. The control device according to any one of claims 9 to 21, wherein, The advanced driver assistance system is the in-vehicle device for which the software is updated in the second update step described above.

23. The control device according to any one of claims 9 to 22, wherein, The power control unit of the aforementioned vehicle is the on-board device for which the software has been updated using the second update step described above.

24. The control device according to any one of claims 1 to 23, wherein, The aforementioned display unit is installed in the aforementioned vehicle.

25. The control device according to any one of claims 1 to 23, wherein, The aforementioned display unit is located on an information terminal separate from the aforementioned vehicle.

26. The control device according to any one of claims 1 to 25, wherein, The control device is a server device that is independent of the aforementioned vehicle.

27. A vehicle, wherein, It has the control device according to any one of claims 1 to 25.

28. A control method, wherein, Include: Control of a display unit that displays progress information on software updates of onboard equipment installed in a vehicle, wherein the vehicle is configured to selectively switch to any one of multiple power modes, and the software update includes an activation process that enables the updated software installed in the onboard equipment to be effective. When the software update is performed in the first update step of the activation process by switching between the multiple power modes according to the first switching type, a first confirmation image is displayed on the display unit before the activation process begins. as well as When the software update is performed in the second update step, which involves switching between the plurality of power modes according to the second switching type, the activation process is performed by displaying a second confirmation image on the display unit before the activation process begins. The first switching type and the second switching type are different from each other, and the first confirmation image and the second confirmation image are different from each other.

29. A program in which, When the above procedure is executed by the control device, the control device shall perform the following: The control processing includes a display unit that controls the display of progress information of software updates for onboard equipment installed in a vehicle. The vehicle is configured to selectively switch to any one of multiple power modes. The software update includes an activation process that enables the activation of the update software installed in the onboard equipment. In the first display process, when the software is updated in the first update step of performing the activation process by switching between the plurality of power modes according to the first switching type, a first confirmation image is displayed on the display unit before the start of the activation process. as well as In the second display processing, when the software update is performed in the second update step of the activation process, which involves switching between the plurality of power modes according to the second switching type, the display unit displays a second confirmation image before the activation process begins. The first switching type and the second switching type are different from each other, and the first confirmation image and the second confirmation image are different from each other.

Images