Device

Abstract

To provide a demand control function that improves user convenience. [Solution] The device includes a processor that grasps the status of electric vehicles being charged at charging equipment that charges electric vehicles, grasps the status of electric vehicles waiting to be charged at the charging equipment, obtains the charging wait time of a specific electric vehicle among the waiting electric vehicles based on the grasped status of the electric vehicle being charged and the status of the waiting electric vehicles, and outputs information on the obtained charging wait time.

Description

[Technical Field]

[0001] The present invention relates to an apparatus. [Background technology]

[0002] Patent Document 1 describes a method for efficiently operating an EV charging system in a building by accepting charging reservations using charging devices, calculating a predicted power usage value corresponding to the charging reservation based on the power usage amount, and creating a charging schedule for the charging reservation based on the predicted power usage value. [Prior art documents] [Patent documents]

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

[0004] For example, there is a demand control function that controls which electric vehicles can be charged when there are many electric vehicles wanting to charge at the same time compared to the power capacity of the charging equipment for electric vehicles.With conventional demand control functions, when a user uses this function, they do not know when an electric vehicle that connected to the charging equipment before the user's electric vehicle will finish charging, and they are not able to know the waiting time until charging can begin. An object of the present invention is to provide a demand control function that improves user convenience. [Means for solving the problem]

[0005] The invention of claim 1 comprises a processor, wherein the processor grasps a status of an electric vehicle being charged at a charging facility that charges the electric vehicle, grasps a status of the electric vehicle waiting to be charged at the charging facility, obtains a charging standby time of a specific electric vehicle among the waiting electric vehicles based on the grasped status of the electric vehicle being charged and the status of the waiting electric vehicles, and outputs information about the obtained charging standby time, wherein the status of the waiting electric vehicles is a status regarding electric vehicles that are waiting earlier than the specific electric vehicle, and the earlier waiting electric vehicles include an electric vehicle that has transitioned from the electric vehicle being charged to the waiting electric vehicle. and when the charging upper limit time, which is a time set on the device side and indicates an upper limit of the charging time per charging in the charging facility, is exceeded, the electric vehicle being charged transitions to the standby electric vehicle. The device is characterized by the following. Claim 2 The invention described in is the device described in claim 1, characterized in that the status of the electric vehicle being charged is the degree of progress of charging of the electric vehicle being charged. Claim 3 The invention described in claim 1 is characterized in that the situation regarding electric vehicles waiting ahead is a situation regarding the number of electric vehicles waiting ahead. [Effects of the Invention]

[0006] The present invention can provide a demand control function that improves user convenience. [Brief explanation of the drawings]

[0007] [Figure 1] 1 is a diagram showing the overall configuration of a charging service system for electric vehicles. [Figure 2] This is the hardware configuration of the management server. [Figure 3] 1 shows the hardware configuration of a user terminal. [Figure 4] FIG. 2 is a functional configuration diagram of a management server. [Figure 5] FIG. 2 is a functional configuration diagram of a user terminal. [Figure 6] 10 is a flowchart showing a processing flow of a management server when pre-charge information is output. [Figure 7]10 is a flowchart showing the flow of processing by a management server when charging an electric vehicle. [Figure 8] 10 is a flowchart showing a flow of processing on the user terminal side up to acquisition of pre-charging information. [Figure 9] 10 is a flowchart showing the flow of processing on the user terminal side when charging at a charging facility. [Figure 10] 10 is a display screen provided to a user when charging an electric vehicle. [Figure 11] This is a display screen provided to the administrator of the facility where the charging equipment is installed and the administrator who manages the management server. DETAILED DESCRIPTION OF THE INVENTION

[0008] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

[0009] FIG. 1 is a diagram showing the overall configuration of an electric vehicle charging service system 1. As shown in FIG. 1, the electric vehicle charging service system 1 has a management server 10 that manages the electric vehicle charging service. The electric vehicle charging service system 1 also has a user terminal 20, which is a terminal of a user who uses the electric vehicle charging service. The electric vehicle charging service system 1 also has a plurality of charging facilities 30 that charge electric vehicles 2. The management server 10, the user terminal 20, and the plurality of charging facilities 30 are connected via a network 90. ​​The electric vehicle 2 is, for example, an electric vehicle of a user who uses the electric vehicle charging service system 1. The distribution board 3 is installed in the facility where the charging facilities 30 are installed, and distributes power from the facility's main power source to each charging facility 30.

[0010] The management server 10 stores and manages facility information as information relating to the charging facility 30. Then, in response to a request from the user terminal 20 or the charging facility 30, the management server 10 outputs the managed facility information to the user terminal 20 or the charging facility 30.

