Charging control device

Abstract

To provide a charging control device, a charging system and a method that are capable of controlling so that a charging apparatus does not become overloaded, and capable of performing charging in response to an early charging request.SOLUTION: In relation to a charging apparatus that electrically charges each of multiple vehicles capable of electrical charging in a parking lot and has a maximum usable power set for simultaneously charging the multiple vehicles, a charging control device controls charging to vehicles connected to the charging apparatus. When a charging time of a vehicle under charging becomes a first time which is shorter than a charging time required to reach full charge, the charging is temporarily terminated.SELECTED DRAWING: Figure 15

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, a charging control unit 3 that controls the charging current of the chargers 2, 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 information on the current and voltage 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 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). In this technology, charging priorities are assigned based on the amount of power consumed, and charging is performed in order from the vehicle with the least mileage or least amount of stored power stored in the vehicle 4, for example. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2020-188669 [Patent Document 2] Japanese Patent Publication No. 2023-034166 Summary of the Invention [Problem to be solved by the invention]

[0004] The above technology can control the charging device so that it does not become overloaded, but there is a problem that even if a charging request is made early, depending on the amount of charge, charging may not be completed for a long time. An object of the present invention is to provide a charge control device and the like that can control a charging device so that it does not become overloaded and that charges in response to an early charging request. [Means for solving the problem]

[0005] In an embodiment, a charging control device electrically charges each of a plurality of vehicles that can be electrically charged in a parking lot, and controls charging of the vehicles connected to the charging device, with the maximum power usage set for charging the plurality of vehicles simultaneously, and temporarily stops charging when the charging time of the vehicle being charged reaches a first hour that is shorter than the charging time for full charge. In the embodiment, the charging control device electrically charges each of a plurality of vehicles that can be electrically charged in a parking lot, and controls the charging of the vehicles connected to the charging device, where the maximum power usage that can be used to charge the plurality of vehicles simultaneously is set, and charges the vehicles one or more times for a first time period that is shorter than the charging time required for a full charge. In an embodiment, a charging control device controls charging of a vehicle connected to a charging device that electrically charges each of multiple vehicles that can be electrically charged in a parking lot, and has a maximum power usage setting that allows simultaneous charging of the multiple vehicles.When the charging time of a vehicle being charged reaches a first time that is shorter than the charging time for full charging, the charging control device determines whether to terminate charging.

[0006] The charging system of the embodiment is a charging system that electrically charges multiple vehicles that can be electrically charged in a parking lot, and includes a charging device having multiple connectors that can be connected to each of the multiple vehicles, and a charging control device that controls the charging of the vehicles by the charging device, wherein the charging device has a maximum power usage setting for simultaneously charging the multiple vehicles, and the charging control device is the charging control device described above. In one embodiment, the charging control method 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 a parking lot, and that has a maximum power usage setting that allows simultaneous charging of the plurality of vehicles.When the charging time of a vehicle being charged reaches a first hour that is shorter than the charging time for full charging, charging is temporarily terminated. [Effects of the Invention]

[0007] According to the above configuration or method, the charging equipment (distribution panel) can be controlled so as not to be overloaded, and charging can be performed in response to an early charging request. Furthermore, it is also possible to charge vehicles that have received a late charging request. [Brief explanation of the drawings]

[0008] [Figure 1] 1 is a schematic diagram of a charging system according to a first embodiment. [Figure 2] FIG. 2 is a diagram illustrating the hardware configuration of a mobile terminal according to the first embodiment. [Figure 3] FIG. 2 is a hardware configuration diagram of a charge control device according to the first embodiment. [Figure 4] (a) shows the charge request table at 22:00 on April 1st, and (b) shows the status table at 22:00 on April 1st. [Figure 5] The following shows a status table, where (a) is the status at 22:40 on April 1st, (b) is the status at 23:10 on April 1st, and (c) is the status at 1:00 on April 2nd. [Figure 6] The figures show the status as of 1:20 on April 2nd, where (a) is the charge request table and (b) is the status table. [Figure 7] FIG. 10 is a schematic sequence diagram when charging is possible in the charging system. [Figure 8] FIG. 10 is a schematic sequence diagram when charging is not possible in the charging system. [Figure 9] FIG. 4 is a schematic sequence diagram when charging is completed in the charging system. [Figure 10]FIG. 10 is a schematic sequence diagram when charging is possible from a standby state in the charging system. [Figure 11] FIG. 4 is a schematic sequence diagram when charging ends in the charging system. [Figure 12] The status table shows (a) the state when a charging request was made from charging number "20230401-7" at 21:10 and before a determination was made that charging was possible, (b) the state after a charging request was made from charging number "20230401-7" and a determination was made that charging was possible, and (c) the state at 22:00. [Figure 13] The following shows a status table, where (a) shows the status at 22:00 on April 1st, and (b) shows the status at 22:20 on April 1st. [Figure 14] 10 is a flowchart showing the processing of a control unit of the charging device. [Figure 15] 10 is a flowchart showing the processing of a control unit of an OCPP server. [Figure 16] 10 is a flowchart showing charging start processing by an OCPP server. [Figure 17] 10 is a flowchart showing the process of determining whether charging has ended or completed by the OCPP server. [Figure 18] 10 is a flowchart showing charging completion processing by the OCPP server. [Figure 19] 10 is a flowchart showing charging termination processing by an OCPP server. [Figure 20] 10 is a flowchart showing charging start processing by an OCPP server. [Figure 21] 10 is a flowchart showing the processing of a control unit of a database. [Figure 22] 10 is a flowchart showing the processing of a control unit of the AP server. [Figure 23] 10 is a flowchart showing a process of determining whether charging has ended or been completed by the OCPP server of the first embodiment A. [Figure 24] 1 shows a status table of the first embodiment A, where (a) shows the state at 1:20 on April 3rd, and (b) shows the state at 1:40 on April 3rd. [Figure 25]10 is a flowchart showing a continuation process of the first embodiment A. [Figure 26] FIG. 10 is a schematic sequence diagram when charging is completed in the charging system of the first embodiment B. [Figure 27] 10 is a flowchart showing a process of determining whether charging has ended or been completed by the OCPP server of the first embodiment B. [Figure 28] FIG. 10 is a schematic sequence diagram when charging is completed in the charging system of the first embodiment C. [Figure 29] 10 is a flowchart showing a process of determining whether charging is complete or not in the charging device of the first embodiment C. [Figure 30] 10 is a flowchart showing a process of determining whether charging has ended or been completed by the OCPP server in the first embodiment C. [Figure 31] 10 is a flowchart showing charging completion processing and the like of the OCPP server of the first embodiment C. [Figure 32] 10(a) is a diagram showing a status table according to the first embodiment D, and FIG. 10(b) is a diagram showing a customer information table according to the first embodiment D. FIG. [Figure 33] 10A is a flowchart showing the chargeability determination process of the control unit of the AP server of the first embodiment D, and FIG. 10B is a flowchart showing the chargeability determination process of the control unit of the OCPP server of the first embodiment D. FIG. [Figure 34] 1 shows the status table of the second embodiment 1, where (a) shows the state at 18:15 on April 1st, and (b) shows the state at 19:05 on April 1st. [Figure 35] The following shows the status table, where (a) is the status at 19:45 on April 1st, and (b) is the status at 20:15 on April 1st. [Figure 36] The following shows a status table, where (a) is the status at 20:45 on April 1st, (b) is the status at 21:30 on April 1st, and (c) is the status at 22:30 on April 1st. [Figure 37] 4 is a time chart illustrating a charging state. [Figure 38] The charging request table for April 1st at 22:30 is shown. [Figure 39] FIG. 10 is a schematic sequence diagram when charging is possible in the charging system. [Figure 40] FIG. 4 is a schematic sequence diagram when charging is completed in the charging system. [Figure 41] FIG. 4 is a schematic sequence diagram when charging ends in the charging system. [Figure 42] FIG. 10 is a schematic sequence diagram when charging is possible from a standby state in the charging system. [Figure 43] FIG. 10 is a schematic sequence diagram of a charge change in the charging system. [Figure 44] 10 is a flowchart showing the processing of a control unit of the charging device. [Figure 45] 10 is a flowchart showing the processing of a control unit of an OCPP server. [Figure 46] 10 is a flowchart showing the charging start and power change processing of the OCPP server. [Figure 47] 10 is a flowchart showing charging completion processing by the OCPP server. [Figure 48] 10 is a flowchart showing the end determination end processing of the OCPP server. [Figure 49] 10 is a flowchart showing a charging determination charging process of an OCPP server. [Figure 50] 10 is a flowchart showing a power determination change process of an OCPP server. [Figure 51] 10 is a flowchart showing the processing of a control unit of a database. [Figure 52] 10 is a flowchart showing the processing of a control unit of the AP server. [Figure 53] 10 is a flowchart showing a chargeability determination process performed by a control unit of an AP server. [Figure 54] 10 is a flowchart showing the termination / continuation determination termination process of the OCPP server of the second embodiment A. [Figure 55] 10 is a flowchart showing a chargeability determination process performed by a control unit of an AP server in a second embodiment B. [Figure 56]10 is a flowchart showing a chargeability determination process performed by a control unit of an AP server in a second embodiment C. [Figure 57] 10 is a flowchart showing the completion / chargeability determination process of the control unit of the OCPP server of the second embodiment B. [Figure 58] 10 is a flowchart showing the termination and chargeability determination process of the control unit of the OCPP server of the second embodiment B. [Figure 59] 11 is a flowchart showing the process (first half) of the control unit of the OCPP server according to the third embodiment. [Figure 60] 11 is a flowchart showing the second half of the process by the control unit of the OCPP server according to the third embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] <Embodiment> As shown in FIG. 1, charging system 101 is used in a parking lot of a housing complex such as an apartment building or an apartment building, or in a parking lot that can accommodate multiple vehicles. The charging system 101 electrically charges a plurality of vehicles 1 that are parked in a parking lot under a contract or the like and that can be electrically charged. The electrically rechargeable vehicle 1 referred to here includes an electric vehicle without an engine, a hybrid vehicle combined with an engine, an electric vehicle that runs on electricity generated by an engine, etc. Vehicle 1 also includes 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 receives an operation (also called a charging request operation) from the owner or user (on their mobile terminal 3) to request charging, the charging control device 105 instructs the charging device 103 to charge while taking into consideration the power usage. FIG. 1 shows an outline of a charging system 101, in which a charging device 103 can be connected to six vehicles 1 and includes six connectors 131, for example.

[0010] <First embodiment 1> 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 a new vehicle 1 that has been requested to be charged is being charged, if the number of vehicles to be charged (total power usage) is less than (or equal to or less than) the maximum number (maximum power usage), the vehicle 1 that has been requested to be charged will be charged, and if the number of vehicles to be charged (total power usage) is greater than (or equal to) the maximum number (maximum power usage), the vehicle 1 that has been requested to be charged will wait for charging. In addition, the charging time for one charging is preset to the first hour, and when one charging is completed, if there is a vehicle 1 in a standby state, the vehicle goes into a standby state, and if there is no vehicle 1 in a standby state, charging for the first hour begins. In this specification, "completion of charging" refers to the termination of charging when the battery is nearly fully charged (more than 90% of full charge), and "end of charging" refers to the termination of a single charge of the first hour. Recharging after the end of charging is also called "charging," and the number of times charging for the first hour is referred to as the "number of charges." It should be noted that these specific forms are provided for the purpose of explaining the embodiments, and the present invention is not limited to these forms.

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

