Management server, management system, management method, and specific program

Abstract

This system provides a management server that can perform appropriate charging management when a vehicle performs charging power throttling control. [Solution] The management server manages the charging of the vehicle's battery. The management server is equipped with an execution device. When the execution device detects that the vehicle has performed charging power throttling control on the battery that is being charged, it performs a detection-specific process that is not performed when charging power throttling control is not being performed. When the vehicle has performed charging power throttling control, the execution device performs the detection-specific process and then performs charging management.

Description

Technical Field

[0001] The present disclosure relates to a management server, a management system, a management method, and a specific program.

Background Art

[0002] Patent Document 1 describes a management system. The management system includes a power supply facility, a vehicle having a battery charged by the power supply facility, and a management server that performs charging management of the battery.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

[0007] A management method for solving the above problems is a management method performed by a computer that manages the charging of a vehicle's battery, which includes: when it detects that the vehicle has performed charging power throttling control on the battery while it is being charged, performing a detection-specific process that is not performed when the charging power throttling control is not being performed; and when the vehicle has performed the charging power throttling control, performing the detection-specific process and then performing the charging management.

[0008] A specific program for solving the above problem is a specific program to be executed by a computer that manages the charging of a vehicle's battery, which causes the computer to perform a detection-specific process that is not performed when the vehicle has performed charging power throttling control on the battery that is being charged, and to perform the detection-specific process and then the charging management when the vehicle has performed the charging power throttling control. [Effects of the Invention]

[0009] According to the management server, management system, management method, and specific program described above, when a vehicle performs charging power throttling control, the execution device performs detection and identification processing, and then performs charging management. Therefore, the management server, management system, management method, and specific program can perform appropriate charging management when a vehicle performs charging power throttling control. [Brief explanation of the drawing]

[0010] [Figure 1] Figure 1 is a schematic diagram showing the management system of the first embodiment. [Figure 2] Figure 2 is a schematic diagram showing the vehicle and power supply equipment of the first embodiment connected together. [Figure 3] Figure 3 is a graph showing the charging command for discrimination in the first embodiment. [Figure 4] Figure 4 is a schematic diagram showing the database of the first embodiment. [Figure 5] Figure 5 is a graph showing the first aperture profile of the first embodiment. [Figure 6] Figure 6 is a graph showing the second aperture profile of the first embodiment. [Figure 7] Figure 7 is a flowchart showing a series of processes performed by the power supply equipment of the first embodiment to determine the type of vehicle. [Figure 8] Figure 8 is a flowchart showing a series of processes performed by the management server of the first embodiment to determine the type of vehicle. [Figure 9] Figure 9 is a flowchart showing a series of processes related to the predicted time performed by the management server of the first embodiment. [Figure 10] Figure 10 is a flowchart showing a series of processes, including detection identification processing, performed by the management server of the first embodiment. [Figure 11] Figure 11 is a flowchart showing a series of processes, including detection and identification processing, performed by the management server of the second embodiment. [Figure 12] Figure 12 is a graph illustrating the energy management performed by the management server in the second embodiment. [Modes for carrying out the invention]

[0011] <First Embodiment> As shown in Figure 1, the management system 10 comprises multiple vehicles 20, multiple power supply equipment 30, a management server 40, an external power supply 50, and multiple mobile terminals 60. The management system 10 manages the charging of the vehicles 20 by the power supply equipment 30.

[0012] <Overview of the Management System> The vehicle 20 has a charging port 21, a charger 22, a battery 23, and a drive motor 24. The vehicle 20 is an electric vehicle. The charging port 21 is connectable to the charging connector 31 of the power supply facility 30. When the charging connector 31 is connected to the charging port 21, the battery 23 can be charged from the power supply facility 30. Also, when the charging connector 31 is connected to the charging port 21, the vehicle 20 is in a state where it can respond to the power supply facility 30.

[0013] The drive motor 24 is a drive source of the vehicle 20. The drive motor 24 drives the vehicle 20 using the electric power stored in the battery 23. The battery 23 stores the electric power for operating the drive motor 24.

[0014] The charger 22 includes a relay that switches the connection and disconnection of the power path from the charging port 21 to the battery 23, and a power conversion circuit. By controlling the charger 22, the battery 23 is charged.

[0015] The vehicle 20 has a response circuit 25 and a control device 26. The response circuit 25 is a circuit for the vehicle 20 to respond to a charging command from the power supply facility 30. The response circuit 25 generates a response charging profile RCP described later as a PWM signal. Also, the response circuit 25 generates a response indicating the charging power as a PWM signal for a charging command at a specified power PX according to a charging plan PL described later.

[0016] The control device 26 controls the charger 22 to charge the battery 23. When the control device 26 detects that the charging connector 31 is connected to the charging port 21, the control device 26 controls the charger 22 to start charging the battery 23. The control device 26 controls the charger 22 to end charging the battery 23 by referring to the charging rate of the battery 23. In FIG. 1, only the details of one vehicle 20 are illustrated, and for other vehicles 20, part of the illustration is omitted.

[0017] The power supply equipment 30 supplies power to the vehicle 20 from an external power source 50 in order to charge the vehicle's battery 23. The power supply equipment 30 is a so-called EVSE (Electric Vehicle Supply Equipment). The power supply equipment 30 includes a charging connector 31, a command circuit 32, a charging circuit 33, a control device 34, and a communication device 35.

[0018] The charging connector 31 can be connected to the charging port 21 of the vehicle 20. The charging connector 31 is connected to the command circuit 32 by a cable. The charging connector 31 is connected to the external power supply 50 by a cable via the charging circuit 33. The external power supply 50 is located outside the vehicle 20. When the charging connector 31 is connected to the charging port 21, the power supply equipment 30 can supply power to the battery 23 from the external power supply 50 via the charging circuit 33.

[0019] The command circuit 32 is a circuit for transmitting a charging command to the vehicle 20. When the charging connector 31 is connected to the charging port 21, the command circuit 32 can transmit a charging command to the vehicle 20. The charging command includes a maximum current command value, which will be described later.

[0020] The charging circuit 33 is a circuit for charging the battery 23 from an external power source 50. When the charging connector 31 is connected to the charging port 21, the charging circuit 33 can supply power to the battery 23 from the external power source 50.

[0021] The control device 34 controls the power supply from the external power source 50 to the vehicle's battery 23 according to the charging plan PL obtained from the management server 40 via the communication device 35. The charging plan PL is time-series data of the requested power per unit time for charging over a predetermined period of time. Note that in Figure 1, only one power supply facility 30 is illustrated in detail, and the other power supply facilities 30 are partially omitted from the illustration.

