Charging management device

Abstract

To reduce a risk of a stolen charger.SOLUTION: A charge management apparatus 20 includes: a communication unit for communicating with a terminal device 30 of a worker delivering and recovering a charger 50 for use in charging a vehicle 40 of a user to and from a desired place of the user; and a control unit for transmitting recovery instructions for recovering the charger 50 through the communication unit to the terminal device 30 based on charging information indicating a charging state to the vehicle 40 from the charger 50.SELECTED DRAWING: Figure 1

Description

Technical Field

[0005]

[0001] The present disclosure relates to a charging management device.

Background Art

[0002] Patent Document 1 discloses a charging reservation system that allows a user to determine whether to perform a charging service by a third party when it is determined that the battery charge amount is below a predetermined value while the vehicle is parked, and reserves the execution of the charging service.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] If a charger whose connection to a vehicle has been disconnected is left unattended on the spot, there is a risk of theft.

[0005] An object of the present disclosure is to reduce the risk of a charger being stolen.

Means for Solving the Problems

[0006] The charging management device according to the present disclosure includes a communication unit that communicates with a terminal device of an operator who delivers and collects a charger for charging a user's vehicle to and from a desired location of the user, and a control unit that transmits a collection instruction for instructing the collection of the charger to the terminal device via the communication unit based on charging information indicating a charging state from the charger to the vehicle. is provided with.

Effects of the Invention

[0007] According to the present disclosure, the risk of a charger being stolen is reduced. [Brief explanation of the drawing]

[0008] [Figure 1] This figure shows the configuration of the system according to the embodiment of this disclosure. [Figure 2] This is a block diagram showing the configuration of a charging management device according to an embodiment of the present disclosure. [Figure 3] This is a flowchart showing the operation of the charging management device according to the embodiment of this disclosure. [Figure 4] This flowchart shows another operation of the charging management device according to the embodiment of this disclosure. [Figure 5] This flowchart shows another operation of the charging management device according to the embodiment of this disclosure. [Modes for carrying out the invention]

[0009] Hereinafter, one embodiment of this disclosure will be described with reference to the figures.

[0010] In each figure, identical or corresponding parts are denoted by the same reference numerals. In the description of this embodiment, the description of identical or corresponding parts will be omitted or simplified as appropriate.

[0011] Referring to Figure 1, the configuration of the system 10 according to this embodiment will be described.

[0012] The system 10 according to this embodiment comprises a charging management device 20, a terminal device 30, a vehicle 40, and a charger 50. The system 10 is used to provide a so-called on-demand charging service. An on-demand charging service is a service in which a worker OP transports the charger 50 in a charger transport vehicle VH or the like, and delivers and collects it at any location 100 desired by the user. In this embodiment, the worker OP patrols the service area of ​​the on-demand charging service in the charger transport vehicle VH, and delivers and collects the charger 50.

[0013] The charging management device 20 can communicate with the terminal device 30 and the vehicle 40 via a network 60 such as the Internet. The charging management device 20 may also be able to communicate with the charger 50 via the network 60.

[0014] The charging management device 20 is installed in a facility such as a data center and is operated by an administrator who manages the system 10. In this embodiment, the administrator who manages the system 10 is, for example, a business operator that provides on-demand charging services. The charging management device 20 is, for example, a computer such as a server belonging to a cloud computing system or other computing system. The charging management device 20 may be installed in the control room of the system 10 and used by the administrator. Alternatively, the charging management device 20 installed in the control room may be shared by two or more administrators. In this embodiment, the charging management device 20 controls the delivery of a charger 50 for charging the user's vehicle 40 to the user's desired location 100 by a charger transport vehicle VH by a worker OP, and the delivery of the charger according to a retrieval instruction RC.

[0015] The terminal device 30 is held by the worker OP. The terminal device 30 is, for example, a mobile device such as a mobile phone, smartphone, or tablet, or a PC. "PC" is an abbreviation for personal computer. The worker OP retrieves the charger 50 according to the retrieval instruction RC transmitted from the charging management device 20 to the terminal device 30.