[0012] (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 installed thereon an application (hereinafter referred to as a "mobile application") that can communicate with the charge control device 105. 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 user operations. The storage unit 35 includes a non-volatile storage medium such as a flash memory, and stores, for example, an operating system for performing various processes, programs, applications, and various data. The communication unit 34 performs data communication via a network (for example, the Internet) using a telephone line or an optical line, Bluetooth (registered trademark) communication, Wi-Fi (registered trademark) communication, and the like. By executing the mobile application, the application becomes capable of communicating with the AP server 108, and various information is sent and received. Note that the user registers with the AP server 108 via the mobile application, and 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, the control unit 33 transmits a request to request charging (hereinafter referred to as a “charging request” and see FIG. 7) to the AP server 108. When the control unit 33 receives, via the mobile application, a report that charging has started (hereinafter referred to as a “charging start report” and see FIG. 7), a report that charging has been completed (hereinafter referred to as a “charging completion report” and see FIG. 9), a report that charging is waiting (hereinafter referred to as a “charging wait report” and see FIG. 8), a report that one charging has ended (hereinafter referred to as a “charging end report” and see FIG. 11), a report that charging has started from a standby state (hereinafter referred to as a “charging start report” and see FIG. 10), or the like, the control unit 33 displays the report on the touch panel unit 36. In addition,

[0013] (3) Charging control device As shown in FIG. 3, the charging control device 105 is configured by 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 and status data of the vehicle 1 to be charged by the charging device 103, 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 charging request data includes, for example, a charging request history, and the status data includes, for example, a charging state. The OCPP server 106, database 107, and 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, database 107, and AP server 108 are provided on a public cloud such as AWS, Azure, or Google Cloud Platform, which improves communication efficiency and simplifies implementation. The processing of the server is realized by software processing, but may also be realized by hardware processing using electrical circuits or the like fabricated within the server. Each server will be explained below.

[0014] (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 nonvolatile storage medium such as an HDD, an SDD, or a flash memory, and stores, for example, a charging request table T11 that stores charging request data such as the charging number (reception number) of the charging request, and a status table T12 that stores status data such as the charging state, as shown in Fig. 4. The clock 175 has a calendar function and measures the date.

[0015] 4(a), the charging request table T11 keeps a record of charging requests, and when a new charging request is received, a new record is added to the bottom. The charging request table T11 stores data such as a "charging number" indicating the order in which the charging request was 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 incomplete, 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 the field of 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-3."

[0016] 4(b), the status table T12 stores data such as a "charging number," which is the same data as the "charging number" in the charging request table T11, a "connector ID," which 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," which indicates the state of charging, an "estimated completion time," which indicates the scheduled completion time of one charging of the vehicle 1 for which charging has been requested, and a "number of charges," which indicates the number of times charging with a first charging time has been completed. The data stored in the status table T12 is referred to as "status data" to distinguish it from the data stored in the charging request table T11. The scheduled end time in the status table T12 may be the start time, in which case the time obtained by adding the charging time for one charging session to the start time becomes the charging end time. The charging state includes "charging" and "standby" as shown in FIG. 4(b). When referring to an item in the status table T12 and the data stored in the field of that item, the item may be surrounded by "." For example, when referring to "charging number," it may mean the item "charging number" in the table, or it may mean data such as "20230401-5."

[0017] The charging request table T11 in FIG. 4(a) and the status table in FIG. 4(b) show the state of FIG. 1 at 22:20 on April 1st. In the charging request table T11, as shown in FIG. 4(a), charging requests are made in the order of connector IDs "4", "2", "6", "1", "3", and "5", and are stored in this order. Connectors with IDs "4" and "2" have completed charging, and the "Charging result" field in the charging request table T11 is marked "Completed." Connectors with IDs "6," "1," and "3" are currently charging, and the "Charging result" field in the charging request table T11 is marked "Incomplete," and the "Charging status" field in the status table T12 is marked "Charging." Connector ID "5" has the "Charging status" field marked "Waiting" in the status table T12, and the "Charging result" field in the charging request table T11 is marked "Incomplete." Note that vehicle 1, which was connected to connectors IDs "2" and "4," remains connected in FIG. In this embodiment, the first hour, which is the time for one charge, is set to two hours, for example, and charging is completed after a total of four charges. As shown in Figure 4, charging with charging number "20230401-3" starts at "11:00" (a charge request is made), and after four two-hour charges, is completed at "19:00." Charging with charging number "20230401-5" starts the first charge at "16:30" (a charge request is made), but charging is not complete. As of "22:20," the second charge has ended, and the scheduled end time of the current charge (third charge) is "22:30."

[0018] The status table T12 in FIG. 5(a) shows the state of FIG. 1 at 22:40 on April 1st. The third charge for charging number "20230401-5" ended at "22:30," as shown in status table T12 in Figure 4(b). At that time, charging number "20230401-8" was "on standby," so charging was temporarily terminated, and as shown in Figure 5(a), the "charging status" became "on standby," and "3" was stored in "number of charges." Charging number "20230401-8", which was on standby at 22:20 in Figure 4, began its first charging at 22:30 due to the completion and standby of charging number "20230401-5". Therefore, in Figure 5(a), "0:30" is stored in the "Scheduled completion time" and "0" is stored in the "Number of charges" for charging number "20230401-8". As shown in Figure 4(a), a request for charging with charging number "20230401-7" was made at "21:10", and "23:10" and "0" are stored in the "Scheduled completion time" and "Number of charges" fields of status table T12.

[0019] The control unit 171 includes a CPU, ROM, RAM, etc., and creates a new charge request record in the charge request table T11, changes fields, registers (creates) in the status table T12, changes status data, and deletes records of completed charge numbers in accordance with requests from the OCPP server 106 and the AP server 108. When the control unit 171 makes changes to the tables T11 and T12 in response to a request from the server, it responds to the requesting server. The times in the tables T11 and T12 may be obtained by the database 107 side or from the server side.

[0020] (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 an OCPP application. The OCPP server 106 is connected to an external payment system that manages charging by means of 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 OCPP 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 using a WEB-API. The database 107 is provided on a public cloud where the OCPP server 106 is installed, and requests to the database 107 are made using SQL.

[0021] As shown in FIG. 7, when the OCPP server 106 receives an instruction to start charging from the AP server 108 (hereinafter referred to as a "charging start instruction"), it sends a signal to the charging device 103 to start charging (hereinafter referred to as a "charging start signal"), requests the database 107 to register status data indicating the start of charging (hereinafter referred to as a "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 transmits 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, the charging device 103 transmits 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 that the user has requested to be charged. The instruction (transmission) to start charging to the charging device 103 utilizes transaction management, and the response signal (remote start transaction) sent from the charging device 103 to the charging start signal (start transaction) is also a "normal charging start signal" indicating that charging has started normally.

[0022] As shown in FIG. 9, the OCPP server 106 determines whether charging of the vehicle 1 (charging request) being charged has been completed, and if it determines that charging has been completed, it sends a signal to the charging device 103 indicating that charging has been completed (hereinafter referred to as the "charging completion signal"), requests the database 107 to delete the record corresponding to the charging completion in the status table (hereinafter referred to as the "status record deletion request"), and if charging has been completed successfully, responds to the AP server 108 that charging has been completed successfully (hereinafter referred to as the "charging completion response"). When the OCPP server 106 determines that charging is complete, it sends 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 sends 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 for which the user has requested charging will complete charging. The instruction (transmission) of charging completion utilizes transaction management, and the response signal (remote stop transaction) sent from the charging device 103 to the charging completion signal (stop transaction) is also a "normal charging completion signal" indicating that charging has been completed normally.

[0023] As shown in FIG. 10, the OCPP server 106 determines whether charging is possible for a waiting charging request (vehicle), and if charging is possible, it sends a charging start signal to the charging device 103, requests the database 107 to start changing the charging status to "charging", and when charging starts normally, it sends a charging start response to the AP server 108. Charging here includes both a case where a new charging request is made and the vehicle enters a standby state without charging, and a case where a single charging session is completed and the vehicle enters a standby state. The instruction (transmission) to start charging utilizes transaction management, similar to the charging start signal (see FIG. 7) sent when a charging start instruction is received from the AP server 108. The response signal (remote start transaction) sent from the charging device 103 to the charging start signal (start transaction) is also a "normal charging start signal" indicating that charging has started normally. The determination of whether charging is possible in response to a waiting charging request is made based on the "charging status" in the status table T12 of the database 107, so before making the determination, a request is made to the database 107 to obtain status data (hereinafter referred to as a "status acquisition request").

[0024] 11, the OCPP server 106 determines whether one charge of the vehicle being charged (charging request) has been completed, and if it determines that charging has been completed, it sends a signal to the charging device 103 to terminate charging (hereinafter referred to as a "charging termination signal"), requests the database 107 to change the status data due to the termination of charging (hereinafter referred to as an "termination change request"), and, if charging has been completed successfully, responds to the AP server 108 that charging has been completed successfully (hereinafter referred to as a "charging termination response"). Note that "charging" in charging termination includes charging at the time of a new charging request (see FIG. 7) and charging from a standby state (see FIG. 10). 11, when the OCPP server 106 determines that charging has ended, it transmits a signal including the "connector ID" of the charging target (hereinafter referred to as the "end preparation signal") to the charging device 103, and in response to this, the charging device 103 transmits 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 for which the user has requested charging will end charging. The instruction (transmission) to end charging utilizes transaction management, and the response signal (remote stop transaction) sent from the charging device 103 to the charging end signal (stop transaction) is also a "normal charging end signal" indicating that charging has ended normally.

[0025] In this way, by having the control unit 161, the communication unit 162, and the memory unit 163 work together, the OCPP server 106 includes, as shown in FIG. 7, a charging start instruction input unit to which a charging start instruction is input from the AP server 108, a charging start signal transmitting unit to transmit a signal (which may include a start preparation signal) to cause the charging device 103 to start charging in accordance with the charging start instruction from the AP server 108, a normal charging start signal receiving unit to receive a normal charging start signal (including a response signal if the start preparation signal is included) from the charging device 103, a charging start response output unit to output a charging start response to the AP server 108 when the normal charging start signal is received from the charging device 103, a start registration request output unit to output a start registration request for status data 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. In addition, by having 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. 9, a charging completion determination unit that determines whether charging of the vehicle that requested charging has been completed, a charging completion signal transmission unit that transmits a signal (which may include a completion preparation signal) to the charging device 103 to complete charging when it is determined that charging has been completed, a normal charging completion signal receiving unit that receives a normal charging completion signal (including a response signal if the completion preparation signal is included) from the charging device 103, a charging completion response output unit that outputs a charging completion response to the AP server 108 when a normal charging completion signal is received from the charging device 103, a status record deletion request output unit that outputs a request to delete a status record to the database 107, and a deletion response input unit that inputs a response to the record deletion request from the database 107. Here, the determination of charging completion is made from the "scheduled end time" and "number of charges" in the status table T12, and therefore the system is also provided with an output unit for requesting estimated end time, etc., which requests the database 107 to acquire status data on the "scheduled end time" and "number of charges," and an acquisition response input unit into which responses to the acquisition of this status data are input.

[0026] In addition, by having 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. 10, a chargeability determination unit that determines whether charging is possible in response to a waiting charge request, a charge start signal transmission unit that transmits a signal (including a start preparation signal) to the charging device 103 to start charging if it is determined that charging is possible, a normal charge start signal receiving unit that receives a normal charge start signal (including a response signal if the start preparation signal is included) from the charging device 103, a charge start response output unit that outputs a charge start response to the AP server 108 when the normal charge start signal is received from the charging device 103, a start change request output unit that outputs a start change request for status data to the database 107, and a start change response input unit that inputs the response to the start change request from the database 107. Here, the determination of whether charging is possible is made from the "charging status" in the status table T12, so the device is also provided with a charging status acquisition request output unit that requests the database 107 to acquire status data for the "charging status," and an acquisition response input unit that receives responses to these charging status acquisition requests.

[0027] In addition, by having 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. 11, a charging completion determination unit that determines whether charging of the charging request (vehicle) has been completed, a charging completion signal transmission unit that transmits a signal (which may include a completion preparation signal) to the charging device 103 to terminate charging when it is determined that charging has been completed, a normal charging completion signal receiving unit that receives a normal charging completion signal (including a response signal if the completion preparation signal is included) from the charging device 103, a charging completion response output unit that outputs a charging completion response to the AP server 108 when the normal charging completion signal is received from the charging device 103, a completion change request output unit that outputs a completion change request for status data to the database 107, and a completion change response input unit that inputs the response to the completion change request from the database 107. Here, the charging completion determination is made from the "scheduled end time" in the status table T12, so the device is also provided with a scheduled end time acquisition request output unit that requests the database 107 to acquire status data for the "scheduled end time," and an acquisition response input unit that receives responses to the acquisition of this status data (scheduled end time).

[0028] (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 using, for example, a WEB-API, or with the mobile terminal 3 using data communication over a network (e.g., the Internet) using a telephone line or an optical line, Bluetooth (registered trademark) communication, Wi-Fi (registered trademark) communication, etc. For communication with the database 107, for example, SQL is used. The clock 184 measures the date and time when a charging request is made, the time when charging started or the time elapsed since the start of charging, and the time when charging is completed. These measured dates and times are stored in fields of a charging request table T11 in the database 107. The clock 184 has a calendar function and measures the year, month, day, hour, and minute. The AP server 108 receives charging requests from the portable terminal 3, and transmits charging start reports, charging completion reports, charging standby reports, (re)charging start reports, and charging completion reports. The AP server 108 issues a command to start charging (outputs a command to start charging) to the OCPP server 106, and inputs a charge start response, a charge end response, a charge completion response, and a (re)charge start response between the AP server 108 and the OCPP server 106. When a new charge request is received from the mobile terminal 3, the OCPP server 106 is instructed to start charging by determining whether or not charging is possible for the vehicle 1 that has received the charge request, and issuing the command if charging is possible. The AP server 108 makes requests to the database 107 such as requests to create a new charging request in the charging request table T11, requests to change the charging request due to completion of charging, requests to obtain status data on the charging state, and requests to register a standby state.

[0029] 7 and 8, when the AP server 108 receives a charge request from the mobile terminal 3, it requests the database 107 to create a charge request for a new record in the charge request table T11 and to acquire the charging status. In response to these requests, the database 107 sends a creation response or an acquisition response. The AP server 108 determines whether or not charging is possible for the vehicle 1 that has newly requested charging, and if charging is possible (as in the case of FIG. 7), outputs a charging start instruction to the OCPP server 106, or if a charging start response indicating that charging has started successfully in response to the charging start instruction is input from the OCPP server 106, sends a charging start report to the mobile terminal 3. The AP server 108 also determines whether or not charging is possible for the vehicle 1 that has newly requested charging, and if charging is not possible (as in FIG. 8), requests registration of status data of "waiting" in the status table T12 of the database 107 (hereinafter referred to as a "waiting registration request"), and if a registration response to the waiting registration request is input from the database 107, sends a charging wait report to the mobile terminal 3. As shown in FIG. 9, when the AP server 108 receives a charging completion response from the OCPP server 106 indicating that charging has been completed successfully, the AP server 108 transmits a charging completion report to the mobile terminal 3, outputs a request to change the charging request in the charging request table T11 to the database 107, and receives a response to the change request. As shown in FIG. 10, when a charging start response is received from the OCPP server 106 indicating that charging has started for a waiting vehicle, the AP server 108 transmits a charging start report to the mobile terminal 3. As shown in FIG. 11, when a charging completion response is received from the OCPP server 106 indicating that one charging session with a charging time of the first hour has been completed, the AP server 108 transmits a charging completion report to the mobile terminal 3.

[0030] In this way, by having the control unit 181, the communication unit 182, and the memory unit 183 work together, the AP server 108 includes, as shown in Figures 7 and 8, a charging request receiving unit that receives a charging request from the mobile terminal 3, a charging feasibility determination unit that determines whether the vehicle 1 that has requested charging can be charged, a charging start instruction output unit that outputs a charging start instruction to the OCPP server 106 if it is determined that charging is possible, a charging start response input unit that receives a charging start response from the OCPP server 106, a charging start report sending unit that sends a charging start report to the mobile terminal 3 when a charging start response is received, a charging standby report sending unit that sends a charging standby report to the mobile terminal 3 if it is determined that charging is not possible, a request output unit that outputs to the database 107 a request to create a charging request in the charging request table T11, a request to obtain the charging status in the status table T12, or a standby registration request in the status table T12 if it is determined that charging is not possible, and a response input unit that receives the requested response from the database 107.

[0031] Furthermore, by having the control unit 181, the communication unit 182, and the memory unit 183 work together, the AP server 108 is provided with, as shown in FIG. 9, a charging completion response receiving unit that receives a charging completion response from the OCPP server 106, a charging completion report sending unit that sends a charging completion report to the portable terminal 3 when a charging completion response is received, a request output unit that outputs a request to the database 107 to change the charging request data in the charging request table T11, and a response input unit that inputs the requested response from the database 107. In addition, by having the control unit 181, the communication unit 182, and the memory unit 183 work together, the AP server 108 is provided with a charging start response input unit that inputs a charging start response to the waiting vehicle 1 from the OCPP server 106, and a charging start report sending unit that sends a charging start report to the mobile terminal 3 when a charging start response is received, as shown in FIG. 10. In addition, by having the control unit 181, the communication unit 182, and the memory unit 183 work together, the AP server 108 is provided with a charging completion response input unit that receives a charging completion response from the OCPP server 106, and a charging completion report transmission unit that transmits a charging completion report to the mobile terminal 3 when a charging completion response is received, as shown in FIG. 11.

[0032] 3. Sequence (1) Charging request Let us take the case of connecting to the connector 131 in FIG. 1 with a connector ID of "3" as an example. The user connects the vehicle 1 to the connector 131 "3" and, at "21:10" on April 1st, uses the mobile application to perform a charging request operation on the mobile terminal 3 as shown in FIG. When the AP server 108 receives a charge request from the mobile terminal 3, it requests the database 107 to create a new charge request. In response to this request, the database 107 creates a record with a charge number of "20230401-7" as a new request in the charge request table T11, registers "3" as the connector ID, "incomplete" as the charging result, and "20230401:2110" as the request date and time, and sends a creation response to the AP server 108, as shown in (a) of FIG.

[0033] (2) Start charging As shown in FIG. 7, when the AP server 108 receives a charging request from the mobile terminal 3, it requests the database 107 to acquire status data on the charging state, and determines whether charging is possible in response to the new request based on the acquired charging state (status data). (2-1) Rechargeable FIG. 12(a) shows the status table T12 when a charge request has been received from the charge number "20230401-7" and before the chargeability determination has been made. As described above, when a new charging request is received, the AP server 108 obtains charging status data from the database 107 and determines whether charging is possible. Here, as shown in FIG. 12(a), there are two charging numbers (vehicle 1) with a charging status of "charging," which is less than the maximum number of charging vehicles (here, three). Therefore, the AP server 108 determines that charging is possible for the new request for charging number "20230401-7." If the AP server 108 determines that charging is possible, it outputs a charge start instruction to the OCPP server 106, as shown in Fig. 7. The charge start instruction has a transaction function and becomes a remote start transaction. The charge start instruction includes data on the "connector ID" for which charging was requested. Upon receiving the instruction to start charging, the OCPP server 106 transmits a start preparation signal to the charging device 103. Upon receiving the start preparation signal, the charging device 103 checks the connection of the "connector ID" included in the start preparation signal, and transmits 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 the charging request matches the "connector ID" to which the vehicle 1 of the charging device 103 is connected, and requests the database 107 to start registration in the status table T12. As shown in FIG. 12(b), the database 107 registers "20230401-7" as the charging number, "3" as the connector ID, "charging" as the charging state, "23:10" as the scheduled end time, and "0" as the "number of charges," and responds to the OCPP server 106 with a start registration. 7, the OCPP server 106 transmits a charging start signal to the charging device 103, and the charging device 103 starts charging the connector 131 with a connector ID of "3" and transmits a response signal indicating that charging has started to the OCPP server 106. The response signal is a normal charging start signal, and is a remote start transaction. Upon receiving the response signal (normal charging start signal), the OCPP server 106 outputs 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.

[0034] (2-2) Cannot be charged FIG. 13(a) shows the status table T12 when a charge request has been received from the charge number "20230401-8" and before the chargeability determination has been made. As shown in Figures 7 and 8, when a new charging request is received, the AP server 108 acquires status data of the charging state. Here, as shown in Figure 13(a), there are three charging numbers (vehicles 1) with a charging state of "charging," which is the same as the maximum number of vehicles that can be charged. Therefore, the AP server 108 determines that charging is not possible for the new request for charging number "20230401-8." 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. 8. In response to this, the database 107 registers "20230401-8" as the charging number, "5" as the connector ID, and "standby" as the charging status, as shown in Fig. 13(b), 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, it reports to the mobile terminal 3 that it is on standby for charging.

[0035] (2-3) Starting charging during standby The OCPP server 106 determines whether charging is possible in response to a waiting charging request. Here, this is determined based on the number of "charging" units in the status table T12. For example, in FIG. 5(a), three vehicles with charging numbers "20230401-7", "20230401-6", and "20230401-8" are currently charging, and vehicle 1 with charging number "20230401-5" is "on standby". After that, charging of vehicle 1 with charging number "20230401-7" is completed, and as shown in (b) of Figure 5, charging of vehicle 1 with charging number "20230401-5", which was on standby, begins, and the charging status becomes "charging". As shown in FIG. 10, the OCPP server 106 requests the database 107 to acquire status data of the charging state, and the database 107 returns the status data to the OCPP server 106 in response to this request.

[0036] The OCPP server 106 counts the number of "waiting" status data returned and determines whether charging is possible. In Figure 5 (a), if the number of waiting vehicles is "1" and charging of vehicle 1 with charging number "20230401-7" ends after "23:10", the number of charging vehicles will be two, with charging numbers "20230401-6" and "20230401-8", which is less than the maximum number of "3", so it is determined that charging is possible for vehicle 1 with "waiting" charging number "20230401-5". 10, when it is determined that charging is possible, the OCPP server 106 outputs a start preparation signal to the charging device 103. Upon receiving the start preparation signal, the charging device 103 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 charging device 103 is connected. In response to this, the OCPP server 106 determines that the "connector ID" of the available charging number matches the "connector ID" to which the vehicle 1 of the charging device 103 is connected, and requests the database 107 to make a start change to change the "charging status" and "scheduled end time" in the status table T12. As shown in (b) of Figure 5, the database 107 changes the charging status of the charging number "20230401-5" to "charging" and the scheduled end time to "1:30", and responds to the OCPP server 106 with a start registration.

[0037] 10, the OCPP server 106 outputs a charging start signal to the charging device 103, and the charging device 103 starts charging the connector 131 with a connector ID of "6", and outputs a response signal indicating that charging has started to the OCPP server 106. The response signal is a normal charging start signal, and is a remote start transaction. When the response signal (normal charging start signal) is input, the OCPP server 106 transmits a (re)charging start response to the AP server 108, and in response to this, the AP server 108 reports to the portable terminal 3 that the (re)charging has started. Note that new charging and (re)charging are the same process between the OCPP server 16 and the charging device 103, but differ between the OCPP server 106 and the DB 107 in that information is registered in a new record at the time of new charging and information in the record field is changed at the time of recharging, and also differ between the OCPP server 106 and the AP server 108 and between the AP server 108 and the mobile terminal 3 in that it is possible to recognize that it is recharging. Note that the charging start process for new charging and (re)charging may be exactly the same process.

[0038] (3) Charging completed The OCPP server 106 determines whether charging is complete or not. Here, this is determined based on the "scheduled completion time" and the "number of charging attempts." For example, the determination is made based on whether the number of charging times (including the completed charging times) of the vehicle 1 that ended at the scheduled end time matches the "number of charging times" that is determined to be complete. In this example, the number of charging times that is determined to be complete is four. For example, in FIG. 5(c), charging with the charging number "20230401-5" has already been completed "3" times, and when the current charging is completed, the number of charging times will be "4", and charging will be determined to be complete. For this reason, the OCPP server 106 requests the database 107, which stores the status table T12, to acquire the estimated end time and other information including the "estimated end time" and "number of charges" of charging, as shown in FIG.

[0039] When a request to acquire the estimated end time and the like is made, the database 107 acquires the "estimated end time" and the "number of charging times" and sends the acquisition response to the OCPP server 106. When it is determined that charging is complete based on the acquired "scheduled completion time" and "number of charging times," a completion preparation signal is output to the charging device 103, as shown in Fig. 9. The charging completion signal has a transaction function and serves as a remote stop transaction. Upon receiving the completion preparation signal, 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 indicating that the connection is established. In response to this, the OCPP server 106 determines that the "connector ID" for the completed charging matches the "connector ID" of the charging device 103 to which the vehicle 1 is connected, and requests the database 107 to delete the status of the completed charging number. The database 107 deletes the record with the charging number "20230401-5," for example, and responds to the OCPP server 106 with a deletion. Note that by deleting a record, the records below the deleted record move up. The OCPP server 106 outputs a charging completion signal to the charging device 103, and the charging device 103 completes charging for charging number "20230401-5" and outputs a response signal indicating that charging has been completed to the OCPP server 106. The response signal is a normal charging completion signal, and serves as a remote stop start transaction.

[0040] When the response signal (charge normal completion signal) is input, the OCPP server 106 transmits a charge completion response to the AP server 108, and in response to this, the AP server 108 reports to the portable terminal 3 that charging has been completed. Furthermore, upon receiving the charging completion response, the AP server 108 requests that 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 be changed. The database 107 changes the charging result corresponding to the charging number "20230401-5" in the charging request table T11 to "completed" and the charging completion date and time to "20230402:0110" as shown in FIG. 6(a), and responds to the AP server 108.

[0041] (4) Charging complete The OCPP server 106 determines whether charging has finished. Here, this is determined based on the "scheduled end time." For example, in FIG. 5(a), the scheduled end time for the charging number "20230401-8" is "0:30", and charging is determined to be completed when this time arrives. For this reason, the OCPP server 106 requests the database 107, which stores the scheduled end time including the "scheduled end time" of charging in the status table T12, as shown in FIG. When a request to acquire the scheduled end time is made, the database 107 acquires the "scheduled end time" and sends the acquisition response to the OCPP server 106. When it is determined that charging is to be completed based on the acquired "scheduled completion time," a completion preparation signal is output to the charging device 103, as shown in Fig. 11. The charging completion signal has a transaction function and serves as a remote stop transaction.

[0042] When the end preparation signal is input, the charging device 103 checks the connection of the "connector ID" included in the end preparation signal, and outputs a response signal to the OCPP server 106 indicating that the connection is established. In response, the OCPP server 106 determines that the "connector ID" for charging completion matches the "connector ID" of the vehicle 1 connected to the charging device 103, and sends a completion change request to the database 107. The "completion change" includes moving the record for the completed charging number to the bottom (this includes deleting the previous record and creating a new record at the bottom), and leaving the "estimated completion time" for the charging number for which charging completed blank and adding "1" to the "number of charges" and storing the result in the "number of charges" field of the bottom record. For example, the database 107 moves the record for the charging number "20230401-7" in FIG. 5(a) to the bottom, as shown in FIG. 5(b), and changes the "charging status" to "standby" and the "number of charges" to "1." 11, the OCPP server 106 outputs a charging end signal to the charging device 103, and the charging device 103 ends charging and outputs a response signal to that effect to the OCPP server 106. The response signal is a normal charging end signal, and serves as a remote stop start transaction. When the response signal (charge normal end signal) is input, the OCPP server 106 transmits a charge end response to the AP server 108, and in response to this, the AP server 108 reports to the portable terminal 3 that charging has ended.

[0043] 4. Flowchart The processing of the control unit of each device will be described. (1)Charging device The processing of the control unit 133 of the charging device 103 will be described with reference to FIG. When the program starts and the control unit 133 receives a start preparation signal from the OCPP server 106 ("Yes" in S101 in the figure), it checks the connection of the vehicle 1 with the "connector ID" included in the start preparation signal and sends a response signal to the OCPP server 106 indicating the confirmation (S102). There are two types of response signals: 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. In the case of an error signal, the error signal is reported to the mobile terminal 3 via the OCPP server 106 and AP server 108. Thereafter, when a charging start signal is received from the OCPP server 106 ("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 sent to the OCPP server 106 (S104).

[0044] In step S105, when a completion preparation signal is received from the 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 confirmation is sent to the OCPP server 106 (S106). Thereafter, when a charging completion signal is received from the OCPP server 106 ("Yes" in S107), charging to the vehicle 1 with the "connector ID" included in the completion preparation signal is turned off, and a response signal (charging normal completion signal) indicating that charging has been completed is sent to the OCPP server 106 (S108). In step S107, if a response signal (charge normal completion signal) is not input ("No"), the process proceeds to step S109.

[0045] In step S109, if a termination preparation signal is received from the OCPP server 106 ("Yes" in the figure), the connection of vehicle 1 with the "connector ID" included in the termination preparation signal is confirmed, and a response signal indicating confirmation is sent to the OCPP server 106 (S110). Thereafter, when a charging completion signal is received from the OCPP server 106 ("Yes" in S111), charging to the vehicle 1 with the "connector ID" included in the completion preparation signal is turned off, and a response signal (charging normal completion signal) indicating that charging has been completed is sent to the OCPP server 106 (S112). In step S111, if a response signal (charge normal end signal) is not received ("No"), the process proceeds to step S101. Although not shown, if there is no signal input in steps S103, S107, and S111, an error may be reported to the mobile terminal 3 via the OCPP server 106 and the AP server 108.

[0046] (2) OCPP server In the OCPP server 106, the OCPP application performs various processes as a result of the control unit 161 executing a program. The following describes this process with reference to the flowchart in FIG. When the OCPP application is started (start in FIG. 15), it is determined whether a charging start instruction has been input from the AP server 108 (S120). If a charge start instruction has been input ("Yes"), the "connector ID" of the charging target is acquired (S121), and charging start processing is performed (S122), and then the process proceeds to step S123. Here, the charge start instruction includes the "connector ID" of the charging target, and the connector ID is acquired from the charge start instruction. The charge start processing in step S122 will be described later. If a charge start instruction has not been input ("No") in step S120, the process proceeds to step S123.

[0047] In step S123, the number of vehicles to be charged N is obtained from database 107, the variable "K" is set to "1" (S124), and the estimated end time etc. for the Kth charging number is obtained (S125). The estimated end time etc. here includes at least the "estimated end time" and "number of charges" for the record for the Kth charging number. Next, a termination / completion determination is made based on the current time and the scheduled termination time (S126). Specifically, as shown in Fig. 17, if the scheduled termination time has passed and the number of charges (including the completed charge) is equal to the number of completed charge times ("Yes" in S1261, "Yes" in S1262), it is determined to be "completed" (S1263), if the scheduled termination time has passed and the number of charges (including the completed charge) is not equal to the number of completed charge times ("Yes" in S1261, "No" in S1262), it is determined to be "completed" (S1264), and if the scheduled termination time has not passed ("No" in S1261), it is determined to be completed or not finished (S1265).

[0048] In step S126, if it is determined that charging is complete ("Complete"), a completion process (S127) is performed and the process proceeds to S130, if it is determined that charging has ended ("End"), a completion process (S128) is performed and the process proceeds to step S130, and if it has not ended or completed ("No"), the process proceeds to step S130. The completion process in step S127 and the completion process in step S128 will be described later. The determination of end / completion of step S126 is performed for all units to be charged N. In other words, the process is repeated until the variable "K" becomes the number of units to be charged "N." If "K" is not "N" ("No" in S130), "K" is incremented by "K+1" (S129) and the process proceeds to step S125; if "K" is "N" ("Yes" in step S130), the process proceeds to step S131.

[0049] In step S131, the number of waiting vehicles M and the number of charging vehicles L are obtained from the "charging status" of database 107, and if there are any waiting vehicles (i.e., the number of waiting vehicles M is 1 or more) ("Yes" in S132), proceed to step S133; if there are no "waiting vehicles" ("No"), proceed to step S120. In step 133, the variable "I" indicating the number of waiting vehicles is set to "1", and it is determined whether charging is possible for the I-th waiting charging request (S134). Specifically, if the numerical value (number of vehicles) obtained by adding the variable "I" to the number of vehicles to be charged "L" is less than the maximum number (numerical value) that can be charged, it is determined that charging is possible, and if it is equal to or greater than the maximum number, it is determined that charging is not possible.

[0050] In step S134, if it is determined that the I-th charging number (vehicle 1) is chargeable ("Yes"), charging start processing (S135) is performed, and the process proceeds to step S 136. The charging start processing in step S135 will be described later. The determination of whether charging is possible in step S134 is performed for all of the waiting units M. That is, the process is repeated until the variable "I" becomes the waiting unit M. If "I" is not "M" ("No" in S136), "I" is set to "I+1" (S137) and the process proceeds to step S134; if "I" is "M" ("Yes" in step S136), the process proceeds to step S120.

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

[0052] (2-2) Completion process (S127) As shown in FIG. 18 (see FIG. 9 for the sequence), the completion process S127 transmits a completion preparation signal to the charging device 103 (S1271). The completion preparation signal includes the "connector ID" of the charging target, and the charging device 103 transmits a response signal indicating that the connection status 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. When the OCPP server 106 receives a response signal in step S1272 ("Yes"), if the response signal is a normal signal ("Normal" in S1273), it requests the database 107 to delete the status record in the status table T12 (S1274), and if it receives a deletion response from the database 107 indicating that the deletion has been completed ("Yes" in S1275), it proceeds to step S1276. In step S1276, a charging completion signal is transmitted to charging device 103. In response to this, charging device 103 completes charging, and upon receiving a response signal (charging normal completion signal) from charging device 103 indicating that charging has been completed normally ("Yes" in S1277), a charging completion response indicating that charging has been completed normally is output to AP server 108 (S1278), and the process proceeds to step S130 in FIG. 15. In step S1273, if the input signal is an error signal ("Error"), an error indicating that the vehicle 1 and the connector are not electrically connected is output to the AP server 108 (S1279), and the process proceeds to step S130 in FIG. 15.

[0053] (2-3) Termination process (S128) As shown in Fig. 19 (see Fig. 11 for the sequence), the termination process S128 transmits a termination preparation signal to the charging device 103 (S1281). The termination preparation signal includes the "connector ID" of the charging target, and the charging device 103 transmits a response signal to the OCPP server 106 indicating that the connection status of the "connector ID" has been confirmed (step S110 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 step S1282, when a response signal is received ("Yes"), if the response signal is a normal signal ("Yes" in S1283), a request is made to database 107 to change the end of status table T12 (S1284), and if a response to the end change is received from database 107 ("Yes" in S1285), the process proceeds to step S1286. In step S1286, a charging end signal is transmitted to charging device 103. In response to this, charging device 103 ends charging, and when a response signal (charging normal end signal) indicating that charging has ended normally is received from charging device 103 (“Yes” in S1287), a charging end response indicating that charging has ended normally is output to AP server 108 (S1288), and the process proceeds to step S130 in FIG. In step S1283, if the input signal is not a normal signal ("No"), an error indicating that the vehicle 1 and the connector are not electrically connected is output to the AP server 108 (S1289), and the process proceeds to step S130 in FIG. 15.

[0054] (2-4) Charging start process (S135) The (re)charging start process in step S135 in FIG. 15 is a process for starting (re)charging the waiting vehicle 1. On the other hand, the charging start process in step S122 is a process for starting the first charging of a vehicle 1 that has newly requested charging. Therefore, both processes perform similar processing as shown in Figures 16 and 20 (see Figures 7 and 10 for the sequences), but differ in that step S122 requests the database 107 to register the start (see steps S1224 to S1225 in Figure 16), whereas step S135 requests the database 107 to change the start (steps S1354 to S1355 in Figure 20), and in that step S122 responds to the AP server 108 to start charging (step S1228 in Figure 16), whereas step S135 responds to the AP server 108 to start charging (step S1358 in Figure 20). The explanation of the flow of the charging start process in step S135 (FIG. 20) can be made using the explanation of the flow of the charging start process in step S122, except for the above-mentioned differences.

[0055] (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 charging request from the AP server 108 ("Yes" in S140), the control unit 171 creates a new charging request in the bottommost record of the charging request table T11, sends a creation response (S141), and proceeds to step S142. The charging request creation request includes a "charging number" assigned in the order of receipt and a "connector ID" for connecting to the vehicle 1 requesting charging, and the control unit 171 registers, for example, "20230401-5", "6", "incomplete", and "20230401:1630" in the "charging number", "connector ID", "charging result", "request date and time", and "charging completion date and time" fields of the newly created record (see (a) in FIG. 4). Note that the request date and time may be determined using the clock 175 in the database 107, or may be included in the charging request creation request.

[0056] (3-2) In step S142, if there is a request to register or delete status data ("Yes"), a response to registration is made by registering (storing) the data in the field of the record at the bottom of the status table T12 or deleting the record of the charging request for which charging has been completed (S143), and the process proceeds to step S144.

[0057] (3-2-1) Registration Registration occurs when there is a new charging request. If charging is possible, the registration request is a start registration request (see Figure 7). For example, a charging request is made at 21:10 for the charging number "20230401-7" in Figure 6(a). At 21:10, before the request, two vehicles are being charged and another vehicle can be charged, as shown in Figure 12(a). In this way, when charging is possible in response to a new request, charging starts immediately, and as shown in the record at the bottom of the status table T12, "20230401-7," "3," "charging," "23:10," and "0" are registered in the "charging number," "connector ID," "charging status," "estimated completion time," and "number of charges," as shown in (b) of Figure 12. The charging time for one charge here is, for example, two hours, and can be set as appropriate. If charging is not possible, the registration request is a standby registration request (see Figure 8). For example, if a new charging request is made at 22:00 for the charging number "20230401-8" in the bottom row of Figure 4(a), at this time, as shown in Figure 13(a), three vehicles 1 are being charged and charging is not possible, and as shown in Figure 13(b), "20230401-8", "5", and "Waiting" are registered in the "Charging Number", "Connector ID", and "Charging Status" of the bottom row of the record. The registration request may include data on the "charging number," "connector ID," "charging status," "estimated completion time," and "number of charges," and the "estimated completion time" may be stored on the database 107 side using the time of clock 175 in database 107.

[0058] (3-2-2) Delete Deletion occurs when charging is completed, as shown in Fig. 9. In other words, when charging is completed, there is no longer any need to manage the number of charging times, etc. For example, (c) in Figure 5 shows the status table T12 at 1:00, where charging number "20230401-5" has been charged three times and the current (fourth) charge is scheduled to end at 1:10. When this charge ends, the number of charges will be four, charging will be complete, and the record for charging number "20230401-5" will be deleted in (b) in Figure 6.

[0059] (3-3) In step S144, if there is a request to change the charging request table T11 ("Yes"), the relevant sections ("Charging result" and "Charging completion date and time") in the charging request table T11 are changed and a change response is made (S145), and the process proceeds to step S146. The request to change the charging request is made when the charging request that was in progress is completed. For example, as shown in (a) of Figure 4, the charging result for the charging number "20230401-5" is "incomplete." However, as shown in (a) of Figure 6, when charging is completed, the charging result is changed to "completed" and the charging completion date and time is changed to "20230402:0110" in the record with the charging number "20230401-5."

[0060] (3-4) In step S146, if there is a request to change the status table T12 ("Yes"), the corresponding part in the status table T12 is changed and a change response is sent (S147), and the process proceeds to step S148. The change request includes a start change request when charging starts from a standby state (see FIG. 10) and an end change request when one charge has ended (see FIG. 11). For example, as shown in (c) of Figure 5, the start change request indicates that charging number "20230401-8" is "waiting," and when charging starts, the charging status in the record for charging number "20230401-8" is changed to "charging" and the scheduled end time is changed to "3:10," as shown in (b) of Figure 6. For example, as shown in Figure 5(a), in a termination change request, charging number "20230401-8" is "charging" and the number of charges is "0." When charging ends at "0:30," as shown in Figure 5(c), the record for charging number "20230401-8" moves to the bottom, the charging status changes to "standby," the expected end time is left blank, and the number of charges is changed to "1."

[0061] (3-5) In step S148, if there is a request to obtain the status ("Yes"), the status data of the corresponding record in the status table T12 is obtained, output to the requesting party, and an acquisition response is made (S149), and the process proceeds to step S140. For example, in response to a request to obtain a status, all fields in the status table T12 are obtained and sent, but it is also possible to obtain only the necessary data.

[0062] (4) AP server In the AP server 108, the AP application performs various processes as a result of the control unit 181 executing a program. The following will explain this process using the flowchart in FIG. When the AP application is run (started) and an operation to start charging is performed from the portable terminal 3 ("Yes" in step S170), a charging request corresponding to the portable terminal 3 is created in the charging request table T11 of the database 107 (S171). Specifically, as shown in Fig. 7 and Fig. 8, a request to create a charging request is made to the database 107, and when a new charging request is created in the charging request table T11, a response is returned from the database 107 indicating that the request has been created. In step S172, the charging state (status data) is acquired. Specifically, as shown in Fig. 7 and Fig. 8, a request is made to the database 107 to acquire the charging state from the status table T12, and the status data of the charging state is returned from the database 107.

[0063] When the control unit 181 acquires the status data, particularly the charging status, it determines whether or not charging is possible for the vehicle 1 that has newly requested charging (S173). Specifically, it acquires (calculates) the number of vehicles currently being charged from the acquired charging status, and if the number is less than the maximum number of vehicles that can be charged, it is determined that "charging is possible," and if the number of vehicles that can be charged is equal to or greater than the maximum number, it is determined that "charging is not possible." If it is determined in step S173 that charging is possible, as shown in FIG. 7, the OCPP server 106 is instructed to start charging (S174), and if a charging start response is received from the OCPP server 106 indicating that charging has started successfully ("Yes" in S175), a charging start report is sent to the portable terminal 3 (S176), and the process proceeds to step S177. If it is determined in step S173 that "charging is not possible", a request is made to database 107 to register in status table T12 of database 107 that charging is in a standby state (S178), a charging standby report is sent to mobile terminal 3 (S179), and the process proceeds to step S177. Specifically, as shown in Fig. 8, standby registration is requested to database 107, and once registration is completed, a response is returned from database 107 indicating that registration has been completed.

[0064] In step S177, if there is a charging completion response from the OCPP server 106 ("Yes"), as shown in FIG. 9, a charging completion report is sent to the portable terminal 3 and a charging request change is made to the database 107 (S180, S181), and the process proceeds to step S182; if there is no charging completion response ("No"), the process proceeds to step S182. Specifically, as shown in FIG. 9, the charge request change is made by requesting the database 107 to change the charge request, and when the charge request table T11 is changed, the database 107 responds to the effect that the change has been made. In step S182, as shown in FIG. 10, if there is a charging start response from the OCPP server 106 ("Yes"), a charging start report is sent to the portable terminal 3 (S183) and the process proceeds to step S184; if there is no charging start response ("No"), the process proceeds to step S184. In step S184, as shown in FIG. 11, if there is a charging completion response from the OCPP server 106 indicating that one charging has been completed ("Yes"), a charging completion report is sent to the portable terminal 3 (S185) and the process proceeds to step S170; if there is no charging completion response ("No"), the process proceeds to step S170.

[0065] <First embodiment A> As shown in FIG. 17, the charge control device 105 of the first embodiment 1 performs termination processing when the scheduled termination time has passed and the number of charging times has not reached the number of charging completion times, regardless of whether there is a charging request during standby. However, if there is a standby charging request before, at, or after the scheduled end time, charging for the first hour may be terminated, and if there is no charging request, charging for the next first hour may be continued. The following mainly describes the changed parts as the first embodiment A.

[0066] 1. OCPP Server Configuration When charging ends and the charging time of the first vehicle 1 being charged reaches the first hour (including a time longer or shorter than one charging time), if there is a second vehicle 1 waiting, the OCPP server charges the waiting second vehicle for the first hour and terminates charging of the first vehicle 1, and if there is no waiting vehicle, continues charging the first vehicle for the next charging time.

[0067] When charging is terminated or completed, the OCPP server 106A, similar to when charging is completed by the OCPP server 106 in the first embodiment 1, has the control unit 161, communication unit 162, and memory unit 163 cooperate to terminate the charging when the first hour of charging is terminated / continue the next charging / determine whether the charging is completed, a charging termination signal transmission unit, a normal charging termination signal reception unit, a charging termination response output unit, a termination change request output unit, a termination change response input unit, a start change request output unit indicating that the next charging has started, a start change response input unit for the next charging, a charging completion signal transmission unit, a normal charging completion signal reception unit, a charging completion response output unit, a status record deletion request output unit, a deletion response input unit, an output unit for a request to obtain estimated termination time, etc., and an acquisition response input unit. The termination / continuation / completion determination unit here is determined based on at least the "scheduled termination time," "number of charges," and "charging state" in the status table T12, and therefore includes a data acquisition request output unit that requests the database 107 to acquire status data on the "scheduled termination time," "number of charges," and "charging state," and an acquisition response input unit that receives responses to the data acquisition.

[0068] 2. OCPP Server Flowchart (1) Overall In the OCPP server 106A, the control unit 161 executes a program, and the OCPP application performs various processes. The following description will be given with reference to the flowcharts of FIG. 15 and FIG. When the OCPP application starts, it performs step S124 from the start of Fig. 15, performs the processing of Fig. 23, and then proceeds to step S131 of Fig. 15. In this way, the flowchart of OCPP server 106A differs in the processing between steps S125 to S130. When the control unit 161 acquires the Kth scheduled end time etc. in step S125, it determines whether the Kth charge end time has passed (S1261A). If it is determined in step S1261A that the end time has not passed ("No"), it is determined that the process has not ended or been completed, and the process proceeds to step S130. In step S1261A, if it is determined that the end time has passed ("Yes"), it is determined whether the number of charges for the charge request for which the end time has arrived (including the number of completed charges) is the number of completed charges (S1262A).

[0069] If it is determined in step S1262A that the number of charging completions has been reached ("Yes"), it is determined that the charging has reached full charge, and a completion process (S127, see FIG. 18) is performed, and the process proceeds to step S130. The completion process is the same as the process in step S128 in the first embodiment. If it is determined in step S1262A that the number of charging completions is not reached ("No"), the status data of all charging states is acquired (S1263A), and if the acquired charging state includes "standby" ("Yes" in S1264A), the charging is terminated, and termination processing for this purpose (S128, see FIG. 19) is performed, and the process proceeds to step S130. Note that the termination processing is the same as the processing in step S128 in the first embodiment. If it is determined in step S1264A that the charging is not in a "standby" state ("No"), the charging is continued as is, and a continuation process for this (S139A) is performed, and the process proceeds to step S130.

[0070] (2) Continuation processing The continuation process is a process for maintaining the charging state as it is and performing the next first hour of charging even after the first hour of charging has ended. FIG. 24(a) shows, for example, the status table T12A as of 1:20 on April 3rd, where the charge with charge number "20230402-7" is the second charge, and the first hour has elapsed at "1:30". After that, when the end time "1:30" passes, there is no new charging request, and charging continues as is for the next first hour. (b) of Figure 24 shows, for example, the status table T12A as of 1:40 on April 3rd, where the request number "20230402-7" has the charging status remaining "charging", the "estimated end time" stores the scheduled end time of the next first hour of charging, and the "number of charges" stores "2", which is the number of charges before the first hour elapsed, "1", plus "1". In this way, if there is no waiting state and processing continues when the scheduled end time passes, the record of the charging number that will pass the scheduled end time (here, "20230402-7") will move to the bottom, and the records of other charging numbers that are currently charging will move up one place.

[0071] 25, when the continuation process starts, a request is made to database 107A to make termination changes to the status table T12A. The termination changes involve moving the record of the charging number and changing the "scheduled termination time" and "number of charges" for the completed charging number. In response to this end change request, database 107A makes the change, and when an end change response is received from database 107A ("Yes" in S1392A), a charging end response is transmitted to AP server 108A (S1393A).

[0072] In the first embodiment A, the first hour of charging is terminated when there is a vehicle 1 in standby mode, so the amount of communication between the OCPP server 106A and the database 107A can be reduced compared to when charging is terminated when there is no vehicle 1 in standby mode.

[0073] <First embodiment B> The OCPP server 106 of the first embodiment determines whether charging is complete, as shown in FIG. However, if the vehicle 1 is equipped with an ECU (Electronic Control Unit) 11 that can communicate with the charging device 103 or the charging control device 105, it may be determined that charging is complete when a charging completion signal is received from the ECU 11 as shown in FIG. 26. The following mainly describes the changed parts as the first embodiment B.

[0074] 1. OCPP Server Configuration When charging is completed, as shown in FIG. 26, the OCPP server 106B receives a charging completion signal from the ECU 11, instructs the charging device 103 to complete charging, requests the database 107 to delete the status record indicating completion of charging, and outputs a charging completion response to the AP server 108. As in the first embodiment 1, the OCPP server 106B has a control unit 161, a communication unit 162 and a memory unit 163 working together to include a charging completion signal receiving unit from the ECU 11, a completion determination unit that determines that charging is complete when the charging completion signal is received, a charging completion signal transmitting unit, a charging normal completion signal receiving unit, a charging completion response output unit, a status record deletion request output unit, and a deletion response input unit.

[0075] 2. OCPP Server Flowchart In the OCPP server 106B, the control unit 161 executes a program, and the OCPP application performs various processes. The following description will be given with reference to the flowcharts of FIG. 15 and FIG. When the OCPP application starts, it performs step S124 from the start of Fig. 15, performs the processing of Fig. 27, and then proceeds to step S131 of Fig. 15. In this way, the flowchart of OCPP server 106B differs in the processing between steps S125 to S130. When the control unit 161 acquires the Kth scheduled end time etc. in step S125, it determines whether the Kth charge end time has passed (S126B). In step S126B, if it is determined that the end time has not passed ("No"), it is not finished and the process proceeds to step S130, and if it is determined that the end time has passed ("Yes"), the process performs termination processing (S128) and proceeds to step S130. In step S130, if K is not equal to the number of charging devices N, "1" is added to K (S129), and the process proceeds to step S125, and if the number of charging devices is equal to N, the process proceeds to step S127B. In step S127B, if a charging completion signal is received from ECU 11 ("Yes"), it is determined that charging is complete and completion processing is performed (S127), and the process proceeds to step S131; if a charging completion signal is not received ("No"), it is determined that charging is not complete and the process proceeds to step S131. In the first embodiment B, the OCPP server 106B does not determine charging completion based on charging time, so there is no need to manage the "number of charging attempts" in the status table T12B, and the amount of communication between the OCPP server 106B and the database 107 can be reduced.

[0076] <First embodiment C> As shown in FIG. 9, the OCPP server 106 of the first embodiment determines whether charging is complete and issues a completion instruction. However, the charging completion process may be performed on the charging device side. Hereinafter, the modified parts will be mainly described as the first embodiment C.

[0077] 1. Configuration (1)Charging device As shown in FIG. 28, when the charging device 103C receives the charging completion signal, it turns off charging itself and reports (transmits) this to the OCPP server 106C. The charging device 103 includes a charge completion signal receiving unit that receives a charge completion signal from the ECU 11 indicating that charging has reached full charge when charging is completed, by having the control unit 133, communication unit 134, and control unit work together, a charge completion unit that turns off charging upon receiving the charge completion signal, and a charge normal completion signal transmitting unit that transmits a charge normal completion signal to the OCPP server 106C indicating that charging has been completed successfully upon receiving the charge completion signal (or turning off charging).

[0078] (2) OCPP server configuration As shown in FIG. 26, when the OCPP server 106C receives a normal charging completion signal from the charging device 103C, it outputs to the database 107 a request to delete the status record (status table T12C) that completes charging and a request to change the charging request (power request table T11C), and receives responses to the deletion request and change request from the database 107. As in the first embodiment 1, the OCPP server 106C includes a normal charging completion signal receiving unit that receives a normal charging completion signal from the charging device 103C by having the control unit 161, communication unit 162, and memory unit 163 cooperate with each other when charging is completed, a charging completion response unit that responds to the AP server 108C that charging is completed upon receiving the normal charging completion signal, a status record deletion request output unit, a deletion response input unit, a charging request change request unit, and a charging request change response unit. In the first embodiment, as shown in FIG. 9, the request for changing the charging request is made by the AP server 108, but in the first embodiment C, it is made by the OCPP server 106C.

[0079] 2. Flowchart (1)Charging device In the charging device 103C, the control unit 133 executes a program, and a dedicated application performs various processes. The following description will be given with reference to the flowcharts of FIG. 14 and FIG. When the application starts, the process goes from start to step S104 in Fig. 14, and after the process in Fig. 29 is performed, the process goes to step S109 in Fig. 14. In this way, the flowchart of charging device 103C differs from that of Fig. 14 in steps 105 to S108. As shown in FIG. 29, when step S104 is completed, if the charging device 103C receives a charging completion signal from the ECU 11 in step S105C ("Yes"), it turns off charging to the vehicle 1 corresponding to the charging completion signal, sends a normal charging completion signal to the OCPP server 106C (S108C), and proceeds to step S109. On the other hand, if the charging completion signal has not been received in step S105C ("No"), the process proceeds to step S109.

[0080] (2) OCPP server The OCPP server 106C and the control unit 161 execute the program, and the OCPP application performs various processes. The following description will be given with reference to the flowcharts of FIG. 15 and FIG. When the OCPP application starts, it performs step S124 from the start of Fig. 15, performs the processing of Fig. 30, and then proceeds to step S131 of Fig. 15. In this way, the flowchart of OCPP server 106C differs in the processing between steps S125 to S130. When the control unit 161 acquires the Kth scheduled end time etc. in step S125, it determines whether the Kth charge end time has passed (S126C). In step S126C, if it is determined that the end time has not passed ("No"), it is not finished and the process proceeds to step S130, and if it is determined that the end time has passed ("Yes"), the process performs termination processing (S128) and proceeds to step S130. In step S130, if K is not equal to the number of charging devices N, "1" is added to K (S129), and the process proceeds to step S125, and if the number of charging devices is equal to N, the process proceeds to step S127C.

[0081] In step S127C, if a normal charging completion signal is received from charging device 103C ("Yes"), it is determined that charging is complete, completion processing is performed (S127C), and the process proceeds to step S131; if a normal charging completion signal is not received ("No"), it is determined that charging is not complete, and the process proceeds to step S131. As shown in FIG. 31, the completion process (S127C) requests the database 107 to delete the status record of the charging number of the vehicle 1 for which charging is completed (S1271C), and when a deletion response is input ("Yes" at S1272C), the process proceeds to step S1273C. In step 1273C, a request is made to the database 107 to change the charging request for the charging number of the vehicle 1 for which charging is to be completed, and when a change response is input ("Yes" in S1274C), the process proceeds to step S1278, where a charging completion response is output to the AP server 108C. In the first embodiment C, the OCPP server 106C does not determine charging completion based on charging time, so there is no need to manage the "number of charges" in the status table T12C. Furthermore, there is no need to send and receive charging completion signals, etc., between the OCPP server 106C and the charging device 103C, which reduces the amount of communication between the OCPP server 106C and the charging device 103C.

[0082] <First embodiment D> 1. Overall structure In the charging system 101 of the first embodiment, the determination of whether or not the vehicle 1 requested to be charged can be charged is made by comparing the number of vehicles being charged with the maximum number of vehicles. In other words, the determination is made based on whether or not the number of vehicles being charged plus the number of vehicles that would be charged if the newly requested vehicle 1 were charged is less than the maximum number. In the charging system of first embodiment D, the charging power of vehicle 1 is registered, and assuming that vehicle 1 that has requested charging is charged with the current charging power usage, if the total charging power usage is less than the maximum power usage, vehicle 1 that has requested charging is charged, and if the total charging power usage is equal to or greater than the maximum power usage, charging of vehicle 1 that has requested charging is put on hold. This allows a plurality of vehicles 1 with different charging power levels to be efficiently charged within the maximum power usage. First embodiment D will be described below, focusing on the differences from first embodiment 1.

[0083] 2.Each part (1) Database The status table T12D of the first embodiment D has a new item, "power usage," as shown in Fig. 32(a). In the "power usage" field, for example, "20" or "15" is stored. Note that "20" is 20 kW, and the maximum power usage of the charging device 13 in this case is 60 kW. That is, in the first embodiment 1, three vehicles 1 equivalent to 20 kW can be charged, and even if the charging power for all three vehicles is 15 kW, only three vehicles can be charged. In contrast, in the first embodiment D, up to four vehicles 1 with a 15 kW capacity can be charged. As shown in FIG. 32(b), database 107D (not shown) stores customer information table T13D having the fields "customer ID," "connector ID," and "charging power." For example, a customer with customer ID "AAA" is charged with a charging power of "20 (kW)" using connector 131 with connector ID "1." In the first embodiment D, the charging start instruction includes the "connector ID" and "power usage," and charging device 103D (not shown) that receives the charging start signal is configured to charge using 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 108D accepts customer information through the user's operation on the mobile terminal 3 and registers the customer information in the customer information table T13D of the database 107D.

[0084] (2) AP server In the AP server 108D, the control unit 181 executes a program, and the AP application performs various processes, as in the first embodiment, but step S173 in FIG. 22 is different. When the user operates to start charging, the AP server 108D creates a new charging request in the database 107D (S170 to S171 in FIG. 22), and then, as shown in FIG. 27, requests and obtains from the database 107D the status ("charging state" and "power usage") and the "power usage" of the "customer ID" for which the new charging request has been made (S172D). In step S173D of (a) in Figure 33, the AP server 108D adds up the "power usage" of all vehicles 1 (charging numbers) currently being charged and the "power usage" of the new charging request to calculate the total power usage of all vehicles 1 when charging, including the vehicle 1 for the new charging request, and determines that charging is possible if the total power usage is less than the maximum power usage ("Yes"), and determines that charging is not possible if the total power usage is greater than or equal to the maximum power usage ("No"). If it is determined that charging is possible, the process proceeds to step S174 in Fig. 22, and if it is determined that charging is not possible, the process proceeds to step S178 in Fig. 22. Note that the processes thereafter are the same as those in the first embodiment, and therefore a description thereof will be omitted. In this way, the AP server 108D includes a total power usage acquisition (calculation) unit that acquires (calculates) the total power usage, which is the sum of the power usage of all vehicles 1 currently being charged and the power usage of the newly requested vehicle 1, and a chargeability determination unit that determines whether charging is possible using the total power usage and the maximum power usage.

[0085] (3) OCPP server In the OCPP server 106D, the control unit 161 executes a program, and the OCPP application performs various processes, as in the first embodiment, but step S134 in FIG. 15 is different. The OCPP server 106D starts the OCPP application and, after completing processing up to step S133, obtains all "charging status" currently being charged and the I-th waiting "power usage" as shown in (b) of Figure 33. In S1341D, the acquired "power usage" of all vehicles 1 (charging numbers) currently charging and the "power usage" during the I-th waiting period 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"), and if it is greater than or equal to the maximum power usage, it is determined that charging is not possible ("No"). If it is determined that charging is possible, the process proceeds to step S135 in Fig. 15, and if it is determined that charging is not possible, the process proceeds to step S136 in Fig. 15. Note that the processes thereafter are the same as those in the first embodiment, and therefore description thereof will be omitted. In this way, the OCPP server 106D includes a total power usage acquisition (calculation) unit that acquires (calculates) the total power usage, which is the sum of the power usage of all vehicles 1 currently being charged and the power usage of the newly requested vehicle 1, and a chargeability determination unit that determines whether charging is possible for a waiting vehicle 1 based on the total power usage and the maximum power usage.

[0086] In the first embodiment D, the charging device 103 can also be controlled so as not to be overloaded. Moreover, the OCPP server 106D can also handle differences in charging power caused by differences in the capacity of the battery of the vehicle 1, by instructing the charging device 103 to include the power to be used during charging in the charging start signal.

[0087] Second Embodiment In the first embodiment, when a new charging request is made that exceeds the maximum power usage (number of vehicles that can be charged) for charging multiple vehicles simultaneously, the charging power is not changed and the new charging request is not charged until charging of the vehicle currently being charged is completed or ended, and the charging state is kept on standby. In the second embodiment, when a new charging request is made that exceeds the maximum power usage for charging multiple vehicles simultaneously, the charging power is reduced and the number of vehicles that can be charged is increased, and the newly requested charging is carried out; when the number of vehicles that can be charged is increased so that the charging power for one vehicle is below the minimum power, the system waits until the charging of the vehicle currently being charged is completed or finished before carrying out the new charging request. In the second embodiment, the charging time is also set. In the device of the second embodiment, if the device has the same or similar configuration as the device of the first embodiment, the description and drawings thereof will be omitted. The reference numerals may be the same as those of the first embodiment, or the reference numerals of the first embodiment may be in the 100s, while the reference numerals of the second embodiment may be in the 200s. For example, the reference numeral "101" is used for the charging system of the first embodiment, while the reference numeral "201" is used for the charging system of the second embodiment, and by changing the reference numerals in Figures 1 and 3 to the 200s, the diagrams will also show the charging system 201 of the second embodiment. Furthermore, the contents described in the first embodiment can be applied to the second embodiment, and even if the same devices are denoted by different reference numerals in the first and second embodiments, they may have the same configuration.

[0088] <Second embodiment 1> 1. Overall structure The charging system 201 of the second embodiment 1 differs from the charging system 101 of the first embodiment 1 in that the charging power can be changed and the charging device 203 performs charging completion processing by itself, and the differences will mainly be described. The charging system 201 of the second embodiment 1 includes a charging device 203 and a charging control device 205 (not shown, see FIG. 1), similarly to the first embodiment 1. In the charging system 201, a maximum power usage for simultaneous charging of a plurality of vehicles 1 is set, and if charging a vehicle for which a new charging request has been made exceeds the maximum power usage, the charging power is reduced for the vehicle currently being charged and the vehicle for which a new charging request has been made. In other words, the maximum power usage when charging simultaneously is set in advance, and if the total power usage (also called "total power usage") when charging the vehicle 1 that has requested charging with the first charging power is less than the maximum power usage, the vehicle 1 that has requested charging is charged with the first charging power (this charging is called "normal charging"), and if the total power usage is equal to or greater than the maximum power usage, all vehicles 1 that are being charged, including the vehicle 1 that has requested charging, are charged with a second charging power that is lower than the first charging power, within the maximum power usage (this charging is called "adjusted charging"). In addition, the charging time for one charging is preset to a first hour regardless of the charging power, and when one charging is completed, if there is a vehicle 1 in standby state, the vehicle goes into standby state, and if there is no vehicle 1 in standby state, charging for the first hour is started (continued). It should be noted that these specific forms are provided for the purpose of explaining the embodiments, and the present invention is not limited to these forms.

[0089] 2.Each part Each device constituting the charging system 201 will be described below. (1)Charging device The charging device 203 includes a circuit section 232, a control section 233, and a communication section 234 (see FIG. 1). The control unit 233 instructs the circuit unit 232 to start charging (ON) with the instructed charging power for the connector 131 via the communication unit 234 from the charging control device 205, or to end and complete charging (OFF), etc. As shown in Figure 39, the charging device 203 performs normal charging or adjusted charging for a new vehicle 1 in accordance with a charging start / power change signal from the OCPP server 206, or changes the charging power and performs adjusted charging for another vehicle 1 that is currently being charged in response to a new charging request. As shown in FIG. 43, the charging device 203 changes the charging power during charging in accordance with the power change signal from the OCPP server 206, and responds to the OCPP server 206 with the change. In addition, as shown in Figure 40, the charging device 203 is connected to the ECU 11 on the vehicle 1 side, and when it receives a charging completion signal from the ECU 11, it completes charging (normal charging or adjusted charging) to the vehicle 1 and sends a normal charging completion signal to the OCPP server 206 indicating that charging has been completed successfully. In this way, the charging device 203 includes a charging start / power change signal receiving unit that receives a charging start / power change signal (which may include a start preparation signal), a response signal transmitting unit that transmits a response signal indicating that charging has started or that the charging power has been changed, a charging completion signal receiving unit that receives a charging completion signal from the ECU 11 etc., a charging normal completion signal transmitting unit that transmits a charging normal completion signal, a charging start signal receiving unit that receives a charging start signal that starts charging of a waiting vehicle 1 and a response signal transmitting unit that transmits the response signal, a power change signal receiving unit that receives a power change signal that changes the charging power, and a power change response signal transmitting unit that transmits a power change response signal that indicates that the power has been changed.

[0090] (2) Mobile devices The mobile terminal 3 has the same configuration as that of the first embodiment 1 (see FIG. 2). The user registers user information such as a user ID for identifying the user and a connector ID indicating the connector 131 to be used via a mobile application. The control unit 233 sends a charging request to the AP server 208 via the mobile application, and displays on the touch panel unit 36 ​​a charging start report, a charging completion report, a charging standby report, and a report that the charging power is being adjusted (hereinafter referred to as a "power adjustment report").

[0091] (3) Charging control device The charging control device 205 includes an OCPP server 206 that functions as a first server, a database 207, and an AP server 208 that functions as a second server (see FIG. 3). (3-1) Database The database 207 includes a control unit 271 , a storage unit 273 , and a clock 275 . The storage unit 273 stores, for example, a charge request table T21, a status table T22, and the like. The charging request table T21 stores data such as "charging number," "connector ID," "charging result," "request date and time," and "charging completion date and time" as in the first embodiment (see FIG. 4(a)). As shown in FIG. 34, the status table T22 stores data such as the "charging number," "connector ID," "charging status," "estimated end time" indicating the scheduled end time of the first hour of charging, and "charging power" indicating the power used by the vehicle 1 during charging. Here, the maximum power usage is set to, for example, 50 kW, and the charging power is, for example, "20" or "15." "20" in FIG. 34(a) indicates charging at the set power (100%), while "15" in FIG. 34(b) indicates a case where the charging power is adjusted, and the adjusted adjusted power is lower than the power during normal charging. In this example, the adjusted power is set to 75% of the set power. Here, we assume only one regulated power of 75%, but if charging at 75% exceeds the maximum power usage, charging can be performed at 50% of the set power (in this case, 10 kW). (a) of Figure 34 shows that normal charging is being performed because the total charging power of the two vehicles is 40 kW, which is less than the maximum power usage, as shown in Figure 37, and the first hour of charging is scheduled to end at 20:00 for charging number "20230401-6" and at 20:30 for charging number "20230401-7".

[0092] Figure 34(b) shows the state of Figure 34(a) in which, in response to a new charging request for charging number "20230401-8," a record for charging number "20230401-8" is added to status table T22, and if vehicle 1 is charged normally, the total power usage, including normal charging for charging numbers "20230401-6" and "20230401-7," will be 60 kW, which is greater than the maximum power usage. Therefore, this shows the state in which adjusted charging with a charging power of 15 kW is being performed for these three vehicles 1, and the charging power has been changed from "20" to "15."

[0093] As shown in FIG. 37, in the state of FIG. 34(b), a new charging request with charging number "20230401-9" is received, and adjustment charging is performed for this charging request. When adjustment charging with charging numbers "20230401-6", "20230401-7", and "20230401-8" is also performed, Since the total power usage is 60 kW, which is greater than the maximum power usage, a record for charging number "20230401-9" is added to status table T22 and the device is in standby state (shown as "Waiting" in the table), as shown in Figure 35(a). As shown in FIG. 38, a new record for the new charging number "20230401-9" is added to the bottom of the charging request table T21, with "20230401-9" as the charging number, "3" as the connector ID, "Incomplete" as the charging result, and "20230401:1915" as the request date and time stored.

[0094] As shown in Figure 37, charging for charging number "20230401-6" ends at 20:00, and instead charging number "20230401-9," which was on standby, undergoes adjusted charging, as shown in (b) of Figure 35. If the charging for charging number "20230401-6," which has finished charging, is assumed to be adjusted charging, and the adjusted charging for charging numbers "20230401-7," "20230401-8," and "20230401-9," which are already undergoing adjusted charging, is added, the total power usage exceeds the maximum, so it is moved to the lowest record and is in standby state (shown as "Waiting" in the table).

[0095] As shown in Figure 37, charging for charging number "20230401-7" ended (completed) at 20:30, and instead charging number "20230401-6", which was on standby, underwent adjusted charging, and in status table T22, as shown in (a) of Figure 36, the charging status is changed from "on standby" to "charging" and the charging power is changed to "15". In addition, for the completed charging number "20230401-7", as shown in Figure 38, in the charging request table T21, the "charging result" is changed from "incomplete" to "completed", "20230401:2030" is stored in the "charging completion date and time", and the record is deleted from the status table T22 as shown in (a) of Figure 36.

[0096] Subsequently, as shown in Figure 37, when charging of charging number "20230401-6" is completed at 21:30 due to full charge, the number of vehicles being charged becomes two, with charging numbers "20230401-8" and "20230401-9." The total power usage in normal charging becomes lower than the maximum power usage, and normal charging begins from 21:30, and the charging power changes from "15" as shown in Figure 36(b) to "20" as shown in Figure 36(c).

[0097] The control unit 271 includes a CPU, ROM, RAM, etc., and creates or modifies a new charging request in the charging request table T21, or registers, modifies, or deletes a request in the status table T22 in response to a request from the OCPP server 206 or the AP server 208. When the control unit 271 makes a change to the tables T21 and T22 in response to a request, it responds to the server that made the request.

[0098] (3-2) OCPP Server The OCPP server 206 includes a control unit 261, a communication unit 262, and a storage unit 263, and executes an OCPP application (see FIG. 3).

[0099] 39, when the OCPP server 206 receives a charging start / power change instruction from the AP server 208, it transmits a charging start / power change signal to the charging device 203, requests the database 207 to start registration / power change, and when charging starts normally, outputs a charging start response to the AP server 208. Note that "charging" here includes "normal charging" and "adjusted charging." As in the first embodiment, the start registration is performed by registering the "charging number," "connector ID," "scheduled end time," and "charging power" of a new charging request that is determined to be chargeable by the charging determination in a new record in the status table T22, as in the first embodiment.

[0100] When the charging determination determines that a new charging request cannot be charged with normal charging but can be charged with adjusted charging, the "charging power" during charging in the status table T22 is changed to the second charging power. For example, in the state shown in FIG. 34(a), a new charging request (charging number "20230401-8") is made, and normal charging is changed to adjusted charging to charge three vehicles, as shown in FIG. 34(b). The signal from the OCPP server 206 instructing to start charging and change power includes the "charging number," "connector ID," and "charging power." If no power change is required, the signal may include only information about a new charging request, or may include all "charging numbers," "connector IDs," and "charging power" currently being charged, and change all charging power (with no change to existing data). In this way, the OCPP server 206 has a charge start / power change instruction input unit, a charge start / power change signal transmission unit, a normal charge start signal reception unit, a charge start response output unit, a start registration / power change request output unit, and a start registration / power change response input unit, by having the control unit 261, communication unit 262, and memory unit 263 work together (see first embodiment 1). In FIG. 39, the display of transactions is omitted.

[0101] As shown in Figure 40, when the OCPP server 206 receives a normal charging completion signal from the charging device 203 indicating that charging of the vehicle 1 (charging request) being charged has been completed, it requests the database 207 to delete the status record of the charging request, and also sends a charging completion response indicating that charging has been completed to the AP server 208. For example, in the state shown in Figure 35(b), charging number "20230401-7" is undergoing adjusted charging, but as shown in Figure 37, charging is completed at 20:30, and the record for charging number "20230401-7" is deleted as shown in Figure 36(a). Note that by receiving a normal charging completion signal from the charging device 203, the amount of processing can be reduced compared to the OCPP server 106 in the first embodiment. In this way, the OCPP server 206 has a normal charging completion signal receiving unit that receives a normal charging completion signal from the charging device 203 by having the control unit 261, the communication unit 262, and the memory unit 263 work together, a charging completion response output unit that outputs a charging completion response to the AP server 208 when a normal charging completion signal is received from the charging device 203, a status record deletion request output unit that outputs a status record deletion request to the database 207, and a deletion response input unit to which the deletion response is input from the database 207.

[0102] As shown in Figure 41, the OCPP server 206 determines whether charging of the charging request (vehicle) has ended, and if it determines that charging has ended, it sends a charging end signal to the charging device 203 to end charging, requests the database 207 to change the "charging status" etc. in the status table T22 to end the charging, and responds to the AP server that charging has ended. For example, in the state shown in Figure 35(a), charging number "20230401-6" is undergoing adjusted charging, but as shown in Figure 37, when charging ends at 20:00, charging number "20230401-6" is moved to the lowest record, the charging status is changed to "standby," and the charging power is left blank, as shown in Figure 35(b). In this way, the OCPP server 206 has a charging completion determination unit, a charging completion signal transmission unit, a charging normal completion signal receiving unit, a charging completion response output unit, a completion change request output unit, and a completion change response input unit, by having the control unit 261, the communication unit 262, and the memory unit 263 work together. The process at the time of charging termination is the same as that in the first embodiment, and an estimated termination time acquisition request output unit and an acquisition response input unit are also provided to determine the termination of charging.

[0103] As shown in Fig. 42, the OCPP server 206 determines whether charging is possible in response to a standby charging request, and if charging is possible, it sends a charging start signal to the charging device 203, requests the database 207 to change the "charging state" and "charging power" in the status table T22 to start, and responds to the AP server 208 that charging has started. For example, in the state shown in Fig. 35(a), charging number "20230401-9" is on standby, but as shown in Fig. 37, adjusted charging will begin at 20:00, and as shown in Fig. 35(b), the charging state of charging number "20230401-9" is changed to "charging," the scheduled end time is changed to "22:00," and the charging power is changed to "15." In this way, the OCPP server 206 has a charging possibility determination unit, a charging start signal transmission unit, a charging normal start signal reception unit, a charging start response output unit, a start change request output unit, and a start change response input unit, by having the control unit 261, communication unit 262, and memory unit 263 work together. As in the first embodiment, the process of determining whether charging is possible in response to a charging request during standby also includes a charging state acquisition request output unit and an acquisition response input unit to determine whether charging is possible.

[0104] As shown in Figure 43, when charging is completed or terminated, the OCPP server 206 determines whether the charging power can be changed to the first charge, and if the change is possible, sends a power change request to the charging device 203 or requests the database 207 to change the "charging power" in the status table T22. For example, in the state of Figure 36(a), adjusted charging is being performed on three vehicles 1, but as shown in Figure 37, charging for charging number "20230401-6" is completed at "21:30" and the charging is changed from adjusted charging to normal charging, and as shown in Figure 36(c), the charging power for charging numbers "20230401-8" and "20230401-9" is changed to "20". In this way, the OCPP server 206 has a power (changeable) determination unit that determines whether the charging power can be changed to the first charge by having the control unit 261, communication unit 262, and memory unit 263 work together, a power change signal transmission unit that transmits a power change signal to the charging device 203 if the power can be changed, a power change response signal receiving unit that receives a signal from the charging device 203 indicating that the change has been made, a power change request output unit that requests the database 207 to change the ``charging power'' in the status table T22, and a power change response input unit that receives a change response from the database 207. The power change determination here is made based on the "charging state" and "charging power" in the status table T22, so the system is also provided with a charging state etc. acquisition request output unit that requests the database 207 to acquire status data such as "charging state", and an acquisition response input unit that receives responses to the acquisition of these charging states etc. The charge change instruction utilizes transaction management, and the response signal (change transaction) output from the charging device 203 to the power change signal (change transaction) is also a "power change response signal" indicating that the power has been changed successfully.

[0105] (3-3) AP Server The AP server 208 includes a control unit 281, a communication unit 282, a storage unit 283, and a clock unit 284 (see FIG. 3). The control unit 281 includes a CPU, a ROM, a RAM, etc., and processes AP applications by the CPU executing programs stored in the storage unit 283. The AP server 208 receives charging requests from the mobile terminal 3 and transmits charging start reports, charging completion reports (see Figure 40), charging standby reports (see Figure 8), charging end reports (see Figure 41), charging start reports (see Figure 42), power change reports (see Figure 43), etc. In this way, by having the control unit 281, the communication unit 282, and the memory unit 283 work together, the AP server 208 provides the mobile terminal 3 with a charging request receiving unit, a charging start report transmitting unit, a charging completion report transmitting unit, a charging standby report transmitting unit, a charging end report transmitting unit, a charging start report transmitting unit, and a power change report transmitting unit.

[0106] 39, when a new charging request is made, the AP server 208 determines whether charging is possible for the vehicle 1 that made the charging request. Here, assuming that the vehicle 1 that made the charging request is charged with the same charging power as the vehicle 1 that is currently being charged (if no vehicle is being charged, the charging power is normal charging), if the total power usage of the vehicle 1 that made the charging request and the vehicle 1 that is being charged is less than the maximum power usage, the AP server 208 determines that charging is possible with the same charging power as the vehicle 1 that is currently being charged (normal charging or adjusted charging). On the other hand, if the total power usage is equal to or greater than the maximum power usage, and the charging power currently being charged is the first charging power, the AP server 208 determines that charging is possible with the second charging power (adjusted charging) if the total power usage when charging the vehicle 1 that made the charging request and all of the vehicles 1 that are being charged simultaneously with the second charging power is less than the maximum power usage, and if the charging power currently being charged is the second charging power, the AP server 208 determines that charging for the new charging request is not possible (if not possible, the AP server 208 enters a waiting state). The AP server 208 outputs a charging start / power change instruction (see Figure 39) to the OCPP server 206 when it determines that charging is possible, and receives a charging start response (including normal charging and adjusted charging, see Figure 39), a charging completion response (see Figure 40), a charging end response (see Figure 41), a charging start response (see Figure 42), a power change response (see Figure 43), etc. In response to a new charging request, when charging is performed without going into standby mode, there are normal charging and adjusted charging, and the charging start / power change instruction includes an instruction to change the charging power. In this way, by having the control unit 281, communication unit 282, and memory unit 283 work together, the AP server 208 is provided with a charging determination unit and a charging start / power change instruction output unit, a charging start response input unit, a charging completion response input unit, a charging end response input unit, a charging start response input unit, and a power change response input unit for the OCPP server 206.

[0107] The AP server 208 requests the database 207 to create a charging request or acquire a charging status when a charging request is made, requests the database 207 to change the charging request when charging is completed, and receives responses to these requests. In this way, the AP server 208 has, with the database 207, a charging request creation request output unit, a creation response input unit, a charging status acquisition request output unit, an acquisition response input unit, a charging request change request output unit, and a change response input unit, by making the control unit 281, the communication unit 282, and the storage unit 283 work together.

[0108] 3. Sequence The processing that differs from the first embodiment will be described. Specifically, the processing for a new charging request, the processing for determining whether charging is possible for a new request and putting the device into standby mode when the result is that charging is not possible, the processing for completing the first hour of charging, and the processing for starting charging from standby mode are the same or approximately the same as in the first embodiment 1. (1) Charge determination (1-1) Normally rechargeable The charging request for charging number "20230401-7" in FIG. 38 will be described. When a charging request is made, the AP server 208 requests the database 207 to acquire the charging status (including charging power), as shown in Fig. 39. In response to this request, the database 207 acquires from the status table T22 that charging is in progress, the charging number is "20230401-6", and the charging power is "20", and responds to the AP server 208. Note that the charging power "20" is the power for normal charging. The AP server 208 assumes that the new charging request will be charged at the same charging power of "20" kW as the current charging, and the total power usage including the charging power of charging number "20230401-6" will be 40 kW, which is less than the maximum power usage of "50 kW." Therefore, it determines that charging is possible for the vehicle 1 with charging number "20230401-7," which is the new charging request. When it is determined that normal charging is possible, the AP server 208 transmits a charge start / power change instruction for normal charging to the OCPP server 206, as shown in Fig. 39. The charge start / power change instruction here includes the charge number "20230401-6" and the charging power "20". In response to this, the OCPP server 206 instructs the charging device 203 to perform (normal) charging on the vehicle with the connector ID corresponding to the charging number "20230401-6." The subsequent steps are the same as those in the first embodiment.

[0109] (1-2) Adjustment charging The charging request for charging number "20230401-8" in FIG. 38 will be described. When charging number "20230401-8" requests charging, charging numbers "20230401-6" and "2023-0401-7" are performing normal charging, as shown in FIG. When a new charging request is made, the AP server 208 requests the database 207 to acquire the charging status (including charging power). In response to this request, the database 207 acquires from the status table T22 that charging is in progress, the charging numbers are "20230401-6" and "20230401-7", and the charging power is "20", and responds to the AP server 208.

[0110] If the AP server 208 charges the new charging request ("20230401-8") at 20 kW, the same as the charging power currently being charged, the total power usage for the three vehicles will be 60 kW, which is greater than the maximum power usage of 50 kW. Next, if the new charging request ("20230401-8") and the charging request currently being charged are charged at 15 kW, which is lower than the current charging power, the total power usage for the three vehicles will be 45 kW, which is less than the maximum power usage of 50 kW. Therefore, it is determined that adjusted charging is possible for vehicle 1 with charging number "20230401-8", which is a new charging request, and the charging power for charging numbers "20230401-6" and "20230401-7" is changed to "15".

[0111] When it is determined that charging with a change in charging power is possible, the AP server 208 transmits a charge start / power change instruction for adjusted charging to the OCPP server 206, as shown in Fig. 39. The charge start / power change instruction here includes the charging numbers "20230401-6," "20230401-7," and "20230401-8" and the charging power "15." In response to this, the OCPP server 206 transmits a charging start / power change signal to the charging device 203 to perform adjusted charging on the vehicles with connector IDs corresponding to the charging numbers "20230401-6", "20230401-7", and "20230401-8". The charge start / power change instruction has a transaction function and is a remote start transaction. The charge start instruction includes the "connector ID" of the charging target, including the new charging request, and its "charging power" data. The charging device 203 checks the connection of the target "connector ID" and outputs a start preparation response signal to the OCPP server 206 indicating that the connection is established. In response to this, the OCPP server 206 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 203 is connected, and requests the database 207 to register the start of adjusted charging and change the charging power.

[0112] In response to the start registration and power change request, the database 207 stores a new charging request ("20230401-8"), "charging status," "scheduled end time," and "charging power" in a new record in the status table T22 as start registration, and changes the charging power of the charging numbers "20230401-6" and "20230401-7" that were in charging to "15" as power change. After completing the registration and change, the database 207 responds with start registration and power change to the OCPP server 206. The OCPP server 206 outputs a charging start / power change signal to the charging device 203, and the charging device 203 starts (or continues) charging the three vehicles 1 with charging numbers "20230401-6", "20230401-7", and "20230401-8" with a charging power of "15", and outputs a response signal (normal charging start signal) to the OCPP server 206 indicating that adjusted charging has started. The charging start response signal is a remote start transaction. When the OCPP server 206 receives the charge start response signal, it transmits a charge start response for adjusted charging to the AP server 208, and in response to this, the AP server 208 notifies the portable terminal 3 that adjusted charging has started.

[0113] (2) Charging completed The completion of charging for charging number "20230401-6" in FIG. 37 will be described. As shown in FIG. 40, when the charging device 203 receives a charging completion signal from the ECU 11, it completes charging of the target vehicle 1 with connector ID "1" and transmits a normal charging completion signal to the OCPP server. In response to this, the OCPP server 206 requests the database 207 to delete the record for charging number "20230401-6" as shown in (b) of Figure 36, since there is a record for charging number "20230401-6" in the status table T22 as shown in (a) of Figure 36.When the database 207 deletes the record, it responds to that effect to the OCPP server 0206. The OCPP server 206 responds to the AP server 208 that charging is complete, and the AP server 208 reports charging completion to the portable terminal 3 and requests the database 208 to change the charging result and charging completion date and time for the corresponding charging number in the charging request table T21 for charging number "20230401-6." The database 207 changes the "charging result" of the record with the charging number "20230401-6" in the charging request table T21 to "completed" and the charging completion date and time to "20230401:2130" as shown in FIG.

[0114] (3) Power change The charging power may be changed in the following cases: when a new charging request is made while normal charging is in progress, the charging power is changed to the second charging power and adjusted charging is performed for the vehicle for the new charging request and for vehicle 1 undergoing normal charging; or when adjusted charging is in progress, charging of vehicle 1 being charged is completed, and the charging power is changed to the first charging power and normal charging is performed for the remaining vehicles being charged. The change to adjusted charging when a new charge request is made is made by the AP server 208 as shown in FIG. 39, and the change to normal charging when charging is completed is made by the OCPP server 206 as shown in FIG. Here, the change at the time of completion of charging will be explained assuming that charging number "20230401-6" in FIG. 36 has completed charging.

[0115] The OCPP server 206 determines the power based on the number of vehicles being charged, in this case the number whose charging state is "charging," and the charging power. As shown in FIG. 43, the OCPP server 206 requests the database 207 to acquire the charging status including the charging status and charging power, and acquires it. Specifically, as shown in FIG. 36(b), two charging units with charging numbers "20230401-8" and "20230401-9" whose charging status is "charging" and charging power "15" are acquired. The OCPP server 206 calculates the total power usage when the charging power of the acquired charging number is set to "20" (here, 40 kW), and since the total power usage is less than the maximum power usage, charging is possible within the maximum power usage even if changing from adjusted charging to normal charging. In this way, when it is determined that the power can be changed, a power change signal is transmitted to the charging device 203. Specifically, a power change signal including the connector IDs (here, "6" and "3") of the charging numbers "20230401-8" and "20230401-9" and the charging power (here, "20") is transmitted. In response to this, the charging device 203 performs normal charging with a charging power of "20" for the vehicles with connector IDs "6" and "3", and transmits a power change response signal to the OCPP server 206. The transaction function is used to send and receive the power change signal and the power change response signal.

[0116] When the OCPP server 206 receives the power change response signal from the charging device 203, it requests a power change from the database 208. Specifically, it requests a change in the charging power for the charging numbers "20230401-8" and "20230401-9" in the status table T22. When the database 207 changes the "charging power" of the records with charging numbers "20230401-8" and "20230401-7" in the status table T22 to "20" as shown in (c) of Figure 36, it outputs a power change response to the OCPP server 206 indicating that the change has been made. When the OCPP server 206 receives the power change response from the status table T22, it outputs a power change response to the AP server 208 indicating that the power has been changed, and the AP server 208 reports the power change to the mobile terminal 3.

[0117] 4. Flowchart The processing of the control unit of each device will be described. Note that the same or substantially similar processing as in other embodiments will be assigned the same step numbers, and their description will be omitted. Also, different step numbers may be used for the same processing.

[0118] (1)Charging device The processing of the control unit 233 of the charging device 203 will be described with reference to FIG. When the program starts, the control unit 233, upon receiving a start preparation signal from the OCPP server 206 ("Yes" in the figure), confirms the connection of vehicle 1 with the "connector ID" included in the start preparation signal, and outputs a response signal (start preparation response signal) to the OCPP server 206 indicating the confirmation (S102). Thereafter, when a charging start / power change signal is received from the OCPP server 206 ("Yes" in S203), charging is turned on for the vehicle 1 with the new "connector ID" included in the charging start / power change signal and the vehicle 1 currently being charged using the "charging power" included in the signal, and a response signal is sent to the OCPP server 206 (S204). Note that charging of a vehicle 1 that is currently being charged may continue as is without changing the charging power, or may change the charging power and continue as is. If there are no vehicles 1 currently being charged, charging is turned on for the vehicle 1 making a new charging request at the power value of "charging power."

[0119] In step S205, if a charging completion signal is received from ECU 11 ("Yes" in the figure), charging of vehicle 1 with the "connector ID" included in the charging completion signal is turned off, and a signal indicating that charging has been completed (charging normal completion signal) is sent to OCPP server 206 (S206). If the charging completion signal has not been received in step S205 ("No"), the process proceeds to step S109.

[0120] In steps S109 to S112, the same processes as in the first embodiment are performed, and the process proceeds to step S207. In step S207, if a power change signal is received from the OCPP server 206 ("Yes" in the figure), the vehicle 1 currently being charged is changed to the "charging power" included in the signal, charging continues, and a signal indicating that the charging power has been changed (power change response signal) is sent to the OCPP server 206 (S208), and the process proceeds to step S101.

[0121] (2) OCPP server In the OCPP server 206, the OCPP application performs various processes as a result of the control unit 261 executing a program. The following will explain this process using the flowcharts in FIGS. When the OCPP application is started (start in FIG. 45), it is determined whether a charge start / power change instruction has been input from the AP server 208 (S220). If a charge start / power change instruction has been input ("Yes"), the charge start / power change process (S221) is performed and the process proceeds to step S223; if no instruction has been input ("No"), the process proceeds to step S223. In step S223, it is determined whether a normal charging completion signal has been received from the charging device 203. If it has been received, completion processing (S224) is performed and the process proceeds to step S225; if it has not been received ("No"), the process proceeds to step S225. Thereafter, the end determination end process, the charge determination charge process, and the power determination change process are performed (S225, S226, S227), and the process proceeds to step S220.

[0122] (2-1) Charging start and power change processing (S221) The charging start and power change processing will be explained mainly with reference to FIG. 46 and FIG. 39 showing the sequence. The charging start / power change process S221 starts when a charging start / power change instruction is input, and a start preparation signal is sent to charging device 203 (S1221). When a response signal is received from charging device 203 ("Yes" at S1222), in step S1223, if the response signal is a normal signal ("Normal" at S1223), a start registration / power change request is made to database 207 in status table T22 (S2224). When a start registration / power change response is received from database 207 ("Yes" at S2225), the process proceeds to step S2226. In step S2226, a charging start / power change signal is transmitted to the charging device 203. This signal includes at least the "connector ID" of the vehicle 1 that will newly start charging, and the "connector ID" and "charging power" of the vehicle 1 whose charging power will be changed. In response to this, the charging device 203 turns on charging for the vehicle 1 with the ``connector ID'' of the new charging request and the vehicle 1 currently being charged using the ``charging power'' included in the signal, and sends a response signal to the OCPP server 206 indicating that charging has started and the power has been changed. In step S2227, if a response signal is received from the charging device 203 ("Yes"), a charging start response indicating that charging has started normally (and the charging power has been changed normally) is output to the AP server 208 (S2228), and the process proceeds to step S223 in FIG. 45. In addition, in step S1223, if the received signal is an error signal ("Error"), an error indicating that the vehicle 1 and the connector 131 are not electrically connected is output to the AP server 208 (S1229), and the process proceeds to step S223 in Figure 45.

[0123] (2-2) Completion process (S224) The completion process will be explained mainly with reference to FIG. 47 and FIG. 40 showing the sequence. Completion processing S224 starts when a normal charging completion signal is received from charging device 203, and requests database 207 to delete the status record in status table T22 (S2241). When a deletion response indicating that deletion has been completed is received from database 207 ("Yes" in S2242), a charging completion response indicating that charging has been completed normally is output to AP server 208 (S2243), and processing proceeds to step S225 in FIG. 45.

[0124] (2-3) End determination end process (S225) The end determination end processing will be described mainly with reference to FIG. 48 and FIG. 41 showing the sequence. When the process starts, in step S123, the number of vehicles to be charged N is obtained from the database 207, the variable "K" is set to "1" (S124), and the scheduled end time of the Kth charging number is obtained (S2251). Next, a termination determination is made based on the current time and the scheduled termination time (S2252). Specifically, if the scheduled termination time has passed ("Yes"), it is determined to be "terminated," and the termination process (S128) shown in Fig. 19 is performed, and the process proceeds to step S130. In step S130, if K is not equal to the number of charging devices N, "1" is added to K (S129), and the process proceeds to step S2251, and if the number of charging devices is equal to N, the process proceeds to step S226.

[0125] (2-4) Charging judgment and charging process (S226) The charging determination charging process will be described mainly with reference to FIG. 49 and FIG. 42 showing the sequence. When the process starts, in step S2260, the charging state is acquired from database 207, and it is determined whether the acquired "charging state" includes "standby" (S2261). Note that a state including "standby" means that the adjustment current of the second charging power is being performed. In step S2261, if the vehicle is "waiting" ("Yes"), the number of waiting vehicles M is obtained, the variable "I" is set to 1, the variable "IW" is set to 0, and the total power consumption W of all vehicles 1 currently charging is calculated (S2262, S2263, S2264). The variable "IW" for calculating the total charging power is added to the charging power during the I-th standby period to obtain "IW", and the total power used during charging, W, is added to "IW" to obtain "TW" (S2265, S2266). In step S2267, it is determined whether "TW" is less than the maximum power usage, and if so, charging start processing is performed for the I-th waiting vehicle 1 (S135). If "TW" is equal to or greater than the maximum power usage, charging is not possible and the vehicle remains in standby, proceeding to step S2268. In step S2268, if the variable "I" is not equal to the number of waiting vehicles M, "1" is added to "I" (S2269) and the process proceeds to step S2265, and if the variable "I" is equal to the number of waiting vehicles M, the process proceeds to step S227. The charging start process in step S135 is shown in FIG.

[0126] (2-5) Power judgment change process (S227) The charging determination charging process will be described mainly with reference to FIG. 50 and FIG. 43 showing the sequence. When the process starts, in step S2271, the charging state is acquired from the database 207, and it is determined whether the charging power during charging is the second charging power ("15") (S2272). In step S2272, if the charging power is the second charging power ("Yes"), the total power usage TW1 when charging all vehicles 1 currently being charged with the first charging power ("20") is calculated (S273), and it is determined whether the calculated total power usage TW1 is less than the maximum power usage (S2274). In step S2274, if the total power usage TW1 is less than the maximum power usage ("Yes"), it is determined that the charging voltage of the vehicle 1 being charged can be changed from the second charging power to the first charging power, and a power change signal is sent to the charging device 203 (S2275). In response to this, the charging device 203 changes the "charging power" included in the signal to the vehicle 1 currently being charged, continues charging, and sends a signal (power change response signal) to the OCPP server 206 indicating that the charging power has been changed. In step S2278, if a power change response signal is received from charging device 203 ("Yes"), a request is made to database 207 to change the power of "charging power" in status table T22 (S2277), and if a change response is received from database 207 indicating that the change has been made ("Yes" in S2278), a power change response indicating that the change in charging power has been successfully completed is output to AP server 208 (S2279), and the process proceeds to step S220 in FIG. 45.

[0127] (3) Database The processing of the control unit 271 of the database 207 will be described with reference to FIG. When the program starts and there is a request to create a charging request from the AP server 208 ("Yes" in S140), the control unit 233 creates a new charging request in the bottom record of the charging request table T21 and sends a creation response (S141), and proceeds to step S142.

[0128] In step S142, if there is a request for registration or deletion of status data ("Yes"), a response to registration etc. is made by registering (storing) in the field of the record at the bottom of the status table T22 or deleting the record of the charge request for which charging has been completed (S143), and the process proceeds to step S144. Registration includes a charge registration (power change) request when charging starts (see FIG. 39), and deletion includes a status record deletion request when charging is completed (see FIG. 40). In step S144, if there is a request to change the charging request table T21 ("Yes"), the corresponding part in the charging request table T21 is changed and a change response is made (S145), and the process proceeds to step S246. The change request includes a request to change the charging request when charging is completed (see FIG. 40), etc.

[0129] In step S246, if there is a change request for the status table T22 ("Yes"), the corresponding part in the status table T22 is changed and a change response is made (S247), and the process proceeds to step S148. Change requests include a start change request when charging starts from a standby state (see FIG. 42), an end change request when one charge has ended (see FIG. 41), and a power change request when the power has been changed (see FIG. 43). In step S148, if there is a status acquisition request ("Yes"), the status data of the corresponding record in the status table T22 is acquired, and output to the request destination for an acquisition response (S149), and the process proceeds to step S140. The status acquisition request may acquire all fields in the status table T22 or only necessary data, and may be a charging status acquisition request for a new request (see FIG. 39), a scheduled end time acquisition request for end determination (see FIG. 41), a charging status acquisition request for charging determination or power determination (see FIGS. 42 and 43), etc.

[0130] (4) AP server In the AP server 208, the AP application performs various processes as a result of the control unit 281 executing a program. The following will be explained with reference to Figs. 52 and 53. The AP application runs (starts), and when an operation to request charging is performed from the portable terminal 3 ("Yes" in step S170), a charging request corresponding to the portable terminal 3 is created in the charging request table T21 of the database 207 (S171). Specifically, as shown in Fig. 39 and Fig. 8, a request to create a charging request is made to the database 207, and when a new request is created in the charging request table T21, a creation response is returned from the database 207.

[0131] In step S272, the charging state etc. (status data) is acquired, and it is determined whether charging is possible (S273). Here, "charging is possible" includes cases where normal charging with the first charging power is possible, and cases where regulated charging in which the first charging power is changed to the second power is possible. Charging is determined by using the "charging status" and "charging power" obtained from database 207 to determine whether the total power usage (TW2) when charging a newly requested vehicle 1 with the currently charging charging power is less than the maximum power usage.If it is less than the maximum power usage, it is determined that charging is possible with the current charging power.If the total power usage (TW2) is greater than or equal to the maximum power usage, and if the current charging power is the first charging power and the total power usage (TW3) when charging is assumed to be at the lower second charging power is less than the maximum power usage, it is determined that charging (adjusted charging) is possible with the second charging power.If the total power usage (TW3) when charging with the second power is greater than or equal to the maximum power usage, it is determined that charging is not possible.If the total power usage (TW2) when charging is assumed to be at the current charging power is greater than or equal to the maximum power usage and the current charging power is the second charging power, it is determined that charging is not possible. Specifically, as shown in FIG. 52, from the acquired "charging status" and "charging power", the total power usage "TW2" is calculated assuming that all vehicles 1 for the new request and the currently charging request are charged with the same charging power as the charging power during charging (S2731), and it is determined whether "TW2" is less than the maximum power usage (S2732).

[0132] In step S2732, if the total power usage "TW2" is less than the maximum power usage ("Yes"), it is determined that charging is possible with the charging power during charging. If it is determined in step 2732 that the power usage is greater than or equal to the maximum power usage ("No"), and if the charging power during current charging is the first charging power ("Yes" in S2733), the total power usage "TW3" assuming that all vehicles 1 for the new request and the currently charging request are charged with the second charging power is calculated (S2734), and it is determined whether "TW3" is less than the maximum power usage (S2735). In step S2735, if it is determined that the power usage is less than the maximum power usage ("Yes"), the charging power is changed from the first charging power to the second charging power, and it is determined that charging is possible with the second charging power, and if it is determined that the power usage is greater than the maximum power usage ("No"), it is determined that charging is not possible. Furthermore, if it is determined in step S2733 that the charging power being charged is not the first charging power (it is the second charging power) ("No"), it is determined that charging is not possible.

[0133] 52, if it is determined in step S273 that charging is possible, a charging start / power change instruction including the "connector ID" and "charging power" of the charging target is output to the OCPP server 206. In response to this, if a charging start response is input from the OCPP server 206 ("Yes" in S275), a charging start report is sent to the portable terminal 3 (S276). If it is determined in step S273 that charging is not possible, a request is made to the database 207 for standby registration in the status table T22 (S178), a charging standby report is sent to the portable terminal 3 (S179), and the process proceeds to step S177.

[0134] In step S177, if a charging completion response is received from the OCPP server 206 ("Yes"), as shown in FIG. 40, a charging completion report is sent to the portable terminal 3 and a charging request change request is sent to the database 207 (S180, S181), and the process proceeds to step S182; if a charging completion response is not received ("No"), the process proceeds to step S182.

[0135] In step S182, as shown in FIG. 42, if there is a charging start response from the OCPP server 206 ("Yes"), a charging start report is sent to the portable terminal 3 (S183) and the process proceeds to step S184; if there is no charging start response ("No"), the process proceeds to step S184.

[0136] In step S184, as shown in FIG. 41, if there is a charging completion response from the OCPP server 206 indicating that one charging has been completed ("Yes"), a charging completion report is sent to the portable terminal 3 (S185) and the process proceeds to step S277; if there is no charging completion response ("No"), the process proceeds to step S277.

[0137] In step S277, as shown in FIG. 43, if a charging change response is received from the OCPP server 206 indicating that the charging power has been changed ("Yes"), a power change report for the charging power is sent to the mobile terminal 3 (S278) and the process proceeds to step S170; if no power change response is received ("No"), the process proceeds to step S170.

[0138] <Second embodiment A> As shown in Fig. 48, the charge control device 205 of the second embodiment 1 performs the termination process of step S128 when the scheduled termination time has passed ("Yes" in step S2252). That is, as shown in Fig. 41, a charge termination signal is transmitted from the OCPP server 206 to the charger 203, and in response to this, the charger 203 turns off charging (step S112 in Fig. 44). However, if there is a standby charging request before, at, or after the scheduled end time, the first hour of charging may be terminated, and if there is no charging request, the next first hour of charging may be continued. The following mainly describes the changed parts as the second embodiment A. Note that the second embodiment A corresponds to the first embodiment A, and the description of the common parts may be omitted.

[0139] 1. OCPP Server Configuration When charging ends and the charging time of the first vehicle 1 being charged reaches the first hour (including a time longer or shorter than one charging time), if there is a second vehicle 1 waiting, the OCPP server charges the waiting second vehicle 1 for the first hour and terminates charging of the first vehicle 1, and if there is no waiting vehicle, continues charging the first vehicle 1 for the next charging time.

[0140] When charging ends, the OCPP server 206A, by cooperating with the control unit 261, the communication unit 262, and the storage unit 263, similarly to when charging is completed by the OCPP server 206 in the second embodiment 1, includes a termination / continuation determination unit that determines whether to terminate the charging or continue and perform the next charging when the first hour of charging ends, a charging termination signal transmission unit when termination is determined, a charging normal termination signal reception unit, a charging termination response output unit, a termination change request output unit, a termination change response input unit, a start change request output unit notifying that the next charging has started when continuation is determined, a start change response input unit for the next charging, a charging status etc. (including the scheduled termination time) acquisition request output unit, and an acquisition response input unit. Note that when charging continues, a notification to that effect may be transmitted to the mobile terminal 3 via the AP server 208.

[0141] 2. OCPP Server Flowchart (1) Overall In the OCPP server 206A, the control unit 261 executes a program, and the OCPP application performs various processes. The following description will be given with reference to the flowcharts in FIGS. When the OCPP application runs, it performs steps from start to step S224 in Figure 45, performs the process (S225A) in Figure 54, and then proceeds to step S226 in Figure 45. In this way, the process of S224A in the flowchart for OCPP server 206A is different. This will be explained using Figure 54. Control unit 261 performs steps S123, S124, and S2251, and determines whether the Kth scheduled end time of charging has passed (S2252A). In step S2252A, if it is determined that the scheduled end time has passed ("Yes"), it is determined whether there is a second vehicle 1 waiting, and if there is a second vehicle 1 waiting ("Yes" in S2253A), the end processing S128 in Figure 19 is performed, and if there is no second vehicle 1 waiting ("No"), the continuation processing S139A is performed. When the termination process S128 or the continuation process 139A is performed, the process proceeds to step S130.

[0142] (2) Continuation Processing (139A) Continuation process 139A is a process for maintaining the charging state as it is and performing the next first hour of charging even after the first hour of charging has ended. In the continuation process (139A) shown in FIG. 25 of the first embodiment 1, the charging status in the status table remains “charging”, the scheduled end time of the next first hour of charging is stored in “scheduled end time”, and a value obtained by adding “1” to “number of charges” is stored. In the second embodiment A, the completion of charging is determined on the vehicle side (ECU 11), so the status table T22 does not have a field for "number of charges," and the "scheduled charging end time" during charging is changed to the "scheduled charging end time" for the next charge. In other words, the content of the change request in step 1391A in Figure 25 is different from that in the first embodiment A. In this way, in the second embodiment A, the first hour of charging is terminated when there is a second vehicle 1 in standby state, so the amount of communication between the OCPP server 206A and the database 207A can be reduced compared to when charging is terminated when there is no second vehicle 1 in standby state.

[0143] <Second embodiment B> In the charging system 201 of the second embodiment 1, when a new charging request is made, a determination as to whether charging for the new charging request is possible is made in accordance with step S273 in FIG. 52 and the flow shown in FIG. 53, but may be made in accordance with another flow. Another example of processing will be explained with reference to FIG. When the charging status, etc. is obtained in step S272 of Figure 52, as shown in Figure 55, the total power usage TW1b when all vehicles 1 currently charging and the vehicle 1 for which a new charging request has been made are charged (assuming) with the first charging power is calculated (S2731B), and the total power usage TW2b when all vehicles 1 currently charging and the vehicle 1 for which a new charging request has been made are charged (assuming) with the second charging power is calculated (S2732B). In step S2733B, if "TW1b" is less than the maximum power usage ("Yes"), it is determined that charging is possible with the first charging power without changing the charging power. If "TW1b" is equal to or greater than the maximum power usage in step S2733B ("No"), it is determined whether "TW2b" is less than the maximum power usage (S2734B). In step S2734B, if "TW2b" is less than the maximum usage power ("Yes") and the charging power during charging is the first charging power ("Yes"), it is determined that the charging power can be changed to the second charging power, and if the charging power during charging is not the first charging power (i.e., charging is being performed at the second charging power, "No"), it is determined that charging is possible without changing the charging power.

[0144] <Second embodiment C> 1. Overall structure In the charging system 201 of the second embodiment, a predetermined ta is set as a charging condition for normal charging. A set power (fixed) is used, and the set power is set lower than the maximum power usage of the charging device. In the charging system of the second embodiment C, charging is performed so that the maximum power usage is shared among the number of vehicles being charged. In this case, even if a new charging request is made, the maximum power usage will not be exceeded, and control can be performed so that the charging device does not become overloaded. Second embodiment C will be described below, focusing on the differences from second embodiment 1.

[0145] 2.AP server The AP server 208C has basically the same configuration as the AP server 208 in the second embodiment 1, but the processing of the AP application executed by the control unit is partially different. In the AP server 208C, similar to the second embodiment 1, the control unit 281C executes a program, and the AP application performs various processes, but in FIG. 52, S273 (FIG. 53) is different. The process corresponding to FIG. 53 will be explained below with reference to FIG. When the charging status, etc. is obtained in step S272, the number N of vehicles being charged is obtained (S2731C), and the maximum amount of power used is divided by the number of vehicles being charged plus "1" for the new charging request to calculate the power usage (S2732C). In step S2733C, if the power usage is less than the preset minimum power usage ("Yes"), it is determined that charging is not possible taking into account charging efficiency, and if it is greater than the minimum power usage ("No"), it is determined that charging is possible with that power usage. This makes it possible to shorten charging time when there are only a few vehicles to be charged. Note that if it is determined that charging is possible, the charging power of the vehicle 1 being charged will be changed.

[0146] 3.OCPP Server In the OCPP server 206C, the control unit 281C executes a program so that the OCPP application performs various processes, as in the second embodiment 1, but steps S224 and S225 in FIG. 45 are different. In this process, when charging of one vehicle is completed or terminated, charging of one waiting vehicle begins, and if the number of vehicles being charged changes due to the completion or termination of charging, the remaining vehicles are charged with new charging power.

[0147] (1) Completion process The process corresponding to S224 will be explained below with reference to FIG. When the control unit 281C completes step S2243 in FIG. 47, it acquires the charging state etc. ( S2244C). In step S2244C, it is determined whether there is a "waiting" request, and if there is a "waiting" request ("Yes"), charging is possible with the same charging power as the vehicle 1 that has completed charging (other vehicles 1 that are being charged) (S2246C), and charging start processing (S135) is performed for the first waiting charging request, and the process returns. If there is no "waiting" status ("No" in step S2245C), the number N of units being charged is acquired in step S2247C, and if the acquired number is "0" ("Yes" in step S2248C), the process returns. In step S2248C, if the number of units to be charged is not "0" ("No"), the maximum power usage is divided by the number of units to be charged N to calculate the power usage (S2249C), and a power change signal is sent to charge at the new power usage (S2275C). Thereafter, steps S2276 to S2279 are performed, and the process returns (proceeds to step S225).

[0148] (2) Termination process Hereinafter, the process corresponding to the termination process S128 (see FIG. 19) in FIG. 48 in the termination determination termination process S225 in FIG. 45 will be described with reference to FIG. When control unit 281C completes step S1288 in FIG. 19, it acquires the charging state and the like (S2253C). In step S2254C, it is determined whether there is a "waiting" request, and if there is a "waiting" request ("Yes"), charging is possible with the same charging power as the vehicle 1 that has finished charging (other vehicles 1 that are being charged) (S2255C), and charging start processing (S135) is performed for the first waiting charging request, and the process returns. If there is no "standby" status ("No" in step S2254C), the number of units to be charged N is acquired in step S2256C, and if the acquired number of units to be charged is "0" ("Yes" in step S2257C), the process returns. In step S2257C, if the number of units being charged is not "0" ("No"), the maximum power usage is divided by the number of units being charged N to calculate the power usage (S2258C), and a power change signal is sent to charge at the new power usage (S2275C). Thereafter, steps S2276 to S2279 are performed, and the process returns (proceeds to step S225).

[0149] (3) Power judgment change processing In the above completion process, steps S2247C, S2248C, S2249C, S2275C, and S2276 to S2279 perform charging determination charging processing and power change processing. If charging has been completed and there are vehicles 1 waiting, it is determined that charging of the waiting vehicles 1 is possible, and if charging has been completed and there are no vehicles 1 waiting, the number of vehicles to be charged decreases and it is determined that charging change is possible. In steps S2256C, S2257C, S2258C, S2275C, and S2276 to S2279 of the above termination process, charging determination charging process and power change process are performed. If charging has finished and there is a vehicle 1 waiting, it is determined that charging of the waiting vehicle 1 is possible, and if charging has finished and there is no vehicle waiting, the number of vehicles to be charged decreases and it is determined that charging change is possible. In this way, since the charge determination charging process and the power determination change process are performed in the completion process and the termination process, steps S226 and S227 in FIG. 45 are unnecessary.

[0150] <Third embodiment> In the first embodiment, the charging control device 105 controls charging for a plurality of vehicles 1 using the same control method. In the third embodiment, the charge control device groups multiple connectors 131 of the charge device 103 and can control each group using a different control method. Although the charge control device is not shown, it is designated by the reference numeral "305" to distinguish it from the charge control devices 105 and 205 of the other embodiments. Similarly, the reference numerals of the components not shown in the third embodiment are also designated by numbers in the 300 range. In the device of the third embodiment, if the device has the same or similar configuration as the device of the first embodiment, the description and drawings thereof will be omitted. The step numbers in the flowchart may use numbers for the same or similar processes as in the first embodiment, and while the step numbers in the first embodiment are in the 1000s, in the third embodiment they may be in the 3000s. Furthermore, the contents described in the first and second embodiments can be applied to the third embodiment, and even if the numbers for the same steps are different between the first and second embodiments and the third embodiment, they may still be the same process.

[0151] 1. Overall structure The charging system of the third embodiment differs from the charging system 101 of the first embodiment in that a plurality of connectors 131 are divided into groups, and the vehicle 1 is charged using a different charging method for each group. Here, for example, the plurality of connectors 131 are divided into two groups. For example, when charging starts for the first group, the battery is charged until it is fully charged (including a charge state of 90% or more of full charge). For example, when charging starts for the second group, the battery is charged until a first hour or approximately a first hour has elapsed, which is shorter than the charging time required to fully charge the battery. In other words, the second group is charged using the control method of the first embodiment. In addition, the parking lot in this embodiment is, for example, a parking lot for an apartment complex, with part of the lot open to general users (users unrelated to the apartment complex) and the rest closed for residents of the apartment complex. The first group is for general use and the second group is for residents. In this example, the control method performed on the first group is referred to as the first control method, and the control method performed on the second group is referred to as the second control method.

[0152] The group attribute indicating to which group a plurality of connectors 131 belong is stored, for example, in a group attribute table of the database 107, with the connector ID and the group attribute (for example, first or second) associated with each other. Note that the grouping can be changed as appropriate, for example, by an administrator or the like.

[0153] 2. Processing details In the third embodiment, as in the first embodiment, charging control of the charging device 103 to the vehicle 1 is performed by the OCPP server 106. Note that the OCPP server of the third embodiment has substantially the same configuration as the OCPP server of the first embodiment, but the contents of the program executed by the control unit are different. The processing of the control unit will be described below with reference to FIGS. When the OCPP application is started (start of FIG. 59), it is determined whether a charge start instruction has been input from the AP server 108 (S120). If a command to start charging has been input ("Yes"), the "connector ID" and "group attribute" of the charging target are acquired (S3001), and it is determined whether the acquired group attribute is "second group" (S3002). If it is determined in step S3002 that the battery belongs to the second group ("Yes"), control is performed using the second charging method. The second charging method is the same as the charging method in the first embodiment, and corresponds to steps S122 to S136 in FIG. That is, if it is determined that it belongs to the second group, charging for the first time period starts (S122) and the process proceeds to step S123, and if it is determined that it does not belong to the second group ("No"), the process proceeds to step S123. In steps S123 to S130, processing is performed according to the charging state during charging, and in steps S131 to S136, charging is performed on waiting vehicles if charging is possible. Note that steps S122 to S136 are the same as those in the first embodiment, so their description will be omitted, and some steps will not be shown in FIG.

[0154] In step S3003 of FIG. 60, if it is determined to be in the first group ("Yes"), control is performed using the first charging method. In other words, if it is determined to be in the first group, charging of the target vehicle 1 in the first group begins (S122) and the process proceeds to step S3004, and if it is determined not to be in the first group ("No"), the process proceeds to step S3004. In step S3004, the number M of vehicles to be charged in the first group is obtained, and it is determined whether full charging has been completed for M vehicles 1. If full charging has been completed, completion processing is performed (S3006 to S3008, S127), and the process proceeds to step S120 in Figure 59.

[0155] 3.Other (1) Group In the above description, a group is defined as one charging device 103 having multiple connectors 131, but for example, if one charging device 103 has one connector 131, multiple charging devices 103 installed in a parking lot may be divided into groups. Furthermore, in the above explanation, there are two groups, but there may be three or more groups. (2) In the above description, the charging control device 305 controls the charging of two groups with one control unit. However, for example, the charging control device 305 may be provided with control units corresponding to the groups. For example, the charging control device 305 may be provided with a first control unit that controls the first group using a first control method and a second control unit that controls the second group using a second control method, and both control units may process in parallel.

[0156] <Modification> The charging system, charging device, and charging control device of the first embodiment (including 1, A to D), the second embodiment (including A to C), and the third embodiment have been described, but are not limited to these embodiments and may be modified as follows, for example. Also, each embodiment may be combined with another embodiment, each embodiment with a modified embodiment, or configurations within the modified embodiments may be combined with each other. Furthermore, examples not described in the first to third embodiments and modifications, and design changes within the scope of the gist, are also included in the inventions according to these embodiments.

[0157] 1. Determine whether the vehicle is properly connected If the vehicle 1 to be charged is not connected properly, the charging control device 105, 205 (, 305), etc. sends an error to the mobile terminal 3, as in step S1229 in Figure 16 or Figure 46, step S1279 in Figure 18, and step S1289 in Figure 19. The charging device 103, 203 (, 303) checks whether it is electrically connected to the vehicle 1 with the "connector ID" included in the start preparation signal, completion preparation signal, or end preparation signal, and outputs a "normal signal" if it is connected, or 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 S1229 in FIG. 16 and FIG. 46, step S1279 in FIG. 18, and step S1289 in FIG.

[0158] (1) Connection judgment 1 In the above method, the determination of whether the vehicle 1 to be charged is connected normally (normal connection determination means) is performed by the charging device 103, 203 (303). However, the normal connection determination may also be performed by the OCPP server 106, 206 (306) or the AP server 108, 208 (308). In this case, the charging device 103, 203 (, 303) outputs only the connection result regarding whether or not there is an electrical connection for the vehicle 1 (connector 131) to be charged or for all vehicles 1 to the OCPP server 106, 206 (, 306) and / or AP server 108, 208 (, 308), and the OCPP server 106, 206 (, 306) or AP server 108, 208 (, 308) can determine whether or not the "connector ID" of the target of the charging request is included in the connection result from the charging device 103, 203 (, 303).

[0159] (2) Connection judgment 2 When a start preparation signal, a completion preparation signal, or an end preparation signal is input to the charging device 103, 203 (, 303) ("Yes" in steps S101, S105, S109 of FIG. 14 or "Yes" in steps S101, S109 of FIG. 44), the charging device 103, 203 (, 303) checks the connection of the "connector ID" included in the signal. However, if the OCPP server 106, 206 (306) or AP server 108, 208 (308) determines whether the connection is normal, the start preparation signal, the completion preparation signal, or the end preparation signal does not need to include the "connector ID." For example, when a start preparation signal, a completion preparation signal, or an end preparation signal is input, the charging device 103, 203 (, 303) checks the electrical connection of all connectors 131 and outputs the connection result to the OCPP server 106, 206 (, 306) or the AP server 108, 208 (, 308). 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, 203 (, 303), the OCPP server 106, 206 (, 306) or the AP server 108, 208 (, 308) determines that the connection is "normal," and if it is not included in the connection result, determines that there is an "error." In this case, the normal connection determination for the vehicle 1 is performed on the OCPP server 106, 206 (306) or AP server 108, 208 (308) side. In consideration of the amount of communication, it is preferable that the connection determination be performed by the charging device 103, 203 (303) or the OCPP server 106, 206 (306).

[0160] 2. Charging possible determination (1) Rechargeable determination 1 As shown in FIGS. 15, 59, and 60, the OCPP 106 (306) acquires the number of units to be charged from the information in the status table and then determines whether charging is possible (step S134). The status table information here is all the "charging states" stored in the status table T12. The means for determining whether charging is possible is realized by software, as in step S134 in Fig. 15 and step S3006 in Fig. 60. However, the information obtained from the status table only needs to be able to ultimately obtain the number of charging units, and may be, for example, all "charging numbers" whose charging status is "charging" or the number of units whose charging status is "charging." Furthermore, if the power usage used for charging can be obtained in the charging device 103, the total power usage during charging may be obtained from the charging device 103. If the power usage of one vehicle 1 is determined in advance, the information in the status table may be the total power usage currently during charging. 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 obtained 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, a normal charging completion signal, or a normal charging end signal is input, and obtains the current number of units being charged from the number on the counter.

[0161] (2) Rechargeable determination 2 53, the AP server 208 makes a determination based on the total power usage and the maximum power usage when all vehicles 1, including the vehicle 1 that has made a new charging request and the vehicle 1 that is being charged, are assumed to be charged. However, if the charging power per vehicle is set, instead of the total power usage, the determination may be made based on the total number of vehicles, including the vehicle that is being charged and the vehicle that has made the new charging request, and the maximum number of vehicles to be charged, which is the maximum power usage divided by the set power. For example, in the case of a first charging power (e.g., 20 kW), the maximum number of vehicles to be charged may be set to two, and in the case of a second charging power (e.g., 15 kW), the maximum number of vehicles to be charged may be set to three, and the number of vehicles including the vehicle 1 that has made the new charging request may be compared. Furthermore, if the set charging power is not constant depending on the size of the vehicle (battery), the number of vehicles may be calculated by setting the standard charging power to 1. For example, if the set power is 20 kW, the total number of vehicles may be calculated as 30 / 20 = 1.5 vehicles with a set power of 30 kW, and 15 / 20 = 0.75 vehicles with a set power of 15 kW.

[0162] 3. Wait In the second group in the first, second, and third embodiments, after a new charge request or the first hour of charging is completed, the devices are placed on standby in the lowest record in the status tables T12 and T22. In other words, they are registered at the end of the charging standby list. This allows charging to be performed in the order of the charge requests, ensuring fairness.

[0163] 4. First Hour (1) The first time period is not particularly limited as long as it is shorter than the charging time (full charge time) required for the battery to charge from 0% to 100%, but is preferably 10 to 40% of the full charge time, and even more preferably 10 to 30%. If the first time is short, the number of times the vehicle is charged in the first time will increase, but it will be difficult to improve the charge amount. Conversely, if the first time is long, the charge amount per charge can be secured, but it will not be possible to charge many vehicles. The first time period mentioned above differs depending on the capacity of the vehicle's battery, but it is preferable that the charge be sufficient to travel approximately 30 to 100 km, which will enable the vehicle to travel to the nearest electric station. (2) The first time period may be set to a fixed time by the manager (management company) of the parking lot of an apartment building, etc., or may be automatically set to vary depending on the time of day. As an example of a time period that varies depending on the time of day, the first time period may be set to be longer during times when there are fewer vehicles parked in the parking lot, such as between 10:00 and 16:00, and may be set to be shorter at other times when there are more vehicles. (3) In the second group of the first and third embodiments, if there are no waiting vehicles after the first hour has elapsed, charging for the first hour is started again, and after the first hour has elapsed (after the termination process ("S128" in Figure 15)), it is determined ("S132" in Figures 15 and 59) whether there are any waiting vehicles. However, during the second first hour of charging (for example, when half the first hour has passed), it may be determined whether there is a vehicle waiting, and if there is a vehicle, the second first hour of charging may be terminated, and if there is no vehicle waiting, the second first hour of charging may be continued. (4) In the second embodiment, a determination is made as to whether or not there is a waiting state after the scheduled end time of the first hour has passed ("S2253A" in FIG. 54), but a determination as to whether or not there is a waiting state may also be made before the scheduled end time has passed.

[0164] 5.Other (1) Although transactions are used in the transmission and reception of signals between the OCPP server 106, 206 (, 306) and the charging device 103, 203 (, 303), transactions do not have to be used. Note that using transactions can prevent malfunctions. Examples of malfunctions include when a normal charging start signal is not sent even though charging is in progress, or when charging is continued without a charging start report being sent to the portable terminal 3. (2) The charging system 101, 201 (, 301) includes a charging device 103, 203 (, 303) and a charging control device 105, 205 (, 305), but the charging device may be configured as a single device that combines a charging unit corresponding to the charging device and a charging control unit corresponding to the charging control device. Also, the charging device may be configured as a device in which the OCPP server 106, 206 (, 306) (its control unit 161, 261 (, 361)) of the charging control device 105, 205 (, 305) is incorporated into the charging device 103, 203 (, 303). (3) Although OCPP is used for communication between the charging devices 103, 203 (, 303) and the OCPP servers 106, 206 (, 306) (first servers), other protocols may also be used. (4) The AP server 108, 208 (, 308) accepts the charging request from the mobile terminal 3, but may accept it in other ways. For example, a card storing identification information such as a vehicle ID may be accepted from the charging device 103, 203 (, 303) or an external reader. (5) The mobile terminal 3 has an application installed that corresponds to the AP server 108, 208 (308), but it may also communicate with the AP (WEB-API) using, for example, an application (front-end) running on a browser. (6) In the first and second embodiments, the maximum power usage (maximum number of charging devices) was set in advance, but it may also be possible for the manager of an apartment building or the like to set it. Furthermore, if the apartment building's power usage is available, the maximum power usage may be set automatically or manually so as to be higher during time periods when power usage in each household in the apartment building is low. Examples of time periods when power usage is low include midnight to 5:00, 10:00 to 16:00, and 21:00 to 24:00. (7) The OP server 108, 208 (308) reports various information to the mobile terminal 3 by email or the like, but may also report by push notification. (8) In the first and second embodiments, a parking lot in an apartment building was described as an example of a parking lot, but it may also be a parking lot in a commercial facility, a sports facility such as a baseball stadium or soccer field, a spectator or entertainment facility such as a concert venue, a medical facility such as a hospital, or a company (hereinafter sometimes referred to as a “general parking lot”). In the third embodiment, a partially open parking lot of an apartment complex has been described as an example of a parking lot, but the parking lot may be a partially open parking lot of a company or hospital, or may be a parking lot of an apartment complex where a first group is for residents who drive a long distance per day, a second group is for residents who drive a short distance per day, and a third group is for non-residents. This makes it possible to provide a parking lot that is easy to use. (9) In the first to third embodiments, the completion of charging is not described as being other than full charge (including a charging state equivalent to full charge), but the charging may be completed by a completion signal from the mobile terminal 3, the charging device 103, etc. Upon completion, the charging completion date and time of the corresponding record in the charging request table is stored, the corresponding record in the status table is deleted, and records lower than that record are moved up. (10) In the first to third embodiments, the association between the vehicle 1 and the charging device 103 is not specifically described. However, for example, the vehicle 1 to be charged may be registered in advance with the charging device 103, and the vehicle 1 may be connected to the connector 131 of a specific charging device 103 to request charging. For example, charging devices are often used by specific people in parking lots of apartment complexes or monthly parking lots. Alternatively, if the vehicle 1 to be charged by the charging device 103 is not specified, for example, the vehicle 1 can be connected to an available charging device 103, and a charging request can be made from a mobile terminal 3, etc., using the device number, QR code (registered trademark), barcode, etc. of the charging device 103. This is often used by unspecified people in commercial facilities, sports facilities, coin parking lots, etc. (11) In the first to third embodiments, the information transmitted from the AP server 108, 208 (308) to the mobile terminal 3 has been described as a charging start report, a charging standby report, a charging completion report, a charging end report, a power change report, etc., but other information may also be transmitted. Examples of other information include a charge fee for charging, a vehicle charging rate (charging level), and an order in a standby state. Note that this information may be checked by accessing an internet URL, in addition to a mobile application.

[0165] In the above embodiment, at least the following inventions are disclosed. Each invention is not limited to the first to third embodiments and modified examples, and inventions 1 to 5 include examples not described therein and design changes that do not deviate from the gist of the invention.

[0166] The technology of Patent Document 1 can control the charging device so that it does not become overloaded, but there is a problem in that even if a charging request is made early, depending on the amount of charge, charging may take a long time to complete. An object of the present invention is to provide a charge control device and the like that can control a charging device so that it does not become overloaded and that charges in response to an early charging request.

[0167] <Invention 1> (1) First charge control device and first charge control method The first charging control device is a charging device that electrically charges each of a plurality of vehicles that can be electrically charged in a parking lot, and is a charging control device that controls charging of the vehicles connected to the charging device, with the maximum power usage set for charging the plurality of vehicles simultaneously, and temporarily stops charging when the charging time of the vehicle being charged reaches a first time that is shorter than the charging time for full charge. The first charging 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 a parking lot and has a maximum power usage setting that allows simultaneous charging of the plurality of vehicles, and when the charging time of the vehicle being charged reaches a first time that is shorter than the charging time for full charging, charging is temporarily terminated. This allows multiple vehicles to be charged without exceeding the maximum power usage. Furthermore, because multiple vehicles are charged in a first hour that is shorter than the time it takes to fully charge, more vehicles can be charged, although the charge amount is lower, compared to fully charging one vehicle first and then fully charging another. In other words, multiple vehicles can be charged evenly in a short charging time.

[0168] (2) Second charge control device and second charge control method The second charging control device is a charging device that electrically charges each of a plurality of vehicles that can be electrically charged in a parking lot, and is a charging control device that controls charging of the vehicles connected to the charging device, the charging device having a set maximum power usage that can be used to charge the plurality of vehicles simultaneously, and charges the vehicles one or more times for a first period of time that is shorter than the charging time required for a full charge. The second charging 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 a parking lot, and for which a maximum power usage that can be simultaneously charged for the plurality of vehicles is set, and in which the vehicle is charged one or more times for a first period that is shorter than the charging time required for full charging. Note that "performed once or more times" may also be expressed as "performed repeatedly." This allows multiple vehicles to be charged without exceeding the maximum power usage. Furthermore, because multiple vehicles are charged in a first time that is shorter than the time it takes to fully charge, more vehicles can be charged, although the charge amount is lower, compared to fully charging one vehicle first and then fully charging another. In other words, multiple vehicles can be charged evenly in a short charging time, gradually increasing the charge amount of all vehicles.

[0169] (3) Third charge control device and third charge control method The third charging control device is a charging control device that electrically charges each of a plurality of vehicles that can be electrically charged in a parking lot, and controls charging of the vehicles connected to the charging device, where the maximum power usage that can be used to charge the plurality of vehicles simultaneously is set, and determines whether to terminate charging when the charging time of the vehicle being charged reaches a first time that is shorter than the charging time for full charge. The third charging control method is a charging control method for controlling charging of vehicles connected to a charging device that electrically charges each of multiple vehicles that can be electrically charged in a parking lot, and for which a maximum power usage limit for simultaneously charging the multiple vehicles is set, and when the charging time of a vehicle being charged reaches a first time that is shorter than the charging time for full charging, it is determined whether to terminate charging. This allows multiple vehicles to be charged without exceeding the maximum power usage. Furthermore, because multiple vehicles are charged in a first hour that is shorter than the time it takes to fully charge, more vehicles can be charged, although the charge amount is lower, compared to fully charging one vehicle first and then fully charging another. In other words, multiple vehicles can be charged evenly in a short charging time. The determination may be realized by software processing or by hardware processing using an electric circuit or the like.

[0170] (4) Fourth charging control device The fourth charging control device puts charging of the newly requested vehicle into a standby state when a new charging request is made in any of the first to third charging control devices and the total power usage when charging the newly requested vehicle exceeds the maximum power usage. This allows charging of multiple vehicles within the maximum power usage limit. The standby state may be registered at the end (tail) of the charging waiting list when there are multiple vehicles waiting to be charged. Furthermore, the charging waiting list may be prioritized over new charging requests. For example, if multiple vehicles are waiting and have completed one or more first-hour charging sessions, and no new charging request has been made and no waiting vehicles have been made, the vehicle may be registered at the front (first) of the charging waiting list. Alternatively, if there are multiple new charging requests and multiple waiting vehicles, the vehicle may be registered at the end (tail). From the perspective of fairness, it is preferable to register the vehicles in order of the earliest time of the new request and the time when the first-hour charging session was completed.

[0171] (4A) 4A charging control device The fourth A charging control device is the first to third charging control devices, A charging request receiving means (corresponding to, for example, step S170 in FIG. 22) for receiving a charging request for the vehicle; a first charge control means for controlling charging of the vehicle for which a new charging request has been made; a first vehicle number acquisition means (corresponding to, for example, step S172 in FIG. 22) for acquiring the number of vehicles being charged; Equipped with The first charging control means charges the vehicle for the new charging request 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 range of the maximum power usage (e.g., "Yes" in step S173, corresponding to S174), and puts the vehicle for the new charging request into standby mode when the acquired number of vehicles to be charged is equal to or greater than the maximum number (e.g., "No" in step S173, corresponding to S181).

[0172] (4B) 4B charging device The charging control device of the fourth B is the charging control device of the fourth A, A second vehicle number acquisition means (corresponding to, for example, step S131 in FIG. 15) for acquiring the number of vehicles being charged among the plurality of vehicles; a second charge control means for controlling charging of the vehicle in the standby state; Furthermore, When the number of vehicles to be charged acquired by the second number-of-vehicles-to-be-charged acquisition means is less than the maximum number, the second charge control means charges at least one of the vehicles in the standby state (e.g., this corresponds to "Yes" in step S134 in Figure 15). (4C) 4C charging control device The 4C charging control device starts charging one of the vehicles in a standby state when the 4B charging control device completes charging one of the vehicles that was being charged or when the first hour of charging ends. This allows vehicles to be charged while in standby mode without exceeding the maximum power usage.

[0173] (5) Fifth charging control device The fifth charging control device is one of the first to third charging control devices, and when a new charging request is made while at least one vehicle of the plurality of vehicles is being charged with a first charging power, if the total power usage when charging the vehicle being charged and the vehicle for which the new charging request has been made with the first charging power exceeds the maximum power usage, the fifth charging control device charges the vehicle for which the new charging request has been made and the vehicle being charged with the first charging power with a second charging power whose total power usage is less than the maximum power usage and is lower than the first charging power. This allows charging of multiple vehicles within the maximum power usage limit. The second charging power is preferably in the range of 40 to 80% of the first charging power, and more preferably in the range of 40 to 70%. If the ratio is small, more vehicles can be charged, but it is difficult to increase the charging amount. If the ratio is large, the charging amount can be increased, but the number of vehicles that can be charged simultaneously decreases.

[0174] (5A) 5A charging control device The 5A charging control device is the first to third charging control devices, A charging request receiving means (corresponding to, for example, step S170 in FIG. 52) for receiving a charging request for the vehicle; a first charge control means for controlling charging of the vehicle for which a new charging request has been made; a first power acquisition means (corresponding to, for example, step S272 in FIG. 52) for acquiring charging power for the vehicle during charging; Equipped with The first charge control means When a new charging request is made while at least one of the plurality of vehicles is being charged, if the total power usage when charging the vehicle being charged and the vehicle for which the new charging request has been made with the charging power during charging exceeds the maximum power usage and the charging power during charging is a first charging power, and if the total power usage when charging the vehicle being charged and the vehicle for which the new charging request has been made with a second charging power lower than the first charging power is less than the maximum power usage, the vehicle for which the new charging request has been made is charged with the second charging power. This allows charging of multiple vehicles within the maximum power usage limit. The second charging power is preferably in the range of 40 to 80% of the first charging power, and more preferably in the range of 40 to 70%. If the ratio is small, more vehicles can be charged, but it is difficult to increase the charging amount. If the ratio is large, the charging amount can be increased, but the number of vehicles that can be charged simultaneously decreases. (5B) 5B charging control device The charging control device of No. 5B is the charging control device of No. 5A, A second vehicle number acquisition means (corresponding to, for example, step S2260 in FIG. 49) for acquiring the number of vehicles currently being charged; a second charge control means for controlling charging of the vehicle in the standby state; Furthermore, The second charging control means charges at least one of the vehicles in the standby state with the second charging power when the total power usage when charging the vehicles being charged acquired by the second vehicle number acquisition means and the vehicles in the standby state with the second charging power is less than the maximum power usage (for example, this corresponds to "Yes" in steps S2262 to S2267 of Figure 49 and S135). (5C) 5C charging control device The 5C charging control device starts charging one of the vehicles in a standby state when the 5B charging control device completes charging one of the vehicles that was being charged or when the first hour of charging ends. This allows vehicles to be charged while in standby mode without exceeding the maximum power usage.

[0175] (6) Sixth charging control device The sixth charge control device is the first to fifth charge control devices, the charging device includes a plurality of connectors for connection to the plurality of vehicles, the plurality of connectors belong to any one of a plurality of groups, The charge control device can control each group using a different control method. This enables highly versatile charging control in parking lots where multiple vehicles are parked. (7) Seventh charging control device The seventh charge control device is the sixth charge control device, a communication unit that receives a request to charge the vehicle from a mobile terminal; The control method is transmitted to the mobile terminal via the communication unit. This allows the user of the charging device to know the charging control method of the charging device via the mobile terminal, thereby improving usability.

[0176] (8) Eighth charging control device The eighth charge control device is the charge control device of the fourth B, fourth C, fifth B, or fifth C, 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 is executed by an application executed by the second server. This allows the first charge control means to be provided without making any major changes to the first server. Furthermore, since the server is used to control the charging device, such as the end of charging for the first period, the burden on the user can be reduced when the charging end is managed by the charging device. In other words, when the charging device manages the charge end, once charging is completed, the user must disconnect the connector 131 from the vehicle 1 or make another charging request from the mobile terminal 3 to reset the charge request. However, when the server is used to manage the charge end by a program (software), the user does not need to reset the charge request.

[0177] (9) Ninth charging control device The ninth charge control device is the charge control device of the fourth B, fourth C, fifth B, or fifth C, 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 is executed by an application executed by the first server or the second server, The second charge control means is executed by an application executed by the first server or the second server. This reduces the amount of communication between the first server and the second server. Also, since the server is used to control the charging device to end charging for the first hour, the burden on the user can be reduced when the charging end is managed by the charging device. In other words, when the charging device manages the charge end, once charging is completed, the connector 131 must be removed from the vehicle 1 or the user must make another charging request from the mobile terminal 3 to reset the charge request. However, when the server is used to manage the charge end by a program (software), the user does not need to perform this resetting operation.

[0178] (10) Charging system The charging system is a charging system that electrically charges a plurality of vehicles that can be electrically charged in a parking lot, and includes 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 has a maximum power usage setting for simultaneously charging the plurality of vehicles, and the charging control devices are first to seventh charging control devices. This allows multiple vehicles to be charged without exceeding the maximum power usage.

[0179] <Invention 2> The technology of Patent Document 1 makes it possible to control charging of a vehicle so that the capacity of the power receiving equipment is not overloaded, but it has the problem of requiring the provision of a first measurement unit and a second measurement unit, which makes the equipment complicated. The second aspect of the present invention aims to provide a charge control device or the like that can control the charger so that it does not overload, without providing a measuring unit or the like.

[0180] (1) Charging control device The first charging control device is a charging control device that electrically charges each of a plurality of vehicles that can be electrically charged in a parking lot, and that controls charging of the vehicles connected to the charging device, with the maximum power usage set for simultaneously charging the plurality of vehicles. When a charging request is made and charging the vehicle for which charging is requested would exceed the maximum power usage, the charging control device puts the charging of the vehicle for which charging is requested into a standby state. This allows the vehicle to be charged without exceeding the maximum power usage. The second charge control device starts charging one of the vehicles in standby mode when the first charge control device completes charging one of the vehicles that has been charged within the maximum power usage range, thereby enabling efficient charging of multiple vehicles without exceeding the maximum power usage range. In the third charge control device, in the second charger, the one vehicle in the standby state is the vehicle that has been in standby for the longest time, thereby enabling a plurality of vehicles to be charged fairly. (2) Charging system The charging system is a charging system that electrically charges a plurality of vehicles that can be electrically charged in a parking lot, and includes 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 the charging of the vehicles by the charging device, wherein the charging device has a maximum power usage setting for simultaneously charging the plurality of vehicles, and the charging control device is any one of the charging control devices 1 to 3 described above. This allows multiple vehicles to be charged without exceeding the maximum power usage. (3) Charging control method The charging control method controls charging of vehicles connected to a charging device that electrically charges each of a plurality of vehicles that can be electrically charged in a parking lot and has a maximum power usage set for simultaneously charging the plurality of vehicles, and when a charging request is made and charging the vehicle for which charging is requested exceeds the maximum power usage, charging of the vehicle for which charging is requested is put into a standby state. This allows multiple vehicles to be charged without exceeding the maximum power usage.

[0181] <Invention 3> The technology of Patent Document 1 makes it possible to control charging of a vehicle so that the capacity of the power receiving equipment is not overloaded, but it has the problem of requiring the provision of a first measurement unit and a second measurement unit, which makes the equipment complicated. The third aspect of the present invention aims to provide a charge control device or the like that can control the charger so that it does not overload, without providing a measuring unit or the like.

[0182] (1) Charging control device A first charging control device is a charging control device that electrically charges each of a plurality of vehicles that can be electrically charged in a parking lot, and that controls charging of the vehicles connected to the charging device, where a maximum power usage is set for simultaneous charging of the plurality of vehicles, and when a new charging request is made while at least one of the plurality of vehicles is being charged at a first charging power, if charging the new vehicle that has been requested to be charged with the first charging power in addition to the vehicle that is being charged would result in a total power usage exceeding the maximum power usage, the first charging control device charges the vehicle that has been requested to be newly charged and the vehicle that is being charged with the first charging power at a second charging power that is lower than the first charging power and results in a total power usage that is less than the maximum power usage, thereby allowing charging to be performed without exceeding the maximum power usage. When charging of one of the vehicles that has been charged with the second charging power is completed in the first charging control device, if charging the remaining vehicles that are being charged with the second charging power at the first charging power is less than the maximum power usage, the second charging control device converts the charging power of the remaining vehicles that are being charged with the second charging power back to the first charging power and charges them, thereby shortening the charging time for the remaining vehicles. The third charge control device, in the second charge control device, when a new charge request is made while charging with the second charging power, puts the vehicle being charged with the second charging power and the newly requested vehicle into standby mode if the total power usage would exceed the maximum power usage if the new request were made while charging with the second charging power. This allows multiple vehicles to be charged according to the charge requests. (2) Charging system A charging system for electrically charging a plurality of vehicles that can be electrically charged in a parking lot includes 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 a maximum power usage for simultaneously charging the plurality of vehicles is set for the charging device, and the charging control device is any one of the first to third charging control devices described above. This allows the plurality of vehicles to be charged without exceeding the maximum power usage. (3) Charging control method A charging control method controls charging of vehicles connected to a charging device that electrically charges each of a plurality of vehicles that can be electrically charged in a parking lot and has a maximum power usage set for simultaneously charging the plurality of vehicles, and when a new charging request is made while at least one of the plurality of vehicles is being charged at a first charging power, if charging the new vehicle that has been requested to be charged at the first charging power in addition to the vehicle that is being charged at the first charging power would result in a total power usage exceeding the maximum power usage, the method charges the new vehicle that has been requested to be charged and the vehicle that is being charged at the first charging power at a second charging power that is lower than the first charging power and results in a total power usage that is less than the maximum power usage. This allows the plurality of vehicles to be charged without exceeding the maximum power usage.

[0183] <Invention 4> Patent Document 1 describes a technique for controlling the charging current of a plurality of chargers, but there is a problem in that the technique is not very versatile in parking lots where a plurality of chargers are installed. Invention 4 aims to provide a highly versatile charge control device and the like.

[0184] (1) When one charging device charges one vehicle (1-1) 1A Charge Control Device and 1A Charge Control Method The first A charging control device is a charging control device that controls charging of vehicles connected to a plurality of charging devices that are installed in a parking lot and electrically charge vehicles that can be electrically charged, and the plurality of charging devices belong to any one of a plurality of groups; The charge control device is capable of controlling the chargers differently for each group. The charging control method of 1A is a charging control method for controlling charging of vehicles connected to a plurality of charging devices that are provided in a parking lot and electrically charge vehicles capable of being electrically charged, the charging control method comprising: the plurality of charging devices belong to any one of a plurality of groups; The charging control method allows different control of the charging devices for each group. This enables highly versatile charging control in parking lots where multiple vehicles are parked. The different controls here include, for example, the control of the charging control device in invention 1, the control of the charging control device in invention 2, and the control of charging until full charge (including a charge state of 90% or more of full charge) once charging has started. Also, the control may be different for each group, or it may be the same. Furthermore, the different control settings can be set appropriately by the administrator of the charging control device and can be changed depending on the usage status of the parking lot, further improving versatility.

[0185] (1-2) Second A charge control device and second A charge control method The second A charging control device is the first A charging control device, wherein the plurality of groups includes at least a first group and a second group; The charging control device In a first group, control is performed so that the vehicles connected to the charging devices belonging to the first group are fully charged or charged to a state equivalent to a full charge; In the second group, the charging device controls the vehicles connected to the second group to be charged for a first time period that is shorter than the charging time required for full charging. A second-A charge control method is the first-A charge control method, wherein the plurality of groups includes at least a first group and a second group; The charge control method includes: In a first group, control is performed so that the vehicles connected to the charging devices belonging to the first group are fully charged or charged to a state equivalent to a full charge; In the second group, the charging device controls the vehicles connected to the second group to be charged for a first time period that is shorter than the charging time required for full charging. This makes it possible, for example, in a parking lot, to open the charging devices in the first group and control them for vehicles that do not have a contract, and close the charging devices in the second group and control them for vehicles that do have a contract, thereby increasing the flexibility of how the parking lot can be used. In an apartment complex parking lot, for example, a first group may be for visitors to the apartment complex residents or members of the public unrelated to the apartment complex, and a second group may be for the apartment complex residents. A public parking lot is a parking lot where cars can be parked and charged. For example, a first group may be a group for public use where anyone can use the charging equipment for a fee, and a second group may be a group where contracted users can use the charging equipment for a fee. Furthermore, a public parking lot may be configured so that users of charging equipment can select between the first and second groups. This allows users to, for example, charge their cars at a charging equipment in the first group if they plan to drive long distances after charging, and charge at a charging equipment in the second group if they plan to drive short distances after charging, thereby increasing the options available to users. The first group of controls is, for example, control that, once charging has started, charges the battery until it is fully charged (including a charge state of 90% or more of full charge), and the second group of controls is control by the charge control device in Invention 1.

[0186] (2) When one charging device charges multiple vehicles (2-1) 1B Charge Control Device and 1B Charge Control Method The first B charging control device is a charging control device that controls charging of a vehicle connected to a plurality of connectors for electrically charging a vehicle that is provided in a parking lot and can be electrically charged, and the plurality of connectors belong to any one of a plurality of groups, The charging control device is capable of controlling charging via the connector in a different manner for each group. A first-B charging control method is a charging control method for a charging device provided in a parking lot and having a plurality of connectors for electrically charging electrically chargeable vehicles, the charging control method controlling charging of the vehicles connected to the connectors, the plurality of connectors belong to any one of a plurality of groups, The charging control method allows different control for each group in controlling charging via the connector. This enables highly versatile charging control in parking lots where multiple vehicles are parked. The different controls here include, for example, the control of the charging control device in invention 1, the control of the charging control device in invention 2, and the control of charging until full charge (including a charge state of 90% or more of full charge) once charging has started. The control may be different for each group, or it may be the same. The different control settings can be set appropriately by the administrator of the charging control device and can be changed depending on the usage status of the parking lot, further improving versatility.

[0187] (2-2) Second-B charge control device and second-B charge control method The second-B charge control device is the first-B charge control device, wherein the plurality of groups includes at least a first group and a second group; The charging control device In a first group, control is performed so that a vehicle connected to a connector belonging to the first group is fully charged or charged to a state equivalent to a full charge; In the second group, control is performed so that the vehicles connected to the connectors belonging to the second group are charged for a first time period that is shorter than the charging time required for full charging. A second-B charge control method is the first-B charge control method, wherein the plurality of groups includes at least a first group and a second group; The charge control method includes: In a first group, control is performed so that a vehicle connected to a connector belonging to the first group is fully charged or charged to a state equivalent to a full charge; In the second group, control is performed so that the vehicles connected to the connectors belonging to the second group are charged for a first time period that is shorter than the charging time required for full charging. This makes it possible, for example, in a parking lot, to open the first group of connectors and control them for vehicles that do not have a contract, and close the second group of connectors and control them for vehicles that do have a contract, thereby increasing the flexibility of how the parking lot can be used. In an apartment complex parking lot, for example, one group may be for visitors to the apartment complex residents or general use unrelated to the apartment complex, and a second group may be for the apartment complex residents. A public parking lot is a parking lot where cars can be parked and charged. For example, a first group may be a public group where anyone can use a connector for a fee, and a second group may be a group where contracted users can use a connector for a fee. Furthermore, a public parking lot may be configured so that a user of a charging device can select between the first group and the second group. This allows a user to, for example, charge using a connector in the first group if they plan to drive a long distance after charging, and charge using a connector in the second group if they plan to drive a short distance after charging, thereby increasing the user's options. The first group of controls is, for example, control that, once charging has started, charges the battery until it is fully charged (including a charge state of 90% or more of full charge), and the second group of controls is control by the charge control device in Invention 1.

[0188] (3) Charging system The charging system is a charging system that electrically charges a plurality of vehicles that can be electrically charged in a parking lot, and includes 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 the charging of the vehicles by the charging device, and the charging control device is the first (A, B) or second (A, B) charging control device described above.

[0189] <Invention 5> Patent Document 1 describes a technique for controlling the charging current of multiple chargers, but it does not display information about charging, making it difficult to say that it is user-friendly for people who use (charge) the chargers. Invention 5 aims to provide a charging control device and the like that is easy to use for people who use charging devices.

[0190] (1) When one charging device charges one vehicle (1-1) 1A charging control device The first charge control device includes: a first communication unit capable of communicating with a plurality of charging devices provided in the parking lot and capable of electrically charging the vehicle; a second communication unit capable of communicating with a mobile terminal of a user or manager of the vehicle; a control unit that controls charging of the vehicle; Equipped with When the control unit receives a charging request from the mobile terminal via the second communication unit, the control unit instructs the charging device to charge the target vehicle via the first communication unit; The control unit transmits a control method for charging the vehicle by the charging device from the second communication unit to the mobile terminal. This allows the user of the charging device to know the charging control method of the charging device via the mobile terminal, improving usability. The control method here includes, for example, the following methods. The first method involves charging for a first hour, which is shorter than the charging time required for full charge, and if there are no waiting vehicles, charging for the first hour is repeated again, and if there are waiting vehicles, charging is terminated and the vehicle waits for charging (this is the control method for the charging control device of Invention 1). The second method is a method in which a maximum power usage is set for charging multiple vehicles simultaneously, and when a charging request is made and charging the vehicle that has been requested to be charged exceeds the maximum power usage, charging of the vehicle that has been requested to be charged is put into standby mode (this is a control method for the charging control device of Invention 2). In the third method, a maximum power usage is set for simultaneous charging of multiple vehicles, and when a new charging request is received while at least one of the multiple vehicles is being charged at a first charging power, if the total power usage exceeds the maximum power usage when charging the new charging-requested vehicle and the vehicle being charged at the first charging power at the first charging power, the vehicle that has requested charging and the vehicle being charged at the first charging power are charged at a second charging power that is lower than the first charging power and causes the total power usage to be less than the maximum power usage (this is the control method of the charging control device of invention 3).The user can use a mobile application or the like to check the control method received from the second server and find a parking lot that uses a method suitable for charging during the current parking period. (1-2) 2A charging control device The second A charging control device is the first A charging control device, the plurality of charging devices belong to any one of a plurality of groups; The control unit can control each group using a different control method, The control unit transmits a plurality of control methods to be performed in each group from the second communication unit to the mobile terminal. This allows the user of the charging device to know the charging control method of the charging device via the mobile terminal and select a charging method that suits the user's wishes, improving usability.

[0191] (2) When one charging device charges multiple vehicles (2-1) 1B charging control device The first B charging control device is a first communication unit capable of communicating with a charging device provided in a parking lot and including a plurality of connectors for electrically charging electrically chargeable vehicles; a second communication unit capable of communicating with a mobile terminal of a user or manager of the vehicle; a control unit that controls charging of the vehicle; Equipped with When the control unit receives a charging request from the mobile terminal via the second communication unit, the control unit instructs the charging device to charge the target vehicle via the first communication unit; The control unit transmits a control method for charging the vehicle by the charging device from the second communication unit to the mobile terminal. This allows the user of the charging device to know the charging control method of the charging device via the mobile terminal, improving usability. The control method here includes, for example, the following methods. The first method involves charging for a first hour, which is shorter than the charging time required for full charge, and if there are no waiting vehicles, charging for the first hour is repeated, and if there are waiting vehicles, charging for the first hour is terminated and the vehicle waits for charging (this is the control method for the charging control device of Invention 1). The second method is a method in which a maximum power usage is set for charging multiple vehicles simultaneously, and when a charging request is made and charging the vehicle that has been requested to be charged exceeds the maximum power usage, charging of the vehicle that has been requested to be charged is put into standby mode (this is a control method for the charging control device of Invention 2). The third method is a method in which a maximum power usage is set for charging multiple vehicles simultaneously, and when a new charging request is made while at least one of the multiple vehicles is being charged at a first charging power, if the total power usage exceeds the maximum power usage when charging the vehicle being charged and the newly requested vehicle at the first charging power, the vehicle that has been requested to be charged and the vehicle being charged at the first charging power are charged at a second charging power that is lower than the first charging power and causes the total power usage to be less than the maximum power usage (this is a control method for the charging control device of Invention 3). In addition, the user can use a mobile application or the like to check the control method received from the second server and search for a parking lot that uses a method suitable for charging during the current parking period. (2-2) Second B charging control device The second-B charge control device is the first-B charge control device, the plurality of connectors belong to any one of a plurality of groups, The control unit can control each group using a different control method, The control unit transmits a plurality of control methods to be performed in each group from the second communication unit to the mobile terminal. This allows the user to know the charging control method of the charging device via the mobile terminal, and allows the user to select a charging method that suits his or her preferences, improving usability.

[0192] (3) Charging system The charging system is a charging system that electrically charges a plurality of vehicles that can be electrically charged in a parking lot, and includes 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 the charging of the vehicles by the charging device, and the charging control device is the first (A, B) or second (A, B) charging control device described above.

[0193] <Other> Each of the first inventions 1 to 5 may have the configuration of other inventions. [Explanation of symbols]

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

Claims

[Claim 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 a parking lot, the charging device having a maximum power usage setting that allows the plurality of vehicles to be charged simultaneously. When the charging time of the vehicle being charged reaches a first hour that is shorter than the charging time required for full charge, charging is temporarily stopped. Charging control device.

Images