Charging notification system and charging notification method

Abstract

This system provides a charging notification system that ensures sufficient power is available for software installation. [Solution] The charging notification system (gateway 10) includes a power consumption estimation unit 11 that estimates the amount of power consumption required to install software on equipment mounted on the vehicle, a charge amount prediction unit 12 that predicts the amount of charge to the battery mounted on the vehicle that will be generated by the vehicle's scheduled driving, a determination unit 13 that determines whether the estimated power consumption exceeds the post-charge energy amount, which is the amount of energy the battery will have when the predicted charge amount is reached, and a communication unit 15 that, if it is determined that the estimated power consumption exceeds the post-charge energy amount, prompts the user in the vehicle to drive to charge the battery.

Description

Technical Field

[0001] The present disclosure relates to a charging notification system and a charging notification method.

Background Art

[0002] Patent Document 1 discloses a technique for ensuring software update while suppressing power consumption of a vehicle battery.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in vehicles such as engine vehicles or hybrid vehicles that are difficult to charge when parked, in order to install software in devices such as an ECU (Electronic Control Unit) mounted on the vehicle, a certain amount or more of the remaining battery capacity of the battery mounted on the vehicle is required.

[0005] Therefore, the present disclosure provides a charging notification system and the like that can secure the amount of electric power required for software installation.

Means for Solving the Problems

[0006] The charging notification system according to this disclosure includes: a power consumption estimation unit that estimates the amount of power consumption required to install software on equipment mounted on a vehicle; a charge amount prediction unit that predicts the amount of charge to a battery mounted on the vehicle that will be generated by the vehicle's scheduled driving; a determination unit that determines whether the estimated power consumption exceeds the post-charge energy amount, which is the amount of energy the battery will have when the predicted charge amount is reached; and a communication unit that, if it is determined that the estimated power consumption exceeds the post-charge energy amount, prompts the user riding in the vehicle to drive to charge the battery.

[0007] The charging notification method relating to this disclosure is a charging notification method executed by a charging notification system, and includes the steps of: estimating the amount of power consumption required to install software on equipment mounted on a vehicle; predicting the amount of charge to a battery mounted on the vehicle that will be generated by the vehicle's scheduled driving; determining whether the estimated amount of power consumption exceeds the post-charge energy amount, which is the energy amount of the battery when the predicted amount of charge is reached; and, if it is determined that the estimated amount of power consumption exceeds the post-charge energy amount, prompting the user riding in the vehicle to drive to charge the battery.

[0008] These comprehensive or specific embodiments may be implemented as a system, method, integrated circuit, computer program, or recording medium such as a computer-readable CD-ROM, or as any combination of a system, method, integrated circuit, computer program, and recording medium. [Effects of the Invention]

[0009] According to a charging notification system or the like relating to one aspect of this disclosure, it is possible to secure the amount of power necessary for software installation. [Brief explanation of the drawing]

[0010] [Figure 1]This is a block diagram showing an example of the application of the charging notification system according to the embodiment. [Figure 2] This is a block diagram showing an example of a gateway according to an embodiment. [Figure 3] This sequence diagram shows an example of the operation of each device when a notification is issued prompting the vehicle to drive for charging. [Figure 4] This figure shows an example of a notification prompting you to drive to charge your device. [Figure 5] This is a sequence diagram showing an example of the operation of each device when notifying the driver of a driving route for charging. [Figure 6] This figure shows an example of a notification confirming whether or not guidance on a driving route for charging is required. [Figure 7] This sequence diagram shows an example of how each device operates when notifying a software installation interruption. [Figure 8] This figure shows an example of a notification regarding the interruption of software installation. [Figure 9] This flowchart shows an example of the operation of the gateway according to the embodiment when it issues a notification prompting the user to drive for charging. [Figure 10] This flowchart shows an example of the behavior of the gateway according to the embodiment when it notifies a software installation interruption. [Figure 11] This flowchart shows an example of the operation when updating the power consumption estimation method of the gateway according to the embodiment. [Figure 12] This flowchart shows an example of the operation of the gateway according to the embodiment when updating the method for predicting the charge amount. [Figure 13] This figure shows an example of data related to software installation held by the gateway according to the embodiment. [Modes for carrying out the invention]

[0011] The embodiments will be described in detail below with reference to the drawings.

[0012] Note that all the embodiments described below show comprehensive or specific examples. The numerical values, shapes, materials, components, arrangement positions and connection forms of the components, steps, order of steps, etc. shown in the following embodiments are merely examples and are not intended to limit the present disclosure.

