Software update system, vehicle, and control method for a vehicle

Abstract

This invention provides a software update system, a vehicle, and a method for controlling the vehicle, improving the possibility of updating software (233). The software update system includes: a vehicle (2) having an electronic control unit (23); and a server device (3) capable of communicating with the vehicle, wherein the vehicle includes: a battery (21) that supplies power to the electronic control unit; a software update unit (403) that updates the software of the electronic control unit; and a battery control unit (401) that controls the remaining battery power. The software update unit sends a first message to the server device inquiring whether there is information related to the software update, and receives a second message from the server device as a response to the first message. When the software update unit receives the second message, the battery control unit changes the remaining battery power control.

Description

Technical Field

[0001] This invention relates to a software update system, a vehicle, and a method for controlling a vehicle. Background Technology

[0002] Previously, techniques for updating software in vehicles with batteries were known. For example, Patent Document 1 discloses a technique in which a reprogramming process is performed to rewrite the program of the electronic control device if the voltage of the auxiliary battery supplying power to the electronic control device is above the executable voltage.

[0003] [Existing Technical Documents]

[0004] [Patent Literature]

[0005] Patent Document 1: Japanese Patent Application Publication No. 2007-237905 Summary of the Invention

[0006] [The problem the invention aims to solve]

[0007] Typically, software updates in vehicles involve an activation process for the updated software. Since the vehicle cannot be used during activation, the activation process is performed based on the vehicle's battery power. However, the vehicle's battery is used for purposes such as improving vehicle performance and fuel economy. Therefore, it is possible that the battery level may be insufficient to proceed to the activation process, and the software update will not occur.

[0008] The present invention was made in view of the above circumstances, and its object is to increase the possibility of software updates.

[0009] [Methods used to solve problems]

[0010] One aspect of the present invention is a software update system comprising a vehicle having an electronic control unit and a server device capable of communicating with the vehicle, wherein the vehicle comprises: a battery supplying power to the electronic control unit; a software update unit updating the software of the electronic control unit; and a battery control unit controlling the remaining battery power. The software update unit sends a first message to the server device inquiring about the availability of information related to the software update, and receives a second message from the server device as a response to the first message. Upon receiving the second message, the battery control unit adjusts the remaining battery power control.

[0011] [Invention Effects]

[0012] According to one aspect of the present invention, the possibility of software updates can be increased. Attached Figure Description

[0013] Figure 1 This is a diagram showing the structure of a software update system.

[0014] Figure 2 This is a diagram showing the structure of the server device.

[0015] Figure 3 This is a diagram showing the structure of the vehicle.

[0016] Figure 4 It is a timing diagram showing the operation of the software update device and the server device.

[0017] Figure 5 This is an example of a notification screen.

[0018] Figure 6 It is a timing diagram showing the operation of the software update device and the server device.

[0019] Figure 7 It is a timing diagram showing the operation of the software update device and the server device.

[0020] Figure 8 This is a flowchart illustrating the operation of the software update device. Detailed Implementation

[0021] [1. First Implementation Method]

[0022] First, the first embodiment will be described.

[0023] [1-1. Structure of the Software Update System]

[0024] Figure 1 This is a diagram showing the structure of software update system 1.

[0025] The software update system 1 includes the vehicle 2 and provides the software 233 (see reference) executed by the ECU (Electronic Control Unit) 23 of the vehicle 2. Figure 3 The server device 3 is connected to the vehicle 2 via a communication network NW. The vehicle 2 downloads update software (hereinafter, marked "D1" to represent update software D1) from the server device 3 to update the software 233 of the ECU 23. That is, the software update system 1 can update the software 233 of the vehicle 2 using OTA (Over The Air).

[0026] ECU 23 is an example of an "electronic control unit".

[0027] In the following description, software includes programs executed by a processor and data associated with those programs that are referenced, generated, updated, or deleted. Updating software refers to the process of replacing processor-executed software with a newer version, which can be done by adding, deleting, or overwriting the software. Furthermore, the deletion of part or all of the processor-executed software, the installation of new software, and the deletion, addition, or overwriting of data used during software execution can also be included in software updates.

