JP7779780B2 - Management device and information processing method - Google Patents

Description

The present invention relates to a management device and an information processing method.

In recent years, research and development has been conducted into secondary batteries that contribute to energy efficiency, as well as charging systems for vehicles equipped with secondary batteries, in order to ensure that more people have access to affordable, reliable, sustainable, and advanced energy.

Patent Document 1 discloses a technology that issues instructions to charge the auxiliary battery of a vehicle that is turned off, such as when parked, based on the stored auxiliary battery status, without constantly monitoring the vehicle's status. Furthermore, Patent Document 2 discloses a technology that branches off the main electrical circuit from a smart meter to connect the electric vehicle's charging device to a residential distribution board, and notifies the charging status via communication to a mobile device, so that the charging status can be monitored even when away from home and the charging current to the electric vehicle can be controlled.

Japanese Patent Application Laid-Open No. 2021-83157 JP 2018-182853 A

In technologies related to secondary batteries and charging/supplying to vehicles equipped with secondary batteries, the sub-battery is supplementally charged using power from the main battery. However, frequent supplemental charging to prevent the battery from running out of power consumes power from the main battery, which can result in a reduced driving range (AER).

To solve the above problem, the present application aims to prevent battery death while minimizing the consumption of the vehicle's main battery by asking the user whether or not supplemental charging from the main battery to the sub-battery is possible before carrying out supplemental charging. This will ultimately contribute to energy efficiency.

According to the present invention,
A management device for managing a remaining charge of a sub-battery of a vehicle having a main battery and a sub-battery,
a remaining charge information acquisition means for acquiring remaining charge information of the sub-battery at the time when the vehicle starts to be parked;
a prediction unit for predicting a timing at which the remaining charge of the sub-battery will fall below a threshold while the vehicle is parked, based on the remaining charge information;
a transmitting means for transmitting an inquiry to a user terminal as to whether or not to supplementarily charge the sub-battery using power from the main battery at a timing before the remaining charge reduction timing predicted by the predicting means;
The transmission means transmits information regarding the supplemental charging to the user terminal together with the inquiry, and the information regarding the supplemental charging is the vehicle's traveling distance, which varies depending on the implementation of the supplemental charging .

According to the present invention, by asking the user whether or not supplemental charging from the main battery to the sub-battery is possible before supplemental charging is performed, it is possible to prevent battery death while suppressing wear on the vehicle's main battery.

1 is a diagram showing an example of a sub-battery remaining charge management system according to an embodiment of the present invention; FIG. 2 is a block diagram showing an example of a hardware configuration of a server that is a management device. FIG. 2 is a block diagram showing an example of a hardware configuration of a vehicle. FIG. 10 is a diagram showing an example of a GUI displayed on a terminal according to an embodiment. 10 is a flowchart illustrating an example of processing by a management device according to an embodiment.

The following embodiments are described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the scope of the claimed invention, and not all combinations of features described in the embodiments are necessarily essential to the invention. Two or more of the multiple features described in the embodiments may be combined in any desired manner. Furthermore, the same reference numbers are used for identical or similar components, and duplicate descriptions will be omitted.

A management device according to one embodiment of the present invention manages the remaining charge of the sub-battery of a vehicle having a main battery and a sub-battery. In particular, the management device according to this embodiment acquires information about the remaining charge of the sub-battery when the vehicle begins parking, and predicts the timing at which the remaining charge of the sub-battery will fall below a threshold while the vehicle is parked based on the acquired information. The management device then sends an inquiry to the user terminal prior to the predicted timing at which the remaining charge will fall, asking whether or not to supplementally charge the sub-battery using power from the main battery. In this embodiment, the management device is a server that acquires various information from the vehicle and predicts the timing at which the remaining charge will fall, but this is merely an example and the present invention is not limited to this configuration.