[0013] (Embodiment) Hereinafter, a charging notification system according to an embodiment will be described.

[0014] FIG. 1 is a block diagram showing an application example of a charging notification system according to an embodiment.

[0015] For example, the charging notification system is a system mounted on the vehicle 100. The vehicle 100 is a vehicle such as an engine vehicle or a hybrid vehicle, and it is difficult to charge when parked. For example, the vehicle 100 includes a gateway 10, a car navigation system 20 (hereinafter referred to as car navigation 20), an HMI (Human Machine Interface) 30, a battery ECU 40, and a plurality of ECUs 50. The gateway 10 is an example of the charging notification system. The HMI 30 includes, for example, a display such as an LCD (Liquid Crystal Display) and an input device such as a touch panel. The HMI 30 is an example of a display device mounted on the vehicle 100. A battery (not shown) is mounted on the vehicle 100 and is controlled by the battery ECU 40.

[0016] The gateway 10 and the car navigation 20 communicate with the server 200 and the user terminal 300 via a network. For example, the gateway 10 is an HPC (High Performance Computer). For example, the server 200 is a server that manages the ECU 50 of the vehicle 100. For example, the user terminal 300 is a terminal such as a smartphone or a tablet of the user of the vehicle 100.

[0017] Next, the configuration of the charging notification system (gateway 10) will be described with reference to FIG. 2.

[0018] Figure 2 is a block diagram showing an example of a gateway 10 according to an embodiment.

[0019] The gateway 10 comprises a power consumption estimation unit 11, a charge amount prediction unit 12, a determination unit 13, an update monitoring unit 14, and a communication unit 15. The gateway 10 is a computer including a processor (microprocessor), memory, and a communication interface. The memory is ROM (Read Only Memory) and RAM (Random Access Memory), and can store programs executed by the processor. The power consumption estimation unit 11, the charge amount prediction unit 12, the determination unit 13, and the update monitoring unit 14 are implemented by the processor, etc., which executes programs stored in memory. The communication unit 15 is implemented by a communication interface having a communication circuit and an antenna, etc.

[0020] For example, the charging notification system may be a computer (device) in a single enclosure, or it may be a system consisting of multiple computers. For example, the car navigation system 20, HMI 30, or ECU 50 may have the functionality of a charging notification system, or the components of the charging notification system may be distributed across at least two of the gateway 10, car navigation system 20, HMI 30, and ECU 50. Alternatively, for example, the charging notification system may be a server 200. The components of the charging notification system may be located on a single server 200, or they may be distributed across multiple servers. Furthermore, for example, the charging notification system may be a user terminal 300.

[0021] The power consumption estimation unit 11 estimates the power consumption required to install software on the equipment mounted on the vehicle 100. The equipment mounted on the vehicle 100 is, for example, the ECU 50. However, this equipment is not limited to the ECU 50; it may be any other equipment mounted on the vehicle 100 besides the ECU 50. Details of the operation of the power consumption estimation unit 11 will be described later.

[0022] The charge amount prediction unit 12 predicts the amount of charge to the battery mounted on the vehicle 100 that will be generated by the vehicle 100's planned driving. The battery mounted on the vehicle 100 is used to supply power to the vehicle 100's electrical system and to start the engine, etc. The battery mounted on the vehicle 100 is charged by a generator mounted on the vehicle 100 while the vehicle 100 is running. Details of the operation of the charge amount prediction unit 12 will be described later.

[0023] The determination unit 13 determines whether the estimated power consumption exceeds the post-charge energy, which is the amount of energy the battery will have when the predicted charge amount is reached. In other words, the determination unit 13 determines whether the power consumption required for software installation exceeds the amount of energy the battery will have when charged by the vehicle 100's planned driving.

[0024] The update monitoring unit 14 interrupts the software installation and notifies the user of the vehicle 100 if the battery level falls below a predetermined level during the installation. Details of the operation of the update monitoring unit 14 will be described later.

[0025] If the communication unit 15 determines that the estimated power consumption exceeds the power consumption after charging, it prompts the user in the vehicle 100 to drive to charge the battery. Details of the operation of the communication unit 15 will be described later.

[0026] Next, the operation of the gateway 10, battery ECU 40, car navigation system 20, and HMI 30 when issuing a notification prompting the vehicle to drive for charging will be explained using Figure 3.

[0027] Figure 3 is a sequence diagram showing an example of the operation of each device when a notification is issued prompting the vehicle to drive for charging.