[0028] The vehicle 2 in this embodiment is a hybrid vehicle. Vehicle 2 can be any type of vehicle, including four-wheeled vehicles, two-wheeled vehicles, and others, and can also be a large vehicle, commercial vehicle, or work vehicle, etc. As an example, a four-wheeled vehicle is illustrated in this embodiment. Vehicle 2 connects to a communication network NW wirelessly, for example, via a cellular communication base station 4. The specific type of the communication network NW is not limited. For example, the communication network NW can also include a cellular communication network, the Internet, a WAN (Wide Area Network), a LAN (Local Area Network), a public line network, a provider device, a dedicated line, a base station, etc.

[0029] Server device 3 is connected to the communication network NW via a wired or wireless communication line and is a computer communicatively connected to vehicle 2. Server device 3 sends update software D1 to vehicle 2.

[0030] [1-2. Structure of the Server Device]

[0031] First, refer to Figure 2 The structure of server device 3 will be described.

[0032] Figure 2 This is a diagram showing the structure of server device 3.

[0033] The server device 3 includes a server control unit 30 and a server communication unit 31.

[0034] The server control unit 30 includes a processor 300 (CPU, Central Processing Unit), a memory 310, and interface circuits for connecting other devices and sensors. The server communication unit 31 is connected to the server control unit 30. The server control unit 30 performs various actions by reading and executing the control program 311 stored in the memory 310.

[0035] Memory 310 is a storage device for storing programs and data. Memory 310 stores control program 311, data processed by processor 300, etc. Memory 310 has non-volatile storage areas. In addition, memory 310 has volatile storage areas that constitute the working area of ​​processor 300. For example, memory 310 includes read-only memory (ROM) and random access memory (RAM).

[0036] The server communication unit 31 has hardware such as communication circuits and communicates with the vehicle 2 under the control of the server control unit 30.

[0037] [1-3. Vehicle Structure]

[0038] Figure 3 This is a diagram showing the structure of vehicle 2.

[0039] Vehicle 2 includes battery 21 and control circuit 22.

[0040] Battery 21 supplies power to various parts of vehicle 2, including ECU 23 and the devices controlled by ECU 23 (described later). Battery 21 is connected to control circuit 22, and its power supply and charging are controlled by control circuit 22. Control circuit 22 controls the power supply to battery 21 according to the control of software update device 41.

[0041] In addition, vehicle 2 has multiple ECUs 23.

[0042] ECU 23 is an electronic control unit that controls the equipment in vehicle 2 and is connected to software update device 41. ECU 23 includes a processor 231 (such as a CPU) and a memory 232. The processor 231 reads and executes the software 233 stored in the memory 232, thereby controlling the connected equipment. The memory 232 is a storage device for programs and data. The memory 232 stores the software 233, data processed by the processor 231, etc. The memory 232 is a dual-library memory (so-called double-sided ROM). Furthermore, the memory 232 may also have volatile storage areas that constitute the working area of ​​the processor 231.

[0043] Vehicle 2 is equipped with ECU 23A, ECU 23B and multiple ECU 23C as ECU 23.

[0044] ECU 23A is connected to engine 24, starter motor 25, and fuel pump 26. Engine 24 is the drive source for vehicle 2. Starter motor 25 is the motor that starts engine 24; it can be a so-called single-cell motor or a motor / generator with regenerative power generation capabilities. Fuel pump 26 supplies fuel from vehicle 2's fuel tank to engine 24. ECU 23A controls the fuel supply to engine 24, the ignition timing in engine 24, and the starter motor 25, among other things. Furthermore, engine 24, starter motor 25, and fuel pump 26 are mounted on vehicle 2.

[0045] ECU 23B is connected to drive motor 27. Drive motor 27 is the drive source for vehicle 2, and it operates by receiving power from battery 21. ECU 23B controls the rotational speed of drive motor 27.