[0016] Vehicle 40 is any type of automobile that uses electricity for at least part of its drive, such as an HEV, PHEV, BEV, or FCEV. "HEV" is an abbreviation for hybrid electric vehicle. "PHEV" is an abbreviation for plug-in hybrid electric vehicle. "BEV" is an abbreviation for battery electric vehicle. "FCEV" is an abbreviation for fuel cell electric vehicle. Although vehicle 40 is an automobile in this embodiment, it may be a vehicle dedicated to MaaS. Vehicle 40 may also be an AV with an automated driving level of any degree. "AV" is an abbreviation for autonomous vehicle. The level of automation may be, for example, any of levels 1 to 5 in the SAE classification. "SAE" is an abbreviation for Society of Automotive Engineers. The number of vehicles 40 provided in system 10 may be arbitrarily determined. In this embodiment, vehicle 40 is located in location 100. Location 100 is a space where vehicle 40 can be parked for the time required for charging, for example, the user's home. Location 100 includes a garage located on the user's property. The user can restrict third-party access to Location 100 by, for example, closing the gate to their house or the gate to their garage.

[0017] Network 60 includes the Internet, at least one WAN, at least one MAN, or a combination thereof. "WAN" is an abbreviation for wide area network. "MAN" is an abbreviation for metropolitan area network. Network 60 may also include at least one wireless network, at least one optical network, or a combination thereof. Wireless networks are, for example, ad hoc networks, cellular networks, wireless LANs, satellite communication networks, or terrestrial microwave networks. "LAN" is an abbreviation for local area network.

[0018] Referring to FIG. 1, the outline of this embodiment will be described.

[0019] In this embodiment, a rush charging service is provided in which, in response to a user's request, a charger 50 for a vehicle 40 is delivered to a desired location 100 such as the user's home or a parking lot and then retrieved.

[0020] [[ID=X]]

[0021] During charging, the charger 50 is connected to the vehicle 40 and placed at an arbitrary location within the user's home compound. For example, the charger 50 may be placed in a garage or the like within the user's home compound. However, for example, a user who wants to use the vehicle 40 may remove the charger 50 from the vehicle 40 and leave it unattended during or after charging. Further, for example, the charger 50 may be left unattended in a parking lot where a third party can park, or the user may move the charger 50 outside the home compound for the retrieval vehicle. If the charger 50 left unattended or moved is left there, it can be easily stolen by a third party.

[0022] ] In this embodiment, the charging management device 20 communicates with the terminal device 30 of the operator OP. The charging management device 20 transmits a recovery instruction RC for instructing the recovery of the charger 50 to the terminal device 30 based on charging information D1 indicating the charging state from the charger 50 to the vehicle 40. The operator OP performs the recovery of the charger 50 according to the recovery instruction RC transmitted to the terminal device 30.

[0023] ​According to this embodiment, a retrieval instruction RC for the charger 50 is transmitted depending on the charging status from the charger 50 to the vehicle 40. For example, a user may disconnect the charger 50 from the vehicle 40 and leave it there after charging is complete. In this case, the charging status is determined by checking the charge rate R of the vehicle 40, and if the charge rate R is above a predetermined value, a retrieval instruction is issued, so that the charger 50 that has finished charging is quickly retrieved. Thus, the risk of theft of the charger 50 is reduced. Alternatively, the charging status is determined by checking whether there is a connection between the charger 50 and the vehicle 40, and if it is determined that there is no connection, a priority retrieval of the charger 50 is issued, so that the charger 50 that has been disconnected from the vehicle 40 can be retrieved preferentially without waiting for charging to be completed. As a result, for example, even if a user who wants to use the vehicle 40 disconnects the charger 50 from the vehicle 40 and leaves it there during charging, the charger 50 will be retrieved preferentially without waiting for charging to be completed. Thus, the risk of the charger 50 being stolen is further reduced.

[0024] Referring to Figure 2, the configuration of the charging management device 20 according to this embodiment will be described.

[0025] The charging management device 20 comprises a control unit 21, a storage unit 22, and a communication unit 23.

[0026] The control unit 21 includes at least one processor, at least one programmable circuit, at least one dedicated circuit, or any combination thereof. The processor is a general-purpose processor such as a CPU or GPU, or a dedicated processor specialized for a specific process. "CPU" is an abbreviation for central processing unit. "GPU" is an abbreviation for graphics processing unit. The programmable circuit is, for example, an FPGA. "FPGA" is an abbreviation for field-programmable gate array. The dedicated circuit is, for example, an ASIC. "ASIC" is an abbreviation for application specific integrated circuit. The control unit 21 controls each part of the charge management device 20 and executes processes related to the operation of the charge management device 20.

