Vehicle

Abstract

This vehicle is provided with: a charging control unit that executes a charging process for charging an on-vehicle battery to execute a predetermined function of the vehicle while the vehicle is in a stopped state; a wireless communication unit that wirelessly communicates with an external device and thereby receives update data for updating a program related to an update target unit provided in the vehicle; and a program update unit that executes an update process for the program related to the update target unit, using the update data. The program update unit includes one or more processors, and one or more memory units connected to the processors. The processor is triggered by the start of the charging process to start the update process for the update target unit that is not related to the predetermined function, using power supplied from the on-vehicle battery.

Description

vehicle

[0001] The present invention relates to a vehicle.

[0002] 2. Description of the Related Art In recent years, techniques have been proposed for updating programs in various electronic devices installed in a vehicle (hereinafter, sometimes referred to as "reprogramming").

[0003] For example, Patent Document 1 discloses a vehicle that can be reprogrammed using update data received via wireless communication. Patent Document 1 also discloses that when reprogramming is performed, if the battery capacity is low, the battery is charged beforehand.

[0004] Japanese Patent Application Laid-Open No. 2019-064424

[0005] When the battery is charged in response to the execution of reprogramming as described above, the battery is charged only for the purpose of reprogramming, which increases the frequency of operation of various components for charging the battery, potentially shortening the lifespan of the various components.

[0006] An object of the present invention is to provide a vehicle that can prevent the shortening of the lifespan of various parts used to charge the battery.

[0007] In order to solve the above problem, a vehicle according to one embodiment of the present invention comprises: a charging control unit that executes a charging process to charge an onboard battery in order to execute a predetermined function of the vehicle while the vehicle is stopped; a wireless communication unit that receives update data for updating a program related to a unit to be updated provided in the vehicle by wirelessly communicating with an external device; and a program update unit that executes an update process for the program related to the unit to be updated using the update data, wherein the program update unit has one or more processors and one or more memories connected to the processors, and wherein, upon the start of the charging process, the processor starts the update process for the unit to be updated that is unrelated to the predetermined function using power supplied from the onboard battery.

[0008] According to the present invention, it is possible to prevent the shortening of the lifespan of various parts used to charge a battery.

[0009] Fig. 1 is a functional block diagram for explaining a vehicle according to an embodiment of the present invention. Fig. 2 is a diagram for explaining a reprogramming execution permission screen according to an embodiment of the present invention. Fig. 3 is a flowchart showing control processing by a predetermined function control unit according to an embodiment of the present invention. Fig. 4 is a flowchart showing control processing by a program update unit according to an embodiment of the present invention. Fig. 5 is a flowchart showing a process for determining whether a termination condition is met according to an embodiment of the present invention.

[0010] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. Specific dimensions, materials, numerical values, etc. shown in the embodiments are merely examples for facilitating understanding of the invention and do not limit the present invention unless otherwise specified. In this specification and drawings, elements having substantially the same functions and configurations are designated by the same reference numerals to avoid redundant explanation, and elements not directly related to the present invention are not shown.

[0011] FIG. 1 is a functional block diagram illustrating a vehicle 100 according to an embodiment of the present invention. In this embodiment, the vehicle 100 is an electric vehicle (EV) equipped with a motor (not shown). However, the present invention may also be applied to a so-called parallel hybrid vehicle equipped with an engine and a motor as a driving source. The present invention may also be applied to various vehicle types, such as plug-in hybrid vehicles (PHEVs) and non-plug-in hybrid vehicles (hybrid vehicles).

[0012] As shown in FIG. 1, a vehicle 100 includes a high-voltage battery 110 mainly for driving a motor, and a low-voltage battery 120 having an output voltage lower than that of the high-voltage battery 110 .

[0013] The high-voltage battery 110 is an in-vehicle battery that can be charged by power supplied from an external power source 200 that is connected to the vehicle 100 by wire or wirelessly.