[0011] The user terminal 20 is configured, for example, with a smartphone, a tablet terminal, a personal computer, or the like. The user terminal 20 is capable of executing application software that enables use of the charging service system 1 for electric vehicles. The user terminal 20 receives information transmitted from the management server 10 and outputs the information to a display unit 26, which will be described later. Then, the user terminal 20 outputs information to the management server 10 in response to user input or the like.

[0012] The multiple charging facilities 30 each have an outlet 31 for charging the electric vehicle 2. Each charging facility 30 is provided with facility identification information 32, such as a two-dimensional code, as information for identifying the charging facility 30. For example, by reading the facility identification information 32 with the user terminal 20, the user can use the charging facility 30 in which the facility identification information 32 that was read is installed. The charging facility 30 then charges the electric vehicle 2 via the outlet 31 in response to user input or by obtaining information instructing charging from the management server 10.

[0013] Furthermore, the multiple charging facilities 30 are provided in the parking lot of the facility, etc., and the multiple charging facilities 30 can simultaneously charge multiple electric vehicles 2 within the range of charging capacity allowed by the facility. The number of multiple electric vehicles 2 that can be simultaneously charged by the multiple charging facilities 30 is sometimes referred to as the "number of vehicles being simultaneously charged." Note that the multiple charging facilities 30 may be simply referred to as charging facilities 30 when there is no need to particularly distinguish between them.

[0014] Fig. 2 shows the hardware configuration of the management server 10. As shown in Fig. 2, the management server 10 has a control unit 11, a memory 12, a storage unit 13, a communication unit 14, an operation unit 15, and a display unit 16. These units are connected via a data bus, an address bus, a PCI (Peripheral Component Interconnect) bus, etc.

[0015] The control unit 11 is a processor that controls the functions of the management server 10 through the execution of various software such as an OS (operating system) and application software. The control unit 11 is configured, for example, by a CPU (Central Processing Unit). The memory 12 is a storage area that stores various software and data used for executing the software, and is used as a working area for calculations. The memory 12 is configured, for example, by a RAM (Random Access Memory).

[0016] The storage unit 13 is a storage area that stores input data for various software programs, output data from various software programs, etc. The storage unit 13 is configured with, for example, an HDD (Hard Disk Drive), an SSD (Solid State Drive), a semiconductor memory, etc. that are used to store programs, various setting data, etc. The storage unit 13 stores DB131 and the like as databases that store various information.

[0017] The communication unit 14 transmits and receives data to and from the user terminal 20 and the outside via the network 90. ​​The operation unit 15 is composed of, for example, a keyboard, a mouse, mechanical buttons, and switches, and accepts input operations. The operation unit 15 also includes a touch sensor that forms a touch panel integrally with the display unit 16. The display unit 16 is composed of, for example, a liquid crystal display or an organic EL (Electro Luminescence) display used to display information, and displays images, text data, and the like.

[0018] Fig. 3 shows the hardware configuration of the user terminal 20. The user terminal 20 has hardware configurations corresponding to the control unit 11, memory 12, storage unit 13, communication unit 14, operation unit 15, and display unit 16 of the management server 10 in Fig. 2, as well as an imaging unit 27. These units are connected via a data bus, an address bus, a PCI bus, etc.

[0019] That is, the user terminal 20 has a control unit 21 configured with a processor such as a CPU, a memory 22 configured with a storage area such as RAM, and a storage unit 23 configured with a storage area such as an HDD, an SDD, a semiconductor memory, etc. The user terminal 20 also has a communication unit 24 that transmits and receives data to and from the management server 10 and the outside via the network 90.

[0020] The user terminal 20 also has an operation unit 25 consisting of a keyboard, mouse, touch panel, etc., and a display unit 26 consisting of a liquid crystal display, an organic EL display, etc. The user terminal 20 also has an imaging unit 27 consisting of a camera, etc., which captures an image of a subject displayed on the display unit 26, which also functions as a camera finder, and acquires the image data.

[0021] In this embodiment, each process is executed by an arbitrary computer. The arbitrary computer may execute these processes by a processor as hardware, a program as software, or a combination thereof. In this case, the processor is configured to execute the various processes in this embodiment in cooperation with the program, and may function as each unit or means in this embodiment. The order in which the processes are executed by the processor is not limited to the order described and may be changed as appropriate. The arbitrary computer may be a general-purpose computer, a computer for specific applications, a workstation, or any other system capable of executing each process.