[system]
A system including a management device according to this embodiment will be described below with reference to Fig. 1. Fig. 1 shows a management system that sets the timing for supplemental charging of a vehicle 110, managed by a management device (server) 100 according to this embodiment. The management device according to this embodiment is the server 100, which is communicatively connected to the vehicle 110 via a network 120. In this embodiment, the server 100 is also connected via the network 120 to a terminal 130 (user terminal) owned by a user 135 of the vehicle 110, and transmits an inquiry to the terminal 130 as to whether or not to supplementally charge the sub-battery.

Figure 2 is a block diagram showing an example of the hardware configuration of the server 100 according to this embodiment. The server 100 includes a processing unit 201, a memory unit 202, and a communication unit 203. The processing unit 201 is a processor such as a CPU, and executes programs stored in the memory unit 202. The memory unit 202 is a storage device such as RAM, ROM, or a hard disk. The communication unit 203 includes a wired or wireless communication interface capable of communicating with the vehicle 110 or the terminal 130 via a communication network.

The memory unit 202 stores various data in addition to the programs executed by the processing unit 201. The programs may be installed on the server 100 from a storage medium such as a CD-ROM. In the example of FIG. 2, a database (DB) 221 is shown as an example of data stored in the memory unit 202. DB 221 is a DB in which information about the vehicle 110 is registered, and may also be referred to as a vehicle DB. DB 221 registers and associates the vehicle 110 with the terminal 130 owned by the user 135 of the vehicle 110. In this embodiment, an inquiry as to whether or not to use the sub-battery of the vehicle 110 is sent to the terminal 130 associated with the vehicle 110. Here, the number of terminals 130 associated with the vehicle 110 is not particularly limited, and multiple vehicles 110 may be associated with one terminal 130. DB 221 can store various information related to the vehicle, such as information about the sub-battery 313 of the vehicle 110.

Figure 3 is a block diagram showing an example of the hardware configuration of the server 100 according to this embodiment. The vehicle 110 according to this embodiment is a vehicle driven by an electric motor 315, and includes a main battery 311 and a sub-battery 313, which are secondary batteries. The vehicle 110 according to this embodiment includes, as on-board equipment, the main battery 311, a converter 312, a sub-battery 313, a control unit 314, a motor 315, an ECU 316, and a communication unit 317.

The main battery 311 is a power source for driving the vehicle's motor 315, and in this embodiment, the sub-battery 313 is supplementally charged using the power of the main battery 311. The voltage of the main battery 311 may be, for example, 150V or higher, 200V or higher, 250V or higher, or 280V or higher. The voltage of the main battery may also be 450V or lower, 400V or lower, or 300V or lower.

The sub-battery 313 is a battery that functions as a power source for an electrical system including an ECU (Electronic Control Unit) including a PCU (Power Control Module) or auxiliary equipment such as audio. In this embodiment, the sub-battery 313 has a lower voltage output than the main battery 311, for example, 12V. However, the voltage of the sub-battery 313 can be any voltage depending on the ECU that controls it, and may be, for example, 100V or a voltage similar to that of the main battery. Using a sub-battery with a 12V output makes it possible to adopt a conventional ECU that was previously powered by a 12V battery. A vehicle 110 equipped with such a sub-battery 313 may be, for example, an electric vehicle or a hybrid vehicle with an additional engine. In this embodiment, the vehicle 110 is described as an electric vehicle (BEV, Battery Electric Vehicle) that drives a motor using a battery.

As described above, the sub-battery 313 according to this embodiment supplies power to the vehicle's 110 electrical system. Because the sub-battery 313 supplies power to the control unit 314, which is the vehicle's 110 control system, if the remaining charge of the sub-battery 313 becomes too low, the control system will shut down and be unable to send instructions to the various electrical systems (hereinafter, this phenomenon will be referred to as "dead battery"). While a dead battery can be prevented by supplementally charging the sub-battery 313 using power from the main battery 311, performing supplemental charging more frequently than necessary will consume power from the main battery 311 and reduce the mileage (AER). In this embodiment, the sub-battery 313 is supplementally charged using power from the main battery 311 at a supplemental charging timing set by the server 100, thereby minimizing power consumption of the main battery while preventing a dead battery. The converter 312 is, for example, a DC/DC converter, and reduces the current stored in the main battery 311 to a predetermined voltage and supplies it to various in-vehicle devices, including the sub-battery 313.