[0014] The low-voltage battery 120 is an in-vehicle battery that can be charged by the output voltage from the high-voltage battery 110, which has been stepped down by a DC-DC converter (not shown). The low-voltage battery 120 is, for example, a 12V auxiliary battery. The low-voltage battery 120 supplies DC power of a relatively low voltage (for example, 12V) to various in-vehicle devices (auxiliaries) mounted on the vehicle 100.

[0015] 1 , vehicle 100 also includes a wireless communication unit 130. Wireless communication unit 130 communicates wirelessly with external device 400 via network 300. External device 400 has a function of distributing update data necessary for updating a program for controlling a later-described update target unit 170 mounted on vehicle 100 (hereinafter, also referred to as "reprogramming") that controls the later-described update target unit 170. The update data includes, for example, information specifying later-described update target unit 170 that is the target for reprogramming, and information about the update program used in reprogramming.

[0016] In this embodiment, when the wireless communication unit 130 is instructed to receive update data by the program update unit 160 (described later) while the vehicle 100 is stopped, the wireless communication unit 130 receives the update data from the external device 400 via the network 300. However, the wireless communication unit 130 may also receive the update data from the external device 400 via the network 300 while the vehicle 100 is traveling.

[0017] As shown in FIG. 1 , the vehicle 100 also includes a predetermined function control unit 140 for executing predetermined functions. The predetermined function control unit 140 includes one or more processors 142 and one or more memories 144 connected to the processors 142. The processor 142 includes, for example, a central processing unit (CPU). The memory 144 includes, for example, a read-only memory (ROM) and a random access memory (RAM). The ROM is a storage element that stores programs used by the CPU, calculation parameters, and the like. The RAM is a storage element that temporarily stores data such as variables and parameters used in processing executed by the CPU.

[0018] The predetermined function control unit 140 controls the execution of predetermined functions of the vehicle 100 while the vehicle 100 is stopped.

[0019] The predetermined function control unit 140 executes, for example, an auxiliary charging function as the predetermined function. The auxiliary charging function is executed when a predetermined charging start condition is met while the vehicle 100 is stopped. For example, the charging start condition is met when the charging rate of the low-voltage battery 120 falls below a predetermined threshold. When the auxiliary charging function is executed, the predetermined function control unit 140 instructs the charging control unit 150, which will be described later, to execute a charging process for the low-voltage battery 120. Upon receiving the instruction from the predetermined function control unit 140, the charging control unit 150 steps down the output voltage from the high-voltage battery 110 using a DC-DC converter (not shown) and supplies the voltage to the low-voltage battery 120, thereby charging the low-voltage battery 120.

[0020] Furthermore, the auxiliary charging function is terminated when a predetermined charging termination condition is met. For example, the charging termination condition is met when the low-voltage battery 120 is fully charged or sufficiently charged to exceed a predetermined threshold. When the charging termination condition is met, the predetermined function control unit 140 instructs the charging control unit 150 (described later) to terminate the charging process for the low-voltage battery 120.

[0021] Furthermore, the predetermined function control unit 140 executes, for example, a pre-air conditioning function as a predetermined function. The pre-air conditioning function is executed when predetermined pre-air conditioning start conditions are met while the vehicle 100 is stopped. For example, the pre-air conditioning start conditions are met when a user inputs an instruction to start using the pre-air conditioning function via the display unit 180 (described later). When the pre-air conditioning function is executed, the predetermined function control unit 140 drives an in-vehicle air conditioner (not shown) to warm or cool the atmosphere in the vehicle cabin. Furthermore, the predetermined function control unit 140 instructs the charging control unit 150 (described later) to execute a charging process for the low-voltage battery 120.

[0022] Furthermore, the pre-AC function is terminated when a predetermined pre-AC termination condition is met. For example, the pre-AC termination condition is met when the user inputs an instruction to terminate use of the pre-AC function via the display unit 180 (described later). When the pre-AC termination condition is met, the predetermined function control unit 140 stops operation of the vehicle air conditioner (not shown). When the pre-AC termination condition is met, the predetermined function control unit 140 instructs the charging control unit 150 (described later) to terminate the charging process for the low-voltage battery 120.

