Charge control device, charging system, and charge control method

Abstract

To provide a charge control device, etc. which can control a charger not to be overloaded and by which a vehicle is charged in response to a charge request at an early stage.SOLUTION: A charge control device controls charge to a vehicle connected with a charger which charges each of a plurality of vehicles which can be charged at a parking lot, in which the maximum use power which can simultaneously charge the plurality of vehicles is set to the charger, and terminates charge once when charging time of the vehicle on charge reaches first time shorter than charging time when the vehicle is fully charged ("end" of a step S126, S128).SELECTED DRAWING: Figure 15

Description

Technical Field

[0001] The present invention relates to the electric charging of an electrically rechargeable vehicle.

Background Art

[0002] As a technique for charging a vehicle, for example, "a plurality of chargers 2 for charging a vehicle 4 and a charging control unit 3 for controlling the charging current of the charger 2, and obtaining received power information from a wattmeter 10 that measures the received power from commercial power P. A first measurement unit 31a, and a second measurement unit 31b that obtains current / voltage information flowing through a step-down transformer 5b that converts the received high-voltage power into low-voltage power and supplies it to the charger 2. 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 as not to 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 as not to exceed the second set value" is disclosed (for example, Patent Document 1). In this technique, comparison is made in terms of the amount of power when allocating the charging priority. For example, charging is sequentially performed from the vehicle with a shorter travelable distance or a smaller amount of stored charge mounted on the vehicle 4.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the above technique, although the charging device can be controlled so as not to be overloaded, there is a problem that even when the charging request is made earlier, depending on the amount of charge, it may not be charged easily. An object of the present invention is to provide a charging control device or the like that can be controlled so that a charging device does not become overloaded and is charged in response to an early charging request.

Means for Solving the Problems

[0005] The charging control device according to the present invention is a charging device that electrically charges each of a plurality of vehicles that can be electrically charged in a parking lot, and for a charging device in which a maximum power consumption that can simultaneously charge the plurality of vehicles is set, in a charging control device that controls charging to the vehicle connected to the charging device, when the charging time of the vehicle being charged reaches a first time that is shorter than the charging time to full charge, charging is temporarily terminated. The charging control device according to the present invention is a charging device that electrically charges each of a plurality of vehicles that can be electrically charged in a parking lot, and for a charging device in which a maximum power consumption that can simultaneously charge the plurality of vehicles is set, in a charging control device that controls charging to the vehicle connected to the charging device, charging to the vehicle is performed one or more times for a first time that is shorter than the charging time to full charge. The charging control device according to the present invention is a charging device that electrically charges each of a plurality of vehicles that can be electrically charged in a parking lot, and for a charging device in which a maximum power consumption that can simultaneously charge the plurality of vehicles is set, in a charging control device that controls charging to the vehicle connected to the charging device, when the charging time of the vehicle being charged reaches a first time that is shorter than the charging time to full charge, it is determined whether to terminate charging.

[0006] The charging system according to the present invention is a charging system that performs electric charging on a plurality of vehicles that can be electrically charged in a parking lot, and includes a charging device having a plurality of connectors connectable to each of the plurality of vehicles, and a charging control device that controls charging of the charging device to the vehicles, the charging device is set with a maximum power consumption for simultaneously charging the plurality of vehicles, and the charging control device is the charging control device described above. The charging control method according to the present invention is an apparatus for electrically charging each of a plurality of vehicles that can be electrically charged in a parking lot, and for a charging device in which a maximum power consumption that can be charged simultaneously for the plurality of vehicles is set, in a charging control method for controlling charging to the vehicle connected to the charging device, when the charging time of the vehicle being charged reaches a first time that is shorter than the charging time to full charge, the charging is temporarily terminated.

Advantages of the Invention

[0007] According to the above configuration or method, it is possible to control so that the charging facility (distribution board) does not become overloaded, and charging is performed for an early charging request. Furthermore, it is also possible to charge a vehicle for which the charging request was late.

Brief Description of the Drawings

[0008]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27

Figure 28

Figure 29

Figure 30

Figure 31

Figure 32

Figure 33

Figure 34

Figure 35

Figure 36

Figure 37

Figure 38

Figure 39

Figure 40

Figure 41

Figure 42

Figure 43

Figure 44

Figure 45

Figure 46

Figure 47

Figure 48

Figure 49

Figure 50

Figure 51

Figure 52

Figure 53

Figure 54

Figure 55

Figure 56

Figure 57

Figure 58

Figure 59

Figure 60

Mode for Carrying Out the Invention

[0009] <Embodiment> As shown in FIG. 1, the charging system 101 is used in a parking lot of an apartment building such as a condominium or a high-rise building, or a parking lot where a plurality of vehicles can be parked. The charging system 101 performs electric charging on a plurality of vehicles 1 that are parked in the parking lot and can be electrically charged according to a contract or the like. The electrically chargeable vehicle 1 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. Further, the vehicle 1 includes four-wheel vehicles, three-wheel vehicles, two-wheel vehicles, etc. The charging system 101 includes a charging device 103 having a plurality of connectors 131 connectable to each of the plurality of vehicles 1, and a charging control device 105 that controls the charging of the charging device 103 to the vehicle 1. When the vehicle 1 is connected to the connector 131 of the charging device 103 and the charging control device 105 receives an operation (also referred to as a charging request operation) for requesting charging from the owner or user (portable terminal 3), the charging control device 105 gives an instruction for charging to the charging device 103 while considering the power consumption. FIG. 1 shows an overview of the charging system 101. For example, the charging device 103 can be connected to six vehicles 1 and is provided with six connectors 131.

[0010] <First Embodiment 1> 1. Overall Configuration In the charging system 101 of the first embodiment 1, the maximum number of vehicles 1 that can be charged simultaneously is set to 3 as the maximum power used for charging a plurality of vehicles 1 at the same time. That is, the charging power of the vehicle 1 and the maximum number of vehicles 1 that can be charged with the maximum power used are set in advance. Assuming that a new vehicle 1 with a charging request is charged, if the number of charging stations (total power used) is less than (or equal to) the maximum number of stations (maximum power used), the vehicle 1 with the charging request is charged. If the number of charging stations (total power used) is greater than (or more than) the maximum number of stations (maximum power used), the charging of the vehicle 1 with the charging request is put on standby. Also, the charging time for one time is set in advance to the first hour. When one charging is completed, if there is a vehicle 1 in the standby state, it enters the standby state. If there is no vehicle 1 in the standby state, the charging for the first hour is started. In this specification, charging completion means ending the charging in a state of being almost fully charged (a state where it is 90% or more of full charge), and charging end means ending the charging after completing one charging for the first hour. Also, performing recharging after charging end is also referred to as "charging", and the number of times of charging for the first hour is referred to as the "number of charging times". Note that these specific forms are for explaining the embodiment and are not limited to this form.

[0011] 2. Each Part Hereinafter, each device constituting the charging system 101 will be described. (1) Charging Device As shown in FIG. 1, the charging device 103 is connected to the distribution board 2 and receives power supply. The charging device 103 includes a circuit unit 132 that receives power from the distribution board 2 and converts it into a charging voltage, a control unit 133 that controls the charging to the vehicle 1 by instructing the start, end, completion, etc. of charging to the circuit unit 132, and a communication unit 134 that communicates with the 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 from the charging control device 105 via the communication unit 134.

[0012] (2) Mobile terminal 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 an application (hereinafter referred to as "mobile application") capable of communicating with the charging control device 105 is installed. Here, the display unit and the operation unit are constituted by a touch panel unit 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 according to the operations of the user. The storage unit 35 includes a non-volatile storage medium such as a flash memory, and stores, for example, an operating system, programs, applications, and various data for performing various processes. The communication unit 34 performs data communication via a network (e.g., the Internet) using a telephone line or an optical fiber, Bluetooth (registered trademark) communication, Wi-Fi (registered trademark) communication, etc. By executing the mobile application, the mobile application can communicate with the AP server 108, and various information is transmitted and received. The user registers with the AP server 108 via the mobile application, so that the user ID of the user (vehicle 1) is associated (linked) with the connector 131 of the charging device 103 used during charging. When the user connects the vehicle 1 to be used to the connector 131 of the charging device 103, the user performs a charging request operation from the touch panel unit 36 using the mobile application of the mobile terminal 3. When the control unit 33 receives a charging request operation from the touch panel unit 36, it transmits a request (hereinafter referred to as "charging request", see Fig. 7) to the AP server 108 to request charging. When the control unit 33 receives, via the mobile application, a report indicating that charging has started (hereinafter referred to as "charging start report", see Fig. 7), a report indicating that charging has been completed (hereinafter referred to as "charging completion report", see Fig. 9), a report indicating that charging is in standby (hereinafter referred to as "charging standby report", see Fig. 8), a report indicating that one charging cycle has ended (hereinafter referred to as "charging end report", see Fig. 11), a report indicating that charging has started from the standby state (hereinafter referred to as "charging start report", see Fig. 10), etc., it displays the report on the touch panel unit 36. Note that

[0013] (3) Charging control device As shown in Fig. 3, the charging control device 105 is composed of one or more servers, virtual servers, or combinations 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, status data, etc. of the vehicle 1 charged by the charging device 103, and an AP server 108 that functions as a second server that gives charging instructions, etc. to the OCPP server 106 according to a charging request from a user (mobile terminal 3). Note that the charging request data includes, for example, a charging request history, etc., and the status data includes, for example, a charging state, etc. The OCPP server 106, the database 107, and the AP server 108 are configured to be able to communicate with each other, and the OCPP server 106 and the charging device 103 are connected based on OCPP (Open Charge Point Protocol). That is, the charging device 103 is a so-called CP (Charge Point). The OCPP server 106, the database 107, and the AP server 108 are provided on a public cloud such as AWS, Azure, or Google Cloud Platform. Thereby, communication efficiency can be improved. Also, it can be easily implemented. Note that the processing of the server is realized by software processing, but may also be realized by hardware processing using an electric circuit or the like fabricated in the server. Hereinafter, each server and the like will be described.