[0027] The storage unit 22 includes at least one semiconductor memory, at least one magnetic memory, at least one optical memory, or any combination thereof. The semiconductor memory is, for example, RAM or ROM. "RAM" is an abbreviation for random access memory. "ROM" is an abbreviation for read-only memory. The RAM is, for example, SRAM or DRAM. "SRAM" is an abbreviation for static random access memory. "DRAM" is an abbreviation for dynamic random access memory. The ROM is, for example, EEPROM. "EEPROM" is an abbreviation for electrically erasable programmable read-only memory. The storage unit 22 functions, for example, as a main memory, an auxiliary memory, or a cache memory. The storage unit 22 stores data used for the operation of the charge management device 20 and data obtained by the operation of the charge management device 20.

[0028] The communication unit 23 includes at least one communication interface, which is, for example, a LAN interface. The communication unit 23 receives data used for the operation of the charging management device 20 and transmits data obtained by the operation of the charging management device 20. In this embodiment, the communication unit 23 communicates with the terminal device 30 and the vehicle 40. The communication unit 23 may also communicate with the charger 50.

[0029] The functions of the charge management device 20 are realized by executing the program according to this embodiment on the processor acting as the control unit 21. In other words, the functions of the charge management device 20 are realized by software. The program causes the computer to perform the operations of the charge management device 20, thereby causing the computer to function as the charge management device 20. That is, the computer functions as the charge management device 20 by performing the operations of the charge management device 20 according to the program.

[0030] The program can be stored on a non-temporary computer-readable medium. Examples of non-temporary computer-readable media include flash memory, magnetic recording devices, optical discs, magneto-optical recording media, or ROM. The program can be distributed, for example, by selling, transferring, or lending portable media such as SD cards, DVDs, or CD-ROMs containing the program. "SD" is an abbreviation for Secure Digital. "DVD" is an abbreviation for digital versatile disc. "CD-ROM" is an abbreviation for compact disc read only memory. The program may also be distributed by storing it in server storage and transferring it from the server to other computers. The program may also be provided as a program product.

[0031] A computer, for example, stores a program stored on a portable medium or a program transferred from a server in its main memory. Then, the computer reads the program stored in the main memory with its processor and executes the processing according to the read program. The computer may also read the program directly from the portable medium and execute the processing according to the program. The computer may also execute the processing according to the received program sequentially each time a program is transferred to the computer from a server. Processing may also be performed by a so-called ASP-type service, which does not transfer programs from the server to the computer, but realizes its function only through execution instructions and result retrieval. "ASP" is an abbreviation for application service provider. A program includes information used for processing by an electronic computer that is equivalent to a program. For example, data that is not a direct instruction to the computer but has the nature of defining the computer's processing falls under "equivalent to a program".

[0032] Some or all of the functions of the charge management device 20 may be implemented by a programmable circuit or a dedicated circuit as the control unit 21. In other words, some or all of the functions of the charge management device 20 may be implemented by hardware.

[0033] The operation of the charge management device 20 according to this embodiment will be described with reference to Figures 3 to 5. This operation corresponds to the charge management method according to this embodiment.

[0034] In step S1 of Figure 3, the control unit 21 of the charging management device 20 acquires charging information D1 from the charger 50. The charging information D1 is information indicating the charging status of the vehicle 40. Specifically, the control unit 21 acquires charging rate data d1, which indicates the charging rate R of the vehicle 40, as charging information D1. The charging rate data d1 may be acquired by any procedure, but for example, it may be acquired by the following procedure. The control unit 21 communicates with the vehicle 40 via the communication unit 23 and receives data indicating the charge amount of the battery installed in the vehicle 40. The control unit 21 acquires the received data as charging rate data d1.

[0035] In step S2 of Figure 3, the control unit 21 of the charging management device 20 determines whether the charging rate R, indicated by the charging rate data d1 acquired as charging information D1 in step S1, is equal to or greater than the charging threshold TH1. The charging threshold TH1 can be any value, but it can be set arbitrarily within a range such that, for example, the time required to charge the vehicle 40 to 100% is within X minutes, so that it is clear that the vehicle 40 is close to being fully charged. If in step S2 it is determined that the charging rate R is equal to or greater than the charging threshold TH1, the process in step S3 is performed. On the other hand, if in step S2 it is determined that the charging rate R is less than the charging threshold TH1, the process in step S5 is performed.

