Software update device, software update method, and software update processing program

Abstract

To provide a software update device, an update method for software and a software update processing program that can update software of an electronic control unit (ECU) without exerting any adverse influence on the ECU.SOLUTION: In a software update system, a software update device 110 mounted on a vehicle 1 comprises a controller 10 which acquires software from an external server and applies the software to respective pieces of equipment mounted on the vehicle 1 to control the respective pieces of equipment, and an on-vehicle battery 3 which can be charged and supplies electric power to the controller, wherein the controller uses the electric power supplied from the on-vehicle battery when the on-vehicle battery is not being charged to execute update processing for the software.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a software update device, a software update method, and a software update processing program. [Background technology]

[0002] JP2017-027549A discloses a software update device that updates the software of an in-vehicle device using an update program received via wireless communication. This software update device performs the update process by supplying power from an in-vehicle battery to the in-vehicle device to be updated. Summary of the Invention

[0003] However, when charging an on-board battery using an external power source or an internal combustion engine, the charging voltage is higher than the voltage used when updating software in an ECU (Electronic Control Unit) that controls on-board devices. Therefore, if a software update is performed using power supplied from the on-board battery while the on-board battery is being charged, a high charging voltage may be applied to the ECU, which may adversely affect the ECU.

[0004] The present invention has been made in consideration of the above-mentioned problems, and has as its object to provide a software update device, a software update method, and a software update processing program that are capable of updating ECU software without adversely affecting the ECU. [Means for solving the problem]

[0005] According to one aspect of the present invention, there is provided a software update device that performs an update process for software that operates an on-board device in a vehicle. The software update device includes a controller that acquires software and applies the software to the device to control the device, and an on-board battery that is rechargeable and supplies power to the controller. When the on-board battery is not being charged, the controller performs the software update process using power supplied from the on-board battery. [Brief explanation of the drawings]

[0006] [Figure 1] FIG. 1 is a schematic diagram of a software update system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a flowchart illustrating software update control according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0007] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

[0008] An embodiment of the present invention will be described with reference to Figures 1 and 2. Figure 1 is a schematic diagram showing the configuration of a software update system 100 and a software update device 110 according to an embodiment of the present invention.

[0009] 1, the software update system 100 is composed of a software update device 110 mounted on a vehicle 1 and an external server 2, and the software update device 110 is composed of a controller 10, a battery (vehicle battery) 3, and an acquisition unit 4. The vehicle 1 is, for example, an electric vehicle (EV).

[0010] The controller 10 includes a gateway 11 that acquires software from an external server 2, and an electronic control unit (ECU) 12 that controls each device mounted on the vehicle 1.

[0011] The gateway 11 is capable of communicating with the external server 2 and the electronic control unit 12, acquires update software from the external server 2, and transmits the acquired update software to the electronic control unit 12 to be updated. The gateway 11 also acquires control information of each device from the electronic control unit 12, and acquires the state of charge (SOC) of the battery 3 from an acquisition unit 4, which will be described later.

[0012] The gateway 11 is composed of a computer equipped with a central processing unit (CPU), a read only memory (ROM), a random access memory (RAM), and an input / output interface (I / O interface), and performs overall control of the software update device 110. The gateway 11 executes a specific program to perform processing for controlling the software update device 110. The gateway 11 performs software update control, which will be described later, together with the electronic control unit 12, for example.

[0013] The electronic control unit 12 is a controller that controls each device mounted on the vehicle 1, and is, for example, a BCM (Body Control Module), a VDC (Vehicle Dynamics Control), or a HEVC (Hybrid Electric Vehicle Control). Each electronic control unit 12 is composed of a computer equipped with a central processing unit (CPU), a read-only memory (ROM), a random access memory (RAM), and an input / output interface (I / O interface). The BCM controls the operating elements of the vehicle body 1, including the engine starter and door locks of the vehicle 1. The VDC controls the brakes and engine output of the vehicle 1 and controls the attitude of the vehicle 1 to prevent skidding of the vehicle 1. If the vehicle 1 is a hybrid vehicle, the HEVC controls the engine and motor, which are the drive sources, to achieve highly efficient driving.