[0028] First, Gateway 10 downloads the software for ECU 50 from Server 200. Next, Gateway 10 checks the amount of data of the downloaded software and estimates the amount of power consumption required for installation from the data of ECU 50 on which the downloaded software will be installed.

[0029] Next, Gateway 10 instructs Battery ECU 40 to check the battery level. Battery ECU 40 checks the battery level and notifies Gateway 10 of the battery level. Next, Gateway 10 instructs Car Navigation System 20 to check the planned driving distance. Car Navigation System 20 checks the planned driving distance and notifies Gateway 10 of the planned driving distance.

[0030] Next, the gateway 10 determines whether further charging of the battery is necessary. In other words, it determines whether further charging of the battery is required even after the vehicle 100 has traveled the planned distance. For example, if further charging of the battery is required, it sends a notification to the HMI 30 prompting it to drive to charge the battery. The HMI 30 displays content corresponding to the notification.

[0031] Figure 4 shows an example of a notification prompting the driver to drive for charging. For example, if the HMI 30 displays content as shown in Figure 4, the user riding in vehicle 100 will understand that they need to drive vehicle 100 a longer distance than the planned driving distance. This allows the user to drive vehicle 100 until the battery power exceeds the power consumption required for software installation, thereby allowing the battery to be charged.

[0032] Furthermore, when prompting the user to drive for charging, the gateway 10 may notify the user of the driving route for charging. The operation of the gateway 10, car navigation system 20, and HMI 30 when notifying the user of the driving route for charging will be explained with reference to Figure 5.

[0033] Figure 5 is a sequence diagram showing an example of the operation of each device when notifying the driver of a driving route for charging. Figure 5 is a sequence diagram showing an example of the operation of each device after the gateway 10 has determined whether further charging of the battery is necessary.

[0034] If the gateway 10 requires further charging of the battery, it will notify the HMI 30 to prompt it to drive to charge the battery, and will ask whether it needs guidance on a driving route for charging. The HMI 30 will then display the content corresponding to the notification.

[0035] Figure 6 shows an example of a notification confirming whether or not guidance on a driving route for charging is needed. For example, if the HMI 30 displays content as shown in Figure 6, a user riding in vehicle 100 can select "Yes" displayed on the HMI 30 if they want to know the driving route for charging, and the driving route will be displayed on the car navigation system 20, etc.

[0036] The user, via the HMI30, notifies the gateway 10 of their confirmation and requests guidance on a driving route for charging. The gateway 10 notifies the car navigation system 20 of the driving distance required for the battery power to exceed the power consumption required for software installation after driving. The car navigation system 20 calculates a driving route based on the notified distance and notifies the user of the calculated driving route. This allows the user to confirm exactly what driving route to take in order to charge the battery to the required amount.

[0037] Note that during software installation, the battery level may become low, preventing the installation from continuing. In such cases, the user may be notified that the installation has been interrupted. The operation of the gateway 10, battery ECU 40, ECU 50, and user terminal 300 when notifying the user of the interruption of software installation will be explained with reference to Figure 7.

[0038] Figure 7 is a sequence diagram showing an example of the operation of each device when notifying a software installation interruption.

[0039] Gateway 10 prompts ECU 50, where the software is installed, to check the software installation status, and ECU 50 notifies Gateway 10 of the installation status. Gateway 10 monitors the installation status to confirm that the installation is proceeding as planned.

[0040] Next, Gateway 10 prompts Battery ECU 40 to check the battery level, and Battery ECU 40 notifies Gateway 10 of the battery level. Gateway 10 then determines whether to interrupt the installation based on the current installation status and the current battery level. For example, if Gateway 10 determines that the battery will run out before the installation is completed if it continues, it decides to interrupt the installation and notifies User Terminal 300 of the interruption. User Terminal 300 then displays information corresponding to the notification.

[0041] Figure 8 shows an example of a notification indicating that software installation has been interrupted. For example, the user can confirm that the installation has been interrupted by seeing content similar to that shown in Figure 8 on the user terminal 300.

[0042] Since the software installation is performed when the vehicle 100 is stopped, it often occurs when the user is not inside the vehicle 100. Therefore, Figure 7 shows an example in which the user terminal 300 is notified of the installation interruption. However, even when the vehicle 100 is stopped, the user may still be inside the vehicle 100, so the HMI 30 may also be notified of the installation interruption.

[0043] Next, the operation of gateway 10 will be explained in detail using Figures 9 to 12.

[0044] First, the operation of the gateway 10 when it issues a notification prompting the vehicle to drive for charging will be explained using Figure 9.