[0022] The management server 40 manages the charging of multiple vehicles 20. For each type of vehicle 20, the management server 40 manages the timing of charging the vehicle 20 based on the planned mileage D to be traveled per charge. For example, for a first-type vehicle 20, when it has traveled only the first distance D1, a notification is displayed on the vehicle 20's display and on the mobile terminal 60 associated with the vehicle 20, instructing it to charge at the power supply equipment 30. Similarly, for a second-type vehicle 20, when it has traveled only the second distance D2, a notification is displayed on the vehicle 20's display and on the mobile terminal 60 associated with the vehicle 20, instructing it to charge at the power supply equipment 30.

[0023] The management server 40 manages notifications for the time when a vehicle 20 will finish charging, targeting the vehicle 20 that has started charging. The management server 40 sends a notification to the mobile terminal 60 associated with the vehicle 20 indicating the estimated time when the vehicle 20 will finish charging. As a result, the management server 40 displays the estimated time when the vehicle 20 will finish charging on the mobile terminal 60.

[0024] The management server 40 includes a communication device 41 and an information processing device 42. The communication device 41 is capable of communicating with the power supply equipment 30 via a wireless communication line. The information processing device 42 comprises an execution device 43 and a storage device 44. The execution device 43 is a CPU including a processor. The storage device 44 is memory. The storage device 44 stores a database DB, a discrimination program PR1, a prediction program PR2, and a specific program PR3.

[0025] As described later, the information processing device 42 executes the discrimination program PR1 to determine the type of vehicle 20 of the target vehicle having a battery 23 to be charged by the power supply equipment 30. Subsequently, the information processing device 42 generates a charging plan PL for charging the battery 23 of the vehicle 20 from the power supply equipment 30, according to the determined type of vehicle 20. The information processing device 42 transmits information indicating the generated charging plan PL to the power supply equipment 30 via the communication device 41.

[0026] The mobile terminal 60 is a display device that displays notifications received from the management server 40. The mobile terminal 60 is registered in the database DB for each vehicle 20. That is, the storage device 44 stores the mobile terminal 60 associated with the vehicle 20.

[0027] <Regarding the CPLT function> The power supply facility 30 has a CPLT function. The CPLT function is a function that determines whether the charging connector 31 is connected to the charging port 21 and starts charging when the charging connector 31 is connected to the charging port 21. CPLT is an abbreviation for Control Pilot.

[0028] As shown in FIG. 2, in a state where the charging connector 31 is connected to the charging port 21, the command line L1 for transmitting a charging command connects the command circuit 32 and the response circuit 25. The command line L1 is a power line. In a state where the charging connector 31 is connected to the charging port 21, the response line L2 for transmitting a response connects the command circuit 32 and the response circuit 25. The response line L2 is a power line. In a state where the charging connector 31 is connected to the charging port 21, the power supply line L3 for supplying power from the external power supply 50 to the battery 23 connects the charging circuit 33 and the charger 22. The power supply line L3 is a power line.

[0029] The command circuit 32 has, for example, a 12V power supply in order to detect the connection state between the charging connector 31 and the charging port 21. The command circuit 32 applies a voltage from the power supply to the command line L1. The response circuit 25 includes a first resistor and a second resistor.

[0030] When the charging connector 31 is not connected to the charging port 21, the voltage applied to the command line L1 does not change due to the first resistor included in the response circuit 25. On the other hand, when the charging connector 31 is connected to the charging port 21, the voltage applied to the command line L1 changes due to the first resistor included in the response circuit 25.

[0031] The control device 34 obtains the voltage of the command line L1 from a voltage sensor that detects the voltage of the command line L1. Based on the obtained voltage of the command line L1, the control device 34 determines whether or not the charging connector 31 and the charging port 21 are connected.

[0032] More specifically, when the charging connector 31 is not connected to the charging port 21, the voltage on the command line L1 remains 12V, the voltage applied from the power supply of the command circuit 32. When the charging connector 31 is connected to the charging port 21, the voltage on the command line L1 changes downstream of the response circuit 25 due to the first resistor included in the response circuit 25, from 12V to, for example, 9V. As a result, the control device 34 determines that the charging connector 31 has been connected to the charging port 21.

[0033] When the control device 34 determines that the charging connector 31 is connected to the charging port 21, the control device 26 outputs a PWM signal to the command line L1. The voltage range of the PWM signal is, for example, from -12V to +12V. The duty cycle range of the PWM signal is, for example, from 5% to 96%. In this case, the PWM signal indicates a maximum current command value of 6A to 80A.

[0034] When the control device 26 obtains the maximum current command value output to the command line L1 from the sensor 27 that detects the PWM signal of the command line L1, it changes the voltage applied to the command line L1 using a second resistor included in the response circuit 25 to indicate that charging can begin. When the second resistor is connected to the command line L1, the voltage on the command line L1 changes, for example, to 6V downstream of the response circuit 25 due to the second resistor included in the response circuit 25. As a result, the control device 34 detects that the vehicle 20 can begin charging.

[0035] When the control device 34 detects that the vehicle 20 is ready to start charging, the control device 34 controls, for example, a switch included in the charging circuit 33 to apply AC200V from the external power supply 50 to the power supply line L3.

[0036] When AC200V is applied to the power supply line L3, the control device 26 controls the charger 22 to set the current to be less than or equal to the maximum current command value and to convert it to a DC voltage using the power conversion circuit, thereby starting to charge the battery 23.

[0037] Thus, when the charging connector 31 is connected to the charging port 21 by the CPLT function, the power supply equipment 30 starts charging the battery 23. In addition, the power supply equipment 30 and the vehicle 20 communicate via power lines. Therefore, the power supply equipment 30 cannot obtain vehicle identification information such as an identification number from the vehicle 20 to identify the vehicle 20.

[0038] As shown in Figure 1, the communication device 35 can communicate with the management server 40 via a wireless communication line. On the other hand, the vehicle 20 does not communicate wirelessly with the management server 40 via the wireless communication line. Therefore, the management server 40 cannot obtain vehicle identification information from the vehicle 20.

[0039] <Regarding the charging command for discrimination> As shown in Figure 2, the control device 34 controls the command circuit 32 to output a predetermined discrimination charge command DCC to the vehicle 20 via the command line L1. The discrimination charge command DCC is a charge command used to determine the type of vehicle 20.