[0022] The processor may be composed of one or more pieces of hardware, and the type of hardware is not limited. For example, the processor may be composed of hardware such as a programmable logic device such as a CPU (Central Processing Unit), an MPU (Micro Processing Unit), or an FPGA (Field Programmable Gate Array), a dedicated circuit for executing specific processes such as an ASIC (Application Specific Integrated Circuit), a GPU (Graphic Processing Unit), or an NPU (Neural Processing Unit). The type of hardware may also be a combination of different types of hardware. When multiple pieces of hardware are configured to execute one or more processes of a certain processor, the multiple pieces of hardware may exist in devices physically separated from each other or in the same device. In any embodiment, the order of each process performed by the processor is not limited to the order described above and may be changed as appropriate. The hardware may be composed of an electric circuit or the like, which is a combination of circuit elements such as semiconductor elements.

[0023] Furthermore, the program may be software, such as firmware or microcode. The program may also be, for example, a group of program modules, each function of which may be implemented by a processor configured to perform the respective function. The program may be program code or multiple code segments stored in one or more non-transitory computer-readable media (e.g., storage media or other storages). The program may be stored across multiple non-transitory computer-readable media that reside in physically separate devices. The program code or code segment may represent a procedure, a function, a subprogram, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. The program code or code segment may be connected to another code segment or a hardware circuit by sending or receiving information, data, arguments, parameters, or memory contents.

[0024] 4 is a functional configuration diagram of the management server 10. The management server 10 has a two-dimensional code information acquisition unit 101 that acquires two-dimensional code information and the like as facility identification information 32 (see FIG. 1). The management server 10 also has a user information acquisition unit 102 that acquires user information that is information that identifies a user who uses the user terminal 20. The management server 10 also has a charging facility identification unit 103 that identifies the charging facility 30 that the user plans to use from the two-dimensional code information and the user information.

[0025] The management server 10 also has a standby status ascertaining unit 104 that ascertains the status of electric vehicles 2 waiting at the charging facility 30. The management server 10 also has a charging status ascertaining unit 105 that ascertains the status of electric vehicles 2 being charged at the charging facility 30 from facility information. The management server 10 also has a simultaneously charged vehicle number ascertaining unit 106 that ascertains the number of electric vehicles 2 that can be charged simultaneously at multiple charging facilities 30 that are supplied with power from a common power source. The management server 10 also has a waiting time prediction unit 107 that predicts the waiting time, which is the time until charging of the electric vehicles 2 begins. The waiting time is an example of a waiting prediction.

[0026] Here, an electric vehicle 2 waiting at charging facility 30 refers to an electric vehicle 2 that has not started charging at charging facility 30 but is ready to be charged. For example, an electric vehicle 2 that is ready refers to an electric vehicle 2 that is connected to charging facility 30 via outlet 31 but is not receiving power from charging facility 30. Also, for example, an electric vehicle 2 that is ready refers to an electric vehicle 2 that is connected to charging facility 30 in excess of the number of electric vehicles 2 that can be charged simultaneously.

[0027] Here, an electric vehicle 2 being charged refers to an electric vehicle 2 being charged at charging facility 30. For example, it refers to an electric vehicle 2 that is connected to charging facility 30 via outlet 31 and is being supplied with power from charging facility 30. It also refers to an electric vehicle 2 being charged at charging facility 30 within the number of vehicles that can be charged simultaneously.

[0028] Furthermore, the management server 10 has a pre-charging information output unit 108 that outputs, in association with the user, pre-charging information that allows the user to understand the waiting time before the electric vehicle 2 is placed on standby at the charging facility 30. It also has a charging standby information output unit 109 that outputs charging standby information that is information used by the user while the electric vehicle 2 is on standby. The management server 10 also has a charging information output unit 110 that outputs charging in-progress information that is information used by the user while the electric vehicle 2 is being charged. The management server 10 has an upper limit charging time acquisition unit 111 that acquires an upper limit charging time that indicates the upper limit of the charging time per charging session at the charging facility 30. The management server 10 has a designated charging time acquisition unit 112 that acquires a designated charging time that is the charging time desired by the user. The management server 10 has a charging end instruction information acquisition unit 113 that acquires information instructing the user to end charging. The management server 10 has a charging facility control unit 114 that controls charging at the charging facility 30.

[0029] The charging facility identification unit 103 identifies the charging facility 30 that the user plans to use to charge the electric vehicle 2. In addition, it identifies charging facilities 30 related to the charging facility 30 that the user plans to use to charge the electric vehicle 2. For example, the charging facility identification unit 103 identifies other charging facilities 30 installed in the facility where the charging facility 30 that the user plans to use is installed. The other charging facilities 30 installed in the facility where the charging facility 30 that the user plans to use is installed may be simply referred to as "other charging facilities 30." These other charging facilities 30 and the charging facility 30 that the user plans to use are supplied with power from a common power source installed in the facility. The electric vehicle 2 that is to be charged at the charging facility 30 that the user plans to use is an example of a specific electric vehicle.