[0045] Figure 9 is a flowchart showing an example of the operation of the gateway 10 according to the embodiment when it issues a notification prompting the user to drive for charging.

[0046] First, the communication unit 15 acquires battery level data, software data to be downloaded, and driving distance data (step S11). For example, the communication unit 15 acquires battery level data from the battery ECU 40, software data to be downloaded from the server 200, and driving distance data from the car navigation system 20.

[0047] Next, the power consumption estimation unit 11 estimates the power consumption required for software installation based on the amount of data of the downloaded software and the data of the ECU 50 (step S12). For example, the power consumption estimation unit 11 estimates that the more data of the downloaded software, the more power consumption is required for software installation. Also, the power consumption required for software installation varies depending on the type of ECU 50 on which the software is installed. Therefore, the power consumption estimation unit 11 estimates the power consumption required for software installation by determining the type of ECU 50 from the data of the ECU 50.

[0048] The power consumption estimation unit 11 may also construct a calculation formula for estimating power consumption from the operating parameters of the SoC (System on a Chip) for the software update. Examples of operating parameters include the number of instructions executed and usage rate per unit time of the CPU, the number of memory accesses and usage rate per unit time of memory, or the number of I / O inputs and outputs per unit time of I / O. In addition, the power consumption estimation unit 11 may estimate the power consumption required for the software installation based on the actual power consumption required for past software installations.

[0049] Next, the charge amount prediction unit 12 obtains the planned driving distance data (planned driving distance data) of the vehicle 100 from the car navigation system 20 installed in the vehicle 100 via the communication unit 15, and predicts the amount of charge generated by the planned driving of the vehicle 100 based on this distance data (step S13). Since the car navigation system 20 has the driving route that the vehicle 100 is scheduled to travel in the future set, distance data of the driving route that the vehicle 100 will travel in the future can be obtained from the car navigation system 20. Therefore, by using the car navigation system 20, the amount of charge generated by future driving can be easily predicted.

[0050] Furthermore, the charge amount prediction unit 12 does not necessarily have to predict the charge amount based on the planned driving distance data obtained from the car navigation system 20. For example, the charge amount prediction unit 12 may obtain the location information and driving history information of the vehicle 100, and predict the charge amount generated by the planned driving of the vehicle 100 based on the location information and driving history information. Users may drive the vehicle 100 along the same route each time when commuting or shopping. Therefore, by checking the driving history information to see what driving routes have been taken in the past from the current location of the vehicle 100, it is possible to estimate what driving routes the user will take in the future. Therefore, the charge amount prediction unit 12 can predict the charge amount based on the distance data of the estimated driving route.

[0051] Next, the determination unit 13 estimates the remaining battery level after charging based on the battery level data and the predicted charge amount (step S14). In other words, the determination unit 13 estimates the remaining battery level when the predicted charge amount is charged to the current battery level.

[0052] Next, the determination unit 13 determines whether or not extra charging is required for software installation (step S15). If the estimated power consumption exceeds the power consumption after charging, the determination unit 13 determines that extra charging is required for software installation. If it is determined that extra charging is not required for software installation (No in step S15), the process ends.

[0053] If the communication unit 15 determines that extra charging is required for software installation (Yes in step S15), it sends display data to the HMI 30 to prompt the user in the vehicle 100 to drive to charge the battery (step S16). For example, the communication unit 15 may prompt the user to drive to charge the battery by displaying a driving route on the HMI 30 such that the battery power exceeds the estimated power consumption after the drive. This allows the user to drive the vehicle 100 so that the battery power exceeds the estimated power consumption by looking at the displayed driving route.

[0054] Next, we will explain the operation of the gateway 10 (specifically, the update monitoring unit 14) when it notifies of an interruption in software installation, using Figure 10.

[0055] Figure 10 is a flowchart illustrating an example of the operation of the gateway 10 according to the embodiment when it notifies a software installation interruption. In the explanation in Figure 10, it is assumed that software installation is being performed on multiple ECUs 50 simultaneously.

[0056] The update monitoring unit 14 obtains the software installation status to the ECU 50 (step S21) and estimates the power consumption required to install the remaining data that has not yet been installed (step S22). If half of the total data to be installed has not yet been installed, the power consumption required to install the remaining data can be estimated as half of the estimated power consumption for all data.

[0057] Next, the update monitoring unit 14 acquires battery level data (step S23) and determines whether there is insufficient battery power to install the remaining data (step S24). The update monitoring unit 14 determines that there is insufficient battery power to install the remaining data if the amount of power consumed to install the remaining data exceeds the amount of battery power. If it is determined that there is insufficient battery power to install the remaining data (No in step S24), the process ends.