[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 non-volatile 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 a charging number (reception number) of a charging request, and a status table T12 that stores status data such as a charging state, as shown in FIG. 4. Note that the clock 175 has a calendar function and measures up to the year, month, and day.

[0015] As shown in FIG. 4(a), the charging request table T11 keeps a history of charging requests, and a new record is added to the bottommost row if there is a new charging request. The charging request table T11 stores data such as a "charging number" indicating the reception order of charging requests, a "connector ID" indicating the ID of the connector 131 to which the vehicle 1 to be charged is connected, a "charging result" indicating completion or non-completion of charging, 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 charging requested was completed. Note that when referring to the items in the charging request table T11 and the data stored in the fields of those items, the item may be suffixed with "". For example, when referring to the "charging number", it may mean the item "charging number" in the table or data such as "20230401-3".

[0016] As shown in Fig. 4(b), the status table T12 stores data such as "charging number" which has the same data as the "charging number" in the charging request table T11, "connector ID" which indicates the ID of the connector 131 to which the vehicle 1 to be charged is connected and has the same data as the "connector ID" in the charging request table T11, "charging status" which indicates the charging state, "scheduled end time" which indicates the scheduled end time of one charging of the vehicle 1 for which charging is requested, and "charging times" which indicates the number of times the charging for the first hour has ended. Note that the data stored in the status table T12 is referred to as "status data" and is distinguished from the data stored in the charging request table T11. The scheduled end time of the status table T12 may be the start time. In this case, the time obtained by adding the charging time for one time to the start time is the charging end time. The charging status includes "charging" and "standby" as shown in Fig. 4(b). When referring to the items in the status table T12 and the data stored in the fields of those items, "" may be attached to the item. For example, when referring to "charging number", it may mean the item "charging number" in the table or 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 at 22:20 on April 1 in the state of Fig. 1. In the charging request table T11, as shown in Fig. 4(a), there are charging requests in the order of connector IDs "4", "2", "6", "1", "3", "5", and they are stored in this order. Connector IDs "4" and "2" have completed charging. In the charging request table T11, the "charging result" item shows "completed". Connector IDs "6", "1", and "3" are in the process of charging. In the charging request table T11, the "charging result" item shows "incomplete", and in the status table T12, the "charging status" item shows "charging". Connector ID "5" has a "charging status" of "waiting" in the status table T12, and the "charging result" item in the charging request table T11 shows "incomplete". Note that vehicle 1 connected to connector IDs "2" and "4" remains connected as shown in Figure 1. In this embodiment, the first time, which is the charging time for one cycle, is set to 2 hours as an example. When charging is completed after a total of 4 charges. As shown in Figure 4, the charging with charge number "20230401-3" started at "11:00" (there was a charging request), and after 4 charges of 2 hours each, it was completed at "19:00". The charging with charge number "20230401-5" started the first charge at "16:30" (there was a charging request), and the charging is not completed yet. At the time of "22:20", the second charge has ended, and the scheduled end time of the current charge (the third charge) is "22:30".

[0018] The status table T12 in Figure 5(a) shows the state at 22:40 on April 1 in the state of Figure 1. As shown in the status table T12 in Figure 4(b), the third charge of charge number "20230401-5" ended at "22:30". At that time, since charge number "20230401-8" was "waiting", once the charging ended, as shown in Figure 5(a), the "charging status" became "waiting", and "3" was stored in the "number of charges". Charge number "20230401-8", which was waiting at the time of "22:20" in Figure 4, started the first charge at "22:30" due to the end and waiting of the charge of charge number "20230401-5". Therefore, in Figure 5(a), "0:30" is stored in the "scheduled end time" of charge number "20230401-8", and "0" is stored in the "number of charges". For the charging with the charging number "20230401 - 7", as shown in Fig. 4(a), a charging request was made at "21:10", and "23:10" and "0" are stored in the "Estimated Completion Time" and "Number of Charges" fields of the status table T12.

[0019] The control unit 171 includes a CPU, ROM, RAM, etc. According to the requests from the OCPP server 106 and the AP server 108, it creates a record of a new charging request in the charging request table T11, changes fields, registers (creates) in the status table T12, changes status data, and deletes the record of the completed charging number. Note that 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 server that made the request. Note that the times of the tables T11 and T12 may be obtained on the database 107 side or from the server side.

[0020] (3 - 2) OCPP Server As shown in Fig. 3, the OCPP server 106 includes a control unit 161, a communication unit 162, and a storage unit 163, and executes an OCPP application. Note that the OCPP server 106 is connected to an external settlement system that manages charging by charging, for example, through communication protocols such as OICP (Open InterChange Protocol) and OCPI (Open Charge Point Interface). The control unit 161 includes a CPU, ROM, RAM, etc. The CPU executes the program stored in the storage unit 163 to perform the processing of the OCPP application. The storage unit 163 includes, for example, non - volatile storage media such as HDD, SDD, flash memory, etc., and stores, for example, an operating system for performing various processes, application programs, and various data. The communication unit 162 communicates with the charging device 103 based on OCPP, an international standard, and communicates with the AP server 108 using the WEB-API. The database 107 is provided on a public cloud where the OCPP server 106 is installed, and SQL is used for requests to the database 107.

[0021] As shown in FIG. 7, when the OCPP server 106 receives an instruction to start charging (hereinafter referred to as "charging start instruction") from the AP server 108, it transmits a signal to the charging device 103 to start charging (hereinafter referred to as "charging start signal"), requests the database 107 to register status data indicating the start of charging (hereinafter referred to as "start registration request"), or responds to the AP server 108 that the charging has started normally when the charging starts normally (hereinafter referred to as "charging start response"). When there is a charging start instruction, the OCPP server 106 transmits a signal (hereinafter referred to as "start preparation signal") including the "connector ID" of the charging target to the charging device 103. In response to this, 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 for which the user has requested charging. The instruction (transmission) to start charging to the charging device 103 uses transaction management, and the response signal from the charging device 103 to the charging start signal (start transaction), i.e., the response signal (remote start transaction), is also a "charging normal start signal" indicating that the charging has started normally.

[0022] As shown in FIG. 9, the OCPP server 106 determines whether or not the charging of the vehicle 1 (charging request) being charged has been completed. When it is determined that the charging has been completed, the OCPP server 106 transmits a signal (hereinafter referred to as the "charging completion signal") instructing the charging device 103 to complete the charging, requests the deletion of a record corresponding to the charging completion in the status table from the database 107 (hereinafter referred to as the "status record deletion request"), or responds to the AP server 108 that the charging has been successfully completed when the charging is successfully completed (hereinafter referred to as the "charging completion response"). When the OCPP server 106 determines that the charging has been completed, the OCPP server 106 transmits a signal (hereinafter referred to as the "completion preparation signal") including the "connector ID" of the charging target to the charging device 103. 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. Thereby, it is possible to confirm whether or not the user's vehicle 1 connected to the connector 131 requested for charging by the user has completed charging. The instruction (transmission) of charging completion utilizes transaction management. The response signal transmitted from the charging device 103 in response to the charging completion signal (stop transaction), i.e., the remote stop transaction, is also a "charging successfully completed signal" indicating that the charging has been successfully completed.

[0023] As shown in FIG. 10, the OCPP server 106 determines whether or not charging is possible for a standby charging request (vehicle). When charging is possible, the OCPP server 106 transmits a charging start signal to the charging device 103, requests the database 107 to change the charging status to "charging in progress", or responds to the AP server 108 with a charging start response when the charging is successfully started. The charging here includes both cases where, when a new charging request is made, the vehicle is in a standby state without being charged, and when one charging is completed and the vehicle is in a standby state. Note that the instruction (transmission) to start charging is a response signal transmitted from the charging device 103 using transaction management, similar to the charging start signal (see Fig. 7) when the AP server 108 receives the charging start instruction. The response signal (remote start transaction) for the charging start signal (start transaction) is also a "normal charging start signal" indicating that charging has started normally. To determine whether charging is possible for a pending charging request, it is done based on the "charging status" in the status table T12 of the database 107. Therefore, before the determination, a request to obtain status data is made to the database 107 (hereinafter referred to as "status acquisition request").

[0024] As shown in Fig. 11, the OCPP server 106 determines whether one charging session of a vehicle being charged (charging request) has ended. When it is determined that charging has ended, the OCPP server 106 transmits a signal (hereinafter referred to as "charging end signal") to the charging device 103 to end the charging, requests the database 107 to change the status data due to the end of charging (hereinafter referred to as "end change request"), or responds to the AP server 108 that charging has ended normally when charging ends normally (hereinafter referred to as "charging end response"). Note that the "charging" for the end of charging includes the charging at the time of a new charging request (see Fig. 7) and the charging from the standby state (see Fig. 10). As shown in Fig. 11, when the OCPP server 106 determines that charging has ended, it transmits a signal (hereinafter referred to as "end preparation signal") including the "connector ID" of the charging target to the charging device 103. Upon receiving this, the charging device 103 transmits a response signal indicating that vehicle 1 is being charged at the target connector 131. Thereby, it can be confirmed whether the user's vehicle 1 connected to the connector 131 requested for charging by the user ends charging. The instruction (transmission) to end charging is a response signal transmitted from the charging device 103 using transaction management. The response signal (remote stop transaction) for the charging end signal (stop transaction) is also a "normal charging end signal" indicating that charging has ended normally.

[0025] In this way, the OCPP server 106, by causing the control unit 161, the communication unit 162, and the storage unit 163 to cooperate, as shown in FIG. 7, has a charging start instruction input unit to which a charging start instruction is input from the AP server 108, a charging start signal transmission unit that transmits a signal (which may include a start preparation signal) for causing the charging device 103 to start charging in accordance with the charging start instruction from the AP server 108, a charging normal start signal reception unit that receives a charging normal start signal (including its response signal if a start preparation signal is included) from the charging device 103, a charging start response output unit that outputs a charging start response to the AP server 108 when a charging normal start signal is received from the charging device 103, a start registration request output unit that outputs a start registration request for status data to the database 107, and a start registration response input unit to which a response to the start registration request is input from the database 107. Also, the OCPP server 106, by causing the control unit 161, the communication unit 162, and the storage unit 163 to cooperate, as shown in FIG. 9, has a charging completion determination unit that determines whether the charging of the vehicle with a charging request has been completed, a charging completion signal transmission unit that transmits a signal (which may include a completion preparation signal) for causing the charging device 103 to complete charging when it is determined that charging has been completed, a charging normal completion signal reception unit that receives a charging normal completion signal (including its response signal if a 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 charging normal completion signal is received from the charging device 103, a status record deletion request output unit that outputs a deletion request for a status record to the database 107, and a deletion response input unit to which a response to the record deletion request is input from the database 107. Since the charging completion determination here is made based on the "scheduled end time" and "number of charging times" in the status table T12, it also has an end scheduled time acquisition request output unit that requests the acquisition of status data of the "scheduled end time" and "number of charging times" from the database 107, and an acquisition response input unit to which a response to the acquisition of these status data is input.

[0026] Further, as shown in FIG. 10, by causing the control unit 161, the communication unit 162, and the storage unit 163 to cooperate, the OCPP server 106 includes a chargeability determination unit that determines whether charging is possible for a pending charging request, a charge start signal transmission unit that transmits a signal (including a start preparation signal) for starting charging to the charging device 103 when it is determined that charging is possible, a charge normal start signal reception unit that receives a charge normal start signal (including its response signal when including the start preparation signal) from the charging device 103, a charge start response output unit that outputs a charge start response to the AP server 108 when there is a reception of the charge normal start signal 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 receives a response to the start change request from the database 107. Here, since the chargeability determination is made based on the "charging status" in the status table T12, it also includes a charging status acquisition request output unit that requests the acquisition of status data of the "charging status" from the database 107, and an acquisition response input unit to which responses to these charging status acquisitions are input.

[0027] Further, as shown in FIG. 11, by causing the control unit 161, the communication unit 162, and the storage unit 163 to cooperate, the OCPP server 106 includes a charge end determination unit that determines whether charging of a charging request (vehicle) has ended, a charge end signal transmission unit that transmits a signal (which may include an end preparation signal) for ending charging to the charging device 103 when it is determined that charging has ended, a charge normal end signal reception unit that receives a charge normal end signal (including its response signal when including the end preparation signal) from the charging device 103, a charge end response output unit that outputs a charge end response to the AP server 108 when there is a reception of the charge normal end signal from the charging device 103, an end change request output unit that outputs an end change request for status data to the database 107, and an end change response input unit that receives a response to the end change request from the database 107. Since the charging completion determination here is made based on the "scheduled end time" in the status table T12, it also includes an end time acquisition request output unit that requests the acquisition of the status data of the "scheduled end time" from the database 107, and an acquisition response input unit to which the responses of these status data (scheduled end time) acquisitions are input.

[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 the programs stored in the storage unit 183 to perform the processing of the AP application. The storage unit 183 includes non-volatile storage media such as an HDD, an SDD, a flash memory, etc., 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 performs data communication using a network (for example, the Internet) using a telephone line or an optical fiber, Bluetooth (registered trademark) communication, Wi-Fi (registered trademark) communication, etc. to communicate with the mobile terminal 3. For communication with the database 107, for example, SQL is used. The clock 184 measures the date and time at the time of the charging request, the time when charging started or the elapsed time since charging started, and the time when charging was completed. These measured date and time, etc. are stored in the fields of the charging request table T11 in the database 107. Note that the clock 184 has a calendar function and measures up to the year, month, day, hour, and minute. The AP server 108 receives a charging request from the mobile terminal 3, or transmits a charging start report, a charging completion report, a charging standby report, a (re) charging start report, and a charging end report. The AP server 108 instructs the start of charging (outputs a charging start instruction) to and from the OCPP server 106, and inputs a charging start response, a charging end response, a charging completion response, and a (re)charging start response. The charging start instruction to the OCPP server 106 is made when it is determined whether charging of the vehicle 1 that has received the charging request is possible after receiving a new charging request from the mobile terminal 3, and is performed when charging is possible. The AP server 108 makes requests to the database 107, such as a request to create a new charging request in the charging request table T11, a request to change due to charging completion, a request to obtain status data of the charging state, and a standby registration request to register the standby state.

[0029] As shown in FIGS. 7 and 8, when the AP server 108 receives a charging request from the mobile terminal 3, it requests the database 107 to create a charging request for a new record in the charging request table T11 or requests to obtain the charging state. In response to these requests, a creation response or an acquisition response is made from the database 107. The AP server 108 determines whether charging is possible for the vehicle 1 with a new charging request. When charging is possible (in the case of FIG. 7), it outputs a charging start instruction to the OCPP server 106, and when a charging start response indicating that charging has started normally is input from the OCPP server 106 in response to the charging start instruction, it reports the start of charging to the mobile terminal 3. Also, the AP server 108 determines whether charging is possible for the vehicle 1 with a new charging request. When charging is not possible (in the case of FIG. 8), it requests the database 107 to register status data of "standby" in the status table T12 (hereinafter referred to as "standby registration request"), and when a registration response is input from the database 107 in response to the standby registration request, it transmits a charging standby report to the mobile terminal 3. As shown in FIG. 9, when the AP server 108 receives a charging completion response indicating that charging has been completed normally from the OCPP server 106, it transmits a charging completion report to the mobile terminal 3, outputs a request to change the charging request to the database 107 for the charging request table T11, and inputs a response to the change request. As shown in FIG. 10, when a charging start response indicating that charging has started is input from the OCPP server 106 to the AP server 108 for a vehicle in standby, the AP server 108 transmits a charging start report to the mobile terminal 3. As shown in FIG. 11, when a charging end response indicating that one charging session with a charging time of the first hour has ended is input from the OCPP server 106 to the AP server 108, the AP server 108 transmits a charging end report to the mobile terminal 3.

[0030] In this way, the AP server 108, by causing the control unit 181, the communication unit 182, and the storage unit 183 to cooperate, as shown in FIGS. 7 and 8, includes a charging request receiving unit that receives a charging request from the mobile terminal 3, a chargeability determination unit that determines whether the vehicle 1 of the charging request is chargeable, a charging start instruction output unit that outputs a charging start instruction to the OCPP server 106 when it is determined to be chargeable, a charging start response input unit that receives a charging start response from the OCPP server 106, a charging start report transmission unit that transmits a charging start report to the mobile terminal 3 when there is a charging start response, a charging standby report transmission unit that transmits a charging standby report to the mobile terminal 3 when it is determined to be non-chargeable, a request output unit that outputs a request to create a charging request in the charging request table T11 in the database 107, a request to acquire the charging state of the status table T12, or a request to register in standby in the status table T12 when it is determined to be non-chargeable, and a response input unit that receives the requested response from the database 107.

[0031] Also, the AP server 108, by causing the control unit 181, the communication unit 182, and the storage unit 183 to cooperate, as shown in FIG. 9, includes a charging completion response receiving unit that receives a charging completion response from the OCPP server 106, a charging completion report transmission unit that transmits a charging completion report to the mobile terminal 3 when there is a charging completion response, a request output unit that outputs a request to change the charging request data in the charging request table T11 in the database 107, and a response input unit that receives the requested response from the database 107. Further, as shown in FIG. 10, the AP server 108 includes a charging start response input unit that receives a charging start response for the vehicle 1 waiting from the OCPP server 106 by causing the control unit 181, the communication unit 182, and the storage unit 183 to cooperate, and a charging start report transmission unit that transmits a charging start report to the mobile terminal 3 when there is a charging start response. Further, as shown in FIG. 11, the AP server 108 includes a charging end response input unit that receives a charging end response from the OCPP server 106 by causing the control unit 181, the communication unit 182, and the storage unit 183 to cooperate, and a charging end report transmission unit that transmits a charging end report to the mobile terminal 3 when there is a charging end response.

[0032] 3. Sequence (1) Charging request Taking the case of connecting to the connector 131 with the connector ID of "3" in FIG. 1 as an example. The user connects the vehicle 1 to the connector 131 of "3" and performs a charging request operation on the mobile terminal 3 using the mobile application at "21:10" on April 1, 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 create a charging request for the new charging request. In response to this request, as shown in FIG. 4(a), the database 107 creates a record with the charging number "20230401-7" as a new request in the charging request table T11, registers "3" in the connector ID, "incomplete" in the charging result, and "20230401:2110" in the request date and time, and performs a creation response to the AP server 108.

[0033] (2) Charging start 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 obtain the status data of the charging state, and determines whether charging is possible for the new request from the obtained charging state (status data). (2-1) Charging possible FIG. 12(a) shows the status table T12 before there is a charging request from the charging number "20230401-7" and before performing a charging possibility determination. As described above, when there is a new charging request, the AP server 108 acquires the status data of the charging state from the database 107 and determines whether charging is possible. Here, as shown in Fig. 12(a), the number of charging numbers (vehicle 1) with the charging state of "charging" is 2 (two vehicles), which is less than the maximum number of charging vehicles (here, three vehicles). Therefore, the AP server 108 determines that charging is possible for the charging number "20230401 - 7", which is a new request. When the AP server 108 determines that charging is possible, as shown in Fig. 7, it outputs a charging start instruction to the OCPP server 106. The charging start instruction has a transaction function and becomes a remote start transaction. The charging start instruction includes the data of the "connector ID" for which the charging request was made. Upon receiving the charging start instruction, the OCPP server 106 sends a start preparation signal to the charging device 103. The charging device 103 that has received the start preparation signal checks the connection of the "connector ID" included in the start preparation signal and sends a response signal indicating that it is connected to the OCPP server 106. In response to this, the OCPP server 106 requests the database 107 to start registering in the status table T12 on the assumption that the "connector ID" for which the charging request was made matches the "connector ID" to which vehicle 1 of the charging device 103 is connected. 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 charging times", and responds to the OCPP server 106 with the start registration. As shown in Fig. 7, the OCPP server 106 sends a charging start signal to the charging device 103, and the charging device 103 starts charging the connector 131 with the connector ID of "3", and sends a response signal indicating that charging has started to the OCPP server 106. The response signal is a normal charging start signal and becomes a remote start transaction. When the OCPP server 106 receives the response signal (normal charging start signal), it outputs a charging start response to the AP server 108. Upon receiving this, the AP server 108 reports the charging start to the mobile terminal 3.

[0034] (2-2) Unable to charge Figure 13(a) shows the status table T12 before a charging request is received from the charging number "20230401-8" and before a chargeable determination is made. As shown in FIGS. 7 and 8, when there is a new charging request, the AP server 108 acquires the status data of the charging state. Here, as shown in FIG. 13(a), there are 3 charging numbers (vehicle 1) in the "charging" state, which is the same as the maximum number of charging stations. Therefore, the AP server 108 determines that charging is not possible for the new charging number "20230401-8". When the AP server 108 determines that a new charging request is not chargeable, as shown in FIG. 8, it requests the database 107 to register a standby for charging. In response to this, as shown in FIG. 13(b), the database 107 registers "20230401-8" as the charging number, "5" as the connector ID, and "standby" as the charging state, and responds to the OCPP server 106 with a standby registration. When the AP server 108 receives a standby registration response from the database 107, it reports the charging standby to the mobile terminal 3.

[0035] (2-3) Start charging while on standby The OCPP server 106 determines whether charging is possible for a charging request while on standby. Here, the determination is made based on the number of "charging" stations in the status table T12. For example, in FIG. 5(a), three vehicles with charging numbers "20230401-7", "20230401-6", and "20230401-8" are charging, and vehicle 1 with the charging number "20230401-5" is "on standby". After that, the charging number "20230401-7" finishes charging, and as shown in FIG. 5(b), the charging of vehicle 1 with the charging number "20230401-5" that was on standby starts and the charging state becomes "charging". As shown in FIG. 10, the OCPP server 106 requests the database 107 to obtain the status data of the charging state, and the database 107 responds to this request by sending the status data to the OCPP server 106.

[0036] The OCPP server 106 counts the number of "waiting" in the responded status data and determines whether charging is possible. In FIG. 5(a), if the number of waiting units is "1" and it is after "23:10" when the charging of vehicle 1 with the charging number "20230401-7" ends, the number of charging units becomes 2 for the charging numbers "20230401-6" and "20230401-8", which is less than the maximum number of "3". Therefore, it is determined that charging is possible for vehicle 1 with the charging number "20230401-5" in the "waiting" state. When it is determined that charging is possible, as shown in FIG. 10, the OCPP server 106 outputs a start preparation signal to the charging device 103. The charging device 103 that receives the start preparation signal checks the connection of the "connector ID" included in the start preparation signal and outputs a response signal indicating that it is connected to the OCPP server 106. In response to this, the OCPP server 106 requests the database 107 to start changing the "charging state" and "scheduled end time" of the status table T12 on the assumption that the "connector ID" of the chargeable charging number matches the "connector ID" to which vehicle 1 of the charging device 103 is connected. As shown in FIG. 5(b), the database 107 changes the charging state of the charging number "20230401-5" to "charging" and the scheduled end time to "1:30", and responds with a start registration to the OCPP server 106.

[0037] As shown in FIG. 10, the OCPP server 106 outputs a charging start signal to the charging device 103. The charging device 103 starts charging the connector 131 with the connector ID of "6" and outputs a response signal indicating that charging has started to the OCPP server 106. Note that the response signal is a normal charging start signal and becomes a remote start transaction. When there is an input of a response signal (normal charging start signal), the OCPP server 106 sends a (re)charging start response to the AP server 108. Upon receiving this, the AP server 108 reports the (re)charging start to the mobile terminal 3. Note that for new charging and (re)charging, the same processing is performed between the OCPP server 16 and the charging device 103. The difference lies in that between the OCPP server 106 and the DB 107, new records are registered with information during new charging, and the information in the fields of the records is changed during recharging. Also, between the OCPP server 106 and the AP server 108 and between the AP server 108 and the mobile terminal 3, the difference is that it is made clear 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 completion The OCPP server 106 determines whether charging has been completed. Here, the determination is made based on the "scheduled end time" and the "number of charging times". For example, it is determined by whether the number of charging times (including the completed charging) of vehicle 1 that ended at the scheduled end time matches the "number of charging times" determined as completed. Here, the number of charging times determined as completed is 4 times. For example, in (c) of Fig. 5, the charging with the charging number "20230401 - 5" has already ended "3" times. When the current charging ends, the number of charging times will be "4", and it is determined that the charging is completed. Therefore, as shown in Fig. 9, the OCPP server 106 requests the database 107 that stores the data in the status table T12 to obtain the scheduled end time, etc., including the "scheduled end time" and the "number of charging times" of the charging.

[0039] Upon receiving a request for obtaining the scheduled end time, etc., the database 107 obtains the "scheduled end time" and the "number of charging times" and sends an acquisition response to the OCPP server 106. When it is determined that charging is complete based on the obtained "scheduled end time" and "number of charging times", as shown in FIG. 9, a completion preparation signal is output to the charging device 103. The charging completion signal has a transaction function and becomes a remote stop transaction. In the charging device 103 that has received the completion preparation signal, the "connector ID" included in the completion preparation signal is checked for connection, and a response signal indicating that it is connected is output to the OCPP server 106. In response to this, the OCPP server 106 requests the database 107 to delete the status of the completed charging number on the assumption that the "connector ID" of the charging completion and the "connector ID" to which the vehicle 1 of the charging device 103 is connected match. The database 107 deletes, for example, the record with the charging number "20230401-5" and responds to the OCPP server 106 with the deletion response. Note that when a record is deleted, the records below the deleted record are moved up. The OCPP server 106 outputs a charging completion signal to the charging device 103. The charging device 103 completes the charging for the charging number "20230401-5" and outputs a response signal indicating that the charging has been completed to the OCPP server 106. The response signal is a normal charging completion signal and becomes a remote stop stat transaction.

[0040] When the OCPP server 106 receives the response signal (normal charging completion signal), it sends a charging completion response to the AP server 108. In response to this, the AP server 108 reports the charging completion to the mobile terminal 3. In addition, when the AP server 108 receives the charging completion response, it requests the database 107 to change 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. The database 107 changes the charging result corresponding to the charging number "20230401-5" to "completed" and the charging completion date and time to "20230402:0110" in the charging request table T11 as shown in FIG. 6(a), and responds to the AP server 108.

[0041] (4) Charging End The OCPP server 106 determines whether charging has ended. Here, it is determined by the "scheduled end time". For example, in Fig. 5(a), the scheduled end time of the charging number "20230401-8" is "0:30", and when this time arrives, it is determined that charging has ended. Therefore, as shown in Fig. 11, the OCPP server 106 requests the database 107 that stores the scheduled end time including the "scheduled end time" of charging in the status table T12. When there is a request for obtaining the scheduled end time, the database 107 obtains the "scheduled end time" and responds with the obtained result to the OCPP server 106. When it is determined that charging has ended based on the obtained "scheduled end time", as shown in Fig. 11, an end preparation signal is output to the charging device 103. Note that the charging end signal has a transaction function and becomes a remote stop transaction.

[0042] In the charging device 103 that has received the end preparation signal, the connection of the "connector ID" included in the end preparation signal is confirmed, and a response signal indicating that it is connected is output to the OCPP server 106. Receiving this, the OCPP server 106 requests the database 107 to change the end condition, assuming that the "connector ID" at the end of charging matches the "connector ID" to which the vehicle 1 of the charging device 103 is connected. "End change" includes moving the record of the charged charging number to the lowest position (including the case of deleting the previous records and creating a new record at the lowest position), leaving the "scheduled end time" of the charged charging number blank, adding "1" to the "number of charges", and storing it in the "number of charges" field of the lowest record. For example, the database 107 moves the record with the charging number "20230401-7" in Fig. 5(a) to the bottom as shown in Fig. 5(b), changes the "charging status" to "waiting", and changes the "number of charges" to "1" respectively. As shown in FIG. 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 becomes a remote stop transaction. When there is an input of a response signal (normal charging end signal), the OCPP server 106 transmits a charging end response to the AP server 108, and upon receiving this, the AP server 108 reports the charging end to the mobile terminal 3.

[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. 14. 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 vehicle 1 with the "connector ID" included in the start preparation signal, and transmits a response signal indicating that the check has been made to the OCPP server 106 (S102). Here, there are two types of signals: a normal signal indicating that the connection of vehicle 1 to be charged has been confirmed, and an error signal indicating that the connection could not be confirmed. In the case of an error signal, it is reported to the mobile terminal 3 via the OCPP server 106 and the AP server 108. After that, when the control unit 133 receives a charging start signal from the OCPP server 106 (Yes in S103), it turns on the charging of vehicle 1 with the "connector ID" included in the start preparation signal, and transmits a response signal (normal charging start signal) indicating that the charging has started to the OCPP server 106 (S104).

[0044] In step S105, when the control unit 133 receives a completion preparation signal from the OCPP server 106 (Yes in the figure), it checks the connection of vehicle 1 with the "connector ID" included in the completion preparation signal, and transmits a response signal indicating that the check has been made to the OCPP server 106 (S106). After receiving a charging completion signal from the OCPP server 106 (Yes in S107), the charging of 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 the charging has been completed is transmitted to the OCPP server 106 (S108). In step S107, if there is no input of the response signal (charging normal completion signal) (No), the process proceeds to step S109.

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

[0046] (2) OCPP Server The OCPP server 106 performs various processes by the control unit 161 executing a program. Hereinafter, it will be described using the flowchart of FIG. 15. When the OCPP application starts operating (start in FIG. 15), it is determined whether a charging start instruction has been input from the AP server 108 (S120). If a charging start instruction has been input (Yes), the "connector ID" to be charged is acquired (S121), and after performing the charging start process (S122), the process proceeds to step S123. Here, the charging start instruction includes the "connector ID" of the charging target, and the connector ID is acquired from the charging start instruction. The charging start process in step S122 will be described later. In step S120, if the charging start instruction has not been input ("No"), the process proceeds to step S123.

[0047] In step S123, the number of charging stations N is acquired from the database 107, the variable "K" is set to "1" (S124), and the scheduled end time, etc. of the K-th charging number is acquired (S125). The scheduled end time, etc. here includes at least the "scheduled end time" and the "number of charging times" of the record of the K-th charging number. Next, an end / complete determination is made based on the current time and the scheduled end time (S126). Specifically, as shown in FIG. 17, if the scheduled end time has passed and the number of charging times (including the charged charging) is equal to the number of completed charges (both "Yes" in S1261 and S1262), it is determined as "completed" (S1263), if the scheduled end time has passed and the number of charging times (including the charged charging) is not equal to the number of completed charges (S1261 is "Yes" and S1262 is "No"), it is determined as "ended" (S1264), and if the scheduled end time has not passed (S1261 is "No"), it is determined that charging has not been completed or ended (S1265).

[0048] In step S126, if it is determined as "charging completed" ("completed"), the completion process (S127) is performed and the process proceeds to S130. If it is determined as "charging ended" ("ended"), the end process (S128) is performed and the process proceeds to step S130. If charging has not been completed or ended ("No"), the process proceeds to step S130. The completion process in step S127 and the end process in step S28 will be described later. The determination of the end / completion of step S126 is performed for all the number of charging stations N. That is, it is repeated until the variable "K" becomes the number of charging stations "N". If "K" is not "N" (i.e., "No" in S130), "K" is incremented by 1 (S129), and the process proceeds to step S125. If "K" is "N" (i.e., "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 stations L are acquired from the "charging status" of the database 107. If there are vehicles waiting (i.e., the number of waiting vehicles M is 1 or more) (i.e., "Yes" in S132), the process proceeds to step S133. If there are no vehicles waiting (i.e., "No"), the process proceeds 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 charging request among the waiting vehicles (S134). Specifically, if the numerical value (number of stations) obtained by adding the variable "I" to the number of charging stations "L" is less than the maximum number of stations for which charging is possible (numerical value), it is determined that charging is possible. If it is greater than or equal to the maximum number of stations, it is determined that charging is not possible.

[0050] In step S134, if it is determined that charging is possible for the I-th charging number (of vehicle 1) (i.e., "Yes"), charging start processing (S135) is performed, and the process proceeds to step S136. 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 the number of waiting vehicles M. That is, it is repeated until the variable "I" becomes the number of waiting vehicles "M". If "I" is not "M" (i.e., "No" in S136), "I" is incremented by 1 (S137), and the process proceeds to step S134. If "I" is "M" (i.e., "Yes" in step S136), the process proceeds to step S120.

[0051] (2-1) Charging start processing (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 the charging device 103 ("Yes"), if the response signal is a normal signal (being "normal" in S1223), a start registration request is made to the status table T12 in the database 107 (S1224). When there is a start registration response indicating that the start registration has been completed from the database 107 (being "Yes" in S1225), the process proceeds to step S1226. In step S1226, a charging start signal is transmitted to the charging device 103. In response to this, the charging device 103 starts charging. When a response signal (charging normal start signal) indicating that the charging has started normally is received from the charging device 103 (being "Yes" in S1227), a charging start response indicating that the charging has started normally is output to the AP server 108 (S1228), and the process proceeds to step S123 in FIG. 15. 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 state of the "connector ID" has been confirmed (step S106 in FIG. 14). Note that 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 could not be confirmed. In the OCPP server 106, when a response signal is received in step S1272 (i.e., "Yes"), if the response signal is a normal signal (i.e., "Normal" in S1273), a request is made to the database 107 to delete the status record in the status table T12 (S1274). When there is a deletion response indicating that the deletion from the database 107 is completed (i.e., "Yes" in S1275), the process proceeds to step S1276. In step S1276, a charging completion signal is sent to the charging device 103. Upon receiving this, in the charging device 103, charging is completed. When a response signal (charging normal completion signal) indicating that the charging has been successfully completed is received from the charging device 103 (i.e., "Yes" in S1277), a charging completion response indicating that the charging has been successfully completed is output to the 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 (i.e., "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) End processing (S128) As shown in FIG. 19 (see FIG. 11 for the sequence), in the end processing S128, a termination preparation signal is sent to the charging device 103 (S1281). Note that the termination preparation signal includes the "connector ID" of the charging target. In the charging device 103, a response signal indicating that the connection state of the "connector ID" has been confirmed is sent to the OCPP server 106 (step S110 in FIG. 14). Note that 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 could not be confirmed. In step S1282, when a response signal is received (i.e., "Yes"), if the response signal is a normal signal (i.e., "Yes" in S1283), a request is made to the database 107 to change the end status in the status table T12 (S1284). When there is a response to the end status change from the database 107 (i.e., "Yes" in S1285), the process proceeds to step S1286. In step S1286, a charging end signal is transmitted to the charging device 103. Upon receiving this, when the charging device 103 ends the charging and receives a response signal (charging normal end signal) indicating that the charging has ended normally from the charging device 103 (which is "Yes" in S1287), a charging end response indicating that the charging has ended normally is output to the AP server 108 (S1288), and the process proceeds to step S130 in FIG. 15. In step S1283, when 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 of FIG. 15 is a process to start (re)charging for the standby vehicle 1. On the other hand, the charging start process in step S122 is a process to start the first charging for the vehicle 1 with a new charging request. Therefore, as shown in FIGS. 16 and 20 (the sequence can be referred to in FIGS. 7 and 10), both processes perform similar processes. However, in step S122, a request for start registration is made to the database 107 (refer to steps S1224 to S1225 in FIG. 16), while in step S135, a request for start change is made to the database 107 (steps S1354 to S1355 in FIG. 20), which is different. Also, in step S122, a response of charging start is sent to the AP server 108 (step S1228 in FIG. 16), while in step S135, a response of charging start is sent to the AP server 108 (step S1358 in FIG. 20), which is different. Note that for the description of the flow of the charging start process in step S135 (FIG. 20), except for the above differences, the description of the flow of the charging start process in step S122 can be used.

[0055] (3) Database The processing of the control unit 171 of the database 107 will be described with reference to FIG. 21. When the program starts, if there is a charging request creation request from the AP server 108 (i.e., "Yes" in S140), the control unit 171 creates a new charging request in the bottommost record of the charging request table T11 and sends a creation response (S141), then proceeds to step S142. The charging request creation request includes a "charging number" assigned in the order of reception and a "connector ID" for connecting to the vehicle 1 of the charging request. The control unit 171 registers, for example, "20230401-5", "6", "incomplete", "20230401:1630" in the items of "charging number", "connector ID", "charging result", "request date and time", and "charging completion date and time" of the newly created record (see (a) of FIG. 4). Note that the request date and time may use the clock 175 of the database 107 or may be included in the charging request creation request.

[0056] (3-2) In step S142, if there is a request for registration or deletion registration of status data, etc. (i.e., "Yes"), the control unit registers (stores) in the fields of the bottommost record of the status table T12, deletes the record of the charging request for which charging has been completed, etc., and sends a registration response (S143), then proceeds to step S144.

[0057] (3-2-1) Registration Registration is performed when there is a new charging request. When charging is possible, the registration request is a start registration request (see FIG. 7). For example, the charging number "20230401-7" in (a) of FIG. 6 has a charging request at "21:10". At "21:10" and in the state before the request, as shown in (a) of FIG. 12, two vehicles are being charged, and one more vehicle is in a state where charging is possible. When charging is possible for a new request in this way, charging starts immediately. As shown in (b) of FIG. 12 and as shown in the bottommost record of the status table T12, "20230401-7", "3", "charging", "23:10", and "0" are registered in "charging number", "connector ID", "charging status", "scheduled end time", and "number of charging times". Note that the charging time for one time here is, for example, 2 hours and can be set as appropriate. When charging is not possible, the registration request is a pending registration request (see Figure 8). For example, when there is a new charging request for the charging number "20230401 - 8" at the bottom row in Figure 4(a) at "22:00", at this time, as shown in Figure 13(a), charging is being performed on 3 vehicles 1 and charging is not possible. As shown in Figure 13(b), "20230401 - 8", "5", and "pending" are registered in the "charging number", "connector ID", and "charging status" of the bottom record. Note that the registration request may include data such as "charging number", "connector ID", "charging status", "scheduled end time", and "number of charging times". The "scheduled end time" may be stored on the database 107 side using the time of the clock 175 in the database 107.

[0058] (3 - 2 - 2) Deletion Deletion occurs when charging is completed, as shown in Figure 9. That is, when charging is completed, there is no need to manage the number of charging times, etc. For example, Figure 5(c) shows the status table T12 at "1:00". The charging number "20230401 - 5" has a charging count of "3" times, and the current (4th) charging is scheduled to end at "1:10". When this charging ends, the charging count becomes 4 times and the charging is completed. In Figure 6(b), the record of the charging number "20230401 - 5" is deleted.

[0059] (3 - 3) In step S144, when there is a change request for the charging request table T11 ("Yes"), the corresponding locations ("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 charging request change request is made when the charging request that was in progress is completed. For example, as shown in Fig. 4(a), the charging result of charging number "20230401-5" is "incomplete". However, as shown in Fig. 6(a), when the charging is completed, in the record of charging number "20230401-5", the charging result is changed to "completed", and the charging completion date and time is changed to "20230402:0110".

[0060] (3-4) In step S146, if there is a change request in the status table T12 ("Yes"), the corresponding location in the status table T12 is changed to make a change response (S147), and then proceed to step S148. The change request includes a start change request when starting charging from the standby state (see Fig. 10) and an end change request when one charging is completed (see Fig. 11). For the start change request, for example, as shown in Fig. 5(c), the charging number "20230401-8" is "on standby". When charging is started, as shown in Fig. 6(b), in the record of charging number "20230401-8", the charging status is changed to "charging", and the estimated end time is changed to "3:10". For the end change request, for example, as shown in Fig. 5(a), the charging number "20230401-8" is "charging" and the number of charging times is "0". When charging ends at "0:30", as shown in Fig. 5(c), the record of charging number "20230401-8" moves to the bottom, the charging status is changed to "on standby", the estimated end time becomes blank, and the number of charging times is changed to "1".

[0061] (3-5) In step S148, if there is a status acquisition request ("Yes"), the status data of the corresponding record in the status table T12 is acquired, output to the request destination to make an acquisition response (S149), and then proceed to step S140. For example, for the status acquisition request, all fields in the status table T12 are acquired and transmitted, but only the necessary data may be acquired.

[0062] (4) AP Server When the control unit 181 of the AP server 108 executes a program, the AP application performs various processes. Hereinafter, it will be described with reference to the flowchart of FIG. 22. When the AP application is operating (it is a start), and there is an operation to start charging from the mobile terminal 3 (Yes in step S170), a charging request corresponding to the mobile terminal 3 is created in the charging request table T11 of the database 107 (S171). Specifically, as shown in FIGS. 7 and 8, when a request to create a charging request is made to the database 107 and a new one is created in the charging request table T11, the database 107 responds that it has been created. In step S172, the charging state (status data) is acquired. Specifically, as shown in FIGS. 7 and 8, a request to acquire the charging state of the status table T12 is made to the database 107, and the status data of the charging state is responded from the database 107.

[0063] When the control unit 181 acquires the status data, particularly the charging state, it determines whether it is possible to charge the vehicle 1 with a new charging request (S173). Specifically, the number of charging stations currently in use is acquired (calculated) from the acquired charging state. If the number of charging stations is less than the maximum number of chargeable stations, it is determined as "chargeable", and if the number of charging stations is greater than or equal to the maximum number, it is determined as "not chargeable". In step S173, when it is determined as "chargeable", as shown in FIG. 7, an instruction to start charging is given to the OCPP server 106 (S174). When there is a charging start response indicating that charging has started normally from the OCPP server 106 (Yes in S175), a charging start report is sent to the mobile terminal 3 (S176), and the process proceeds to step S177. In step S173, when it is determined as "not chargeable", a request is made to the database 107 to register in the status table T12 of the database 107 that charging is in a standby state (S178). A charging standby report is sent to the mobile terminal 3 (S179), and the process proceeds to step S177. The standby registration is specifically, as shown in FIG. 8, a request for standby registration is made to the database 107, and when it is registered, the database 107 responds that it has been registered.

[0064] In step S177, when there is a charging completion response from the OCPP server 106 (i.e., "Yes"), as shown in FIG. 9, a charging completion report is sent to the mobile terminal 3 and a charging request change is made to the database 107 respectively (S180, S181), and then it proceeds to step S182. When there is no charging completion response (i.e., "No"), it proceeds to step S182. Specifically, as shown in FIG. 9, for the charging request change, a request to change the charging request is made to the database 107. When the charging request table T11 is changed, a response indicating the change is sent from the database 107. In step S182, as shown in FIG. 10, when there is a charging start response from the OCPP server 106 (i.e., "Yes"), a charging start report is sent to the mobile terminal 3 (S183), and then it proceeds to step S184. When there is no charging start response (i.e., "No"), it proceeds to step S184. In step S184, as shown in FIG. 11, when there is a charging end response from the OCPP server 106 indicating that one charging session has ended (i.e., "Yes"), a charging end report is sent to the mobile terminal 3 (S185), and then it proceeds to step S170. When there is no charging end response (i.e., "No"), it proceeds to step S170.

[0065] <First Embodiment A> As shown in FIG. 17, the charging control device 105 of the first embodiment 1 performs an end process regardless of the presence or absence of a pending charging request when the scheduled end time has elapsed and the number of charging times has not reached the number of charging completions. However, before, at the end, or after the scheduled end time, if there is a pending charging request, the first-hour charging may be ended, and if there is no charging request, the next first-hour charging may be continued. Hereinafter, the main modified parts will be described as the first embodiment A.

[0066] 1. Configuration of the OCPP Server When the charging of the first vehicle 1 is completed, if the charging time of the first vehicle 1 during charging reaches the first hour (including a time equal to or more than one charging time or a time less than one charging time), and there is a second vehicle 1 waiting, the OCPP server will perform charging for the second waiting vehicle for the first hour and end the charging of the first vehicle 1. If there is no waiting vehicle, the OCPP server will continue the next charging session of the first vehicle.

[0067] When the charging is completed or finished, the OCPP server 106A, similar to when the charging of the OCPP server 106 in the first embodiment is completed, causes the control unit 161, the communication unit 162, and the storage unit 163 to cooperate, and includes an end / continue / complete determination unit that determines whether to end the charging, continue the next charging, or complete the charging when the charging for the first hour is completed; a charging end signal transmission unit; a charging normal end signal reception unit; a charging end response output unit; an end change request output unit; an end change response input unit; a start change request output unit for indicating the start of the next charging; a start change response input unit for the start of the next charging; a charging completion signal transmission unit; a charging normal completion signal reception unit; a charging completion response output unit; a status record deletion request output unit; a deletion response input unit; an end scheduled time acquisition request output unit; and an acquisition response input unit. Here, the end / continue / complete determination unit is at least performed based on the "end scheduled time", "number of charging sessions", and "charging status" in the status table T12. Therefore, it includes a data acquisition request output unit that requests the acquisition of status data of "end scheduled time", "number of charging sessions", and "charging status" from the database 107, and an acquisition response input unit to which responses to these data acquisitions are input.

[0068] 2. Flowchart of the OCPP Server (1) Overall The OCPP server 106A causes the OCPP application to perform various processes by the control unit 161 executing a program. The following will be described with reference to the flowcharts in FIGS. 15 and 23. When the OCPP application operates, it starts from step S124 in FIG. 15, performs the processing in FIG. 23, and then proceeds to step S131 in FIG. 15. Thus, the flowchart of the OCPP server 106A has different processing between steps S125 to S130. When the control unit 161 acquires the K-th scheduled end time etc. in step S125, it determines whether the end time of the K-th charging has elapsed (S1261A). In step S1261A, if it is determined that the end time has not elapsed (i.e., "No"), it is considered not ended / complete, and the process proceeds to step S130. In step S1261A, if it is determined that the end time has elapsed (i.e., "Yes"), it determines whether the number of charging requests at the end time (the number including the completed charging) is the number of completed chargings (S1262A).

[0069] In step S1262A, if it is determined that it is the number of completed chargings (i.e., "Yes"), it is considered that full charge has been reached in this charging, and the completion process (S127, see FIG. 18) is performed, and the process proceeds to step S130. Note that the completion process is the same as the process of step S128 in the first embodiment 1. In step S1262A, if it is determined that it is not the number of completed chargings (i.e., "No"), it acquires the status data of all charging states (S1263A). If there is "standby" in the acquired charging state (i.e., "Yes" in S1264A), it is considered that this charging ends, and the end process for this purpose (S128, see FIG. 19) is performed, and the process proceeds to step S130. Note that the end process is the same as the process of step S128 in the first embodiment 1. In step S1264A, if there is no "standby" (i.e., "No"), it is considered that charging continues as it is, and the continuation process for this purpose (S139A) is performed, and the process proceeds to step S130.

[0070] (2) Continuation process The continuation process is a process that maintains the charging state as it is even after the charging in the first hour ends and performs the next charging in the first hour. Fig. 24(a) shows the status table T12A at 1:20 on April 3, for example. The charging with the charging number "20230402-7" is the second charging, and the first hour elapses at "1:30". After that, when the end time "1:30" is passed, there is no new charging request, and the charging for the next first hour is continuously performed as it is. Fig. 24(b) is the status table T12A at 1:40 on April 3, for example. The request number "20230402-7" remains in the "charging" state. The "scheduled end time" stores the scheduled end time of the charging for the next first hour, and the "number of charging times" stores "2", which is obtained by adding "1" to the number of charging times "1" before the first hour has passed. In this way, when the scheduled end time is passed and there is no standby state and continuous processing is performed, the record of the charging number that has passed the scheduled end time (here, "20230402-7") moves to the bottom, and the records of the other charging numbers being charged move up by one.

[0071] As shown in Fig. 25, when the flowchart of the continuous processing starts, it requests the database 107A to change the end of the status table T12A. The end change is the movement of the record of the charging number and the change of the "scheduled end time" and "number of charging times" of the charged charging number. Upon receiving this end change request, when the database 107A makes the change and there is an end change response from the database 107A (which is "Yes" in S1392A), it sends a charging end response to the AP server 108A (S1393A).

[0072] In the first embodiment A, in order to end the charging for the first hour when there is a vehicle 1 in the standby state, the communication volume between the OCPP server 106A and the database 107A can be reduced compared to the case where it ends without a vehicle 1 in the standby state.

[0073] <First Embodiment B> The OCPP server 106 of the first embodiment 1 determines the completion of charging as shown in Fig. 9. However, when an ECU (Electronic Control Unit) 11 capable of communicating with the charging device 103 or the charge control device 105 is mounted on the vehicle 1, when receiving a charge completion signal from the ECU 11 as shown in FIG. 26, it may be determined that the charging is completed. Hereinafter, the main modified parts will be described as the first embodiment B.

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

[0075] 2. Flowchart of OCPP Server In the OCPP server 106B, the control unit 161 executes a program, and the OCPP application performs various processes. Hereinafter, it will be described with reference to the flowcharts of FIGS. 15 and 27. When the OCPP application operates, it performs step S124 from the start in FIG. 15, performs the process in FIG. 27, and then proceeds to step S131 in FIG. 15. In this way, the flowchart of the OCPP server 106B has different processes between steps S125 to S130. When the control unit 161 acquires the Kth scheduled end time or the like in step S125, it determines whether the end time of the Kth charging has elapsed (S126B). In step S126B, if it is determined that the end time has not elapsed (i.e., "No"), it is considered not to be the end, and the process proceeds to step S130. If it is determined that the end time has elapsed (i.e., "Yes"), the end process is performed (S128), and the process proceeds to step S130. In step S130, if K is not equal to the number of charging stations N, "1" is added to K (S129), and the process proceeds to step S125. If K is equal to the number of charging stations N, the process proceeds to step S127B. In step S127B, if the charging completion signal is received from ECU11 (i.e., "Yes"), it is determined that charging is completed, and the completion process is performed (S127), and the process proceeds to step S131. If the signal is not received (i.e., "No"), it is determined that charging is not completed, and the process proceeds to step S131. In the first embodiment B, since the OCPP server 106B does not determine charging completion based on the charging time, it is not necessary to manage the "number of charging times" in the status table T12B, and the communication volume 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 1 determines charging completion and gives a completion instruction. However, the charging device side may perform the charging completion process. Hereinafter, the main modified parts will be 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 the charging itself and reports (transmits) that fact to the OCPP server 106C. When the charging is completed, the charging device 103 includes a charging completion signal receiving unit that receives a charging completion signal indicating that the charging is fully charged from the ECU 11 by the cooperation of the control unit 133, the communication unit 134, and the control unit, a charging completion unit that turns off the charging when receiving the charging completion signal, and a charging normal completion signal transmitting unit that transmits a charging normal completion signal indicating that the charging has been normally completed to the OCPP server 106C when receiving the charging completion signal (or turning off the charging).

[0078] (2) Configuration of the OCPP server As shown in FIG. 26, when the OCPP server 106C receives a charging normal completion signal from the charging device 103C, it outputs a deletion of a status record (status table T12C) for completing the charging and a change request for the charging request (power request table T11C) to the database 107, or receives a response to the deletion request and the change request from the database 107. When the charging is completed, the OCPP server 106C, similar to the first embodiment 1, includes a charging normal completion signal receiving unit that receives a charging normal completion signal from the charging device 103C by the cooperation of the control unit 161, the communication unit 162, and the storage unit 163, a charging completion response unit that responds to the AP server 108C that the charging is completed when receiving the charging normal 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 1, 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 The charging device 103C performs various processes by a dedicated application when the control unit 133 executes a program. Hereinafter, it will be described with reference to the flowcharts of FIGS. 14 and 29. When the application operates, it starts from step S104 in FIG. 14, performs the process in FIG. 29, and then proceeds to step S109 in FIG. 14. In this way, the flowchart of the charging device 103C differs from steps 105 to S108 in FIG. 14. As shown in FIG. 29, when the charging device 103C finishes step S104 and receives a charging completion signal from the ECU 11 at step S105C (i.e., "Yes"), it turns off the charging of the vehicle 1 corresponding to the charging completion signal, transmits a charging normal completion signal to the OCPP server 106C (S108C), and proceeds to step S109. On the other hand, if it does not receive a charging completion signal at step S105C (i.e., "No"), it proceeds to step S109.

[0080] (2) OCPP Server When the control unit 161 of the OCPP server 106C executes a program, the OCPP application performs various processes. The following will be described using the flowcharts in FIGS. 15 and 30. When the OCPP application operates, it starts from step S124 in FIG. 15, performs the process in FIG. 30, and then proceeds to step S131 in FIG. 15. In this way, the flowchart of the OCPP server 106C differs in the processes between steps S125 to S130. When the control unit 161 acquires the K-th scheduled end time, etc. at step S125, it determines whether the end time of the K-th charging has passed (S126C). If it is determined at step S126C that the end time has not passed (i.e., "No"), it is considered not ended and proceeds to step S130. If it is determined that the end time has passed (i.e., "Yes"), it performs an end process (S128) and proceeds to step S130. At step S130, if K is not equal to the number of charging stations N, "1" is added to K (S129), and it proceeds to step S125. If K is equal to the number of charging stations N, it proceeds to step S127C.

[0081] In step S127C, if a charging normal completion signal is received from the charging device 103C (i.e., "Yes"), it is determined that charging has been completed, and completion processing is performed (S127C), then the process proceeds to step S131. If not received (i.e., "No"), it is determined that charging has not been completed, and the process proceeds to step S131. As shown in FIG. 31, the completion processing (S127C) requests the database 107 to delete the status record of the charging number of the vehicle 1 that has completed charging (S1271C). When a deletion response is input (i.e., "Yes" in S1272C), the process proceeds to step S1273C. In step 1273C, the database 107 is requested to change the charging request of the charging number of the vehicle 1 that has completed charging. When a change response is input (i.e., "Yes" in S1274C), the process proceeds to step S1278, and a charging completion response is output to the AP server 108C. In the first embodiment C, in the OCPP server 106C, since charging completion is not performed based on the charging time, it is not necessary to manage the "number of charging times" in the status table T12C. Furthermore, there is no need to transmit and receive a charging completion signal, etc., between the charging device 103C, and the communication volume between the OCPP server 106C and the charging device 103C can be reduced.

[0082] <First Embodiment D> 1. Overall Configuration In the charging system 101 of the first embodiment 1, the determination of the chargeability of the vehicle 1 for which a charging request has been made is performed by comparing the number of charged units with the maximum number of units. In other words, it is determined whether the number of units when assuming that the newly requested vehicle 1 is charged in addition to the number of vehicles being charged is less than the maximum number of units. In the charging system of the first embodiment D, the charging power of the vehicle 1 is registered. When assuming that the vehicle 1 for which a charging request is made is charged to the current charging power consumption, if the total charging power consumption is less than the maximum power consumption, charging is performed on the vehicle 1 for which the charging request is made. If the total charging power consumption is greater than or equal to the maximum power consumption, charging of the vehicle 1 for which the charging request is made is put on standby. Thereby, charging of a plurality of vehicles 1 with different charging powers can be effectively charged within the maximum power consumption. Hereinafter, the first embodiment D will be described, and the differences from the first embodiment 1 will be explained.

[0083] 2. Each part (1) Database As shown in Fig. 32(a), the status table T12D of the first embodiment D newly has an item of "power consumption". In the field of "power consumption", for example, "20" or "15" etc. are stored. Note that "20" means 20kW, and the maximum power consumption of the charging device 13 here is 60kW. That is, in the first embodiment 1, 3 vehicles 1 corresponding to 20kW can be charged, and even if the charging power of 3 vehicles is 15kW, only 3 vehicles can be charged. In contrast, in the first embodiment D, if the vehicle 1 is 15kW, up to 4 vehicles can be charged. As shown in Fig. 32(b), the database 107D (not shown) stores a customer information table T13D having items of "customer ID", "connector ID", and "charging power". For example, a customer with a customer ID of "AAA" is charged by the connector 131 with a connector ID of "1" at a charging power of "20 (kW)". Note that in the first embodiment D, the charging start instruction includes "connector ID" and "power consumption", and the charging device 103D (not shown) that receives the charging start signal is configured to charge with the "power consumption" included in the charging start signal. When communicating and registering with the user's mobile terminal 3, the AP server 108D receives customer information according to the user's operation from the mobile terminal 3 and registers it in the customer information table T13D of the database 107D.

[0084] (2) AP server Similar to the first embodiment 1, in the AP server 108D, when the control unit 181 executes a program, the AP application performs various processes, and in Fig. 22, step S173 is different. When there is an operation to start charging by the user, the AP server 108D creates a new charging request in the database 107D (S170 - S171 in FIG. 22), and as shown in FIG. 27, requests and acquires from the database 107D the status (\"charging state\" and \"power consumption\") and the \"power consumption\" of the \"customer ID\" for which a new charging request has been made (S172D). In step S173D of FIG. 33(a), the AP server 108D adds up the \"power consumption\" of all the vehicles 1 being charged (charging number) and the \"power consumption\" of the new charging request, calculates the total power consumption of all the vehicles 1 when charging including the vehicle 1 of the new charging request, and if the total power consumption is less than the maximum power consumption, determines that charging is possible (\"Yes\"), and if it is greater than or equal to the maximum power consumption, determines that charging is not possible (\"No\"). When it is determined that charging is possible, it proceeds to step S174 in FIG. 22, and when it is determined that charging is not possible, it proceeds to step S178 in FIG. 22. Note that the subsequent processing is the same as that of the first embodiment 1, and the description thereof is omitted. In this way, the AP server 108D includes a total power consumption acquisition (calculation) unit that acquires (calculates) the total power consumption, which is the sum of the power consumption of all the vehicles 1 being charged and the power consumption of the vehicle 1 of the new request, and a chargeable determination unit that determines whether charging is possible based on the total power consumption and the maximum power consumption.

[0085] (3) OCPP Server Similar to the first embodiment 1, in the OCPP server 106D, when the control unit 161 executes a program, the OCPP application performs various processes, and step S134 is different in FIG. 15. When the OCPP server 106D starts the OCPP application and finishes the processing up to step S133, as shown in FIG. 33(b), it acquires all the \"charging states\" of the vehicles currently being charged and the \"power consumption\" of the I-th vehicle waiting. In S1341D, the "power consumption" of all the vehicles 1 (charging numbers) being charged is obtained, and this is added to the "power consumption" of the I-th vehicle on standby. When charging the vehicle 1 on standby, the total power consumption of all the vehicles 1 is calculated. If the calculated power consumption is less than the maximum power consumption, it is determined that charging is possible ("Yes"), and if it is greater than or equal to the maximum power consumption, 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 subsequent processing is the same as that in the first embodiment 1, and the description thereof is omitted. In this way, the OCPP server 106D includes a total power consumption acquisition (calculation) unit that acquires (calculates) the total power consumption, which is the sum of the power consumption of all the vehicles 1 being charged and the power consumption of the vehicle 1 of the new request, and a chargeable determination unit that determines whether charging is possible for the vehicle 1 on standby based on the total power consumption and the maximum power consumption.

[0086] Also in the first embodiment D, the charging device 103 can be controlled so as not to be overloaded. Further, the OCPP server 106D can also handle differences in charging power caused by differences in the battery capacity of the vehicle 1, etc., by including the power consumption during charging in the charging start signal and instructing the charging device 103.

[0087] <Second Embodiment> In the first embodiment, when there is a new charging request that exceeds the maximum power consumption (number of chargeable units) for charging a plurality of vehicles simultaneously, the charging of the new charging request is put on standby without being performed until the charging of the vehicle being charged is completed or terminated without changing the charging power. In the second embodiment, when there is a new charging request that exceeds the maximum power consumption for charging a plurality of vehicles simultaneously, the charging power is reduced to increase the number of chargeable charging units and the charging of the new request is performed. When increasing the number of chargeable units causes the charging power of one unit to be less than or equal to the minimum power, the charging of the new charging request is put on standby without being performed until the charging of the vehicle being charged is completed or terminated. Note that also in this second embodiment, a charging time for one time is set. In the apparatus of the second embodiment, when it has the same configuration as or a similar configuration to the apparatus of the first embodiment, the description and the drawings thereof are omitted. The reference signs may be those of the configuration of the first embodiment, or may be in the 200s while those of the first embodiment are in the 100s. For example, while the reference sign of the charging system of the first embodiment is "101", "201" is used as the reference sign of the charging system of the second embodiment, and by changing the reference signs in FIGS. 1 and 3 to the 200s, the figure also shows the charging system 201 of the second embodiment. In addition, the content described in the first embodiment can be applied to the second embodiment, and even if the reference signs are different for the same apparatus in the first embodiment and the second embodiment, they may have the same configuration.

[0088] <Second Embodiment 1> 1. Overall Configuration The charging system 201 of the second embodiment 1 is different from the charging system 101 of the first embodiment 1 in that the charging power can be changed and the charging device 203 itself performs the charging completion process, and mainly, the differences will be described. The charging system 201 of the second embodiment 1 includes a charging device 203 and a charging control device 205, similarly to the first embodiment 1 (not shown, see FIG. 1). In the charging system 201, the maximum power for simultaneous charging of a plurality of vehicles 1 is set. When charging a newly requested vehicle causes the maximum power to be exceeded, the charging power is reduced for both the charging vehicle and the newly requested vehicle for charging. That is, the maximum power for simultaneous charging is set in advance. If the total power consumption (also referred to as "total power consumption") when assuming charging the requested vehicle 1 with the first charging power is less than the maximum power, the requested vehicle 1 is charged with the first charging power (this charging is referred to as "normal charging"). If the total power consumption is greater than or equal to the maximum power, all charging vehicles 1 including the requested vehicle 1 are charged with a second charging power lower than the first charging power within the maximum power (this charging is referred to as "adjusted charging"). Also, the charging time for one charge is preset to the first hour regardless of the charging power. When one charge is completed, if there is a vehicle 1 in the standby state, it enters the standby state, and if there is no vehicle 1 in the standby state, the charging for the first hour starts (continues). Note that these specific forms are for explaining the embodiments and are not limited to this form.

[0089] 2. Each part Hereinafter, each device constituting the charging system 201 will be described. (1) Charging device The charging device 203 includes a circuit unit 232, a control unit 233, and a communication unit 234 (see FIG. 1). The control unit 233 instructs the circuit unit 232 to start (turn on) charging, complete charging (turn off), etc. at the instructed charging power for the connector 131 instructed from the charging control device 205 via the communication unit 234. As shown in FIG. 39, the charging device 203 performs normal charging or regulated charging on a new vehicle 1 according to a charging start / power change signal from the OCPP server 206, or changes the charging power for another vehicle 1 being charged in response to a new charging request and performs regulated charging. As shown in FIG. 43, the charging device 203 changes the charging power during charging according to a power change signal from the OCPP server 206 and responds to the OCPP server 206 about the change. Also, as shown in FIG. 40, the charging device 203 is connected to the ECU 11 on the vehicle 1 side. When it receives a charging completion signal from the ECU 11, it completes the charging (normal charging or regulated charging) for the vehicle 1 and transmits a charging normal completion signal indicating that the charging has been completed normally to the OCPP server 206. Thus, 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 the charging power has been changed, a charging completion signal receiving unit that receives a charging completion signal from the ECU 11 or the like, 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 for starting charging of the standby vehicle 1, a response signal transmitting unit that transmits a response signal thereto, a power change signal receiving unit that receives a power change signal for changing the charging power, and a power change response signal transmitting unit that transmits a power change response signal indicating that the power has been changed.

[0090] (2) Mobile terminal 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 transmits a charging request to the AP server 208 via a 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 indicating that the charging power is being adjusted (hereinafter referred to as "power adjustment report") in addition to these.

[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 charging request table T21, a status table T22, and the like. Similar to the first embodiment 1, the charging request table T21 stores data such as "charging number", "connector ID", "charging result", "request date and time", "charging completion date and time", etc. (see FIG. 4(a)). As shown in FIG. 34, the status table T22 stores data such as, for example, "charging number", "connector ID", "charging state", "scheduled end time" indicating the scheduled end time of charging in the first hour, and "charging power" indicating the power consumption of the vehicle 1 during charging. Here, the maximum power consumption is set to 50 kW, for example, and the charging powers are, for example, "20" and "15". "20" in FIG. 34(a) indicates the case of charging at the set power (100%), and "15" in FIG. 34(b) indicates the case where the charging power is adjusted, and the 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, only one adjusted power of 75% is assumed. However, if the power exceeds the maximum power consumption during charging at 75%, charging may be performed at a power of 50% of the set power (which is "10" kW in this case). As shown in FIG. 37, FIG. 34(a) shows a state where the total charging power of two vehicles is 40 kW, which is less than the maximum power consumption, so normal charging is being performed. The charging in the first hour is scheduled to end at 20:00 for the charging number "20230401 - 6" and at 20:30 for the charging number "20230401 - 7".

[0092] FIG. 34(b) shows a state where, with respect to the state of FIG. 34(a), there is a new charging request with the charging number "20230401 - 8", and a record with the charging number "20230401 - 8" is added to the status table T22. Assuming that the vehicle 1 is normally charged, the total power consumption when combined with the normal charging of the charging numbers "20230401 - 6" and "20230401 - 7" becomes 60 kW, which exceeds the maximum power consumption. Therefore, an 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, assuming that there is a new charging request with the charging number "20230401-9" for the state of FIG. 34(b) and adjusted charging is performed for this charging request, and adjusted charging for the charging numbers "20230401-6", "20230401-7", and "20230401-8" is added, the total power consumption becomes 60 kW, which is equal to or greater than the maximum power consumption. Therefore, as shown in FIG. 35(a), a record with the charging number "20230401-9" is added to the status table T22 and is in the standby state (shown as "Standby" in the table). Note that, as shown in FIG. 38, for the new charging number "20230401-9", a record is newly added at the bottom of the charging request table T21, and the charging number "20230401-9", the connector ID "3", the charging result "Incomplete", and the request date and time "20230401:1915" are stored respectively.

[0094] As shown in FIG. 37, the charging of the charging number "20230401-6" ends at 20:00. Instead, the charging number "20230401-9" that was in the standby state is adjusted for charging as shown in FIG. 35(b). Assuming that the charging of the charged charging number "20230401-6" is adjusted, and the adjusted charging for the charging numbers "20230401-7", "20230401-8", and "20230401-9" that are already in the adjusted charging process is added, the power consumption exceeds the maximum power consumption. Therefore, it moves to the bottom record and is in the standby state (shown as "Standby" in the table).

[0095] As shown in FIG. 37, the charging of the charging number "20230401-7" ends (completes) at 20:30. Instead, the charging number "20230401-6" that was in the standby state is adjusted for charging. As shown in FIG. 36(a), in the status table T22, the charging state changes from "Standby" to "Charging" and the charging power changes to "15" respectively. Note that 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 as shown in Figure 36(a), the record is deleted in the status table T22.

[0096] After that, as shown in Figure 37, when the charging of the charging number "20230401-6" is completed at 21:30 due to full charge, the vehicle 1 being charged becomes two vehicles with charging numbers "20230401-8" and "20230401-9", and the total power consumption in the case of normal charging is lower than the maximum power consumption, and it is normally charged after 21:30. As shown in Figure 36(b), the charging power is changed from "15" to "20" as shown in Figure 36(c).

[0097] The control unit 271 includes a CPU, a ROM, a RAM, etc. According to the requests from the OCPP server 206 and the AP server 208, it creates / modifies a new charging request in the charging request table T21, and registers / modifies / deletes in the status table T22. Note that when the control unit 271 makes changes, etc. 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 the OCPP application (see Figure 3).

[0099] As shown in Figure 39, when the OCPP server 206 receives a charging start / power change instruction from the AP server 208, it sends a charging start / power change signal to the charging device 203, makes a start registration / power change request to the database 207, and outputs a charging start response to the AP server 208 when the charging starts normally. Note that the "charging" here includes "normal charging" and "regulated charging". The start registration, similar to the first embodiment 1, registers the charging request determined to be chargeable by the charging determination for a new charging request in a new record of the status table T22 with "charging number", "connector ID", "scheduled end time", and "charging power".

[0100] Power change: When it is determined by the charging determination that a new charging request is not chargeable by normal charging but is chargeable by adjusted charging, the "charging power" during charging is changed to the second charging power in the status table T22. For example, in the state of (a) in FIG. 34, there is a new charging request (charging number "20230401-8"), and it is changed from the previous normal charging to adjusted charging, and three devices are charged as shown in (b) of FIG. 34. Note that the charging start / power change instruction signal of the OCPP server 206 includes "charging power" in addition to "charging number" and "connector ID". When there is no power change, it may include only the information of the new charging request, or it may include all "charging numbers", "connector IDs", and "charging powers" during charging, and all charging power changes (existing data remains unchanged) may be performed. In this way, the OCPP server 206, by cooperating the control unit 261, the communication unit 262, and the storage unit 263, includes a charging start / power change instruction input unit, a charging start / power change signal transmission unit, a charging normal start signal reception unit, a charging start response output unit, a start registration / power change request output unit, and a start registration / power change response input unit (refer to the first embodiment 1). Note that in FIG. 39, the display of the transaction is omitted.

[0101] As shown in FIG. 40, when the OCPP server 206 receives a normal charging completion signal from the charging device 203 indicating that the 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 the charging has been completed to the AP server 208. For example, in the state of FIG. 35(b), the charging number "20230401-7" is being adjusted for charging. However, as shown in FIG. 37, when the charging is completed at 20:30, as shown in FIG. 36(a), the record of the charging number "20230401-7" has been deleted. Note that by receiving the normal charging completion signal from the charging device 203, the processing volume can be reduced compared to the OCPP server 106 in the first embodiment 1. In this way, the OCPP server 206, by cooperating the control unit 261, the communication unit 262, and the storage unit 263, includes a normal charging completion signal receiving unit that receives a normal charging completion signal from the charging device 203, a charging completion response output unit that outputs a charging completion response to the AP server 208 when there is a normal charging completion signal 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 that receives a deletion response from the database 207.

[0102] As shown in FIG. 41, the OCPP server 206 determines whether the charging of the charging request (vehicle) has ended. If it is determined that the charging has ended, it sends a charging end signal to the charging device 203 to end the charging, requests the database 207 to change the end status such as the "charging status" in the status table T22, or responds to the AP server that the charging has ended. For example, in the state of FIG. 35(a), the charging number "20230401-6" is being adjusted for charging. However, as shown in FIG. 37, when the charging ends at 20:00, as shown in FIG. 35(b), the charging number "20230401-6" moves to the lowest record, the charging status changes to "waiting", and the charging power becomes blank. In this way, by causing the control unit 261, the communication unit 262, and the storage unit 263 to cooperate with each other, the OCPP server 206 includes a charging end determination unit, a charging end signal transmission unit, a charging normal end signal reception unit, a charging end response output unit, an end change request output unit, and an end change response input unit. Note that the processing at the time of charging end is the same as that in the first embodiment, and in order to determine the charging end, it also includes an end scheduled time acquisition request output unit and an acquisition response input unit.

[0103] As shown in FIG. 42, the OCPP server 206 determines whether it is possible to charge for a standby charging request. If it is possible to charge, the OCPP server 206 transmits a charging start signal to the charging device 203, requests the database 207 to change the start of the "charging state" and "charging power" in the status table T22, and responds to the AP server 208 that charging has started. For example, in the state of FIG. 35(a), the charging number "20230401-9" is in standby, but as shown in FIG. 37, when regulated charging is performed from 20:00, as shown in FIG. 35(b), the charging state of the charging number "20230401-9" is changed to "charging", the end scheduled time is changed to "22:00", and the charging power is changed to "15". In this way, by causing the control unit 261, the communication unit 262, and the storage unit 263 to cooperate with each other, the OCPP server 206 includes a chargeability 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. Note that the processing of whether it is possible to charge for a standby charging request is the same as that in the first embodiment 1, and in order to determine the chargeability, it also includes a charging state acquisition request output unit and an acquisition response input unit.

[0104] As shown in FIG. 43, when charging is completed or ended, the OCPP server 206 determines whether it is possible to change the charging power to the first charging. If it is possible to change, the OCPP server 206 transmits a power change 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 FIG. 36(a), three vehicles 1 are being adjusted for charging. However, as shown in FIG. 37, when the charging with the charging number "20230401-6" is completed at "21:30" and the charging is changed from adjusted charging to normal charging. As shown in FIG. 36(c), the charging powers of the charging numbers "20230401-8" and "20230401-9" are changed to "20". In this way, the OCPP server 206 includes a power (changeable) determination unit that determines whether it is possible to change the charging power to the first charging by cooperating the control unit 261, the communication unit 262, and the storage unit 263; a power change signal transmission unit that transmits a power change signal to the charging device 203 when the power change is possible; a power change response signal reception unit that receives a signal indicating that the change has been made from the charging device 203; 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 response to the change from the database 207. For the determination of the power change here, it is performed based on the "charging status" and "charging power" in the status table T22. Therefore, it also includes a charging status and the like acquisition request output unit that requests the database 207 to acquire status data such as the "charging status", and an acquisition response input unit to which responses to the acquisition of these charging statuses and the like are input. The charging change instruction uses transaction management, and the response signal (change transaction) from the charging device 203 to the power change signal (change transaction) is also a "power change response signal" indicating that the power change has been successfully performed.

[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 the CPU executes a program stored in the storage unit 283 to process the AP application. The AP server 208 receives a charging request from the mobile terminal 3, and transmits a charging start report, a charging completion report (see Fig. 40), a charging standby report (see Fig. 8), a charging end report (see Fig. 41), a charging start report (see Fig. 42), a power change report (see Fig. 43), etc. to the mobile terminal 3. In this way, the AP server 208 makes the control unit 281, the communication unit 282, and the storage unit 283 cooperate with each other, so that the mobile terminal 3 is provided 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] As shown in Fig. 39, when there is a new charging request, the AP server 208 determines whether the vehicle 1 for which the charging request is made can be charged. Here, assuming that the vehicle 1 with the charging request is charged with the same charging power as the vehicle 1 currently being charged (if there is no vehicle currently being charged, it is the charging power of normal charging), if the total power consumption of the vehicle 1 with the charging request and the vehicle 1 currently being charged is less than the maximum power consumption, it is determined that the vehicle 1 with the new charging request can be charged with the same charging power as the vehicle 1 currently being charged (normal charging or regulated charging). On the other hand, when the total power consumption is greater than or equal to the maximum power consumption, if the charging power currently being charged is the first charging power, and if the total power consumption when all of the vehicle 1 that requested the charging and the vehicle 1 currently being charged are charged with the second charging power at the same time is less than the maximum power consumption, it is determined that charging with the second charging power (regulated charging) is possible. If the charging power currently being charged is the second charging power, it is determined that the charging of the new charging request is impossible (in the case of impossibility, it enters a waiting state). The AP server 208 outputs a charging start / power change instruction (see Fig. 39) when it is determined that charging is possible to the OCPP server 206, and inputs a charging start response (including normal charging and regulated charging, see Fig. 39), a charging completion response (see Fig. 40), a charging end response (see Fig. 41), a charging start response (see Fig. 42), a power change response (see Fig. 43), etc. In addition, when charging is performed without entering the standby state for a new charging request, there are normal charging and adjusted charging. The charging start and power change instructions include instructions involving changes in the charging power. In this way, the AP server 208 causes the control unit 281, the communication unit 282, and the storage unit 283 to cooperate with each other, and thus includes a charging determination unit, 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 with respect to the OCPP server 206.

[0107] The AP server 208 requests the creation of a charging request and the acquisition of the charging state from the database 207 at the time of the charging request, requests a change to the charging request at the time of charging completion, and receives responses to these requests. In this way, the AP server 208 causes the control unit 281, the communication unit 282, and the storage unit 283 to cooperate with each other, and thus includes a charging request creation request output unit, a creation response input unit, a charging state acquisition request output unit, an acquisition response input unit, a charging request change request output unit, and a change response input unit with respect to the database 207.

[0108] 3. Sequence The processing different from the first embodiment will be described. Specifically, the processing for a new charging request, the processing of setting the standby state when the determination result of whether charging is possible for the new request is non-chargeable, the processing for the end of charging in the first hour, and the processing of starting charging from the standby state are the same as or substantially the same as those in the first embodiment 1. (1) Charging determination (1-1) Normal charging possible The charging request with the charging number "20230401-7" in FIG. 38 will be described. When there is a charging request, as shown in FIG. 39, the AP server 208 requests the database 207 to acquire the charging state (including the charging power). 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. Assuming that the AP server 208 charges a new charging request at the same "20" kW as the charging power during charging, the total power consumption with the charging power of the charging number "20230401 - 6" becomes 40 kW, which is less than the maximum power consumption of "50 kW". Therefore, it is determined that charging is possible for the vehicle 1 with the charging number "20230401 - 7", which is a new charging request. When the AP server 208 determines that normal charging is possible, as shown in FIG. 39, it transmits a charging start and power change instruction for normal charging to the OCPP server 206. Here, the charging start and power change instruction is the charging number "20230401 - 6" and the charging power "20". In response to this, the OCPP server 206 processes the charging device 203 to perform (normal) charging on the vehicle with the connector ID corresponding to the charging number "20230401 - 6". After this, it is the same as in the first embodiment 1.

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

[0110] Assuming that the AP server 208 charges a new charging request ("20230401 - 8") at the same "20" kW as the charging power during charging, the total power consumption of the three becomes 60 kW, which is equal to or more than the maximum power consumption of "50 kW". Next, assuming that the new charging request ("20230401 - 8") and the charging requests during charging are charged at "15" kW, which is lower than the current charging power, the total power consumption of the three becomes 45 kW, which is less than the maximum power consumption of "50 kW". Therefore, it is determined that the vehicle 1 with the charging number "20230401-8", which is a new charging request, can be adjusted for charging, and the charging power of the charging numbers "20230401-6" and "20230401-7" is changed to "15".

[0111] When the AP server 208 determines that charging is possible with a change in charging power, as shown in FIG. 39, it sends a charging start and power change instruction for adjusted charging to the OCPP server 206. The charging start and power change instruction here includes the charging numbers "20230401-6", "20230401-7", "20230401-8" and the charging power "15". Receiving this, the OCPP server 206 sends a charging start and power change signal to the charging device 203 to perform adjusted charging on the vehicle with the connector ID corresponding to the charging numbers "20230401-6", "20230401-7", "20230401-8". The charging start and power change instruction has a transaction function and becomes a remote start transaction. The charging start instruction includes data on the "connector ID" and its "charging power" of the charging target including a new charging request. The charging device 203 checks the connection of the target "connector ID" and outputs a start preparation response signal indicating that it is connected to the OCPP server 206. Receiving this, the OCPP server 206 requests the database 207 to register the start of adjusted charging and change the charging power on the assumption that the "connector ID" of the charging request matches the "connector ID" to which the vehicle 1 of the charging device 203 is connected.

[0112] In response to the start registration and power change request, the database 207 stores, as a start registration, a new charging request ("20230401-8") and the "charging status", "scheduled end time", and "charging power" in a new record of the status table T22, and as a power change, changes the charging power of the charging numbers "20230401-6" and "20230401-7" that were being charged to "15". Then, after performing the registration and change, it responds to the OCPP server 206 with the start registration and power change. The OCPP server 206 outputs a charging start and power change signal to the charging device 203. The charging device 203 starts (or continues) charging with a charging power of "15" for three vehicles 1 with charging numbers "20230401-6", "20230401-7", and "20230401-8", and outputs a response signal (charging normal start signal) indicating that regulated charging has started to the OCPP server 206. Note that the charging start response signal becomes a remote start transaction. When there is an input of a charging start response signal, the OCPP server 206 transmits a charging start response of regulated charging to the AP server 208. Upon receiving this, the AP server 208 reports the charging start of regulated charging to the mobile terminal 3.

[0113] (2) Charging completion The charging completion of the 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 the charging of the connector ID "1" of the target vehicle 1 and transmits a charging normal completion signal to the OCPP server. Upon receiving this, the OCPP server 206 requests the database 207 to delete the record of the charging number "20230401-6" in the status table T22 as shown in Fig. 36(a). When the database 207 deletes the record, it responds to the OCPP server 0206 to that effect. The OCPP server 206 responds with a charging completion response to the AP server 208. The AP server 208 reports the charging completion to the mobile terminal 3 and requests the database 208 to change the charging result and charging completion date and time of the corresponding charging number in the charging request table T21 for the charging number "20230401-6". The database 207 changes the "charging result" of the record with the charging number "20230401-6" to "completed" and the charging completion date and time to "20230401:2130" in the charging request table T21 as shown in Fig. 38 and responds to the AP server 208.

[0114] (3) Power change When changing the charging power, in the state where normal charging is being performed, when there is a new charging request, for the vehicle with the new charging request and Vehicle 1 that is being normally charged, the charging power is changed to the second charging power to perform adjusted charging; and in the state where adjusted charging is being performed, when the charging of Vehicle 1 being charged is completed, for the remaining vehicles being charged, the charging power is changed to the first charging power to perform normal charging. The change to adjusted charging at the time of a new charging request is performed by the AP server 208 as shown in FIG. 39, and the change to normal charging at the time of charging completion is performed by the OCPP server 206 as shown in FIG. 43. Here, regarding the change at the time of charging completion, the case where the charging number "20230401-6" in FIG. 36 is charged will be described.

[0115] The OCPP server 206 determines the power based on the number of vehicles being charged during power determination, here, the number in the "charging" state, and the charging power. As shown in FIG. 43, the OCPP server 206 requests the database 207 to obtain charging status information including the charging state and charging power, and obtains it. Specifically, as shown in FIG. 36(b), two charging numbers "20230401-8" and "20230401-9" with the charging state being "charging" and the charging power "15" are obtained. The OCPP server 206 calculates the total power consumption when the charging power of the obtained charging numbers is set to "20" (here, it becomes 40 kW). Since the total power consumption is less than the maximum power consumption, even if the charging is changed from adjusted charging to normal charging, it is possible to charge within the maximum power consumption. In this way, when it is determined that the power can be changed, a power change signal is sent to the charging device 203. Specifically, a power change signal including the connector IDs of the charging numbers "20230401-8" and "20230401-9" (here, "6" and "3") and the charging power (here, "20") is sent. In response to this, the charging device 203 performs normal charging with a charging power of "20" for vehicles with connector IDs "6" and "3", and transmits a power change response signal to the OCPP server 206. Note that the transmission and reception of the power change signal and the power change response signal utilize the transaction function.

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

[0117] 4. Flowchart The processing of the control units of each device will be described. For the same processing or substantially the same processing as in other embodiments, the same step numbers are used and the description thereof is omitted. Also, even for the same processing, different step numbers may be used.

[0118] (1) Charging device The processing of the control unit 233 of the charging device 203 will be described with reference to Fig. 44. When the program starts, when the control unit 233 receives a start preparation signal from the OCPP server 206 (Yes in the figure), it checks the connection of vehicle 1 with the "connector ID" included in the start preparation signal, and outputs a response signal (start preparation response signal) indicating that the check has been made to the OCPP server 206 (S102). After receiving a charging start / power change signal from the OCPP server 206 (Yes in S203), for vehicle 1 with the new "connector ID" included in the charging start / power change signal and the vehicle 1 currently being charged, charging is turned on with the "charging power" included in the signal, and a response signal is transmitted to the OCPP server 206 (S204). Note that the charging of vehicle 1 during charging may continue without changing the charging power or may continue after the charging power is changed. If there are no vehicles 1 being charged, charging is turned on for the vehicle 1 with a new charging request with the power value of "charging power".

[0119] In step S205, when a charging completion signal is received from the ECU11 (Yes in the figure), the 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 transmitted to the OCPP server 206 (S206). If a 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 processing as in the first embodiment 1 is performed, and the process proceeds to step S207. In step S207, when a power change signal is received from the OCPP server 206 (Yes in the figure), for the vehicle 1 currently being charged, it is changed to the "charging power" included in the signal, and charging continues. A signal indicating that the charging power has been changed (power change response signal) is transmitted to the OCPP server 206 (S208), and the process proceeds to step S101.

[0121] (2) OCPP Server The OCPP server 206 performs various processes by the control unit 261 executing a program. Hereinafter, it will be described using the flowcharts of FIGS. 45 to 50. When the OCPP application operates (start in FIG. 45), it is determined whether a charging start / power change instruction has been input from the AP server 208 (S220). When a charging start / power change instruction is input (i.e., "Yes"), the charging start / power change process (S221) is performed and the process proceeds to step S223. When no instruction is input (i.e., "No"), the process proceeds to step S223. In step S223, it is determined whether a charging normal completion signal has been received from the charging device 203. If the signal has been received, the completion process (S224) is performed and the process proceeds to step S225. If the signal has not been received (i.e., "No"), the process proceeds to step S225. After that, end determination end process, charging determination charging process, and power determination change process are performed (S225, S226, S227), and the process proceeds to step S220.

[0122] (2-1) Charging start / power change process (S221) The charging start / power change process will mainly be described with reference to FIG. 46 and FIG. 39 showing the sequence. When a charging start / power change instruction is input, the charging start / power change process S221 starts. A start preparation signal is sent to the charging device 203 (S1221). When a response signal is received from the charging device 203 (i.e., "Yes" in S1222), in step S1223, if the response signal is a normal signal (i.e., "normal" in S1223), a start registration / power change is requested from the database 207 to the status table T22 (S2224). When a start registration / power change response is received from the database 207 (i.e., "Yes" in S2225), the process proceeds to step S2226. In step S2226, a charging start / power change signal is sent to the charging device 203. This signal includes at least the "connector ID" of the vehicle 1 that newly starts charging and the "connector ID" and "charging power" of the vehicle 1 that changes the charging power. In response to this, the charging device 203 turns on the charging with the "charging power" included in the signal for the vehicle 1 with the "connector ID" of the new charging request and the vehicle 1 currently under charging, and sends a response signal indicating that charging start and power change have been performed to the OCPP server 206. In step S2227, when a response signal is received from the charging device 203 (i.e., "Yes"), an AP server 208 outputs a charging start response indicating that charging has started normally (and the charging power has been changed normally) (S2228), and the process proceeds to step S223 in FIG. 45. In step S1223, if the received signal is an error signal (i.e., "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 FIG. 45.

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

[0124] (2-3) End determination end process (S225) The end determination end process will be mainly described with reference to FIG. 48 and FIG. 41 showing the sequence. When the process starts, in step S123, the charging count N is obtained from the database 207, the variable "K" is set to "1" (S124), and the scheduled end time of the K-th charging number is obtained (S2251). Next, an end determination is made based on the current time and the scheduled end time (S2252). Specifically, if the scheduled end time has passed (i.e., "Yes"), it is determined as "end", and the end 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 charging count N, "1" is added to K (S129), and the process proceeds to step S2251. If K is equal to the charging count N, the process proceeds to step S226.

[0125] (2-4) Charge Judgment and Charging Process (S226) The charge judgment and charging process will mainly be described with reference to FIG. 49 and FIG. 42 showing the sequence. When the process starts, at step S2260, the charging state is acquired from the database 207, and it is determined whether "waiting" exists in the acquired "charging state" (S2261). Note that the "waiting" state is a state in which the adjustment current of the second charging power is being performed. At step S2261, if it is "waiting" ("Yes"), the number of waiting vehicles M is acquired, the variable "I" = 1, the variable "IW" = 0, and the total power consumption W of all vehicles 1 being charged is calculated (S2262, S2263, S2264). The value obtained by adding the charging power of the I-th waiting vehicle to the variable "IW" for calculating the total charging power is set as "IW", and further, the value obtained by adding the total power consumption W of the vehicles being charged to "IW" is set as "TW" (S2265, S2266). At step S2267, it is determined whether "TW" is less than the maximum power consumption. If it is less, the charging start process is performed on the I-th vehicle 1 waiting (S135). If "TW" is greater than or equal to the maximum power consumption, the process proceeds to step S2268 while remaining waiting without being able to charge. At 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. If the variable "I" is equal to the number of waiting vehicles M, the process proceeds to step S227. Note that the charging start process of step S135 is shown in FIG. 20.

[0126] (2-5) Power Judgment Change Process (S227) The charge judgment and charging process will mainly be described with reference to FIG. 50 and FIG. 43 showing the sequence. When the process starts, at 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 it is determined that the charging power is the second charging power (i.e., "Yes"), the total power consumption TW1 when charging all the vehicles 1 being charged at the first charging power ("20") is calculated (S273), and it is determined whether the calculated total power consumption TW1 is less than the maximum power consumption (S2274). In step S2274, if it is determined that the total power consumption TW1 is less than the maximum power consumption (i.e., "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 for the vehicle 1 currently being charged, continues charging, and sends a signal (power change response signal) indicating that the charging power has been changed to the OCPP server 206. In step S2278, when a power change response signal is received from the charging device 203 (i.e., "Yes"), a request for changing the "charging power" in the status table T22 of the database 207 is made (S2277). If there is a change response indicating that the change has been made from the database 207 (i.e., "Yes" in S2278), a power change response indicating that the change of the charging power has been completed normally is output to the 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. 51. When the program starts, if there is a charging request creation request from the AP server 208 (i.e., "Yes" in S140), the control unit 233 creates a new charging request in the bottommost record of the charging request table T21 and sends a creation response (S141), and then proceeds to step S142.

[0128] In step S142, if there is a request for registration or deletion registration of status data (i.e., "Yes"), registration (storage) is performed in the fields of the bottommost record of the status table T22, or the record of the charging request for which charging has been completed is deleted to perform a registration response (S143), and the process proceeds to step S144. For registration, there is a charging registration (· power change) request at the start of charging (see FIG. 39), and for deletion, there is a status record deletion request at the completion of charging (see FIG. 40). In step S144, if there is a request for change to the charging request table T21 (i.e., "Yes"), the corresponding location in the charging request table T21 is changed to perform a change response (S145), and the process proceeds to step S246. The request for change includes a charging request change request at the completion of charging (see FIG. 40), etc.

[0129] In step S246, if there is a request for change to the status table T22 (i.e., "Yes"), the corresponding location in the status table T22 is changed to perform a change response (S247), and the process proceeds to step S148. The request for change includes a start change request when starting charging from the standby state (see FIG. 42), an end change request when one charging session is completed (see FIG. 41), a power change request when the power is changed (see FIG. 43), etc. In step S148, if there is a request for acquisition of status (i.e., "Yes"), the status data of the corresponding record in the status table T22 is acquired, output to the request destination to perform an acquisition response (S149), and the process proceeds to step S140. For the request for acquisition of status, all fields in the status table T22 may be acquired, or only necessary data may be acquired. There are a charging state acquisition request at the time of a new request (see FIG. 39), an end scheduled time acquisition request for end determination (see FIG. 41), a charging state acquisition request for charging determination and power determination (see FIGS. 42 and 43), etc.

[0130] (4) AP Server When the control unit 281 of the AP server 208 executes a program, the AP application performs various processes. This will be described below with reference to FIGS. 52 and 53. When the AP application is running (started) and there is a charging request operation from the mobile terminal 3 (Yes in step S170), a charging request corresponding to the mobile terminal 3 is created in the charging request table T21 of the database 207 (S171). Specifically, as shown in FIGS. 39 and 8, when a request to create a charging request is made to the database 207 and a new one is created in the charging request table T21, a creation response is received 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, being able to charge includes the case where normal charging with the first charging power is possible and the case where adjusted charging with the second power changed from the first charging power is possible. The determination of charging is based on whether the total power consumption (TW2) when charging the vehicle 1 of the new request with the current charging power is less than the maximum power consumption, as determined from the "charging state" and "charging power" obtained from the database 207. If it is less, it is determined that charging is possible with the current charging power. When the total power consumption (TW2) is greater than or equal to the maximum power consumption, if the current charging power is the first charging power, it is determined that charging is possible with the second charging power with a lower charging power if the total power consumption (TW3) when assuming charging with the second charging power is less than the maximum power consumption. If the total power consumption (TW3) when assuming charging with the second power is greater than or equal to the maximum power consumption, it is determined that charging is impossible. If the total power consumption (TW2) when assuming charging with the current charging power is greater than or equal to the maximum power consumption and the current charging power is the second charging power, it is determined that charging is impossible. Specifically, as shown in FIG. 52, from the acquired "charging state" and "charging power", the total power consumption "TW2" when assuming charging all the vehicle 1 of the new request and the ongoing request with the same charging power as the charging power during charging is calculated (S2731), and it is determined whether the "TW2" is less than the maximum power consumption (S2732).

[0132] In step S2732, if the total power consumption "TW2" is less than the maximum power consumption ("Yes"), it is determined that charging is possible with the charging power during charging. If it is determined in step 2732 that the power consumption is equal to or greater than the maximum power consumption ("No"), and if the current charging power during charging is the first charging power ("Yes" in S2733), the total power consumption "TW3" when assuming that all vehicles 1 of the new request and the request during charging are charged with the second charging power is calculated (S2734), and it is determined whether the "TW3" is less than the maximum power consumption (S2735). If it is determined in step S2735 that the power consumption is less than the maximum power consumption ("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. If it is determined that the power consumption is equal to or greater than the maximum power consumption ("No"), it is determined that charging is impossible. Also, in step S2733, if it is determined that the charging power during charging is not the first charging power (it is the second charging power) ("No"), it is determined that charging is impossible.

[0133] Returning to FIG. 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" to be charged is output to the OCPP server 206. On the other hand, when a charging start response is input from the OCPP server 206 ("Yes" in S275), a charging start report is sent to the mobile terminal 3 (S276). If it is determined in step S273 that "charging is impossible", a standby registration of the status table T22 is requested from the database 207 (S178), a charging standby report is sent to the mobile terminal 3 (S179), and the process proceeds to step S177.

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

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

[0136] In step S184, as shown in FIG. 41, when there is a charging end response from the OCPP server 206 indicating that one charging session has ended (i.e., "Yes"), a charging end report is sent to the mobile terminal 3 (S185), and the process proceeds to step S277. When there is no charging end response (i.e., "No"), the process proceeds to step S277.

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

[0138] <Second Embodiment A> As shown in FIG. 48, when the scheduled end time has elapsed (i.e., "Yes" in step S2252), the charging control device 205 of the second embodiment 1 performs the end process of step S128. That is, as shown in FIG. 41, a charging end signal is sent from the OCPP server 206 to the charging device 203, and upon receiving this, the charging device 203 turns off the charging (step S112 in FIG. 44). However, before, at, or after the end of the scheduled end time, if there is a pending charging request, the charging for the first hour may be ended, and if there is no charging request, the charging for the next first hour may be continued. Hereinafter, the main modified parts will be described 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. Configuration of the OCPP Server When the charging of the OCPP server ends, if the charging time of the first vehicle 1 during charging reaches the first hour (including a time equal to or more than or less than the charging time for one time), when there is a second vehicle 1 waiting, the OCPP server performs charging for the first hour on the waiting second vehicle 1 and ends the charging of the first vehicle 1. If there is no waiting vehicle, the OCPP server continues the next charging session of the first vehicle 1.

[0140] When the charging of the OCPP server 206A ends, similar to when the charging of the OCPP server 206 in the second embodiment is completed, by causing the control unit 261, the communication unit 262, and the storage unit 263 to cooperate, an end / continuation determination unit that determines whether to end the charging or continue the next charging when the charging for the first hour ends, a charging end signal transmission unit when an end determination is made, a charging normal end signal reception unit, a charging end response output unit, an end change request output unit, an end change response input unit, a start change request output unit indicating that the next charging has started when a continuation determination is made, a start change response input unit for the next charging, a charging state etc. (including the scheduled end time) acquisition request output unit, and an acquisition response input unit are provided. In addition, when continuing to charge, it may be configured to transmit a notice to that effect to the mobile terminal 3 via the AP server 208.

[0141] 2. Flowchart of the OCPP server (1) Overall The OCPP server 206A causes the control unit 261 to execute a program, and the OCPP application performs various processes. Hereinafter, it will be described with reference to the flowcharts of FIGS. 45 and 54. When the OCPP application operates, it performs from the start in FIG. 45 to step S224, performs the process (S225A) in FIG. 54, and then proceeds to step S226 in FIG. 45. In this way, the flowchart of the OCPP server 206A differs in the process of S224A. It will be described with reference to FIG. 54. The control unit 261 performs steps S123, S124, S2251 to determine whether the scheduled end time of the K-th charging has passed (S2252A). In step S2252A, when it is determined that the scheduled end time has passed (i.e., "Yes"), it is determined whether there is a second vehicle 1 waiting. If there is a second vehicle 1 waiting (i.e., "Yes" in S2253A), the end process S128 in FIG. 19 is performed. If there is no second vehicle 1 waiting (i.e., "No"), the continuation process S139A is performed. Note that when the end process S128 or the continuation process 139A is performed, the process proceeds to step S130.

[0142] (2) Continuation process (139A) The continuation process 139A is a process for maintaining the charging state as it is even when the charging for the first hour is completed and performing the next charging for the first hour. In the continuation process (139A) shown in FIG. 25 of the first embodiment 1, the charging state in the status table remains "charging", the scheduled end time of the next charging for the first hour is stored in the "scheduled end time", and the value obtained by adding "1" to the "number of charging times" is stored. In the second embodiment A, since the vehicle side (ECU11) performs the charging completion determination, in the status table T22, there is no field for the "number of charging times", and the "scheduled end time of charging" during charging is changed to the "scheduled end time of charging" for the next charging. That is, the content to be changed in step 1391A of FIG. 25 is different from that in the first embodiment A. In this way, in the second embodiment A, since the charging for the first hour is terminated when there is a second vehicle 1 in the standby state, the communication volume between the OCPP server 206A and the database 207A can be reduced compared to the case where it ends in a state where there is no second vehicle 1 in the standby state.

[0143] <Second Embodiment B> In the charging system 201 of the second embodiment 1, when there is a new charging request, the determination as to whether the charging of the new charging request is possible is made in step S273 of FIG. 52 and the flow shown in FIG. 53, but it may be made in other flows. This will be described using FIG. 55 of another example of the process. When the charging state or the like is acquired in step S272 of FIG. 52, as shown in FIG. 55, the total power consumption TW1b in the case where all the vehicles 1 being charged and the vehicle 1 with a new charging request are charged at the first charging power (assuming so) is calculated (S2731B), and the total power consumption TW2b in the case where all the vehicles 1 being charged and the vehicle 1 with a new charging request are charged at the second charging power (assuming so) is calculated (S2732B). In step S2733B, when "TW1b" is less than the maximum power consumption ("Yes"), it is determined that charging is possible at the first charging power without changing the charging power. In step S2733B, when "TW1b" is greater than or equal to the maximum power consumption ("No"), it is determined whether "TW2b" is less than the maximum power consumption (S2734B). In step S2734B, when "TW2b" is less than the maximum power consumption ("Yes") and the charging power during charging is the first charging power ("Yes"), it is determined that charging is possible by changing the charging power to the second charging power, and when the charging power during charging is not the first charging power (that is, when charging is in progress at the second charging power, "No"), it is determined that charging is possible without changing the charging power.

[0144] <Second Embodiment C> 1. Overall Configuration In the charging system 201 of the second embodiment 1, as the charging condition for normal charging, a preset set power (fixed) is used, and the set power is set lower than the maximum power consumption of the charging device. In the charging system of the second embodiment C, charging is performed so as to share the maximum power consumption according to the number of vehicles to be charged. Also in this case, even if there is a new charging request, the maximum power consumption will not be exceeded, and control can be performed so that the charging device does not become overloaded. Hereinafter, the second embodiment C will be described, and the differences from the second embodiment 1 will be described.

[0145] 2. AP Server The AP server 208C has basically the same configuration as the AP server 208 of the second embodiment 1, but the processing of the AP application executed by the control unit is partially different. Similar to the first embodiment of the second embodiment, the AP server 208C performs various processes by the control unit 281C executing a program. In FIG. 52, S273 (FIG. 53) is different. Hereinafter, the process corresponding to FIG. 53 will be described with reference to FIG. 56. When the charging state or the like is acquired in step S272, the number of charging stations N of the vehicle being charged is acquired (S2731C), and the power consumption is calculated by dividing the maximum usage amount by the value obtained by adding "1" for the new charging request to the number of charging stations (S2732C). In step S2733C, if the power consumption is less than the preset minimum power consumption ("Yes"), it is determined that charging is not possible in consideration of charging efficiency. If it is greater than the minimum power consumption ("No"), it is determined that charging is possible with the power consumption. Thus, when the number of charging stations is small, the charging time can be shortened. Note that when it is determined that charging is possible, the charging power of the vehicle 1 being charged is changed.

[0146] 3. OCPP Server Similar to the first embodiment of the second embodiment, the OCPP server 206C performs various processes by the control unit 281C executing a program. S224 and S225 in FIG. 45 are different. In this process, when the charging of one vehicle is completed or terminated, charging is started for one of the waiting vehicles. When the number of charging stations changes due to the completion or termination of charging, charging is performed on the remaining vehicles with the new charging power.

[0147] (1) Completion Process Hereinafter, the process corresponding to S224 will be described with reference to FIG. 57. When the control unit 281C finishes step S2243 in FIG. 47, it acquires the charging state and the like ( S2244C). In step S2244C, it is determined whether there is a "standby". If there is a "standby" (i.e., "Yes"), it is possible to charge with the same charging power as the vehicle 1 that has completed charging (the other vehicle 1 being charged). For the first charging request in standby, charging start processing (S135) is performed, and then return. In step S2245C, if there is no "standby" (i.e., "No"), in step S2247C, the number of charging stations N being charged is obtained. If the obtained number of charging stations is "0" (i.e., "Yes" in step S2248C), then return. In step S2248C, if the number of charging stations is not "0" (i.e., "No"), the power consumption obtained by dividing the maximum power consumption by the number of charging stations N is calculated (S2249C), and a power change signal is sent to charge with the new power consumption (S2275C). After that, steps S2276 to S2279 are performed, and then return (proceed to step S225).

[0148] (2) End processing Hereinafter, the processing corresponding to the end processing S128 in FIG. 48 during the end determination end processing S225 in FIG. 45 (see FIG. 19) will be described with reference to FIG. 58. When the control unit 281C finishes step S1288 in FIG. 19, it acquires the charging state, etc. (S2253C). In step S2254C, it is determined whether there is a "standby". If there is a "standby" (i.e., "Yes"), it is possible to charge with the same charging power as the vehicle 1 that has completed charging (the other vehicle 1 being charged). For the first charging request in standby, charging start processing (S135) is performed, and then return. In step S2254C, if there is no "standby" (i.e., "No"), in step S2256C, the number of charging stations N being charged is obtained. If the obtained number of charging stations is "0" (i.e., "Yes" in step S2257C), then return. In step S2257C, if the number of charging stations is not "0" (i.e., "No"), the power consumption obtained by dividing the maximum power consumption by the number of charging stations N is calculated (S2258C), and a power change signal is sent to charge with the new power consumption (S2275C). Thereafter, steps S2276 to S2279 are performed, and a return is made (proceed to step S225).

[0149] (3) Power determination change process In steps S2247C, S2248C, S2249C, S2275C, S2276 to S2279 within the above completion process, charging determination charging processing and power change processing are performed. Note that if there is a vehicle 1 waiting after charging is completed, it is determined that charging of the waiting vehicle 1 is possible. If there is no vehicle 1 waiting after charging is completed, the number of charging stations decreases, and it is determined that a charging change is possible. In steps S2256C, S2257C, S2258C, S2275C, S2276 to S2279 within the above end process, charging determination charging processing and power change processing are performed. Note that if there is a vehicle 1 waiting after charging is finished, it is determined that charging of the waiting vehicle 1 is possible. If there is no vehicle waiting after charging is finished, the number of charging stations decreases, and it is determined that a charging change is possible. Thus, in the completion process and the end process, since charging determination charging processing and power determination change processing are performed, steps S226 and S227 in FIG. 45 become unnecessary.

[0150] <Third Embodiment> In the first embodiment, the charging control device 105 controls charging of a plurality of vehicles 1 in the same control manner. In the third embodiment, the charging control device groups a plurality of connectors 131 of the charging device 103 so that they can be controlled in different control manners for each group. Note that although not shown in the figure, the reference numeral of the charging control device is "305" to distinguish it from the charging control devices 105 and 205 in other embodiments. Similarly, the reference numerals of the configurations not shown in the third embodiment are also indicated by the 300 series. In the device of the third embodiment, when it has the same configuration or a similar configuration as the device of the first embodiment, the description and the figure thereof are omitted. The step numbers in the flowchart may use the same numbers for the same processing and similar processing as in the first embodiment, or may be in the 3000 series in the third embodiment while the step numbers in the first embodiment are in the 1000 series. In addition, the content described in the first and second embodiments can be applied to the third embodiment. Even if the numbers of the same steps are different between the first and second embodiments and the third embodiment, they may be the same process.

[0151] 1. Overall Configuration Compared with the charging system 101 of the first embodiment, the charging system of the third embodiment is different in that a plurality of connectors 131 are grouped, and the vehicle 1 is charged with different charging methods for each group. Here, for example, the plurality of connectors 131 are divided into two groups. The first group, for example, charges until it reaches full charge (including a charge state of 90% or more of full charge) when charging starts. The second group, for example, charges until the first time or approximately the first time, which is shorter than the charging time to reach full charge, has elapsed when charging starts. That is, the second group is charged by the control method of the first embodiment. In addition, the parking lot of this embodiment is, for example, a parking lot in an apartment building, part of which is open to general users (users not related to the apartment building), and the rest is closed for the residents of the apartment building. 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 which group the plurality of connectors 131 belong to is stored, for example, in the group attribute table of the database 107 with the connector ID and the group attribute (for example, the first or the second) associated. Note that the grouping can be appropriately changed by an administrator or the like.

[0153] 2. Processing Content Also in the third embodiment, similar to the first embodiment, the OCPP server 106 controls the charging of the charging device 103 to the vehicle 1. The OCPP server of the third embodiment has substantially the same configuration as the OCPP server of the first embodiment, but the content of the program executed by the control unit is different. The processing of the control unit will be described below with reference to FIGS. 59 and 60. When the OCPP application is running (which is the start in FIG. 59), it is determined whether a charging start instruction has been input from the AP server 108 (S120). If a charging start instruction 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 the "second group" (S3002). In step S3002, if it is determined that it is the second group ("Yes"), control is performed using the second charging method. Note that the second charging method is the same as the charging method in the first embodiment and corresponds to steps S122 to S136 in FIG. 15. That is, if it is determined that it is the second group, charging for the first hour is started (S122), and the process proceeds to step S123. If it is determined that it is not 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. In steps S131 to S136, charging is performed if the vehicle waiting is chargeable. Note that since steps 122 to S136 are the same as those in the first embodiment, the description thereof is omitted, and also in FIG. 59, the illustration of some steps is omitted.

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

[0155] 3. Others (1) Group In the above description, a plurality of connectors 131 are provided in one charging device 103. However, for example, when one connector 131 is provided in one charging device 103, a plurality of charging devices 103 provided in a parking lot may be grouped. Also, in the above description, the number of groups is two, but it may be three or more. (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 include a control unit corresponding to each group. For example, it may include a first control unit that controls according to a first control method for the first group and a second control unit that controls according to a second control method for the second group, and both control units may process in parallel.

[0156] <Modification Example> The charging systems, charging devices, and charging control devices of the first embodiment (including 1, A to D), the second embodiment (including A to C), and the third embodiment have been described, but the present invention is not limited to these embodiments. For example, the following modification examples may be applicable. Also, combinations of different embodiments, combinations of embodiments and modification examples, and combinations of configurations within modification examples may be possible. In addition, examples not described in the first to third embodiments and modification examples, as well as design changes that do not depart from the gist, are included in the invention according to these embodiments.

[0157] 1. Normal Connection Judgment of Vehicle When the charging control devices 105, 205 (, 305), etc. determine that the vehicle 1 to be charged is not normally connected, they send an error to the mobile terminal 3 as in step S1229 of FIG. 16, step S1279 of FIG. 18, and step S1289 of FIG. 19. The charging devices 103, 203 (, 303) check whether they are electrically connected to the vehicle 1 with the "connector ID" included in the start preparation signal, completion preparation signal, or end preparation signal. If connected, they output a "normal signal", and if not connected, they output an "error" signal. However, the determination may also be made by the following method. Note that the connection determination means is realized by software as in step S1229 of FIGS. 16 and 46, step S1279 of FIG. 18, and step S1289 of FIG. 19.

[0158] (1) Connection determination 1 In the above method, the determination of whether the vehicle 1 to be charged is normally connected (normal connection determination means) is performed on the side of the charging devices 103, 203 (, 303). However, the normal connection determination may also be performed on the side of the OCPP servers 106, 206 (, 306) or the AP servers 108, 208 (, 308). In this case, the charging devices 103, 203 (, 303) output only the connection result of the electrical connection of the vehicle 1 (connector 131) to be charged or all vehicles to the OCPP servers 106, 206 (, 306) and / or the AP servers 108, 208 (, 308). The OCPP server 106, 206 (, 306) or the AP server 108, 208 (, 308) can make a normal connection determination based on whether the "connector ID" of the charging request target is included in the connection result from the charging devices 103, 203 (, 303).

[0159] (2) Connection determination 2 When there is an input of a start preparation signal, a completion preparation signal, or an end preparation signal (the "Yes" in steps S101, S105, S109 of FIG. 14 or the "Yes" in steps S101, S109 of FIG. 44), the charging devices 103, 203 (, 303) confirm the connection of the "connector ID" included in the signal. However, when the normal connection determination is performed on the side of the OCPP server 106, 206 (, 306) or the AP server 108, 208 (, 308), the "connector ID" may not be included in the start preparation signal, the completion preparation signal, or the end preparation signal. For example, when there is an input of a start preparation signal, a completion preparation signal, or an end preparation signal, the charging devices 103, 203 (, 303) check the electrical connections of all the connectors 131, and output the connection results to the OCPP servers 106, 206 (, 306) or the AP servers 108, 208 (, 308). The OCPP servers 106, 206 (, 306) or the AP servers 108, 208 (, 308) determine that it is "normal" if the "connector ID" for which a new charging request has been made is included in the connectors connected in the connection results from the charging devices 103, 203 (, 303), and determine it as "error" if it is not included in the connection results. This can be implemented in this way. In this case, the normal connection determination of the vehicle 1 is performed on the OCPP server 106, 206 (, 306) or the AP server 108, 208 (, 308) side. Note that considering the communication volume, it is preferable to perform the connection determination on the charging device 103, 203 (, 303) or the OCPP server 106, 206 (, 306).

[0160] 2. Chargeability determination (1) Chargeability determination 1 As shown in FIGS. 15, 59, and 60, after obtaining the number of charging stations from the information in the status table, the OCPP 106 (, 306) determines whether charging is possible (step S134). The information in the status table here is all the "charging states" stored in the status table T12. The chargeability determination means is realized by software as in step S134 of FIG. 15 or step S3006 of FIG. 60. However, for the acquisition of the information in the status table, it is only necessary to finally obtain the number of charging stations. For example, it may be all the "charging numbers" in the "charging" state, or it may be the number of stations in the "charging" state. Also, when it is possible to obtain the power consumption used for charging in the charging device 103, the total power consumption during charging may be obtained from the charging device 103. When the power consumption of one vehicle 1 is predetermined, the information in the status table may be the total power consumption currently during charging. In this case, the OCPP server 106 or the AP server 108 can be implemented by making a determination through comparison between the difference between the current power consumption obtained from the charging device 103 and the maximum power consumption, and the power consumption that can be charged to one vehicle 1. Also, the AP server 108 and / or the OCPP server 106 may be equipped with a counter, add "1" each time a charging start response or a charging normal start signal is input, and subtract "1" each time a charging completion response, a charging normal completion signal, or a charging normal end signal is input, and obtain the current number of charging stations according to the number of the counter.

[0161] (2) Chargeability determination 2 As shown in FIG. 53, the AP server 208 determines based on the total power consumption when assuming that all vehicles 1 including the vehicle 1 with a new charging request and the vehicle 1 being charged are charged, and the maximum power consumption. However, when the charging power per unit is set, instead of the total power consumption, it may be determined based on the total number of vehicles being charged and the vehicle with a new charging request, and the maximum number of charging stations obtained by dividing the maximum power consumption by the set power. For example, in the case of the first charging power (for example, "20" kW), the maximum number of charging stations is set to 2, and in the case of the second charging power (for example, "15" kW), the maximum number of charging stations is set to 3, and it may be compared with the number including the vehicle 1 with a new request. Also, when the set charging power is not constant depending on the size of the vehicle (battery), a reference charging power may be set to one unit, and the number of vehicles may be calculated. For example, when the set power of 20 kW is used as the reference charging power, a vehicle with a set power of 30 kW is regarded as 30 / 20 = 1.5 units, and a vehicle with a set power of 15 kW is regarded as 15 / 20 = 0.75 units, and the total number of units may be calculated.

[0162] 3. Standby In the second group in the first, second, and third embodiments, after a new charging request and the end of charging in the first hour, the system waits in the lowest record of the status tables T12 and T22. That is, it is registered at the end of the charging standby. This enables charging in the order of charging requests and ensures fairness.

[0163] 4. The first hour (1) The first hour is not particularly limited as long as it is shorter than the charging time (full charge time) from 0% to 100% of the battery charge. Preferably, it is 10 - 40% of the full charge time, and more preferably 10 - 30% of the full charge time. If the first hour is short, the number of charging times in the first hour increases, but it is difficult to improve the charge amount. Conversely, if the first hour is long, the charge amount for one charge can be ensured, but many vehicles cannot be charged. The above first hour varies depending on the capacity of the vehicle's battery, but preferably, it is a time that ensures charging sufficient to travel about 30 - 100 km. This enables travel to a nearby electric station. (2) The first hour may be set to a fixed time that does not change by the administrator (management company) of a parking lot such as an apartment building, or may be automatically set to vary according to the time zone. As an example of variation by time zone, in a time zone when there are few vehicles parked in the parking lot, for example, from 10:00 to 16:00, the first hour may be set longer, and in other times, since there are more vehicles, the first hour may be set shorter. (3) In the second group of the first and third embodiments, after the first hour has elapsed, if there are no waiting vehicles, the charging for the first hour is started again, and it is determined whether there are any waiting vehicles after the first hour has elapsed (after the end process ("S128" in FIG. 15)) ( "S132" in FIGS. 15 and 59). However, during the re - charging for the first hour (for example, when half of the first hour has elapsed), it may be determined whether there are any waiting vehicles. If there is a vehicle, the re - charging for the first hour is terminated, and if there are no waiting vehicles, the re - charging for the first hour is continued. (4) In the second embodiment, it is determined whether or not the device is in standby after the scheduled end time of the first hour has elapsed (\"S2253A\" in FIG. 54), but it may also be determined whether or not the device is in standby before the scheduled end time has elapsed.

[0164] 5. Others (1) In the signal transmission and reception between the OCPP servers 106, 206 (, 306) and the charging devices 103, 203 (, 303), a transaction is used, but it is not necessary to use a transaction. Note that using a transaction can prevent malfunction. Examples of malfunctions include cases where a normal charging start signal is not transmitted even though charging is in progress, and cases where charging is performed without a charging start report being sent to the mobile terminal 3. (2) The charging systems 101, 201 (, 301) include the charging devices 103, 203 (, 303) and the charging control devices 105, 205 (, 305), but it may be a charging device that combines a charging unit corresponding to the charging device and a charging control unit corresponding to the charging control device into one. Also, a device in which the OCPP servers 106, 206 (, 306) (control units 161, 261 (, 361)) of the charging control devices 105, 205 (, 305) are incorporated into the charging devices 103, 203 (, 303) may be used as the charging device. (3) OCPP is used for the communication between the charging devices 103, 203 (, 303) and the OCPP servers 106, 206 (, 306) (first servers), but other protocols may be used. (4) The AP servers 108, 208 (, 308) receive charging requests from the mobile terminal 3, but they may receive them by other methods. For example, a card storing identification information such as a vehicle ID may be received from the charging device 103, 203 (, 303) or an external reader. (5) The mobile terminal 3 has an application corresponding to the AP servers 108, 208 (, 308), but for example, it may communicate with the AP (WEB-API) using an application (front-end) operating on a browser. (6)In the first and second embodiments, the maximum power consumption (maximum number of charging stations) was set in advance, but it may be settable by the manager of an apartment building or the like. Further, when the power consumption of the apartment building can be used, the maximum power consumption may be automatically or manually set to be increased during the time periods when the power consumption of each household in the apartment building decreases. The time periods when the power consumption decreases are, for example, from 0 to 5 o'clock, from 10 to 16 o'clock, and from 21 to 24 o'clock. (7)The OP servers 108, 208 (, 308) are currently reporting various information to the mobile terminal 3 via email or the like, but may report by push notification. (8)In the first and second embodiments, as an example of the parking lot, the parking lot of an apartment building was described, but it may be a commercial facility, a sports facility such as a stadium or a soccer field, a spectator / entertainment facility such as a concert venue, a medical facility such as a hospital, or a parking lot of a company or the like (hereinafter sometimes referred to as a "general parking lot"). In the parking lot of the third embodiment, as an example of the parking lot, a parking lot of an apartment building with a partially open area was described, but it may be a parking lot of a company, a hospital, or the like with a partially open area, or a parking lot of an apartment building or the like where the first group is for residents with a large daily driving distance, the second group is for residents with a small daily driving distance, and the third group is for non-residents, etc. This can provide a more convenient parking lot. (9)In the first to third embodiments, the completion of charging has not been described other than full charge (including a charge state corresponding to full charge), but it may be completed by a completion signal from the mobile terminal 3, the charging device 103, or the like. Upon completion, store the charging completion date and time of the corresponding record in the charging request table, delete the corresponding record in the status table, and move up the records lower than the said record. (10)In the first to third embodiments, the association between the vehicle 1 and the charging device 103 has not been specifically described, but 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 the determined charging device 103 to request charging. This is often the case for use by specific people in the parking lot of an apartment building or a monthly parking lot, for example. Alternatively, the vehicle 1 to be charged to the charging device 103 is not determined. For example, the vehicle 1 may be connected to an available charging device 103, and a charging request may be made from the mobile terminal 3 or the like using the device number, QR code (registered trademark), barcode, etc. of the charging device 103. For example, it is often used by unspecified people in commercial facilities, sports facilities, coin parking, etc. (11) In the first to third embodiments, as the information transmitted from the AP servers 108, 208 (, 308) to the mobile terminal 3, the charging start report, charging standby report, charging completion report, charging end report, power change report, etc. have been described, but other information may be transmitted. Other information includes, for example, the charging fee due to charging, the charging rate (degree of charge) of the vehicle, the order in the standby state, etc. Note that these information may be made available for confirmation by accessing the URL of the Internet in addition to the mobile application.

[0165] The above embodiments disclose at least the following inventions. Each invention is not limited to the first to third embodiments and the modified examples, and includes Inventions 1 to 5 even if there are examples not described therein or design changes within the scope not departing from the gist.

[0166] In the technology of Patent Document 1, it is possible to control so that the charging device does not become overloaded, but there is a problem that even when the charging request is made earlier, depending on the amount of charge, it may not be charged easily. An object of the present invention is to provide a charging control device or the like that can control so that the charging device does not become overloaded and is charged for an early charging request.

[0167] <Invention 1> (1) The first charging control device and the first charging control method The first charging control device is a charging device that charges each of a plurality of vehicles that can be electrically charged in a parking lot, and for a charging device in which a maximum power consumption that can simultaneously charge the plurality of vehicles is set, in the charging control device that controls charging to the vehicle connected to the charging device, when the charging time of the vehicle being charged reaches a first time that is shorter than the charging time to full charge, charging is once terminated. The first charging control method is a method for controlling charging to a vehicle connected to a charging device that charges each of a plurality of vehicles that can be electrically charged in a parking lot, and for a charging device in which a maximum power consumption that can simultaneously charge the plurality of vehicles is set, in the charging control method that controls charging to the vehicle connected to the charging device, when the charging time of the vehicle being charged reaches a first time that is shorter than the charging time to full charge, charging is once terminated. Thereby, a plurality of vehicles can be charged without exceeding the maximum power consumption. Further, since charging is performed on a plurality of vehicles in a first time shorter than full charge, compared with the case where one vehicle is fully charged and then other vehicles are fully charged, although the amount of charge is low, many vehicles can be charged. That is, a plurality of vehicles can be evenly charged in a short charging time.

[0168] (2) Second charging control device and second charging control method The second charging control device is a charging device that charges each of a plurality of vehicles that can be electrically charged in a parking lot, and for a charging device in which a maximum power consumption that can simultaneously charge the plurality of vehicles is set, in the charging control device that controls charging to the vehicle connected to the charging device, charging to the vehicle is performed one or more times for a first time that is shorter than the charging time to full charge. The second charging control method is a method for controlling charging to a vehicle connected to a charging device that charges each of a plurality of vehicles that can be electrically charged in a parking lot, and for a charging device in which a maximum power consumption that can simultaneously charge the plurality of vehicles is set, in the charging control method that controls charging to the vehicle connected to the charging device, charging to the vehicle is performed one or more times for a first time that is shorter than the charging time to full charge. Note that "performed one or more times" may be "performed repeatedly". As a result, a plurality of vehicles can be charged without exceeding the maximum power consumption. Further, since the plurality of vehicles are charged in a first time shorter than the full charge time, compared with the case where other vehicles are fully charged after one vehicle is fully charged, although the amount of charge is lower, many vehicles can be charged. That is, a plurality of vehicles can be evenly charged in a short charging time, and the amount of charge of all vehicles can be gradually increased.

[0169] (3) Third charging control device and third charging control method The third 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 for a charging device in which a maximum power consumption that can simultaneously charge the plurality of vehicles is set, in a charging control device that controls charging to the vehicle connected to the charging device, when the charging time of the vehicle being charged reaches a first time shorter than the charging time to full charge, it is determined whether to end the charging. The third charging control method is a charging control method for a charging device that electrically charges each of a plurality of vehicles that can be electrically charged in a parking lot, and for a charging device in which a maximum power consumption that can simultaneously charge the plurality of vehicles is set, in a charging control method that controls charging to the vehicle connected to the charging device, when the charging time of the vehicle being charged reaches a first time shorter than the charging time to full charge, it is determined whether to end the charging. As a result, a plurality of vehicles can be charged without exceeding the maximum power consumption. Further, since the plurality of vehicles are charged in a first time shorter than the full charge time, compared with the case where other vehicles are fully charged after one vehicle is fully charged, although the amount of charge is lower, many vehicles can be charged. That is, a plurality of vehicles can be evenly charged in a short charging time. Note that the determination may be realized by software processing or may be realized by hardware processing using an electric circuit or the like.

[0170] (4) Fourth charging control device When there is a new charging request in the first to third charging control devices, if the total power consumption when charging the vehicle with the new charging request exceeds the maximum power consumption, the charging of the vehicle with the new charging request is put on standby. Thereby, charging of a plurality of vehicles can be performed within the maximum power consumption. In the standby state, when there are a plurality of vehicles waiting for charging, it may be registered at the end of the vehicles waiting for charging. Also, the charging waiting may be prioritized for new charging requests. For example, when there are a plurality of vehicles waiting for the charging in the first hour to be completed more than once and there is no vehicle that has become a new charging request and is waiting, it is registered at the front (first) of the charging waiting, and when there are a plurality of vehicles that are new charging requests and are waiting, it may be registered at the end of them. From the viewpoint of fairness, it is preferable to register in ascending order of the time of the new request and the time when the charging in the first hour is completed.

[0171] (4A) The 4A charging control device The 4A charging control device is in the first to third charging control devices, a charging request receiving means for receiving a charging request of the vehicle (for example, corresponding to step S170 in FIG. 22), a first charging control means for controlling charging for the vehicle with the new charging request, a first number acquisition means for acquiring the number of charging stations of the vehicle being charged (for example, corresponding to step S172 in FIG. 22) and includes When the number of charging stations acquired by the first number acquisition means is less than the maximum number that can be charged within the range of the maximum power consumption, the first charging control means charges the vehicle with the new charging request (for example, "Yes" in step S173, corresponding to S174), and when the acquired number of charging stations is greater than or equal to the maximum number, the vehicle with the new charging request is put on standby (for example, "No" in step S173, corresponding to S181).

[0172] (4B) The 4B charging device The 4B charging control device is in the 4A charging control device, Among the plurality of vehicles, a second charging station number acquisition means for acquiring the number of charging stations that are being charged (for example, corresponding to step S131 in FIG. 15), a second charging control means for controlling charging for the vehicle in the standby state, and further includes: When the number of charging stations acquired by the second charging station number acquisition means is less than the maximum number, the second charging control means charges at least one of the vehicles in the standby state (for example, corresponding to "Yes" in step S134 of FIG. 15). (4C) Charging control device of 4C In the charging control device of 4C, when the charging of one of the vehicles that was being charged is completed or the charging for the first hour ends in the charging control device of 4B, charging is started for one of the vehicles in the standby state. Thereby, it is possible to charge the vehicle in the standby state without exceeding the maximum power consumption.

[0173] (5) Fifth charging control device In the first to third charging control devices, when there is a new charging request during charging of at least one of the plurality of vehicles with the first charging power, and the total power consumption when charging the vehicle being charged and the vehicle that made the new charging request with the first charging power exceeds the maximum power consumption, for the vehicle that made the new charging request and the vehicle being charged with the first charging power, charging is performed with a second charging power that is less than the maximum power consumption and lower than the first charging power. Thereby, charging of a plurality of vehicles can be performed within the maximum power consumption. The second charging power is preferably within the range of 40 to 80% of the first charging power, and more preferably within the range of 40 to 70% of the first charging power. If the ratio is small, it becomes possible to charge many vehicles, but it is difficult to improve the charging amount. If the ratio is large, the charging amount can be improved, but at the same time, the number of vehicles that can be charged simultaneously decreases.

[0174] (5A) Charging control device of 5A The charging control device of 5A is in the first to third charging control devices. Charging request receiving means for receiving a charging request of the vehicle (for example, corresponding to step S170 in FIG. 52), first charging control means for controlling charging for the vehicle with a new charging request, first power acquisition means for acquiring the charging power of the vehicle being charged (for example, corresponding to step S272 in FIG. 52) and comprises, the first charging control means, when there is a new charging request during charging for at least one of the plurality of vehicles, and the total power consumption when charging the vehicle being charged and the vehicle with the new charging request with the charging power during charging exceeds the maximum power consumption, and when the charging power during charging is the first charging power, if the total power consumption when charging the vehicle being charged and the vehicle with the new charging request with a second charging power lower than the first charging power is less than the maximum power consumption, the vehicle with the new charging request is charged with the second charging power. Thereby, charging of a plurality of vehicles can be performed within the maximum power consumption. The second charging power is preferably within the range of 40 to 80% of the first charging power, and more preferably within the range of 40 to 70% of the first charging power. If the ratio is small, it becomes possible to charge many vehicles, but it is difficult to improve the charging amount. If the ratio is large, the charging amount can be improved, but at the same time the number of vehicles that can be charged simultaneously decreases. (5B) Charging control device of 5B The charging control device of 5B is the charging control device of 5A, second number acquisition means for acquiring the number of vehicles being charged (for example, corresponding to step S2260 in FIG. 49), second charging control means for controlling charging for the vehicle in the standby state, and further comprises, When the total power consumption when charging the charging vehicles acquired by the second charging control means and the waiting vehicles with the second charging power is less than the maximum power consumption, at least one of the waiting vehicles is charged with the second charging power (for example, "Yes" in steps S2262 to S2267 and S135 in FIG. 49 are applicable). (5C) Charging control device of 5C In the charging control device of 5C, when the charging of one of the vehicles being charged in the charging control device of 5B is completed or the charging for the first hour ends, charging is started for one of the waiting vehicles. As a result, it is possible to charge the waiting vehicles without exceeding the maximum power consumption.

[0175] (6) Charging control device of 6 The charging control device of 6 is in the charging control devices of 1 to 5, The charging device includes a plurality of connectors for connecting to each of the plurality of vehicles, The plurality of connectors belong to any of a plurality of groups, The charging control device can be controlled by different control methods for each group. As a result, it is possible to perform highly versatile charging control in a parking lot where a plurality of vehicles park. (7) Charging control device of 7 The charging control device of 7 is in the charging control device of 6, It has a communication unit that receives a charging request to the vehicle from a mobile terminal, The control method is transmitted to the mobile terminal via the communication unit. As a result, a user using the charging device can know the charging control method of the charging device via the mobile terminal, and the usability can be improved.

[0176] (8) Charging control device of 8 The charging control device of 8 is in the charging control devices of 4B, 4C, 5B, and 5C, 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 and comprising The first charging control means is executed by an application executed by the second server. Thereby, the first charging control means can be provided without making a major change to the first server. Also, since the server is used to control the charging device to end charging at the first time, etc., the burden on the user can be reduced when the charging device manages the end of charging. That is, when managed by the charging device, once charging is completed, in order to reset the charging request, the connector 131 is once removed from the vehicle 1 or the user makes a new charging request from the mobile terminal 3, but when managed by a program (software) using the server, the user's reset operation becomes unnecessary.

[0177] (9) Ninth charging control device The ninth charging control device is in the fourth B, fourth C, fifth B, and fifth C charging control devices 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 and comprising The first charging control means is executed by an application executed by the first server or the second server, The second charging control means is executed by an application executed by the first server or the second server. Thereby, the communication volume between the first server and the second server can be reduced. Also, since the server is used to control the charging device to end charging at the first time, etc., the burden on the user can be reduced when the charging device manages the end of charging. That is, when managed by the charging device, once charging is completed, in order to reset the charging request, the connector 131 is once removed from the vehicle 1 or the user makes a new charging request from the mobile terminal 3, but when managed by a program (software) using the server, the user's reset operation becomes unnecessary.

[0178] (10) Charging system A charging system is a charging system that charges a plurality of vehicles that can be electrically charged in a parking lot. The charging system includes a charging device having a plurality of connectors connectable to each of the plurality of vehicles, and a charging control device that controls charging of the charging device to the vehicles. The charging device has a maximum power consumption set for simultaneously charging the plurality of vehicles, and the charging control device includes first to seventh charging control devices. Thus, a plurality of vehicles can be charged without exceeding the maximum power consumption.

[0179] <Invention 2> In the technology of Patent Document 1, it is possible to control the charging of vehicles so that the capacity of the power receiving facility does not become overloaded. However, there is a problem that it is necessary to provide a first measurement unit and a second measurement unit, which makes the equipment complicated. An object of Invention 2 is to provide a charging control device and the like that can control the charging device so as not to become overloaded without providing a measurement unit or the like.

[0180] (1) Charging control device The first charging control device is a device that charges each of a plurality of vehicles that can be electrically charged in a parking lot. For a charging device having a maximum power consumption set for simultaneously charging the plurality of vehicles, in the charging control device that controls the charging of the vehicle connected to the charging device, when charging the vehicle that has made a charging request causes the maximum power consumption to be exceeded, the charging of the vehicle that has made the charging request is put on standby. Thus, a vehicle can be charged without exceeding the maximum power consumption. The second charging control device, in the first charging control device, when the charging of one of the vehicles charging within the range of the maximum power consumption is completed, starts charging one of the vehicles in the standby state. Thus, a plurality of vehicles can be efficiently charged without exceeding the maximum power consumption. The third charging control device, in the second charging device, the one vehicle in the standby state is the vehicle with the longest standby time. Thus, a plurality of vehicles can be charged fairly. (2) Charging system A charging system is a charging system that performs electric charging on a plurality of vehicles that can be electrically charged in a parking lot. The charging system 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 charging device to the vehicles. The maximum power consumption for simultaneously charging the plurality of vehicles is set in the charging device. The charging control device is any one of the first to third charging control devices described above. This enables charging of a plurality of vehicles without exceeding the maximum power consumption. (3) Charging control method A charging control method is a device that charges each of a plurality of vehicles that can be electrically charged in a parking lot. For a charging device in which the maximum power consumption for simultaneously charging the plurality of vehicles is set, in a charging control method for controlling the charging of the vehicle connected to the charging device, when charging the vehicle that has made a charging request causes the maximum power consumption to be exceeded, the charging of the vehicle that has made the charging request is put on standby. This enables charging of a plurality of vehicles without exceeding the maximum power consumption.

[0181] <Invention 3> In the technology of Patent Document 1, it is possible to control the charging of a vehicle so that the capacity of the power receiving facility does not become overloaded, but there is a problem that it is necessary to provide a first measurement unit and a second measurement unit, and the equipment becomes complicated. The object of Invention 3 is to provide a charging control device or the like that can control the charging device so as not to become overloaded without providing a measurement unit or the like.

[0182] (1) Charging control device The first charging control device is a device for electrically charging each of a plurality of vehicles that can be electrically charged in a parking lot. For a charging device in which a maximum power consumption for simultaneously charging the plurality of vehicles is set, in the charging control device that controls charging to the vehicles connected to the charging device, when a new charging request is received while at least one of the plurality of vehicles is being charged with a first charging power, if charging the newly requested vehicle with the first charging power in addition to the vehicle being charged results in the total power consumption exceeding the maximum power consumption, then for the vehicle with the new charging request and the vehicle being charged with the first charging power, charging is performed with a second charging power that is less than the maximum power consumption and lower than the first charging power. Thereby, charging can be performed without exceeding the maximum power consumption. The second charging control device, in the first charging control device, when charging of one of the vehicles being charged with the second charging power is completed, if charging the remaining vehicles being charged with the second charging power with the first charging power results in less than the maximum power consumption, then the charging power of the remaining vehicles being charged with the second charging power is returned to the first charging power for charging. Thereby, the charging time for the remaining vehicles can be shortened. The third charging control device, in the second charging control device, when a new charging request is received while charging is being performed with the second charging power, if charging the vehicle with the new charging request with the second charging power in addition to the vehicle being charged with the second charging power results in the total power consumption exceeding the maximum power consumption, then charging of the vehicle with the new charging request being charged with the second charging power is put on standby. Thereby, a plurality of vehicles can be charged according to the charging requests. (2) Charging system A charging system is a charging system that performs electric charging for a plurality of vehicles that can be electrically charged in a parking lot. The charging system includes a charging device having a plurality of connectors connectable to each of the plurality of vehicles, and a charging control device that controls charging of the charging device to the vehicles. The charging device has a maximum power consumption for simultaneously charging the plurality of vehicles set therein, and the charging control device is any one of the first to third charging control devices described above. Thereby, a plurality of vehicles can be charged without exceeding the maximum power consumption. (3) Charging control method The charging control method is an apparatus for electrically charging each of a plurality of vehicles that can be electrically charged in a parking lot, and for a charging device in which a maximum power consumption for simultaneously charging the plurality of vehicles is set, in a charging control method for controlling the charging of the vehicle connected to the charging device, when a new charging request occurs while charging at least one of the plurality of vehicles with a first charging power, in addition to the vehicle being charged with the first charging power, if charging the newly requested charging vehicle with the first charging power would cause the total power consumption to exceed the maximum power consumption, then for the newly requested charging vehicle and the vehicle being charged with the first charging power, charge with a second charging power that is less than the maximum power consumption and lower than the first charging power. Thereby, it is possible to charge a plurality of vehicles without exceeding the maximum power consumption.

[0183] <Invention 4> In Patent Document 1, a technique for controlling the charging current of a plurality of chargers is described, but in a parking lot provided with a plurality of chargers, there is a problem of low versatility. Invention 4 aims to provide a highly versatile charging control device and the like.

[0184] (1) When one charging device charges one vehicle (1-1) First A charging control device and first A charging control method The first A charging control device is a charging control device for controlling the charging of a vehicle connected to a charging device, for a plurality of charging devices provided in a parking lot and for electrically charging a vehicle that can be electrically charged, the plurality of charging devices belong to any of a plurality of groups, the charging control device can perform different controls for the charging devices for each group. The first A charging control method is a charging control method for controlling the charging of a vehicle connected to a charging device, for a plurality of charging devices provided in a parking lot and for electrically charging a vehicle that can be electrically charged, the plurality of charging devices belong to any of a plurality of groups, The charging control method enables different controls for the charging devices for each group. This makes it possible to perform highly versatile charging control in a parking lot where a plurality of 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, the control of charging until full charge (including a charge state of 90% or more of full charge) when charging is started, etc. Also, the controls may be different or the same for each group. Further, the settings of the different controls can be appropriately made by the administrator of the charging control device, can be changed according to the usage status of the parking lot, and can further improve versatility.

[0185] (1-2) Second A charging control device and second A charging control method The second A charging control device is the first A charging control device in which the plurality of groups include at least a first group and a second group. The charging control device In the first group, it controls so that the vehicle connected to the charging device belonging to the first group is charged to full charge or a charge equivalent to full charge. In the second group, it controls to perform charging for a first time shorter than the charging time to full charge for the vehicle connected to the charging device belonging to the second group. The second A charging control method is the first A charging control method in which the plurality of groups include at least a first group and a second group. The charging control method In the first group, it controls so that the vehicle connected to the charging device belonging to the first group is charged to full charge or a charge equivalent to full charge. In the second group, it controls to perform charging for a first time shorter than the charging time to full charge for the vehicle connected to the charging device belonging to the second group. As a result, for example, in a parking lot, it becomes possible to control the charging devices of the first group to be open and available for vehicles without a contract, and to control the charging devices of the second group to be closed and available for vehicles with a contract, thereby increasing the degree of freedom in the use of the parking lot. In the parking lot of an apartment building, for example, the first group is for visitors to the residents of the apartment building or for the general public with no relation to the apartment building, and the second group is for the residents of the apartment building. A general-purpose parking lot is a parking lot where a vehicle can be parked and charged. For example, the first group may be a group where anyone can use the charging device for a fee for general use, and the second group may be a group where a contract holder can use the charging device for a fee. Also, in a general-purpose parking lot, for example, the user may be able to select between the first group and the second group for using the charging device. As a result, for example, when traveling a long distance after charging, charging can be performed using the charging device of the first group, and when traveling a short distance after charging, charging can be performed using the charging device of the second group, thereby increasing the options for the user. Note that the control of the first group is, for example, control to perform charging until full charge (including a charge state of 90% or more of full charge) when charging is started, and the control of the second group is the control of the charging control device in Invention 1.

[0186] (2) When one charging device charges a plurality of vehicles (2-1) The first B charging control device and the first B charging control method The first B charging control device is a charging control device that controls charging to a vehicle connected to the connector for a charging device provided in a parking lot and having a plurality of connectors for electrically charging an electrically chargeable vehicle, wherein the plurality of connectors belong to any of a plurality of groups, the charging control device is capable of different control for each group in the control of charging performed via the connector. The charging control method of 1B is a charging control method for controlling the charging of a vehicle connected to a connector of a charging device provided in a parking lot and having a plurality of connectors capable of electric charging, in which the plurality of connectors belong to any of a plurality of groups, and in the charging control performed via the connector, different controls can be performed for each group. Thereby, it becomes possible to perform highly versatile charging control in a parking lot where a plurality of vehicles park. Here, different controls include, for example, the control of the charging control device in Invention 1, the control of the charging control device in Invention 2, the control of performing charging until full charge (including a charge state of 90% or more of full charge) when charging is started, etc. Also, the controls for each group may be different or the same. Further, the setting of different controls can be appropriately performed by the administrator of the charging control device, can be changed according to the usage situation of the parking lot, and the versatility can be further improved.

[0187] (2-2) The 2B charging control device and the 2B charging control method The 2B charging control device is the 1B charging control device in which the plurality of groups include at least a first group and a second group, and the charging control device in the first group, controls so that the vehicle connected to the connector belonging to the first group is charged to full charge or a charge equivalent to full charge, and in the second group, controls so that charging is performed for a first time shorter than the charging time required to fully charge the vehicle connected to the connector belonging to the second group. The 2B charging control method is the 1B charging control method in which the plurality of groups include at least a first group and a second group, and the charging control method in the first group, controls so that the vehicle connected to the connector belonging to the first group is charged to full charge or a charge equivalent to full charge, In the second group, control is performed to charge a vehicle connected to a connector belonging to the second group for a first hour, which is shorter than the charging time required to fully charge the vehicle. As a result, for example, in a parking lot, it becomes possible to control the connector of the first group to be open for non-contracted vehicles and the connector of the second group to be closed for contracted vehicles, thereby increasing the degree of freedom in the use of the parking lot. In the parking lot of an apartment building, for example, the first group is for visitors to the residents of the apartment building or for general use not related to the apartment building, and the second group is for the residents of the apartment building. A general parking lot is a parking lot where a vehicle can be parked and charged. For example, the first group may be a group where anyone can use the connector for a fee for general use, and the second group may be a group where a contractor can use the connector for a fee. Also, in a general parking lot, for example, the user may be allowed to select between the first group and the second group for using the charging device. As a result, for example, when traveling a long distance after charging, charging can be done using the connector of the first group, and when traveling a short distance after charging, charging can be done using the connector of the second group, thereby increasing the options for the user. Note that the control of the first group is, for example, control to charge until full charge (including a charge state of 90% or more of full charge) when charging is started, and the control of the second group is the control of the charging control device in Invention 1.

[0188] (3) Charging system A charging system is a charging system that performs electric charging on a plurality of vehicles that can be electrically charged in a parking lot, and includes a charging device having a plurality of connectors connectable to each of the plurality of vehicles, and a charging control device that controls the charging of the charging device to the vehicles. The charging control device is the charging control device of the first (A, B) or second (A, B) above.

[0189] <Invention 5> Patent Document 1 describes a technique for controlling the charging current of a plurality of chargers, but information regarding charging is not displayed, making it difficult to say that it is user-friendly for the person using (charging with) the charger. The fifth invention aims to provide a charging control device and the like that are user-friendly for the person using the charging device.

[0190] (1) When one charging device charges one vehicle (1-1) The first A charging control device The first charging control device includes: a first communication unit capable of communicating with a plurality of charging devices provided in a parking lot and capable of electrically charging a vehicle; a second communication unit capable of communicating with a mobile terminal of the user or administrator of the vehicle; a control unit for controlling the charging of the vehicle; and when the control unit receives a charging request from the mobile terminal via the second communication unit, it instructs the charging device to charge the target vehicle via the first communication unit; the control unit transmits the charging control method of the charging device to the vehicle to the mobile terminal from the second communication unit. Thereby, the user using the charging device can know the charging control method of the charging device via the mobile terminal, improving the usability. Here, the control methods include, for example, the following methods. The first method is to charge for a first time shorter than the charging time until full charge, and if there is no waiting vehicle, charge again for the first time. If there is a waiting vehicle, end the charging and wait for charging (this is the control method of the charging control device of Invention 1). The second method is that the maximum power consumption for simultaneously charging a plurality of vehicles is set. When charging the vehicle that has made the charging request would exceed the maximum power consumption when a charging request is received, the charging of the vehicle that has made the charging request is put on standby (this is the control method of the charging control device of Invention 2). In the third method, the maximum power for simultaneous charging of a plurality of vehicles is set. When a new charging request is received while at least one of the plurality of vehicles is being charged with the first charging power, if charging both the vehicle being charged and the vehicle that has made the new charging request with the first charging power would cause the total power consumption to exceed the maximum power for use, then for the vehicle with the new charging request and the vehicle being charged with the first charging power, charging is performed with a second charging power that is less than the first charging power and for which the total power consumption is less than the maximum power for use (this is the control method of the charging control device of Invention 3). Note that the user can use a mobile application or the like to check the control method received from the second server, and can search for a parking lot that uses a method suitable for the charging to be performed during the current parking. (1-2) Charging control device of 2A The charging control device of 2A is the charging control device of 1A, where the plurality of charging devices belong to one of a plurality of groups, the control unit can perform control using different control methods for each group, the control unit transmits the plurality of control methods performed in each group from the second communication unit to the mobile terminal. As a result, the user who uses the charging device can, via the mobile terminal, know the charging control method of the charging device, can select a charging method that conforms to the user's intention, and the usability is improved.

[0191] (2) When one charging device charges a plurality of vehicles (2-1) Charging control device of 1B The charging control device of 1B includes a first communication unit capable of communicating with a charging device provided in a parking lot and having a plurality of connectors for electrically charging an electrically chargeable vehicle, a second communication unit capable of communicating with a mobile terminal of the user or administrator of the vehicle, and a control unit for controlling the charging of the vehicle and is provided with when the control unit receives a charging request from the mobile terminal via the second communication unit, it instructs the charging device to charge the target vehicle via the first communication unit, The control unit transmits, from the second communication unit to the mobile terminal, the control method for charging the vehicle by the charging device. As a result, the user of the charging device can know the charging control method of the charging device via the mobile terminal, improving usability. Here, examples of the control method include the following methods. The first method is to charge for a first time shorter than the charging time to full charge, and if there is no waiting vehicle, charge again for the first time. If there is a waiting vehicle, end the charging for the first time and wait for charging (this is the control method of the charging control device of Invention 1). The second method is that the maximum power consumption for simultaneously charging a plurality of vehicles is set. When charging the vehicle that has made the charging request would exceed the maximum power consumption when there is a charging request, the charging of the vehicle that has made the charging request is put on standby (this is the control method of the charging control device of Invention 2). The third method is that the maximum power consumption for simultaneously charging a plurality of vehicles is set. When there is a new charging request while charging at least one of the plurality of vehicles with the first charging power, if charging the newly requested vehicle in addition to the vehicle being charged with the first charging power would exceed the maximum power consumption, for the vehicle with the new charging request and the vehicle being charged with the first charging power, charge with a second charging power that is less than the maximum power consumption and lower than the first charging power (this is the control method of the charging control device of Invention 3). Note that the user can use a mobile application or the like to check the control method received from the second server, and can search for a parking lot that uses a method suitable for the charging to be performed during the current parking. (2-2) Charging control device of 2B The charging control device of 2B is the same as the charging control device of 1B, except that the plurality of connectors belong to any of a plurality of groups, the control unit can control with different control methods for each group, and the control unit transmits, from the second communication unit to the mobile terminal, the plurality of control methods performed in each group. As a result, the user can know the charging control method of the charging device via the mobile terminal, select a charging method according to the user's intention, and the usability is improved.

[0192] (3) Charging system The charging system is a charging system that performs electric charging on 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 charging device to the vehicle. The charging control device is the first (A, B) or second (A, B) charging control device described above.

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

Explanation of symbols

[0194] 1 Vehicle 3 Mobile terminal 101 Charging system 103 Charging device 105 Charging control device 106 OCPP server 107 Database 108 AP server

Claims

1. A charging control device for controlling charging to a vehicle connected to a charging device that charges each of a plurality of vehicles that can be electrically charged in a parking lot, the charging device having a set maximum power consumption that enables simultaneous charging of the plurality of vehicles, wherein: when the charging time of a vehicle being charged reaches a first time that is shorter than the charging time to full charge, charging is temporarily terminated; A charging control device.

2. A charging control device for controlling charging to a vehicle connected to a charging device that charges each of a plurality of vehicles that can be electrically charged in a parking lot, the charging device having a set maximum power consumption that enables simultaneous charging of the plurality of vehicles, wherein: charging of the vehicle is performed one or more times for a first time that is shorter than the charging time to full charge; A charging control device.

3. A charging control device for controlling charging to a vehicle connected to a charging device that charges each of a plurality of vehicles that can be electrically charged in a parking lot, the charging device having a set maximum power consumption that enables simultaneous charging of the plurality of vehicles, wherein: when the charging time of a vehicle being charged reaches a first time that is shorter than the charging time to full charge, it is determined whether to terminate charging; A charging control device.

4. When there is a new charging request, if the total power consumption when charging the vehicle with the new charging request exceeds the maximum power consumption, charging to the vehicle with the new charging request is put on standby; The charging control device according to any one of Claims 1 to 3.

5. When there is a new charging request during charging of at least one of the plurality of vehicles with a first charging power, if the total power consumption when charging the vehicle being charged and the vehicle with the new charging request with the first charging power exceeds the maximum power consumption, then for the vehicle with the new charging request and the vehicle being charged with the first charging power, charging is performed with a second charging power that is less than the maximum power consumption and lower than the first charging power; The charging control device according to any one of Claims 1 to 3.

6. The charging device includes a plurality of connectors for connecting to each of the plurality of vehicles, the plurality of connectors belong to any one of a plurality of groups, the charging control device can be controlled by different control methods for each group; The charging control device according to any one of Claims 1 to 3.

7. The charging control device has a communication unit that receives a charging request to the vehicle from a mobile terminal, and transmits the control method to the mobile terminal via the communication unit. The charging control device according to claim 6.

8. In a charging system that performs electric charging on a plurality of vehicles that can be electrically charged in a parking lot, a charging device including a plurality of connectors each connectable to each of the plurality of vehicles, and a charging control device that controls charging of the vehicle by the charging device, wherein the charging device has a maximum power consumption set for simultaneously charging the plurality of vehicles, the charging control device is the charging control device according to any one of claims 1 to 3, a charging system.

9. In a charging control method for controlling charging to a vehicle connected to a charging device that is a device for electrically charging each of a plurality of vehicles that can be electrically charged in a parking lot and has a maximum power consumption set for simultaneously charging the plurality of vehicles, when the charging time of a vehicle being charged reaches a first time that is shorter than the charging time to full charge, charging is temporarily terminated. A charging control method.

Images