In this embodiment, the communication unit 317 transmits to the server 100 remaining charge information of the sub-battery at the start of parking the vehicle. Here, the start of parking the vehicle refers to the timing when the ignition of the vehicle 110 is turned off, but is not particularly limited to the timing when an operation to keep the vehicle stationary by parking, such as when the parking brake is used, is performed. The communication unit 317 transmits the remaining charge information of the sub-battery as an SOC (State Of Charge) value. The remaining charge information may also be expressed by referring to, for example, voltage and temperature. Hereinafter, when the term "remaining charge information" is simply used, it refers to the remaining charge information of the sub-battery 313.

The control unit 314 is, for example, a PCU, and receives power from the sub-battery 313 to control the vehicle's electrical system. The control unit 314 in this embodiment may control the auxiliary charging of the sub-battery, may control the motor 315, or may control the ECU 316. Alternatively, the control unit 314 may be implemented as an ECU dedicated to auxiliary charging of the sub-battery, and the ECU 316 may control other parts of the vehicle. In this embodiment, the control unit 314 controls auxiliary charging of the sub-battery at a timing according to instructions from the server 100.

The ECU 316 is a variety of electrical systems installed in the vehicle 110, such as an audio system or air conditioner. The communication unit 317 sends and receives data to and from the server 100 via the network 120.

In the management system illustrated in FIG. 1, the server 100 predicts when the vehicle 110 will run out of battery power based on the remaining charge information of the sub-battery 313 at the start of parking the vehicle 110. The server 100 sets a threshold value for the remaining charge of the sub-battery 313, and estimates the timing at which the remaining charge is predicted to fall below the threshold as the timing at which the battery will run out (remaining charge low timing). Below, the processing performed by the server 100 will be described as being performed by the processing unit 201 shown in FIG. 2.

The threshold used to determine whether the battery will die can be set according to the user's desired conditions, but for example, it may be set in the range of 10% to 30% using the SOC. Furthermore, taking into account charging efficiency depending on the battery temperature, the threshold for remaining battery charge information may be set based on predicted temperature information. Here, predicted temperature information may be forecast information for the air temperature, the outside temperature of the vehicle when parked, or the temperature of the battery after sufficient time has passed since parking. The server 100 can set the threshold for remaining battery charge information higher, assuming that the lower the predicted temperature information, the worse the charging efficiency will be.

The server 100 can calculate the timing of the remaining charge decrease based on the remaining charge information of the sub-battery 313 and the amount of power consumed (discharged) due to the dark current of the sub-battery 313. The amount of discharge due to the dark current of the sub-battery 313 while on standby may be set in advance based on, for example, the type of vehicle 110, or may be calculated based on various electrical equipment such as a car navigation system or a drive recorder equipped in the vehicle 110, or may be obtained from records of past consumption amounts. For example, by periodically obtaining remaining charge information from the vehicle 110, the server 100 can calculate the amount of consumption, such as a 1% decrease in SOC per day. This discharged amount may also be calculated statistically from the amount of discharged when parked over a predetermined period (e.g., one month).

The server 100 sets the timing for supplementary charging the sub-battery 313 using power from the main battery 311 before the remaining charge is low. The server 100 may set the timing for supplementary charging based on, for example, remaining battery information, or may set the timing for supplementary charging based on information on factors related to the battery charging speed, such as temperature information or battery degradation information, in addition to the remaining battery information. The server 100 according to this embodiment may set the timing for supplementary charging based on a temperature forecast, for example, so as to prioritize supplementary charging when the temperature is high. Since charging is considered to be sufficiently efficient when the temperature is 0°C or higher, the server 100 may set the timing for supplementary charging when the temperature is 0°C or higher. Similarly, the server 100 may set the timing for supplementary charging based on the temperature desired by the user. The server 100 may also set the timing for supplementary charging to start on a day when charging can be performed efficiently, such as during the daytime on the day with the highest (maximum or average) temperature within a predetermined period (e.g., one week) for which temperature information is acquired. On the other hand, extremely high temperatures, such as when the engine compartment exceeds 60°C, can have a negative impact on charging, so supplemental charging may not be set when it is predicted that certain high temperature conditions will be met, such as not performing supplemental charging on days when the temperature is predicted to exceed 35°C for a certain period of time (for example, six hours).

