Charge control device, charging system, and charge control method

Abstract

To provide a charge control device capable of controlling to prevent a charging device from being overloaded.SOLUTION: A charge control device for a charging device 103 controls charging to each of a plurality of electrically chargeable vehicles connected to the charging device, the charging device being a device which electrically charges each vehicle in an apartment house and in which maximum usage power to simultaneously charge the plurality of vehicles is set. In the case where charging is requested from a vehicle while the number of vehicles exceeds the maximum number of simultaneously chargeable vehicles within a range of the maximum usage power ("No" in a step S175), charging to the vehicle that requests charging while exceeding the maximum number of vehicles is brought into a standby state (a step S180).SELECTED DRAWING: Figure 19A

Description

[Technical field]

[0001] The present invention relates to the electrical charging of electrically chargeable vehicles. [Background technology]

[0002] As a technology for charging a vehicle, for example, one has been disclosed that "has a plurality of chargers 2 for charging vehicles 4, and a charging control unit 3 that controls the charging current of the chargers 2, has a first measurement unit 31a that obtains received power information from an electricity meter 10 that measures received power from commercial power P, and a second measurement unit 31b that obtains current and voltage information flowing through a step-down transformer 5b that converts the received high-voltage power to low-voltage power and supplies it to the charger 2, and the charging control unit 3 compares the received power information obtained by the first measurement unit 31a with a predetermined first set value and controls it so that it does not exceed the first set value, and also compares the power information obtained by the second measurement unit 31b with a predetermined second set value and controls it so that it does not exceed the second set value" (for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2020-188669 A [Patent Document 2] JP 2023-034166 A Summary of the Invention [Problem to be solved by the invention]

[0004] The above technology makes it possible to control charging of a vehicle so that the capacity of the power receiving equipment is not overloaded. However, there is a problem in that it is necessary to provide a first measurement unit and a second measurement unit, making the equipment complicated. An object of the present invention is to provide a charge control device and the like that can control a charging device so as not to overload it, without providing a measuring unit or the like. [Means for solving the problem]

[0005] The charging control device of the present invention is a device that electrically charges each of a plurality of vehicles that can be electrically charged in an apartment building, and is a charging control device that controls charging of the vehicles connected to the charging device, and when a charging request is made and charging the vehicle for which charging has been requested would exceed the maximum power usage, the charging control device puts the charging of the vehicle for which charging has been requested into a standby state. The charging system of the present invention is a charging system that electrically charges a plurality of vehicles that can be electrically charged in an apartment building, and comprises a charging device having a plurality of connectors that can be connected to each of the plurality of vehicles, and a charging control device that controls charging of the vehicles by the charging device, wherein the charging device is set with a maximum power usage for simultaneously charging the plurality of vehicles, and the charging control device is the charging control device described above. The charging control method of the present invention is a charging control method for controlling charging of vehicles connected to a charging device that electrically charges each of a plurality of vehicles that can be electrically charged in an apartment building, and which has a maximum power usage set for simultaneously charging the plurality of vehicles, and which controls charging of the vehicles connected to the charging device, in which, when a charging request is made and charging the vehicle for which charging has been requested would exceed the maximum power usage, charging of the vehicle for which charging has been requested is put into a standby state. In the charging control device, charging system, and charging control method of the present invention, the determination of "when a charging request is made, charging the vehicle for which charging has been requested would exceed the maximum power usage" may be made based on the number of vehicles for which charging has been requested, or may be made based on the total power usage including the vehicles for which charging has been requested. Effect of the Invention

[0006] According to the above configuration or method, it is possible to control the charging equipment (distribution board) so that it does not become overloaded. [Brief description of the drawings]

[0007] [Figure 1] 1 is a schematic diagram of a charging system according to a first embodiment. [Diagram 2] FIG. 2 is a diagram illustrating the hardware configuration of a mobile terminal. [Diagram 3] FIG. 2 is a diagram illustrating the hardware configuration of a charging control device. [Figure 4A] FIG. 2 is a diagram showing a charging request table in FIG. [Figure 4B] FIG. 2 is a diagram showing a status table after the connection in FIG. [Diagram 5] This is a schematic diagram after connection to the connector "1" of the charging device. [Figure 6A] FIG. 6 is a diagram showing a charging request table after connection to the connector “1” in FIG. 5. [Figure 6B] FIG. 6 is a diagram showing a status table after connection to the connector "1" in FIG. 5. [Figure 7] This is a schematic diagram after connection to the connector "5" of the charging device. [Figure 8A] FIG. 8 is a diagram showing a charging request table after connection to the connector “5” in FIG. 7. [Figure 8B] FIG. 8 is a diagram showing a status table after connection to the connector “5” in FIG. 7. [Figure 9A] 8 is a diagram showing a charging request table after connection to the connector "5" in FIG. 7 and charging of the connector "6" is completed. FIG. [Figure 9B] FIG. 8 is a diagram showing a status table after connection to the connector “5” in FIG. 7 and charging of the connector “6” is completed. [Figure 10] FIG. 11 is a schematic sequence diagram of a case where charging is possible in the charging system. [Figure 11] FIG. 11 is a schematic sequence diagram of a case where charging is not possible in the charging system. [Figure 12] FIG. 4 is a schematic sequence diagram when charging is completed in the charging system. [Figure 13] FIG. 4 is a schematic sequence diagram of a case where charging is possible from a standby state in the charging system. [Figure 14] 5 is a flowchart showing a process of a control unit of the charging device. [Figure 15] 13 is a flowchart showing the process of a control unit of the OCPP server. [Figure 16] 13 is a flowchart showing charging start processing of an OCPP server. [Figure 17] 13 is a flowchart showing charging completion processing of the OCPP server. [Figure 18] 13 is a flowchart showing the process of a control unit of a database. [Figure 19A] 13 is a flowchart showing the process of a control unit of the AP server. [Figure 19B] 13 is a flowchart showing the process of a control unit of the AP server. [Figure 20] FIG. 2 is a hardware configuration diagram of a charge control device according to a first embodiment A. [Figure 21] FIG. 11 is a schematic sequence diagram of a case where charging is possible in the charging system. [Figure 22] FIG. 11 is a schematic sequence diagram of a case where charging is not possible in the charging system. [Diagram 23] FIG. 4 is a schematic sequence diagram when charging is completed in the charging system. [Figure 24] FIG. 4 is a schematic sequence diagram of a case where charging is possible from a standby state in the charging system. [Diagram 25] FIG. 4 is a hardware configuration diagram of a charge control device according to a first embodiment B. [Figure 26A] FIG. 11 is a diagram showing a status table according to the first embodiment C. [Figure 26B] FIG. 13 is a diagram showing a customer information table according to the first embodiment C. [Figure 27] 13 is a flowchart showing the process of a control unit of the AP server. [Figure 28] 13 is a flowchart showing the process of a control unit of the OCPP server. [Figure 29] FIG. 11 is a schematic sequence diagram when charging is completed in the charging system according to the first modified example. [Diagram 30] FIG. 11 is a schematic sequence diagram when charging is completed in the charging system according to the first modified example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] First Embodiment As shown in FIG. 1, the charging system 101 is used in a parking lot of a collective housing complex such as an apartment building or an apartment complex, or in an indoor parking lot (contract parking) capable of parking a plurality of vehicles. The charging system 101 performs electrical charging on a plurality of vehicles 1 that are parked in a parking lot under a contract or the like and that are capable of being electrically charged. The electrically rechargeable vehicle 1 referred to here includes electric vehicles that do not have an engine, hybrid vehicles that are combined with an engine, electric vehicles that run on electricity generated by an engine, etc. Vehicles 1 also include four-wheeled vehicles, three-wheeled vehicles, two-wheeled vehicles, etc. The charging system 101 includes a charging device 103 having a plurality of connectors 131 connectable to a plurality of vehicles 1, respectively, and a charging control device 105 that controls charging of the vehicles 1 by the charging device 103. When the vehicle 1 is connected to the connector 131 of the charging device 103 and an operation to request the start of charging (also called a charging request operation) is received from the owner or user (of the mobile terminal 3) of the vehicle, the charging control device 105 instructs the charging device 103 to start charging while taking into account the power usage. FIG. 1 shows an outline of a charging system 101, in which, for example, a charging device 103 can be connected to six vehicles 1, that is, the charging system 101 has six connectors 131.

[0009] First Embodiment 1. Overall structure In the charging system 101 of the first embodiment, the maximum number of vehicles 1 that can be charged simultaneously is set to three as the maximum power usage for simultaneously charging a plurality of vehicles 1. In other words, the charging power of vehicle 1 and the maximum number of vehicles 1 that can be charged with the maximum power usage are set in advance, and assuming that the vehicle 1 that has requested charging is charged, if the number of vehicles that have requested charging is less than the maximum number, the vehicle 1 that has requested charging is charged, and if the number of vehicles that have requested charging is equal to or greater than the maximum number, the vehicle 1 that has requested charging is put on hold for charging. It should be noted that these specific forms are provided merely to illustrate the embodiments, and the present invention is not limited to these forms.

[0010] 2.Each part Each device constituting the charging system 101 will be described below. (1)Charging device The charging device 103 is connected to the distribution board 2 and receives a supply of power. The charging device 103 has a circuit unit 132 that receives power from the distribution board 2 and converts it into a charging voltage, a control unit 133 that controls charging of the vehicle 1 by instructing the circuit unit 132 to start and complete charging, and a communication unit 134 that communicates with the charging control device 105. The control unit 113 instructs the circuit unit 132 to start charging, complete charging, wait for charging, etc., for the connector 131 instructed by the charging control device 105 via the communication unit 134 .