[0036] In step S3 of Figure 3, the control unit 21 of the charge management device 20 determines whether a retrieval instruction RC instructing the retrieval of the charger 50 has already been transmitted. If a retrieval instruction RC has not been transmitted in step S3, the process in step S4 is performed. If a retrieval instruction RC has already been transmitted in step S3, the process in step S5 is performed.

[0037] In step S4 of Figure 3, the control unit 21 of the charging management device 20 transmits a retrieval instruction RC to the terminal device 30 via the communication unit 23, instructing the retrieval of the charger 50. Specifically, the control unit 21 transmits a normal retrieval instruction RC1 as the retrieval instruction RC, instructing the normal retrieval of the charger 50. In this embodiment, normal retrieval means that the charger 50 is retrieved when the worker OP, who is patrolling in the charger transport vehicle VH, comes close to location 100. For example, the control unit 21 creates a message M1 as the normal retrieval instruction RC1, which means "Please retrieve the charger 50," and transmits the created message M1 to the terminal device 30 via the communication unit 23. The terminal device 30 receives the message M1 from the charging management device 20 and outputs the received message M1 to an output unit such as a display. Alternatively, the terminal device 30 may output the content of the received message M1 as sound from a speaker corresponding to the output unit. Upon seeing message M1 output to terminal device 30, worker OP patrols in charger transport vehicle VH and retrieves charger 50 at location 100.

[0038] As described above, the charging management device 20 according to this embodiment transmits a retrieval instruction RC to the terminal device 30 to instruct the retrieval of the charger 50, based on charging information D1 indicating the charging status from the charger 50 to the vehicle 40. Specifically, the control unit 21 of the charging management device 20 acquires charging rate data d1 indicating the charging rate R of the vehicle 40 as charging information D1. The control unit 21 then determines whether the charging rate R indicated by the acquired charging rate data d1 is equal to or greater than the charging threshold TH1. If the control unit 21 determines that the charging rate R is equal to or greater than the charging threshold TH1, it transmits a normal retrieval instruction RC1 as a retrieval instruction RC.

[0039] With this configuration, the charger 50 is quickly retrieved once charging is complete. Therefore, the risk of theft of the charger 50 is reduced.

[0040] In the embodiment described above, the control unit 21 of the charging management device 20 may further perform the processing from steps S5 to S8 shown in Figure 3. Specifically, the control unit 21 may acquire connection data d2 indicating the connection status between the charger 50 and the vehicle 40 as charging information D1. Based on the acquired connection data d2, the control unit 21 may determine whether the charger 50 is connected to the vehicle 40, and if it is determined that the charger 50 is not connected to the vehicle 40, it may send a priority retrieval instruction RC2 as a retrieval instruction RC, which instructs the priority retrieval of the charger 50. In this embodiment, priority retrieval of the charger 50 means prioritizing the retrieval of the charger 50 without waiting for the vehicle 40 to be fully charged. This is because, even if the vehicle 40 is not fully charged, if the charger 50 is disconnected from the vehicle 40, it is desirable to prioritize the retrieval of the charger 50 from the standpoint of preventing theft.

[0041] In step S5 of Figure 3, the control unit 21 of the charging management device 20 acquires connection data d2, which indicates the connection status between the charger 50 and the vehicle 40, as charging information D1. The connection data d2 may be acquired by any procedure, but for example, it may be acquired by the following procedure. The control unit 21 communicates with the charger 50 via the communication unit 23 and receives data indicating the connection status of the cable 501 provided by the charger 50. Alternatively, the control unit 21 may acquire data indicating the locked state of the connector that connects the charger 50 to the charging port of the vehicle 40 as connection data d2. The control unit 21 acquires the received data as connection data d2.

[0042] In step S6 of Figure 3, the control unit 21 of the charging management device 20 determines whether the charger 50 is connected to the vehicle 40 based on the connection data d2 acquired as charging information D1 in step S5. For example, suppose in step S5, data indicating the connection status of the cable 501 provided by the charger 50 is received as connection data d2. In this case, the control unit 21 refers to the connection data d2 and determines that the charger 50 is not connected to the vehicle 40 if it indicates that the cable 501 is not connected. Alternatively, suppose in step S5, data indicating the lock status of the connector for connecting the charger 50 to the charging port of the vehicle 40 is received as connection data d2. In this case, the control unit 21 refers to the connection data d2 and determines that the charger 50 is not connected to the vehicle 40 if it indicates that the connector is unlocked. If it is determined in step S6 that the charger 50 is not connected to the vehicle 40, the process in step S7 is performed. On the other hand, if it is determined in step S6 that the charger 50 is connected to the vehicle 40, the process returns to step S1 and is performed again.

