Charge management system, charge system, charge management method, and program
Patent Information
- Application Number
- IN202317028013
- Authority / Receiving Office
- IN · IN
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2020-11-06
- Filing Date
- 2023-04-17
- Publication Date
- 2026-07-10
- Estimated Expiration
- 2041-11-01
AI Technical Summary
Existing electric vehicle charging management systems lack an efficient method to determine whether the charging connector is connected to the socket upon vehicle return, leading to incomplete return status management.
A charging management system that includes an acquire module to acquire connection status information and a decider module to determine if the charging connector is connected to the socket, ensuring the electric vehicle return is properly recorded and scheduled for charging.
This solution ensures accurate management of electric vehicle returns and efficient charging scheduling, preventing incomplete return notifications and ensuring timely charging operations.
Abstract
Description
Technical Field
[0001] The present disclosure generally relates to a charging management system, a chargingsystem, a charging management method, and a program. More particularly, the presentdisclosure relates to a charging management system, a charging system, a charging managementmethod, and a program, all of which are configured or design to manage charging an electricvehicle.Background Art
[0002] Patent Literature 1 discloses an operating system for providing car sharing services thattemporarily 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 userand the capability of assigning an electric car to the reservation.
[0003] An operating system as disclosed in Patent Literature 1 needs to make management ofcharging an electric vehicle returned by the user. In that case, when the electric vehicle isreturned by the user, a connection status needs to be managed by determining whether a chargingconnector of a charger is connected to a socket of the electric vehicle returned.Citation ListPatent Literature
[0004] Patent Literature 1: JP 2018-18250 ASummary of Invention
[0005] It is therefore an object of the present disclosure to provide a charging managementsystem, a charging system, a charging management method, and a program, all of which areconfigured or designed to manage a connection status by determining whether a chargingconnector of a charger is connected to a socket of an electric vehicle returned by the user.
[0006] A charging management system according to an aspect of the present disclosure includesan acquire and a decider. The acquire acquires connection status information indicatingwhether a charging connector of a charger is connected to a socket of an electric vehicle. Thedecider determines, depending on whether the connection status information acquired by theacquire indicates that the charging connector is connected to the socket, whether return of theelectric vehicle from a user is completed.
[0007] A charging system according to another aspect of the present disclosure includes thecharging management system described above and the charger.
[0008] A charging management method according to still another aspect of the present disclosureincludes an acquisition step and a decision step. The acquisition step includes acquiringconnection status information indicating whether a charging connector of a charger is connectedto a socket of an electric vehicle. The decision step includes determining, depending on whetherthe connection status information acquired in the acquisition step indicates that the chargingconnector is connected to the socket, whether return of the electric vehicle from a user is completed.
[0009] A program according to yet another aspect of the present disclosure is designed to causeone or more processors to perform the charging management method described above.Brief Description of Drawings
[0010] FIG. 1 schematically illustrates a configuration for a management system according to anexemplary embodiment;FIG. 2 is a sequence chart showing the procedure of operation of the management system;FIG. 3 is a block diagram of a charging management system included in the managementsystem;FIG. 4 is a block diagram of a terminal device included in the management system;FIG. 5 is a block diagram of a power supply system included in the management system;FIG. 6 is a block diagram of a charger included in the management system;FIG. 7 is a block diagram of a use management system included in the managementsystem;FIG. 8 illustrates an exemplary use schedule of the management system;FIG. 9 illustrates an exemplary charging schedule of the management system; andFIG. 10 is a sequence chart showing another procedure of operation of a chargingmanagement system.Description of Embodiments
[0011] (1) Embodiment(1-1) OverviewFIG. 1 illustrates a management system 10 according to an exemplary embodiment. Themanagement system 10 is a system for managing the use of one or more moving vehicles 100 byone or more users. In particular, in the exemplary embodiment to be described below, themanagement system 10 is supposed to be a system for managing the use of a plurality of movingvehicles 100 (100A-100D) by a plurality of users. The management system 10 manages theplurality of moving vehicles 100 to allow each of the plurality of users to use a moving vehicle100 that meets his or her demand (i.e., a moving vehicle 100 that 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 requirespayment of fees. For example, if the plurality of moving vehicles 100 are owned by a companyand one of the moving vehicles 100 is used by a user who is an employee of the company, then nopayment of fees is required. On the other hand, if the company allows a user who is not anemployee of the company to use one of their own moving vehicles 100 (i.e., if the company rentsthe moving vehicle 100 to the user), then the user who is not employed by the company pays thefee for using the moving vehicle 100.
[0012] In this embodiment, each moving vehicle 100 includes a storage battery 110 and a socket111 (refer to FIG. 1). The storage battery 110 is a chargeable and dis chargeable secondarybattery (such as a battery). The storage battery 110 is used as a power source for the movingvehicle 100. That is to say, the storage battery 110 is used to drive a drive source (such as amotor) of the moving vehicle 100. The socket 111 is a part to / from which a charging connector411 of a charger 41 may be connected and disconnected. When the charging connector 411 ofthe charger 41 is connected to the socket 111, the socket 111 receives power from the charger 41and charges the storage battery 110 with the power received. The moving vehicle 100 may be,for example, an electric vehicle designed to travel using the electric energy stored in the storagebattery 110. Examples of the electric vehicles include an electric car designed to travel based onthe output of a motor and a plug-in hybrid car designed to travel using the output of an engine andthe output of a motor in combination. That is to say, the electric vehicle may herein refer to a carthat uses electricity as part or all of its power source. The moving vehicle 100 does not have tobe 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 vehicle 100 is supposed to be an electric car and will behereinafter referred to as an "electric car 100" as needed to make the following description moreeasily understandable.
[0013] The management system 10 may be used in, for example, car-sharing services and rents-car services. In particular, according to this embodiment, the management system 10 may beused 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 corporationbut also a person not belonging to the corporation. That is to say, the management system 10may 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.
[0014] As shown in FIG. 1, the management system 10 includes a charging management system20, a use management system 30, a power supply system 40, and terminal devices 50. Thecharging management system 20, the use management system 30, the power supply system 40,and the terminal devices 50 may be connected to a communications network 60. The powersupply system 40 includes chargers 41. In this embodiment, the charging management system20 and the chargers 41 form a charging system.
[0015] Each of the terminal devices 50 is a device that allows the user to transmit a demand forusing the electric car 100 to a moving vehicle management system 11.
[0016] The use management system 30 is a system for managing the use of one or more electriccars 100 by one or more users. For example, in response to a demand from a user, the usemanagement system 30 selects an electric car 100 that meets the user's demand from a plurality ofelectric cars 100 and assigns the electric car 100 to the user. Specifically, on the user's demand,the use management system 30 determines a use schedule for the plurality of electric cars 100 andassigns one of the electric cars 100 to the user by reference to the use schedule.
[0017] The charging management system 20 is a system for managing charging one or moreelectric cars 100 by the power supply system 40. For example, the charging management system20 appropriately controls charging one or more electric cars 100, thereby reducing the chances ofthe remaining capacity of the storage battery 110 of the electric car(s) 100 running short when theelectric car(s) 100 needs to be used. Specifically, the charging management system 20determines a charging schedule for the plurality of electric cars 100 by reference to the useschedule given by the use management system 30 and controls the power supply system 40following the charging schedule.
[0018] The power supply system 40 includes one or more chargers 41 (41A-41D) for use tocharge the electric car(s) 100. Each charger 41 may charge an electric car 100 with electricitysupplied from a power supply such as a commercial AC power supply or a distributed powersupply (such as a solar battery, a storage battery, a fuel cell, or a wind power generator). In thepower supply system 40, each charger 41 charges an electric car 100 in accordance with aninstruction from the charging management system 20 with the charging connector 411 of thecharger 41 connected to the socket 111 of the electric car 100, thereby having one or more electriccars 100 charged as per the charging schedule.
[0019] The charging management system 20 and the use management system 30 are connectedto the communications network 60 to establish the moving vehicle management system 11. Themoving vehicle management system 11 manages schedule information including the use scheduleand the charging schedule of one or more electric cars 100 and assigns, in accordance with theschedule information and a demand from a user, an electric car 100 that meets the user's demandto him or her.
[0020] FIG. 2 illustrates an exemplary operation of the management system 10. The useroperates his or her terminal device 50 to send a demand for using (hereinafter referred to as a "usedemand") an electric car 100 (in M11). The use demand from the user is transmitted from theterminal device 50 to the use management system 30. In accordance with the use demand fromthe user, the use management system 30 provides the charging management system 20 withdemand information (in M12). The demand information may include, for example, informationabout a demand period in which use of the electric car 100 is demanded. As used herein, the"demand period" refers to a period in which use of the electric car 100 is demanded by the user.The charging management system 20 generates decision information based on an amount ofavailable electricity from the storage battery 110 in the demand period of the electric car 100 (inS11). The amount of available electricity is obtained based on the use schedule of the pluralityof electric cars 100 and the demand information. The decision information is information for useto determine whether or not there is any electric car 100 available in the demand period, amongthe plurality of electric cars 100. The charging management system 20 presents the decisioninformation to the use management system 30 (in M13). The use management system 30 makes,by reference to the use demand from the user and the decision information, a decision about theavailability of the electric car 100 (i.e., determines whether or not there is any electric car 100 thatmeets the user's demand for using the electric car 100) (in S12). When finding one or moreelectric cars 100 available, the use management system 30 transmits information about the one ormore electric cars 100 available to the terminal device 50, thereby presenting the one or moreelectric cars 100 available to the user (in M14). When the user chooses, on the terminal device50, an electric car 100 that he or she wants to use from the one or more electric cars 100 available,information about the electric car 100 chosen by the user is sent to the use management system 30(in M15). In response, the use management system 30 authorizes the use of the electric car 100chosen by the user and notifies the terminal device 50 and the charging management system 20that the use of the electric car 100 has been authorized (in M16 and M17). Then, the usemanagement system 30 updates the use schedule of the plurality of electric cars 100 (in S13).Meanwhile, the charging management system 20 updates the charging schedule of the plurality ofelectric cars 100 (in S14). Thereafter, the charging management system 20 controls the powersupply system 40 (in M18), thereby charging the electric car 100 connected to each charger 41 asper the charging schedule (in S15).
[0021] Also, when returning the electric car 100 that the user has used, the user operates his orher terminal device 50 to make a return notification informing that he or she has returned theelectric car 100 used (in M19). The return notification includes a user ID and return placeinformation. The user ID is identification information to identify the user. The return placeinformation is information to identify (i.e., determine) a place where the user has returned theelectric car 100. In this embodiment, when returning the electric car 100 used, the user choosesone return place from a plurality of respecified return places and parks (i.e., returns) the electriccar 100 to the return place thus chosen. Then, the user connects the charging connector 411 of acharger 41 installed in the return place to the socket 111 of the electric car 100 returned.Thereafter, the user transmits, as the return notification, return information including his or herown user ID and return place information about the return place chosen, to the use managementsystem 30. Note that each of the plurality of respecified return places is provided withpredefined return place information. Thus, when transmitting the return notification, the usertransmits the predefined return place information.
[0022] The return notification is transmitted from the user's terminal device 50 to the usemanagement system 30. In response, the use management system 30 transfers the user ID andreturn place information, which are included in the return notification, to the charging managementsystem 20 (in M20). Then, the charging management system 20 sends a request for theconnection status information of the charger 41 installed in the return place, identified by the returnplace information, to the power supply system 40 (in M21). In response, the power supplysystem 40 transmits the connection status information of the charger 41 to the chargingmanagement system 20 (in M22). As used herein, the connection status information isinformation indicating whether the charging connector 411 of the charger 41 is connected to thesocket 111 of the electric car 100. The charging management system 20 determines, based onthe connection status information, whether the charging connector 411 of the charger 41 isconnected to the socket 111 of the electric car 100. When finding the charging connector 411connected to the socket 111, the charging management system 20 decides that the return of theelectric car 100 from the user be completed (in S16). In that case, as soon as the return of theelectric car 100 from the user is completed, the charging management system 20 updates thecharging schedule for the plurality of electric cars 100 so that the charging schedule includescharging the electric car 100 returned (in S17). Then, the charging management system 20controls the power supply system 40 (in M23), thereby charging the electric car 100 connected toeach charger 41 following the charging schedule (in S18).
[0023] In this manner, the management system 10 according to this embodiment assigns anelectric car 100 to the user. In addition, in the management system 10, the charging managementsystem 20 includes a connection checking system for checking, when the electric car 100 isreturned from the user, whether the charging connector 411 of a charger 41 is connected to theelectric car 100 returned. This connection checking system (charging management system 20) isimplemented as an acquire 231 and a decider 236 (refer to FIG. 3). In other words, theconnection checking system includes the acquire 231 and the decider 236. The acquire 231acquires the connection status information indicating whether the charging connector 411 of thecharger 41 is connected to the socket 111 of the electric car 100. The decider 236 determines,depending on whether the connection status information acquired by the acquire 231 indicatesthat the charging connector 411 is connected to the socket 111, whether the return of the electriccar 100 from the user is completed.
[0024] Such a connection checking system (charging management system 20) may makemanagement by determining whether the charging connector 411 of a charger 41 is connected tothe socket 111 of the electric car 100 returned from the user.
[0025] (1-2) DetailsNext, the management system 10 according to this embodiment will be described infurther detail. As shown in FIG. 1, the management system 10 includes the chargingmanagement system 20, the use management system 30, the power supply system 40, and theterminal devices 50. The charging management system 20, the use management system 30, thepower supply system 40, and the terminal devices 50 may be connected to the communicationsnetwork 60. In particular, the charging management system 20 and the use management system30 are connected to the communications network 60 to establish the moving vehicle managementsystem 11. In addition, the power supply system 40 includes the chargers 41. The chargingmanagement system 20 and the chargers 41 form a charging system.
[0026] The communications network 60 may include the Internet. The communicationsnetwork 60 does not have to be a network compliant with a single communications protocol butmay also be a plurality of networks compliant with multiple different communications protocols,respectively. The communications protocol may be selected from various known wired andwireless communication standards. Although illustrated in a simplified form in FIG. 1, thecommunications network 60 may include various data communications devices such as a repeaterhub, a switching hub, a bridge, a gateway, and a router.
[0027] Each of the terminal devices 50 may be used to enter information into the moving vehiclemanagement system 11 and display thereon information provided by the moving vehiclemanagement system 11. As shown in FIG. 4, the terminal device 50 includes an input / outputinterface 51, a communications interface 52, and a processor 53. The terminal device 50 may beimplemented as, for example, a desktop computer, a laptop computer, or a mobile communicationsdevice (such as a smart phone, a tablet computer, or a wearable device). In this embodiment, theterminal device 50 is implemented as a smart phone.
[0028] The input / output interface 51 includes an input device for use to operate the terminaldevice 50. The input device may include, for example, a keyboard, a mouse, a trackball, or atouch pad. In addition, the input / output interface 51 includes an image display device fordisplaying information thereon. The image display device may include a display device with areduced thickness such as a liquid crystal display or an organic EL display.
[0029] The communications interface 52 is a communications interface. The communicationsinterface 52 may be connected to the communications network 60 and has the capability ofestablishing communication over the communications network 60. The communicationsinterface 52 is compliant with a predetermined communications protocol. The predeterminedcommunications protocol may be selected from various known wired and wireless communicationstandards.
[0030] The processor 53 is configured to perform overall control on the terminal device 50, i.e.,control the input / output interface 51 and the communications interface 52. The processor 53 hasthe capability of transmitting, in response to an operating command entered through theinput / output interface 51, information entered by the user from the communications interface 52to the moving vehicle management system 11 via the communications network 60. In addition,the processor 53 also has the capability of presenting, to the user via the input / output interface 51,information provided by the moving vehicle management system 11 and received at thecommunications interface 52 over the communications network 60.
[0031] The processor 53 may be implemented as a computer system including one or moreprocessors (microprocessors) and one or more memories. That is to say, the functions of theprocessor 53 are 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 isstored in advance in the memory of the processor 53. Alternatively, the program may also bedownloaded via a telecommunications line such as the Internet or distributed after having beenstored in a non-transitory storage medium such as a memory card.
[0032] The power supply system 40 is a system for charging the storage battery 110 for use as apower source for the electric car 100. As shown in FIG. 1 the power supply system 40 is installedin a facility 400. The facility 400 may include a parking lot 410 for the electric cars 100 and abuilding 420 annexed to the parking lot 410. Examples of the facility 400 include dwellinghouses (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).
[0033] As shown in FIG. 5, the power supply system 40 includes a plurality of chargers 41 (41A-41D) for use to charge the electric cars 100, power supply equipment 42, a plurality of currentsensors 43, a gateway 44, and a management device 45.
[0034] The parking lot 410 includes a plurality of separate parking spaces 416 (416A-416D)(refer to FIG. 1). Each of the plurality of separate parking spaces 416 is a space wide enough topark a single electric car 100. The separate parking space 416 is also a charging place where theelectric car 100 is charged. The separate parking space 416 is also a return place where theelectric car 100 rented to the user is returned. Around each separate parking space 416, a singlecharger 41 associated with the separate parking space 416 is installed. That is to say, the pluralityof chargers 41 (41A-41D) are provided one to one for the plurality of separate parking spaces 416(416A-416D). The electric car 100 parked in each separate parking space 416 is charged withthe charger 41 provided for the separate parking space 416.
[0035] The chargers 41 are connected to the power supply equipment 42. Each charger 41 maycharge the storage battery 110 of an electric car 100 connected to the charger 41 with the powersupplied from the power supply equipment 42. The charger 41 may be connected to an electriccar 100 parked in its corresponding separate parking space 416. The charger 41 may use varioustypes of charging stations, which are roughly classifiable into two types, namely, standard chargingstations and rapid charging stations. In this embodiment, a standard charging station for chargingthe storage battery 110 by receiving single-phase AC power of 200 V (or 100V) is used for thechargers 41. 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 nocontrol 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, thechargers 41 are supposed to adopt the "Mode 3" scheme.
[0036] The charger 41 includes the charging connector 411, a communications interface 412, anda processor 415 as shown in FIG. 6.
[0037] The charging connector 411 is a part to be connected removable to the socket 111 of anelectric car 100 and is connected to the housing of the charger 41 via a cable. The chargingconnector 411 supplies the power, delivered from the power supply equipment 42 to the charger41, to the electric car 100 connected to the charging connector 411. The charging connector 411includes a plurality of connection terminals. The plurality of connection terminals of thecharging connector 411 are connected to a plurality of connection terminals provided for the socket111 of the electric car 100. The plurality of connection terminals of the charging connector 411corresponds one to one to the plurality of connection terminals of the socket 111. Each of theplurality of connection terminals of the charging connector 411 includes a power supply terminaland a signal terminal. The power supply terminal is a terminal for outputting power therethroughand is connected to a corresponding one (power supply terminal) of the plurality of connectionterminals of the socket 111. The signal terminal is a terminal through which a connection statussignal (such as a control pilot (CPLT) signal) is transmitted and received between the charger 41and the electric car 100 and is connected to a corresponding one (signal terminal) of the pluralityof connection terminals of the socket 111. As used herein, the "connection status signal" refersto a signal representing a connection status (e.g., either connected or unconnected) between thecharging connector 411 and the socket 111 of the electric car 100.
[0038] The communications interface 412 is connected to the gateway 44 and establishescommunication with the management device 45 and the charging management system 20 via thegateway 44.
[0039] The processor 415 is a control circuit for controlling the operation of the charger 41. Theprocessor 415 may 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 processor 415are 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 inadvance in the memory of the processor 415. Alternatively, the program may also be downloadedvia a telecommunications line such as the Internet or distributed after having been stored in a non transitory storage medium such as a memory card.
[0040] The processor 415 includes a connection status detector 413 and a controller 414.
[0041] The connection status detector 413 determines whether the charging connector 411 isconnected to the socket 111 of the electric car 100 and acquires the result of detection as connectionstatus information. More specifically, the connection status detector 413 transmits and receives,between the charger circuit of the electric car 100 and itself via the signal terminal of the chargingconnector 411, a signal for use to check the connection status between the charging connector 411and the socket 111 of the electric car 100 (i.e., a connection status signal (CPLT signal)). In thisembodiment, the connection status detector 413 has a control pilot (CPLT) function and transmitsand receives, using the CPLT function, the connection status signal (CPLT signal) between thecharger circuit for the electric car 100 and itself. As used herein, the "CPLT function" refers tothe function of checking, by transmitting and receiving the CPLT signal, whether the chargingconnector 411 of the charger 41 and the socket 111 of the electric car 100 are connected to eachother without fail and starting charging the electric car 100 if the answer is YES.
[0042] The connection status detector 413 determines, based on the voltage level of theconnection status signal supplied from the signal terminal of the charging connector 411, whetherthe charging connector 411 is connected to the socket 111. While the charging connector 411has not been connected to the socket 111 yet, the voltage level of the connection status signal is afirst voltage level (of 12 V, for example). On the other hand, in a state where the chargingconnector 411 is connected to the socket 111, the voltage level of the connection status signal is asecond voltage level (of 6 V or 9 V, for example) which is lower than the first voltage level. Whenfinding the voltage level of the connection status signal to be the first voltage level, the connectionstatus detector 413 detects that the charging connector 411 has not been connected to the socket111 yet. On the other hand, when finding the voltage level of the connection status signal to bethe second voltage level, the connection status detector 413 detects that the charging connector411 is connected to the socket 111.
[0043] In accordance with an instruction given by the management device 45, the controller 414outputs the result of detection (connection status information) by the connection status detector413 to the management device 45 and controls starting and stopping supplying power from thecharging connector 411.
[0044] The power supply equipment 42 is connected to a power grid 200 and may receive powerfrom a commercial AC power supply 210. In addition, the power supply equipment 42 is alsoconnected to distributed power supply 300 and may supply power to, or receive power from, thedistributed power supply 300. The distributed power supply 300 may be either an AC powersupply or a DC power supply. Examples of the AC power supplies include AC power generationsystems such as a wind power generation system. Examples of the DC power supplies includesolar batteries, fuel cells, and secondary batteries (storage batteries). Examples of the secondarybatteries includes nickel-hydrogen batteries and lithium-ion batteries. The power supplyequipment 42 may distribute the power supplied from either the commercial AC power supply 210or the distributed power supply 300 to the respective chargers 41. Note that the power supplyequipment 42 may have a configuration already known in the art, and a detailed description thereofwill be omitted herein.
[0045] The plurality of current sensors 43 include a first current sensor 431, and a plurality ofsecond current sensors 432A-432D. The first current sensor 431 is installed on an electrical pathbetween the power grid 200 and the power supply equipment 42 and may measure a currentsupplied from the power grid 200 to the power supply equipment 42. The second current sensors432A-432D are installed on the electrical paths between the power supply equipment 42 and thechargers 41A-41D and may measure the current supplied from the power supply equipment 42 tothe chargers 41A-41D. Note that the current sensors 43 may each have a configuration alreadyknown in the art, and a. detailed description thereof will be omitted herein.
[0046] The management device 45 may control the plurality of chargers 41. Specifically, asshown in FIG. 5, the management device 45 is connected to the gateway 44 and communicateswith the plurality of chargers 41 and the plurality of current sensors 43 via the gateway 44. Thisallows the management device 45 to control the respective chargers 41 and acquire operating statusinformation representing the operating status of the power supply system 40 and the connectionstatus information representing the connection status between the charging connectors 411 of thechargers 41 and the sockets 111 of the electric cars 100. In this embodiment, the operating statusof the power supply system 40 is represented by results of current measurements made by theplurality of current sensors 43 (including the first current sensor 431 and the plurality of secondcurrent sensors 432A-432D). The management device 45 is connected to the communicationsnetwork 60 via the gateway 44 and is ready to communicate with the charging management system20 via the gateway 44 and the communications network 60. In accordance with an instructiongiven by the charging management system 20, the management device 45 may acquire theconnection status information of the charging connector 411 from each charger 41 and transmitthe connection status information thus acquired to the charging management system 20. Inaddition, in accordance with an instruction given by the charging management system 20, themanagement device 45 controls the respective chargers 41. This enables the electric cars 100 tobe charged as per the charging schedule.
[0047] The use management system 30 is a system for managing the use of one or more electriccars 100 by one or more users. In this embodiment, the use management system 30 determinesa use schedule for the plurality of electric vehicles 100 and manages the use of the electric cars100 by reference to the use schedule.
[0048] FIG. 8 shows an exemplary use schedule. In FIG. 8, the use schedule indicates thescheduled use periods of a plurality of (e.g., four in this example) electric cars 100A-100D duringa specified period. In FIG. 8, the specified period is one day. However, this is only an exampleand should not be construed as limiting. The specified period does not have to be one day butmay also be, for example, one week, one month, or one year and may be set as appropriateaccording to the operating status of the management system 10. The scheduled use period meansa period for which the electric car 100 is scheduled to be used by the user. The scheduled useperiod is a period for which the user is allowed an exclusive use of the electric car 100. In otherwords, the scheduled use period is a period for which the user has the right to use the electric car100 exclusively. Thus, during the scheduled use period, the user is allowed to use the electric car100 freely as far as the predefined contract is fulfilled. For example, during the scheduled useperiod, the user may go anywhere by the electric car 100 or have a meal or go shopping by parkingthe electric car 100 in a parking lot.
[0049] In FIG. 8, as for the electric car 100A, a scheduled use period U11 is set as a period from08:00 to 12:00 and another scheduled use period U12 is set as a period from 14:00 to 18:00. Asfor the electric car 100B, a scheduled use period U21 is set as a period from 08:00 to 10:00 andanother scheduled use period U22 is set as a period from 16:00 to 18:00. As for the electric car100C, a scheduled use period U31 is set as a period from 08:00 to 12:00 and another scheduleduse period U32 is set as a period from 14:00 to 16:00. As for the electric car 100D, a scheduleduse period U41 is set as a period from 08:00 to 18:00.
[0050] In addition, the use management system 30 holds information about the electric energyconsumption expected with respect to each of the scheduled use periods included in the useschedule. The electric energy consumption expected corresponds to a decrease in the remainingcapacity of the storage battery 110 due to the use of the electric car 100 in the scheduled use period.Note that the electric energy consumption expected does not have to be an electric energy requiredto allow the electric car 100 to travel at a predetermined speed during the scheduled use period butmay be set with various conditions, including the attribute information of the electric car 100,taken into account. The attribute information of the electric car 100 may include at least one ofthe type, the intended use, the initial location, the destination, the distance to travel, the number ofpassengers to travel, or the mode of use. For example, if the intended use indicated by theattribute information of the electric car 100 is shopping, the electric energy consumption expectedmay be set at 50% of the electric energy required to allow the electric car 100 to travel at thepredetermined speed during the scheduled use period.
[0051] The use management system 30 includes a communications interface 31, a storage device32, and a processor 33 as shown in FIG. 7. The use management system 30 may be implementedas, for example, a server.
[0052] The communications interface 31 is a communications interface. The communicationsinterface 31 may be connected to the communications network 60 and has the capability ofestablishing communication over the communications network 60. The communicationsinterface 31 is compliant with a predetermined communications protocol. The predeterminedcommunications protocol may be selected from various known wired and wireless communicationstandards.
[0053] The storage device 32 may be used to store information to be used by the processor 33.For example, the use schedule may be stored in the storage device 32. In addition, not only theuse schedule but also the electric energy consumptions expected with respect to the scheduled useperiods included in the use schedule are stored in the storage device 32 as well. The storagedevice 32 includes one or more storage devices. The storage device may be, for example, arandom-access memory (RAM) or an electrically erasable programmable read-only memory(EEPROM).
[0054] The processor 33 is a control circuit for controlling the operation of the use managementsystem 30. The processor 33 may be implemented as a computer system including one or moreprocessors (microprocessors) and one or more memories. That is to say, the functions of theprocessor 33 are 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 isstored in advance in the memory of the processor 33. Alternatively, the program may also bedownloaded via a telecommunications line such as the Internet or distributed after having beenstored in a non-transitory storage medium such as a memory card.
[0055] The processor 33 includes an accepter 331, a decider 332, a notifier 333, and an updater334, as shown in FIG. 7. Note that in FIG. 7, the accepter 331, the decider 332, the notifier 333,and the updater 334 do not represent substantive configurations but represent functions to beperformed by the processor 33. The accepter 331, the decider 332, the notifier 333, and theupdater 334 will be described later.
[0056] The charging management system 20 is a system for managing charging one or moreelectric cars 100. In this embodiment, the charging management system 20 uses the power-supplysystem 40 to charge the plurality of electric cars 100. The electric cars 100 are supposed to becharged basically outside of their scheduled use periods. Thus, the charging management system20 determines a charging schedule by reference to the use schedule generated by the usemanagement system 30. Then, the charging management system 20 controls charging the electriccars 100 according to the charging schedule thus determined.
[0057] FIG. 9 shows an exemplary charging schedule determined by reference to the useschedule shown in FIG. 8. Note that the use schedule is also shown in FIG. 9. In FIG. 9, thecharging schedule indicates scheduled charging periods of a plurality of (e.g., four in thisembodiment) electric cars 100A-100D during a specified period. In FIG. 9, the specified periodis one day. However, this is only an example and should not be construed as limiting. Thespecified 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 managementsystem 10. The scheduled charging period means a period for which the electric car 100 isscheduled to be charged. The scheduled charging periods are set not to overlap with thescheduled use periods during the specified period.
[0058] In FIG. 9, as for the electric car 100A, a scheduled charging period C11 is set as a periodfrom 0:00 to 2:00, another scheduled charging period C12 is set as a period from 12:00 to 14:00,and still another scheduled charging period C13 is set as a period from 20:00 to 00:00. As forthe electric car 100B, a scheduled charging period C21 is set as a period from 00:00 to 04:00,another scheduled charging period C22 is set as a period from 10:00 to 16:00, still anotherscheduled charging period C23 is set as a period from 18:00 to 20:00, and yet another scheduledcharging period C24 is set as a period from 22:00 to 00:00. As for the electric car 100C, ascheduled charging period C31 is set as a period from 00:00 to 06:00, another scheduled chargingperiod C32 is 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 car 100D, a scheduled charging periodC41 is set as a period from 02:00 to 08:00 and another scheduled charging period C42 is set as aperiod from 18:00 to 00:00.
[0059] The charging management system 20 includes a communications interface 21, a storagedevice 22, and a processor 23 as shown in FIG. 3. The charging management system 20 may beimplemented as, for example, a server.
[0060] The communications interface 21 is a communications interface. The communicationsinterface 21 may be connected to the communications network 60 and has the capability ofestablishing communication over the communications network 60. The communicationsinterface 21 is compliant with a predetermined communications protocol. The predeterminedcommunications protocol may be selected from various known wired and wireless communicationstandards.
[0061] The storage device 22 may be used to store information to be used by the processor 23.For example, the charging schedule may be stored in the storage device 22. In addition, the useschedule acquired from the use management system 30 may also be stored in the storage device22. The storage device 32 includes one or more storage devices. The storage device may be,for example, a random-access memory (RAM) or an electrically erasable programmable read-onlymemory (EEPROM).
[0062] The processor 23 is a control circuit for controlling the operation of the chargingmanagement system 20. The processor 23 may be implemented as a computer system includingone or more processors (microprocessors) and one or more memories. That is to say, thefunctions of the processor 23 are performed by making the one or more processors execute one ormore (computer) programs (applications) stored in the one or more memories. In thisembodiment, the program is stored in advance in the memory of the processor 23. Alternatively,the program may also be downloaded via a telecommunications line such as the Internet ordistributed after having been stored in a non-transitory storage medium such as a memory card.
[0063] The processor 23 includes the acquire 231, a presenter 232, a determiner 233, a controller234, a notifier 235, and a decider 236 as shown in FIG. 3. Note that in FIG. 3, the acquire 231,the presenter 232, the determiner 233, the controller 234, the notifier 235, and the decider 236 donot represent substantive configurations but represent functions to be performed by the processor23.
[0064] Next, the respective constituent elements of the charging management system 20, namely,the acquire unit 231, the presenter 232, the determiner 233, the controller 234, the notifier 235,and the decider 236 and the respective constituent elements of the use management system 30,namely, the accepter 331, the decider 332, the notifier 333, and the updater 334, will be described.As shown in FIG. 2, the charging management system 20 and the use management system 30transmit and receive information to / from each other. Thus, in the following description, theseconstituent elements of the charging management system 20 and the use management system 30will be described following the flow of operations performed by the charging management system20 and the use management system 30 to give higher priority to making the following descriptioneasily understandable.
[0065] First, the respective constituent elements of the charging management system 20 and theuse management system 30 will be described with reference to FIGS. 2-7 following the flow ofoperations performed when the user rents an electric car 100.
[0066] The accepter 331 of the use management system 30 accepts the user's demand for using(hereinafter referred to as "use demand") a moving vehicle 100, which has been transmitted fromthe terminal device 50 (in M11). The user's use demand for the electric car 100 includes at leasta demand period in which use of the electric car 100 is demanded. As used herein, the demandperiod is period in which the user demands the use of the electric car 100. The user's use demandfor the electric car 100 may also include the user's attribute information and the electric car's 100attribute information. The user's attribute information may be information indicating whetherthe user belongs to a corporation. Also, the electric car's 100 attribute information may includeat 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.
[0067] The decider 332 of the use management system 30 determines whether there is anyelectric car 100 that meets the use demand accepted by the accepter 331 (i.e., the user's use demandfor the electric car 100) (in S12). In this embodiment, the decider 332 selects an electric car 100that meets the user's use demand from the plurality of electric cars 100. In selecting such anelectric car 100 that meets the user's use demand from the plurality of electric cars 100, the decider332 refers to the decision information acquired from the charging management system 20. Toacquire the decision information from the charging management system 20, the decider 332provides the charging management system 20 with demand information (in M12). The demandinformation includes information about the demand period in which use of the electric car 100 isdemanded. In this embodiment, the demand information includes information about the electricenergy required to use the electric car 100 for the demand period.
[0068] In this case, the user's use demand for the electric car 100 may include the user's attributeinformation and the electric vehicle's 100 attribute information. The electric vehicle's 100attribute information may include at least one of the type, the intended use, the initial location, thedestination, 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 car 100 and the classification of the electriccar 100 (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 placewhere the electric car 100 is stationed at the beginning of the scheduled use period. The placemay be a place where the electric car 100 is supposed to be charged. Examples of the destinationinclude a place that the user is going to visit by using the electric car 100. For example, if theuser uses the electric car 100 to go shopping, then the destination is the shop that he or she is goingto visit. On the other hand, if the user uses the electric car 100 to go on a trip, then the destinationis a sightseeing spot or accommodations that the user is going to visit. The distance to travel isthe distance that the user plans to travel by the electric car 100. The distance to travel may be thedistance to travel to make a round trip between the initial location and the destination. Thenumber 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 scheduledto get on the electric car 100. The mode of use is the mode of use of the electric car 100. Inthis embodiment, the mode of use is supposed to be a mode in which the electric car 100 is usedby a company's employee (i.e., for business use) and a mode in which the electric car 100 is usedby a person who is not a company's employee (for non-business use; such as car sharing or carrenting).
[0069] The decider 332 may obtain the electric energy required based on the attribute informationof the electric car 100. For example, if the attribute information of the electric car 100 includesthe distance to travel, then the electric energy required may be estimated based on the distance totravel. Alternatively, the distance to travel may also be estimated based on the initial locationand the destination. For example, the type of the electric car 100 and the number of passengersto travel may affect the electric mileage of the electric car 100. The electric mileage may affectthe electric energy required. Therefore, the electric energy required may be changed accordingto the type of the moving vehicle (electric car 100). Alternatively, the electric energy requiredmay also be changed according to the intended use of the moving vehicle (electric car 100).Examples of the intended use of the electric car 100 include trip and shopping. Going on a tripwill require a longer distance to travel than going shopping. Thus, if the intended use is goingon a trip, then the electric energy required is set at a larger value than in a situation where theintended use is going shopping. Optionally, the demand information may include the user'sattribute information and the electric car's 100 attribute information, both of which are includedin the user's use demand for the electric car 100. That is to say, the electric energy required doesnot have to be the electric energy required to allow the electric car 100 to operate (travel) for thedemand period but may also be set with various conditions including the attribute information ofthe electric car 100 taken into account.
[0070] The acquires 231 of the charging management system 20 acquires demand information,including information about the demand period in which use of an electric car 100 is demanded,from the use management system 30 that manages the use of a plurality of electric cars 100, eachincluding the storage battery 110 for use as a power source (in M12). In this embodiment, thedecider 332 of the use management system 30 transmits the demand information to the chargingmanagement system 20 and the acquire 231 of the charging management system 20 receives thedemand information over the communications network 60. In addition, the acquire 231 acquiresthe use schedule for the electric cars 100 from the use management system 30. At this time, theacquire 231 also acquires, from the use management system 30, information about the electricenergy consumption expected for the scheduled use period included in the use schedule.
[0071] The presenter 232 of the charging management system 20 presents the decisioninformation to the use management system 30 (in M13). The decision information is informationfor use to determine whether any electric car 100 is available in the demand period. The presenter232 generates the decision information based on the amount of available electricity in the storagebattery 110 in the demand period in which the use of the electric car 100 is demanded (in S11).In this embodiment, the decision information includes basic information. The basic informationincludes information indicating the amount of available electricity in the demand period in whichthe use of the electric car 100 is demanded (hereinafter referred to as a "first amount of availableelectricity"). Optionally, the decision information may include influence information as needed.As used herein, the "influence information" is information indicating how the use of the electriccar 100 in one or more scheduled use periods is affected by reserving the amount of availableelectricity in the storage battery 110 (first amount of available electricity) for the demand period.In particular, the influence information includes information indicating the amount of availableelectricity in the storage battery 110 (second amount of available electricity) in one or morescheduled use periods when the amount of available electricity in the storage battery 110 (firstamount of available electricity) is reserved for the demand period. In this manner, the presenter232 may present decision information, including the basic information and the influenceinformation, to the use management system 30.
[0072] The decider 332 of the use management system 30 determines, by reference to thedecision information provided by the presenter 232 of the charging management system 20,whether there is any electric car 100 that meets the user's use demand for the electric car 100 (i.e.,whether there is any electric car 100 available in the demand period) (in S12). The decider 332selects an electric car 100, of which the amount of available electricity (first amount of availableelectricity) is equal to or greater than the electric energy required to use the electric car 100 for thedemand period, as an optional moving vehicle (electric car) 100 that may be used in the demandperiod. Nevertheless, even if the first amount of available electricity is equal to or greater thanthe electric energy required but the second amount of available electricity is less than the electricenergy consumption expected, then the electric car 100 should be regarded as non-usable in thedemand period. Thus, the decider 332 excludes a moving vehicle (electric car) 100, of which thesecond amount of available electricity in a scheduled use period following the demand period isless than the electric energy consumption expected, from the list of moving vehicles (electric cars)100 that may be used in the demand period.
[0073] Optionally, the decider 332 may also regard even a moving vehicle (electric car) 100, ofwhich the second amount of available electricity in the scheduled use period following the demandperiod is less than the electric energy consumption expected, as an optional moving vehicle(electric car) 100 that may be used in the demand period with a collateral condition presented tothe user. In this case, the collateral condition is that the user agrees to use a moving vehicle 100,of which the second amount of available electricity is less than the electric energy consumptionexpected. In other words, the collateral condition is that the user agrees to charge the movingvehicle 100 by him- or herself. In that case, the use management system 30 may offer a discounton the fee for using the moving vehicle 100 as an advantage on the condition that the user agreesto use a moving vehicle 100, of which the second amount of available electricity is less than theelectric energy consumption expected.
[0074] In this manner, according to this embodiment, the decider 332 selects, based on thedecision information, one or more moving vehicles (electric cars) 100 that may be used in thedemand period, as electric car (s) 100 that meet the user's use demand for the electric cars 100.
[0075] The notifier 333 of the use management system 30 transmits notification information tonotify the user of the one or more electric cars 100 that have been selected by the decider 332 aselectric cars 100 that meet the user's use demand (i.e., electric cars 100 that may be used in thedemand period) to the terminal device 50 (in M14). This allows the terminal device 50 to presentthe information about the one or more electric cars 100 selected by the decider 332 as optionalelectric cars 100 that meet the user's use demand to the user via the input / output interface 51.The user may choose, by operating the input / output interface 51, any desired electric car 100 fromthe one or more electric cars 100 presented on the input / output interface 51. Then, the terminaldevice 50 transmits information about the electric car 100 chosen by the user to the usemanagement system 30 (in M15). If there is no electric car 100 that meets the user's use demand,then the user may be notified that there are no electric cars 100 that meet his or her use demand.
[0076] The updater 334 of the use management system 30 receives information about the electriccar 100 chosen by the user from the terminal device 50 (in M15). The updater 334 notifies theterminal device 50 and the charging management system 20 that the scheduled use period is fixedwith the electric car 100 chosen by the user (in M16, M17). The updater 334 changes the useschedule to set a period corresponding to the demand period as the scheduled use period withrespect to the electric car 100 chosen by the user. In this manner, the updater 334 changes(updates) the use schedule according to the user's demand (in S13). In addition, the updater 334also sets the electric energy required for the demand period as the electric energy consumptionexpected for the newly set scheduled use period.
[0077] On being notified by the updater 334 that the scheduled use period is fixed with theelectric car 100 chosen by the user, the determiner 233 of the charging management system 20determines (updates) the charging schedule since the use schedule has been changed by fixing thescheduled use period (in S14). That is to say, to reduce the chances of the remaining capacity ofthe storage battery 110 of the electric car 100 running short when needed now that a new scheduleduse period has been added to the use schedule, the determiner 233 reorganizes (updates) thecharging schedule. For example, the charging schedule may be changed to compensate for thedecrease in the remaining capacity of the storage battery 110 at the end of the use schedule. Inthis manner, the determiner 233 changes (updates) the charging schedule in response to a change(update) of the use schedule.
[0078] The controller 234 of the charging management system 20 controls the power supplysystem 40 (in M18). More specifically, the controller 234 controls the power supply system 40according to the updated charging schedule. That is to say, the controller 234 controls chargingat least one of the respective storage batteries 110 of the plurality of electric cars 100 according tothe updated charging schedule. Specifically, in each scheduled charging period of the chargingschedule, the controller 234 has each electric car 100 charged with its associated charger 41.Thus, the power supply system 40 performs charging the electric car (s) 100 following the chargingschedule (in S15).
[0079] Next, the respective constituent elements of the charging management system 20 and theuse management system 30 will be described with reference to FIGS. 2-4 and FIG. 10 followingthe flow of operations performed when the user returns an electric car 100 used.
[0080] The accepter 331 of the use management system 30 accepts, from the terminal device 50and via the communications interface 31, a return notification informing that the moving vehicle100 has been returned to the return place (in M19). Note that the return notification includes auser ID and return place information. The user ID is identification information to identify theuser. The return place information is information to identify (i.e., determine) the place where theuser has returned the electric car 100. Then, the accepter 331 transmits the return informationthus accepted to the charging management system 20 via the communications interface 31 (inM20). In this embodiment, when returning the electric car 100 used, the user chooses oneseparate parking space (e.g., a separate parking space 416A) from vacant separate parking spaces416 and parks (i.e., returns) the electric car 100 in the separate parking space 416A chosen. Eachof the plurality of separate parking spaces 416 is provided with a piece of place information toidentify (determine) the place. The user returns the electric car 100 used to the separate parkingplace 416A chosen with the separate parking space 416A chosen regarded as a return place(hereinafter also referred to as a "return place 416A") and with place information of the separateparking space 416A regarded as return place information. Then, the user connects the chargingconnector 411 of a charger 41A installed in the separate parking space 416A chosen to the socket111 of the electric car 100 returned to the separate parking space 416A chosen. Thereafter, usingthe terminal device 50, the user transmits, as the return notification, return information includinghis or her own user ID and return place information about the return place 416A chosen, to the usemanagement system 30. Then, the accepter 331 of the use management system 30 accepts thereturn information from the terminal device 50 via the communications interface 31.
[0081] The acquire 231 of the charging management system 20 acquires the return information(i.e., the user ID and the return place information) from the use management system 30 via thecommunications interface 21 (in M20). On acquiring the return information from the usemanagement system 30, the acquire 231 sends a request for the connection status information ofthe charger 41A installed in the return place 416A, identified by the return place informationincluded in the return information, to the power supply system 40 via the communications interface21 (in M21). Note that the request for the connection status information includes the return placeinformation included in the return information.
[0082] The management device 45 of the power supply system 40 acquires the request forconnection status information from the charging management system 20 via the gateway 44 (inM21). Then, the management device 45 acquires the connection status information from thecharger 41A installed in the return place 416A, identified by the return place information includedin the request for connection status information acquired, and transmits the connection statusinformation thus acquired to the charging management system 20 via the gateway 44 (in M22).
[0083] The acquire 231 of the charging management system 20 acquires the connection statusinformation from the power supply system 40 via the communications interface 21 (in M22).Then, the decider 236 of the charging management system 20 determines, based on the connectionstatus information acquired by the acquire 231, whether the return of the electric car 100 from theuser is completed. That is to say, if the connection status information indicates that the chargingconnector 411 of the charger 41A is connected to the socket 111 of the electric car 100, the decider236 decides that the return of the electric car 100 from the user be completed (i.e., returncompleted) (in S16). On the other hand, if the connection status information indicates that thecharging connector 411 of the charger 41A has not been connected to the socket 111 of the electriccar 100 yet, then the decider 236 decides that the return of the electric car 100 from the user beincomplete (i.e., return incomplete) (in S19).
[0084] If the decider 236 decides that the return be completed (in S16), the determiner 233 of thecharging management system 20 updates the charging schedule upon the completion of the return(in S17). That is to say, to charge the storage battery 110 of the electric car 100 that has beenreturned, the determiner 233 reorganizes (i.e., updates) the charging schedule. In this manner,the determiner 233 changes (updates) the charging schedule to charge the electric car 100 that hasbeen returned. Then, the controller 234 of the charging management system 20 controls thepower supply system 40 following the charging schedule updated (in M23). Thus, the powersupply system 40 charges the electric car 100 following the charging schedule updated (in S18).
[0085] If the decider 236 decides that the return be incomplete (in S19), then the notifier 235 ofthe charging management system 20 performs processing to transmit a return incompletenotification to the terminal device 50 (i.e., the terminal device of the user who has returned theelectric car 100 to the return place 416A) (in M24). More specifically, the notifier 235 sends arequest for transmitting a return incomplete notification to the terminal device 50 (notificationtransmission request) to the use management system 30. As used herein, the "return incompletenotification" refers to a notification informing that the charging connector 411 of the charger 41Aat the return place 416A is not connected to the socket 111 of the electric car 100.
[0086] On receiving the notification transmission request from the charging management system20 via the communications interface 31 (in M24), the notifier 333 of the use management system30 transmits the return incomplete notification to the terminal device 50 via the communicationsinterface 31 (in M25).
[0087] When the communications interface 52 receives the return incomplete notification fromthe use management system 30 (in M25), the terminal device 50 informs the user of the contentsof the return incomplete notification (that the charging connector 411 of the charger 41A at thereturn place 416A is not connected to the socket 111 of the electric car 100) via the input / outputinterface 51. This enables prompting the user to connect the charging connector 411 of thecharger 41A to the socket 111 of the electric car 100 that he or she has returned to the return place416A.
[0088] On checking the contents of the return incomplete notification on the terminal device 50,the user connects the charging connector 411 of the charger 41A to the socket 111 of the electriccar 100 that he or she has returned to the return place 416A. Then, the user retransmits, usingthe terminal device 50, the return information to the use management system 30 (in M26). Inresponse, the use management system 30, the charging management system 20, and the powersupply system 40 perform the processing steps (M26-M29) following the same flow as theprocessing steps (M19-M22) described above. As a result, the decider 236 of the chargingmanagement system 20 decides, this time, that the return be completed (in S20). Then, as in theflow of the above-described processing (S18, M23, S18), the determiner 233 of the chargingmanagement system 20 updates the charging schedule so that the charging schedule includescharging the electric car 100 returned (in S21). Thereafter, the controller 234 of the chargingmanagement system 20 controls the power supply system 40 following the charging schedule thusupdated (in M30). Thus, the power supply system 40 charges the plurality of electric cars 100 asper the charging schedule thus updated (in S22).
[0089] (1-3) RecapitulationAs can be seen from the foregoing description, the charging management system 20includes the acquire 231 and the decider 236. The acquire 231 acquires connection statusinformation indicating whether the charging connector 411 of a charger 41 is connected to thesocket 111 of an electric car (electric vehicle) 100. The decider 236 determines, depending onwhether the connection status information acquired by the acquire 231 indicates that the chargingconnector 411 is connected to the socket 111, whether return of the electric car 100 from a user iscompleted. Such a charging management system 20 may make management by determiningwhether the charging connector 411 of the charger 41 is connected to the socket 111 of the electriccar 100 returned by the user.
[0090] (1-4) Non-system implementationsThe concept of the present disclosure may also be implemented as a charging managementmethod, not just the charging management system 20. The charging management methodincludes an acquisition step and a decision step. The acquisition step includes acquiringconnection status information indicating whether the charging connector 411 of a charger 41 isconnected to the socket 111 of an electric car (electric vehicle) 100. The decision step includesdetermining, depending on whether the connection status information acquired by the acquirer 231indicates that the charging connector 411 is connected to the socket 111, whether return of theelectric car 100 from a user is completed. This charging management method enables makingmanagement by determining whether the charging connector 411 of the charger 41 is connectedto the socket 111 of the electric car 100 returned by the user.
[0091] The charging management system 20 may also be implemented using a computer system.That is to say, the method (charging management method) performed by the charging managementsystem 20 may also be carried out by making a computer system execute a program. Theprogram is a computer program designed to cause one or more processors to perform the chargingmanagement method. Such a program, as well as the charging management system, enablesmaking management by determining whether the charging connector 411 of the charger 41 isconnected to the socket 111 of the electric car 100 returned by the user.
[0092] Optionally, the charging management system 20 may also be implemented as, for example,a non-transitory storage medium on which a computer program is stored.
[0093] (2) VariationsNote that the embodiment described above is only an exemplary one of variousembodiments of the present disclosure and should not be construed as limiting. Rather, theexemplary embodiment may be readily modified in various manners depending on a design choiceor any other factor without departing from the scope of the present disclosure. Next, variationsof the exemplary embodiment will be enumerated one after another. Note that the variations tobe described below may be adopted in combination as appropriate.
[0094] (2-1) First variationIn the exemplary embodiment described above, if the decider 236 of the chargingmanagement system 20 decides that the return be incomplete, the notifier 235 of the chargingmanagement system 20 performs processing to transmit a return incomplete notification to theterminal device 50 owned by the user (i.e., the user who has returned the electric car 100 to thereturn place 416A). As used herein, the "return incomplete" refers to a state where the chargingconnector 411 of the charger 41A at the return place 416A has not been connected yet to the socket111 of the electric car 100 returned to the return place 416A, thus making the return of the electriccar 100 incomplete.
[0095] Alternatively, if the decider 236 of the charging management system 20 decides that thereturn be incomplete, the notifier 235 of the charging management system 20 may also performprocessing to transmit a connection request notification to the terminal device 50 owned by aperson who shares the electric car 100 with, and is different from, the user. As used herein, the"connection request notification" refers to a notification requesting that the charging connector411 of the charger 41A at the return place 416A be connected to the socket 111 of the electric car100 returned to the return place 416A. That is to say, if the return of the electric car 100 isincomplete, another person may be requested to connect the charging connector 411 to the electriccar 100 instead of the user by transmitting the connection request notification to the person'sterminal device 50 instead of the user's terminal device 50.
[0096] More specifically, the notifier 235 of the charging management system 20 sends a requestfor transmitting the connection request notification to the notifier 333 of the use managementsystem 30 and the notifier 333 transmits, in response to the request, the connection requestnotification to the person's terminal device 50. Note that the storage device 32 of the usemanagement system 30 manages the communications addresses of the respective terminal devices50 of all sharers and the notifier 333 transmits, based on the communications address stored in thestorage device 32, the connection request notification to the person's terminal device 50.
[0097] Alternatively, the notifier 235 of the charging management system 20 may transmit theconnection request notification to the person's terminal device 50 directly not via he usemanagement system 30. In that case, the storage device 22 of the charging management system20 manages the communications addresses of the respective terminal devices 50 of all sharers andthe notifier 235 transmits, based on the communications address stored in the storage device 22,the connection request notification to the person's terminal device 50.
[0098] (2-2) Second variationIn the exemplary embodiment described above, if the decider 236 decides that the returnbe incomplete, the notifier 235 of the charging management system 20 transmits the notificationtransmission request to the use management system 30 (in M24). Then, on receiving thenotification transmission request, the notifier 333 of the use management system 30 transmits areturn completion notification to the terminal device 50 of the user's (in M25). Alternatively, thenotifier 235 of the charging management system 20 may transmit the return completionnotification to the terminal device 50 of the user's not via the use management system 30.
[0099] (2-3) Third variationIn the exemplary embodiment described above, the acquire 231 of the chargingmanagement system 20 transmits a request for the connection status information to themanagement device 45 of the power supply system 40 (in M28). In response to the request, themanagement device 45 acquires the connection status information from the charger 41 andtransmits the connection status information thus acquired to the acquire 231 (in M29).Alternatively, the acquire 231 may transmit the request for the connection status information tothe charger 41 not via the management device 45 and the charger 41 may transmit the connectionstatus information to the acquire 231 in response to the request.
[0100] (2-4) Fourth variationIn the exemplary embodiment described above, the controller 234 of the chargingmanagement system 20 controls the plurality of chargers 41 via the management device 45 of thepower supply system 40. Alternatively, the controller 234 may control the plurality of chargers41 directly, not via the management device 45.
[0101] (3) AspectsAs can be seen from the foregoing description, the exemplary embodiment and itsvariations described above are specific implementations of the following aspects of the presentdisclosure.
[0102] A charging management system (20) according to a first aspect includes an acquire (231)and a decider (236). The acquire (231) acquires connection status information indicatingwhether a charging connector (411) of a charger (41) is connected to a socket (111) of an electricvehicle (100). The decider (236) determines, depending on whether the connection statusinformation acquired by the acquire (231) indicates that the charging connector (411) is connectedto the socket (111), whether return of the electric vehicle (100) from a user is completed.
[0103] This configuration enables making management by determining whether the chargingconnector (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.
[0104] In a charging management system (20) according to a second aspect, which may beimplemented in conjunction with the first aspect, the acquire (231) acquires return informationindicating that the user has returned the electric vehicle (100). When the acquire (231) acquiresthe return information, the decider (236) determines, based on the connection status informationacquired by the acquire (231), whether the return of the electric vehicle (100) from the user iscompleted.
[0105] This configuration enables determining, at the timing when the user has just returned theelectric vehicle (100), whether the return of the electric vehicle (100) from the user is completed.
[0106] A charging management system (20) according to a third aspect, which may beimplemented in conjunction with the first or second aspect, includes a notifier (235). When thedecider (236) decides that the return of the electric vehicle (100) from the user be incomplete, thenotifier (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).
[0107] 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 theelectric vehicle (100).
[0108] In a charging management system (20) according to a fourth aspect, which may beimplemented 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, processingto transmit a connection request notification to a terminal device (50) owned by a person who issharing the electric vehicle (100) with, and is different from, the user. The connection requestnotification requests that the charging connector (411) be connected to the socket (111).
[0109] 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 theelectric 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).
[0110] A charging management system (20) according to a fifth aspect, which may beimplemented 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 becompleted, the controller (234) controls the charger (41) to make the charger (41) charge theelectric vehicle (100) following a charging schedule.
[0111] According to this configuration, it is not until a decision has been made that the return ofthe electric vehicle (100) be completed (i.e., the charging connector (411) be connected to theelectric vehicle (100)) that the electric vehicle (100) starts being charged. This prevents the userfrom failing to charge the electric vehicle (100) by forgetting to connect the charging connector(411) to the electric vehicle (100).
[0112] 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).
[0113] This configuration enables providing a charging system including the chargingmanagement system (20) and the charger (41).
[0114] A charging management method according to a seventh aspect includes an acquisitionstep and a decision step. The acquisition step includes acquiring connection status informationindicating whether a charging connector (411) of a charger (41) is connected to a socket (111) ofan electric vehicle (100). The decision step includes determining, depending on whether theconnection 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 iscompleted.
[0115] This method enables managing the connection status indicating whether a charger (41) isconnected to an electric vehicle (100) returned by the user. This allows the electric vehicle (100)to be charged efficiently.
[0116] A program according to an eighth aspect is designed to cause one or more processors toperform the charging management method according to the seventh aspect.
[0117] This enables providing a program designed to cause one or more processors to performthe charging management method described above.Reference Signs List
[0118] 20 Charging Management System41 Charger50 Terminal Device100 Electric Car (Electric Vehicle)111 Socket231 acquire234 Controller236 Decider411 Charging Outlet
Claims
1. A charging management system comprising: an acquire configured to acquire connection status information indicating whether a charging connector of a charger is connected to a socket of an electric vehicle; and a decider configured to determine, depending on whether the connection status information acquired by the acquire indicates that the charging connector is connected to the socket, whether return of the electric vehicle from a user is completed.
2. The charging management system of claim 1, wherein the acquire is configured to acquire return information indicating that the user has returned the electric vehicle, and the decider is configured to, when the acquire acquires the return information, determine, based on the connection status information acquired by the acquire, whether the return of the electric vehicle from the user is completed.
3. The charging management system of claim 1 or 2, comprising a notified configured to, when the decider decides that the return of the electric vehicle from the user be incomplete, perform processing to transmit a return incomplete notification, informing that the charging connector is not connected to the socket, to a terminal device owned by the user.
4. The charging management system of claim 3, wherein the notified is configured to, when the decider decides that the return of the electric vehicle from the user be incomplete, perform processing to transmit a connection request notification, requesting that the charging connector be connected to the socket, to a terminal device owned by a person who is sharing the electric vehicle with, and is different from, the user.
5. The charging management system of any one of claims 1 to 4, comprising a controller configured to, when the decider decides that the return of the electric vehicle from the user be completed, control the charger to make the charger charge the electric vehicle following a charging schedule.
6. A charging system comprising: the charging management system of any one of claims 1 to 5; and the charger.
7. A charging management method comprising: an acquisition step including acquiring connection status information indicating whether a charging connector of a charger is connected to a socket of an electric vehicle; and a decision step including 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.