[0030] The status of the electric vehicles 2 waiting at the charging facility 30 ascertained by the waiting status ascertaining unit 104 is the status of electric vehicles 2 that are waiting to be charged earlier at other charging facilities 30. For example, the waiting status ascertaining unit 104 ascertains the number of electric vehicles 2 that are waiting to be charged earlier. Furthermore, for example, the waiting status ascertaining unit 104 ascertains the remaining predicted waiting time of the electric vehicles 2 that are waiting to be charged earlier. Furthermore, for example, the waiting status ascertaining unit 104 may ascertain information ascertained by the charging status ascertaining unit 105, and ascertains the remaining time, which will be described later. Note that "electric vehicles 2 waiting at charging facility 30" may also be referred to as "waiting electric vehicles 2".

[0031] The status of the electric vehicle 2 being charged at the charging facility 30 ascertained by the charging status ascertaining unit 105 is the status of an electric vehicle 2 that has been previously charged at another charging facility 30. For example, the charging status ascertaining unit 105 ascertains the degree of progress of charging of the electric vehicle 2. The degree of progress is an index that indicates the progress of charging of the electric vehicle 2 at the charging facility 30. The index mainly includes the remaining time obtained by subtracting the time actually spent charging from a predetermined time. For example, the remaining time obtained by subtracting the time actually spent charging from the upper limit charging time set by the administrator, the remaining time obtained by subtracting the time actually spent charging from the specified charging time designated by the user, etc.

[0032] Furthermore, the charging status ascertaining unit 105 ascertains whether the charging facility 30 is currently charging by ascertaining the progress of charging of the electric vehicle 2. For example, the charging status ascertaining unit 105 ascertains that charging of the electric vehicle 2 has ended when the remaining time reaches 0. Furthermore, the charging status ascertaining unit 105 ascertains that charging of the electric vehicle 2 has ended when the user presses a button to end charging and the progress of charging can no longer be ascertained.

[0033] The number of vehicles being charged simultaneously grasped by the unit 106 for grasping the number of vehicles being charged simultaneously is, for example, a value determined by the facility where the charging equipment 30 is installed. Alternatively, the management server 10 may determine the number of vehicles being charged simultaneously by grasping the charging capacity of the facility. For example, the number of vehicles being charged simultaneously by the charging equipment 30 may be changed depending on the remaining power supply capacity of the facility or the time of day. The number of vehicles being charged simultaneously is an example of the status of the electric vehicles 2 being charged.

[0034] The waiting time prediction unit 107 predicts the waiting time based on the status of waiting electric vehicles 2 and the status of charging electric vehicles 2. For example, the waiting time prediction unit 107 predicts the waiting time taking into consideration the number of waiting electric vehicles 2, the number of electric vehicles 2 being charged, the number of vehicles being charged simultaneously, the remaining time of the upper limit of charging time for waiting electric vehicles 2, the remaining time of the designated charging time for waiting electric vehicles 2, the remaining time of the upper limit of charging time for charging electric vehicles 2, and the remaining time of the designated charging time for charging electric vehicles 2.

[0035] For example, when the number of vehicles being charged simultaneously is one, the waiting time may be the sum of the remaining time in the upper limit of charging time of the electric vehicle 2 being charged and the remaining time in the upper limit of charging time of the electric vehicle 2 being on standby, the sum of the designated charging time of the electric vehicle 2 being charged and the remaining time in the upper limit of charging time of the electric vehicle 2 being on standby, or the remaining time in the upper limit of charging time of the electric vehicle 2 being charged. The waiting time prediction unit 107 basically predicts the smallest waiting time among the waiting time values ​​that can be calculated from various times.

[0036] Furthermore, for example, when there are multiple vehicles being charged simultaneously, the waiting time is predicted taking into account the remaining time for each of the multiple electric vehicles 2 in addition to the value for when there is one vehicle. For example, when there are two vehicles being charged simultaneously, the prediction is made taking into account which of the multiple electric vehicles 2 being charged has the shortest remaining time. Note that, as with the case of one vehicle, the waiting time prediction unit 107 basically predicts the time that gives the smallest value of the waiting time that can be calculated from various times.

[0037] Furthermore, the waiting time predicted by the waiting time prediction unit 107 is a value that is updated in real time according to changes in the status of electric vehicles being charged and changes in the status of electric vehicles waiting to be charged. Changes in the status of electric vehicles being charged and changes in the status of electric vehicles waiting to be charged refer to changes in the various times and numbers used to predict the waiting time described above, such as changes in the number of electric vehicles 2 being charged and changes in the number of waiting electric vehicles 2.