[0046] ECU 23C is connected to one or more controlled objects 28. Examples of controlled objects 28 include a windshield wiper device that operates the windshield wipers of vehicle 2, and a device that turns the lights of vehicle 2 on and off.

[0047] Vehicle 2 is equipped with a TCU (Telematics Control Unit) 29.

[0048] TCU 29 is a communication device that conforms to the communication standard of vehicle 2 and communicates with devices other than vehicle 2. TCU 29 includes, for example, an antenna, a transmitter, a receiver, etc., and communicates with server device 3 under the control of software update device 41.

[0049] Vehicle 2 is equipped with a touch panel 40.

[0050] The touch panel 40 consists of a display and a touch sensor, which accepts touch operations and displays various information.

[0051] Vehicle 2 is equipped with a software update device 41.

[0052] The software update device 41 is a device for updating the software 233 of the ECU 23. The software update device 41 includes a processor 400 (such as a CPU), a memory 410, and interface circuitry for connecting other devices and sensors. The memory 410 is a storage device for storing programs and data. The memory 410 stores the control program 411, data processed by the processor 400, etc. The memory 410 has non-volatile storage areas. Additionally, the memory 410 has volatile storage areas, constituting the working area of ​​the processor 400. For example, the memory 410 may be composed of ROM or RAM.

[0053] The processor 400 functions as the battery control unit 401, notification unit 402, and software update unit 403 by executing the control program 411.

[0054] The battery control unit 401 performs battery level control on the battery 21. The battery control unit 401 performs either first control or second control to control the battery level of the battery 21.

[0055] The first control consumes more power from battery 21 than the second control. In the first control, the driving motor 27, as the drive source of vehicle 2, is used at a higher rate than the engine 24. When executing the first control, the battery control unit 401 instructs the control circuit 22 to increase the power supply from battery 21 to driving motor 27, and instructs the ECU 23 to decrease the output of engine 24.

[0056] The second control is a control that further suppresses the power consumption of battery 21 compared to the first control. In the second control, the engine 24, as the drive source of vehicle 2, is used at a higher rate than the drive motor 27. When executing the second control, the battery control unit 401 instructs the control circuit 22 to reduce the amount of power supplied from battery 21 to drive motor 27, and instructs the ECU 23 to increase the output of engine 24.

[0057] The notification unit 402 notifies the user of vehicle 2 of information by displaying information on the touch panel 40. The information notified by the notification unit 402 will be described later.

[0058] The software update unit 403 updates the software 233 of the ECU 23. The software update unit 403 performs the following processes: querying for information related to the update of the software 233, downloading the update software D1, installing the update software D1 on the ECU 23, and activating the update software D1 on the ECU 23.

[0059] [1-4. Actions]

[0060] Next, refer to Figure 4 The actions of each part of the software update system 1 related to the update of software 233 are explained.

[0061] Figure 4 This is a timing diagram illustrating the operation of the software update device 41 and the server device 3. Figure 4 At the start of the operation, the remaining capacity control of battery 21 is the first control.

[0062] The software update unit 403 sends an inquiry message to the server device 3 via the TCU 29, asking whether there is any information related to the update of the software 233 (step SA1).

[0063] Asking for information is an example of "first information".

[0064] When the server control unit 30 receives an inquiry message via the server communication unit 31, it sends a first response message to the vehicle 2 (step SA2).

[0065] The first response information is the information that responds to the query information, indicating whether there is any information related to the update of software 233.

[0066] The first response message is an example of the "second message".

[0067] The software update unit 403 receives the first response information via the TCU 29. If the received first response information indicates that there is a software update 233, the touch panel 40 displays the first screen (step SA3).

[0068] The first screen is a prompt to the user of vehicle 2 asking if they want to update software 233. The user is prompted as needed. For example, in the case of a software update for purposes such as troubleshooting, sometimes the user is not prompted.

[0069] If an instruction to update software 233 is displayed on the first screen, the battery control unit 401 changes the battery 21's remaining power control from the first control to the second control (step SA4).