[0040] As shown in Figure 3, the DCC for discriminative charging command is time-series data of the requested power for charging. Specifically, the DCC for discriminative charging command instructs the requested power to be zero from time t0 to time t1. From time t1 to time t2, the DCC for discriminative charging command instructs the requested power to be the first power P1. The first power P1 is, for example, 6kW. The change in power from zero to the first power P1 is a power change of a specified magnitude or greater. Therefore, the DCC for discriminative charging command has a power change of a specified magnitude or greater. The specified magnitude is a power magnitude that has been determined in advance by tests and simulations in order to discriminate between the 20 types of vehicles. The specified magnitude is, for example, 3kW.

[0041] The DCC (Digital Control Command) for determining charging power instructs the requested power to be the second power P2 between time t2 and time t3. The second power P2 is less than the first power P1. For example, the second power P2 is 0.5 kW. The change in power from the first power P1 to the second power P2 is a power change of a specified magnitude or greater. Therefore, the DCC for determining charging power has a power change of a specified magnitude or greater.

[0042] The DCC (Digital Control Command) for determining the charging parameters instructs the requested power to be zero from time t3 to time t4. The DCC for determining the charging parameters terminates the current charging parameter when time t4 arrives. Thus, the DCC for determining the charging parameters is a time-series data of the requested power from time t0 to time t4.

[0043] Incidentally, when the vehicle 20 charges the battery 23 in accordance with the charging command, the control device 26 charges the battery 23 so that the current is less than or equal to the maximum current command value. Therefore, even when the same charging command is received, the battery 23 is charged to a charging power different from the requested power as specified in the charging command, depending on the type of vehicle 20.

[0044] <About the database> As shown in Figure 4, the database DB includes a charging profile CP associated with the vehicle type 20, a charging power restriction profile LP associated with the vehicle type 20, and a planned driving distance D associated with the vehicle type 20.

[0045] The charging profile CP is time-series data of the charging power when the vehicle 20 charges the battery 23 according to the DCC (Digital Control Command) for discrimination. Multiple charging profiles CP have been obtained in advance through testing and simulation.

[0046] The vehicle types 20 include Type 1 and Type 2. The charging profile CP associated with Type 1 is the first charging profile CP1. The charging profile CP associated with Type 2 is the second charging profile CP2. In other words, the storage device 44 stores multiple charging profiles CP for each type of vehicle 20.

[0047] The first charging profile CP1 is the charging profile CP when a first-type vehicle 20 charges the battery 23 according to the discrimination charging command DCC. For example, the first charging profile CP1 indicates that when the vehicle 20 charges the battery 23 according to the discrimination charging command DCC, charging at the first power P1 is requested, but the battery 23 is not being charged at the first power P1.

[0048] Specifically, the first charging profile CP1 indicates that the charging power is zero from time t0 to time t1. In the first charging profile CP1, charging at the first power P1 is required from time t1 to time t2, but the charging power is less than the first power P1 and greater than or equal to the second power P2. Specifically, the charging power from time t1 to time t2 is half the power of the first power P1.

[0049] The first charging profile CP1 shows that the charging power is the second power P2 from time t2 to time t3. The first charging profile CP1 shows that the charging power is zero from time t3 to time t4.

[0050] The second charging profile CP2 is the charging profile CP when a Type 2 vehicle 20 charges the battery 23 according to the discriminative charging command DCC. For example, the second charging profile CP2 indicates that when the vehicle 20 charges the battery 23 according to the discriminative charging command DCC, there is a response delay in the charging power to changes in the required power that exceed a specified magnitude.

[0051] Specifically, the second charging profile CP2 shows that the charging power is zero from time t0 to time t1. From time t1 to time t2, the second charging profile CP2 shows that the charging power gradually increases from zero to the first power P1, and then remains at the first power P1. In other words, the second charging profile CP2 shows a response delay to the change in the required power increasing from zero to the first power P1.

[0052] The second charging profile CP2 shows that the charging power gradually decreases from the first power P1 to the second power P2 between time t2 and time t3, and then the charging power is the second power P2. In other words, the second charging profile CP2 shows a response delay to the change in required power from the first power P1 to the second power P2. The second charging profile CP2 shows that the charging power is zero between time t3 and time t4.

[0053] The charging power throttling profile LP is time-series data of the charging power when charging power throttling control is performed while the vehicle 20 is charging the battery 23 at a specified power PX. The charging power throttling profile LP includes data indicating the time NT required from the start of charging power throttling control until the battery 23 is fully charged. Multiple charging power throttling profiles LP have been obtained in advance through testing and simulation.

[0054] The charging power restriction profile LP associated with Type 1 is the first restriction profile LP1. The charging power restriction profile LP associated with Type 2 is the second charging profile CP2. In other words, the storage device 44 stores multiple charging power restriction profiles LP for each type of vehicle 20.

[0055] As shown in Figure 5, the first aperture profile LP1 is the time-series data of the charging power when charging power throttling control is performed while the first type vehicle 20 is charging the battery 23 at a specified power PX.

[0056] Specifically, the first aperture profile LP1 indicates that the charging power is the specified power PX from time t10 after charging starts at the specified power PX until time t11 when charging power aperture control starts.

[0057] The first aperture profile LP1 indicates that at time t11 when the charging power aperture control is started, the charging power is reduced from the specified power PX to the first aperture power P11. The first aperture profile LP1 indicates that the charging power is the first aperture power P11 from time t11 when the charging power aperture control is started until time t12 when the charging power aperture control is ended.

[0058] The first aperture profile LP1 indicates that the charging power becomes zero at time t12. In other words, the first aperture profile LP1 indicates that the charging power aperture control and charging are completed at time t12. Therefore, in the first aperture profile LP1, the time from time t11 to time t12 is the required time NT.

[0059] As shown in Figure 6, the second aperture profile LP2 is the time-series data of the charging power when charging power throttling control is performed while the second type vehicle 20 is charging the battery 23 at a specified power PX.

[0060] Specifically, the second aperture profile LP2 indicates that the charging power is the specified power PX from time t20, after charging has started at the specified power PX, until time t21, when charging power aperture control is started.

[0061] The second aperture profile LP2 indicates that at time t21, when the charging power aperture control is initiated, the charging power is reduced from the specified power PX to the first aperture power P21. The second aperture profile LP2 indicates that from time t21 to time t22, which is after time t21, the charging power is the first aperture power P21.