[0011] (2) Mobile devices As shown in FIG. 2, the mobile terminal 3 includes a display unit, an operation unit, a control unit 33, a communication unit 34, and a storage unit 35, and has a mobile terminal application installed therein. Here, the display section and the operation section are configured by a touch panel section 36. The control unit 33 includes a CPU, a ROM, a RAM, etc., and performs various processes by the CPU executing programs and applications stored in the storage unit 35 in accordance with operations by the user. The storage unit 35 includes a non-volatile storage medium such as a flash memory, and stores, for example, an operating system, programs, applications, and various data for performing various processes. The communication unit 34 performs data communication, Bluetooth (registered trademark) communication, Wi-Fi (registered trademark) communication, and the like via a network (eg, the Internet) using a telephone line or an optical line. By executing the mobile application, the mobile application becomes capable of communicating with the AP server 108, and various information is transmitted and received. Note that, by a user registering with the AP server 108 via the mobile application, the user ID of the user (vehicle 1) is associated (linked) with the connector 131 of the charging device 103 used for charging. When the user connects the vehicle 1 to be used to the connector 131 of the charging device 103, the user uses the mobile application of the mobile terminal 3 to perform a charging request operation on the touch panel unit . When the control unit 33 receives a charging request operation from the touch panel unit 36, it transmits a request for charging (hereinafter referred to as a “charging request”) to the AP server 108. When the control unit 33 receives a report that charging has started (hereinafter referred to as a “charging start report”), a report that charging has been completed (hereinafter referred to as a “charging completion report”), or a report that charging is waiting (hereinafter referred to as a “charging wait report”) via the mobile application, it displays the report on the touch panel unit 36.

[0012] (3) Charging control device As shown in FIG. 3, the charging control device 105 is configured with one or more servers, virtual servers, or a combination thereof. The charging control device 105 includes an OCPP server 106 that functions as a first server capable of communicating with the charging device 103, a database (hereinafter, referred to as "DB" in the drawings) 107 that stores charging request data (charging request history) of the vehicle 1 being charged by the charging device 103 and charging status data indicating the charging status, and an AP server 108 that functions as a second server that issues charging instructions, etc. to the OCPP server 106 in accordance with a charging request from a user (mobile terminal 3). The OCPP server 106, the database 107, and the AP server 108 are configured to be able to communicate with each other, and the OCPP server 106 and the charging device 103 are connected based on the OCPP (Open Charge Point Protocol). In other words, the charging device 103 is a so-called CP (Charge Point). The OCPP server 106, the database 107, and the AP server 108 are provided on a public cloud such as AWS, Azure, or Google Cloud Platform. This can improve communication efficiency and can be easily implemented. Each server will be described below.

[0013] (3-1) Database As shown in FIG. 3, the database 107 includes a control unit 171, a storage unit 173, and a clock 175. The storage unit 173 includes, for example, a non-volatile storage medium such as an HDD, an SDD, or a flash memory, and stores, for example, a charging request table T11 (see FIG. 4A) that stores a charging request, a status table T12 (FIG. 4B) that stores a charging state (status), etc. The clock 175 has a calendar function and measures the date.

[0014] 4A, the charging request table T11 keeps a record of charging requests, and new charging requests are added if any. The charging request table T11 stores data such as a "charging number" indicating the order in which the charging requests were received, a "connector ID" indicating the ID of the connector 131 to which the vehicle 1 to be charged is connected, a "charging result" indicating whether charging is complete or not, a "request date and time" indicating the date and time when the charging request was made, and a "charging completion date and time" indicating the date and time when the requested charging was completed. When referring to an item in the charging request table T11 and the data stored in that item, " " may be added to the item. For example, "charging number" may refer to the item "charging number" in the table, or may refer to data such as "20230401-1."

[0015] The status table T12 stores data such as a "charging number" that indicates the order of the charging request and is the same data as the "charging number" in the charging request table T11, a "connector ID" that indicates the ID of the connector 131 to which the vehicle 1 to be charged is connected and is the same data as the "connector ID" in the charging request table T11, a "charging status" that indicates the status of charging, and a "start time" that indicates the time when charging of the vehicle 1 for which charging has been requested begins. The charging state includes "charging" and "standby" as shown in FIG. 8B, as well as "charged." Note that " " may be added to an item in the status table T12 and the information stored in that item. For example, "charging number" may mean the item "charging number" in the table, or may mean information such as "20230401-1."

[0016] The charging request table T11 and the status table in FIG. 4 show the state in FIG. As shown in FIG. 4A, in the charging request table T11, charging requests are made in the order of connector IDs "3", "1", "5", "2", "6", and "3", and the connector IDs are stored in this order. Connector IDs "3", "1", "5", and "2" have already completed charging, and the "Charging Result" item is marked as "Completed." Connector IDs "6" and "3" are currently charging, and the "Charging Result" item is marked as "Incomplete." Note that vehicles 1 connected to connectors IDs "1" and "5" are used (not connected) in FIG. 1, while vehicle 1 with connector ID "4" remains connected. For charging number "20230404-5" with connector ID "6", charging began at "22:00", and for charging number "20230401-6", charging began at "22:30", and the charging status for both "charging numbers" is "charging".

[0017] The charging request table T11 and the status table T12 in FIG. 6 show the state in FIG. In FIG. 5, in contrast to FIG. 1, a vehicle 1 is connected to connector "1" and is being charged. In the charging request table T11 shown in Fig. 6A, data "2023-0401-7" has been added to the bottom of the "charging number" field of a new record as a new charging request using connector "1" compared to Fig. 4A. In the status table T12 shown in Fig. 6B, data "20230401-7" has been added to the bottom of the "charging number" field of a new record as a new charging request using connector "1" compared to Fig. 4B. The vehicle 1 with the charging number "20230401-7" corresponds to the third vehicle, which is the maximum number of vehicles that can be charged by the charging device 103 in this example, and is currently being charged.

[0018] The charging request table T11 and the status table T12 in FIG. 8 show the state in FIG. In FIG. 7, in contrast to FIG. 5, vehicle 1 has been newly connected to connector "5". However, since the current number of vehicles being charged is the same as the maximum number, the vehicle is not being charged and is in a standby state. 8, a record with a charging number of "20230401-8" has been added as a new charging request using the connector "5" to the charging request table T11 and the status table T12 shown in FIG.

[0019] FIG. 9 shows the state when charging for the charging number "20230401-5" is completed. In FIG. 9A, in the record with the charging number "20230401-7", the charging result has been updated to "Completed" and the charging completion date and time has been updated to "20230402:0600". In Figure 9B, charging for the vehicle with charging number "20230401-5" has been completed, so the record for this "charging number" is deleted, and the number of vehicles 1 with a charging status of "charging" becomes two. After this, charging of the vehicle with charging number "20230401-8" begins (in Figure 9B it is listed as "Waiting").

[0020] The control unit 171 includes a CPU, a ROM, a RAM, etc., and creates and updates a new charging request in the charging request table T11, and registers, updates, and deletes in the status table T12 in response to a request from the OCPP server 106 or the AP server 108. Note that the control unit 171 responds to the requesting server after updating the tables T11 and T12 in response to a request. Note that the time in the tables T11 and T12 may be acquired and registered on the database 107 side.

[0021] (3-2) OCPP Server 3, the OCPP server 106 includes a control unit 161, a communication unit 162, and a storage unit 163, and executes a CP application. The OCPP server 106 is connected to an external payment system that manages charges due to charging, for example, via a communication protocol such as OICP (Open InterChange Protocol) or OCPI (Open Charge Point Interface). The control unit 161 includes a CPU, a ROM, a RAM, etc., and the CPU executes a program stored in the storage unit 163 to process the CP application. The storage unit 163 includes, for example, a non-volatile storage medium such as an HDD, an SDD, or a flash memory, and stores, for example, an operating system for performing various processes, application programs, and various data. Here, the communication unit 162 communicates with the charging device 103 based on the OCPP, which is an international standard, and communicates with the AP server 108 by using a WEB-API. The database 107 is provided on a public cloud where the OCPP server 106 is provided, and requests to the database 107 are made using SQL.

[0022] As shown in FIG. 10, when the OCPP server 106 receives an instruction to start charging (hereinafter referred to as a "charging start instruction") from the AP server 108, it outputs a signal to the charging device 103 to start charging (hereinafter referred to as a "charging start signal"), requests the database 107 to register a status indicating the start of charging (hereinafter referred to as a "charging start registration request"), and, if charging starts normally, responds to the AP server 108 that charging is normal (hereinafter referred to as a "charging start response"). When the OCPP server 106 receives a command to start charging, it outputs a signal including the "connector ID" of the charging target (hereinafter referred to as the "start preparation signal") to the charging device 103, and in response to this, the charging device 103 outputs a response signal indicating that the vehicle 1 is connected to the target connector 131. This makes it possible to confirm whether the user's vehicle 1 is actually connected to the connector 131 for which the user has requested charging. The charging start instruction to the charging device 103 utilizes transaction management, and the response signal output from the charging device 103, which is a response signal (remote start transaction) to the charging start signal (start transaction), is also a "normal charging start signal" indicating that charging has started normally.

[0023] As shown in FIG. 12, when the OCPP server 106 receives an instruction to complete charging (hereinafter referred to as a "charging completion instruction") from the AP server 108, it outputs a signal to the charging device 103 to complete charging (hereinafter referred to as a "charging completion signal"), requests the database 107 to update the status to indicate completion of charging (hereinafter referred to as a "completion update request"), and, when charging is completed normally, responds to the AP server 108 that charging has been completed normally (hereinafter referred to as a "charging completion response"). When the OCPP server 106 receives a charging completion instruction, it outputs a signal including the "connector ID" of the charging target (hereinafter referred to as the "completion preparation signal") to the charging device 103, and in response to this, the charging device 103 outputs a response signal indicating that the vehicle 1 is being charged to the target connector 131. This makes it possible to confirm whether the user's vehicle 1 connected to the connector 131 requested by the user to be charged will complete charging. The charging completion instruction utilizes transaction management, and the response signal output from the charging device 103, which is a response signal (remote stop transaction) to the charging completion signal (stop transaction), is also a "normal charging completion signal" indicating that charging has been completed normally.

[0024] 13, the OCPP server 106 determines whether charging is possible in response to a waiting charging request, and if charging is possible, outputs a charging start signal to the charging device 103, requests the database 107 to update the charging status to "charging" to start, and sends a charging start response to the AP server 108 when charging starts normally. Note that the charging start signal utilizes transaction management in the same way as the charging start signal when a charging start instruction is received from the AP server 108, and the response signal (remote start transaction) output from the charging device 103 to the charging start signal (start transaction) also serves as a "normal charging start signal" indicating that charging has started normally. Whether charging is possible in response to a waiting charging request is determined based on the "charging state" in the status table T12 of the database 107, so a request to acquire the status (hereinafter referred to as a "status acquisition request") is made to the database 107 before the determination.