[0058] If the update monitoring unit 14 determines that there is insufficient battery power to install the remaining data (Yes in step S24), it determines which software (ECU 50) to interrupt the installation of (step S25). For example, if multiple software programs are being installed, the update monitoring unit 14 determines which software to interrupt the installation of based on the priority of the software, the age of the data to be installed, the amount of data that has not yet been installed, or the remaining battery level. For example, it can interrupt the installation of software with a low priority, software with newer data to be installed, software with a large amount of data that has not yet been installed, or software that cannot be completed with the current battery level.

[0059] If software installation is being performed on only one ECU50, the software installation on that ECU50 will be interrupted.

[0060] Then, the update monitoring unit 14 sends data to the user terminal 300 via the communication unit 15 indicating that the software installation will be interrupted (step S26).

[0061] Thus, the update monitoring unit 14 may interrupt the installation and notify the user if the battery level falls below a predetermined level during software installation. This allows the user to be aware that the installation has been interrupted.

[0062] Next, the operation of the gateway 10 (specifically, the power consumption estimation unit 11) when updating the power consumption estimation method will be explained using Figure 11.

[0063] Figure 11 is a flowchart showing an example of the operation of the gateway 10 according to the embodiment when updating the power consumption estimation method.

[0064] First, the power consumption estimation unit 11 acquires battery capacity data for each ECU 50 before and after software installation (step S31). This allows the power consumption estimation unit 11 to calculate the amount of power actually consumed by each ECU 50 due to software installation.

[0065] Next, the power consumption estimation unit 11 compares the estimated power consumption required for installing the software of a given ECU 50 with the power consumption actually consumed by the software installation of the ECU 50 (step S32), and determines whether the difference between the estimated power consumption and the actual power consumption is within a predetermined value (step S33). The predetermined value is not particularly limited and can be set as appropriate.

[0066] If the power consumption estimation unit 11 determines that the difference between the estimated power consumption and the actual power consumption is greater than a predetermined value (No in step S33), it updates the power consumption estimation method (step S34). For example, if the power consumption estimation unit 11 determines that the estimated power consumption is greater than the actual power consumption, it updates the estimation method so that the estimated power consumption is smaller, and if the estimated power consumption is smaller than the actual power consumption, it updates the estimation method so that the estimated power consumption is larger.

[0067] If the power consumption estimation unit 11 determines that the difference between the estimated power consumption and the actual power consumption is within a predetermined value (Yes in step S33), the processing in step S34 is not performed, and the processing in step S35 is performed.

[0068] Next, the power consumption estimation unit 11 determines whether or not it has performed a comparison check (specifically, the process from step S32) between the estimated power consumption and the actual power consumption for all ECUs 50 (step S35). If there are any ECUs 50 for which the above check has not been performed (No in step S35), the process from step S32 is performed for those ECUs 50. If the above check has been performed for all ECUs 50 (Yes in step S35), the process ends.

[0069] Thus, the power consumption estimation unit 11 determines whether the difference between the estimated power consumption and the power consumption actually consumed by the software installation is within a predetermined value, and if the difference is greater than the predetermined value, it may update the power consumption estimation method. If the estimated power consumption deviates from the actual value, the accuracy of determining whether the estimated power consumption exceeds the power consumption after charging will deteriorate, and if a misdetermination occurs, there is a risk that the power required for software installation will not be secured. Therefore, if the estimated power consumption deviates from the actual value, the deviation can be corrected, and it is possible to prevent the inability to secure the power required for software installation during the next installation.

[0070] Next, the operation of the gateway 10 (specifically, the charge amount prediction unit 12) when updating the charge amount prediction method will be explained using Figure 12.

[0071] Figure 12 is a flowchart showing an example of the operation of the gateway 10 according to the embodiment when updating the method for predicting the charge amount.

[0072] First, the charge amount prediction unit 12 obtains the actual charge amount when the vehicle 100 has performed its planned run (step S41), and determines whether the difference between the predicted charge amount and the actual charge amount is within a predetermined value (step S42). The predetermined value is not particularly limited and can be set as appropriate.

[0073] If the charge amount prediction unit 12 determines that the difference between the predicted charge amount and the actual charge amount is greater than a predetermined value (No in step S42), it updates the prediction method for the predicted charge amount (step S43). For example, if the predicted charge amount is greater than the actual charge amount, the charge amount prediction unit 12 updates the prediction method to make the predicted charge amount smaller, and if the predicted charge amount is smaller than the actual charge amount, it updates the prediction method to make the predicted charge amount larger.