[0038] The pre-charging information output by the pre-charging information output unit 108 includes, for example, a waiting time predicted when the two-dimensional code information and user information are acquired, the power required by the charging equipment 30, and an upper limit charging time. The charging standby information output by the charging standby information output unit 109 includes, for example, a waiting time predicted when charging start instruction information described below is acquired, and the remaining time of the specified charging time. The charging information output by the charging information output unit 110 includes, for example, the remaining time of the upper limit charging time and the remaining time of the specified charging time.

[0039] The upper charging time limit acquired by the upper charging time limit acquisition unit 111 is a value determined to provide equal opportunities for charging to the electric vehicles 2 that are being charged at the charging facility 30. The upper charging time limit is, for example, a value determined by the facility that owns the charging facility 30. This upper charging time limit may be different for each charging facility 30 or may be the same for each charging facility 30.

[0040] Furthermore, the designated charging time acquired by the designated upper limit time acquisition unit 112 is determined, for example, by an input by the user. When the charging end instruction information acquisition unit 113 acquires the charging end instruction information, the management server 10 outputs charging end notification information to the user terminal 20. The charging end notification information is information that notifies the user that charging has ended.

[0041] The charging equipment control unit 114 controls whether or not the charging equipment 30 charges the electric vehicle 2 based on each piece of information acquired by the management server 10. For example, when the remaining time of the upper charging time limit reaches 0, the charging equipment control unit 114 outputs information to the charging equipment 30 charging the electric vehicle 2 whose remaining time has reached 0, to control the charging equipment 30 to stop charging the electric vehicle 2. In this case, the electric vehicle 2 being charged becomes a standby electric vehicle 2. Also, for example, when the waiting time for the standby electric vehicle 2 has elapsed, the charging equipment control unit 114 controls the charging equipment 30 connected to the electric vehicle 2 whose waiting time has elapsed to start charging the electric vehicle 2. In this case, the standby electric vehicle 2 becomes a charging electric vehicle 2. In this way, the electric vehicle 2 is controlled so that the state of the electric vehicle 2 being charged and the state of the standby electric vehicle 2 alternate between each other until the remaining time of the specified charging time reaches 0 and until charging completion instruction information is acquired.

[0042] Furthermore, for example, when the remaining time of the specified charging time reaches 0, information is output to the charging equipment 30 that is charging the electric vehicle 2 whose remaining time has reached 0, to control the charging to stop charging of the electric vehicle 2. In this case, the electric vehicle 2 that is being charged becomes an electric vehicle 2 whose charging has finished. An electric vehicle 2 whose charging has finished is an electric vehicle 2 that has finished charging as desired by the user. When charging of the electric vehicle 2 is finished, the user releases the connection between the electric vehicle 2 and the charging equipment 30 and ends use of the charging service system for electric vehicles 2. The charging equipment 30 then becomes a charging equipment 30 that is not connected to any electric vehicle 2. Furthermore, for example, when charging end instruction information is acquired, information is output to the charging equipment 30 that is charging the electric vehicle corresponding to the user that output the charging end instruction information, to control the charging to stop charging of the electric vehicle 2. In this case, the waiting electric vehicle 2 or the electric vehicle 2 that is being charged becomes an electric vehicle 2 whose charging has finished.

[0043] 5 is a functional configuration diagram of the user terminal 20. This function is executed by application software provided to the user terminal 20. The user terminal 20 has a two-dimensional code information reading unit 201 that reads two-dimensional code information using the imaging unit 27. It also has a two-dimensional code information output unit 202 that outputs the two-dimensional code information to the management server 10. It also has a user information output unit 203 that outputs user information by adding it to the two-dimensional code information.

[0044] The user terminal 20 includes a charging start instruction information output unit 204 that outputs charging start instruction information that instructs the user to start charging the electric vehicle 2. For example, the charging start instruction information is output when the user presses a start button displayed on the display unit 26. The user terminal 20 also includes a pre-charging start information acquisition unit 205 that acquires pre-charging start information from the pre-charging start information output unit 108. The user terminal 20 also includes a charging standby information acquisition unit 206 that acquires charging standby information from the charging standby information output unit 109. The user terminal 20 also includes a charging in-progress information acquisition unit 207 that acquires charging in-progress information from the charging in-progress information output unit 110. The pre-charging start information, charging standby information, and charging in-progress information are displayed on the display unit 26, for example, as information usable by the user. The user terminal 20 also includes a charging end instruction information output unit 208 that outputs charging end instruction information to the charging end instruction information acquisition unit 113, which indicates that charging should be ended. For example, the charging end instruction information is output when the user presses an end button displayed on the display unit 26. The charge start instruction information is an example of instruction information.