[0025] In this way, by making the control unit 161, the communication unit 162, and the memory unit 163 work together, the OCPP server 106 is provided with a charging start instruction receiving unit that receives a charging start instruction from the AP server 108, a charging start signal output unit that outputs a signal (which may include a start preparation signal) for causing the charging device 103 to start charging in accordance with the charging start instruction from the AP server 108, a normal charging start signal input unit to which a normal charging start signal (including a response signal if the start preparation signal is included) is input from the charging device 103, a charging start response transmitting unit that transmits a charging start response to the AP server 108 when the normal charging start signal is input from the charging device 103, a start registration request output unit that outputs a status start registration request to the database 107, and a start registration response input unit to which the response to the start registration request is input from the database 107, as shown in FIG. 10. In addition, by making the control unit 161, the communication unit 162 and the memory unit 163 work together, the OCPP server 106 is provided with, as shown in FIG. 12, a charging completion instruction receiving unit that receives a charging completion instruction from the AP server 108, a charging completion signal output unit that outputs a signal (which may include a completion preparation signal) to cause the charging device 103 to complete charging in accordance with the charging completion instruction from the AP server 108, a normal charging completion signal input unit to which a normal charging completion signal (including a response signal if the completion preparation signal is included) is input from the charging device 103, a charging completion response sending unit that transmits a charging completion response to the AP server 108 when the normal charging completion signal is input from the charging device 103, a completion update request output unit that outputs a status completion update request to the database 107, and a completion update response input unit to which the response to the completion update request is input from the database 107. In addition, by making the control unit 161, the communication unit 162 and the memory unit 163 work together, the OCPP server 106 is provided with a chargeability determination unit that determines whether charging is possible in response to a waiting charging request, as shown in FIG. 13, a charge start signal output unit that outputs a signal (including a start preparation signal) to cause the charging device 103 to start charging when it is determined that charging is possible, a normal charge start signal input unit to which a normal charge start signal (including a response signal if the start preparation signal is included) is input from the charging device 103, a charge start response transmission unit that transmits a charge start response to the AP server 108 when the normal charge start signal is input from the charging device 103, a start update request output unit that outputs a status start update request to the database 107, and a start update response input unit to which the response to the start update request is input from the database 107.

[0026] (3-3) AP Server As shown in FIG. 3, the AP server 108 includes a control unit 181, a communication unit 182, a storage unit 183, and a clock 184. The control unit 181 includes a CPU, a ROM, a RAM, etc., and the CPU executes a program stored in the storage unit 183 to process an AP application. The storage unit 183 includes a non-volatile storage medium such as an HDD, an SDD, or a flash memory, and stores, for example, application programs and various data. The communication unit 182 communicates with the OCPP server 106 and the mobile terminal 3, for example, by using a WEB-API, or by using data communication using a network (for example, the Internet) that uses a telephone line or an optical line, Bluetooth (registered trademark) communication, Wi-Fi (registered trademark) communication, etc. For communication with the database 107, SQL is used. The clock 184 measures the date and time when charging is requested, the time when charging starts, and the time when charging is completed. These measured dates and times are stored in the database 107. The clock 184 has a calendar function and measures the date and time. The AP server 108 receives a charging request from the portable terminal 3, and transmits a charging start report, a charging completion report, and a charging standby report. The AP server 108 transmits a charging start instruction and a charging completion instruction to and receives a charging start response and a charging completion response from the OCPP server 106. When a new charging request is received from the mobile terminal 3, the AP server 108 instructs the OCPP server 106 to start charging by determining whether or not charging is possible for the vehicle 1 that has received the charging request, and issuing the charging start instruction if charging is possible. The AP server 108 sends, to the database 107, a request to create a new charging request in the charging request table T11, a request to update the completion of charging, a request to obtain the status of the charging state, and a request to register, update, or delete the status.

[0027] 10, when the AP server 108 receives a charge request from the mobile terminal 3, the AP server 108 requests the database 107 to create a new charge request in the charge request table T11 and to obtain the status. In response to these requests, the database 107 makes a creation response or an acquisition response. The AP server 108 determines whether charging is possible for the vehicle 1 for which a new charging request has been made, and if charging is possible (as in the case of Figures 1 and 5), it sends a charging start instruction to the OCPP server 106, and when it receives a charging start response from the OCPP server 106 indicating that charging has started normally in response to the charging start instruction, it reports the start of charging to the mobile terminal 3. As shown in FIG. 11, the AP server 108 determines whether charging is possible for the vehicle 1 that has newly requested charging, and if charging is not possible, requests that a status of "waiting" be registered in the status table T12 of the database 107 (hereinafter referred to as a "waiting registration request"). When a registration response is input from the database 107 to the waiting registration request, the AP server 108 transmits a charging waiting report to the mobile terminal 3. As shown in FIG. 12, the AP server 108 determines whether charging of the vehicle 1 being charged has been completed, and if charging has been completed, sends a charging completion instruction to the OCPP server 106, or sends a charging completion report to the portable terminal 3 when it receives a charging completion response from the OCPP server 106 indicating that charging has been successfully completed in response to the charging completion instruction.

[0028] In this way, the AP server 108, by making the control unit 181, the communication unit 182, and the memory unit 183 work together, has a charging request receiving unit that receives a charging request from the portable terminal 3, a charging feasibility determination unit that determines whether charging is possible for the vehicle 1 that has been requested to be charged, a charging start instruction transmitting unit that transmits a charging start instruction to the OCPP server 106 when it is determined that charging is possible, a charging start response receiving unit that receives a charging start response from the OCPP server 106, a charging start report transmitting unit that transmits a charging start report to the portable terminal 3 when there is a charging start response, and a charging completion report transmitting unit that determines whether charging of the vehicle 1 being charged is completed. The charging completion information transmitting unit includes a determination unit, a charging completion instruction transmitting unit which transmits a charging completion instruction to the OCPP server 106 when it is determined that charging is completed, a charging completion response receiving unit which receives a charging completion response from the OCPP server 106, a charging completion report transmitting unit which transmits a charging completion report to the portable terminal 3 when a charging completion response is received, a request output unit which outputs to the database 107 requests for creating a charging request, updating a charging request, etc. in the charging request table T11, and requests for acquiring, registering, updating, waiting, deleting, etc. of a status in the status table T12, and a response input unit which inputs the requested response from the database 107.

[0029] 3. Sequence (1) Charging request 1, a case will be taken as an example in which the vehicle 1 is connected to the connector 131 with a connector ID of "1." The user connects the vehicle 1 to the connector 131, and uses a mobile application to perform a charging request operation on the mobile terminal 3 as shown in FIG. When the AP server 108 receives a charging request (for example, connector "1" in FIG. 5) from the mobile terminal 3, it requests the database 107 to create a new charging request. In response to this request, the database 107 creates a record with a charging number of "20230401-7" as a new request in the charging request table T11 as shown in FIG. 6A, registers "1" as the connector ID, "incomplete" as the charging result, and "20230401:2300" as the request date and time, and sends a creation response to the AP server 108. Next, the AP server 108 requests the database 107 to obtain a status. In response to this request, the database 107 obtains the contents of the status table T12 shown in Fig. 4B and responds to the AP server 108. Here, charging has not started for the connector 131 with the connector ID "1" in Fig. 5, and the number of devices being charged is two in the status table T12 in Fig. 4B.

[0030] (2) Start charging The AP server 108 judges from the status returned from the database 107 whether charging is possible in response to the new request. (2-1) Rechargeable For example, in FIG. 1, charging of devices with connector IDs other than "1" is possible only for two devices with connector IDs "6" and "3", which is less than the maximum number of devices that can be charged (3). Therefore, charging is determined to be possible. When it is determined that charging is possible, the AP server 108 transmits a charge start instruction to the OCPP server 106 as shown in Fig. 10. The charge start instruction has a transaction function and becomes a remote start transaction. The charge start instruction includes data of the "connector ID" for which charging was requested. Upon receiving the instruction to start charging, the OCPP server 106 outputs a start preparation signal to the charging device 103. The charging device 103 to which the start preparation signal has been input checks the connection of the "connector ID" included in the start preparation signal, and outputs a response signal to the OCPP server 106 indicating that the connection is established. In response to this, the OCPP server 106 determines that the "connector ID" for which the charging request was made matches the "connector ID" to which the vehicle 1 of the charging device 103 is connected, and requests the database 107 to start registration. As shown in Fig. 6B, the database 107 registers "20230401-7" as the charging number, "1" as the connector ID, "charging" as the charging status, and "23:00" as the start time, and responds to the OCPP server 106 with a request for start registration. The OCPP server 106 outputs a charging start signal to the charging device 103, and the charging device 103 starts charging to the connector 131 with a connector ID of "1" and outputs a response signal to the effect that charging has started to the OCPP server 106. Note that the response signal is a normal charging start signal, and serves as a remote start transaction. When the OCPP server 106 receives the response signal (normal charging start signal), it transmits a charging start response to the AP server 108, and in response to this, the AP server 108 reports to the portable terminal 3 that charging has started.

[0031] (2-2) Cannot be charged For example, in Fig. 5, when vehicle 1 is connected to connector ID "5" and a new charging request is made from the user of vehicle 1, charging with connector IDs other than "5" is possible for three vehicles with connector IDs "6," "3," and "1," which match the maximum number of vehicles that can be charged (three). In this state, charging vehicle 1 with connector ID "5" would exceed the maximum number of vehicles. For this reason, it is determined that charging is not possible. When the AP server 108 determines that the new charging request is not chargeable, it requests the database 107 to register a standby status for charging, as shown in Fig. 11. The database 107 registers "20230401-8" as the charging number, "5" as the connector ID, and "waiting" as the charging status, as shown in Fig. 8B, and responds to the OCPP server 106 with the standby registration. When the AP server 108 receives a standby registration response from the database 107, the AP server 108 reports the charging standby state to the mobile terminal 3.