[0074] If it is determined that the difference between the predicted charge amount and the actual charge amount is within a predetermined value (Yes in step S42), or after step S43, the process ends.

[0075] Thus, the charge amount prediction unit 12 determines whether the difference between the predicted charge amount and the actual charge amount to the battery generated by the planned driving of the vehicle 100 is within a predetermined value, and if the difference is greater than the predetermined value, it may update the method for predicting the charge amount. If the predicted charge amount deviates from the actual value, the accuracy of determining whether the estimated power consumption exceeds the post-charge power amount will deteriorate, and if a misdetermination occurs, there is a risk that the power amount necessary for software installation will not be secured. Therefore, if the predicted charge amount deviates from the actual value, the deviation can be corrected, and it is possible to prevent the inability to secure the power amount necessary for software installation during the next installation.

[0076] The gateway 10 may also maintain data as shown in Figure 13. Figure 13 is a diagram showing an example of data related to software installation maintained by the gateway 10 according to the embodiment. As shown in Figure 13, the gateway 10 may manage the version of the software to be installed, the address of the ECU 50 on which the software is installed, the data size of the software to be installed, the power forecast value (estimated power consumption), the software priority, the software installation status, the software activation status, or the date and time of software download.

[0077] As explained above, for example, software installation on equipment such as the ECU 50 mounted on vehicle 100 is performed when vehicle 100 is not in use and is stationary, but software installation requires a certain amount of power. Vehicles such as electric vehicles can charge the battery mounted on the vehicle when stationary, so they can secure the power necessary for software installation. On the other hand, vehicles such as engine vehicles or hybrid vehicles 100 cannot charge the battery mounted on the vehicle 100 when stationary, so they may not be able to secure the power necessary for software installation. Therefore, in this disclosure, the amount of charge generated by the planned driving of vehicle 100 is predicted, and it is determined whether the amount of power consumed to install the software exceeds the amount of power of the battery after charging. In other words, it is determined whether the amount of power consumed to install the software exceeds the amount of power of the battery when it is charged by the planned driving of vehicle 100. If the amount of power consumed to install the software exceeds the amount of power of the battery when it is charged by the planned driving of vehicle 100, the software installation cannot be completed, and the user is prompted to drive to charge the battery. In other words, the user is prompted to drive a longer distance than the planned driving of vehicle 100. This ensures that the necessary power is available for software installation.

[0078] (Other embodiments) As described above, embodiments have been explained as examples of the technology relating to this disclosure. However, the technology relating to this disclosure is not limited thereto and can be applied to embodiments that have been modified, replaced, added to, or omitted as appropriate. For example, the following modified examples are also included in one embodiment of this disclosure.

[0079] For example, in the above embodiment, an example was described in which the charging notification system includes an update monitoring unit 14, but the charging notification system does not necessarily have to include an update monitoring unit 14.

[0080] For example, this disclosure can be implemented not only as a charging notification system, but also as a charging notification method that includes steps (processes) performed by the components constituting the charging notification system.

[0081] The charging notification method is a charging notification method executed by a charging notification system, and as shown in Figure 9, includes the steps of: estimating the amount of power consumption required to install software on equipment mounted on the vehicle (step S12); predicting the amount of charge to the battery mounted on the vehicle due to the vehicle's scheduled driving (step S13); determining whether the estimated power consumption exceeds the post-charge energy amount, which is the amount of energy the battery will have when the predicted charge amount is reached (step S15); and if it is determined that the estimated power consumption exceeds the post-charge energy amount (Yes in step S15), prompting the user in the vehicle to drive to charge the battery (step S16).

[0082] For example, this disclosure can be implemented as a program that causes a computer (processor) to execute the steps included in the charging notification method. Furthermore, this disclosure can be implemented as a non-temporary computer-readable recording medium, such as a CD-ROM, on which the program is recorded.

[0083] For example, if this disclosure is implemented in a program (software), each step is executed by the program using hardware resources such as the computer's CPU, memory, and input / output circuits. In other words, each step is executed by the CPU obtaining data from memory or input / output circuits, performing calculations, and outputting the calculation results to memory or input / output circuits.

[0084] In the above embodiment, each component included in the charging notification system may be implemented by dedicated hardware or by executing a software program suitable for each component. Each component may also be implemented by a program execution unit such as a CPU or processor reading and executing a software program recorded on a recording medium such as a hard disk or semiconductor memory.