[0043] In step S7 of Figure 3, the control unit 21 of the charging management device 20 sets the priority PL for retrieving the charger 50. Specifically, the control unit 21 sets priority PL1 as the priority PL. In this embodiment, priority PL is an indicator of the timing for retrieving the charger 50. A higher priority PL means that the charger 50 needs to be retrieved at an earlier time. In this embodiment, the timing for retrieving the charger 50 according to priority PL1 can be arbitrarily determined as long as it is earlier than the timing for retrieval by normal retrieval.

[0044] In step S8 of Figure 3, the control unit 21 of the charging management device 20 transmits a priority retrieval instruction RC2, which instructs the priority retrieval of the charger 50, to the terminal device 30 via the communication unit 23. Specifically, the control unit 21 creates a message M2 as the priority retrieval instruction RC2, which instructs the priority retrieval of the charger 50. The control unit 21 creates a message M2 that includes the priority PL1 set in step S7. The control unit 21 transmits the created message M2 to the terminal device 30 via the communication unit 23. The terminal device 30 receives the message M2 from the charging management device 20 and outputs the received message M2 to an output unit such as a display. Alternatively, the terminal device 30 may output the contents of the received message M2 as sound from a speaker corresponding to the output unit. When worker OP sees the message M2 output to the terminal device 30, he prioritizes the retrieval of the charger 50 according to the priority PL1 included in the message M2. Specifically, the worker OP will go directly to location 100 and retrieve the charger 50 without having to patrol the service area of ​​the on-site charging service.

[0045] As described above, the control unit 21 of the charging management device 20 acquires connection data d2, which indicates the connection status between the charger 50 and the vehicle 40, as charging information D1. Based on the acquired connection data d2, it determines whether the charger 50 is connected to the vehicle 40. If it is determined that the charger is not connected, it transmits a priority retrieval instruction RC2 as a retrieval instruction RC, which instructs the charger to be retrieved preferentially.

[0046] With this configuration, the charger 50 removed from the vehicle 40 will be immediately retrieved regardless of whether charging is complete or not. Therefore, even if the user removes the charger 50 from the vehicle 40 and leaves it unattended before charging is complete, the charger 50 will be quickly retrieved without waiting for the vehicle 40 to finish charging. Thus, the risk of theft of the charger 50 can be further reduced.

[0047] In the embodiment described above, if the control unit 21 of the charging management device 20 determines that the charger 50 is not connected, it may further acquire access data D2, determine whether entry to location 100 is permitted based on the acquired access data D2, and lower the priority PL if it determines that entry to location 100 is not permitted. Access data D2 is data indicating whether entry to location 100 is permitted. Specifically, after the priority PL1 is set in step S7 of Figure 3, the control unit 21 may further perform the processing from steps S9 to S12 shown in Figure 4.

[0048] In step S9 of Figure 4, the control unit 21 of the charge management device 20 acquires access data D2. Access data D2 may be acquired by any procedure, but for example, it may be acquired by the following procedure.

[0049] For example, suppose location 100 is the user's home, and the vehicle 40 is being charged by the charger 50 in the garage on the property of that home. In this case, the control unit 21 of the charging management device 20 communicates with, for example, an imaging sensor installed on the property of the home via the communication unit 23, and receives the image captured by the imaging sensor via the communication unit 23. The control unit 21 acquires data indicating the received image as access data D2.

[0050] In step S10 of Figure 4, the control unit 21 of the charging management device 20 determines whether entry to location 100 is permitted based on the access data D2 acquired in step S9. Specifically, the control unit 21 analyzes the image shown in the access data D2 acquired in step S9 and determines whether the garage gate is closed. Alternatively, the control unit 21 may determine whether the gate to the user's home is closed. Instead of analyzing the image shown in the acquired access data D2, the control unit 21 may detect whether the gate to the home or the garage gate is locked based on information from a lock sensor attached to the gate to the home or the garage gate. If it is determined that the gate to the home or the garage gate is locked, the control unit 21 may determine that entry to location 100 is not permitted. If it is determined in step S10 that entry to location 100 is not permitted, the process in step S11 is performed. On the other hand, if it is determined in step S10 that entry to location 100 is permitted, the process returns to step S9 and is performed again.