[0045] FIG. 6 is a flowchart showing the processing flow of the management server 10 when outputting pre-charge information. First, the two-dimensional code information acquisition unit 101 and the user information acquisition unit 102 of the management server 10 acquire two-dimensional code information and user information assigned to the two-dimensional code information (step 601). Next, the facility identification unit 103 identifies the charging facility 30 that the user plans to use based on the two-dimensional code information and the user information (step 602). Then, the waiting status ascertaining unit 104 ascertains the waiting status of the electric vehicle waiting at the charging facility 30 (step 603). Next, the charging status ascertaining unit 105 ascertains the charging status of the electric vehicle 2 being charged at the charging facility 30 (step 604). Then, the waiting time prediction unit 107 obtains a predicted waiting time based on the charging status and the waiting status (step 605). Next, the pre-charge information output unit 108 outputs the pre-charge information including the waiting time in association with the user (step 606).

[0046] FIG. 7 is a flowchart showing the processing flow of the management server 10 when charging an electric vehicle 2 at a charging facility 30. First, the management server 10 acquires charging start instruction information from the user terminal 20 (step 701). Next, the facility identification unit 103 of the management server 10 identifies the charging facility 30 that the user plans to use based on the user information attached to the charging start instruction information (step 702). The standby status ascertaining unit 104 ascertains the standby status of the electric vehicle 2 waiting at the charging facility 30 (step 703). Then, the charging status ascertaining unit 105 ascertains the charging status of the electric vehicle 2 being charged at the charging facility 30 (step 704). Next, the waiting time prediction unit 107 obtains a predicted waiting time based on the standby status and the charging status (step 705). Then, it is determined whether or not there is a waiting time (step 706). If there is a waiting time (YES in step 706), the charging waiting information output unit 109 outputs charging waiting information including the waiting time (step 707). Then, the processes from step 703 to step 706 are executed again.

[0047] If there is no waiting time (NO in step 706), the charging information output unit 110 outputs charging information to the user terminal 20 (step 708). Next, the charging equipment control unit 114 determines whether the upper limit charging time has been reached (step 709). If the upper limit charging time has been reached (YES in step 709), the processing from step 703 is executed. If the upper limit charging time has not expired (NO in step 709), the charging equipment control unit 114 determines whether a charging end instruction has been acquired from the user terminal 20 (step 710). If a charging end instruction has been acquired (YES in step 710), the management server 10 outputs charging end notification information to the user terminal 20 (step 712). If a charging end instruction has not been acquired (NO in step 710), the charging equipment control unit 114 determines whether the charging time specified by the user has been reached (step 711). If the charging time specified by the user has been reached (YES in step 711), charging end notification information is output (step 712). If the user-specified charging time has not yet been reached, the process returns to step 708 .

[0048] 8 is a flowchart showing the flow of processing on the user terminal 20 side up to the acquisition of pre-charging information. The user terminal 20 starts up an application for realizing the charging service system 1 for electric vehicles 2 through a user operation (step 801). Next, the user terminal 20 reads two-dimensional code information through a user operation (step 802). Next, the user terminal 20 adds user information to the two-dimensional code information and outputs it (step 803). Then, the pre-charging information acquisition unit 205 acquires the pre-charging information (step 804). Then, the user terminal 20 displays the pre-charging information on the display unit 26 (step 805).

[0049] FIG. 9 is a flowchart showing the flow of processing on the user terminal 20 side when charging at the charging facility 30. The charging start instruction information output unit 204 of the user terminal 20 outputs charging start instruction information (step 901). Next, the charging standby information acquisition unit 206 determines whether charging standby information has been acquired (step 902). If charging standby information has been acquired (YES in step 902), the charging standby information is displayed on the display unit 26 (step 903). If charging standby information has not been acquired (NO in step 902), the charging information acquisition unit 207 determines whether charging information has been acquired (step 904). If charging information has not been acquired (NO in step 904), the process returns to step 902. If charging information has been acquired (YES in step 904), the charging information is displayed on the display unit 26 (step 905). Next, the user terminal 20 determines whether charging completion notification information has been acquired (step 906). If charging completion notification information has not been acquired (NO in step 906), the process returns to step 902. If the charging end notification information is acquired (YES in step 906), the charging end notification information is displayed on the display unit 26 (step 907).