[0014] The electronic control unit 12 can communicate with the gateway 11 and constantly transmits control information for each device as a signal to the gateway 11. Each electronic control unit 12 acquires software including a specific program from the gateway 11 and controls the target device by applying the acquired software to the device. The electronic control unit 12 also performs software update control, which will be described later, together with the gateway 11.

[0015] Each electronic control unit 12 also includes two storage units 121, 122 that store software acquired from the gateway 11. The electronic control unit 12 applies the software stored in one storage unit (first storage unit) 121 to the device. The electronic control unit 12 also updates the software by changing the software applied to the device to the software stored in the other storage unit (second storage unit) 122. Details of the software update process will be described later.

[0016] The battery 3 is connected to the gateway 11 and each electronic control unit 12. The battery 3 is a power source that supplies power to the gateway 11 and each electronic control unit 12, and can be charged by connecting to an external power source. The battery 3 can also be charged by an internal combustion engine (not shown) of the vehicle 1.

[0017] The acquisition unit 4 is a sensor or the like that detects (acquires) the state of charge (SOC) of the battery 3. The state of charge of the battery 3 detected by the acquisition unit 4 is transmitted to the gateway 11 as a signal.

[0018] Next, the software update process will be described.

[0019] As described above, each electronic control unit 12 includes two storage units 121 and 122. When the electronic control unit 12 acquires software (first software) transmitted from the gateway 11, the software is stored in one of the storage units (first storage unit) 121, and the electronic control unit 12 applies the software to the device. Note that the first software may not be acquired from the gateway 11, but may be already stored in the first storage unit 121 in the initial state.

[0020] Next, when the electronic control unit 12 acquires the update software (second software) transmitted from the gateway 11, the update software is stored in the other storage unit (second storage unit) 122. While the electronic control unit 12 acquires and stores the second software, the first software is applied to the device.

[0021] In this way, by providing two storage units 121 and 122 in each electronic control unit 12, the electronic control unit 12 can acquire (download) and store (install) update software while the first software is applied to the device. In other words, update software can be acquired and stored without stopping the operation of the controlled device.

[0022] When the update software (second software) is acquired and stored, the electronic control unit 12 changes the software applied to the device from the first software to the second software. This updates the software applied to the device. Hereinafter, the process of changing the software applied to the device from the first software to the second software will be referred to as a software update process (activation).

[0023] However, when charging the battery 3, the charging voltage is higher than the voltage used during the software update process of the electronic control unit 12. Therefore, if the software update process is performed using power supplied from the battery 3 while the battery 3 is being charged, the high charging voltage may be applied to the electronic control unit 12, such as an ECU, which may adversely affect the electronic control unit 12. In particular, if the vehicle 1 is an electric vehicle, the battery 3 typically has a larger capacity and a higher charging voltage than vehicles other than electric vehicles. Therefore, if the software update process is performed while a high-capacity external power source is connected to charge the battery 3, there is a possibility that a danger may occur to people inside or near the vehicle 1. Therefore, in this embodiment, the software update process is performed using power supplied from the battery 3 when the battery 3 is not being charged.

[0024] Specifically, the gateway 11 executes the software update process when the battery 3 of the vehicle 1 is not being charged, and prohibits charging of the battery 3 during the software update process.

[0025] In this way, the software update process is executed when the battery 3 of the vehicle 1 is not being charged, which prevents a high charging voltage from being applied to the electronic control unit (ECU) 12 during activation. In other words, the software update process can be executed without adversely affecting the ECU.

[0026] Furthermore, since the power used in the software update process is very small compared to the power used to operate other devices, there is almost no risk of the battery running out even if the battery 3 is not charged when the software update process is performed. In particular, if the vehicle 1 is an electric vehicle, the capacity of the battery 3 is usually larger than that of vehicles other than electric vehicles, so there is extremely little risk of the battery running out due to the software update process.

[0027] For example, if the execution of the software update process would cause the SOC of the battery 3 to become nearly zero, the gateway 11 prohibits the software update process. In such a case, since there is a risk that the battery will run out due to the execution of the software update process, it is necessary to charge the battery 3 before the software update process is executed. Therefore, the gateway 11 prohibits the software update process and notifies the driver, for example, by a display device, that the battery 3 needs to be charged.