[0051] In step S11 of Figure 4, the control unit 21 of the charging management device 20 lowers the priority PL for retrieving the charger 50. Specifically, the control unit 21 sets priority PL2, which is lower than priority PL1 set in step S7 of Figure 3. This is because, even if the charger 50 is not connected to the vehicle 40, if access to location 100 is prohibited, the risk of theft of the charger 50 is considered small, and therefore the timing of retrieving the charger 50 can be delayed. By lowering the priority PL when access to location 100 is prohibited, even if the charger 50 is not connected to the vehicle 40, the charger 50 can be retrieved by waiting until, for example, a worker OP patrolling in a charger transport vehicle VH comes near location 100. This reduces the risk of theft of the charger 50 while improving the efficiency of the worker OP's retrieval of the charger 50. In this embodiment, the timing of retrieval of the charger 50 by priority PL2 can be arbitrarily determined as long as it is later than the timing of retrieval by priority PL1. For example, the timing of the retrieval of charger 50 by priority PL2 may be the same as the timing of normal retrieval. Alternatively, the timing of the retrieval of charger 50 by priority PL2 may be earlier than the timing of normal retrieval, and later than the timing of retrieval by priority PL1.

[0052] In step S12 of Figure 4, the control unit 21 of the charging management device 20 transmits a priority retrieval instruction RC2 to the terminal device 30 via the communication unit 23, instructing the priority retrieval of the charger 50. Specifically, the control unit 21 creates a message M2' as the priority retrieval instruction RC2, instructing the priority retrieval of the charger 50. The control unit 21 creates a message M2' that includes the priority PL2 set in step S11, and transmits the created message M2' to the terminal device 30. The other processes in step S12 are the same as in step S8 of Figure 3, so their explanation is omitted. Upon seeing the message M2' transmitted to the terminal device 30, worker OP retrieves the charger 50 according to the priority PL2 included in the message M2'.

[0053] As described above, if the control unit 21 of the charging management device 20 determines that the charger 50 is not connected, it further acquires access data D2 indicating whether or not entry to location 100 is permitted, and determines whether or not entry to location 100 is permitted based on the acquired access data D2. If the control unit 21 determines that entry to location 100 is not permitted, it lowers the priority PL for retrieving the charger 50.

[0054] With this configuration, if it is determined that the charger 50 is not connected to the vehicle 40, access data D2 indicating whether or not entry to location 100 is permitted is further acquired, and a priority PL is set based on the acquired access data D2. In other words, by determining whether or not entry to location 100 is permitted, and lowering the priority PL if it is determined that entry is not permitted, the risk of theft of the charger 50 can be reduced while improving the efficiency of the recovery of the charger 50 by the worker OP.

[0055] In the embodiment described above, if it is determined in step S6 of Figure 3 that the charger 50 is not connected to the vehicle 40, the control unit 21 of the charging management device 20 may further acquire position data D3 indicating the position P1 of the charger 50, and if the distance between the position P1 indicated by the acquired position data D3 and location 100 is greater than or equal to the distance threshold TH2, it may further transmit the position data D3 to the terminal device 30. Specifically, if it is determined in step S6 of Figure 3 that the charger 50 is not connected, the control unit 21 may further perform the processing from steps S9' to S11' shown in Figure 5. The processing from steps S9' to S11' shown in Figure 5 may be performed instead of the processing from steps S9 to S11 in Figure 4, or may be performed together with the processing from steps S9 to S11 in Figure 4.

[0056] In step S9' of Figure 5, the control unit 21 of the charging management device 20 further acquires position data D3 indicating the position P1 of the charger 50. The position data D3 may be acquired by any procedure, but for example, it may be acquired by the following procedure. The control unit 21 acquires the data indicating the position P1 measured by the positioning unit of the charger 50 as position data D3. The position P1 is indicated, for example, in two-dimensional or three-dimensional coordinates. The positioning unit includes at least one GNSS receiver. GNSS is, for example, GPS, QZSS, BDS, GLONASS, or Galileo. QZSS satellites are called quasi-zenith satellites. The charger 50 transmits the data indicating the position P1 measured by the positioning unit to the charging management device 20. The control unit 21 receives the data indicating the position P1 transmitted from the charger 50 via the communication unit 23 and acquires the received data as position data D3.