[0023] Furthermore, the predetermined function control unit 140 executes, for example, a my room function as the predetermined function. The my room function is executed when a predetermined my room start condition is met while the vehicle 100 is stopped. For example, the my room start condition is met when a command to start using the my room function is input from the user via the display unit 180 (described later). When the my room function is executed, the predetermined function control unit 140 enables the use of various in-vehicle devices (auxiliaries), such as audio equipment (not shown). Furthermore, the predetermined function control unit 140 instructs the charging control unit 150 (described later) to execute a charging process for the low-voltage battery 120.

[0024] Furthermore, execution of the my room function is terminated when a predetermined my room termination condition is met. For example, the my room termination condition is met when the user inputs an instruction to terminate use of the my room function via the display unit 180 (described later). When the my room termination condition is met, the predetermined function control unit 140 stops the use of various in-vehicle devices (auxiliaries) such as audio equipment (not shown). When the my room termination condition is met, the predetermined function control unit 140 instructs the charging control unit 150 (described later) to terminate the execution of the charging process for the low-voltage battery 120.

[0025] Furthermore, the predetermined function control unit 140 executes, for example, an external charging function as the predetermined function. The external charging function is executed when a predetermined external charging start condition is met while the vehicle 100 is stopped. For example, the external charging start condition is met when the external power source 200 is connected to the vehicle 100 by wire or wirelessly. When the external charging function is executed, the predetermined function control unit 140 instructs the charging control unit 150 (described later) to execute a charging process for the high-voltage battery 110 and the low-voltage battery 120.

[0026] Furthermore, the external charging function is terminated when a predetermined external charging termination condition is met. For example, the external charging termination condition is met when the high-voltage battery 110 and the low-voltage battery 120 are fully charged or sufficiently charged to exceed a predetermined threshold. When the external charging termination condition is met, the predetermined function control unit 140 instructs the charging control unit 150 (described later) to terminate the charging process for the high-voltage battery 110 and the low-voltage battery 120.

[0027] 1 , the vehicle 100 includes a charging control unit 150. The charging control unit 150 has one or more processors 152 and one or more memories 154 connected to the processor 152. The charging control unit 150 controls the execution of the charging process for at least one of the high-voltage battery 110 or the low-voltage battery 120 based on an instruction to execute the charging process from the predetermined function control unit 140. The charging control unit 150 also ends the execution of the charging process for the high-voltage battery 110 or the low-voltage battery 120 based on an instruction to end the execution of the charging process from the predetermined function control unit 140.

[0028] 1, the vehicle 100 also includes a program update unit 160. The program update unit 160 includes one or more processors 162 and one or more memories 164 connected to the processors 162.

[0029] The vehicle 100 also includes a plurality of update target units 170. Each of the plurality of update target units 170 includes one or more processors 172 and one or more memories 174 connected to the processors 172. In this embodiment, the update target units 170 are units that are unrelated to the execution of a predetermined function. The plurality of update target units 170 may be control units for various electronic devices mounted on the vehicle 100. Specifically, the update target units 170 are, for example, an engine control unit that controls the engine, a motor control unit that controls the motor, a car navigation system control unit that controls the car navigation system, an autonomous driving control unit that controls autonomous driving of the vehicle 100, etc.

[0030] When a predetermined function is executed or a charging process for the vehicle battery is executed, the program update unit 160 instructs the wireless communication unit 130 to check whether new update data has been distributed from the external device 400.

[0031] If new update data has been distributed from the external device 400, a reprogramming execution permission screen 180a (FIG. 2) is displayed on the display unit 180 to request the user's permission to execute reprogramming.

[0032] 2 is a diagram illustrating a reprogramming execution permission screen 180a according to one embodiment of the present invention. As shown in FIG. 2, the reprogramming execution permission screen 180a displays, for example, a warning message about performing reprogramming and a button image that allows the user to select whether or not to perform reprogramming (YES or NO).

[0033] When the user presses the YES button on the reprogramming execution permission screen 180a to permit reprogramming, the program update unit 160 starts the reprogramming process. If the user presses the NO button on the reprogramming execution permission screen 180a to deny reprogramming, the program update unit 160 does not start the reprogramming process. If the user does not press either the YES or NO button on the reprogramming execution permission screen 180a, the program update unit 160 does not start the reprogramming process.