[0028] 2 is a flowchart illustrating software update control according to an embodiment of the present invention. Note that all of the following controls are executed by the controller 10 (gateway 11, electronic control unit 12). Also, in the initial state, it is assumed that first software is stored in the first storage unit 121 of the electronic control unit 12, and that the first software is applied to the controlled device.

[0029] In step S101, the gateway (GW) 11 acquires update software (second software) from the external server 2, and then transmits the update software to the electronic control unit 12 to be updated.

[0030] In step S102, the electronic control unit 12 acquires (downloads) the update software (second software) from the gateway 11.

[0031] Next, in step S103, the electronic control unit 12 stores (installs) the update software (second software) in the second storage unit 122. Even during the acquisition and storage of the second software in steps S102 and S103, the first software is applied to the devices controlled by the electronic control unit 12, so the devices controlled by the electronic control unit 12 are not stopped.

[0032] In step S104, the gateway 11 acquires the SOC value of the battery 3 detected by the acquisition unit 4, and determines whether the SOC of the battery 3 is equal to or greater than a predetermined value (threshold value). The predetermined value here is, for example, a value that causes the SOC of the battery 3 to become nearly zero when a software update process is performed. If the SOC of the battery 3 is equal to or greater than the predetermined value (threshold value), the gateway 11 executes the process of step S105. On the other hand, if the SOC of the battery 3 is less than the predetermined value, the gateway 11 executes the process of step S114.

[0033] If the SOC of the battery 3 is lower than the predetermined value, the gateway 11 prohibits the software update process in step S114. Preferably, the gateway 11 notifies the driver, for example, by a display device, that the battery 3 needs to be charged. When the gateway 11 prohibits the software update process, the process returns to step S104. When the battery 3 is charged and the SOC of the battery 3 becomes equal to or higher than the predetermined value, the gateway 11 executes the process of step S105.

[0034] If the SOC of the battery 3 is equal to or greater than the predetermined value in step S104, the gateway 11 determines in step S105 whether the battery 3 is being charged. The determination of whether the battery 3 is being charged is made based on, for example, the control information of each device from the electronic control unit 12 and the SOC of the battery 3 detected by the acquisition unit 4. If the battery 3 is not being charged, the gateway 11 executes the process of step S106. On the other hand, if the battery 3 is being charged, the gateway 11 executes the process of step S115.

[0035] If the battery 3 is being charged, in step S115, the gateway 11 prohibits the software update process and returns to the process of step S105. When the charging of the battery 3 is stopped, the gateway 11 executes the process of step S106.

[0036] If the battery 3 is not being charged in step S105, the gateway 11 prohibits charging of the battery 3 in step S106.

[0037] In step S107, the gateway 11 supplies the power required for the software update process from the battery 3 to the electronic control unit 12, and the electronic control unit 12 executes the software update process using the power supplied from the battery 3. Specifically, the electronic control unit 12 changes the software applied to the controlled device from the first software to the second software. As a result, the software applied to the device is updated from the first software to the second software. Preferably, during the software update process, a display device or the like notifies the driver that the update process is in progress.

[0038] When the software update is completed, in step S108, the gateway 11 releases the prohibition on charging the battery 3 and ends the software update control.

[0039] In this way, when the battery 3 is not being charged, the software update process is performed using power supplied from the battery 3, which prevents a high charging voltage from being applied to the electronic control unit 12 during the update process. Furthermore, since charging of the battery 3 is prohibited before the software update process, it is possible to more reliably prevent a high charging voltage from being applied to the electronic control unit 12 during the update process.

[0040] Furthermore, since the electronic control unit 12 has two storage units 121, 122, it can acquire and store update software (second software) while the first software stored in the first storage unit 121 is applied to the device. Therefore, the device controlled by the electronic control unit 12 to be updated is not stopped while the update software is being acquired and stored. In other words, charging of the battery (vehicle battery) 3 is not prohibited while the update software is being acquired and stored, and charging of the battery (vehicle battery) 3 is prohibited only during the software update process. Therefore, the time during which charging of the battery (vehicle battery) 3 is prohibited can be shortened compared to when the device controlled by the electronic control unit 12 to be updated is stopped to acquire and store the update software.