[0085] Some or all of the functions of the charging notification system according to the above embodiment are typically implemented as an LSI (Large-Scale Integrated Circuit). These may be individually integrated into a single chip, or some or all of them may be integrated into a single chip. Furthermore, the implementation is not limited to an LSI; it may also be implemented using a dedicated circuit or a general-purpose processor. An FPGA (Field Programmable Gate Array), which can be programmed after the LSI is manufactured, or a reconfigurable processor that allows for the reconfiguration of the connections and settings of the circuit cells inside the LSI may also be used.

[0086] Furthermore, if advances in semiconductor technology or other derived technologies lead to the emergence of integrated circuit technologies that replace LSIs, then naturally, those technologies may be used to integrate each component included in the charging notification system.

[0087] Furthermore, this disclosure also includes forms obtained by applying various modifications to the embodiments that a person skilled in the art could conceive, and forms realized by arbitrarily combining the components and functions of each embodiment without departing from the spirit of this disclosure.

[0088] (Note) Based on the above description of embodiments, the following technologies are disclosed.

[0089] (Technology 1) A charging notification system comprising: a power consumption estimation unit that estimates the amount of power consumption required to install software on equipment mounted on a vehicle; a charge amount prediction unit that predicts the amount of charge to a battery mounted on the vehicle that will be generated by the vehicle's scheduled driving; a determination unit that determines whether the estimated power consumption exceeds the post-charge energy amount, which is the amount of energy the battery will have when the predicted charge amount is charged; and a communication unit that, if it is determined that the estimated power consumption exceeds the post-charge energy amount, prompts the user riding in the vehicle to drive to charge the battery.

[0090] For example, software installation on devices such as ECUs installed in a vehicle is performed when the vehicle is stationary and not in use, but software installation requires a certain amount of power. Vehicles such as electric vehicles can charge their batteries when stationary, thus securing the power necessary for software installation. On the other hand, vehicles such as engine-powered vehicles or hybrid vehicles cannot charge their batteries when stationary, and may not be able to secure the power necessary for software installation. Therefore, in this disclosure, the amount of charge generated by the vehicle's planned driving is predicted, and it is determined whether the amount of power consumed for software installation exceeds the amount of power in the battery after charging. In other words, it is determined whether the amount of power consumed for software installation exceeds the amount of power in the battery when charged by the vehicle's planned driving. If the amount of power consumed for software installation exceeds the amount of power in the battery when charged by the vehicle's planned driving, the software installation cannot be completed, and the user is prompted to drive to charge the battery. In other words, the user is prompted to drive a longer distance than the vehicle's planned driving distance. This ensures that the amount of power necessary for software installation is secured.

[0091] (Technology 2) The charging amount prediction unit obtains data on the planned distance traveled by the vehicle from a car navigation system installed in the vehicle, and predicts the charging amount based on the distance data, the charging notification system according to Technology 1.

[0092] According to this, the amount of charge generated by future driving can be easily predicted by using a car navigation system.

[0093] (Technology 3) The charging notification system according to Technology 1 or 2, wherein the communication unit prompts the user to drive to charge the battery by displaying on a display device mounted on the vehicle a driving route in which the amount of power of the battery exceeds the estimated amount of power consumption after driving.

[0094] According to this, by viewing the displayed driving route, users can drive the vehicle in a way that the battery power exceeds the estimated power consumption.

[0095] (Technology 4) The charging notification system according to any one of Technologies 1 to 3, further comprising an update monitoring unit that interrupts the installation and notifies the user when the remaining battery level falls below a predetermined level during software installation.

[0096] According to this, the user can be aware that the installation was interrupted.

[0097] (Technology 5) The charging notification system according to Technology 4, wherein the update monitoring unit determines which software to interrupt the installation of based on the priority of the software, the age of the data to be installed, the amount of data not yet installed, or the remaining battery level, when multiple software programs are being installed.

[0098] For example, you can interrupt the installation of low-priority software, software with new data to install, software with a large amount of uninstalled data, or software that cannot be installed completely with the current battery level.

[0099] (Technology 6) The charging notification system according to any one of Technologies 1 to 5, wherein the power consumption estimation unit determines whether the difference between the estimated power consumption and the power consumption actually consumed by the software installation is within a predetermined value, and updates the power consumption estimation method if the difference is greater than the predetermined value.