[0034] As part of the reprogramming process, the program update unit 160 first determines the priority order for executing reprogramming when multiple update data sets have been distributed, i.e., when multiple reprogramming operations are scheduled. In this embodiment, when update data sets have been distributed for multiple update target units 170, the program update unit 160 executes reprogramming operations one by one, starting with the update process with the highest priority and then the update process with the lowest priority. In other words, the program update unit 160 can execute update operations for multiple update target functions in order of the priority of the functions. Note that the update target unit 170 to be reprogrammed in one operation is one selected from the multiple update target units 170.

[0035] In this embodiment, the program update unit 160 sets a high priority for update processes related to the vehicle 100's driving functions and a low priority for update processes related to functions other than the vehicle 100's driving functions. That is, the program update unit 160 executes update processes related to the vehicle 100's driving functions with higher priority than update processes related to functions other than the vehicle 100's driving functions. This enables reprogramming related to driving functions, which are relatively important, to be executed with higher priority than reprogramming of other functions, which are relatively less important. Note that, although this embodiment illustrates a case in which the program update unit 160 determines the priority of reprogramming execution on the vehicle 100 side, the priority may be determined in advance on the external device 400 side. In this case, the vehicle 100 executes reprogramming according to the priority determined in advance on the external device 400 side.

[0036] Furthermore, in this embodiment, if any of the above-described charging end condition, pre-air conditioning end condition, personal room end condition, and external charging end condition is met during the update process, the program update unit 160 causes the charge control unit 150 to continue charging the low-voltage battery 120 until the predetermined end condition is met. This makes it possible to reduce the risk of the low-voltage battery 120 running out of power before the update process is completed, which could result in the update process being interrupted.

[0037] In this embodiment, a case will be described in which multiple predetermined termination conditions (hereinafter also referred to as "charging termination conditions") for the charging process of the low-voltage battery 120 by the charging control unit 150 are set depending on the type of program function to be updated and the progress of the update process. Specifically, as a first charging termination condition, for example, when all update processes scheduled to be executed are completed, the program update unit 160 may satisfy the predetermined termination condition and terminate the charging process of the low-voltage battery 120 by the charging control unit 150. This makes it possible to ensure power for the low-voltage battery 120 until the update processes for all functions to be updated are completed.

[0038] As a second charge termination condition, for example, when the timing for ending the charging process of the low-voltage battery 120 arrives while one or more update processes related to the driving functions of the vehicle 100 are being executed, the program update unit 160 may satisfy a predetermined termination condition and terminate the charging process of the low-voltage battery 120 when all of the update processes related to the driving functions are completed. In other words, even when the timing for ending the charging process of the low-voltage battery 120 by the charging control unit 150 arrives while the update process related to the driving functions is being executed, the program update unit 160 may extend and continue the charging process until all of the update processes related to the driving functions are completed. This makes it possible to reliably complete reprogramming of driving functions that are relatively important.

[0039] As a third charging termination condition, for example, when the timing for ending the charging process arrives during execution of an update process for a function other than the driving function, and no update process for a function other than the driving function is scheduled to be executed thereafter, the program update unit 160 may satisfy a predetermined termination condition and terminate the charging process of the low-voltage battery 120 upon completion of the ongoing update process. In other words, the program update unit 160 may extend and continue the charging process at least until the ongoing update process is completed. This allows power to be secured in the low-voltage battery 120 until the update process for at least one of the currently ongoing functions is completed.

[0040] In addition, if the time comes to end the charging process while an update process related to a function other than the driving function is being executed, and an update process related to a function other than the driving function is scheduled to be executed afterwards, the termination conditions will differ depending on the content of the update process scheduled to be executed.