[0032] (2-3) Charging completed The AP server 108 determines whether or not charging is complete based on the elapsed time from the start of charging. For example, in FIG. 8B, the charging start time for the charging number "20230401-5" is "2200", and it is determined whether a predetermined time (here, 8 hours) has elapsed since the charging start time. Therefore, the AP server 108 makes a request to acquire the charging start time from the database 107 that stores the "start time" of charging in a status table T12, as shown in FIG. When a start time acquisition request is made, the database 107 acquires the "start time" and returns the acquisition response to the AP server 108. When it is determined that charging is complete based on the acquired "start time", a charging completion instruction is sent to the OCPP server 106 as shown in Fig. 12. The charging completion instruction has a transaction function and becomes a remote stop transaction. The charging completion instruction includes data on the "connector ID" of charging completion. When receiving the charge completion instruction, the OCPP server 106 outputs a completion preparation signal to the charging device 103. When the completion preparation signal is input, the charging device 103 checks the connection of the "connector ID" included in the completion preparation signal, and outputs a response signal to the OCPP server 106 to the effect that the connection is established. In response to this, the OCPP server 106 determines that the "connector ID" for charging completion matches the "connector ID" to which the vehicle 1 of the charging device 103 is connected, and requests a charging completion update from the database 107. The database 107 updates the charging status of the record with the charging number "20230401-5" to "Charged" and responds with a completion update to the OCPP server 106. The OCPP server 106 outputs a charging completion signal to the charging device 103, and the charging device 103 completes charging for the connector ID "6" and outputs a response signal indicating that charging has been completed to the OCPP server 106. Note that the response signal is a normal charging completion signal, and serves as a remote stop start transaction. When the OCPP server 106 receives the response signal (normal charging completion signal), it transmits a charging completion response to the AP server 108, and upon receiving this, the AP server 108 reports the charging completion to the portable terminal 3. Furthermore, upon receiving a charging completion response, the AP server 108 requests updating of the “charging result” and “charging completion date and time” of the corresponding charging number (connector ID) in the charging request table T11 of the database 107, and requests deletion of the record corresponding to the “charging number” for which charging has been completed in the status table T12. The database 107 updates the charging result corresponding to the connector ID "6" in the charging request table T11 to "completed" and the charging completion date and time to "20230402:0300" as shown in FIG. 9A, and deletes the record with the "connector ID" of "6" in the status table T12 as shown in FIG. 9B, and responds to the AP server 108.

[0033] (2-4) Starting charging during standby The OCPP server 106 judges whether charging is possible in response to a waiting charging request. Here, this is judged based on the number of "charging" units in the status table T12. For example, in FIG. 8B, three devices with connector IDs "6," "3," and "1" are charging, and charging with "connector ID" "5" is "on standby." After that, charging of the vehicle with the charging number "20230401-5" in the charging request table T11 in FIG. 9A is completed, two vehicles are "charging" in the status table T12 in FIG. 9B, and charging of the vehicle with the charging number "20230401-8" becomes possible. As shown in FIG. 13, the OCPP server 106 requests the database 107 to obtain the status, and in response to this request, the database 107 returns the status to the OCPP server 106. The OCPP server 106 counts the number of "charging" statuses returned (the number of vehicles currently being charged) and determines whether charging is possible. In FIG. 9B, since the number of vehicles being charged is "2", which is less than the maximum number of "3", it is determined that charging is possible for vehicle 1 with the "on standby" charging number "20230401-8". 13, when it is determined that charging is possible, the OCPP server 106 outputs a start preparation signal to the charging device 103. The sequence thereafter is as described above in "(2-1) Start of charging", and therefore description thereof will be omitted.

[0034] 4. Flowchart The processing of the control unit of each device will be described. (1)Charging device The process of control unit 133 of charging device 103 will be described with reference to FIG. When the program starts and a start preparation signal is input from the OCPP server 106 ("Yes" in the figure), the control unit 133 checks the connection of the vehicle 1 with the "connector ID" included in the start preparation signal, and outputs a response signal indicating the confirmation to the OCPP server 106 (S102). There are two types of response signals here: a normal signal indicating that the connection of the vehicle 1 to be charged has been confirmed, and an error signal indicating that the connection has not been confirmed. Thereafter, if a charging start signal is input from the OCPP server 106 within a specified time ("Yes" in S103), charging to the vehicle 1 with the "connector ID" included in the start preparation signal is turned on, and a response signal indicating that charging has started (normal charging start signal) is output to the OCPP server 106 (S104). In step S103, if the charging start signal is not input within a predetermined time, the process proceeds to step S105 ("No" in S103). If, in step S101, a start preparation signal has not been input ("No"), the process proceeds to step S105.

[0035] In step S105, when a completion preparation signal is input from OCPP server 106 ("Yes" in the figure), the connection of vehicle 1 with the "connector ID" included in the completion preparation signal is confirmed, and a response signal indicating the confirmation is output to OCPP server 106 (S106). Thereafter, if a charging completion signal is input from the OCPP server 106 within a specified time ("Yes" in S107), charging to the vehicle 1 with the "connector ID" included in the completion preparation signal is turned off, a response signal indicating that charging is complete (charging normal completion signal) is output to the OCPP server 106 (S108), and the process returns to step S101. In step S107, if a response signal (charge normal completion signal) is not input within a predetermined time, the process returns to step S101 ("No" in S107). If the completion preparation signal has not been input in step S105 ("No"), the process returns to step S101.

[0036] (2) OCPP Server In the OCPP server 106, the control unit 161 executes a program, and the OCPP application performs various processes. The following will be described with reference to the flowcharts in Figs. 15 to 17. When the OCPP application is started (start of FIG. 15), it is determined whether a charging start instruction has been received from the AP server 108 (S120). If a charging start instruction has been received ("Yes"), the "connector ID" of the charging target is acquired (S121), charging start processing is performed (S121), and the process proceeds to step S123. Here, the charge start instruction includes a "connector ID" of the charging target, and the connector ID is acquired from the charge start instruction. Note that the charge start process in step S122 will be described later. In step S120, if a charging start instruction has not been received ("No"), the process proceeds to step S123.

[0037] In step S123, it is determined whether a charging completion instruction has been received from the AP server . If a charge completion instruction has been received ("Yes"), the "connector ID" that is the target of charge completion is acquired (S124), and a charge completion process (S125) is performed, and then the process proceeds to step S126. Here, the charge completion instruction includes a "connector ID" of the charging completion target, and the connector ID is acquired from the charge completion instruction. Note that the charge completion process in step S125 will be described later. In step S123, if a charging completion instruction has not been received ("No"), the process proceeds to step S126.

[0038] In step S126, the charging status is acquired within a predetermined time ("Yes"). If the acquired "charging state" is "waiting" ("Yes" in S127), the number of vehicles to be charged is acquired from the acquired charging status (S128), and it is determined whether the waiting vehicles 1 can be charged (S129). Whether charging is possible is determined by whether the number of vehicles to be charged is less than the maximum number of vehicles that can be charged. In step S129, if charging is possible ("Yes"), the "connector ID" of the connector to be charged is obtained, charging start processing is performed, and the process proceeds to step S120 (S130, S131). The “connector ID” to be charged is the “connector ID” that is “on standby” and is registered in the status table T12 of the database 107 and that is “on standby” for the longest waiting time (registered in the record located at the top of the status table T12). On the other hand, if the charging state is not "standby" in step S127 ("No"), and if charging is not possible in step S128 ("No"), the process proceeds to step S120.

[0039] (2-1) Charging start process (S122) 16, the charging start process S122 outputs a start preparation signal to the charging device 103 (S1221). The start preparation signal includes a "connector ID" of the charging target, and the charging device 103 outputs a response signal indicating that the connection state of the "connector ID" has been confirmed (step S102 in FIG. 14). In the OCPP server 106, a response signal is input in step S1222 ("Yes"), and if the response signal is a normal signal ("Normal" in S1223), a start registration is requested from the database 107 in the status table T12 (S1224), and if a start registration response is received from the database 107 indicating that the start registration has been completed ("Yes" in S1225), the process proceeds to step S1226. In step S1226, a charging start signal is output to charging device 103. In response to this, charging device 103 starts charging, and when a response signal (charging normal start signal) indicating that charging has started normally is input from charging device 103 ("Yes" in S1227), a charging start response indicating that charging has started normally is transmitted to AP server 108, and the process proceeds to step S123 in FIG. In step S1223, if the input signal is an error signal ("Error"), an error indicating that the vehicle 1 and the connector 131 are not electrically connected is transmitted to the AP server 108 (S1229), and the process proceeds to step S123 in FIG.

[0040] (2-2) Charging completion process As shown in Fig. 17, the charging completion process S125 outputs a completion preparation signal to the charging device 103 (S1251). The completion preparation signal includes the "connector ID" of the charging target, and the charging device 103 outputs a response signal indicating that the connection state of the "connector ID" has been confirmed (step S106 in Fig. 14). There are two types of response signals: a normal signal indicating that the connection has been confirmed, and an error signal indicating that the connection has not been confirmed. In the OCPP server 106, a response signal is input in step S1252 ("Yes"), and if the response signal is a normal signal ("Normal" in S1253), a completion update is requested to the database 107 for the status table T12 (S1254), and if a completion update response is received from the database 107 indicating that the completion update has been completed ("Yes" in S1255), the process proceeds to step S1256. In step S1256, a charging completion signal is output to charging device 103. In response to this, charging device 103 completes charging, and when a response signal (charging normal completion signal) indicating that charging has been completed normally is input from charging device 103 ("Yes" in S1257), a charging completion response indicating that charging has been completed normally is transmitted to AP server 108, and the process proceeds to step S126 in FIG. In step S1253, if the input signal is an error signal ("Error"), an error indicating that the vehicle 1 and the connector are not electrically connected is transmitted to the AP server 108 (S1259), and the process proceeds to step S126 in FIG.

[0041] (2-3) Charging start process (S131) The charging start process in step S131 is a process for starting charging for a waiting vehicle 1. The charging start process in step S122 is a process for starting charging for a vehicle 1 for which a new charging request has been made. For this reason, both processes perform similar processing, but are different in that step S122 makes a start registration request to the database 107 (see step S1224 in FIG. 16), whereas step S131 makes a start update request (see FIG. 13).