[0100] If the estimated power consumption deviates from the actual value, the accuracy of determining whether the estimated power consumption exceeds the amount of power after charging will decrease, and if a misjudgment occurs, there is a risk that the amount of power required for software installation will not be secured. Therefore, if the estimated power consumption deviates from the actual value, the deviation can be corrected, and the inability to secure the amount of power required for software installation during the next installation can be prevented.

[0101] (Technical 7) The charging amount prediction unit determines whether the difference between the predicted charging amount and the amount of charge actually generated to the battery by the planned driving of the vehicle is within a predetermined value, and if the difference is greater than the predetermined value, updates the method for predicting the charging amount, as described in any of Technical 1 to 6.

[0102] If the predicted charge amount deviates from the actual value, the accuracy of determining whether the estimated power consumption exceeds the post-charge power amount will decrease, and if a misjudgment occurs, there is a risk that the power required for software installation will not be secured. Therefore, if the predicted charge amount deviates from the actual value, the deviation can be corrected, and the inability to secure the power required for software installation during the next installation can be prevented.

[0103] (Technical 8) A charging notification method performed by a charging notification system, comprising: estimating the amount of power consumption required to install software on equipment mounted on a vehicle; predicting the amount of charge to a battery mounted on the vehicle resulting from the vehicle's scheduled driving; determining whether the estimated power consumption exceeds the post-charge energy amount, which is the energy amount of the battery when the predicted charge amount is charged; and, if it is determined that the estimated power consumption exceeds the post-charge energy amount, prompting the user riding in the vehicle to drive to charge the battery.

[0104] This allows for a charging notification method that ensures sufficient power is available for software installation. [Industrial applicability]

[0105] This disclosure is applicable to vehicles such as gasoline-powered vehicles or hybrid vehicles. [Explanation of symbols]

[0106] 10 Gateways 11. Power Consumption Estimation Section 12 Charge level prediction unit 13 Judgment section 14 Update Monitoring Department 15 Communications Department 20 Car Navigation 30 HMI 40 Battery ECU 50 ECU 100 vehicles 200 servers 300 user terminals

Claims

1. A power consumption estimation unit that estimates the amount of power consumption required to install software on equipment mounted on the vehicle, A charge amount prediction unit predicts the amount of charge to the battery mounted on the vehicle that will be generated by the scheduled driving of the vehicle, A determination unit that determines whether the estimated power consumption, which is the estimated amount of power consumption, exceeds the post-charge energy amount, which is the amount of energy in the battery when the predicted charge amount, which is the predicted charge amount, is charged. The system includes a communication unit that, when it is determined that the estimated power consumption exceeds the power consumption after charging, prompts the user riding in the vehicle to drive to charge the battery. Charging notification system.

2. The charge amount prediction unit obtains data on the planned distance traveled by the vehicle from the car navigation system installed in the vehicle, and predicts the charge amount based on the distance data. The charging notification system according to claim 1.

3. The communication unit prompts the user to drive to charge the battery by displaying a driving route on the vehicle's display device that, after driving, will cause the battery's energy output to exceed the estimated power consumption. The charging notification system according to claim 1.

4. The charging notification system includes an update monitoring unit that interrupts the installation and notifies the user if the battery level falls below a predetermined level during software installation. A charging notification system according to any one of claims 1 to 3.

5. The update monitoring unit, when multiple software programs are being installed, determines which software to interrupt the installation of based on the priority of the software, the age of the data to be installed, the amount of data not yet installed, or the remaining battery level. The charging notification system according to claim 4.

6. The power consumption estimation unit determines whether the difference between the estimated power consumption and the power consumption actually consumed by the software installation is within a predetermined value, and if the difference is greater than the predetermined value, it updates the power consumption estimation method. A charging notification system according to any one of claims 1 to 3.

7. The charge amount prediction unit determines whether the difference between the predicted charge amount and the actual charge amount to the battery generated by the vehicle's planned driving is within a predetermined value, and if the difference is greater than the predetermined value, it updates the method for predicting the charge amount. A charging notification system according to any one of claims 1 to 3.

8. A charging notification method performed by a charging notification system, The steps include: estimating the power consumption required for installing software on equipment installed in the vehicle, A step of predicting the amount of charge to the battery installed in the vehicle that will be generated by the scheduled driving of the vehicle, The steps include determining whether the estimated power consumption, which is the estimated amount of power consumption, exceeds the post-charge energy amount, which is the amount of energy in the battery when the predicted charge amount, which is the predicted charge amount, is charged, If it is determined that the estimated power consumption exceeds the power consumption after charging, the step includes prompting the user in the vehicle to drive to charge the battery. Charging notification method.

Images