[0062] The second aperture profile LP2 indicates that at time t22, the charging power decreases from the first aperture power P21 to the second aperture power P22. The second aperture power P22 is less than the first aperture power P21. The second aperture profile LP2 indicates that the charging power is the second aperture power P22 from time t22 to time t23, which is after time t22.

[0063] The second aperture profile LP2 indicates that at time t23, the charging power decreases from the second aperture power P22 to the third aperture power P23. The third aperture power P23 is less than the second aperture power P22. The second aperture profile LP2 indicates that from time t23 to time t24 (after time t23), the charging power is the third aperture power P23.

[0064] The second aperture profile LP2 indicates that at time t24, the charging power decreases from the third aperture power P23 to the fourth aperture power P24. The fourth aperture power P24 is less than the third aperture power P23. The second aperture profile LP2 indicates that from time t24 to time t25 (after time t24), the charging power is the fourth aperture power P24.

[0065] The second aperture profile LP2 indicates that the charging power becomes zero at time t25. In other words, the second aperture profile LP2 indicates that the charging power throttling control and charging have ended at time t25. Therefore, in the second aperture profile LP2, the required time NT is the time from time t21 to time t25. Thus, the second aperture profile LP2 indicates that the charging power decreases in a stepwise manner by throttling the charging power in multiple stages.

[0066] The planned mileage D is the distance that the management server 40 plans to travel per charge when performing operation management. The planned mileage D associated with Type 1 is the first distance D1. The planned mileage D associated with Type 2 is the second distance D2. Note that multiple planned mileage D values ​​have been obtained in advance through testing and simulation.

[0067] <Regarding vehicle type identification> As shown in Figure 7, when the charging connector 31 is connected to the charging port 21 of the target vehicle, the control device 34 starts a series of processes to determine the type of target vehicle. Once the control device 34 starts a series of processes to determine the type of target vehicle 20, the control device 34 first performs the process in step S11.

[0068] In step S11, the control device 34 outputs a DCC (Digital Control Command) for discrimination to the target vehicle. After that, the control device 34 proceeds to step S12. In step S12, the control device 34 generates a response charge profile RCP in response to the discriminative charge command DCC when the target vehicle charges the battery 23 in accordance with the discriminative charge command DCC. The response charge profile RCP is time-series data of the charging power when the target vehicle charges the battery 23 in accordance with the discriminative charge command DCC.

[0069] In detail, for a target vehicle to which a DCC (Digital Control Command) for discrimination has been input, the control device 26 controls the response circuit 25 to output time-series data of the charging power when charging according to the DCC for discrimination to the power supply equipment 30 via the response line L2. The response circuit 25 outputs a PWM signal to the response line L2. The PWM signal indicates the value of the current when charging. The control device 34 calculates the current value when the vehicle 20 is charging based on the detection value of the sensor 37 that detects the PWM signal. The control device 34 calculates the charging power by multiplying the voltage value when charging by the charging circuit 33 by the calculated current value. Then, the control device 34 generates the time-series data of the calculated charging power as a response charging profile RCP. After that, the control device 34 proceeds to step S13.

[0070] In step S13, the control device 34 transmits data indicating the generated response charge profile RCP from the communication device 35 to the management server 40. After that, the control device 34 terminates this series of processes.

[0071] As shown in Figure 8, when the communication device 41 receives data indicating the response charge profile RCP, the information processing device 42 starts a series of processes to determine the type of vehicle 20. In the information processing device 42, the execution device 43 starts executing the discrimination program PR1, thereby starting a series of processes to determine the type of vehicle 20.

[0072] When the execution device 43 starts executing the discrimination program PR1, the execution device 43 first starts processing in step S21. In step S21, the execution device 43 acquires the response charge profile RCP of the target vehicle received by the communication device 41. After that, the execution device 43 proceeds to step S22.

[0073] In step S22, the execution device 43 compares the response charge profile RCP with the multiple charge profiles CP. In step S22, the execution device 43 outputs the charge profile CP that matches the response charge profile RCP as the comparison result.

[0074] For example, the execution device 43 fits the response charge profile RCP to each of the multiple charge profiles CP. Then, the execution device 43 outputs the charge profile CP with the highest degree of match as the comparison result.

[0075] Specifically, when the charging power between time t1 and time t2 in the response charging profile RCP is half the power of the first power P1, the first charging profile CP1 is output as the comparison result. Also, when there is a response delay from time t1 and time t2 in the response charging profile RCP, the second charging profile CP2 is output as the comparison result. After that, the execution device 43 proceeds to step S23.

[0076] In step S23, the execution device 43 determines the type of vehicle 20 of the target vehicle based on the comparison result between the response charge profile RCP and the multiple charge profiles CP. In detail, the execution device 43 determines that the type of target vehicle is the type of vehicle 20 associated with the charging profile CP that matches the response charging profile RCP in step S22. For example, if the execution device 43 outputs a comparison result in which the response charging profile RCP matches the first charging profile CP1, the execution device 43 determines that the type of vehicle 20 of the target vehicle is type 1.

[0077] For example, if the execution device 43 outputs a comparison result showing that the response charge profile RCP matches the second charge profile CP2, the execution device 43 determines that the type of vehicle 20 of the target vehicle is type 2.

[0078] In this way, the execution device 43 determines the type of vehicle 20 of the target vehicle based on the response charge profile RCP and the multiple charge profiles CP. Furthermore, when the execution device 43 determines the type of vehicle 20, it determines the type of vehicle 20 according to the comparison result of the response charge profile RCP and the multiple charge profiles CP.

[0079] When the execution device 43 completes the processing in step S23, the execution device 43 terminates this series of processes. Subsequently, the execution device 43 transmits a charging plan PL corresponding to the type of vehicle 20 it has identified as a charging command to the power supply equipment 30. The power supply equipment 30 then outputs a charging command so that it can charge the vehicle 20 according to the charging plan PL corresponding to the type of vehicle 20. The charging plan PL corresponding to the type of vehicle 20 is the same in that it requests charging at a specified power PX, but the time for which charging is requested differs depending on the type of vehicle 20.

[0080] <Regarding the estimated time calculated at the start of charging> When the execution device 43 transmits the charging plan PL as a charging command to the power supply equipment 30, that is, when charging based on the charging plan PL is started, it starts executing the prediction program PR2, thereby initiating a series of processes for calculating and displaying the predicted time PT.