To this end, the server 100 can obtain a temperature forecast for the parking area after the vehicle 110 begins parking. In this embodiment, the server 100 is communicatively connected to a weather forecast server (not shown) that provides weather forecasts, and obtains weather forecast information from the weather forecast server, including temperature forecasts for each area for a specified period. However, if a temperature forecast for the parking area of the vehicle 110 can be obtained, there is no need to use a weather forecast server; for example, the server 100 may predict the temperature, or temperature forecast information stored in the vehicle 110 may be obtained. Here, the temperature forecast is assumed to be the minimum temperature for each day (or for a specified period), but the average temperature, maximum temperature, etc. may also be used depending on the application.

The server 100 sends an inquiry (supplementary charging confirmation) to the terminal 130 asking whether or not to perform supplementary charging. Upon receiving the supplementary charging confirmation, the terminal 130 displays a message to the user 135 to confirm whether or not they intend to perform supplementary charging, and obtains user input regarding whether or not to perform supplementary charging.

Figure 4 is a diagram showing an example of a GUI of a notification screen for the user displayed by the terminal 130 upon receiving confirmation of supplemental charging in this embodiment. Messages 402, 403, and a confirmation button 404 are displayed on the display screen 401 of the terminal 130. Message 402 is a display that informs the user of the date on which the battery will run out (when the remaining charge will decrease). In the example of Figure 4, message 402 displays a message indicating that the vehicle may not be able to start due to a dead battery in 10 days. Message 403 is a display that informs the user of the mileage that will change when supplemental charging is performed. In the example of Figure 4, it displays a message indicating that the mileage will change from 300 km before to 280 km after supplemental charging. In this way, the server 100 may transmit information regarding supplemental charging along with confirmation of supplemental charging. The terminal 130 obtains user input via the confirmation button 404 and transmits the selection result to the server 100. Note that the display in Figure 4 is just one example; for example, the notification bar displayed by swiping on the touch panel may only display the confirmation button 404, allowing input, and tapping the corresponding location on the notification bar may display the entire information in Figure 4.

Here, if it is determined that the user 135 intends to perform supplemental charging based on the selection result, the server 100 can send a supplemental charging start instruction to the vehicle 110 at the supplemental charging timing. Here, the server 100 may send a start instruction at the supplemental charging timing to cause the vehicle 110 to start supplemental charging, or may send information indicating the supplemental charging timing to the vehicle 110, and the control unit 314 may start supplemental charging at the supplemental charging timing based on that information.

The server 100 can set the timing for sending the supplementary charging confirmation to the terminal 130 based on the timing of when the remaining charge is low. For example, the server 100 can send the supplementary charging confirmation simultaneously with when the remaining charge is low, or a predetermined period of time in advance (e.g., 10 days as shown in message 402 in FIG. 4). Any timing can be set as long as it allows the user to check.

Furthermore, the server 100 will not allow the vehicle 110 to perform supplemental charging if there is no input from the user in response to the supplemental charging confirmation. However, supplemental charging may be performed even if no input from the user is confirmed.

In this embodiment, when confirmation of supplemental charging is made, the user is notified by a screen display such as that shown in FIG. 4, but the method is not limited to this as long as the user is notified. For example, the server 100 may send a voice inquiry to the terminal 130, or may control the terminal 130 to simultaneously perform a vibration or lighting process. By notifying the user via an automated voice call, the user can more reliably confirm the notification.

Figure 5 is a flowchart showing an example of the management process for the remaining charge of the sub-battery 313 performed by the processing unit 201 of the server 100 according to this embodiment. In this embodiment, the process according to Figure 5 is started when the vehicle 110 is parked and the ignition is turned off, and remaining charge information for the sub-battery 313 is sent to the server 100. The process according to Figure 5 is realized, for example, by the CPU of the processing unit 201 reading a program stored in the ROM or memory unit 202 into RAM and executing it.

