Vehicle control device

Abstract

The invention relates to a vehicle control apparatus. A vehicle control device executes a process of detecting a request to update a control program from an external server to an in-vehicle ECU during charging of an in-vehicle battery by an external power supply. When at least a part of the request for updating is detected, the vehicle control device executes a process for prohibiting the in-vehicle ECU from executing an update during charging.

Description

Technical Field

[0001] The technology disclosed in this specification relates to a vehicle control device. Background Art

[0002] Japanese Patent Application Laid-Open No. 2023-18875 discloses a so-called On The Air (OTA) technology for receiving an update of a control program of an ECU mounted on a vehicle from an external server via wireless communication. Summary of the invention

[0003] If an OTA update occurs during charging of the vehicle battery, the power consumption due to the update increases. Therefore, for example, when charging the battery to a predetermined target SOC, the charging time is extended by the time corresponding to the power consumption due to the update.

[0004] The vehicle control device disclosed in this specification is a vehicle control device for controlling a vehicle. The vehicle includes: a battery that can be charged using an external power source; a communication unit that can communicate various data with an external server through wireless communication; and an ECU that performs various controls based on a pre-stored control program.

[0005] While the battery is being charged by the external power source, the vehicle control device executes a process of detecting a request from the external server to the ECU to update the control program.

[0006] The vehicle control device executes a process of prohibiting the ECU from executing the update during charging when at least a portion of the update request is detected.

[0007] The vehicle control device can be various devices. The vehicle control device can be separate from the vehicle or integrated with the vehicle. The vehicle control device can be, for example, a user's portable terminal (such as a smartphone, a notebook PC, a wearable device), or a control device mounted on the vehicle (such as an ECU).

[0008] According to the above configuration, it is possible to prohibit the execution of the update of the ECU during charging. By prohibiting the update during charging, it is possible to suppress the situation where the charging time becomes longer than when the update is executed during charging. Thus, the charging time of the vehicle can be optimized. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Features, advantages, and technical and industrial significance of exemplary embodiments of the present invention will be described below with reference to the accompanying drawings, in which like reference numerals represent like elements, and in which:

[0010] Figure 1 is a block diagram of an OTA system 1;

[0011] Figure 2is a flow chart illustrating the contents of the update process;

[0012] Figure 3 is a flowchart illustrating the calculation process of the remaining charging time of the first embodiment; and

[0013] Figure 4 1 is a flowchart for explaining the calculation process of the remaining charging time in the second embodiment. DETAILED DESCRIPTION

[0014] The following lists additional features of the drive device disclosed in this specification.

[0015] In the process of prohibiting the ECU, when the urgency of the update is within a predetermined low level range, the execution of the update may be prohibited.

[0016] According to the above configuration, it is possible to perform a less urgent update after the battery is fully charged, and it is possible to prevent the charging time from being prolonged.

[0017] The vehicle control device may also perform a process of calculating the update power consumed by the vehicle due to the update and the required power required by the battery thereafter when the update is performed during charging. Alternatively, the vehicle control device may further perform a process of calculating the remaining charging time required for charging the battery from the external power source by subtracting the stored power at the time of starting charging the battery from the total of the update power and the required power. The vehicle control device may also perform a process of notifying the user of the calculated remaining charging time.

[0018] According to the above configuration, the user can be informed of the remaining charging time required to charge the required amount of electric power, and the user can be urged to optimize the charging time.

[0019] The required amount of power may also be the amount of power required to move to a destination.

[0020] According to the above configuration, the charging time can be optimized so that the battery can be charged with the amount of electricity required to travel to the destination.

[0021] When the update is performed during charging, the vehicle control device may also determine whether the battery can be charged at the destination. If the vehicle control device determines that charging at the destination is possible, the vehicle control device may calculate the required power for a one-way trip to the destination. If the vehicle control device determines that charging at the destination is not possible, the vehicle control device may calculate the required power for a round trip to the destination.

[0022] According to the above configuration, the required power amount can be optimized according to whether the battery can be charged at the destination, and the situation where the battery runs out of power during the round trip to the destination can be prevented.

[0023] Example 1

[0024] Structure of OTA system 1

[0025] Figure 1 The OTA system 1 shown mainly includes an electric vehicle 10, an external server 100, a portable terminal 200, and an external power source 300. Figure 1 The dotted line represents the signal line.

