JP2023137815A - Management device and information processing method - Google Patents

Abstract

To prevent batteries from running out while suppressing a main battery of a vehicle from being exhausted by notifying users and prompting them to take action before a sub-battery runs out.SOLUTION: A management device manages the remaining power of a sub-battery of a vehicle that includes a main battery and the sub-battery. The management device acquires remaining power information of the sub-battery at the time when the vehicle starts parking. The management device predicts a remaining power drop timing at which the remaining power of the sub-battery falls below a threshold while the vehicle is parked, based on the acquired remaining power information. The management device transmits a notification regarding the remaining power drop timing to a user terminal at a timing earlier than the predicted remaining power drop timing.SELECTED DRAWING: Figure 3

Description

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

In recent years, in order to ensure that more people have access to affordable, reliable, sustainable, and advanced energy, secondary batteries that contribute to energy efficiency, and vehicles equipped with secondary batteries, have been introduced. Research and development regarding charging and power supply is being carried out.

Patent Document 1 discloses a technique that, when deterioration of an automobile battery is confirmed, makes it possible to easily determine whether the deterioration symptoms are due to long-term neglect. Furthermore, Patent Document 2 discloses that a battery for in-vehicle equipment, which is generated by an on-board generator, is notified of battery conditions such as a low charge state or an abnormal state, so that users who are away from the vehicle can A technique has been disclosed that makes it possible to appropriately grasp the state of a vehicle.

Japanese Patent Application Publication No. 2003-32809 Japanese Patent Application Publication No. 2013-131809

By the way, in the technology related to charging and supplying secondary batteries and vehicles equipped with secondary batteries, supplementary charging of the sub-battery is performed using power from the main battery, but supplementary charging is required frequently to prevent the battery from dying. If this is done, the problem is that the power of the main battery will be consumed and the driving distance (AER) will decrease.

In order to solve the above-mentioned problem, this application aims to suppress the battery drain while suppressing the consumption of the main battery of the vehicle by notifying the user and prompting the user to take measures before the sub-battery causes the battery to drain. be. This in turn contributes to energy efficiency.

According to the invention,
A management device that manages the remaining amount of the sub-battery of a vehicle having a main battery and a sub-battery,
Remaining amount information acquisition means for acquiring remaining amount information of the sub-battery at the time when the vehicle starts parking;
Prediction means for predicting a timing at which the remaining capacity of the sub-battery decreases below a threshold while the vehicle is parked, based on the remaining capacity information;
Temperature forecast acquisition means for acquiring a temperature forecast for the parking area of the vehicle after the vehicle starts parking;
Transmitting means for transmitting a notification regarding the remaining capacity reduction timing to a user terminal at a timing earlier than the remaining capacity reduction timing predicted by the prediction means;
Provided is a management device comprising:

According to the present invention, by notifying the user and prompting the user to take measures before the sub-battery runs out, it is possible to suppress the battery from running out while suppressing the consumption of the main battery of the vehicle.

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

Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the claimed invention, and not all combinations of features described in the embodiments are essential to the invention. Two or more features among the plurality of features described in the embodiments may be arbitrarily combined. In addition, the same or similar configurations are given the same reference numerals, and duplicate explanations will be omitted.

A management device according to an embodiment of the present invention manages the remaining amount of a sub-battery of a vehicle that includes a main battery and a sub-battery. In particular, the management device according to the present embodiment acquires the remaining amount information of the sub-battery at the time when the vehicle starts parking, and based on the obtained remaining amount information, the remaining amount of the sub-battery decreases below a threshold value while the vehicle is parked. Predict the timing when the remaining amount will decrease. Next, the management device transmits a notification regarding the remaining amount reduction timing to the user terminal at a timing earlier than the predicted remaining amount reduction timing. In this embodiment, the management device is a server that acquires various information from the vehicle and predicts the timing when the remaining battery level will decrease; however, this is just an example, and the configuration is not limited to this. do not have.

[system]
Hereinafter, with reference to FIG. 1, a system including a management device according to this embodiment will be described. FIG. 1 shows a management system that is managed by a management device (server) 100 according to this embodiment and sets the timing for supplementary charging of a vehicle 110. The management device according to this embodiment is a server 100, which is communicably connected to a vehicle 110 via a network 120. Further, in this embodiment, the server 100 connects to a terminal 130 (user terminal) owned by a user 135 of the vehicle 110 via the network 120, and transmits to the terminal 130 a notification regarding the timing when the remaining power of the sub-battery decreases.