[0042] (3) Database The processing of the control unit 171 of the database 107 will be described with reference to FIG. (3-1) When the program starts and there is a request to create a power charging request from the AP server 108 ("Yes" in S140), the control unit 133 creates a new power charging request in the bottommost record of the power charging request table T11, sends a creation response (S141), and proceeds to step S142. The charging request creation request includes a “connector ID” for connecting to the vehicle 1 requesting charging, and the control unit 171 registers, for example, “20230401-07”, “1”, and “20230401:2300” in the “charging number”, “connector ID”, and “request date and time” fields (see FIG. 6A).

[0043] (3-2) In step S142, if there is a request to register or update the status ("Yes"), a registration / update response is made by registering the record at the bottom of the status table T12 or updating the contents (S143), and the process proceeds to step S144. (3-2-1) Registration Registration occurs when there is a new charge request. If charging is possible, the registration request is a start registration request (see Figure 10), and for example, as shown in the record at the bottom of Figure 6B, "20230401-7", "1", "charging", and "23:00" are registered in the "charging number", "connector ID", "charging status", and "start time". If charging is not possible, the registration request is a standby registration request (see Figure 11), and for example, as shown in the record at the bottom of Figure 8B, "20230401-8", "5", and "Waiting" are registered in the "Charging Number", "Connector ID", and "Charging Status". The registration / update request includes the “charging number”, “connector ID”, “charging state”, and “start time”. Note that the “time” may be stored as the time of the clock 175 of the database 107.

[0044] (3-2-2) Update The updates include updating the "charging status" from "standby" to "charging" and updating the "charging status" from "charging" to "charged." For example, when charging starts for the "charging number" "20230401-8" in FIG. 8B, "standby" in the status table T12 is updated to "charging", and the time when charging started is stored in "start time". In addition, when charging of the vehicle 1 that is being charged is completed, the status "charging" is updated to "charged."

[0045] (3-3) In step S144, if there is a request to update the charging request table T11 ("Yes"), the corresponding portion in the charging request table T11 is updated and an update response is made (S145), and the process proceeds to step S146. For example, a charging request update request is issued when a charging request that was in progress is completed, and includes at least one of the "charging number" and "connector ID." The control unit 171 updates the "charging result" from "Incomplete" in the record with the "charging number" of "20230401-5" in FIG. 8A to "Completed" as shown in FIG. 9A, and stores "20230402:0600" in the "charging completion date and time" as shown in the same figure.

[0046] (3-4) In step S146, if there is a request to delete a status ("Yes"), the record of the corresponding status or all statuses in the status table T12 is deleted, a deletion response is made (S147), and the process proceeds to step S148. For example, a status deletion request is made when a charging request that was in progress is completed, and includes at least one of the "charging number" and "connector ID." For example, the control unit 171 deletes the record with the "charging number" of "20230401-5" in Figure 8B, where the "charging status" is "charging," as in Figure 9B, with the "charging number" being "20230401-5." (3-5) In step S148, if there is a status acquisition request ("Yes"), the information of the record of the corresponding status in the status table T12 is acquired and transmitted to the request destination as an acquisition response (S149), and the process proceeds to step S140. For example, in response to a request to obtain a status, all "charging states" in the status table T12 are obtained and transmitted.

[0047] (4) AP server In the AP server 108, the control unit 181 executes a program, and the AP application performs various processes. The following will be described with reference to the flowcharts in Figures 19A and 19B. When the AP application is started (start of FIG. 19A) and a charging start operation is performed from the portable terminal 3 ("Yes" in step S170), a charging request including a "connector ID" corresponding to the ID of the portable terminal 3 is requested to the database 107 (S171). In response to this charge request, when a creation response is received from the database 107 indicating that the charge request has been created in the charge request table T11 ("Yes" in S172), a request is made to the database 107 to obtain a status. If there is a response to this request from the database 107 indicating that the "charging status" information from the status table T12 has been acquired ("Yes" in S174), then in step S175, the number of vehicles currently being charged is calculated from the acquired charging status, and it is determined whether charging is possible in response to a new charging request.

[0048] The determination of whether charging is possible is made by comparing the number of devices being charged with the maximum number of devices that can be charged, and for example, when the number of devices being "charged" is two as in Fig. 4B, it is determined that charging is possible since this is less than the maximum number (three). On the other hand, when the number of devices being "charged" is three as in Fig. 6B, it is determined that charging is not possible since this is greater than the maximum number (three). If it is determined in step S175 that charging is possible ("Yes"), the OCPP server 106 is instructed to start charging (S176), and if there is a charging start response from the OCPP server 106 indicating that charging has started normally ("Yes" in S177), a charging start report is sent to the portable terminal 3 (S178), and the process proceeds to step S183. Also, if there is an "error" response in step S177 ("No"), an error report is sent to the portable terminal 3 (S179), and the process proceeds to step S183. If it is determined in step S175 that charging is not possible (No), charging is not started and a request is made to database 107 to register that charging is in a standby state (S180). If a response to the standby registration is received (Yes in S181), a charging standby report is sent to portable terminal 3 (S182), and the process proceeds to step S183.

[0049] In step S183, as shown in FIG. 19B, a request is made to the database 107 to acquire the "start time" from the status table T12. When an acquisition response is received from the database 107 in response to this acquisition request indicating that the "start time" information in the status table T12 has been acquired ("Yes" in S184), it is determined whether or not charging has been completed in response to the charging request during charging (step S185). Completion of charging is determined based on the time elapsed from the start time, and for example, if the "start time" of the "charging number" "20230401-5" in Fig. 8B is "22:00" and the time of determination is "6:00", charging is determined to be complete because the charging time (e.g., 8 hours) has elapsed. On the other hand, the "start time" of the "charging number" "20230401-6" in Fig. 8B is "22:30", and charging is determined to be incomplete because the charging time (e.g., 8 hours) has not elapsed. In addition, if multiple start times are obtained, it may be determined whether charging is completed for all of them, or the "start time" in the top row of the status table T12 may be obtained and the completion of charging may be determined for the charge in that top row. If it is determined in step S185 that charging is complete ("Yes"), the OCPP server 106 is instructed to complete charging (S186), and if a charging completion response indicating that charging was successfully completed is received from the OCPP server 106 ("Yes" in S187), a charging completion report is sent to the portable terminal 3 (S188). Next, since charging is completed, a request is made to the database 107 to update the charging request table T11 (S189), and if a response to the update is received ("Yes" in S190), a request is made to delete the corresponding record in the charging request table T11 (S191), and if a response to the deletion is received ("Yes" in S192), the process proceeds to step S170.

[0050] <First embodiment A> The charging control device 105 of the first embodiment includes an OCPP server 106, a database 107, and an AP server 108, but for example, the OCPP server 106 may have the same functions as the AP server 108. In this case, the charging control device 105A includes an OCPP server 106A and a database 107A, and will be described below as a first embodiment A.

[0051] 1.Charging control device The charging control device 105A includes an OCPP server 106A that is capable of communicating with the charging device 103 and the portable terminal 3 and functions as a server that controls the charging device 103 in accordance with a charging request from a user (portable terminal 3), and a database (hereinafter referred to as "DB" in the drawings) 107A that stores charging request data (charging request history) of the vehicle 1 being charged by the charging device 103 and charging status data indicating the charging status. The OCPP server 106A has the functions of the AP server 108 in the first embodiment, and the database 107A is the same as in the first embodiment, but requests for registration and the like are input only from the OCPP server 106A. As shown in FIG. 20, the OCPP server 106A includes at least a control unit 161A, a communication unit 162A, a storage unit 163A, and a clock 164A. The control unit 161A is basically the same as in the first embodiment, but the contents of the programs it executes are different, and the processing as an OCPP application is different. The communication unit 162A communicates with the database 107A, and also communicates with the portable terminal 3 using, for example, data communication using a network (for example, the Internet) using a telephone line or an optical line, Bluetooth (registered trademark) communication, Wi-Fi (registered trademark) communication, etc. Note that the communication unit 162A communicates with the charging device 103 using OCPP. The storage unit 163A is basically the same as that in the first embodiment, but the contents of the programs it stores (that is, the programs executed by the control unit 161A) are different. The clock 164A measures the date and time when a charging request is made, the time when charging is started, and the time when charging is completed. These measured dates and times are stored in the database 107A. The clock 164A has a calendar function and measures the date and time.

[0052] 21 to 24, the OCPP server 106A includes a charging request receiving unit that receives a charging request from the portable terminal 3, a charging feasibility determination unit that determines whether the vehicle 1 that has requested charging is capable of being charged, a charging start signal output unit that outputs a charging start signal (which may include a start preparation signal) for causing the charging device 103 to start charging when it is determined that charging is possible, and a normal charging start signal output unit that receives a normal charging start signal (including a response signal if the start preparation signal is included) from the charging device 103. a signal input unit, a charging start report transmitting unit that transmits a charging start report to the portable terminal 3 when a charging normal start signal is input from the charging device 103, a charging standby report transmitting unit that transmits a charging standby report to the portable terminal 3 when it is determined that charging is not possible, a charging request creation request output unit that outputs a charging request creation request to the database 107A, a charging request creation response input unit that inputs a response to the charging request creation request from the database 107A, a status acquisition request output unit that outputs a status acquisition request to the database 107A, and a status acquisition request output unit that outputs a status acquisition request to the database 107A. a start registration request output unit that outputs a start registration request for the status to database 107A; a start registration response input unit that receives the response to the start registration request from database 107A; a standby registration request output unit that outputs a standby registration request for the status to database 107A when it is determined that charging is not possible; a standby registration response input unit that receives the response to the standby registration request from database 107A; a charging completion determination unit that determines whether charging of vehicle 1 being charged is completed; and a charging completion determination unit that notifies charging device 103 of charging completion when it is determined that charging is completed. a normal charging completion signal input unit to which a normal charging completion signal (including a response signal when the completion preparation signal is included) is input from charging device 103; a charging completion report transmission unit to transmit a charging completion report to portable terminal 3 when the normal charging completion signal is input from charging device 103; a start time acquisition request output unit to output a start time acquisition request to database 107A to acquire a start time; and a start time acquisition response input unit to which a response to the start time acquisition request is input from database 107A.a completion update request output unit that outputs a completion update request to the database 107A, a completion update response input unit that inputs a response to the completion update request from the database 107A, a charging request update request output unit that outputs a charging request update request to the database 107A, a charging request update response input unit that inputs the response to the charging request update request from the database 107A, a status deletion request output unit that outputs a status deletion request, a deletion response input unit that inputs the response to the deletion request from the database 107A, a charging possibility determination unit that determines whether charging is possible for a waiting charging request, and a charging The charging device 103 includes a charging start signal output unit that outputs a charging start signal (which may include a start preparation signal) for causing the charging device 103 to start charging when it is determined that charging is possible, a normal charging start signal input unit that receives a normal charging start signal (including a response signal when the start preparation signal is included) from the charging device 103, a charging completion report transmitting unit that transmits a charging completion report to the portable terminal 3 when the normal charging start signal is received from the charging device 103, a start update request output unit that outputs a status start update request to the database 107A, and a start update response input unit that receives a response to the start update request from the database 107A.