[0041] For example, as a fourth charging termination condition, for example, if a second update process uncorrelated with a first update process is scheduled to be executed while a first update process related to a function other than the driving function is being executed, the program update unit 160 may satisfy the predetermined termination condition upon completion of the first update process. That is, for reprogramming of a relatively less important function other than the driving function, the program update unit 160 may terminate the charging process as soon as the ongoing reprogramming (first update process) is completed. This prevents the execution time of the reprogramming of a relatively less important function from being prolonged, thereby preventing a decrease in user convenience due to waiting for the charging of the low-voltage battery 120 to be completed.

[0042] On the other hand, as a fifth charging termination condition, for example, if a second update process correlated with a first update process related to a function other than the driving function is scheduled to be executed while the first update process is being executed, the program update unit 160 may continue the charging process until at least the first and second update processes are completed. In other words, even if the reprogramming is related to a function other than the driving function that is relatively less important, the charging process may be continued until all update processes for multiple correlated functions are completed. This prevents multiple correlated update processes from being executed only partially, and allows the correlated update processes to be completed together.

[0043] 3 is a flowchart showing a control process performed by the predetermined function control unit 140 according to an embodiment of the present invention. Note that various processes, including the processes described below, can be executed by the processor 142 of the predetermined function control unit 140.

[0044] 3, first, the predetermined function control unit 140 determines whether the vehicle 100 is stopped (S100-1). If the vehicle 100 is not stopped (NO in S100-1), the predetermined function control unit 140 ends the control process.

[0045] If the vehicle 100 is stopped (YES in S100-1), the predetermined function control unit 140 determines whether the start conditions of any of the predetermined functions are met (S100-3). If the start conditions of none of the predetermined functions are met (NO in S100-3), the predetermined function control unit 140 ends the control process.

[0046] If the start condition of any of the predetermined functions is met (YES in S100-3), the predetermined function control unit 140 transmits predetermined function start information indicating that execution of the predetermined function will start to the program update unit 160 (S100-5). The predetermined function start information may include, for example, information regarding the type of the predetermined function whose execution will start.

[0047] Furthermore, the predetermined function control unit 140 instructs the charging control unit 150 to start the execution of the charging process (S100-7). Based on the instruction to execute the charging process from the predetermined function control unit 140, the charging control unit 150 starts the execution of the charging process for at least one of the high-voltage battery 110 and the low-voltage battery 120.

[0048] Furthermore, the predetermined function control unit 140 executes a predetermined function start process for starting the execution of the predetermined function for which it has been determined in step S100-3 that the start condition is met (S100-9).

[0049] When the execution of a predetermined function is started, the predetermined function control unit 140 determines whether the termination condition for the predetermined function being executed is met (S100-11). If the termination condition for the predetermined function being executed is not met (NO in S100-11), the predetermined function control unit 140 continues the execution of the predetermined function.

[0050] If the termination condition is met (YES in S100-11), the predetermined function control unit 140 transmits predetermined function termination information indicating that the termination condition of the predetermined function is met to the program update unit 160 (S100-13). The predetermined function termination information may include, for example, information about the type of the predetermined function for which the termination condition is met.

[0051] The predetermined function control unit 140 determines whether or not update start information indicating that an update process triggered by the execution of a predetermined function or the execution of a charging process for the vehicle battery has already been received from the program update unit 160 (S100-15). The update start information may include, for example, information indicating the type of update process that is scheduled to be executed.

[0052] If the update start information has not yet been received (NO in S100-15), the predetermined function control unit 140 proceeds to step S100-19, which will be described later. On the other hand, if the update start information has already been received (YES in S100-15), the predetermined function control unit 140 determines whether or not update end information indicating that the update process has been completed and the end condition has been met has already been received (S100-17).

[0053] If the predetermined function control unit 140 has not yet received the update end information (NO in S100-17), it continues executing the predetermined function. If the predetermined function control unit 140 has already received the update end information (YES in S100-17), it executes a predetermined function end process to end the execution of the predetermined function (S100-19). The predetermined function control unit 140 also instructs the charging control unit 150 to end the charging process (S100-21) and ends the control process. The predetermined function control unit 140 may be able to receive update start information and update end information between steps S100-9 and S100-11 and between steps S100-13 and S100-19. The predetermined function control unit 140 may also be able to constantly receive update start information and update end information.