In S501, the server 100 acquires various information from the vehicle 110, including remaining charge information of the sub-battery. Here, the server 100 acquires the remaining charge information as SOC. In S502, the server 100 predicts the timing when the sub-battery 313 will run out based on the remaining charge information acquired in S501. The server 100 according to this embodiment predicts the timing when the sub-battery 313 will run out using information indicating the amount of discharge due to dark current of the vehicle 110 stored in DB221. However, in S501, it is also possible to acquire information indicating the amount of discharge due to dark current of the vehicle 110 from the vehicle 110 in addition to the remaining charge information.

In S503, the server 100 obtains a weather forecast. In this embodiment, the server 100 obtains a weather forecast corresponding to the parking area of the vehicle 110 from a weather forecast server and references the temperature forecast included in the weather forecast. Here, the server 100 may have obtained the location information of the vehicle 110 parked as the parking area in S501, or may use the area corresponding to the vehicle 110 stored in DB221 as the parking area.

In S504, server 100 sets the timing for supplemental charging of sub-battery 313 based on the temperature forecast obtained in S503. For example, server 100 may determine that the timing for starting supplemental charging is the daytime (e.g., 12 noon) on the day with the highest minimum temperature within the specified period (here, one week) of the obtained temperature forecast. Alternatively, for example, server 100 may calculate the timing for starting supplemental charging based on the temperature forecast so that supplemental charging will be completed on the date and time when the battery will run out, and may determine that the timing for starting supplemental charging is the daytime on a day before the calculated timing when the minimum temperature exceeds a threshold value that satisfies the conditions for starting supplemental charging.

At S505, the server 100 sends an inquiry to the user terminal asking whether or not to perform supplemental charging. Here, the server 100 sends a confirmation of supplemental charging to the terminal 130 associated with the vehicle for which the remaining charge has been obtained. At S506, the server 100 acquires information input by the user to the terminal 130, which is a response to the inquiry sent at S505, indicating whether or not to perform supplemental charging of the sub-battery.

In S507, server 100 determines whether or not to perform supplemental charging based on the information acquired in S506. If input indicating that supplemental charging will be performed is acquired in S506, processing proceeds to S508; otherwise, processing ends. In S508, server 100 instructs vehicle 110 to start supplemental charging. As described above, server 100 may send the start instruction to vehicle 110 at the timing to start supplemental charging, or may send an instruction including information indicating the start timing to vehicle 110 before the start timing.

This process predicts when the battery will run out based on the remaining charge of the sub-battery, and before that time, the user is asked whether or not the sub-battery can be supplementally charged from the main battery, and then supplemental charging is performed, thereby making it possible to prevent the battery from running out while also reducing wear on the vehicle's main battery.

Note that, although the processing shown in FIG. 4 according to this embodiment has been described as being performed by the server 100, some or all of this processing may be performed by the vehicle 110. That is, the control unit of the vehicle 110 may acquire various information and even set the supplemental charging timing and control the supplemental charging. Furthermore, instead of the server 100, a similar processing may be performed by an information and communications terminal held by an administrator. In this case, the selection processing is executed by a CPU (not shown) built into the information and communications terminal that loads the selection processing program stored in a storage device such as an HDD into RAM or the like. Here, the selection processing program executed by the CPU may be installed in the storage device of the information and communications terminal via a storage medium such as a CD-ROM.

Note that each process according to this embodiment is assumed to be performed when the vehicle 110 is stopped in a parking lot (i.e., a parking position where charging is not possible, or when charging has been forgotten) and the battery charge level is decreasing due to dark current. In this embodiment, we have described a situation in which the sub-battery 313 is supplementally charged while the vehicle is stopped, but it is also possible that supplemental charging occurs while the vehicle is traveling. In such a case, while the sub-battery 313 is being supplementally charged, power is supplied from the main battery 311 to the control unit 314 via the converter 312. In other words, depending on the situation, the main battery may provide some or all of the power supply from the sub-battery described above.