[0070] Next, the notification unit 402 notifies the user of the change in the battery 21's remaining power control by displaying a notification screen TG on the touch panel 40 (step SA5).

[0071] Figure 5 This is an example of a notification screen (TG).

[0072] The notification screen TG is a screen that notifies you of a change in the remaining battery control of battery 21.

[0073] The notification screen TG displays the reason information J1 and the impact information J2.

[0074] Reason information J1 indicates the reason for changing the reserve control of battery 21. Figure 5 The string in the middle reads "in preparation for software updates".

[0075] Impact information J2 indicates the potential impact of changing the margin control of battery 21. Figure 5 The strings in the middle are "acceleration performance may deteriorate" and "fuel consumption performance may deteriorate".

[0076] return Figure 4As explained, the software update unit 403 sends a request to update the software D1 to the server device 3 via the TCU 29 (step SA6).

[0077] When the server control unit 30 receives the request information via the server communication unit 31, it sends the second response information to the vehicle 2 (step SA7).

[0078] The second response information is information indicating the response to the requested information, including the update software D1.

[0079] When the software update unit 403 receives the second information from the server device 3, that is, when it downloads the update software D1 from the server device 3, it installs the downloaded update software D1 into the target ECU 23 (step SA8).

[0080] If step SA8 is described in detail, the software update unit 403 transmits the update software D1 to the target ECU 23 and instructs the target ECU 23 to write the update software D1 into the memory 232.

[0081] As described above, the memory 232 of the ECU 23 is a dual-database memory. Therefore, the ECU 23 can operate according to the software 233 stored in one storage area MA of the memory 232 while simultaneously writing update software D1 to the other storage area MA of the memory 232. Thus, for example, even when the vehicle 2 is in motion, the ECU 23 can write update software D1 to the memory 232.

[0082] Next, when the ignition power of vehicle 2 is disconnected, the software update unit 403 determines whether to transfer to the activation process of update software D1 (step SA9).

[0083] Step SA9 is described in detail.

[0084] In the activation process, to disable the use of vehicle 2, the activation process is performed by supplying power from battery 21. Therefore, the software update unit 403 obtains the remaining power of battery 21, and if the obtained remaining power of battery 21 is above a predetermined level, a positive determination is made in step SA9. This predetermined level is appropriately determined through prior testing, simulation, etc., so that the remaining power of the battery will not disappear during the activation process.

[0085] If the software update unit 403 determines that the process should proceed to activation, it displays a second screen on the touch panel 40 asking whether to start the software update (step SA10).

[0086] Then, if the software update unit 403 receives an instruction to start the software 233 update on the second screen, it instructs the ECU 23 to perform the activation process (step SA11) for updating the software 233.

[0087] The activation process in ECU 23 will be explained here.

[0088] When ECU 23 receives an instruction to perform activation processing, it performs activation processing for the update software D1. The activation processing for the update software D1 includes the following steps: setting the startup parameters of ECU 23 so that when ECU 23 starts, it loads the written update software D1 and begins to follow the control of the update software D1. For example, the activation processing for the update software D1 includes activating the memory area MA containing the update software D1 as a read area and deactivating the memory area MA not containing the update software D1 as a read area.

[0089] In addition, Figure 4 In the timing sequence shown, if the software update unit 403 receives the first response information from the server device 3, it may also skip the processing of step SA3 and proceed to the processing of step SA4 and beyond.

[0090] [2. Second Implementation]

[0091] Next, the second embodiment will be described.

[0092] In the description of the second embodiment, the same reference numerals are used for the constituent elements that are the same as those in the software update system 1 of the first embodiment, and detailed descriptions are omitted as appropriate.

[0093] The second implementation differs from the first implementation in the actions related to updating the software 233.

[0094] Figure 6 This is a timing diagram showing the operation of the software update device 41 and the server device 3.

[0095] exist Figure 6 In the timing diagram shown, for and Figure 4 The timing diagrams shown use the same step numbers for the same steps, and their detailed descriptions are omitted as appropriate.