[0054] By the above process, when the termination condition of the predetermined function is satisfied and the started update process has not been completed, the predetermined function control unit 140 can extend the charging process. Also, when the termination condition of the predetermined function is satisfied and the started update process has been completed, the predetermined function control unit 140 can terminate the charging process.

[0055] 4 is a flowchart showing the control processing by the program update unit 160 according to one embodiment of the present invention. In this embodiment, the control processing by the predetermined function control unit 140 described above and the control processing by the program update unit 160 described below are executed in parallel. Furthermore, various processes including the processes described below can be executed by the processor 162 of the program update unit 160.

[0056] 4, first, the program update unit 160 determines (S200-1) whether or not predetermined function start information has been received from the predetermined function control unit 140. As a result, if the predetermined function start information has not been received (NO in S200-1), the program update unit 160 ends the control process.

[0057] If predetermined function start information has been received (YES in S200-1), the program update unit 160 instructs the wireless communication unit 130 to check whether new update data has been distributed from the external device 400. Then, the program update unit 160 determines whether new update data has been distributed from the external device 400 (S200-3). If new update data has not been distributed (NO in S200-3), the program update unit 160 ends the control process.

[0058] If new update data is to be distributed (YES in S200-3), the program update unit 160 displays the reprogramming execution permission screen 180a (FIG. 2) on the display unit 180 (S200-5).

[0059] The program update unit 160 determines whether or not a permission operation has been performed by pressing the YES button on the reprogramming execution permission screen 180a (S200-7), and whether or not a denial operation has been performed by pressing the NO button on the reprogramming execution permission screen 180a (S200-9).

[0060] As a result, if a denial operation is performed (NO in S200-7 and YES in S200-9), the program update unit 160 ends the display of the reprogramming execution permission screen 180a and ends the control process. On the other hand, if neither a permission operation nor a denial operation is performed (NO in S200-7 and NO in S200-9), the program update unit 160 continues to display the reprogramming execution permission screen 180a.

[0061] Furthermore, if the permission operation is performed (YES in S200-7), the program update unit 160 transmits update start information to the predetermined function control unit 140 (S200-11).

[0062] Furthermore, the program update unit 160 determines the priority order for executing reprogramming for new update data that will be distributed (S200-13).

[0063] The program update unit 160 instructs the wireless communication unit 130 to receive the update data with the highest priority determined in step S200-13, and acquires the update data (S200-15).

[0064] The program update section 160 identifies the update target unit 170 to be reprogrammed based on the update data acquired in step S200-15 (S200-17).

[0065] The program update unit 160 determines whether a start condition for starting reprogramming is met (S200-19). Specifically, for example, the program update unit 160 may determine that the start condition is met when the current voltage of the low-voltage battery 120 exceeds a lower limit voltage of the low-voltage battery 120 set for each type of update target unit 170. Note that the lower limit voltage of the low-voltage battery 120 may be determined based on, for example, the power required for previous reprogramming of the update target unit 170.

[0066] If the start condition for starting the reprogramming execution is not met (NO in S200-19), the program update unit 160 waits without starting the reprogramming execution.

[0067] If the start condition for starting the execution of reprogramming is met (YES in S200-19), the program update unit 160 starts the execution of the update process based on the update data acquired in the above step S200-15 (S200-21).

[0068] The program update unit 160 determines whether the update process that has started execution has been completed (S200-23). ​​If the update process that has started execution has not been completed (NO in S200-23), the program update unit 160 continues execution of the update process.

[0069] Furthermore, when the update process that has started execution is completed (YES in S200-23), the program update unit 160 executes a termination condition satisfaction determination process (S300) to determine whether or not a termination condition related to reprogramming is satisfied. This termination condition satisfaction determination process (S300) will be described in detail later.

[0070] The program update unit 160 determines whether the termination condition for reprogramming is met (S200-25) based on the result of the termination condition satisfaction determination process (S300). If the termination condition is not met (NO in S200-25), the program update unit 160 proceeds to step S200-15 and executes the update process with the highest priority among the update processes that have been scheduled but not yet executed, in the same manner as described above.