[0026] The electric vehicle 10 mainly includes a battery 11, a power converter 12, a motor 13 for driving, an ECU 14, a voltage sensor 20, a current sensor 21, a charger 24, a charging socket 23, a data communication device 26, a navigation device 40, and a panel 50. The battery 11 is a rechargeable secondary battery, specifically, a lithium-ion battery. The power converter 12 converts the DC power of the battery 11 into driving power (AC power) for the motor 13. The power converter 12 supplies driving power to the motor 13.

[0027] The electric vehicle 10 can receive power supply from the external power source 300 via the charging socket 23 and the charger 24. The charging cable 301 is connected to the main body of the external power source 300. The charging cable 301 has a connector 302 at the top. By connecting (inserting) the connector 302 to the charging socket 23, the electric vehicle 10 is in the plug-in state. In this way, the battery 11 can be plug-in charged.

[0028] The ECU 14 includes a CPU 15 and a memory 16. The memory 16 stores a control program 17. Actually, there are a plurality of control programs 17 according to each function. However, in this specification, one control program 17 is described.

[0029] Various controls in the ECU 14 are performed by the CPU 15 executing the control program 17 stored in the memory 16 .

[0030] The current sensor 21 measures the charge and discharge current of the battery 11 and sends the measurement data to the ECU 14. The voltage sensor 20 measures the voltage of the battery 11 and sends the measurement data to the ECU 14. The ECU 14 can obtain the state of charge (SOC) of the battery 11 using the charge and discharge current and the open circuit voltage (OCV) of the battery 11.

[0031] The data communication device 26 communicates various data with the external server 100 via the wireless communication 27. The data communication device 26 communicates various data with the portable terminal 200 via the short-distance wireless communication 28. An example of the short-distance wireless communication 28 is Bluetooth (registered trademark).

[0032] The navigation device 40 includes a CPU 41 and map data 42. The navigation device 40 can use the GPS signal to determine the position of the electric vehicle 10. The navigation device 40 is configured to perform a route search for finding a driving route (e.g., the shortest route) from the current position of the electric vehicle 10 to the destination, and display the driving route found by the route search on the panel 50.

[0033] The external server 100 is a server for each vehicle to perform an OTA-based update. The external server 100 is connected to each vehicle via wireless communication 27 so as to be able to communicate. The external server 100 includes a CPU 101 and a memory 102. An update program 110 is stored in the memory 102. The update program 110 is a program used to update the control program 17 stored in each vehicle. Whenever the control program 17 is updated, the update program 110 is registered in the memory 102. Whenever a new update program 110 is stored, the external server 100 sends an update notification to each vehicle via the wireless communication 27.

[0034] The update notification is information for requesting an update to the control program 17 stored in each vehicle. In addition, the update notification includes a priority flag. The priority flag is information indicating the level of urgency of the update. The level of urgency can be, for example, two levels, "high" and "low", or multiple levels of three or more. The level of urgency can be predetermined by the update manager or the user. For example, the update manager can also appropriately determine the level of urgency based on the content of the update. In addition, the user can also instruct the external server 100 to increase the urgency of the update related to the function he wants to use.

[0035] The portable terminal 200 is a device carried by the user of the electric vehicle 10. The portable terminal 200 may be various devices. For example, a smartphone, a tablet terminal, a notebook PC, a wearable device (e.g., a smart watch), etc. may be used as the portable terminal 200. In this embodiment, the case where the portable terminal 200 is a smartphone is described.

[0036] The portable terminal 200 mainly includes a CPU 201, a memory 202, and a touch panel 203. The memory 202 mainly stores a schedule application 211, a map application 212, and an update application 213. The schedule application 211 is an application for managing the user's schedule. For example, the user can pre-register a mobile schedule (destination, departure time, arrival time, etc.) in the schedule application 211. The map application 212 is an application for navigating the path to the destination in conjunction with the GPS. In addition, the map application 212 can also retrieve the location where the external power supply 300 is set. The update application 213 is an application for executing the update process of the control program. The specific content of the update process will be described later.

[0037] Update Processing

[0038] use Figure 2 The flowchart of 200 is used to explain the content of the update process. In this embodiment, the case where the portable terminal 200 is a vehicle control device is described. That is, the case where the portable terminal 200 performs the update process is described. Specifically, the CPU 201 reads the update application 213 from the memory 202 and executes it, thereby performing the update process. Figure 2 The process may be always executed while the portable terminal 200 is connected to the electric vehicle 10 for communication via the short-distance wireless communication 28. It should be noted that "step 10" will be abbreviated as "S10" hereinafter.