[0057] In step S10' of Figure 5, the control unit 21 of the charging management device 20 determines whether the distance between the location P1 indicated by the location data D3 acquired in step S9' and location 100 is greater than or equal to the distance threshold TH2. The distance threshold TH2 can be any value, but for example, if location 100 is the user's home, it can be set arbitrarily within a range of Y meters outward from the outer perimeter of the property so that it can be determined that the charger 50 has left the property. If it is determined in step S10' that the distance threshold TH2 is greater than or equal to the distance threshold TH2, the process in step S11' is performed. On the other hand, if it is determined in step S10' that the distance threshold TH2 is less than the distance threshold TH2, the process returns to step S9' and is performed again.

[0058] In step S11' of Figure 5, the control unit 21 of the charging management device 20 further transmits the position data D3 acquired in step S9'. Specifically, the control unit 21 transmits the position data D3 indicating the position P1 of the charger 50 to the terminal device 30 via the communication unit 23.

[0059] As described above, if the control unit 21 of the charging management device 20 determines that the charger 50 is not connected, it further acquires position data D3 indicating the position P1 of the charger 50, and transmits the position data D3 again if the distance between the position P1 indicated by the acquired position data D3 and location 100 is greater than or equal to the distance threshold TH2.

[0060] With this configuration, if it is determined that the charger 50 is not connected to the vehicle 40, and the distance between the location P1 of the charger 50 and location 100 is greater than or equal to the distance threshold TH2, in addition to the charger 50 retrieval instruction RC, location data D3 indicating the location P1 of the charger 50 is transmitted to the worker OP's terminal device 30. Therefore, for example, even if the charger 50 is detached from the vehicle 40 and taken away from location 100 by a third party, the worker OP can refer to the location data D3 transmitted from the charging management device 20 to the terminal device 30, find the charger 50, and retrieve it. Thus, the risk of the charger 50 being stolen is further reduced.

[0061] This disclosure is not limited to the embodiments described above. For example, two or more blocks described in the block diagram may be combined, or one block may be divided. Instead of executing two or more steps described in the flowchart in chronological order as described, they may be executed in parallel or in a different order, depending on the processing capacity of the device performing each step, or as necessary. Other modifications are possible without departing from the spirit of this disclosure. [Explanation of Symbols]

[0062] 10 Systems 20 Charging management device 21 Control Unit 22 Memory section 23 Communications Department 30 Terminal devices 40 vehicles 50 charger 501 Cable 60 Networks 100 locations OP worker VH Charger Transport Vehicle

Claims

1. A communication unit that communicates with a terminal device of a worker who delivers and retrieves a charger for charging the user's vehicle to a location desired by the user, A control unit transmits a retrieval instruction to the terminal device via the communication unit, based on charging information indicating the charging status from the charger to the vehicle, to instruct the retrieval of the charger. In a charging management device equipped with, The control unit acquires connection data indicating the connection status between the charger and the vehicle as charging information, determines whether the charger is connected to the vehicle based on the acquired connection data, and if it is determined that the charger is not connected, transmits a priority retrieval instruction as a retrieval instruction, which instructs the charger to be retrieved preferentially without waiting for the vehicle to be fully charged.

2. The charging management device according to claim 1, wherein the control unit, when it determines that the charger is connected to the vehicle, acquires charging rate data indicating the charging rate of the vehicle as charging information, determines whether the charging rate indicated by the acquired charging rate data is equal to or greater than a charging threshold, and if it is determined to be equal to or greater than a charging threshold, transmits a normal recovery instruction as a recovery instruction.

3. The charging management device according to claim 1 or 2, wherein the control unit, when it is determined that the charger is not connected, further acquires location data indicating the location of the charger, and further transmits the location data when the distance between the location indicated by the acquired location data and the location is greater than or equal to a distance threshold.

4. The charging management device according to claim 1 or claim 2, wherein the control unit, when it is determined that the charger is not connected, further acquires access data indicating whether or not it is permitted to enter the location, determines whether or not it is permitted to enter the location based on the acquired access data, and when it is determined that entry is not permitted, lowers the priority for retrieving the charger.

Images