[0081] As shown in Figure 9, when the execution device 43 starts executing the prediction program PR2, the execution device 43 first starts processing in step S31. In step S31, the execution device 43 identifies the planned mileage D for the type of vehicle 20 that was determined by executing the discrimination program PR1.

[0082] For example, when the execution device 43 determines that the vehicle 20 is of type 1, it identifies the planned mileage D as the first distance D1. Also, for example, when the execution device 43 determines that the vehicle 20 is of type 2, it identifies the planned mileage D as the second distance D2. After that, the execution device 43 proceeds to step S32.

[0083] In step S32, the execution device 43 calculates a predicted time PT based on the identified planned driving distance D. The predicted time PT is the time when the battery 23 of the vehicle 20, which started charging based on the charging plan PL, is expected to finish charging. The longer the planned driving distance D, the later the predicted time PT is calculated. After that, the execution device 43 proceeds to step S33.

[0084] In step S33, the execution device 43 displays the calculated predicted time PT on the mobile terminal 60 associated with the vehicle 20 that has started charging. After that, the execution device 43 terminates this series of processes.

[0085] <Regarding the calculation of the end time, which is a detection-specific process> When the power supply equipment 30 starts charging the vehicle 20's battery 23 using the charging plan PL as a charging command, the power supply equipment 30 outputs a charging command at the specified power PX to the vehicle 20.

[0086] When vehicle 20 receives a charging command at the specified power PX, the control device 26 controls the response circuit 25 to perform charging at the specified power PX and to output a response to the power supply equipment 30 indicating that charging at the specified power PX is being performed.

[0087] While the power supply equipment 30 receives a response to the charging command from the response circuit 25, the control device 34 monitors whether charging power throttling control is being performed in response to a charging command at a specified power PX. Specifically, the control device 34 determines whether the charging power has decreased in response to a charging command at a specified power PX. When the charging power has decreased in response to a charging command at a specified power PX, the control device 34 determines whether the charging power indicated by the response is greater than zero. When the charging power indicated by the response is greater than zero, the control device 34 detects that the vehicle 20 is performing charging power throttling control.

[0088] When the control device 34 detects that charging power throttling control is being performed in the vehicle 20, the control device 34 controls the communication device 41 to send a signal to the management server 40 indicating that the vehicle 20 has performed charging power throttling control.

[0089] When the management server 40 receives a signal indicating that the vehicle 20 has performed charging power throttling control, the execution device 43 starts executing the specific program PR3. In other words, when the vehicle 20 performs charging power throttling control, the execution device 43 starts executing the specific program PR3.

[0090] As shown in Figure 10, when the execution device 43 starts executing the specific program PR3, the execution device 43 first performs the process in step S41. In step S41, the execution device 43 performs detection-time identification processing. Detection-time identification processing is not performed when charge power throttling control is not being executed. Detection-time identification processing is to calculate the end time ET when the charging of the battery 23 is completed.

[0091] In particular, the execution device 43 calculates the end time ET based on the required time NT included in the charging profile CP associated with the type of vehicle 20 on which the charging power throttling control was performed. Specifically, the execution device 43 calculates the end time ET as a time that is NT after the current time. After that, the execution device 43 proceeds to step S42.

[0092] In step S42, the execution device 43 performs detection identification processing and then manages the charging. Specifically, the execution device 43 displays the calculated end time ET on the mobile terminal 60, which is a display device, in place of the predicted time PT that was previously displayed. By displaying the end time ET, the execution device 43 informs the user of the vehicle 20 of the time when the vehicle 20 is expected to finish charging. After that, the execution device 43 terminates this series of processes.

[0093] In the first embodiment, the management system 10 implements a management method that includes performing detection-specific processing by having the execution device 43, which is a computer, execute a specific program PR3, and then performing charging management after the detection-specific processing has been performed.

[0094] The management method is a management method performed by a management system 10, which includes an execution device 43, a computer that manages the charging of the battery 23 of the vehicle 20. The management method includes detecting that the vehicle 20 has performed charging power throttling control on the battery 23 while it is being charged, and performing a detection-specific process that is not performed when charging power throttling control is not being performed. The management method also includes performing charging management after performing the detection-specific process when the vehicle 20 has performed charging power throttling control.

[0095] In other words, the specific program PR3 is executed by the execution device 43, which is a computer that manages the charging of the vehicle's battery 23. The specific program PR3 instructs the execution device 43 to perform a detection-specific process that is not performed when the vehicle 20 has performed charging power throttling control on the battery 23 that is being charged, and does not perform a detection-specific process when the charging power throttling control is not being performed. The specific program PR3 instructs the execution device 43 to perform the detection-specific process and then perform charging management when the vehicle 20 has performed charging power throttling control.

[0096] <Operation of the First Embodiment> In the first embodiment, if a vehicle 20 that has traveled the planned distance D starts charging and does not perform charging power throttling control, the vehicle 20 will end charging at the predicted time PT.

[0097] On the other hand, if vehicle 20, having traveled the planned distance D, starts charging, and then implements charging power throttling control, vehicle 20 will not complete charging at the predicted time PT. In this case, vehicle 20 will terminate charging at the end time ET.

[0098] <Effects of the First Embodiment> (1-1) The management server 40 includes an execution device 43 that manages the charging of the vehicle 20's battery 23. When the execution device 43 detects that the vehicle 20 has performed charging power throttling control on the battery 23 that is being charged, it performs a detection-specific process that is not performed when charging power throttling control is not being performed. When the vehicle 20 has performed charging power throttling control, the execution device 43 performs the detection-specific process and then performs charging management.

[0099] According to the management server 40, when the vehicle 20 performs charging power throttling control, the execution device 43 performs detection and identification processing and then manages the charging. Therefore, the management server 40 can perform appropriate charging management when the vehicle 20 performs charging power throttling control.

[0100] (1-2) The detection-based identification process is to calculate the end time ET when the battery 23 is finished charging. When the vehicle 20 performs charging power throttling control, the management server 40 can calculate the end time ET which is later than when charging power throttling control is not performed. As a result, the management server 40 can perform charging management based on the end time ET after charging power throttling control has been performed.

[0101] (1-3) The management server 40 further includes a storage device 44 that stores the required time NT from the start of charging power throttling control for each type of vehicle 20 until the charging of the battery 23 is completed. The execution device 43 calculates the completion time ET based on the required time NT for the type of vehicle 20 on which charging power throttling control was performed.