[0071] On the other hand, if the termination condition is met (YES in S200-25), the program update unit 160 transmits update termination information to the predetermined function control unit 140 and terminates the control process.

[0072] 5 is a flowchart showing the termination condition satisfaction determination process (S300) according to an embodiment of the present invention. Note that various processes including the processes described below can be executed by the processor 162 of the program update unit 160.

[0073] The program update unit 160 determines whether predetermined function end information has been received from the predetermined function control unit 140 (S300-1). That is, it determines whether the timing for ending the charging process has arrived. As a result, if predetermined function end information has not been received (NO in S300-1), the program update unit 160 determines whether all update processes scheduled to be executed have been completed (S300-3).

[0074] If all update processes scheduled to be executed have been completed (YES in S300-3), the program update unit 160 determines that the termination condition is met (S300-5), and ends the termination condition fulfillment determination process.

[0075] Furthermore, if all update processes scheduled for execution have not been completed (NO in S300-3), the program update unit 160 determines that the termination condition is not met (S300-7) and terminates the termination condition fulfillment determination process.

[0076] If the predetermined function end information has been received (YES in S300-1), the program update unit 160 determines whether the update process for the driving function has been completed (S300-9). If the update process for the driving function has been completed (YES in S300-9), the program update unit 160 determines whether the update process for all driving functions scheduled to be executed has been completed (S300-11).

[0077] As a result, if the update process for all driving functions scheduled to be executed has been completed (YES in S300-11), the program update unit 160 determines that the termination condition has been met (S300-13) and terminates the termination condition fulfillment determination process.

[0078] Also, if the update processing for all driving functions scheduled to be executed has not been completed (NO in S300-11), the program update unit 160 determines that the termination condition is not met (S300-15) and terminates the termination condition fulfillment determination processing.

[0079] Furthermore, when an update process related to a function other than the driving function is completed (NO in S300-9), the program update unit 160 determines whether or not an update process correlated with the completed update process is scheduled to be executed (S300-17). As a result, when an update process correlated with the completed update process is scheduled to be executed (YES in S300-17), the program update unit 160 determines that the termination condition is not satisfied (S300-19), and terminates the termination condition satisfaction determination process.

[0080] Furthermore, if no update process correlated with the completed update process is scheduled to be executed (NO in S300-17), the program update unit 160 determines that the termination condition is met (S300-21) and terminates the termination condition fulfillment determination process.

[0081] As described above, vehicle 100 of the present embodiment includes charging control unit 150 that executes a charging process to charge the onboard battery to execute a predetermined function of vehicle 100 while vehicle 100 is stopped. Vehicle 100 also includes wireless communication unit 130 that receives update data for updating a program related to update target unit 170 provided in vehicle 100 by wirelessly communicating with external device 400. Vehicle 100 also includes program update unit 160 that executes an update process for the program related to update target unit 170 using the update data. Program update unit 160 includes one or more processors 162 and one or more memories 164 connected to processor 162. When the charging process is started, processor 162 starts an update process for update target unit 170 that is unrelated to the predetermined function, using power supplied from the onboard battery.

[0082] In the vehicle 100 of this embodiment, reprogramming can be performed in response to the execution of a predetermined function or the execution of a charging process for the vehicle battery. That is, the charging of the vehicle battery (low-voltage battery 120) is not performed in response to the execution of reprogramming (update process). This prevents the vehicle battery from being charged solely for the purpose of reprogramming, thereby suppressing an increase in the frequency of operation of various components for charging the vehicle battery and reducing the risk of shortening the lifespan of the various components. Furthermore, the predetermined function control unit 140 and the charging control unit 150, which are used to perform the existing charging process for the low-voltage battery 120, do not need to be significantly modified; the reprogramming can be performed simply by adding a program update unit 160. This reduces the risk of increased costs.

[0083] In the vehicle 100 of this embodiment, the processor 162 may be capable of sequentially executing the update processes related to multiple functions. The processor 162 may then prioritize execution of the update process related to the driving functions of the vehicle 100 over update processes related to functions other than the driving functions. This allows reprogramming related to driving functions, which are relatively important, to be prioritized.