[0053] 2. Sequence (1) Charging request 21, when the OCPP server 106A receives a charge request from the portable terminal 3, it requests the database 107A to create a new charge request for the charge request. In response to this request, the database 107A creates a new request in the charge request table T11 and sends a creation response to the OCPP server 106A. The OCPP server 106A requests the database 107A to obtain the status, and obtains the status.

[0054] (2) Start charging The OCPP server 106A judges whether charging is possible for the new request based on the status acquired from the database 107A. The judgment method is the same as that in the first embodiment, and is performed by comparing the current number of charging devices with the maximum number of devices that can be connected. FIG. 21 shows a case where charging is possible, and will be described with reference to FIG. If it is determined that charging is possible, the OCPP server 106A outputs a start preparation signal to the charging device 103, and when a response signal is input from the charging device 103, it requests the database 107A to register the start of charging, and when a start registration response indicating registration is received, it transmits a charging start signal to the charging device 103, and when a charging start response signal (normal charging start signal) is input from the charging device 103, it reports the start of charging to the portable terminal 3. FIG. 22 shows a case where charging is not possible, and will be described with reference to FIG. If it is determined that charging is not possible, the OCPP server 106A requests the database 107A to register the charging standby state. When a registration response indicating that the registration has been completed is input from the database 107A, the OCPP server 106A reports the charging standby state to the portable terminal 3.

[0055] (3) Charging completed The OCPP server 106A determines whether charging is complete based on the elapsed time from the start of charging, as in the first embodiment. 23, the OCPP server 106A requests database 107A to acquire a start time, and when it determines that charging is complete from the acquired start time, it outputs a completion preparation signal to charging device 103, and when a response signal is input from database 107, it requests database 107A to update the completion of charging. When the OCPP server 106A receives a response of the completion update from database 107A, it outputs a charging completion signal to charging device 103, and when a response signal indicating that charging is completed (charging normal completion signal) is input from charging device 103, it reports the completion of charging to the portable terminal 3. Furthermore, when the OCPP server 106A receives a response from the charging device 103 that charging is complete, it requests the database 107A to update the charging request in the charging request table T11, and also requests the database 107A to delete the record in the status table T12 indicating that charging has been completed.

[0056] (4) Starting charging during standby The OCPP server 106A judges whether charging is possible in response to a waiting charging request, as in the first embodiment, based on the number of "charging" units in the status table T12. As shown in FIG. 24, the OCPP server 106 requests the database 107 to acquire a status, and judges whether charging is possible or not based on an acquisition response from the database 107A. In FIG. 24, when it is determined that charging is possible, the OCPP server 106A outputs a start preparation signal to the charging device 103, and when a response signal is input from the charging device 103, it requests a start update from the database 107A, and when a start update response indicating that the update has been received is received, it transmits a charging start signal to the charging device 103, and when a charging start response signal (normal charging start signal) is input from the charging device 103, it reports the start of charging to the portable terminal 3.

[0057] <First embodiment B> As shown in FIG. 3, the charging control device 105 of the first embodiment has an OCPP server 106, a database 107, and an AP server 108, and the charging control device 105A of the first embodiment A has an OCPP server 106A and a database 107A, as shown in FIG. 20. However, the charging control device 105B may be configured by a single computer such as a personal computer or a workstation, and will be described below as a first embodiment B. As shown in FIG. 25, the charge control device 105B of the first embodiment B includes at least a control unit 151B, a communication unit 152B, a storage unit 153B, and a clock 154B. The memory unit 153B corresponds to the databases 107, 107A in the first embodiment and first embodiment A, and stores a charging request table T11 and a status table T12, as well as various data such as the program executed by the control unit 151B, the maximum number of devices that can be charged, and the time until charging is completed. The control unit 151B is configured to execute, for example, a program stored in the storage unit 153B to run, for example, an application similar to the application of the OCPP server 106A of the first embodiment A. The control unit 151B performs creation, registration, update, etc. of a new request in the charging request table T11 stored in the storage unit 153B, and registration, update, deletion, etc. in the status table T12. The communication unit 152B is capable of communicating with the mobile terminal 3, and is configured to be capable of communicating with the charging device 103 by OCPP. When the charging control device 105B is installed in a management room of an apartment building, the communication may be possible using a local network such as a LAN.

[0058] <First embodiment C> 1. Overall structure In the charging system 101 of the first embodiment, the chargeability of the vehicle 1 requested to be charged is determined by comparing the number of vehicles being charged with the maximum number of vehicles. In other words, the chargeability is determined based on whether the number of vehicles being charged plus the number of newly requested vehicles 1 that would be charged is less than the maximum number. In the charging system of the first embodiment C, the charging power of vehicle 1 is registered, and assuming that the vehicle 1 requested to be charged is charged with the current charging power usage, if the charging power usage is less than the maximum power usage, the vehicle 1 requested to be charged is charged, and if the charging power usage is equal to or greater than the maximum power usage, the charging of the vehicle 1 requested to be charged is put on hold. Hereinafter, the first embodiment C will be described, focusing on the differences from the first embodiment.

[0059] 2.Each part (1) Database The status table T12C of the first embodiment C has a new item of "power usage" as shown in FIG. 26A. In the "power usage" field, for example, "20" or "15" is stored. "20" is 20 kW, and the maximum power usage here is 60 kW. Furthermore, database 107C (not shown) stores customer information table T13C having items of "customer ID," "connector ID," and "charging power" as shown in FIG. 26B. For example, a customer ID of "AAA" is charged with a charging power of "20 (kW)" using connector 131 having a connector ID of "1." In the first embodiment C, the charging start instruction includes the "connector ID" and "power usage," and charging device 103C (not shown) that receives the charging start signal is configured to charge with the "power usage" included in the charging start signal. When communicating with the user's mobile terminal 3 and registering the same, the AP server 108C accepts customer information from the user via the mobile terminal 3 and registers the customer information in a customer information table T13C of the database 107C.

[0060] (2) AP server In AP server 108C, similarly to the first embodiment, control unit 181C executes a program, and AP applications perform various processes, but steps S173 to S175 in FIG. 19A are different. When the user operates to start charging, the AP server 108C creates a new charging request in the database 107C (S170 to S172 in FIG. 19A), and, as shown in FIG. 27, requests and obtains from the database 107C the status (for example, the "power usage" of vehicle 1 (charging number) currently being charged) and the "power usage" of the "customer ID" for which the new charging request has been made (S173C, 174C). In step S175C of FIG. 27, the AP server 108C adds up the acquired "power usage" of all vehicles 1 (charging numbers) and the "power usage" of the new charging request to calculate the power usage of all vehicles 1 when charging, including the vehicle 1 of the new charging request, and if the calculated power usage is less than the maximum power usage, it determines that charging is possible ("Yes"), and if it is equal to or greater than the maximum power usage, it determines that charging is not possible ("No"). If it is determined that charging is possible, the process proceeds to step S176 in Fig. 19A, and if it is determined that charging is not possible, the process proceeds to step S180 in Fig. 19A. Note that the processes thereafter are the same as those in the first embodiment, and therefore description thereof will be omitted.

[0061] (3)OCPP Server In the OCPP server 106C, as in the first embodiment, the control unit 161C executes a program, and the OCPP application performs various processes, but steps S126 to S128 in FIG. 15 are different. The OCPP server 106C starts the OCPP application and completes the process up to step S125 (S120 to S125). The OCPP server 106C acquires the charging status in step S126C of Fig. 28. The charging status includes the "power usage" of all vehicles 1 (charging numbers) that are charging and the "power usage" of the waiting vehicle 1 (charging number) that has been waiting for the longest time. In S127C, the obtained "power usage" of all vehicles 1 (charging numbers) and the "power usage" of the vehicle 1 (charging number) with the longest standby time are added together to calculate the power usage of all vehicles 1 when charging the waiting vehicle 1 (charging number).If the calculated power usage is less than the maximum power usage, it is determined that charging is possible ("Yes" in S128C), and if it is equal to or greater than the maximum power usage, it is determined that charging is not possible ("No" in S128C). If it is determined that charging is possible, the process proceeds to step S129 in Fig. 15, and if it is determined that charging is not possible, the process proceeds to step S120 in Fig. 15. Note that the processes thereafter are the same as those in the first embodiment, and therefore description thereof will be omitted.

[0062] In the first embodiment C, the charging device 103C can be controlled so as not to be overloaded. Moreover, since the OCPP server 106C can instruct the charging device 103C on the power usage during charging, it can also handle differences in charging power caused by differences in the capacity of the battery of the vehicle 1, etc.

[0063] <First Modification> Although the charging system, charging device, and charging control device of the first embodiment (including A to C) have been described, they are not limited to the first embodiment, and may be, for example, a first modified example as follows. Also, the first embodiment and the first modified example, or the configurations in the first modified example may be combined. Furthermore, examples that are not described in the first embodiment or first modified example, and design changes that do not deviate from the gist of the invention are also included in the invention related to the first embodiment.