[0050] 10(a) to 10(d) are display screens provided to a user when charging an electric vehicle 2. FIGS. 10(a) to 10(d) are, for example, screens obtained from the management server 10 and output by the display unit 26 of the user terminal 20. FIG. 10(a) is a display screen when facility identification information 32 installed in the charging facility 30 is read. FIG. 10(b) is a display screen when pre-charging information in the charging facility 30 is output. FIG. 10(c) is a display screen when charging standby information in the charging facility 30 is output. FIG. 10(d) is a display screen when charging in progress information is output. Note that the information described in FIGS. 10(a) to 10(d) may be updated depending on changes in the standby status or charging status.

[0051] Fig. 10(a) is a screen that appears when, for example, a user operates the user terminal 20 to execute an application related to a charging service system for electric vehicles. Then, for example, when the user operates the imaging unit 27 to read facility identification information 32 installed in the charging facility 30, the process described in Fig. 6 is performed, and the screen of Fig. 10(b) is displayed on the display unit 26 of the user terminal 20.

[0052] 10(b), a waiting time before starting charging 251, which is a waiting time when the pre-charging information is acquired, is displayed as pre-charging information. Also, a designated charging time input field 252, which is a field for inputting a designated charging time, is displayed as pre-charging information. Also, charging power information 253, which is the charging power of charging facility 30 that the user plans to use, is displayed as pre-charging information.

[0053] 10(b) also displays, as pre-charging information, power plan information 254, which is information about the charging power plan subscribed to by the user and the amount of power that can be used in the charging service system. The power plan information 254 displays, for example, the amount of power that will be used in this charging, the amount of power that has already been used, and the amount of power that is expected to remain after this charging, out of the amount of power that can be used under the usage plan subscribed to by the user.

[0054] 10(b) also displays caution information 255 for use of the charging service system for electric vehicles 2. For example, the information indicates that charging will automatically end when the specified charging time has elapsed. The information indicates that charging will temporarily end after the upper limit charging time of one hour, and if there is an electric vehicle waiting, charging will start again after the waiting electric vehicle 2 has been charging for one hour.

[0055] 10(b) also displays a start charging button 256, which is a button for instructing the start of charging of the electric vehicle 2. For example, when the user presses the start charging button 256, charge start instruction information is transmitted to the management server 10. Then, the process described in FIG. 7 is performed, and if there is a waiting time, the user terminal 20 acquires charge standby information from the management server 10, and the screen of FIG. 10(c) is displayed on the display unit 26 of the user terminal 20.

[0056] In Fig. 10(c), charging standby information is displayed as charging standby wait time 261, which is the wait time when charging standby information is acquired. Therefore, this may differ from waiting time 251 before charging starts. In addition, Fig. 10(c) displays designated charging time 262. In addition, Fig. 10(c) displays remaining time 263 of the designated charging time, which is the time obtained by subtracting the time that charging actually took place at charging facility 30 from the designated charging time.

[0057] 10(c) displays a charging end button 263, which is a button for ending charging at the charging facility 30. Pressing this charging end button ends charging at the charging facility 30. Then, charging end notification information, which is information indicating, for example, the amount of charge already performed and the charging fee for the amount of charge, is displayed.

[0058] 10(c) is a value that is updated depending on changes in the standby state and the charging state. For example, when the remaining time during the standby state for charging becomes 0, the user terminal 20 acquires charging information from the management server 10, and the display unit 26 of the user terminal 20 displays the screen shown in FIG. 10(d).

[0059] In Fig. 10(d), the charging information includes a designated charging time 262, a remaining time of the designated charging time 263, and a charging end button 264. For example, when the remaining time of the designated charging 262 reaches 0 or when the charging end button 264 is pressed, charging automatically ends and charging end notification information is displayed. Also, for example, when the upper charging time limit expires, the screen in Fig. 10(c) is displayed again. The information output from the management server 10 at this time includes information regarding the waiting time for outputting charging standby information again. This information regarding the waiting time for outputting charging standby information again is an example of recharging standby information.

[0060] 11(a) and (b) are display screens provided to the administrator of the facility where the charging equipment 30 is installed or the administrator who manages the management server 10. FIGS. 11(a) and (b) are screens output to, for example, a terminal owned by the facility administrator or the administrator of the management server 10. FIG. 11(a) is a display screen when the upper limit charging time for multiple charging equipment 30 installed in the facility is set collectively. FIG. 11(b) is a display screen when the upper limit charging time is set for each charging equipment 30 installed in the facility.

[0061] FIG. 11(a) displays a collective setting button 271, which is a button for transitioning to a screen for collectively setting the upper charging time limit for multiple charging facilities 30. FIG. 11(a) also displays an individual setting button 272, which is a button for individually setting the upper charging time limit for multiple charging facilities 30. FIG. 11(a) also displays a collective setting input field 273, which is an input field for collectively setting the upper charging time limit, and an apply collective setting button 274, which applies the upper charging time limit entered in the collective setting input field 273. For example, when the administrator enters a specified time in the collective setting input field 273 and presses the apply collective setting button 274, the management server 10 collectively sets the upper charging time limit for multiple charging facilities 30 to the time specified by the administrator. For example, when the administrator presses the individual setting button 272, the screen shown in FIG. 11(b) appears.