[Summary of the embodiment]
The above-described embodiment discloses at least the following management device and information processing method.

1. The management device (e.g., 100) of the above embodiment
A management device for managing a remaining capacity of a sub-battery of a vehicle (e.g., 110) having a main battery (e.g., 311) and a sub-battery (e.g., 313),
a remaining amount information acquisition means (e.g., 201) for acquiring remaining amount information of the sub-battery at the time of starting parking of the vehicle;
a prediction means (e.g., 201) for predicting a timing at which the remaining charge of the sub-battery will fall below a threshold while the vehicle is parked, based on the remaining charge information;
a transmitting means (e.g., 201) for transmitting to a user terminal an inquiry as to whether or not to supplementarily charge the sub-battery using power from the main battery at a timing before the remaining charge reduction timing predicted by the predicting means;
Equipped with.
According to this embodiment, it is possible to prevent the main battery of the vehicle from running out while suppressing consumption of the battery.

2. In the management device of the above embodiment,
The battery further includes a setting unit for setting a supplementary charging timing (e.g., S504) for performing the supplementary charging before the remaining charge low timing,
The transmission means transmits the inquiry to the user terminal at a timing that is set based on the supplementary charging timing.
According to this embodiment, it is possible to send a query to the user before the set supplementary charging timing as to whether or not to perform supplementary charging.

3. In the management device of the above embodiment,
The parking control system further includes a temperature forecast acquisition means for acquiring a temperature forecast of a parking area of the vehicle after the parking of the vehicle starts (for example, S503),
The setting means sets the supplementary charging timing based on the temperature forecast.
According to this embodiment, it is possible to set the timing of supplementary charging in consideration of changes in charging efficiency based on the temperature.

4. In the management device of the above embodiment,
The setting means sets the supplementary charging timing by giving priority to a timing when the temperature is high.
According to this embodiment, supplementary charging can be performed at a timing that satisfies the temperature conditions suitable for supplementary charging.

5. In the management device of the above embodiment,
The transmission means transmits the inquiry and information regarding the supplementary charging to the user terminal.
According to this embodiment, it is possible to allow the user to confirm information regarding supplementary charging before selecting whether or not supplementary charging is required.

6. In the management device of the above embodiment,
The information regarding supplemental charging is information indicating the timing of the remaining charge decrease, or the travel distance of the vehicle that varies depending on the execution of supplemental charging.
According to this embodiment, it is possible to have the user check the estimated battery life or the reduced driving distance due to supplemental charging before selecting whether or not supplemental charging is required.

7. In the management device of the above embodiment,
the main battery is a power source for driving a motor of the vehicle,
The sub-battery has a lower voltage output than the main battery and serves as a power source for electrical equipment of the vehicle.
According to this embodiment, it is possible to appropriately perform supplementary charging of the sub-battery of the electric vehicle.

8. The management device of the above embodiment
The vehicle is communicably connected to an on-board device (e.g., 107) of the vehicle,
The battery charger further includes an instruction unit that transmits an instruction to start the supplementary charging to the in-vehicle device at a timing prior to the remaining charge reduction timing predicted by the prediction unit (for example, S507).
According to this embodiment, it is possible to issue a supplementary charging instruction from the management device side while suppressing the consumption of the main battery of the vehicle.

9. In the management device of the above embodiment,
The remaining amount information acquiring means acquires the remaining amount information from the vehicle-mounted device.
According to this embodiment, it becomes possible for the management device to predict the timing of supplementary charging based on the acquired remaining amount information.

10. In the management device of the above embodiment,
the management device is an on-board device mounted on the vehicle,
The management device
The battery includes a control unit that operates a charger that performs supplementary charging of the sub-battery at a timing prior to the timing of the remaining charge decrease predicted by the prediction unit.
According to this embodiment, the timing of supplementary charging can be set by the vehicle-mounted device.