[0039] In S10, CPU 201 of mobile terminal 200 checks whether there is an update notification. CPU 201 monitors whether electric vehicle 10 receives an update notification from external server 100 via short-distance wireless communication 28. CPU 201 waits if no update notification is received (S10: No), and proceeds to S20 if received (S10: Yes).

[0040] In S20 , the CPU 201 determines whether the battery 11 of the electric vehicle 10 is being charged. The determination method may be various. For example, the charging state may be inquired of the ECU 14 via the short-distance wireless communication 28 .

[0041] If it is determined in S20 that the control unit is not charging (S20: No), the process proceeds to S110. In S110, the CPU 201 executes an update. Specifically, the CPU 201 sends an update instruction to the ECU 14 via the short-distance wireless communication 28. The ECU 14 that has received the update instruction receives the update program 110 from the external server 100 via the wireless communication 27. Then, the ECU 14 executes the received update program 110, thereby updating the control program 17. Then, the process returns to S10.

[0042] On the other hand, if it is determined in S20 that the battery is being charged (S20: YES), the process proceeds to S30. In S30, the CPU 201 checks the content of the priority flag included in the update notification. Specifically, the CPU 201 receives the update notification from the ECU 14 via the short-distance wireless communication 28. Then, the CPU 201 reads the priority flag in the update notification.

[0043] In S40, CPU 201 determines whether the urgency of the update is high. When the level of the urgency of the priority mark is higher than the range of the predetermined low level, CPU 201 determines that the urgency is high. In addition, when the level of the urgency of the priority mark is within the range of the predetermined low level, it is determined that the urgency is not high.

[0044] If it is determined in S40 that the urgency is high (S40: Yes), the process proceeds to S50. In S50, the CPU 201 performs a calculation process for the remaining charging time. Figure 3 An example of the subroutine processing performed in S50 is shown in FIG.

[0045] In S210, the CPU 201 calculates the update power amount. The update power amount is the power amount consumed by the electric vehicle 10 due to the update. Various methods can be used to calculate the update power amount. For example, the update power amount can also be calculated based on the estimated current amount and the estimated processing time in the update process. The estimated processing time can also be estimated based on the data size of the update program. In addition, for example, the update power amount can also be set to a predetermined value.

[0046] In S220, the CPU 201 calculates the required power. The required power is the amount of power that needs to be stored in the battery 11 after charging is completed. Various methods can be used to calculate the required power. For example, the required power can also be calculated based on the amount of power required to move to the destination.

[0047] The required power required to move to the destination can be calculated by various methods. For example, the update application 213 can also be linked with the schedule application 211 and the map application 212. The update application 213 can read the destination from the travel schedule registered in the schedule application 211. In addition, the update application 213 can calculate the driving distance to the read destination using the map application 212. In this way, the update application 213 can automatically calculate the required power required to move to the destination.

[0048] In S230, CPU 201 calculates the remaining charging time. The remaining charging time is the time required to charge the battery 11 with the minimum charging power from the external power source 300. The minimum charging power is the power required to be charged at the minimum. The minimum charging power is obtained by subtracting the stored power at the time of starting to charge the battery 11 from the total of the updated power and the required power. In other words, in order to move to the destination, the battery 11 needs to be charged for a charging time longer than the remaining charging time. Then, the process proceeds to S60 ( Figure 2 ).

[0049] In S60, CPU 201 notifies the user of the calculated remaining charging time. Various methods can be used as the notification method. For example, the remaining charging time can also be displayed on the touch panel 203 of the portable terminal 200. In addition, for example, the remaining charging time can also be displayed on the panel 50 of the electric vehicle 10 via short-range wireless communication 28. The display content can be various. For example, a message such as "Due to urgent software update, charging to ○○% requires ○○ minutes" can also be displayed. Then, regardless of whether charging is completed, enter S110 and perform the update. After the update is completed, return to S10. It should be noted that the content of S110 has been explained, so the explanation is omitted here.