[0062] 11(b) displays a collective setting button 271 and an individual setting button 272. Also, FIG. 11(b) displays an individual setting input field 275, which is an input field for individually setting the upper charging time limit. Also, FIG. 11(b) displays an apply individual setting button 276, which applies the upper charging time limit input in the individual setting input field 275 individually to each charging facility 30. For example, when the administrator inputs a specified time in the individual setting input field 275 and presses the apply individual setting button 276, the management server 10 sets the upper charging time limit for each of the multiple charging facilities 30 individually, using the time specified by the administrator as the upper charging time limit.

[0063] Note that this embodiment is not limited to an embodiment in which a plurality of electric vehicles 2 are charged using a common power source, and is not limited to an embodiment in which a plurality of charging facilities 30 each have one outlet 31. For example, a single charging facility 30 may have a plurality of outlets 31. In this case, the standby status of an electric vehicle 2 that is already connected to an outlet 31 of a single charging facility 30 and is waiting is grasped, and the charging status of an electric vehicle 2 that is already connected to an outlet 31 of a single charging facility 30 and is being charged is grasped, thereby outputting information on the charging standby time. Similarly, a plurality of charging facilities 30 may have a plurality of outlets 31.

[0064] Furthermore, the management server 10 does not necessarily need to acquire the designated charging time. For example, if the designated charging time is not acquired, the management server 10 detects the amount of charge in the rechargeable battery provided in the electric vehicle 2. Then, until the amount of charge in the electric vehicle 2 reaches full charge, the management server 10 may perform control such that the electric vehicle 2 alternates between being charged and being on standby, as described above. Then, when the amount of charge in the electric vehicle 2 reaches full charge, charging may be terminated.

[0065] Furthermore, for example, if the designated charging time is not acquired, the management server 10 determines the value of the current flowing to the rechargeable battery of the electric vehicle 2 via the charging facility 30. Specifically, a certain threshold is set for the value of the current flowing to the rechargeable battery of the electric vehicle 2. If the value of the current measured for a certain period of time is below the threshold, it is possible to determine that the rechargeable battery of the electric vehicle 2 has reached full charge and terminate charging. The threshold is a value that indicates approaching full charge, and for example, a current value near 0 A, such as 0.1 A, is set as the threshold. Note that charging control based on these detections of the charge amount may also be performed when the designated charging time is acquired.

[0066] Furthermore, the facility identification information may be read not only by reading two-dimensional code information but also by exchanging information using non-contact data communication technologies such as communication standards NFC (Near Field Communication), Bluetooth, RFID (Radio Frequency Identification), etc. Furthermore, the facility identification information may be read not only by a terminal but also by a charging card or the like using these communication technologies.

[0067] Furthermore, the charging facility 30 is not limited to a configuration in which an outlet 31 is provided in the charging facility 30 and charging is performed by, for example, connecting the charging cable 32 of the user's electric vehicle 2 to the outlet 31. For example, the charging cable 31 may be attached to the charging facility 30 in advance. Furthermore, the charging facility 30 may be a normal charger that supplies received AC power directly to the electric vehicle 2, or a rapid charger that converts AC voltage. [Explanation of symbols]

[0068] 10... Management server, 20... User terminal, 30... Charging equipment

Claims

1. a processor; The processor: The status of an electric vehicle being charged at a charging facility for the electric vehicle is grasped, grasping a status of the electric vehicle waiting to be charged at the charging facility; acquiring a charging standby time for a specific electric vehicle among the standby electric vehicles based on the grasped status of the electric vehicle being charged and the status of the standby electric vehicles; outputting the acquired information on the charging standby time; the status of the waiting electric vehicle is a status regarding an electric vehicle that is waiting before the specific electric vehicle, The device includes an electric vehicle that has transitioned from the electric vehicle being charged to the standby electric vehicle, The device is characterized in that the electric vehicle being charged transitions to the standby electric vehicle when the charging upper limit time, which is a time set on the device side and indicates the upper limit of the charging time per charging session at the charging facility, is exceeded.

2. 2. The device according to claim 1, wherein the status of the electric vehicle during charging is a progress of charging of the electric vehicle during charging.

3. 2. The device according to claim 1, wherein the situation regarding the electric vehicles waiting ahead is a situation regarding the number of electric vehicles waiting ahead.

Images