[0102] The way in which charging power is reduced during charging power throttling control may differ for each type of vehicle 20. Therefore, the required time NT may differ for each type of vehicle 20. Since the management server 40 calculates the completion time ET based on the required time NT for each type of vehicle 20 on which charging power throttling control was performed, it can calculate an appropriate completion time ET even if the required time NT differs for each type of vehicle 20.

[0103] (1-4) The execution device 43 displays the calculated end time ET on the display device associated with the vehicle 20. The management server 40 can inform the user of the vehicle 20 of the end time ET by displaying the end time ET on the display device.

[0104] (1-5) The display device is a mobile terminal 60 linked to vehicle 20. Even if the user of vehicle 20 is not on board vehicle 20, the user of vehicle 20 can still find out the end time ET.

[0105] (1-6) When the execution device 43 starts charging the battery 23, it calculates the predicted time PT at which the battery 23 will be completed based on the planned mileage D of the vehicle 20, and displays the calculated predicted time PT on the display device. When the execution device 43 displays the completion time ET on the display device, it displays the completion time ET instead of the predicted time PT.

[0106] The end time ET, calculated considering that vehicle 20 has performed charging power throttling control, is more likely to match the actual time charging ends than the predicted time PT, which is calculated regardless of whether vehicle 20 performs charging power throttling control or not. Therefore, by displaying the end time ET, which is more likely to be closer to the actual time charging ends, on the display device, the user of vehicle 20 can know the actual time charging ends more accurately.

[0107] <Second Embodiment> The management system 10 in the second embodiment will now be described with reference to the drawings. In the second embodiment, the specific details of the detection identification process and charge management differ from those of the first embodiment. The following description will focus on the differences from the first embodiment, and the same points will be simplified or omitted.

[0108] In the second embodiment, charge management is energy management. In the second embodiment, the detection and identification process is to exclude the vehicle 20 that has performed charge power throttling control from the control target of the energy management.

[0109] The management server 40 controls multiple power supply equipment 30 for multiple vehicles 20 as part of energy management. Specifically, the management server 40 adjusts the amount of power available to each vehicle 20 so that the total amount of power charged when charging using an external power supply 50 reaches a predetermined reference value RV. Therefore, the management server 40 manages the charging of the batteries 23 of multiple vehicles 20 using multiple power supply equipment 30.

[0110] <Regarding exclusion from the control target of energy management, which is a detection-based identification process> In the second embodiment, when the management server 40 receives a signal indicating that the vehicle 20 has performed charging power throttling control, the execution device 43 starts executing the specific program PR3. The specific program PR3 in the second embodiment is a program that excludes the vehicle from the control target of energy management as a detection-based specific process.

[0111] As shown in Figure 11, when the execution device 43 starts executing the specific program PR3, it first starts the process in step S51. In step S51, the execution device 43 excludes the vehicle 20 that has undergone charging power throttling control from the control target of the energy management system. After that, the execution device 43 proceeds to step S52.

[0112] In step S52, the execution device 43 calculates the throttled power PY of the vehicle 20 that was excluded by the charging power throttle control. The throttled power PY is the value obtained by subtracting the charging power when the charging power throttle control was performed from the specified power PX. After that, the execution device 43 proceeds to step S53.

[0113] In step S53, the execution device 43 distributes the throttled power PY to the vehicles 20 controlled by the energy management system. That is, the execution device 43 uses the power equivalent to the throttled power PY to charge the batteries 23 of the vehicles 20 that are not undergoing power throttling among the multiple vehicles 20. After that, the execution device 43 proceeds to the process in step S54.

[0114] In step S54, the execution device 43 determines whether charging of the vehicle 20, which has undergone charging power throttling control, has finished. For example, when the charging power indicated by the vehicle 20's response to the charging command becomes zero, the power supply equipment 30 receives a notification from the power supply equipment 30 indicating that charging of the vehicle 20 has finished. When the execution device 43 receives this notification, it determines that charging of the vehicle 20 has finished.

[0115] When the execution device 43 determines that charging of the vehicle 20 for which charging power throttling control has been performed has not been completed (S54: NO), the execution device 43 returns to step S52. Then, the process from steps S52 to S54 is repeated again.

[0116] On the other hand, when the execution device 43 determines that charging of the vehicle 20 on which charging power throttling control has been performed has been completed (S54: YES), the execution device 43 terminates this series of processes. In this way, in the second embodiment, the execution device 43 performs a detection and identification process to exclude the vehicle 20 on which charging power throttling control has been performed from the control target of energy management, and then performs energy management on the control target vehicle 20.

[0117] <Operation of the second embodiment> This explanation uses an example in which the management server 40 performs energy management for two vehicles 20, a first vehicle and a second vehicle, using two power supply facilities 30, a first power supply facility and a second power supply facility. The management server 40 performs energy management so that the sum of the charging power of the two vehicles 20 becomes the reference value RV.

[0118] As shown in Figure 12, at time t30, the first charging power PC1 of the first vehicle is at the reference value RV. Therefore, the sum of the charging powers of the two vehicles 20 is at the reference value RV. Subsequently, at time t31, which is after time t30, the first vehicle performs charging power throttling control.

[0119] When the first vehicle initiates charging power throttling control, the first vehicle is excluded from energy management control by the management server 40. Therefore, the charging power of the first vehicle changes naturally according to the charging power throttling control. As a result, from time t31 onward, the charging power of the first vehicle gradually decreases, for example.

[0120] At time t31, the management server 40 starts charging the second vehicle, using the throttle power PY of the first vehicle as the second charging power PC2, which is the charging power of the second vehicle. The first charging power PC1 gradually decreases from time t31. Therefore, the second charging power PC2 gradually increases from time t31.

[0121] Subsequently, at time t33, which is later than time t31, the charging of the first vehicle is completed. As a result, the second charging power PC2 is set to the reference value RV, and the use of the first vehicle's throttled power PY for charging the second vehicle, which is not undergoing charging power throttled control, is terminated.

[0122] <Effects of the second embodiment> In the second embodiment, in addition to the effects of the first embodiment (1-1), the following further effects are achieved.

[0123] (2-1) Charging management is an energy management system that manages the charging of multiple batteries 23 for multiple vehicles 20. The detection and identification process is to exclude the vehicle 20 that has performed charging power throttling control from the control target of the energy management system.