FIG. 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 section 201, a storage section 202, and a communication section 203. The processing unit 201 is a processor represented by a CPU, and executes a program stored in the storage unit 202. The storage unit 202 is a storage device such as a RAM, ROM, or hard disk. Communication unit 203 includes a wired or wireless communication interface that can communicate with vehicle 110 or terminal 130 via a communication network.

The storage unit 202 stores various data in addition to programs executed by the processing unit 201. The program 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 illustrated as data stored in the storage unit 202. The DB 221 is a DB in which information about the vehicle 110 is registered, and the DB 221 may be called a vehicle DB. The vehicle 110 and the terminal 130 owned by the user 135 of the vehicle 110 are registered in the DB 221 in association with each other. In this embodiment, a notification regarding the timing of decreasing the remaining amount is transmitted to the terminal 130 associated with the vehicle 110. Here, the number of terminals 130 associated with vehicle 110 is not particularly limited, and one terminal 130 may be associated with a plurality of vehicles 110. The DB 221 can store various types of information regarding the vehicle, such as usage information indicating the usage status or usage settings of the vehicle 110 by the user, which will be described later, or information regarding the sub-battery 313 of the vehicle 110.

FIG. 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 the present embodiment is a vehicle that is driven by an electric motor 315 and includes a main battery 311 and a sub-battery 313 that are secondary batteries. The vehicle 110 according to the present embodiment includes a main battery 311, a converter 312, a sub-battery 313, a control section 314, a motor 315, an ECU 316, and a communication section 317 as onboard devices.

The main battery 311 is a power source for driving the motor 315 of the vehicle, 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 more, 200V or more, 250V or more, or 280V or more. Further, the voltage of the main battery may be 450V or less, 400V or less, or 300V or less.

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. The sub-battery 313 according to this embodiment is a battery with a lower voltage output than the main battery 311, and its voltage is, for example, 12V. However, the voltage of the sub-battery 313 can be any voltage depending on the controlling ECU, and may be, for example, 100V, or may be about the same voltage as the main battery. By using a sub-battery with an output of 12V, it becomes possible to employ a conventional ECU that is driven by a 12V battery. The vehicle 110 equipped with such a sub-battery 313 may be, for example, an electric vehicle or a hybrid vehicle additionally equipped with an engine. In this embodiment, the description will be given assuming that the vehicle 110 is an electric vehicle (BEV, Battery Electric Vehicle) whose motor is driven by a battery.