[0096] In addition, Figure 6 At the start of the operation, the remaining capacity control of battery 21 is the first control.

[0097] Compare Figure 6 and Figure 4As can be seen, in the second embodiment, when the software update device 41 downloads the update software D1, it changes the battery 21's remaining power control and notifies the user of the change.

[0098] That is, when the software update device 41 of the second embodiment shows an instruction to update software 233 on the first screen, it performs step SA6 without executing steps SA4 and SA5. Alternatively, when the software update device 41 of the second embodiment receives the second response information, i.e., when the update software D1 has been downloaded, it performs steps SA4 and SA5, and then performs steps SA8 and beyond.

[0099] Furthermore, the second implementation method is also the same, in Figure 6 In the timing sequence shown, the software update device 41 can also skip the processing of step SA3 after receiving the first response information from the server device 3.

[0100] [3. Third Implementation Method]

[0101] Next, the third embodiment will be described.

[0102] In the description of the third embodiment, the same reference numerals are used for the constituent elements that are the same as those of the constituent elements of the software update system 1 of the first embodiment, and detailed descriptions are omitted as appropriate.

[0103] The third implementation differs from the first implementation in the actions related to updating the software 233.

[0104] Figure 7 This is a timing diagram showing the operation of the software update device 41 and the server device 3.

[0105] exist Figure 7 In the timing diagram shown, for and Figure 4 The timing diagrams shown use the same step numbers for the same steps, and their detailed descriptions are omitted as appropriate.

[0106] In addition, Figure 7 At the start of the operation, the remaining capacity control of battery 21 is the first control.

[0107] Compare Figure 8 and Figure 4 As can be seen, in the third embodiment, when the software update device 41 installs update software D1 in the ECU 23 to which the battery 21 is located, it changes the battery 21's remaining power control and notifies the user of the change in battery 21's remaining power control.

[0108] That is, when the software update device 41 of the third embodiment shows an instruction to update the software 233 on the first screen, it performs the processing of step SA6 without executing steps SA4 and SA5. Furthermore, when the software update device 41 of the third embodiment has installed the update software D1 on the target ECU 23, it performs steps SA4 and SA5, and then performs the processing from step SA9 onwards.

[0109] Furthermore, the third embodiment also similarly... Figure 7 In the timing sequence shown, the software update device 41 can also skip the processing of step SA3 after receiving the first response information from the server device 3.

[0110] [4. Fourth Implementation Method]

[0111] Next, the fourth embodiment will be described.

[0112] In the description of the fourth embodiment, the same reference numerals are used for the constituent elements that are the same as those of the constituent elements of the software update system 1 of the first embodiment, and detailed descriptions are omitted as appropriate.

[0113] The fourth implementation differs from the first implementation in the actions related to updating the software 233.

[0114] In the fourth embodiment, no changes to the battery 21's balance control or notifications of changes to the battery 21's balance control are made before the update software D1 is installed on the ECU 23.

[0115] Figure 8 This is a flowchart illustrating the operation of the software update device 41. Figure 8 The flowchart shown is performed after the downloaded update software D1 is installed on ECU 23, which is the target.

[0116] The software update unit 403 determines whether the ignition power supply of vehicle 2 has been disconnected (step SB1). If the software update unit 403 determines that the ignition power supply has not been disconnected (step SB1: no), it performs step SB1 again.

[0117] On the other hand, when the software update unit 403 determines that the ignition power has been disconnected (step SB1: Yes), it determines whether the remaining amount of battery 21 is above a predetermined level (step SB2). Furthermore, this predetermined level is the remaining amount of battery 21 that can withstand activation processing, and is appropriately determined through prior testing, simulation, etc.

[0118] If the software update unit 403 determines that the remaining amount of battery 21 is above the specified remaining amount (step SB2: Yes), it determines whether to start the activation process (step SB3).

[0119] Step SB3 will be described in detail.