[0084] In the vehicle 100 of this embodiment, if the time to end the charging process arrives while the update process related to the driving functions is being executed, the processor 162 may continue the charging process until all update processes related to the driving functions are completed. This makes it possible to reliably complete the reprogramming of the driving functions, which are relatively important.

[0085] Furthermore, in the vehicle 100 of this embodiment, when the time comes to end the charging process while an update process related to a function other than the driving function is being executed, the processor 162 may continue the charging process at least until the update process currently being executed is completed. This makes it possible to prevent a situation in which the reprogramming process takes a long time and reduces user convenience.

[0086] Furthermore, in the vehicle 100 of this embodiment, when a second update process correlated with the first update process is scheduled to be executed while a first update process related to a function other than the driving function is being executed, and when the time for the charging process to end arrives, the processor 162 may continue the charging process at least until the second update process ends. This makes it possible to prevent a situation in which only some of the correlated update processes are executed.

[0087] While the present invention has been described above with reference to the accompanying drawings, it goes without saying that the present invention is not limited to such embodiments. It is clear that those skilled in the art can conceive of various modifications and alterations within the scope of the claims, and it is understood that such modifications and alterations also fall within the technical scope of the present invention.

[0088] The series of processes performed by vehicle 100 according to the above embodiment may be implemented using software, hardware, or a combination of software and hardware. The programs constituting the software may be stored in advance in, for example, a non-transitory storage medium provided inside or outside each device. The programs are then read from, for example, a non-transitory storage medium (e.g., ROM) to a temporary storage medium (e.g., RAM) and executed by a processor such as a CPU.

[0089] Furthermore, according to the above embodiment, it is possible to provide a program for executing the processing of each function of the vehicle 100. Furthermore, it is also possible to provide a non-transitory computer-readable recording medium storing the program. The non-transitory recording medium may be, for example, a disk-type recording medium such as an optical disk, a magnetic disk, or a magneto-optical disk, or may be a semiconductor memory such as a flash memory or a USB memory.

[0090] REFERENCE SIGNS LIST 100 Vehicle 110 High-voltage battery 120 Low-voltage battery 130 Wireless communication unit 150 Charging control unit 160 Program update unit 162 Processor 164 Memory 170 Update target unit 400 External device

Claims

1. A charging control unit that performs a charging process to charge the onboard battery in order to perform a predetermined function of the vehicle while the vehicle is stopped, A wireless communication unit that receives update data for updating the program related to the update target unit installed in the vehicle by wirelessly communicating with an external device, A program update unit that uses the update data to perform update processing on the program related to the update target unit, Equipped with, The program update unit, One or more processors, One or more memories connected to the processor, It has, The aforementioned processor, The start of the charging process triggers the sequential commencement of a plurality of update processes related to the update target unit, which are unrelated to the predetermined function, using the power supplied from the vehicle battery. If the timing for the charging process to end arrives before the completion of the update process that is currently running, the charging process will be continued until the update process that is currently running is completed. A vehicle that, upon completion of the update process currently underway, cancels the execution of any update processes scheduled after that update process and terminates the charging process.

2. The aforementioned processor, The update processes related to multiple functions can be executed sequentially. The vehicle according to claim 1, wherein the update process relating to the driving function of the vehicle is performed with priority over the update process relating to functions other than the driving function.

3. The aforementioned processor, The vehicle according to claim 2, wherein if the timing for the completion of the charging process arrives while the update process related to the driving function is being executed, the charging process is continued until all of the update processes related to the driving function are completed.

4. The aforementioned processor, The vehicle according to claim 2 or 3, wherein if the timing for the end of the charging process arrives while the update process relating to a function other than the driving function is being executed, the charging process is continued at least until the ongoing update process is completed.

5. The aforementioned processor, The vehicle according to claim 4, wherein, while a first update process relating to a function other than the driving function is being executed, a second update process correlated with the first update process is scheduled to be executed, and when the timing for the completion of the charging process arrives, the charging process is continued at least until the second update process is completed.