The sub-battery 313 according to this embodiment supplies power to the electrical system of the vehicle 110 as described above. The sub-battery 313 supplies power to the control unit 314, which is the control system of the vehicle 110, so if the remaining charge of the sub-battery 313 drops too much, the control system will stop and instructions will no longer be sent to the various electrical systems ( (Hereinafter, this phenomenon will be referred to as "depleted battery.") Battery exhaustion can be prevented by supplementary charging of the sub-battery 313 using power from the main battery 311, but if supplementary charging is performed more frequently than necessary, the power of the main battery 311 will be consumed and the mileage (AER) will decrease. Resulting in. By notifying the user and prompting the user to take action before the sub-battery runs out, it is possible to prevent supplementary charging from being carried out at unnecessary timings, thereby suppressing main battery consumption and suppressing the battery from running out. Converter 312 is, for example, a DC/DC converter, and reduces the current stored in main battery 311 to a predetermined voltage and supplies it to various on-vehicle devices including sub-battery 313.

In the present embodiment, the communication unit 317 transmits to the server 100 information on the remaining amount of the sub-battery at the time when the vehicle starts parking. Here, the start of parking of the vehicle is defined as the timing when the ignition of the vehicle 110 is turned off, but it may also be the timing when an operation is performed to keep the vehicle stationary, such as when the parking brake is used. There are no particular limitations. The communication unit 317 transmits the remaining amount information of the sub-battery as an SOC (State of Charge) value. The remaining amount information may also be expressed with reference to voltage and temperature, for example. Hereinafter, when it is simply expressed as "remaining amount information", it refers to the remaining amount 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 electrical system of the vehicle. The control unit 314 according to the present embodiment may control supplementary charging of the sub-battery, may control the motor 315, and may control the ECU 316. Alternatively, the control unit 314 may be implemented as an ECU dedicated to supplementary charging of the sub-battery, and the ECU 316 may control other vehicles. In this embodiment, the control unit 314 controls supplementary charging of the sub-battery at a timing according to an instruction from the server 100.

The ECU 316 is a variety of electrical systems installed in the vehicle 110, such as an audio system or an air conditioner. The communication unit 317 transmits 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 the timing at which the battery of the vehicle 110 will run out, based on the remaining amount information of the sub-battery 313 at the time when the vehicle 110 starts parking. The server 100 sets a threshold value for the remaining amount of the sub-battery 313, and estimates the timing at which the remaining amount is predicted to fall below the threshold value as the timing at which the battery runs out (remaining amount drop timing). The processing performed by the server 100 will be described below as being performed by the processing unit 201 shown in FIG. 2.

The threshold value used to determine whether or not the battery will run out can be set according to the user's desired conditions, but it is assumed that it is set in the range of 10% to 30% using SOC, for example. Further, the threshold value of the remaining amount information may be set based on the predicted temperature information, taking into consideration the charging efficiency depending on the temperature of the battery. The predicted temperature information here may be temperature forecast information, the outside temperature of the vehicle at the time of parking, or the battery temperature after a sufficient period of time has passed since parking. good. The server 100 can set the threshold value of the remaining amount information high, assuming that the lower the expected temperature information, the worse the charging efficiency becomes. For this purpose, the server 100 can obtain a temperature forecast for the parking area after the vehicle 110 starts parking. In this embodiment, the server 100 is communicably connected to a weather forecast server (not shown) that performs weather forecasts, and receives weather forecast information including temperature forecasts for a predetermined period for each region from the weather forecast server. shall be obtained. However, if the temperature forecast in the parking area of the vehicle 110 can be obtained, there is no need to use the weather forecast server; for example, the server 100 may predict the temperature, or the temperature stored in the vehicle 110 may be Forecast information may be obtained. Here, the minimum temperature for each day (or for a predetermined period) is used as the temperature forecast, but the average temperature, maximum temperature, etc. may be used depending on the purpose.

The server 100 can calculate the above-mentioned remaining power reduction timing based on the remaining power information of the sub-battery 313 and the power consumption amount (discharge amount) due to the dark current of the sub-battery 313. The amount of discharge due to dark current of the sub-battery 313 during standby may be set in advance based on the type of the vehicle 110, for example, and calculated based on various electrical components such as a car navigation device or a drive recorder included in the vehicle 110. or may be obtained from past consumption records. For example, by periodically acquiring the remaining amount information from the vehicle 110, the server 100 can calculate the consumption amount such that the remaining amount information decreases by 1% in SOC per day. This amount of discharge may be statistically calculated from the amount of discharge during parking during a predetermined period (for example, one month).

The server 100 transmits to the terminal 130 a notification regarding the timing for decreasing the remaining amount (remaining amount decreasing notification). The terminal 130 that has received the notification of low remaining power notifies the user using the received notification.

FIG. 4 is a diagram illustrating an example of a GUI of a notification screen to the user, which is displayed by the terminal 130 that has received the notification of low remaining power in this embodiment. A message 402 is displayed on the display screen 401 of the terminal 130. The message 402 is a display that informs the user that at the remaining power timing, it will be difficult to drive due to the remaining power state of the sub-battery (because the battery will run out). In the example of FIG. 4, a message 402 urging charging is also displayed on the display screen 401. In this way, the server 100 may send a notification urging supplementary charging as a notification of low remaining power.

Additionally, the server 100 may cause the terminal 130 to display a display inquiring whether or not to perform supplementary charging in addition to the low remaining power notification, and may cause the terminal 130 to obtain user input regarding whether or not supplementary charging is necessary. . In that case, the terminal 130 obtains user input using a confirmation button (not shown) and transmits the selection result to the server 100. Here, if it is determined that there is an intention to perform supplementary charging according to the selection result of user 135, server 100 can transmit an instruction to start supplementary charging to vehicle 110. Here, the server 100 may cause the vehicle 110 to start supplementary charging at the timing when the instruction to start supplementary charging is transmitted, and the server 100 transmits the instruction to start supplementary charging including information indicating the supplementary charging timing to the vehicle 110, and controls the The unit 314 may start supplementary charging at the supplementary charging timing based on the information.

Note that the server 100 can set the timing for transmitting the remaining amount reduction notification to the terminal 130 based on the remaining amount reduction timing. For example, the server 100 may send the supplementary charging implementation confirmation remaining power reduction notification at the same time as the remaining power reduction timing, or may send it a predetermined period (for example, 10 days) in advance, or at any timing that the user can confirm. You can make any settings you want.

In this embodiment, it is assumed that the user who confirms the notification of low remaining power decides whether or not to perform supplementary charging and takes action, and if there is no input from the user in response to the notification of low remaining power, the vehicle 110 is not allowed to perform supplementary charging. However, supplementary charging may be performed even when input from the user cannot be confirmed.

In this embodiment, the user is notified of the low remaining power by a screen display as shown in FIG. 4, but if the user is to be notified, it is limited to this mode. Not allowed. For example, the server 100 may send an audio notification to the terminal 130, or may control the terminal 130 to simultaneously perform a vibration or lighting process. By giving a notification using an automated voice over the telephone, the user can confirm the notification more reliably.

The server 100 also predicts the next timing of use of the vehicle 110 after parking, and sends a notification of low remaining capacity to the terminal 130 if the above-mentioned timing for decreasing the remaining capacity arrives before the predicted timing of use. You can also do this. That is, if it is predicted that the battery of the vehicle 110 will run out before the next time it is used, a low remaining battery level notification may be issued. To this end, the server 100 acquires usage information indicating the usage status or usage settings of the vehicle 110 by the user from the vehicle 110, and estimates the timing at which the user will use the vehicle 110 next time based on the acquired usage information. be able to. Here, for example, the server 100 may collect usage history data such as ``the user uses the vehicle 110 only on a fixed day of the week'', or ``how many days later will the user use the vehicle next time'', etc. Data indicating the date and time of use can be obtained from the vehicle 110. In this way, when it is predicted that the battery will be depleted the next time it is used, by notifying the timing, it is possible to encourage the user to respond to the depleted battery in addition to their usual actions.

This data for which the date and time of use by the user can be predicted is such that the vehicle 110 records the date and time when the ignition was turned on, and the percentage of days when the ignition was turned on during a predetermined period (for example, one month) is 7. A day of the week that can be determined to be frequently used by the user based on predetermined conditions, such as a day of the week when the vehicle is frequently used by the user, may be estimated as the day of the week when the user uses the vehicle. Further, the data representing the date and time of use of the vehicle by the user may be input directly by the user into the ECU 316 of the vehicle 110, or may be input via an application by inputting it into a mobile terminal (not shown) associated with the user. good.

When setting the supplementary charging timing, server 100 can transmit an instruction to start supplementary charging at the supplementary charging timing to vehicle 110. When the communication unit 317 receives the instruction to start supplementary charging, the communication unit 317 causes the control unit 314 to perform control so that supplementary charging is performed at the supplementary charging timing. Here, the server 100 may start supplementary charging by transmitting a start instruction at the supplementary charging timing, or transmits information indicating the supplementary charging timing to the vehicle 110, and the control unit 314 performs supplementary charging based on the information. Supplementary charging may be started at the appropriate timing.

FIG. 4 is a flowchart illustrating an example of a process for managing the remaining amount of the sub-battery 313 performed by the processing unit 201 of the server 100 according to the present embodiment. In this embodiment, when the vehicle 110 is parked and the ignition is turned off, the process shown in FIG. The processing according to FIG. 4 is realized, for example, by the CPU of the processing unit 201 reading a program held in the ROM or the storage unit 202 into the RAM and executing it.

In S501, the server 100 acquires various information including sub-battery remaining amount information from the vehicle 110. Here, the server 100 acquires the remaining amount information as the SOC. In S502, the server 100 predicts the timing at which the sub-battery 313 will be charged based on the remaining capacity information acquired in S501. The server 100 according to the present embodiment predicts the timing at which the sub-battery 313 will go up using the information stored in the DB 221 that indicates the amount of discharge due to the dark current of the vehicle 110. Information indicating the amount of discharge due to the dark current of the vehicle 110 may be acquired from the vehicle 110.

In S503, the server 100 estimates the next time the user of the vehicle 110 will use the vehicle 110. In this embodiment, the usage history of the vehicle 110 is stored in the DB 221, and the server estimates the next usage timing by referring to the usage history. It does not matter if the date and time of next use is obtained.

In S504, the server 100 determines whether the battery will run out by the date and time of next use estimated in S503. If the battery is dead, the process advances to S505, and if the battery is not dead, the process ends without instructing supplementary charging.

In S505, the server 100 transmits a low remaining amount notification to the vehicle 110. In S506, the server 100 determines whether supplementary charging is necessary. Here, the server 100 sends a low remaining power notification and allows the user to confirm whether supplementary charging is necessary on the terminal 130, and if the user inputs an instruction to perform supplementary charging, supplementary charging is necessary. It shall be determined that If it is determined that supplementary charging is necessary, the process advances to S507; otherwise, the process ends.

In S507, server 100 instructs vehicle 110 to start supplementary charging. As described above, server 100 may transmit a start instruction to vehicle 110 at the start timing of supplementary charging, or may transmit an instruction including information indicating the start timing to vehicle 110 before the start timing. good.

According to this kind of processing, the timing when the battery will run out according to the remaining capacity of the sub-battery is predicted, and the user is notified and prompted to take action before the sub-battery runs out, thereby reducing the main battery of the vehicle. It becomes possible to suppress battery drain while suppressing consumption.

Note that although the processing shown in FIG. 4 according to the present embodiment has been described as being performed by the server 100, part or all of this processing may be performed by the vehicle 110. That is, the control unit of the vehicle 110 can acquire each piece of information, set the supplementary charging timing, and perform supplementary charging control. Further, instead of the server 100, an information communication terminal or the like held by the administrator may perform similar processing. In this case, a CPU (not shown) incorporated in the information communication terminal executes the selection process by loading a selection process program recorded in a storage device such as an HDD into a RAM or the like. Here, the selection processing program executed by the CPU may be installed in the storage device of the information communication terminal via a storage medium such as a CD-ROM.

Note that each process according to the present embodiment is performed when the vehicle 110 stops in a parking lot (that is, in a parking position where charging is not possible or when charging is forgotten), and the amount of charge of the battery decreases due to dark current. It is assumed that it will be carried out in the state. Although the present embodiment has been described on the assumption that supplementary charging of the sub-battery 313 is performed during such a stop, it is also conceivable that supplementary charging is performed, for example, while the vehicle is running. In such a case, power is supplied from the main battery 311 to the control unit 314 via the converter 312 while sub-battery 311 is supplementally charged. That is, the main battery may supply part or all of the power from the sub-battery in the above description depending on the situation.

[Summary of embodiments]
The above embodiments disclose at least the following management device and information processing method.

1. The management device (for example, 100) of the above embodiment is
A management device that manages the remaining capacity of a sub-battery of a vehicle (for example, 110) having a main battery (for example, 311) and a sub-battery (for example, 313),
Remaining amount information acquisition means (for example, 201) that acquires remaining amount information of the sub-battery at the time when the vehicle starts parking;
prediction means (for example, 201) that predicts a timing at which the remaining capacity of the sub-battery decreases below a threshold value while the vehicle is parked based on the remaining capacity information;
a transmitting unit (for example, 201) that transmits a notification regarding the remaining capacity reduction timing to a user terminal at a timing before the remaining capacity decreasing timing predicted by the prediction unit;
Equipped with.
According to this embodiment, it is possible to suppress battery depletion while suppressing consumption of the main battery of the vehicle.

2. In the management device of the above embodiment,
The notification regarding the remaining power reduction timing is a notification indicating that it will be difficult for the vehicle to travel at the remaining power reduction timing due to the state of the remaining power of the sub-battery.
According to this embodiment, it is possible to notify the user that it is difficult to drive due to a dead battery and prompt the user to take action.

3. In the management device of the above embodiment,
comprising a usage prediction means for predicting the timing of use of the vehicle after parking (for example, S503);
The transmitting means transmits a notification regarding the remaining amount reduction timing to the user terminal when the remaining amount reduction timing predicted by the prediction means arrives before the usage timing predicted by the usage prediction means.
According to this embodiment, if it is predicted that the battery will run out before the next time the vehicle is used, it is possible to prompt the user to take action.

4. 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 is a battery with a lower voltage output than the main battery, and is a power source for electrical components of the vehicle.
According to this embodiment, it becomes possible to appropriately manage the dead battery state of the sub-battery of an electric vehicle.

5. The management device of the above embodiment is
It is communicatively connected to the vehicle-mounted device (for example, 107) of the vehicle.
According to this embodiment, it is possible to manage the dead battery state from the management device side while suppressing consumption of the main battery of the vehicle.

3. In the management device of the above embodiment,
The remaining amount information acquisition means obtains the remaining amount information from the on-vehicle device.
According to this embodiment, it becomes possible to manage the dead battery state on the management device side based on the acquired remaining power information.

7. In the management device of the above embodiment,
The management device is an on-vehicle device mounted on the vehicle.
According to this embodiment, it becomes possible to manage the dead battery state using the on-vehicle device of the vehicle.

8. The information processing method of the above embodiment is as follows:
An information processing method performed by a management device (for example, 100) that manages the remaining amount of the sub-battery of a vehicle having a main battery and a sub-battery,
a remaining amount information obtaining step (for example, S501) of obtaining remaining amount information of the sub-battery at the time when the vehicle starts parking;
a prediction step (for example, S502) of predicting a timing at which the remaining capacity of the sub-battery decreases below a threshold value while the vehicle is parked based on the remaining capacity information;
The method further includes a sending step (for example, S505) of transmitting a notification regarding the remaining amount reduction timing to the user terminal at a timing before the predicted remaining amount reduction timing.
According to this embodiment, it is possible to suppress battery depletion while suppressing consumption of the main battery of the vehicle.

Although the embodiments of the invention have been described above, the invention is not limited to the above embodiments, and various modifications and changes can be made within the scope of the gist of the invention.

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

Claims (8)

A management device that manages the remaining amount of the sub-battery of a vehicle having a main battery and a sub-battery,
Remaining amount information acquisition means for acquiring remaining amount information of the sub-battery at the time when the vehicle starts parking;
Prediction means for predicting a timing at which the remaining capacity of the sub-battery decreases below a threshold while the vehicle is parked, based on the remaining capacity information;
Transmitting means for transmitting a notification regarding the remaining amount reduction timing to a user terminal at a timing before the remaining amount reduction timing predicted by the prediction means;
A management device comprising: 2. The notification regarding the remaining power reduction timing is a notification indicating that it is difficult for the vehicle to travel at the remaining power reduction timing due to the state of the remaining power of the sub-battery. management device. comprising a usage prediction means for predicting the timing of use of the vehicle after parking;
The transmitting means transmits a notification regarding the remaining amount reduction timing to the user terminal when the remaining amount reduction timing predicted by the prediction means arrives before the usage timing predicted by the usage prediction means. The management device according to claim 1 or 2, characterized in that: The main battery is a power source for driving a motor of the vehicle,
The sub-battery is a battery with a lower voltage output than the main battery, and is a power source for electrical components of the vehicle.
The management device according to any one of claims 1 to 3, characterized in that: The management device according to any one of claims 1 to 4, wherein the management device is communicably connected to an on-vehicle device of the vehicle. 6. The management device according to claim 5, wherein the remaining amount information acquisition means obtains the remaining amount information from the on-vehicle device. The management device according to any one of claims 1 to 4, wherein the management device is an on-vehicle device mounted on the vehicle. An information processing method performed by a management device that manages the remaining amount of the sub-battery of a vehicle having a main battery and a sub-battery, the method comprising:
a remaining amount information obtaining step of obtaining remaining amount information of the sub-battery at the time when the vehicle starts parking;
a prediction step of predicting a timing at which the remaining capacity of the sub-battery decreases below a threshold while the vehicle is parked based on the remaining capacity information;
a sending step of transmitting a notification regarding the remaining amount reduction timing to a user terminal at a timing before the predicted remaining amount reduction timing;
An information processing method comprising:

Images