[0120] If the software update unit 403 detects an activation process start operation on the second screen, it makes a positive determination in step SB3. On the other hand, if the software update unit 403 detects an activation process not start operation on the second screen, or if the absence of activation process start operation on the second screen persists for a predetermined period of time, it makes a negative determination in step SB3.

[0121] If the software update unit 403 determines that the activation process should not be started (step SB3: No), the processor 400 returns the process to step SB1.

[0122] On the other hand, when the software update unit 403 determines that the activation process has started (step SB3: Yes), it instructs the ECU 23, which has the update software D1 installed, to execute the activation process (step SB4).

[0123] Returning to the explanation of step SB2, if the software update unit 403 determines that the remaining amount of battery 21 is not above the specified remaining amount (step SB2: no), the battery control unit 401 determines whether the remaining amount control of battery 21 has been changed to the second control (step SB5).

[0124] If the battery control unit 401 determines that the control has been changed to the second control (step SB5: yes), the processor 400 performs the determination in step SB1 again.

[0125] On the other hand, if the battery control unit 401 determines that the second control has not been changed (step SB5: no), it determines whether the number of times the battery 21 cannot be moved to the activation process due to insufficient remaining power is more than a predetermined number (step SB6).

[0126] Step SB6 is described in detail.

[0127] Battery control unit 401 Figure 8 After the flowchart begins, the number of times a negative decision is made in step SB2 is counted. If the number of negative decisions in step SB2 exceeds a predetermined number, a positive decision is made in step SB6. Furthermore, a positive decision is made in step SB6 when, during a predetermined number of driving cycles, the battery 21 cannot be moved to the activation process due to insufficient charge. A driving cycle refers to the period from when the ignition power is turned on until when the ignition power is turned off.

[0128] On the other hand, if the number of times the battery control unit 401 makes a negative determination in step SB2 is not more than a predetermined number, it makes a negative determination in step SB6.

[0129] Next, if the battery control unit 401 makes a negative determination in step SB6 (step SB6: no), the processor 300 returns the process to step SB1.

[0130] On the other hand, if the battery control unit 401 makes a positive determination in step SB6 (step SB6: yes), it changes the remaining control of the battery 21 from the first control to the second control (step SB7).

[0131] Next, notification unit 402 notified that the remaining power control of battery 21 had been changed (step SB8).

[0132] [5. Other Implementation Methods]

[0133] The above-described implementation method is merely one approach and can be arbitrarily modified and applied.

[0134] In the above embodiments, the case where vehicle 2 is a hybrid vehicle is illustrated. However, vehicle 2 may also be an electric vehicle without an engine 24, rather than a hybrid vehicle. In this other embodiment, the battery capacity control of battery 21 is changed from a first control to a second control by changing the destination of the power supply to battery 21. Furthermore, in this other embodiment, vehicle 2 does not have ECU 23A or any devices controlled by ECU 23A.

[0135] In the above embodiment, the notification unit 402 provides notifications via information display. In other embodiments, the notification unit 402 may also provide notifications via sound. In this case, the vehicle 2 is equipped with a speaker that outputs sound into the vehicle interior.

[0136] Processors 231, 300, and 400 can be composed of multiple processors or a single processor. These processors can also be hardware programmed to implement the aforementioned functionalities. In this case, these processors are, for example, composed of ASICs (Application Specific Integrated Circuits) or FPGAs (Field Programmable Gate Arrays).

[0137] also, Figure 3 The internal structure of vehicle 2 shown is an example, and the specific installation method is not particularly limited. That is, it is not necessarily necessary to install hardware corresponding to each part separately; of course, it can also be configured so that the functions of each part are implemented by a processor executing a program. In addition, in the above embodiments, a part of the function implemented by software can be made into hardware, or a part of the function implemented by hardware can be implemented by software.

[0138] in addition, Figure 4 as well as Figures 6-8 The steps shown are divided according to the main processing content, and this invention is not limited by the method or name of the division of processing units. Depending on the processing content, it may also be divided into more step units. Alternatively, a single step unit may contain more processes. Furthermore, the order of these steps may be appropriately replaced without affecting the spirit of this invention.