[0050] On the other hand, in S40, if it is determined that the urgency is not high (S40: No), the process proceeds to S70. In S70, the CPU 201 prohibits the ECU 14 from executing the update during charging. This prohibition process can be executed by various methods. In this embodiment, the prohibition process is executed by waiting for the update instruction to be sent to the ECU 14 before the update start time arrives (S100: Yes).

[0051] In S80, CPU 201 reserves the update start time. The update start time can be any time after charging is completed. This is because, for updates that are not urgent, there is no problem even if the update is postponed. Preferably, the update start time is reserved during a time period when the user does not use the electric vehicle 10 or during the next charging period.

[0052] The update start time can be scheduled by various methods. It can also be automatically scheduled by the update application 213. For example, the update application 213 can also read the non-use time period of the electric vehicle 10 from the schedule registered in the schedule application program 211. Then, the update start time can also be set within the range of the non-use time period. Thus, it is possible to perform updates when the electric vehicle 10 is not in use. In addition, for example, the update application 213 can also read the parking position of the electric vehicle 10 during the non-use time period of the electric vehicle 10 from the schedule application 211, and read from the map application 212 whether there is an external power supply 300 at the parking position. Moreover, the update start time can also be set within the time period when the parking position where the external power supply 300 is parked for a long time. Thus, the update can be performed when there is enough charging time, so it can be fully charged even if the update power is consumed.

[0053] In S90, CPU 201 determines whether the current charging is completed. This determination can be made based on the charging status transmitted from ECU 14 via short-distance wireless communication 28. If charging is not completed (S90: No), the system waits, and if charging is completed (S90: Yes), the system proceeds to S100.

[0054] In S100, the CPU 201 determines whether the scheduled update start time has arrived. If it has not arrived (S100: No), the CPU 201 waits, and if it has arrived (S100: Yes), the CPU 201 proceeds to S110. The CPU 201 executes the update in S110. After the update is completed, the CPU 201 returns to S10.

[0055] Effect

[0056] The subject is explained. Since OTA-based software updates occur irregularly, OTA-based updates sometimes occur during the charging of the battery 11 of the electric vehicle 10. In this case, the power consumption caused by the update increases. Therefore, for example, when the battery 11 is charged to a predetermined target SOC, the charging time will be extended by a time corresponding to the updated power consumption. Due to the unexpected extension of the charging time, it may be disadvantageous to the user. Therefore, in the technology of the present specification, when an OTA-based update occurs during the charging of the battery 11, the urgency of the update can be determined (S40). Then, when the urgency is not high (S40: No), the update during charging can be prohibited (S70). That is, the update start timing can be optimized according to the urgency. As a result, compared with the case where the update is performed during charging, the situation where the charging time becomes longer can be suppressed.

[0057] In the technology of this specification, the minimum required charging time, i.e., the remaining charging time, can be calculated based on the updated power amount and the required power amount required to move to the destination (S230). Then, the calculated remaining charging time can be notified to the user (S60). Thus, the user can be prompted to optimize the charging time. (For example, if in a hurry, leave immediately after the remaining charging time has passed, and if there is room for spare time, charge for a time longer than the remaining charging time, etc.).

[0058] Example 2

[0059] In the second embodiment, a second method of the remaining charging time calculation process (S50) is described. In the second embodiment, only the difference from the first embodiment is described. Figure 4 An example of the second embodiment of the subroutine processing performed in S50 is shown in FIG.

[0060] In S310, the CPU 201 calculates the update power amount. The content of S310 is the same as that of the above-mentioned S210, so the description is omitted.

[0061] In S315, CPU 201 determines whether the battery can be charged at the destination. This determination can be performed by various methods. For example, the update application 213 can also be linked with the schedule application 211 and the map application 212. The update application 213 can read the departure time, destination, and stay time at the destination from the mobile schedule registered in the schedule application 211. In addition, the update application 213 can use the map application 212 to obtain the driving distance to the read destination and whether there is an external power supply 300 at the destination. Then, when there is an external power supply 300 at the destination and the stay time at the destination is more than a predetermined predetermined time, the update application 213 can determine that charging can be performed at the destination.

[0062] In S315, if it is determined that charging at the destination is possible (S315: Yes), the process proceeds to S320. In S320, the CPU 201 calculates the required power based on the power required for a one-way trip to the destination. This is because the power required for the return trip can be charged at the destination. Then, the process proceeds to S330.