[0064] 1. Check if the vehicle is properly connected If the vehicle 1 to be charged is not connected normally, the charging control device 105 transmits an error to the mobile terminal 3 as in step S1229 in FIG. 16 or step S1259 in FIG. The charging device 103 checks whether it is electrically connected to the vehicle 1 with the "connector ID" included in the start preparation signal or the completion preparation signal, and outputs a "normal signal" if it is connected, and outputs an "error" signal if it is not connected. However, the determination may be made in the following manner. The connection determination means is realized by software, as in step S1223 in FIG. 16 and step S1253 in FIG. (1) Connection check 1 In the above method, the determination as to whether the vehicle 1 to be charged is normally connected (normal connection determination means) is performed on the side of the charging device 103. However, the normal connection determination may be performed on the side of the OCPP server 106 or the AP server 108. The charging device 103 outputs only the connection result regarding the presence or absence of electrical connection of the vehicle 1 (connector 131) to be charged or of all vehicles 1 to the OCPP server 106 and / or AP server 108, and the OCPP server 106 or AP server 108 can determine whether the connection is normal based on whether the "connector ID" of the vehicle that is the subject of the charging request is included in the connection result from the charging device 103.

[0065] (2) Connection check 2 When a start preparation signal or a completion preparation signal is input ("Yes" in step S101 in FIG. 14), the charging apparatus 103 checks the connection of the "connector ID" included in the signal. However, when the OCPP server 106 or AP server 108 determines whether a connection is normal, the start preparation signal or the completion preparation signal does not need to include a "connector ID." When a start preparation signal or a completion preparation signal is input, the charging device 103 checks the electrical connections of all connectors 131 and outputs the connection results to the OCPP server 106 or the AP server 108. If the "connector ID" for which a new charging request has been made is included among the connected connectors in the connection result from the charging device 103, the OCPP server 106 or the AP server 108 determines that the connection is "normal," and if it is not included in the connection result, determines that an "error" has occurred. In this case, the normal connection determination for the vehicle 1 is performed on the OCPP server 106 or AP server 108 side. In addition, taking into consideration the amount of communication, it is preferable that the connection determination be performed by the charging device 103 or the OCPP server 106.

[0066] 2. Charging possible determination As shown in FIG. 15, the OCPP 106 acquires the charging status and the number of units to be charged, and then determines whether charging is possible (steps S126 to S128). As shown in FIG. 19A, the AP server 108 acquires the charging status and the number of units to be charged, and then determines whether charging is possible (steps S173 to S175). The charging status here refers to all "charging states" stored in the status table T12. The chargeability determination means is realized by software, such as steps S126 to S128 in Fig. 15 and steps S173 to 175 in Fig. 19A. However, the charging status may be acquired as long as the number of charging units can be ultimately obtained, and may be, for example, all "charging numbers" whose charging status is "charging", or the number of units whose charging information is "charging". Furthermore, if the power usage being used for charging can be acquired in the charging device 103 and the power usage when charging one vehicle 1 is determined in advance, the charging status may be the current total power usage. In this case, the OCPP server 106 or the AP server 108 can make a determination by comparing the difference between the current power usage and the maximum power usage acquired from the charging device 103 with the power usage that can be used to charge one vehicle 1. In addition, the AP server 108 and / or the OCPP server 106 may be provided with a counter that adds "1" each time a charging start response or a normal charging start signal is input and subtracts "1" each time a charging completion response or a normal charging completion signal is input, and obtains the current number of units being charged from the number on the counter.

[0067] 3.Charging completion determination The charging completion determination is performed by determining whether charging is complete or not based on the elapsed time from the acquired start time as shown in Fig. 19B. Note that the charging completion determination means is realized by software as in steps S183 to S185. However, if the vehicle 1 is equipped with an ECU (Electronic Control Unit) 11 capable of communicating with the charging device 103 or the charging control device 105, the OCPP server 106D (or the AP server 108) may acquire a detection result (e.g., voltage) from the ECU 11 as shown in Fig. 29, and may determine the completion of charging by comparing the acquired detection result with a voltage at which charging is deemed to be completed (hereinafter, referred to as "charging completion voltage") As described above, when the OCPP server 106D makes the determination, the AP server 108 in the first embodiment does not need to acquire the start time from the database 107 or transmit a charging completion instruction to the OCPP server 106 (see Fig. 12). In addition, the detection result of the ECU 11 may be acquired by the charging device 103, and the detection result acquired by the charging device 103 may be output to the OCPP server 106 or the AP server 108, and the OCPP server 106 or the AP server 108 may make a decision. 30, the charging device 103E may acquire the detection result of the ECU 11 and determine the completion of charging by comparing the acquired detection result with the charging completion voltage, in which case the charging device 103E may itself perform the charging completion determination and transmit a charging normal completion signal to the OCPP server 106E. In this case, there is no need to exchange a stop transaction signal as shown in FIG. 12 or FIG. 23. In addition, if the charging device 103 is equipped with a voltage detection unit that detects the charging voltage, the completion of charging may be determined by the voltage detected by the charging device 103, or the completion of charging may be determined by outputting the voltage from the charging device 103 to the OCPP server 106 or AP server 108 and having the OCPP server 106 or AP server 108 make the determination. Although the charging completion judgment is made based on the charging time when the battery charging rate reaches 80% or more (fully charged state), for example, the charging of the first vehicle may be completed in a short time such as two hours, and the second vehicle 1 in a waiting state may be charged, and if the first vehicle 1 is not fully charged, it may be put in the lowest waiting state. This allows multiple vehicles to be charged equally.

[0068] 4.Other (1) Although transactions are used in transmitting and receiving signals between the OCPP server 106 and the charging device 103, they do not necessarily have to be used. Note that using transactions can prevent malfunctions. Examples of malfunctions include cases where a normal charging start signal is not output even though charging is in progress, or where charging is continued without a charging start report being sent to the mobile terminal. (2) The charging system includes a charging device and a charging control device. However, the charging device may be configured as a single unit that includes a charging section equivalent to the charging device and a charging control section equivalent to the charging control device. (3) Although OCPP is used for communication between the charging device 103 and the first server (OCPP server 106), other protocols may be used. (4) The AP server 108 accepts the charging request from the mobile terminal 3, but may accept the request in other ways. For example, the AP server 108 may accept the charging request from the charging device 103 or an external reader, using a card that stores identification information such as a vehicle ID. (5) An application compatible with the AP server 108 is installed on the mobile terminal, but it may also be possible to communicate with the AP (WEB-API) by using, for example, an application (front-end) running on a browser. (6) In the embodiment, the maximum power usage (maximum number of devices to be charged) is set in advance, but it may be possible for the user to set it.

[0069] <First Invention 1> The first embodiment (including A to C and modified examples) includes the following first invention 1. The first invention 1 is not limited to the first embodiment, first embodiments A to C, and first modified example, and includes examples not described in the first embodiment, first embodiments A to C, and first modified example, and design changes that do not deviate from the gist of the invention.

[0070] (1) Charging control device The first charge control device includes: In a charging control device that electrically charges each of a plurality of vehicles that can be electrically charged in an apartment complex and in which a maximum power usage for simultaneously charging the plurality of vehicles is set (or can be set), when a charging request is made from a vehicle exceeding the maximum number that can be simultaneously charged within the range of the maximum power usage, charging of the vehicles requested to be charged in excess of the maximum number is put into a standby state. This ensures that the maximum power usage is not exceeded and the charging equipment (distribution board) does not become overloaded.

[0071] The second charge control device includes: A charging control device controls charging of a vehicle connected to a charging device that electrically charges each of a plurality of vehicles that can be electrically charged in an apartment complex and in which a maximum power usage for simultaneously charging the plurality of vehicles is set (or can be set), the charging control device comprising: A charging request receiving means (corresponding to step S170, for example) for receiving a charging request for the vehicle; a first charge control means for controlling charging of the vehicle that has requested charging; A first vehicle number acquisition means (corresponding to, for example, steps S173 to S174) for acquiring the number of the vehicles being charged; Equipped with The first charging control means puts the vehicle that requested charging into a charging state in which it charges when the number of vehicles to be charged acquired by the first number acquisition means is less than the maximum number that can be charged within the maximum power usage range (e.g., "Yes" in step S175, corresponding to S176), and puts the vehicle that requested charging into a standby state when the acquired number of vehicles to be charged is equal to or greater than the maximum number (e.g., "No" in step S175, corresponding to S180). This ensures that the maximum power usage is not exceeded and the charging equipment (distribution board) does not become overloaded.

[0072] The third charge control device starts charging one of the vehicles in a standby state when charging of the one of the vehicles that has been charged in the first charge control device is completed. This allows vehicles to be charged while on standby without exceeding the maximum power usage.

[0073] The fourth charge control device is the second charge control device, A second vehicle number acquisition means for acquiring the number of vehicles being charged among the plurality of vehicles (e.g., corresponding to “Yes” in step S126, S127, and S128); a second charge control means for controlling charging of the vehicle in the standby state; Further equipped with When the number of vehicles to be charged acquired by the second vehicle number acquisition means is less than the maximum number, the second charging control means sets one of the vehicles in the standby state to a charging state in which it charges the vehicle (corresponding to "Yes" in steps S129, S130, and S131). This allows vehicles to be charged while on standby without exceeding the maximum power usage.

[0074] The fifth charging control device is the third charging control device, The one vehicle in the waiting state is the vehicle that has been waiting the longest. This allows the standby time to be shortened without exceeding the maximum power consumption.

[0075] The sixth charge control device is the fourth charge control device, The second charging control means starts charging the vehicle when the number of vehicles to be charged acquired by the second vehicle number acquisition means is less than the maximum number, the vehicle having the longest standby time. This allows the standby time to be shortened without exceeding the maximum power consumption.

[0076] The seventh charging control device is the second, fourth or sixth charging control device, The charging completion determination means (corresponding to step S185, for example) is provided for determining whether or not charging of the vehicle being charged has been completed. This makes it possible to determine when the vehicle being charged has completed charging.

[0077] The eighth charge control device is the second, fourth, sixth or seventh charge control device, A first server capable of communicating with the charging device; a second server capable of communicating with the first server and a mobile terminal of a user of the vehicle; Equipped with The first charging control means is executed by an application executed by the second server. This makes it possible to provide the first charge control means without making any major changes to the first server.