[0041] To more reliably prevent the charging voltage from being applied to the electronic control unit 12, it is preferable to prohibit charging of the battery 3 before the software update process, but this is not necessarily limited to this. In particular, the software update process in this embodiment does not include acquiring and storing update software, so the software update process is completed in a short time. Therefore, if the software update process is started when the battery 3 is not being charged, there is no need to prohibit charging of the battery 3. In other words, the processes of steps S106 and S108 may be omitted.

[0042] Furthermore, to reliably prevent the battery from running out due to the software update process, it is preferable to prohibit the software update process when the SOC is lower than a predetermined value, but prohibiting the software update process based on the SOC is not essential. Typically, the battery 3 is charged before its SOC reaches zero, and the power used in the software update process is very small compared to the power used to operate other devices. Therefore, even if the process of prohibiting the software update process based on the SOC is omitted, there is almost no risk of the battery running out due to the software update process. In other words, the processes of steps S104 and S114 may be omitted.

[0043] After the software update process is completed, the next time the software is updated, the update software transmitted from the gateway 11 to the electronic control unit 12 is stored (overwritten) in the first storage unit 121. The software to be applied to the device is changed from the second software stored in the second storage unit 122 to the update software stored in the first storage unit 121, thereby executing a re-update of the software.

[0044] The processing shown in FIG. 2 is configured as a program to be executed by the controller 10, which is a computer, and these programs are stored in a storage medium.

[0045] According to the software updating device 110 of the above embodiment, the following effects can be obtained.

[0046] In the software update device 110, the electronic control unit 12 (controller 10) executes the software update process using power supplied from the battery (vehicle battery) 3 when the battery (vehicle battery) 3 is not being charged. Because the software update process is executed when the battery (vehicle battery) 3 is not being charged, it is possible to prevent a high charging voltage from being applied to the electronic control unit (ECU) 12 during activation. In other words, the software update process can be executed without adversely affecting the ECU.

[0047] In software update device 110, when battery (vehicle battery) 3 is not being charged by an external power source, software update processing is performed using power supplied from battery (vehicle battery) 3. If software update processing is performed while a large-capacity external power source is connected to charge battery 3, there is a possibility that danger will arise for people inside or near vehicle 1. On the other hand, in software update device 110 of this embodiment, software update processing is performed when battery 3 is not being charged by an external power source, so that danger will not arise for people inside or near vehicle 1.

[0048] In the software update device 110, when the battery (on-board battery) 3 is not being charged by the internal combustion engine of the vehicle 1, the software update process is performed using power supplied from the battery (on-board battery) 3. Since the software update process is performed when the battery (on-board battery) 3 is not being charged by the internal combustion engine, it is possible to prevent a high charging voltage from being applied to the electronic control unit (ECU) 12 during activation. In other words, the software update process can be performed without adversely affecting the ECU.

[0049] Before executing the software update process, the software update device 110 prohibits charging of the battery (vehicle battery) 3. This more reliably prevents a high charging voltage from being applied to the electronic control unit 12 during the software update process.

[0050] The electronic control unit 12 (controller 10) also has a first storage unit 121 that stores first software and a second storage unit 122 that stores second software. Therefore, update software (second software) can be acquired and stored in the second storage unit 122 while the first software stored in the first storage unit 121 is applied to the device. Therefore, the device controlled by the electronic control unit 12 to be updated is not stopped while the update software is acquired and stored. That is, charging of the battery (vehicle battery) 3 is not prohibited while the update software is acquired and stored, and charging of the battery (vehicle battery) 3 is prohibited only during the software update process. Therefore, compared to when the device controlled by the electronic control unit 12 to be updated is stopped to acquire and store the update software, the time during which charging of the battery (vehicle battery) 3 is prohibited can be shortened, improving convenience during software update work.

[0051] In the software update device 110, the gateway 11 (controller 10) prohibits the software update process when the state of charge (SOC) of the battery (vehicle battery) 3 acquired by the acquisition unit 4 is less than a predetermined value. This makes it possible to reliably prevent the battery 3 from running out of power due to a shortage of power stored in the battery 3 caused by the execution of the software update process.

[0052] In this embodiment, the electronic control unit 12 is a BCM, a VDC, or a HEVC, but the type of electronic control unit 12 is not limited to these, and the number of electronic control units is not limited to these, as long as they control the equipment installed in the vehicle 1.