[0063] On the other hand, in S315, if it is determined that charging at the destination is not possible (S315: No), the process proceeds to S325. In S325, the CPU 201 calculates the required power based on the power required for traveling to and from the destination. This is because the power required for the outbound and return trips needs to be charged at the current time point. Then, the process proceeds to S330.

[0064] In S330, CPU 201 calculates the remaining charging time. The contents of S330 are the same as those of S230, so the description is omitted. Then, the process proceeds to S60 ( Figure 2 ).

[0065] In S60, CPU 201 notifies the user of the calculated remaining charging time. At this time, when the departure time is determined, the charging amount when charging to the departure time may also be notified. For example, a message such as "It will take at least ○○ minutes of charging to charge. It can be charged to ○○%. If it is further charged for ○○ minutes before the departure time, it can be further charged to ○○%." may be displayed. It should be noted that the charging amount can be indicated by the percentage of SOC or the cruising distance.

[0066] The above detailed description of the implementation methods is provided, but these are merely examples and do not limit the claims. The technologies described in the claims include technologies obtained by various deformations and changes to the specific examples exemplified above. The technical elements described in this specification or drawings exert technical usefulness alone or in various combinations, and are not limited to the combinations described in the claims at the time of application. In addition, the technologies exemplified in this specification or drawings are technologies that achieve multiple purposes at the same time, and achieving one of the purposes itself has technical usefulness.

[0067] Modifications

[0068] The vehicle control device that performs the update process is not limited to the portable terminal 200, and can be various devices. For example, the external server 100 can also be a vehicle control device. In this case, the CPU 101 of the external server 100 can perform the update process by reading the update application from the memory 102 and executing it. In addition, for example, the ECU 14 of the electric vehicle 10 itself can also function as a vehicle control device. In this case, the CPU 15 of the ECU 14 can perform the update process by reading the update application from the memory 16 and executing it.

[0069] In S40, the method of determining the urgency of the update is not limited to the method using the flag, and various methods may be used. For example, a method of inquiring the external server 100 about the urgency may be used.

[0070] The method for executing the prohibition process of S70 is not limited to the method using the update start time. For example, S80 may be skipped, and the process may proceed to S110 based on the completion of charging in S90 to immediately execute the update. In addition, for example, in S70, an instruction may be sent to the ECU 14 to wait for the update for a predetermined time.

[0071] The method of connecting the portable terminal 200 and the electric vehicle 10 is not limited to the method via the short-distance wireless communication 28. For example, a wired connection may be used.

[0072] Instead of the map application 212 included in the portable terminal 200 , the navigation device 40 mounted on the electric vehicle 10 may be used.

Claims

1. A vehicle control device, the vehicle control device is a vehicle control device for controlling a vehicle, the vehicle is a vehicle having a battery that can be charged using an external power supply, a communication unit that can communicate various data with an external server through wireless communication, and an ECU that performs various controls based on a pre-stored control program, wherein: The vehicle control device is configured to: perform a process of detecting a request for updating the control program from the external server to the ECU while the battery is being charged by the external power supply; as well as The vehicle control device is configured to execute a process of prohibiting the ECU from executing the update during the charging when at least a part of the time when the request for the update is detected.

2. The vehicle control device according to claim 1, wherein: In the process of prohibiting the ECU, if the urgency of the update is within a predetermined low level range, execution of the update is prohibited.

3. The vehicle control device according to claim 2, wherein: The vehicle control device is configured to: when the updating is performed during the charging, further perform a process of calculating an updating power amount consumed by the vehicle due to the updating and a required power amount required by the battery thereafter; The vehicle control device is configured to further execute the following processing: calculate a remaining charging time required for charging the battery from the external power supply by subtracting the amount of stored electric power at the time of starting charging the battery from the total amount of the updated electric power and the required electric power; and The vehicle control device is configured to further execute a process of notifying a user of the calculated remaining charging time.

4. The vehicle control device according to claim 3, wherein: The required amount of electric power is the amount of electric power required to move to the destination.

5. The vehicle control device according to claim 4, wherein: The vehicle control device is configured to: determine whether the battery can be charged at the destination when the update is performed during the charging; The vehicle control device is configured to calculate the required electric power for a one-way trip to the destination when it is determined that charging is possible at the destination; and The vehicle control device is configured to calculate the required amount of electric power for traveling to and from the destination when it is determined that charging is not possible at the destination.

Images