[0078] A ninth charging control device is the fourth or sixth charging control device, A first server capable of communicating with the charging device; a second server capable of communicating with the first server and a mobile terminal of a user of the vehicle; Equipped with The first charge control means and the second charge control means are executed by an application executed by the second server. This makes it possible to provide the first charge control means without making any major changes to the first server.

[0079] A tenth charging control device is the fourth or sixth charging control device, A first server capable of communicating with the charging device; a second server capable of communicating with the first server and a mobile terminal of a user of the vehicle; Equipped with the first charging control means is executed by an application executed by the second server, The second charging control means is executed by an application executed by the first server. This makes it possible to reduce the amount of communication between the first server and the second server.

[0080] An eleventh charging control device is the seventh charging control device, A first server capable of communicating with the charging device; a second server capable of communicating with the first server and a mobile terminal of a user of the vehicle; Equipped with The charging completion determination means is executed by an application executed by the first server or the second server.

[0081] (2) Charging system The first charging system is a charging system that electrically charges a plurality of vehicles that can be electrically charged in an apartment building, A charging device including a plurality of connectors connectable to each of the plurality of vehicles; a charge control device that controls charging of the vehicle by the charging device; Equipped with The charging device is set to a maximum power usage for simultaneously charging the plurality of vehicles, The charge control device is any one of the first to eleventh charge control devices. The maximum power consumption may be set as a fixed value that cannot be changed, or may be set as a variable value that can be changed.

[0082] (3) Charging control method The first charge control method is A charging control method for controlling charging of a vehicle connected to a charging device that electrically charges each of a plurality of vehicles that can be electrically charged in an apartment building, the charging device having a maximum power usage for simultaneously charging the plurality of vehicles set or capable of being set, comprising: When the number of vehicles making charging requests exceeds the maximum number that can be charged simultaneously within the range of the maximum power usage, charging of the vehicles for which charging is requested in excess of the maximum number is put into a standby state.

[0083] <First Invention 2> In the first embodiment (including A to C, etc.), the following first invention 2 exists. The first invention 2 is not limited to the first embodiment, first embodiments A to C, and first modified example, and includes examples not described in the first embodiment, first embodiments A to C, and first modified example, and design changes that do not deviate from the gist of the invention.

[0084] (1) Charging control device The first charge control device includes: In a charging control device that electrically charges each of a plurality of vehicles that can be electrically charged in an apartment complex and in which a maximum power usage for simultaneously charging the plurality of vehicles is set (or can be set), when a charging request is made from a new vehicle, charging of the vehicle that has been requested to be charged is put into standby mode if the power usage assumed to be used to charge the vehicle is equal to or greater than the maximum power usage. This ensures that the maximum power usage is not exceeded and the charging equipment (distribution board) does not become overloaded.

[0085] The second charge control device includes: A charging control device controls charging of a vehicle connected to a charging device that electrically charges each of a plurality of vehicles that can be electrically charged in an apartment complex and in which a maximum power usage for simultaneously charging the plurality of vehicles is set (or can be set), the charging control device comprising: A charging request receiving means (corresponding to step S170, for example) for receiving a charging request for the vehicle; a first charge control means for controlling charging of the vehicle that has requested charging; a first power usage acquisition (calculation) means (corresponding to, for example, steps S173C to S175C) for acquiring (calculating) a total power usage of the vehicle being charged and the vehicle that has requested charging; Equipped with The first charging control means puts the vehicle that has requested charging into a charging state in which it charges when the total power usage acquired by the first power usage acquisition (calculation) means is less than the maximum power usage (e.g., "Yes" in step S175C, corresponding to S176), and puts the vehicle that has requested charging into a standby state when the acquired total power usage is equal to or greater than the maximum power usage (e.g., "No" in step S175C, corresponding to S180). This ensures that the maximum power usage is not exceeded and the charging equipment (distribution board) does not become overloaded.

[0086] The third charge control device starts charging one of the vehicles in a standby state when charging of the one of the vehicles that has been charged in the first charge control device is completed. This allows vehicles to be charged while on standby without exceeding the maximum power usage.

[0087] The fourth charge control device is the second charge control device, A second power usage acquisition (calculation) means (corresponding to, for example, steps S126C and S127C) for acquiring (calculating) a total power usage of a vehicle being charged and one of the vehicles being in standby among the plurality of vehicles; a second charge control means for controlling charging of the vehicle in the standby state; Further equipped with When the total power usage acquired (calculated) by the second power usage acquisition (calculation) means is less than the maximum power usage, the second charging control means puts one of the vehicles in the standby state into a charging state in which it charges the vehicle (corresponding to "Yes" in step S128C, S129, and S122). This allows vehicles to be charged while on standby without exceeding the maximum power usage.

[0088] The fifth charging control device is the third charging control device, The one vehicle in the waiting state is the vehicle that has been waiting the longest. This allows the standby time to be shortened without exceeding the maximum power consumption.

[0089] The sixth charge control device is the fourth charge control device, The one vehicle in the waiting state is the vehicle that has been waiting the longest. This allows the standby time to be shortened without exceeding the maximum power consumption.

[0090] The seventh charging control device is the second, fourth or sixth charging control device, The charging completion determination means (corresponding to step S185, for example) is provided for determining whether or not charging of the vehicle being charged has been completed. This makes it possible to determine when the vehicle being charged has completed charging.

[0091] The eighth charge control device is the second, fourth, sixth or seventh charge control device, A first server capable of communicating with the charging device; a second server capable of communicating with the first server and a mobile terminal of a user of the vehicle; Equipped with The first charging control means is executed by an application executed by the second server. This makes it possible to provide the first charge control means without making any major changes to the first server.

[0092] A ninth charging control device is the fourth or sixth charging control device, A first server capable of communicating with the charging device; a second server capable of communicating with the first server and a mobile terminal of a user of the vehicle; Equipped with The first charge control means and the second charge control means are executed by an application executed by the second server. This makes it possible to provide the first charge control means without making any major changes to the first server.

[0093] A tenth charging control device is the fourth or sixth charging control device, A first server capable of communicating with the charging device; a second server capable of communicating with the first server and a mobile terminal of a user of the vehicle; Equipped with the first charging control means is executed by an application executed by the second server, The second charging control means is executed by an application executed by the first server. This makes it possible to reduce the amount of communication between the first server and the second server.

[0094] An eleventh charging control device is the seventh charging control device, A first server capable of communicating with the charging device; a second server capable of communicating with the first server and a mobile terminal of a user of the vehicle; Equipped with The charging completion determination means is executed by an application executed by the first server or the second server.

[0095] (2) Charging system The first charging system is a charging system that electrically charges a plurality of vehicles that can be electrically charged in an apartment building, A charging device including a plurality of connectors connectable to each of the plurality of vehicles; a charge control device that controls charging of the vehicle by the charging device; Equipped with The charging device has a maximum power usage for simultaneously charging the plurality of vehicles set or is capable of setting the maximum power usage, The charge control device is any one of the first to eleventh charge control devices.

[0096] (3) Charging control method The first charge control method is A charging control method for controlling charging of a vehicle connected to a charging device that electrically charges each of a plurality of vehicles that can be electrically charged in an apartment building, the charging device having a maximum power usage for simultaneously charging the plurality of vehicles set or capable of being set, comprising: When the total power usage of the vehicle requested for new charging and all the vehicles currently being charged is equal to or greater than the maximum power usage, charging of the vehicle requested for new charging is put into a standby state.

[0097] <First Invention 3> In the first embodiment (including A to C, etc.), the following first invention 3 exists. The first invention is not limited to the first embodiment, first embodiments A to C, and first modified example, and the first invention 3 includes examples not described in the first embodiment, first embodiments A to C, and first modified example, and design changes that do not deviate from the gist of the invention.

[0098] (1) Charging control device The charging control device is A charging control device controls charging of a vehicle connected to a charging device that electrically charges each of a plurality of vehicles that can be electrically charged in an apartment complex and in which a maximum power usage for simultaneously charging the plurality of vehicles is set (or can be set), the charging control device comprising: When the charging time of at least one first vehicle among the vehicles reaches a first hour, if there is another second vehicle waiting to be charged, charging of the first vehicle is stopped, and if charging of the first vehicle is incomplete, the charging state of the first vehicle is put into a waiting state, and charging is performed for the second vehicle. This allows multiple vehicles to be charged equally.

[0099] <Other> Each of the first inventions 1 to 3 may have the configuration of another invention. [Explanation of symbols]

[0100] 1 vehicle 3. Mobile devices 101 Charging System 103 Charging device 105 Charging control device 106 OCPP Server 107 Database 108 AP Server

Claims

1. A charging control device controls charging of a vehicle connected to a charging device that electrically charges each of a plurality of vehicles that can be electrically charged in an apartment complex and has a maximum power usage setting for simultaneously charging the plurality of vehicles, the charging control device comprising: when a charging request is made and charging the vehicle for which charging has been requested would result in exceeding the maximum power usage, charging the vehicle for which charging has been requested is put into a standby state; Charging control device.

2. when charging of one of the vehicles that has been charged within the range of the maximum power usage is completed, charging of one of the vehicles that is in a standby state is started. The charge control device according to claim 1 .

3. The one vehicle in the waiting state is a vehicle that has been waiting for the longest time. The charge control device according to claim 2 .

4. A charging system for electrically charging a plurality of vehicles capable of being electrically charged in an apartment complex, A charging device including a plurality of connectors connectable to each of the plurality of vehicles; a charging control device that controls charging of the vehicle by the charging device; Equipped with The charging device is set to a maximum power usage for simultaneously charging the plurality of vehicles, The charging control device is a charging control device according to any one of claims 1 to 3. Charging system.

5. A charging control method for a charging device that electrically charges each of a plurality of vehicles that can be electrically charged in an apartment complex, the charging device having a maximum power usage setting for simultaneously charging the plurality of vehicles, the charging control method comprising: when a charging request is made and charging the vehicle for which charging has been requested would result in exceeding the maximum power usage, charging the vehicle for which charging has been requested is put into a standby state; Charging control method.

Images