[0139] Furthermore, when implementing the system update method based on the software update device 41 described above using the processor 400, the program executed by the processor 400 can also be configured as a recording medium or a transmission medium for transmitting the program. That is, the control program 411 can also be implemented with the control program 411 recorded on a removable information recording medium. Examples of information recording media include magnetic recording media such as hard disks, optical recording media such as CDs, USB (Universal Serial Bus) memory, SSD (Solid State Drive) and other semiconductor storage devices, but other recording media can also be used.

[0140] [6. Structure supported by the above embodiments]

[0141] The above implementation supports the following structures.

[0142] (Structure 1)

[0143] A software update system includes a vehicle with an electronic control unit and a server device capable of communicating with the vehicle. The vehicle includes: a battery that supplies power to the electronic control unit; a software update unit that updates the software of the electronic control unit; and a battery control unit that manages the remaining battery power. The software update unit sends a first message to the server device inquiring about the availability of information related to the software update, and receives a second message from the server device as a response to the first message. Upon receiving the second message, the battery control unit adjusts the remaining battery power management.

[0144] According to the software update system of Structure 1, the battery reserve control is modified in the event of a anticipated software update. Therefore, the battery reserve can be controlled from before the activation process to prevent it from becoming insufficient to proceed to the activation process. This reduces the likelihood of the battery being unable to proceed to the activation process due to insufficient reserve, thus increasing the likelihood of a successful software update.

[0145] (Structure 2)

[0146] According to the software update system of Structure 1, when the software update unit downloads update software after receiving the second information, the battery control unit changes the remaining battery capacity control.

[0147] According to the software update system of Structure 2, the battery balance control is changed when a software update is required. Therefore, the battery balance can be controlled from before the activation process to prevent it from becoming insufficient for the activation process. This reduces the possibility of being unable to proceed to the activation process due to insufficient battery balance, thus increasing the likelihood of a successful software update. Furthermore, the battery balance control is changed only when the update software has been downloaded. Therefore, the impact of changing the battery balance control before the update software is downloaded can be prevented.

[0148] (Structure 3)

[0149] According to the software update system of structure 2, the battery control unit changes the battery's remaining capacity control when the update software is installed in the electronic control unit.

[0150] According to the software update system of Structure 3, the battery balance control is changed when a software update is required. Therefore, the battery balance can be controlled from before the activation process to prevent it from becoming insufficient to proceed to the activation process. This reduces the possibility of failing to proceed to the activation process due to insufficient battery balance, thus increasing the likelihood of a software update. Furthermore, the battery balance control is changed when the update software is installed. Therefore, the impact of changing the battery balance control on the vehicle before the installation of the update software can be suppressed. That is, this impact on the vehicle over a long period can be suppressed.

[0151] (Structure 4)

[0152] According to the software update system of structure 3, if, after the update software is installed, the battery control unit cannot switch to the activation process of the update software due to insufficient battery charge during a predetermined number of driving cycles, the battery charge control changes the battery charge control.

[0153] According to the software update system of Structure 4, the following situation can be suppressed: the impact of changes to the battery reserve control of the vehicle over a long period of time after the update software is installed.

[0154] (Structure 5)

[0155] A software update system according to any one of structures 1 to 4, wherein the software update system includes a notification unit that, when the battery control unit changes the battery's remaining power control, notifies the user of the vehicle that the battery's remaining power control has been changed.

[0156] According to the software update system of Structure 5, even if the vehicle is affected by changes in battery capacity control, the user of the vehicle can be prevented from feeling uncomfortable about the impact.

[0157] (Structure 6)

[0158] According to the software update system of structure 5, the notification unit notifies the reason for the change in the battery's remaining power control and the possible impact of the change in the battery's remaining power control.

[0159] According to the software update system of Structure 6, even if the vehicle is affected by changes in battery capacity control, the discomfort experienced by vehicle users due to such changes can be further suppressed.

[0160] (Structure 7)