[0124] When the management server 40 performs energy management, vehicles 20 on which charging power throttling control is implemented have less flexibility in adjusting charging power compared to vehicles 20 on which charging power throttling control is not implemented. When performing energy management, the management server 40 excludes vehicles 20 on which charging power throttling control is implemented from the scope of energy management control. Therefore, by not including vehicles 20 with a low degree of flexibility in adjusting charging power as control targets, the management server 40 can suppress the imposition of constraints on the degree of flexibility in adjusting charging power.

[0125] (2-2) The management server 40 further includes a storage device 44 that stores a charging power throttling profile LP for each type of vehicle 20. The charging power throttling profile LP is time-series data of the charging power per unit time from the start of charging power throttling control until the charging of the battery 23 is completed. In energy management, the execution device 43 charges the batteries 23 of vehicles 20 that are not performing charging power throttling control with the throttling power PY of the vehicle 20 that is performing charging power throttling control.

[0126] In energy management, the execution device 43 can use the reduced power PY from the vehicle 20 that has performed charging power reduction control to charge the battery 23 of the vehicle 20 that has not performed charging power reduction control. Therefore, the power reduced by the vehicle 20 can be used without being excessively wasted.

[0127] The management system 10 manages the charging of the vehicle's battery 23. When the management system 10 detects that the vehicle 20 has performed charging power throttling control on the battery 23 that is being charged, it performs a detection-specific processing that is not performed when charging power throttling control is not being performed. When the vehicle 20 has performed charging power throttling control, the management system 10 performs the detection-specific processing and then manages the charging.

[0128] <Example of changes> Each of the above embodiments can be implemented with the following modifications. Each of the above embodiments and the following modifications can be combined with each other to the extent that they do not contradict each other technically.

[0129] Vehicle 20 is not limited to an electric vehicle, or so-called BEV (Battery Electric Vehicle), which is driven solely by a drive motor 24 that uses electricity stored in a battery 23. Vehicle 20 only needs to have a battery 23. For example, vehicle 20 may be a plug-in hybrid vehicle, or so-called PHEV (Plug-in Hybrid Electric Vehicle).

[0130] Vehicle 20 may be able to communicate wirelessly with the management server 40. Vehicle 20 may also be able to transmit vehicle identification information to the management server 40. The information processing device 42 may perform either the determination of the type of vehicle 20 based on the vehicle identification information or the determination of the type of vehicle 20 using the determination program PR1. Even in this case, the information processing device 42 can determine the type of vehicle 20 by executing the determination program PR1 without necessarily acquiring the vehicle identification information.

[0131] The power supply equipment 30 may be equipped with connectors and circuits for each power supply method so as to support multiple types of power supply methods, such as a DC method in addition to an AC method. The communication method between the power supply equipment 30 and the vehicle 20 is not limited to power line communication. For example, the communication method between the power supply equipment 30 and the vehicle 20 may be CAN. In this case, the power supply equipment 30 may obtain the response charge profile RCP from the vehicle 20 by obtaining information indicating the response charge profile RCP via CAN.

[0132] The display device does not have to be a mobile terminal 60 associated with the vehicle 20. For example, it may be a display mounted on the vehicle 20, or if the management server 40 has a display, it may be a display owned by the management server 40.

[0133] In each of the above embodiments, the management server 40 does not need to obtain the response charge profile RCP from the power supply equipment 30. For example, if the management server 40 and the vehicle 20 are capable of wireless communication, the management server 40 may obtain the response charge profile RCP from the vehicle 20.

[0134] The method by which the management server 40 determines the type of vehicle 20 in each of the above embodiments is not limited to the examples of the embodiments described above. For example, the management server 40 may acquire identification information to identify the vehicle 20 and determine the type of vehicle 20 based on that identification information.

[0135] The management server 40 does not need to detect that the vehicle 20 has performed charging power throttling control when the charging power of the battery 23 falls below a predetermined value. For example, the management server 40 may detect that the vehicle 20 has performed charging power throttling control by receiving a notification from the vehicle 20 indicating that charging power throttling control has been performed.

[0136] The execution device 43 does not have to calculate the predicted time PT and display the predicted time PT on the mobile terminal 60 when starting to charge the battery 23. When displaying the end time ET on the display device, the execution device 43 does not have to display the end time ET instead of the predicted time PT. For example, the execution device 43 may display the end time ET in addition to the predicted time PT on the display device.

[0137] The execution device 43 does not have to display the end time ET on the display device. For example, the execution device 43 may generate a charging plan PL for other vehicles 20 based on the calculated end time ET.

[0138] The storage device 44 does not need to store the required time NT for each type of vehicle 20. The execution device 43 does not need to calculate the end time ET based on the required time NT for each type of vehicle 20. For example, the execution device 43 may calculate the end time ET as a time that is delayed by a predetermined fixed amount of time from the predicted time PT, regardless of the type of vehicle 20.

[0139] The information processing device 42 may be configured as a circuit including one or more processors that execute various processes according to a computer program (software). Alternatively, the information processing device 42 may be configured as a circuit including one or more dedicated hardware circuits, such as application-specific integrated circuits (ASICs), or a combination thereof, that execute at least some of the various processes. The processor includes a CPU and memory such as RAM and ROM. The memory stores program code or instructions configured to cause the CPU to execute processes. Memory, or computer-readable media, includes any available media accessible by a general-purpose or dedicated computer. The same applies to the control devices 26 and 34.

[0140] The response charge profile RCP does not have to be time-series data of the charging power when charging based on the discriminative charge command DCC. For example, the response charge profile RCP may be data showing the average value of the charging power when the battery 23 is charged according to the discriminative charge command DCC. The response charge profile RCP may be data showing the response to charging when the battery 23 is charged according to the discriminative charge command DCC.

[0141] The comparison results between the response charging profile RCP and the charging profile CP are not limited to the examples of the above embodiment. For example, by fitting the response charging profile RCP to all charging profiles CP, the comparison result may match the charging profile CP with the highest degree of agreement.

[0142] When the information processing device 42 determines the type of vehicle 20, it does not need to determine the type of vehicle 20 based on the comparison result of the response charging profile RCP and the charging profile CP. For example, the information processing device 42 may calculate the difference between the response charging profile RCP and the determination charging command DCC, and then determine the type of vehicle 20 associated with the charging profile CP having the calculated difference as the type of vehicle 20 of the target vehicle. In this way, the information processing device 42 only needs to determine the type of vehicle 20 based on the response charging profile RCP and the charging profile CP.

