CHARGING MANAGEMENT SYSTEM, CHARGING SYSTEM, CHARGING MANAGEMENT METHOD, AND PROGRAM

Provided is a charging management system designed to make management by determining whether a charging connector of a charger is connected to a socket of an electric vehicle returned by a user. A charging management system includes an acquirer and a decider. The acquirer acquires connection status information indicating whether a charging connector of a charger is connected to a socket of an electric vehicle. The decider determines, depending on whether the connection status information acquired by the acquirer indicates that the charging connector is connected to the socket, whether return of the electric vehicle from a user is completed.

TECHNICAL FIELD

The present disclosure generally relates to a charging management system, a charging system, a charging management method, and a program. More particularly, the present disclosure relates to a charging management system, a charging system, a charging management method, and a program, all of which are configured or design to manage charging an electric vehicle.

BACKGROUND ART

Patent Literature 1 discloses an operating system for providing car sharing services that temporarily rent an electric car (which is an exemplary electric vehicle) at the user's demand The operating system has the capability of accepting a reservation for an electric car from the user and the capability of assigning an electric car to the reservation.

An operating system as disclosed in Patent Literature 1 needs to make management of charging an electric vehicle returned by the user. In that case, when the electric vehicle is returned by the user, a connection status needs to be managed by determining whether a charging connector of a charger is connected to a socket of the electric vehicle returned.

CITATION LIST

Patent Literature

Patent Literature 1: JP 2018-18250 A

SUMMARY ON INVENTION

It is therefore an object of the present disclosure to provide a charging management system, a charging system, a charging management method, and a program, all of which are configured or designed to manage a connection status by determining whether a charging connector of a charger is connected to a socket of an electric vehicle returned by the user.

A charging management system according to an aspect of the present disclosure includes an acquirer and a decider. The acquirer acquires connection status information indicating whether a charging connector of a charger is connected to a socket of an electric vehicle. The decider determines, depending on whether the connection status information acquired by the acquirer indicates that the charging connector is connected to the socket, whether return of the electric vehicle from a user is completed.

A charging system according to another aspect of the present disclosure includes the charging management system described above and the charger.

A charging management method according to still another aspect of the present disclosure includes an acquisition step and a decision step. The acquisition step includes acquiring connection status information indicating whether a charging connector of a charger is connected to a socket of an electric vehicle. The decision step includes determining, depending on whether the connection status information acquired in the acquisition step indicates that the charging connector is connected to the socket, whether return of the electric vehicle from a user is completed.

A program according to yet another aspect of the present disclosure is designed to cause one or more processors to perform the charging management method described above.

DESCRIPTION OF EMBODIMENTS

FIG.1illustrates a management system10according to an exemplary embodiment. The management system10is a system for managing the use of one or more moving vehicles100by one or more users. In particular, in the exemplary embodiment to be described below, the management system10is supposed to be a system for managing the use of a plurality of moving vehicles100(100A-100D) by a plurality of users. The management system10manages the plurality of moving vehicles100to allow each of the plurality of users to use a moving vehicle100that meets his or her demand (i.e., a moving vehicle100that he or she wants or wishes to use). As used herein, the “use” refers to both use that requires no payment of fees and use that requires payment of fees. For example, if the plurality of moving vehicles100are owned by a company and one of the moving vehicles100is used by a user who is an employee of the company, then no payment of fees is required. On the other hand, if the company allows a user who is not an employee of the company to use one of their own moving vehicles100(i.e., if the company rents the moving vehicle100to the user), then the user who is not employed by the company pays the fee for using the moving vehicle100.

In this embodiment, each moving vehicle100includes a storage battery110and a socket111(refer toFIG.1). The storage battery110is a chargeable and dischargeable secondary battery (such as a battery). The storage battery110is used as a power source for the moving vehicle100. That is to say, the storage battery110is used to drive a drive source (such as a motor) of the moving vehicle100. The socket111is a part to/from which a charging connector411of a charger41may be connected and disconnected. When the charging connector411of the charger41is connected to the socket111, the socket111receives power from the charger41and charges the storage battery110with the power received. The moving vehicle100may be, for example, an electric vehicle designed to travel using the electric energy stored in the storage battery110. Examples of the electric vehicles include an electric car designed to travel based on the output of a motor and a plug-in hybrid car designed to travel using the output of an engine and the output of a motor in combination. That is to say, the electric vehicle may herein refer to a car that uses electricity as part or all of its power source. The moving vehicle100does not have to be a four-wheeler but may also be a two-wheeler (e-bike), a three-wheeler, or an electric bicycle. In the following description, the moving vehicle100is supposed to be an electric car and will be hereinafter referred to as an “electric car100” as needed to make the following description more easily understandable.

The management system10may be used in, for example, car-sharing services and rent-a-car services. In particular, according to this embodiment, the management system10may be used to provide a service of renting a vehicle owned by a corporation such as a company to a user. In that case, the user may be not only a person (such as an employee) belonging to the corporation but also a person not belonging to the corporation. That is to say, the management system10may be used to provide a service of renting a vehicle that no person belonging to the corporation (such as an employee) plans to use to a person not belonging to the corporation.

As shown inFIG.1, the management system10includes a charging management system a use management system30, a power supply system40, and terminal devices50. The charging management system20, the use management system30, the power supply system40, and the terminal devices50may be connected to a communications network60. The power supply system40includes chargers41. In this embodiment, the charging management system and the chargers41form a charging system.

Each of the terminal devices50is a device that allows the user to transmit a demand for using the electric car100to a moving vehicle management system11.

The use management system30is a system for managing the use of one or more electric cars100by one or more users. For example, in response to a demand from a user, the use management system30selects an electric car100that meets the user's demand from a plurality of electric cars100and assigns the electric car100to the user. Specifically, on the user's demand, the use management system30determines a use schedule for the plurality of electric cars100and assigns one of the electric cars100to the user by reference to the use schedule.

The charging management system20is a system for managing charging one or more electric cars100by the power supply system40. For example, the charging management system appropriately controls charging one or more electric cars100, thereby reducing the chances of the remaining capacity of the storage battery110of the electric car(s)100running short when the electric car(s)100needs to be used. Specifically, the charging management system20determines a charging schedule for the plurality of electric cars100by reference to the use schedule given by the use management system30and controls the power supply system40following the charging schedule.

The power supply system40includes one or more chargers41(41A-41D) for use to charge the electric car(s)100. Each charger41may charge an electric car100with electricity supplied from a power supply such as a commercial AC power supply or a distributed power supply (such as a solar battery, a storage battery, a fuel cell, or a wind power generator). In the power supply system40, each charger41charges an electric car100in accordance with an instruction from the charging management system20with the charging connector411of the charger41connected to the socket111of the electric car100, thereby having one or more electric cars100charged as per the charging schedule.