11. The information processing method of the above embodiment is
An information processing method performed by a management device (e.g., 100) that manages a remaining charge of a sub-battery of a vehicle having a main battery and a sub-battery, comprising:
a remaining amount information acquisition step (e.g., S501) of acquiring remaining amount information of the sub-battery at the start of parking the vehicle;
a prediction step (e.g., S502) of predicting a timing at which the remaining charge of the sub-battery will fall below a threshold while the vehicle is parked, based on the remaining charge information;
a transmission step (e.g., S505) of transmitting to a user terminal an inquiry as to whether or not to perform supplementary charging of the sub-battery using power from the main battery at a timing before the remaining charge decrease timing predicted in the prediction step;
Equipped with.
According to this embodiment, it is possible to prevent the main battery of the vehicle from running out while suppressing consumption of the battery.

The above describes an embodiment of the invention, but the invention is not limited to the above embodiment, and various modifications and variations are possible within the scope of the invention.

201: Processing unit, 202: Storage unit, 203: Communication unit

Claims (9)

A management device for managing a remaining charge of a sub-battery of a vehicle having a main battery and a sub-battery,
a remaining charge information acquisition means for acquiring remaining charge information of the sub-battery at the time when the vehicle starts to be parked;
a prediction unit for predicting a timing at which the remaining charge of the sub-battery will fall below a threshold while the vehicle is parked, based on the remaining charge information;
a transmitting means for transmitting an inquiry to a user terminal as to whether or not to supplementarily charge the sub-battery using power from the main battery at a timing before the remaining charge reduction timing predicted by the predicting means;
Equipped with
the transmission means transmits information regarding the supplementary charging together with the inquiry to the user terminal;
The management device is characterized in that the information regarding supplemental charging is a travel distance of the vehicle that varies depending on the implementation of supplemental charging . a setting unit for setting a supplementary charging timing to perform the supplementary charging before the remaining charge low timing;
2. The management device according to claim 1, wherein the transmission means transmits the inquiry to the user terminal at a timing that is set based on the supplementary charging timing. a temperature forecast acquisition means for acquiring a temperature forecast of a parking area of the vehicle after the vehicle starts to park,
3. The management device according to claim 2, wherein the setting means sets the supplementary charging timing based on the temperature forecast. The management device described in claim 3, wherein the setting means sets the supplementary charging timing by prioritizing timing when the temperature is high. the main battery is a power source for driving a motor of the vehicle,
The sub-battery has a lower voltage output than the main battery and serves as a power source for electrical equipment of the vehicle.
4. The management device according to claim 1, wherein the management device is a management device for managing a plurality of data items. the management device is communicably connected to an on-board device of the vehicle,
The management device
an instruction unit that transmits an instruction to start the supplementary charging to the in-vehicle device at a timing before the remaining charge reduction timing predicted by the prediction unit;
The management device according to any one of claims 1 to 5 , characterized in that: 7. The management device according to claim 6 , wherein the remaining amount information acquisition means acquires the remaining amount information from the vehicle-mounted device. the management device is an on-board device mounted on the vehicle,
The management device
a control unit that operates a charger that performs supplemental charging of the sub-battery at a timing before the remaining charge reduction timing predicted by the prediction unit;
The management device according to any one of claims 1 to 5 , characterized in that: An information processing method performed by a management device that manages a remaining charge of a sub-battery of a vehicle having a main battery and a sub-battery, comprising:
a remaining amount information acquisition step of acquiring remaining amount information of the sub-battery at the start of parking the vehicle;
a prediction step of predicting a timing at which the remaining charge of the sub-battery will fall below a threshold while the vehicle is parked, based on the remaining charge information;
a transmission step of transmitting to a user terminal an inquiry as to whether or not to perform supplementary charging of the sub-battery using power from the main battery at a timing before the remaining charge reduction timing predicted in the prediction step;
Equipped with
information about the supplementary charging is transmitted to the user terminal together with the inquiry;
An information processing method , wherein the information regarding supplemental charging is a travel distance of the vehicle that varies depending on whether supplemental charging is performed .