[0143] In each of the above embodiments, the charge management does not have to be energy management that manages the charging of multiple batteries 23 for multiple vehicles 20. Also, the charge management does not have to be displaying the end time ET on a display device. For example, the charge management may be the generation of a charge plan PL. In this case, the execution device 43 only needs to generate the charge plan PL based on the result of the detection-time identification process when it performs the detection-time identification process.

[0144] In each of the above embodiments, the detection-time identification process does not necessarily have to exclude the vehicle 20 that performed the charging power throttling control from the control target of the energy management system. Also, the detection-time identification process does not necessarily have to calculate the end time ET.

[0145] In the second embodiment, the storage device 44 does not need to store the charging power throttling profile LP. In energy management, the execution device 43 does not need to charge the batteries 23 of vehicles 20 that are not performing charging power throttling control with the power reduced by the vehicles 20 that are performing charging power throttling control. For example, the execution device 43 may use a power obtained by multiplying the number of vehicles 20 performing charging power throttling control by a predetermined constant power to charge the vehicles 20 controlled by energy management.

[0146] In the management system 10, the management server 40 does not have to perform charging management and detection-based identification processing. For example, the power supply equipment 30 may perform charging management and detection-based identification processing, or if the management system 10 has a relay device that relays between the power supply equipment 30 and the management server 40, the relay device may perform charging management and detection-based identification processing. Alternatively, the power supply equipment 30 may perform detection-based identification processing and the management server 40 may perform charging management. In other words, it is sufficient for the management system 10 to perform charging management and detection-based identification processing.

[0147] [Note] The technical concepts that can be understood from the above embodiments and modified examples are described below. The technical concepts that can be understood from the above embodiments and modified examples are described below.

[0148] [Note 1] A management server for managing the charging of a vehicle's battery, comprising an execution device that, when the vehicle performs charging power throttling control on the battery while it is being charged, performs a detection-time identification process that is not performed when the charging power throttling control is not being performed, and when the vehicle performs the charging power throttling control, performs the detection-time identification process and then performs the charging management.

[0149] [Note 2] The management server described in Note 1, wherein the detection-time identification process is to calculate the completion time when the battery charging is finished. [Note 3] The management server described in Note 2 further comprises a storage device that stores the required time from the start of the charging power throttling control for each type of vehicle until the battery is charged, and the execution device calculates the completion time based on the required time for the type of vehicle on which the charging power throttling control was performed.

[0150] [Note 4] The execution device is the management server described in Note 2 or Note 3, which performs the action of displaying the calculated end time on a display device associated with the vehicle. [Note 5] The display device is the management server described in Note 4, which is a mobile terminal associated with the vehicle.

[0151] [Note 6] The execution device further performs the following actions when starting to charge the battery: calculate an estimated time when the battery will be charged based on the planned mileage of the vehicle; and display the calculated estimated time on the display device; and when displaying the completion time on the display device, the execution device displays the completion time instead of the estimated time; as described in Note 4 or Note 5.

[0152] [Note 7] The charge management is an energy management system that manages the charging of multiple batteries for multiple vehicles, and the detection and identification process excludes the vehicle that has performed the charging power throttling control from the control target of the energy management system, as described in Note 1.

[0153] [Note 8] The execution device further includes a storage device that stores time-series data of the charging power per unit time from the start of the charging power throttling control for each type of vehicle until the charging of the battery is completed, and the execution device is a management server as described in Note 7, which in the energy management charges the battery of a vehicle that has not performed the charging power throttling control with the amount of power reduced by the vehicle that has performed the charging power throttling control. [Explanation of Symbols]

[0154] 10…Management System 20... Vehicles 23…Battery 30…Power supply equipment 40…Management Server 43…Execution device 44…Storage device 50…External power supply 60… Mobile devices D...Planned mileage ET... End time NT... Required time PR3...Specific Program PT... Predicted time

Claims

1. A management server that manages the charging of vehicle batteries, When the vehicle performs charging power throttling control on the battery while it is being charged, it performs a detection-specific process that is not performed when the charging power throttling control is not being performed. When the vehicle performs the charging power throttling control, it is equipped with an execution device that performs the detection-specific processing and then executes the charging management. Management server.

2. The aforementioned detection and identification process involves calculating the end time when the battery charging is completed. The management server according to claim 1.

3. The system further includes a storage device that stores the time required from the start of the charging power throttling control for each type of vehicle until the battery is fully charged. The execution device calculates the completion time based on the required time for the type of vehicle on which the charging power throttling control was performed. The management server according to claim 2.

4. The execution device then displays the calculated end time on the display device associated with the vehicle. The management server according to claim 2 or claim 3.

5. The display device is a portable terminal linked to the vehicle. The management server according to claim 4.

6. The execution device is When starting to charge the aforementioned battery, the estimated time when the battery will be charged is calculated based on the planned mileage of the vehicle, The calculated predicted time is further displayed on the display device, When displaying the aforementioned end time on the display device, the execution device shall display the aforementioned end time instead of the predicted time. The management server according to claim 4.

7. The aforementioned charging management is an energy management system that manages the charging of multiple batteries for multiple vehicles, The detection-time identification process involves excluding the vehicle that performed the charging power throttling control from the control target of the energy management system. The management server according to claim 1.

8. The system further includes a storage device that stores time-series data of the charging power per unit time from the start of the charging power throttling control for each type of vehicle until the charging of the battery is completed. In the energy management, the execution device charges the battery of a vehicle that is not performing the charging power throttling control using the power reduced by the vehicle that has performed the charging power throttling control. The management server according to claim 7.

9. A management system for managing the charging of a vehicle's battery, When it is detected that the vehicle has performed charging power throttling control on the battery while it is being charged, the detection-specific processing that is not performed when the charging power throttling control is not being performed is executed. When the vehicle performs the charging power throttling control, the detection-specific processing is performed, and then the charging management is performed. Management system.

10. A management method performed by a management system including a computer that manages the charging of a vehicle's battery, When it is detected that the vehicle has performed charging power throttling control on the battery while it is being charged, a detection-specific processing is performed that is not performed when the charging power throttling control is not being performed. When the vehicle performs the charging power throttling control, the charging management is performed after the detection identification process is carried out. Management method.

11. A specific program to be executed by a computer that manages the charging of a vehicle's battery, To the aforementioned computer, When it is detected that the vehicle has performed charging power throttling control on the battery while it is being charged, a detection-specific processing is performed that is not performed when the charging power throttling control is not being performed. When the vehicle performs the charging power throttling control, the system will perform the detection-specific processing and then perform the charging management. A specific program.

Images