The charging management system20and the use management system30are connected to the communications network60to establish the moving vehicle management system11. The moving vehicle management system11manages schedule information including the use schedule and the charging schedule of one or more electric cars100and assigns, in accordance with the schedule information and a demand from a user, an electric car100that meets the user's demand to him or her.

FIG.2illustrates an exemplary operation of the management system10. The user operates his or her terminal device50to send a demand for using (hereinafter referred to as a “use demand”) an electric car100(in M11). The use demand from the user is transmitted from the terminal device50to the use management system30. In accordance with the use demand from the user, the use management system30provides the charging management system20with demand information (in M12). The demand information may include, for example, information about a demand period in which use of the electric car100is demanded. As used herein, the “demand period” refers to a period in which use of the electric car100is demanded by the user. The charging management system20generates decision information based on an amount of available electricity from the storage battery110in the demand period of the electric car100(in S11). The amount of available electricity is obtained based on the use schedule of the plurality of electric cars100and the demand information. The decision information is information for use to determine whether or not there is any electric car100available in the demand period, among the plurality of electric cars100. The charging management system20presents the decision information to the use management system30(in M13). The use management system30makes, by reference to the use demand from the user and the decision information, a decision about the availability of the electric car100(i.e., determines whether or not there is any electric car100that meets the user's demand for using the electric car100) (in S12). When finding one or more electric cars100available, the use management system30transmits information about the one or more electric cars100available to the terminal device50, thereby presenting the one or more electric cars100available to the user (in M14). When the user chooses, on the terminal device50, an electric car100that he or she wants to use from the one or more electric cars100available, information about the electric car100chosen by the user is sent to the use management system30(in M15). In response, the use management system30authorizes the use of the electric car100chosen by the user and notifies the terminal device50and the charging management system20that the use of the electric car100has been authorized (in M16and M17). Then, the use management system30updates the use schedule of the plurality of electric cars100(in S13). Meanwhile, the charging management system20updates the charging schedule of the plurality of electric cars100(in S14). Thereafter, the charging management system20controls the power supply system40(in M18), thereby charging the electric car100connected to each charger41as per the charging schedule (in S15).

Also, when returning the electric car100that the user has used, the user operates his or her terminal device50to make a return notification informing that he or she has returned the electric car100used (in M19). The return notification includes a user ID and return place information. The user ID is identification information to identify the user. The return place information is information to identify (i.e., determine) a place where the user has returned the electric car100. In this embodiment, when returning the electric car100used, the user chooses one return place from a plurality of prespecified return places and parks (i.e., returns) the electric car100to the return place thus chosen. Then, the user connects the charging connector411of a charger41installed in the return place to the socket111of the electric car100returned. Thereafter, the user transmits, as the return notification, return information including his or her own user ID and return place information about the return place chosen, to the use management system30. Note that each of the plurality of prespecified return places is provided with predefined return place information. Thus, when transmitting the return notification, the user transmits the predefined return place information.

The return notification is transmitted from the user's terminal device50to the use management system30. In response, the use management system30transfers the user ID and return place information, which are included in the return notification, to the charging management system20(in M20). Then, the charging management system20sends a request for the connection status information of the charger41installed in the return place, identified by the return place information, to the power supply system40(in M21). In response, the power supply system40transmits the connection status information of the charger41to the charging management system20(in M22). As used herein, the connection status information is information indicating whether the charging connector411of the charger41is connected to the socket111of the electric car100. The charging management system20determines, based on the connection status information, whether the charging connector411of the charger41is connected to the socket111of the electric car100. When finding the charging connector411connected to the socket111, the charging management system20decides that the return of the electric car100from the user be completed (in S16). In that case, as soon as the return of the electric car100from the user is completed, the charging management system20updates the charging schedule for the plurality of electric cars100so that the charging schedule includes charging the electric car100returned (in S17). Then, the charging management system20controls the power supply system40(in M23), thereby charging the electric car100connected to each charger41following the charging schedule (in S18).

In this manner, the management system10according to this embodiment assigns an electric car100to the user. In addition, in the management system10, the charging management system20includes a connection checking system for checking, when the electric car100is returned from the user, whether the charging connector411of a charger41is connected to the electric car100returned. This connection checking system (charging management system20) is implemented as an acquirer231and a decider236(refer toFIG.3). In other words, the connection checking system includes the acquirer231and the decider236. The acquirer231acquires the connection status information indicating whether the charging connector411of the charger41is connected to the socket111of the electric car100. The decider236determines, depending on whether the connection status information acquired by the acquirer231indicates that the charging connector411is connected to the socket111, whether the return of the electric car100from the user is completed.

Such a connection checking system (charging management system20) may make management by determining whether the charging connector411of a charger41is connected to the socket111of the electric car100returned from the user.

Next, the management system10according to this embodiment will be described in further detail. As shown inFIG.1, the management system10includes the charging management system20, the use management system30, the power supply system40, and the terminal devices50. The charging management system20, the use management system30, the power supply system40, and the terminal devices50may be connected to the communications network60. In particular, the charging management system20and the use management system30are connected to the communications network60to establish the moving vehicle management system11. In addition, the power supply system40includes the chargers41. The charging management system20and the chargers41form a charging system.

The communications network60may include the Internet. The communications network60does not have to be a network compliant with a single communications protocol but may also be a plurality of networks compliant with multiple different communications protocols, respectively. The communications protocol may be selected from various known wired and wireless communication standards. Although illustrated in a simplified form inFIG.1, the communications network60may include various data communications devices such as a repeater hub, a switching hub, a bridge, a gateway, and a router.

Each of the terminal devices50may be used to enter information into the moving vehicle management system11and display thereon information provided by the moving vehicle management system11. As shown inFIG.4, the terminal device50includes an input/output interface51, a communications interface52, and a processor53. The terminal device50may be implemented as, for example, a desktop computer, a laptop computer, or a mobile communications device (such as a smartphone, a tablet computer, or a wearable device). In this embodiment, the terminal device50is implemented as a smartphone.

The input/output interface51includes an input device for use to operate the terminal device50. The input device may include, for example, a keyboard, a mouse, a trackball, or a touchpad. In addition, the input/output interface51includes an image display device for displaying information thereon. The image display device may include a display device with a reduced thickness such as a liquid crystal display or an organic EL display.

The communications interface52is a communications interface. The communications interface52may be connected to the communications network60and has the capability of establishing communication over the communications network60. The communications interface52is compliant with a predetermined communications protocol. The predetermined communications protocol may be selected from various known wired and wireless communication standards.

The processor53is configured to perform overall control on the terminal device50, i.e., control the input/output interface51and the communications interface52. The processor53has the capability of transmitting, in response to an operating command entered through the input/output interface51, information entered by the user from the communications interface52to the moving vehicle management system11via the communications network60. In addition, the processor53also has the capability of presenting, to the user via the input/output interface51, information provided by the moving vehicle management system11and received at the communications interface52over the communications network60.

The processor53may be implemented as a computer system including one or more processors (microprocessors) and one or more memories. That is to say, the functions of the processor53are performed by making the one or more processors execute one or more (computer) programs (applications) stored in the one or more memories. In this embodiment, the program is stored in advance in the memory of the processor53. Alternatively, the program may also be downloaded via a telecommunications line such as the Internet or distributed after having been stored in a non-transitory storage medium such as a memory card.

The power supply system40is a system for charging the storage battery110for use as a power source for the electric car100. As shown inFIG.1the power supply system40is installed in a facility400. The facility400may include a parking lot410for the electric cars100and a building420annexed to the parking lot410. Examples of the facility400include dwelling houses (such as single-family dwelling houses and multi-family dwelling houses) and non-dwelling facilities (such as factories, commercial facilities, amusement facilities, hospitals, offices, and office buildings).

As shown inFIG.5, the power supply system40includes a plurality of chargers41(41A-41D) for use to charge the electric cars100, power supply equipment42, a plurality of current sensors43, a gateway44, and a management device45.

The parking lot410includes a plurality of separate parking spaces416(416A-416D) (refer toFIG.1). Each of the plurality of separate parking spaces416is a space wide enough to park a single electric car100. The separate parking space416is also a charging place where the electric car100is charged. The separate parking space416is also a return place where the electric car100rented to the user is returned. Around each separate parking space416, a single charger41associated with the separate parking space416is installed. That is to say, the plurality of chargers41(41A-41D) are provided one to one for the plurality of separate parking spaces416(416A-416D). The electric car100parked in each separate parking space416is charged with the charger41provided for the separate parking space416.

The chargers41are connected to the power supply equipment42. Each charger41may charge the storage battery110of an electric car100connected to the charger41with the power supplied from the power supply equipment42. The charger41may be connected to an electric car100parked in its corresponding separate parking space416. The charger41may use various types of charging stations, which are roughly classifiable into two types, namely, standard charging stations and rapid charging stations. In this embodiment, a standard charging station for charging the storage battery110by receiving single-phase AC power of 200 V (or 100V) is used for the chargers41. The modes of standard charging may be classifiable into “Mode 1,” “Mode 2,” and “Mode 3” according to the charging control scheme (see IEC 61851-1 standard). Specifically, according to “Mode 1,” power is supplied to an electric car from a charging station having no control circuits. According to “Mode 2,” a control circuit is built in a charging cable. According to “Mode 3,” a control circuit is built in the charging station. In this embodiment, the chargers41are supposed to adopt the “Mode 3” scheme.

The charger41includes the charging connector411, a communications interface412, and a processor415as shown inFIG.6.

The charging connector411is a part to be connected removably to the socket111of an electric car100and is connected to the housing of the charger41via a cable. The charging connector411supplies the power, delivered from the power supply equipment42to the charger41, to the electric car100connected to the charging connector411. The charging connector411includes a plurality of connection terminals. The plurality of connection terminals of the charging connector411are connected to a plurality of connection terminals provided for the socket111of the electric car100. The plurality of connection terminals of the charging connector411corresponds one to one to the plurality of connection terminals of the socket111. Each of the plurality of connection terminals of the charging connector411includes a power supply terminal and a signal terminal. The power supply terminal is a terminal for outputting power therethrough and is connected to a corresponding one (power supply terminal) of the plurality of connection terminals of the socket111. The signal terminal is a terminal through which a connection status signal (such as a control pilot (CPLT) signal) is transmitted and received between the charger41and the electric car100and is connected to a corresponding one (signal terminal) of the plurality of connection terminals of the socket111. As used herein, the “connection status signal” refers to a signal representing a connection status (e.g., either connected or unconnected) between the charging connector411and the socket111of the electric car100.

The communications interface412is connected to the gateway44and establishes communication with the management device45and the charging management system20via the gateway44.

The processor415is a control circuit for controlling the operation of the charger41. The processor415may be implemented as a computer system including one or more processors (microprocessors) and one or more memories. That is to say, the functions of the processor415are performed by making the one or more processors execute one or more (computer) programs (applications) stored in the one or more memories. In this embodiment, the program is stored in advance in the memory of the processor415. Alternatively, the program may also be downloaded via a telecommunications line such as the Internet or distributed after having been stored in a non-transitory storage medium such as a memory card.

The processor415includes a connection status detector413and a controller414.

The connection status detector413determines whether the charging connector411is connected to the socket111of the electric car100and acquires the result of detection as connection status information. More specifically, the connection status detector413transmits and receives, between the charger circuit of the electric car100and itself via the signal terminal of the charging connector411, a signal for use to check the connection status between the charging connector411and the socket111of the electric car100(i.e., a connection status signal (CPLT signal)). In this embodiment, the connection status detector413has a control pilot (CPLT) function and transmits and receives, using the CPLT function, the connection status signal (CPLT signal) between the charger circuit for the electric car100and itself. As used herein, the “CPLT function” refers to the function of checking, by transmitting and receiving the CPLT signal, whether the charging connector411of the charger41and the socket111of the electric car100are connected to each other without fail and starting charging the electric car100if the answer is YES.

The connection status detector413determines, based on the voltage level of the connection status signal supplied from the signal terminal of the charging connector411, whether the charging connector411is connected to the socket111. While the charging connector411has not been connected to the socket111yet, the voltage level of the connection status signal is a first voltage level (of 12 V, for example). On the other hand, in a state where the charging connector411is connected to the socket111, the voltage level of the connection status signal is a second voltage level (of 6 V or 9 V, for example) which is lower than the first voltage level. When finding the voltage level of the connection status signal to be the first voltage level, the connection status detector413detects that the charging connector411has not been connected to the socket111yet. On the other hand, when finding the voltage level of the connection status signal to be the second voltage level, the connection status detector413detects that the charging connector411is connected to the socket111.

In accordance with an instruction given by the management device45, the controller414outputs the result of detection (connection status information) by the connection status detector413to the management device45and controls starting and stopping supplying power from the charging connector411.

The power supply equipment42is connected to a power grid200and may receive power from a commercial AC power supply210. In addition, the power supply equipment42is also connected to distributed power supply300and may supply power to, or receive power from, the distributed power supply300. The distributed power supply300may be either an AC power supply or a DC power supply. Examples of the AC power supplies include AC power generation systems such as a wind power generation system. Examples of the DC power supplies include solar batteries, fuel cells, and secondary batteries (storage batteries). Examples of the secondary batteries includes nickel-hydrogen batteries and lithium-ion batteries. The power supply equipment42may distribute the power supplied from either the commercial AC power supply210or the distributed power supply300to the respective chargers41. Note that the power supply equipment42may have a configuration already known in the art, and a detailed description thereof will be omitted herein.

The plurality of current sensors43include a first current sensor431, and a plurality of second current sensors432A-432D. The first current sensor431is installed on an electrical path between the power grid200and the power supply equipment42and may measure a current supplied from the power grid200to the power supply equipment42. The second current sensors432A-432D are installed on the electrical paths between the power supply equipment42and the chargers41A-41D and may measure the current supplied from the power supply equipment42to the chargers41A-41D. Note that the current sensors43may each have a configuration already known in the art, and a. detailed description thereof will be omitted herein.

The management device45may control the plurality of chargers41. Specifically, as shown inFIG.5, the management device45is connected to the gateway44and communicates with the plurality of chargers41and the plurality of current sensors43via the gateway44. This allows the management device45to control the respective chargers41and acquire operating status information representing the operating status of the power supply system40and the connection status information representing the connection status between the charging connectors411of the chargers41and the sockets111of the electric cars100. In this embodiment, the operating status of the power supply system40is represented by results of current measurements made by the plurality of current sensors43(including the first current sensor431and the plurality of second current sensors432A-432D). The management device45is connected to the communications network60via the gateway44and is ready to communicate with the charging management system via the gateway44and the communications network60. In accordance with an instruction given by the charging management system20, the management device45may acquire the connection status information of the charging connector411from each charger41and transmit the connection status information thus acquired to the charging management system20. In addition, in accordance with an instruction given by the charging management system20, the management device45controls the respective chargers41. This enables the electric cars100to be charged as per the charging schedule.

The use management system30is a system for managing the use of one or more electric cars100by one or more users. In this embodiment, the use management system30determines a use schedule for the plurality of electric vehicles100and manages the use of the electric cars100by reference to the use schedule.

FIG.8shows an exemplary use schedule. InFIG.8, the use schedule indicates the scheduled use periods of a plurality of (e.g., four in this example) electric cars100A-100D during a specified period. InFIG.8, the specified period is one day. However, this is only an example and should not be construed as limiting. The specified period does not have to be one day but may also be, for example, one week, one month, or one year and may be set as appropriate according to the operating status of the management system10. The scheduled use period means a period for which the electric car100is scheduled to be used by the user. The scheduled use period is a period for which the user is allowed an exclusive use of the electric car100. In other words, the scheduled use period is a period for which the user has the right to use the electric car100exclusively. Thus, during the scheduled use period, the user is allowed to use the electric car100freely as far as the predefined contract is fulfilled. For example, during the scheduled use period, the user may go anywhere by the electric car100or have a meal or go shopping by parking the electric car100in a parking lot.

InFIG.8, as for the electric car100A, a scheduled use period U11is set as a period from 08:00 to 12:00 and another scheduled use period U12is set as a period from 14:00 to 18:00. As for the electric car100B, a scheduled use period U21is set as a period from 08:00 to 10:00 and another scheduled use period U22is set as a period from 16:00 to 18:00. As for the electric car100C, a scheduled use period U31is set as a period from 08:00 to 12:00 and another scheduled use period U32is set as a period from 14:00 to 16:00. As for the electric car100D, a scheduled use period U41is set as a period from 08:00 to 18:00.

In addition, the use management system30holds information about the electric energy consumption expected with respect to each of the scheduled use periods included in the use schedule. The electric energy consumption expected corresponds to a decrease in the remaining capacity of the storage battery110due to the use of the electric car100in the scheduled use period. Note that the electric energy consumption expected does not have to be an electric energy required to allow the electric car100to travel at a predetermined speed during the scheduled use period but may be set with various conditions, including the attribute information of the electric car100, taken into account. The attribute information of the electric car100may include at least one of the type, the intended use, the initial location, the destination, the distance to travel, the number of passengers to travel, or the mode of use. For example, if the intended use indicated by the attribute information of the electric car100is shopping, the electric energy consumption expected may be set at 50% of the electric energy required to allow the electric car100to travel at the predetermined speed during the scheduled use period.

The use management system30includes a communications interface31, a storage device32, and a processor33as shown inFIG.7. The use management system30may be implemented as, for example, a server.

The communications interface31is a communications interface. The communications interface31may be connected to the communications network60and has the capability of establishing communication over the communications network60. The communications interface31is compliant with a predetermined communications protocol. The predetermined communications protocol may be selected from various known wired and wireless communication standards.

The storage device32may be used to store information to be used by the processor33. For example, the use schedule may be stored in the storage device32. In addition, not only the use schedule but also the electric energy consumptions expected with respect to the scheduled use periods included in the use schedule are stored in the storage device32as well. The storage device32includes one or more storage devices. The storage device may be, for example, a random-access memory (RAM) or an electrically erasable programmable read-only memory (EEPROM).

The processor33is a control circuit for controlling the operation of the use management system30. The processor33may be implemented as a computer system including one or more processors (microprocessors) and one or more memories. That is to say, the functions of the processor33are performed by making the one or more processors execute one or more (computer) programs (applications) stored in the one or more memories. In this embodiment, the program is stored in advance in the memory of the processor33. Alternatively, the program may also be downloaded via a telecommunications line such as the Internet or distributed after having been stored in a non-transitory storage medium such as a memory card.

The processor33includes an accepter331, a decider332, a notifier333, and an updater334, as shown inFIG.7. Note that inFIG.7, the accepter331, the decider332, the notifier333, and the updater334do not represent substantive configurations but represent functions to be performed by the processor33. The accepter331, the decider332, the notifier333, and the updater334will be described later.

The charging management system20is a system for managing charging one or more electric cars100. In this embodiment, the charging management system20uses the power supply system40to charge the plurality of electric cars100. The electric cars100are supposed to be charged basically outside of their scheduled use periods. Thus, the charging management system20determines a charging schedule by reference to the use schedule generated by the use management system30. Then, the charging management system20controls charging the electric cars100according to the charging schedule thus determined.

FIG.9shows an exemplary charging schedule determined by reference to the use schedule shown inFIG.8. Note that the use schedule is also shown inFIG.9. InFIG.9, the charging schedule indicates scheduled charging periods of a plurality of (e.g., four in this embodiment) electric cars100A-100D during a specified period. InFIG.9, the specified period is one day. However, this is only an example and should not be construed as limiting. The specified period does not have to be one day but may also be, for example, one week, one month, or one year and may be set as appropriate according to the operating status of the management system10. The scheduled charging period means a period for which the electric car100is scheduled to be charged. The scheduled charging periods are set not to overlap with the scheduled use periods during the specified period.

InFIG.9, as for the electric car100A, a scheduled charging period C11is set as a period from 0:00 to 2:00, another scheduled charging period C12is set as a period from 12:00 to 14:00, and still another scheduled charging period C13is set as a period from 20:00 to 00:00. As for the electric car100B, a scheduled charging period C21is set as a period from 00:00 to 04:00, another scheduled charging period C22is set as a period from 10:00 to 16:00, still another scheduled charging period C23is set as a period from 18:00 to 20:00, and yet another scheduled charging period C24is set as a period from 22:00 to 00:00. As for the electric car100C, a scheduled charging period C31is set as a period from 00:00 to 06:00, another scheduled charging period C32is set as a period from 12:00 to 14:00, and still another scheduled charging period C33is set as a period from 16:00 to 22:00. As for the electric car100D, a scheduled charging period C41is set as a period from 02:00 to 08:00 and another scheduled charging period C42is set as a period from 18:00 to 00:00.

The charging management system20includes a communications interface21, a storage device22, and a processor23as shown inFIG.3. The charging management system20may be implemented as, for example, a server.

The communications interface21is a communications interface. The communications interface21may be connected to the communications network60and has the capability of establishing communication over the communications network60. The communications interface21is compliant with a predetermined communications protocol. The predetermined communications protocol may be selected from various known wired and wireless communication standards.

The storage device22may be used to store information to be used by the processor23. For example, the charging schedule may be stored in the storage device22. In addition, the use schedule acquired from the use management system30may also be stored in the storage device22. The storage device32includes one or more storage devices. The storage device may be, for example, a random-access memory (RAM) or an electrically erasable programmable read-only memory (EEPROM).

The processor23is a control circuit for controlling the operation of the charging management system20. The processor23may be implemented as a computer system including one or more processors (microprocessors) and one or more memories. That is to say, the functions of the processor23are performed by making the one or more processors execute one or more (computer) programs (applications) stored in the one or more memories. In this embodiment, the program is stored in advance in the memory of the processor23. Alternatively, the program may also be downloaded via a telecommunications line such as the Internet or distributed after having been stored in a non-transitory storage medium such as a memory card.

The processor23includes the acquirer231, a presenter232, a determiner233, a controller234, a notifier235, and a decider236as shown inFIG.3. Note that inFIG.3, the acquirer231, the presenter232, the determiner233, the controller234, the notifier235, and the decider236do not represent substantive configurations but represent functions to be performed by the processor23.

Next, the respective constituent elements of the charging management system20, namely, the acquirer unit231, the presenter232, the determiner233, the controller234, the notifier235, and the decider236and the respective constituent elements of the use management system30, namely, the accepter331, the decider332, the notifier333, and the updater334, will be described. As shown inFIG.2, the charging management system20and the use management system30transmit and receive information to/from each other. Thus, in the following description, these constituent elements of the charging management system20and the use management system30will be described following the flow of operations performed by the charging management system20and the use management system30to give higher priority to making the following description easily understandable.

First, the respective constituent elements of the charging management system20and the use management system30will be described with reference toFIGS.2-7following the flow of operations performed when the user rents an electric car100.

The accepter331of the use management system30accepts the user's demand for using (hereinafter referred to as “use demand”) a moving vehicle100, which has been transmitted from the terminal device50(in M11). The user's use demand for the electric car100includes at least a demand period in which use of the electric car100is demanded. As used herein, the demand period is period in which the user demands the use of the electric car100. The user's use demand for the electric car100may also include the user's attribute information and the electric car's100attribute information. The user's attribute information may be information indicating whether the user belongs to a corporation. Also, the electric car's100attribute information may include at least one of the type, the intended use, the initial location, the destination, the distance to travel, the number of passengers to travel, or the mode of use.

The decider332of the use management system30determines whether there is any electric car100that meets the use demand accepted by the accepter331(i.e., the user's use demand for the electric car100) (in S12). In this embodiment, the decider332selects an electric car100that meets the user's use demand from the plurality of electric cars100. In selecting such an electric car100that meets the user's use demand from the plurality of electric cars100, the decider332refers to the decision information acquired from the charging management system20. To acquire the decision information from the charging management system20, the decider332provides the charging management system20with demand information (in M12). The demand information includes information about the demand period in which use of the electric car100is demanded. In this embodiment, the demand information includes information about the electric energy required to use the electric car100for the demand period.

In this case, the user's use demand for the electric car100may include the user's attribute information and the electric vehicle's100attribute information. The electric vehicle's100attribute information may include at least one of the type, the intended use, the initial location, the destination, the distance to travel, the number of passengers to travel, or the mode of use. Examples of the type include the model of the electric car100and the classification of the electric car100(which may be an ordinary car or a small car). Examples of the intended use include trip, shopping, pickup and drop-off, and delivery. Examples of the initial location include the place where the electric car100is stationed at the beginning of the scheduled use period. The place may be a place where the electric car100is supposed to be charged. Examples of the destination include a place that the user is going to visit by using the electric car100. For example, if the user uses the electric car100to go shopping, then the destination is the shop that he or she is going to visit. On the other hand, if the user uses the electric car100to go on a trip, then the destination is a sightseeing spot or accommodations that the user is going to visit. The distance to travel is the distance that the user plans to travel by the electric car100. The distance to travel may be the distance to travel to make a roundtrip between the initial location and the destination. The number of passengers to travel is the number of passengers who plan to travel by the electric car100. For example, the number of passengers to travel is the number of persons who are scheduled to get on the electric car100. The mode of use is the mode of use of the electric car100. In this embodiment, the mode of use is supposed to be a mode in which the electric car100is used by a company's employee (i.e., for business use) and a mode in which the electric car100is used by a person who is not a company's employee (for non-business use; such as car sharing or car renting).

The decider332may obtain the electric energy required based on the attribute information of the electric car100. For example, if the attribute information of the electric car100includes the distance to travel, then the electric energy required may be estimated based on the distance to travel. Alternatively, the distance to travel may also be estimated based on the initial location and the destination. For example, the type of the electric car100and the number of passengers to travel may affect the electric mileage of the electric car100. The electric mileage may affect the electric energy required. Therefore, the electric energy required may be changed according to the type of the moving vehicle (electric car100). Alternatively, the electric energy required may also be changed according to the intended use of the moving vehicle (electric car100). Examples of the intended use of the electric car100include trip and shopping. Going on a trip will require a longer distance to travel than going shopping. Thus, if the intended use is going on a trip, then the electric energy required is set at a larger value than in a situation where the intended use is going shopping. Optionally, the demand information may include the user's attribute information and the electric car's100attribute information, both of which are included in the user's use demand for the electric car100. That is to say, the electric energy required does not have to be the electric energy required to allow the electric car100to operate (travel) for the demand period but may also be set with various conditions including the attribute information of the electric car100taken into account.

The acquirer231of the charging management system20acquires demand information, including information about the demand period in which use of an electric car100is demanded, from the use management system30that manages the use of a plurality of electric cars100, each including the storage battery110for use as a power source (in M12). In this embodiment, the decider332of the use management system30transmits the demand information to the charging management system20and the acquirer231of the charging management system20receives the demand information over the communications network60. In addition, the acquirer231acquires the use schedule for the electric cars100from the use management system30. At this time, the acquirer231also acquires, from the use management system30, information about the electric energy consumption expected for the scheduled use period included in the use schedule.

The presenter232of the charging management system20presents the decision information to the use management system30(in M13). The decision information is information for use to determine whether any electric car100is available in the demand period. The presenter232generates the decision information based on the amount of available electricity in the storage battery110in the demand period in which the use of the electric car100is demanded (in S11). In this embodiment, the decision information includes basic information. The basic information includes information indicating the amount of available electricity in the demand period in which the use of the electric car100is demanded (hereinafter referred to as a “first amount of available electricity”). Optionally, the decision information may include influence information as needed. As used herein, the “influence information” is information indicating how the use of the electric car100in one or more scheduled use periods is affected by reserving the amount of available electricity in the storage battery110(first amount of available electricity) for the demand period. In particular, the influence information includes information indicating the amount of available electricity in the storage battery110(second amount of available electricity) in one or more scheduled use periods when the amount of available electricity in the storage battery110(first amount of available electricity) is reserved for the demand period. In this manner, the presenter232may present decision information, including the basic information and the influence information, to the use management system30.

The decider332of the use management system30determines, by reference to the decision information provided by the presenter232of the charging management system20, whether there is any electric car100that meets the user's use demand for the electric car100(i.e., whether there is any electric car100available in the demand period) (in SLY). The decider332selects an electric car100, of which the amount of available electricity (first amount of available electricity) is equal to or greater than the electric energy required to use the electric car100for the demand period, as an optional moving vehicle (electric car)100that may be used in the demand period. Nevertheless, even if the first amount of available electricity is equal to or greater than the electric energy required but the second amount of available electricity is less than the electric energy consumption expected, then the electric car100should be regarded as non-usable in the demand period. Thus, the decider332excludes a moving vehicle (electric car)100, of which the second amount of available electricity in a scheduled use period following the demand period is less than the electric energy consumption expected, from the list of moving vehicles (electric cars)100that may be used in the demand period.

Optionally, the decider332may also regard even a moving vehicle (electric car)100, of which the second amount of available electricity in the scheduled use period following the demand period is less than the electric energy consumption expected, as an optional moving vehicle (electric car)100that may be used in the demand period with a collateral condition presented to the user. In this case, the collateral condition is that the user agrees to use a moving vehicle100, of which the second amount of available electricity is less than the electric energy consumption expected. In other words, the collateral condition is that the user agrees to charge the moving vehicle100by him- or herself. In that case, the use management system30may offer a discount on the fee for using the moving vehicle100as an advantage on the condition that the user agrees to use a moving vehicle100, of which the second amount of available electricity is less than the electric energy consumption expected.

In this manner, according to this embodiment, the decider332selects, based on the decision information, one or more moving vehicles (electric cars)100that may be used in the demand period, as electric car (s)100that meet the user's use demand for the electric cars100.

The notifier333of the use management system30transmits notification information to notify the user of the one or more electric cars100that have been selected by the decider332as electric cars100that meet the user's use demand (i.e., electric cars100that may be used in the demand period) to the terminal device50(in M14). This allows the terminal device50to present the information about the one or more electric cars100selected by the decider332as optional electric cars100that meet the user's use demand to the user via the input/output interface51. The user may choose, by operating the input/output interface51, any desired electric car100from the one or more electric cars100presented on the input/output interface51. Then, the terminal device50transmits information about the electric car100chosen by the user to the use management system30(in M15). If there is no electric car100that meets the user's use demand, then the user may be notified that there are no electric cars100that meet his or her use demand

The updater334of the use management system30receives information about the electric car100chosen by the user from the terminal device50(in M15). The updater334notifies the terminal device50and the charging management system20that the scheduled use period is fixed with the electric car100chosen by the user (in M16, M17). The updater334changes the use schedule to set a period corresponding to the demand period as the scheduled use period with respect to the electric car100chosen by the user. In this manner, the updater334changes (updates) the use schedule according to the user's demand (in S13). In addition, the updater334also sets the electric energy required for the demand period as the electric energy consumption expected for the newly set scheduled use period.

On being notified by the updater334that the scheduled use period is fixed with the electric car100chosen by the user, the determiner233of the charging management system20determines (updates) the charging schedule since the use schedule has been changed by fixing the scheduled use period (in S14). That is to say, to reduce the chances of the remaining capacity of the storage battery110of the electric car100running short when needed now that a new scheduled use period has been added to the use schedule, the determiner233reorganizes (updates) the charging schedule. For example, the charging schedule may be changed to compensate for the decrease in the remaining capacity of the storage battery110at the end of the use schedule. In this manner, the determiner233changes (updates) the charging schedule in response to a change (update) of the use schedule.

The controller234of the charging management system20controls the power supply system40(in M18). More specifically, the controller234controls the power supply system40according to the updated charging schedule. That is to say, the controller234controls charging at least one of the respective storage batteries110of the plurality of electric cars100according to the updated charging schedule. Specifically, in each scheduled charging period of the charging schedule, the controller234has each electric car100charged with its associated charger41. Thus, the power supply system40performs charging the electric car (s)100following the charging schedule (in S15).

Next, the respective constituent elements of the charging management system20and the use management system30will be described with reference toFIGS.2-4andFIG.10following the flow of operations performed when the user returns an electric car100used.

The accepter331of the use management system30accepts, from the terminal device50and via the communications interface31, a return notification informing that the moving vehicle100has been returned to the return place (in M19). Note that the return notification includes a user ID and return place information. The user ID is identification information to identify the user. The return place information is information to identify (i.e., determine) the place where the user has returned the electric car100. Then, the accepter331transmits the return information thus accepted to the charging management system20via the communications interface31(in M20). In this embodiment, when returning the electric car100used, the user chooses one separate parking space (e.g., a separate parking space416A) from vacant separate parking spaces416and parks (i.e., returns) the electric car100in the separate parking space416chosen. Each of the plurality of separate parking spaces416is provided with a piece of place information to identify (determine) the place. The user returns the electric car100used to the separate parking place416A chosen with the separate parking space416A chosen regarded as a return place (hereinafter also referred to as a “return place416A”) and with place information of the separate parking space416A regarded as return place information. Then, the user connects the charging connector411of a charger41A installed in the separate parking space416A chosen to the socket111of the electric car100returned to the separate parking space416A chosen. Thereafter, using the terminal device50, the user transmits, as the return notification, return information including his or her own user ID and return place information about the return place416A chosen, to the use management system30. Then, the accepter331of the use management system30accepts the return information from the terminal device50via the communications interface31.

The acquirer231of the charging management system20acquires the return information (i.e., the user ID and the return place information) from the use management system30via the communications interface21(in M20). On acquiring the return information from the use management system30, the acquirer231sends a request for the connection status information of the charger41A installed in the return place416A, identified by the return place information included in the return information, to the power supply system40via the communications interface21(in M21). Note that the request for the connection status information includes the return place information included in the return information.

The management device45of the power supply system40acquires the request for connection status information from the charging management system20via the gateway44(in M21). Then, the management device45acquires the connection status information from the charger41A installed in the return place416A, identified by the return place information included in the request for connection status information acquired, and transmits the connection status information thus acquired to the charging management system20via the gateway44(in M22).

The acquirer231of the charging management system20acquires the connection status information from the power supply system40via the communications interface21(in M22). Then, the decider236of the charging management system20determines, based on the connection status information acquired by the acquirer231, whether the return of the electric car100from the user is completed. That is to say, if the connection status information indicates that the charging connector411of the charger41A is connected to the socket111of the electric car100, the decider236decides that the return of the electric car100from the user be completed (i.e., return completed) (in S16). On the other hand, if the connection status information indicates that the charging connector411of the charger41A has not been connected to the socket111of the electric car100yet, then the decider236decides that the return of the electric car100from the user be incomplete (i.e., return incomplete) (in S19).

If the decider236decides that the return be completed (in S16), the determiner233of the charging management system20updates the charging schedule upon the completion of the return (in S17). That is to say, to charge the storage battery110of the electric car100that has been returned, the determiner233reorganizes (i.e., updates) the charging schedule. In this manner, the determiner233changes (updates) the charging schedule to charge the electric car100that has been returned. Then, the controller234of the charging management system20controls the power supply system40following the charging schedule updated (in M23). Thus, the power supply system40charges the electric car100following the charging schedule updated (in S18).

If the decider236decides that the return be incomplete (in S19), then the notifier235of the charging management system20performs processing to transmit a return incomplete notification to the terminal device50(i.e., the terminal device of the user who has returned the electric car100to the return place416A) (in M24). More specifically, the notifier235sends a request for transmitting a return incomplete notification to the terminal device50(notification transmission request) to the use management system30. As used herein, the “return incomplete notification” refers to a notification informing that the charging connector411of the charger41A at the return place416A is not connected to the socket111of the electric car100.

On receiving the notification transmission request from the charging management system20via the communications interface31(in M24), the notifier333of the use management system30transmits the return incomplete notification to the terminal device50via the communications interface31(in M25).

When the communications interface52receives the return incomplete notification from the use management system30(in M25), the terminal device50informs the user of the contents of the return incomplete notification (that the charging connector411of the charger41A at the return place416A is not connected to the socket111of the electric car100) via the input/output interface51. This enables prompting the user to connect the charging connector411of the charger41A to the socket111of the electric car100that he or she has returned to the return place416A.

On checking the contents of the return incomplete notification on the terminal device50, the user connects the charging connector411of the charger41A to the socket111of the electric car100that he or she has returned to the return place416A. Then, the user retransmits, using the terminal device50, the return information to the use management system30(in M26). In response, the use management system30, the charging management system20, and the power supply system40perform the processing steps (M26-M29) following the same flow as the processing steps (M19-M22) described above. As a result, the decider236of the charging management system20decides, this time, that the return be completed (in S20). Then, as in the flow of the above-described processing (S18, M23, S18), the determiner233of the charging management system20updates the charging schedule so that the charging schedule includes charging the electric car100returned (in S21). Thereafter, the controller234of the charging management system20controls the power supply system40following the charging schedule thus updated (in M30). Thus, the power supply system40charges the plurality of electric cars100as per the charging schedule thus updated (in S22).

As can be seen from the foregoing description, the charging management system20includes the acquirer231and the decider236. The acquirer231acquires connection status information indicating whether the charging connector411of a charger41is connected to the socket111of an electric car (electric vehicle)100. The decider236determines, depending on whether the connection status information acquired by the acquirer231indicates that the charging connector411is connected to the socket111, whether return of the electric car100from a user is completed. Such a charging management system20may make management by determining whether the charging connector411of the charger41is connected to the socket111of the electric car100returned by the user.

The concept of the present disclosure may also be implemented as a charging management method, not just the charging management system20. The charging management method includes an acquisition step and a decision step. The acquisition step includes acquiring connection status information indicating whether the charging connector411of a charger41is connected to the socket111of an electric car (electric vehicle)100. The decision step includes determining, depending on whether the connection status information acquired by the acquirer231indicates that the charging connector411is connected to the socket111, whether return of the electric car100from a user is completed. This charging management method enables making management by determining whether the charging connector411of the charger41is connected to the socket111of the electric car100returned by the user.

The charging management system20may also be implemented using a computer system. That is to say, the method (charging management method) performed by the charging management system20may also be carried out by making a computer system execute a program. The program is a computer program designed to cause one or more processors to perform the charging management method. Such a program, as well as the charging management system, enables making management by determining whether the charging connector411of the charger41is connected to the socket111of the electric car100returned by the user.

Optionally, the charging management system20may also be implemented as, for example, a non-transitory storage medium on which a computer program is stored.

Note that the embodiment described above is only an exemplary one of various embodiments of the present disclosure and should not be construed as limiting. Rather, the exemplary embodiment may be readily modified in various manners depending on a design choice or any other factor without departing from the scope of the present disclosure. Next, variations of the exemplary embodiment will be enumerated one after another. Note that the variations to be described below may be adopted in combination as appropriate.

(2-1) First Variation

In the exemplary embodiment described above, if the decider236of the charging management system20decides that the return be incomplete, the notifier235of the charging management system20performs processing to transmit a return incomplete notification to the terminal device50owned by the user (i.e., the user who has returned the electric car100to the return place416A). As used herein, the “return incomplete” refers to a state where the charging connector411of the charger41A at the return place416A has not been connected yet to the socket111of the electric car100returned to the return place416A, thus making the return of the electric car100incomplete.

Alternatively, if the decider236of the charging management system20decides that the return be incomplete, the notifier235of the charging management system20may also perform processing to transmit a connection request notification to the terminal device50owned by a person who shares the electric car100with, and is different from, the user. As used herein, the “connection request notification” refers to a notification requesting that the charging connector411of the charger41A at the return place416A be connected to the socket111of the electric car100returned to the return place416A. That is to say, if the return of the electric car100is incomplete, another person may be requested to connect the charging connector411to the electric car100instead of the user by transmitting the connection request notification to the person's terminal device50instead of the user's terminal device50.

More specifically, the notifier235of the charging management system20sends a request for transmitting the connection request notification to the notifier333of the use management system30and the notifier333transmits, in response to the request, the connection request notification to the person's terminal device50. Note that the storage device32of the use management system30manages the communications addresses of the respective terminal devices of all sharers and the notifier333transmits, based on the communications address stored in the storage device32, the connection request notification to the person's terminal device50.

Alternatively, the notifier235of the charging management system20may transmit the connection request notification to the person's terminal device50directly not via he use management system30. In that case, the storage device22of the charging management system manages the communications addresses of the respective terminal devices50of all sharers and the notifier235transmits, based on the communications address stored in the storage device22, the connection request notification to the person's terminal device50.

(2-2) Second Variation

In the exemplary embodiment described above, if the decider236decides that the return be incomplete, the notifier235of the charging management system20transmits the notification transmission request to the use management system30(in M24). Then, on receiving the notification transmission request, the notifier333of the use management system30transmits a return completion notification to the terminal device50of the user's (in M25). Alternatively, the notifier235of the charging management system20may transmit the return completion notification to the terminal device50of the user's not via the use management system30.

(2-3) Third Variation

In the exemplary embodiment described above, the acquirer231of the charging management system20transmits a request for the connection status information to the management device45of the power supply system40(in M28). In response to the request, the management device45acquires the connection status information from the charger41and transmits the connection status information thus acquired to the acquirer231(in M29). Alternatively, the acquirer231may transmit the request for the connection status information to the charger41not via the management device45and the charger41may transmit the connection status information to the acquirer231in response to the request.

In the exemplary embodiment described above, the controller234of the charging management system20controls the plurality of chargers41via the management device45of the power supply system40. Alternatively, the controller234may control the plurality of chargers41directly, not via the management device45.

As can be seen from the foregoing description, the exemplary embodiment and its variations described above are specific implementations of the following aspects of the present disclosure.

A charging management system (20) according to a first aspect includes an acquirer (231) and a decider (236). The acquirer (231) acquires connection status information indicating whether a charging connector (411) of a charger (41) is connected to a socket (111) of an electric vehicle (100). The decider (236) determines, depending on whether the connection status information acquired by the acquirer (231) indicates that the charging connector (411) is connected to the socket (111), whether return of the electric vehicle (100) from a user is completed.

This configuration enables making management by determining whether the charging connector (411) of a charger (41) is connected to the socket (111) of an electric vehicle (100) returned by the user. This allows the electric vehicle (100) to be charged appropriately. In a charging management system (20) according to a second aspect, which may be implemented in conjunction with the first aspect, the acquirer (231) acquires return information indicating that the user has returned the electric vehicle (100). When the acquirer (231) acquires the return information, the decider (236) determines, based on the connection status information acquired by the acquirer (231), whether the return of the electric vehicle (100) from the user is completed.

This configuration enables determining, at the timing when the user has just returned the electric vehicle (100), whether the return of the electric vehicle (100) from the user is completed.

A charging management system (20) according to a third aspect, which may be implemented in conjunction with the first or second aspect, includes a notifier (235). When the decider (236) decides that the return of the electric vehicle (100) from the user be incomplete, the notifier (235) performs processing to transmit a return incomplete notification to a terminal device (50) owned by the user. The return incomplete notification informs that the charging connector (411) is not connected to the socket (111).

This configuration enables notifying the user, who has returned the electric vehicle (100), that the charging connector (411) of the charger (41) is not connected to the socket (111) of the electric vehicle (100).

In a charging management system (20) according to a fourth aspect, which may be implemented in conjunction with the third aspect, the notifier (235) performs, when the decider (236) decides that the return of the electric vehicle (100) from the user be incomplete, processing to transmit a connection request notification to a terminal device (50) owned by a person who is sharing the electric vehicle (100) with, and is different from, the user. The connection request notification requests that the charging connector (411) be connected to the socket (111).

This configuration enables requesting, when the charging connector (411) of the charger (41) is not connected to the socket (111) of the electric vehicle (100), a person who is sharing the electric vehicle (100) with, and is different from, the user that has returned the electric vehicle (100) to connect the charging connector (411) to the electric vehicle (100).

A charging management system (20) according to a fifth aspect, which may be implemented in conjunction with any one of the first to fourth aspects, includes a controller (234). When the decider (236) decides that the return of the electric vehicle (100) from the user be completed, the controller (234) controls the charger (41) to make the charger (41) charge the electric vehicle (100) following a charging schedule.

According to this configuration, it is not until a decision has been made that the return of the electric vehicle (100) be completed (i.e., the charging connector (411) be connected to the electric vehicle (100)) that the electric vehicle (100) starts being charged. This prevents the user from failing to charge the electric vehicle (100) by forgetting to connect the charging connector (411) to the electric vehicle (100).

A charging system according to a sixth aspect includes the charging management system (20) according to any one of the first to fifth aspects and the charger (41).

This configuration enables providing a charging system including the charging management system (20) and the charger (41).

A charging management method according to a seventh aspect includes an acquisition step and a decision step. The acquisition step includes acquiring connection status information indicating whether a charging connector (411) of a charger (41) is connected to a socket (111) of an electric vehicle (100). The decision step includes determining, depending on whether the connection status information acquired in the acquisition step indicates that the charging connector (411) is connected to the socket (111), whether return of the electric vehicle (100) from a user is completed.

This method enables managing the connection status indicating whether a charger (41) is connected to an electric vehicle (100) returned by the user. This allows the electric vehicle (100) to be charged efficiently.

A program according to an eighth aspect is designed to cause one or more processors to perform the charging management method according to the seventh aspect.

This enables providing a program designed to cause one or more processors to perform the charging management method described above.

REFERENCE SIGNS LIST