[0053] Furthermore, the software update control including the software update process of this embodiment may be executed simultaneously for a plurality of electronic control units 12, or may be executed at different times for each electronic control unit 12.

[0054] In addition, in this embodiment, the gateway 11 performs overall control of the software update device 110, and the electronic control unit 12 performs control of each device mounted on the vehicle 1, but the subject of each control may be either the gateway 11 or the electronic control unit 12. For example, the gateway 11 may perform a change in software to be applied to a device (software update process) instead of the electronic control unit 12.

[0055] Furthermore, in this embodiment, the electronic control unit 12 is configured to have two storage units 121 and 122, but this is not necessarily limited to this. As described above, it is preferable that the electronic control unit 12 have two storage units 121 and 122 because this shortens the time during which charging of the battery 3 is prohibited. However, the electronic control unit 12 may be configured to have only one storage unit. In this case, the software update process is performed by overwriting the software stored in the storage unit with update software. Therefore, since the devices controlled by the electronic control unit 12 are stopped while the electronic control unit 12 is acquiring (downloading) and storing (installing) the update software, the electronic control unit 12 acquires the update software when the battery 3 is not being charged. Furthermore, preferably, charging of the battery 3 is prohibited while the electronic control unit 12 is acquiring (downloading) and storing (installing) the update software.

[0056] Although the embodiments of the present invention have been described above, the above embodiments merely illustrate some of the application examples of the present invention, and it is not intended that the technical scope of the present invention be limited to the specific configurations of the above embodiments.

Claims

1. A software update device that performs an update process for software that operates equipment mounted on a vehicle, a controller that acquires the software and applies the software to the device to control the device; a rechargeable vehicle battery that supplies power to the controller; an acquisition unit that acquires the amount of stored power of the in-vehicle battery; Equipped with the controller executes the software update process using power supplied from the vehicle battery when the vehicle battery is not being charged; Charging of the vehicle battery is not prohibited during the acquisition and storage of the update software, When the software update process is performed after the software update process is performed, If the detected amount of charge in the vehicle battery is less than a predetermined value, the software update process is prohibited; When the vehicle battery is charged and the amount of charge in the vehicle battery reaches or exceeds a predetermined value, charging of the vehicle battery is prohibited and then the software update process is executed. Software update device.

2. 2. The software update device according to claim 1, the vehicle battery is rechargeable by an external power source; the controller executes the software update process using power supplied from the vehicle battery at least when the vehicle battery is not being charged by the external power supply; Software update device.

3. 3. The software update device according to claim 1, the on-board battery is rechargeable by an internal combustion engine of the vehicle; the controller executes the software update process using power supplied from the vehicle battery at least when the vehicle battery is not being charged by the internal combustion engine. Software update device.

4. 4. A software update device according to claim 1, The controller a first storage unit that stores the acquired first software; a second storage unit that stores the acquired second software; executing a software update process by changing the software applied to the device from the first software to the second software; Software update device.

5. 5. A software update device according to claim 1, Installed in electric vehicles, Software update device.

6. A method for updating software that operates a device mounted on a vehicle, comprising: acquiring the software and applying the software to the device; updating the software using power supplied from a rechargeable vehicle battery when the vehicle battery is not being charged; Charging of the vehicle battery is not prohibited during the acquisition and storage of the update software, When the software update process is performed after the software update process is performed, If the detected amount of charge in the vehicle battery is less than a predetermined value, the software update process is prohibited; When the vehicle battery is charged and the amount of charge in the vehicle battery reaches or exceeds a predetermined value, charging of the vehicle battery is prohibited and then the software update process is executed. How to update your software.

7. A software update processing program for realizing an update process of software that operates a device mounted on a vehicle, obtaining said software and applying said software to said device; Obtaining the amount of charge stored in a rechargeable vehicle battery; updating the software using power supplied from the vehicle battery when the vehicle battery is not being charged; Charging of the vehicle battery is not prohibited during the acquisition and storage of the updated software; When the software update process is performed after the software update process is performed, If the detected amount of charge in the vehicle battery is less than a predetermined value, the software update process is prohibited; When the vehicle battery is charged and the amount of charge in the vehicle battery reaches or exceeds a predetermined value, charging of the vehicle battery is prohibited and then the software update process is executed; A software update processing program that enables the controller to achieve the above.

Images