[0161] A vehicle having an electronic control unit and capable of communicating with a server device, wherein the vehicle comprises: a battery supplying power to the electronic control unit; a software update unit updating the software of the electronic control unit; and a battery control unit controlling the remaining battery level. The software update unit sends first information to the server device inquiring about the availability of information related to the software update, and receives second information from the server device as a response to the first information. Upon receiving the second information, the battery control unit adjusts the remaining battery level control.

[0162] According to the vehicle of Structure 7, it achieves the same effect as the software update system of Structure 1.

[0163] (Structure 8)

[0164] A method for controlling a vehicle, the vehicle having an electronic control unit and a battery supplying power to the electronic control unit, and the vehicle being able to communicate with a server device, wherein the method for controlling the vehicle includes the following steps: sending first information to the server device inquiring about whether there is information related to an update of the software of the electronic control unit; receiving second information from the server device as a response to the first information; and, upon receiving the second information, changing the remaining battery capacity control.

[0165] The vehicle control method of Structure 8 achieves the same effect as the software update system of Structure 1.

[0166] Explanation of reference numerals in the attached figures

[0167] 1…Software update system, 2…Vehicle, 3…Server device, 4…Base station, 21…Battery, 22…Control circuit, 23, 23A, 23B, 23C…ECU (Electronic Control Unit), 24…Engine, 25…Starter motor, 26…Fuel pump, 27…Drive motor, 28…Controlled object device, 29…TCU, 30…Server control unit, 31…Server communication unit, 40…Touch panel, 41…Software update device, 231…Processor, 232…Memory, 233…Software, 300…Processor, 310…Memory, 311…Control program, 400…Processor, 401…Battery control unit, 402…Notification unit, 403…Software update unit, 410…Memory, 411…Control program, D1…Update software, J1…Reason information, J2…Impact information, MA…Storage area, NW…Communication network, TG…Notification screen.

Claims

1. A software update system comprising a vehicle having an electronic control unit and a server device capable of communicating with the vehicle, wherein, The vehicle has the following features: A battery that supplies power to the electronic control unit; The software update unit updates the software of the electronic control unit; and The battery control unit controls the remaining battery capacity. The software update unit sends a first message to the server device inquiring whether there is any information related to the software update, and receives a second message from the server device as a response to the first message. Upon receiving the second information from the software update unit, the battery control unit changes the remaining battery capacity control.

2. The software update system according to claim 1, wherein, If the software update unit downloads update software after receiving the second information, the battery control unit changes the battery's remaining capacity control.

3. The software update system according to claim 2, wherein, When the updated software is installed in the electronic control unit, the battery control unit changes the remaining battery capacity control.

4. The software update system according to claim 3, wherein, If, after the update software is installed, the battery cannot be switched to the activation process of the update software due to insufficient battery charge during a predetermined number of driving cycles, the battery control unit changes the battery charge control.

5. The software update system according to any one of claims 1 to 4, wherein, The software update system includes a notification unit that notifies the vehicle user of the change in battery charge control when the battery control unit changes the battery charge control.

6. The software update system according to claim 5, wherein, The notification department notifies the reasons for changing the battery's remaining capacity control and the possible impact of the change.

7. A vehicle having an electronic control unit and capable of communicating with a server device, wherein, This vehicle is equipped with: A battery that supplies power to the electronic control unit; The software update unit updates the software of the electronic control unit; and The battery control unit controls the remaining battery capacity. The software update unit sends a first message to the server device inquiring whether there is any information related to the software update, and receives a second message from the server device as a response to the first message. Upon receiving the second information from the software update unit, the battery control unit changes the remaining battery capacity control.

8. A method for controlling a vehicle, the vehicle having an electronic control unit and a battery supplying power to the electronic control unit, and the vehicle being able to communicate with a server device, wherein... The vehicle control method includes the following steps: Send a first message to the server device inquiring whether there is any information related to an update of the software in the electronic control unit; Receive second information from the server device as a response to the first information; and Upon receiving the second information, the remaining battery capacity control is changed.

Images