Charging management device, charging management method, and mobile body

Abstract

The present disclosure provides a charging management device, a charging management method, and a mobile body. The charging management device includes an interface configured to acquire information about a schedule of a user, and a control unit configured to manage a charging schedule of a battery of a mobile body used by the user based on the information about the schedule of the user. The interface outputs a query about the schedule of the user and acquires a response to the query from the user. The control unit updates the schedule of the user based on the response of the user.

Description

Technical Field

[0001] This disclosure relates to a charging management device, a charging management method, and a mobile body. Background Technology

[0002] Conventionally, structures related to vehicle battery charging, such as those disclosed in International Patent Application Publication 2020-100288, involve generating a charging schedule for a vehicle based on its predicted power consumption and charging conditions, where the predicted power consumption is calculated based on the vehicle's future driving schedule. For example, Japanese Patent Application Publication 2014-115838 discloses a method for querying a user about the vehicle's charging schedule and for changing the vehicle's charging schedule based on the query results. For example, Japanese Patent Application Publication 2016-32339 discloses a method for determining the battery charging schedule and power factor in such a way that the battery supplies the unnecessary power required to draw more power while maintaining a stable power distribution system, and satisfies the predetermined time for the battery connection to terminate. Summary of the Invention

[0003] In terms of charging mobile devices, there is a need to improve user convenience.

[0004] The purpose of this disclosure, which was made in view of the above reasons, is to improve the convenience of users.

[0005] One embodiment of the charging management device disclosed herein includes: an interface for acquiring information related to a user's schedule; and a control unit for managing the charging schedule of a mobile device's battery based on the information related to the user's schedule. The interface outputs a query related to the user's schedule and obtains a response from the user to the query. The control unit updates the user's schedule based on the user's response.

[0006] One embodiment of the charging management method disclosed herein includes acquiring information related to a user's schedule. The charging management method includes managing the charging of a mobile device used by the user based on the information related to the user's schedule. The charging management method includes outputting a query related to the user's schedule. The charging management method includes obtaining a response from the user to the query. The charging management method includes updating the user's schedule based on the user's response.

[0007] One embodiment of this disclosure provides a mobile device used by a user. The mobile device includes: a battery; an interface for acquiring information related to the user's schedule; and a control unit for managing the charging of the battery based on the information related to the user's schedule. The interface outputs queries related to the user's schedule and obtains answers to the queries from the user as information related to the user's schedule.

[0008] The charging management device, charging management method, and mobile body according to one embodiment of the present disclosure can improve user convenience. Attached Figure Description

[0009] The features, advantages, and technical and industrial significance of exemplary embodiments of the present invention will now be described with reference to the accompanying drawings, wherein like symbols denote like elements, wherein:

[0010] Figure 1 This is a schematic diagram illustrating an example of the structure of a charging management system according to one embodiment.

[0011] Figure 2 This is a block diagram illustrating an example of the structure of a charging management system according to one embodiment.

[0012] Figure 3 This is a flowchart illustrating a processing example of a charging management method according to one embodiment. Detailed Implementation

[0013] (Example of the structure of charging management system 1)

[0014] like Figure 1 as well as Figure 2 As shown, a charging management system 1 according to one embodiment includes a server 10, a mobile body 20, and a charging device 40. The mobile body 20 includes a battery 28 and is powered by electricity supplied to the battery 28. The charging device 40 charges the battery 28 using electricity supplied from a power generation device 52 via a power distribution network 50. The charging management system 1 manages the charging schedule of the battery 28 of the mobile body 20. As a charging schedule, the charging management system 1 manages the period during which the battery 28 is charged. In addition, the charging management system 1 can set a target value for the charging rate of the battery 28 through the charging schedule. The charging management system 1 can set the start time of charging the battery 28 through the charging schedule. The charging management system 1 can set the end time of charging the battery 28 through the charging schedule.

[0015] User 80 of mobile body 20 utilizes mobile body 20 by riding on it. In other words, mobile body 20 is provided for user 80 to ride on.

[0016] The charging management system 1 manages the charging schedule of the battery 28 of the mobile device 20. The charging management system 1 can manage the charging schedule of the battery 28 in a way that the user 80 of the mobile device 20 is unaware of the charging rate of the battery 28, thereby completing the charging of the battery 28. The following describes a structural example of the charging management system 1.

[0017] <Server 10>

[0018] Server 10 includes a server control unit 12 and a server interface 14. Server interface 14 is also referred to as server I / F 14.

[0019] The server control unit 12 controls the various structural units of the server 10. The server control unit 12 is also simply referred to as the control unit. The server control unit 12 may be configured to include one or more processors. In this embodiment, "processor" can be a general-purpose processor, a dedicated processor specialized for a specific process, etc., but is not limited to these. The server control unit 12 may also be configured to include one or more dedicated circuits. Dedicated circuits may include, for example, FPGAs (Field-Programmable Gate Arrays) or ASICs (Application Specific Integrated Circuits). The server control unit 12 may be configured to include dedicated circuits but not processors, or it may be configured to include both processors and dedicated circuits.

[0020] Server 10 may also include a storage unit. The storage unit may be, for example, a semiconductor memory, magnetic memory, or optical memory, but is not limited to these. The storage unit may function as a main storage device, an auxiliary storage device, or a cache memory. The storage unit may include electromagnetic storage media such as a disk. The storage unit stores any information used in the operation of server 10. For example, the storage unit may also store system programs or application programs. The storage unit may also be included in server control unit 12.

[0021] Server I / F14 outputs information or data to server control unit 12, or inputs information or data to server control unit 12. Server I / F14 is also simply referred to as interface or I / F.

[0022] Server I / F14 may include a communication module configured to communicate with mobile device 20 via network 30. The communication module may include, for example, a communication module corresponding to mobile device communication standards such as 4G (4th Generation) or 5G (5th Generation), but is not limited to these. Server I / F14 may also be configured to connect to the communication module.

[0023] Server I / F14 may include input devices that receive information or data from user 80. Input devices may include, for example, a touch panel, touch sensor, or pointing device such as a mouse. Input devices may also include physical keys. Input devices may also include audio input devices such as a microphone. Server I / F14 may also be configured to connect to input devices.

[0024] The server I / F14 may include output devices that output information or data to the user 80. Output devices may include, for example, display devices for outputting visual information such as images, characters, or graphics. Display devices may be configured as LCD (Liquid Crystal Display), organic EL (Electro-Luminescence) displays, inorganic EL displays, or PDP (Plasma Display Panel), etc. Display devices are not limited to these displays and may be configured to include various other types of displays. Display devices may be configured to include light-emitting devices such as LED (Light Emission Diode) or LD (Laser Diode), etc. Display devices may include various other devices. Output devices may include, for example, sound output devices such as speakers for outputting auditory information such as sound. Output devices are not limited to these examples and may include various other devices. The server I / F14 may also be configured to connect to output devices.

[0025] Server 10 may include one or more server devices capable of communicating with each other. Server 10 is also referred to as a charging management device.

[0026] <Movement 20>

[0027] The mobile body 20 includes a drive unit 26 and a battery 28 that supplies power to the drive unit 26. The mobile body 20 moves by the operation of the drive unit 26. The drive unit 26 may include a motor. The drive unit 26 may also include an engine. The drive unit 26 receives power supplied by the battery 28 as at least a portion of the energy that enables the drive unit 26 to operate. The battery 28 supplies power to the drive unit 26 by discharging pre-charged power. The battery 28 is charged using power supplied from the charging device 40.

[0028] The mobile body 20 also includes a battery control unit 27 for controlling the charging and discharging of the battery 28. The battery control unit 27 is connected to the charging device 40 and the drive unit 26. The battery control unit 27 can control the charging current flowing from the charging device 40 to the battery 28, thereby controlling the charging from the charging device 40 to the battery 28. The battery control unit 27 can control the discharging from the battery 28 to the drive unit 26 by controlling the discharging current flowing from the battery 28 to the drive unit 26.

[0029] The mobile unit 20 also includes a mobile unit control unit 22. The mobile unit control unit 22 controls the movement of the mobile unit 20 by controlling the drive unit 26. The mobile unit control unit 22 can also control the charging and discharging of the battery 28 by controlling the battery control unit 27. The mobile unit control unit 22 is also simply referred to as the control unit. The mobile unit control unit 22 may include one or more processors. The mobile unit control unit 22 may include one or more dedicated circuits without a processor, or it may include both a processor and one or more dedicated circuits. The mobile unit control unit 22 may also be configured to include a storage unit.

[0030] The mobile unit 20 also includes a mobile unit interface 24. The mobile unit interface 24 is also referred to as mobile unit I / F 24. The mobile unit I / F 24 is also simply referred to as an interface or I / F. The mobile unit I / F 24 can be configured to include a communication module capable of communicating with the server 10 via the network 30. The communication module of the mobile unit I / F 24 can be configured to have the same or similar structure as the communication module exemplified as the server I / F 14. The mobile unit I / F 24 can also be configured to connect to the communication module. The mobile unit I / F 24 can, for example, be configured to include an in-vehicle communication unit. The mobile unit I / F 24 can communicate with the mobile unit control unit 22 and the battery control unit 27 via, for example, an in-vehicle network such as CAN (Controller Area Network) or a dedicated line.

[0031] The mobile body 20 also includes a mobile body terminal 25, but this is not mandatory. The mobile body terminal 25 can be located inside the mobile body 20. If the mobile body 20 is a vehicle, the mobile body terminal 25 can be configured as, for example, a navigation device. The mobile body terminal 25 is not limited to these examples and can include various instruments.

[0032] Mobile terminal 25 may include a control unit configured to include a processor, etc. Mobile terminal 25 may include a storage unit. Mobile terminal 25 may be connected to mobile I / F 24 for communication. Mobile terminal 25 may output information to server 10 or retrieve information from server 10 via mobile I / F 24 and network 30. Mobile terminal 25 may include an input device for receiving input from user 80. The input device of mobile terminal 25 may be configured to be the same as or similar in structure to the input device exemplified as server I / F 14. Mobile terminal 25 may include an output device for outputting information to user 80. The output device of mobile terminal 25 may be configured to be the same as or similar in structure to the output device exemplified as server I / F 14. The server control unit 12 of server 10 or the mobile control unit 22 of mobile 20 may both receive input from user 80 from mobile terminal 25 and output information notified to user 80 to mobile terminal 25.

[0033] Mobile terminal 25 may also be included in mobile I / F 24. Mobile I / F 24 may include an input device for receiving information or data from user 80 of mobile I / F 20. Mobile I / F 24 may also be configured to connect to an input device. The input device of mobile I / F 24 may be configured to be the same as or similar in structure to the input device exemplified as server I / F 14. Mobile I / F 24 may include an output device for outputting information or data to user 80 of mobile I / F 20. Mobile I / F 24 may also be configured to connect to an output device. The output device of mobile I / F 24 may be configured to be the same as or similar in structure to the output device exemplified as server I / F 14.

[0034] The mobile unit control unit 22 is connected to the network 30 via the mobile unit I / F 24 to enable communication. The mobile unit control unit 22 can obtain information from the server 10 instructing the charging of the battery 28. This information instructing the charging of the battery 28 is also referred to as charging instruction information. The charging instruction information may include information specifying the time to begin charging the battery 28. That is, the charging instruction information may include information related to the charging schedule of the battery 28. The charging instruction information may include information specifying a target value for the charging rate of the battery 28. The mobile unit control unit 22 can control the battery control unit 27 based on the charging instruction information obtained from the server 10, thereby controlling the charging of the battery 28.

[0035] The battery control unit 27 is connected to the network 30 via the mobile unit I / F 24 for communication. The battery control unit 27 can output information related to the charging rate of the battery 28 to the server 10. The battery control unit 27 can obtain charging instruction information from the server 10. Based on the charging instruction information obtained from the server 10, the battery control unit 27 can control the charging of the battery 28.

[0036] The battery control unit 27 can also be integrally formed with the battery 28. That is, the function of the battery control unit 27 can also be implemented by the structure included in the battery 28. Alternatively, the battery control unit 27 can also be included in the mobile body control unit 22. That is, the function of the battery control unit 27 can also be implemented by the mobile body control unit 22.

[0037] The number of mobile bodies 20 managed by the charging management system 1 is not limited to one, but may be two or more. Mobile bodies 20 can also be moved by the user 80 through driving or operation. Mobile bodies 20 can also be moved through autonomous driving or automatic operation controlled by the mobile body control unit 22. When the mobile body 20 is a vehicle, autonomous driving may be implemented, for example, according to any level from SAE (Society of Automotive Engineers) Level 1 to Level 5. Autonomous driving is not limited to the illustrated definition and may be implemented based on other definitions.

[0038] The mobile body 20 may also include a location information acquisition unit. This unit acquires the location information of the mobile body 20 itself. The location information acquisition unit may include a receiver corresponding to a satellite positioning system. For example, the receiver corresponding to a satellite positioning system may include a GPS (Global Positioning System) receiver. The mobile body 20 can output the location information acquired by the location information acquisition unit from the mobile body I / F 24 to the server 10. The mobile body control unit 22 can control autonomous driving based on the location information of the mobile body 20.

[0039] <User Terminal 70>

[0040] The charging management system 1 may also include a user terminal 70. The user terminal 70 can be carried by a user 80 of the mobile body 20. The user terminal 70 can be configured to be used even when the user 80 leaves the mobile body 20. The user terminal 70 may include, for example, a portable terminal such as a smartphone. The user terminal 70 may include a PC such as a laptop PC (Personal Computer) or a tablet PC. The user terminal 70 is not limited to these examples and may include various instruments.

[0041] User terminal 70 may include a control unit configured to include a processor, etc. User terminal 70 may include a storage unit. User terminal 70 may include a communication unit configured to include a communication module capable of communicating with server 10 or mobile unit 20 via network 30. The communication module may include, for example, a communication module corresponding to mobile communication standards such as 4G (4th Generation) or 5G (5th Generation), but is not limited to these. User terminal 70 may include an input device for receiving input from user 80. User terminal 70 may include an output device for outputting information to user 80. Server control unit 12 of server 10 or mobile unit control unit 22 of mobile unit 20 can both receive input from user 80 from user terminal 70 and output information notified to user 80 to user terminal 70.

[0042] <Charging device 40 and power distribution network 50>

[0043] The charging device 40 supplies power to the battery control unit 27 to charge the battery 28. The charging device 40 supplies power from the power distribution network 50 to the battery control unit 27.

[0044] The power distribution network 50 electrically connects power supply sources such as power generation equipment 52 to power supply destinations such as charging devices 40. In this embodiment, the power distribution network 50 is configured to electrically connect the power generation equipment 52 and the charging device 40, enabling it to supply power from the power generation equipment 52 to the charging device 40.

[0045] Power generation equipment 52 includes, for example, power plants that generate electricity through various means such as thermal power generation, hydropower generation, nuclear power generation, or renewable energy generation. Renewable energy generation includes, for example, solar power generation, wind power generation, geothermal power generation, or hydropower generation.

[0046] In this embodiment, the charging management system 1 is configured to communicate with the power distribution network server 54 via network 30. The power distribution network server 54 may be configured to be the same as or similar to server 10. The power distribution network server 54 acquires information related to the state of the power distribution network 50. This information related to the state of the power distribution network 50 is also referred to as power distribution network information. The power distribution network information includes information related to the power demand of the power supply destination of the power distribution network 50. The power distribution network server 54 may generate information indicating the power output of the power generation equipment 52, which serves as the power supply source, and output it to the power generation equipment 52 to meet the power demand of the power supply destination of the power distribution network 50.

[0047] The distribution network server 54 can acquire information related to the state of the power generation equipment 52. This information is also referred to as power generation equipment information. The power generation equipment information can include information related to the electrical power that the power generation equipment 52 can output at the current point in time, as well as information related to the electrical power that is presumed the power generation equipment 52 can output in the future. Based on the power generation equipment information, the distribution network server 54 can generate information instructing the power generation capacity of the power generation equipment 52.

[0048] The power distribution server 54 can output power distribution information to the server 10 or the mobile body 20. The server control unit 12 of the server 10 or the mobile body control unit 22 of the mobile body 20 can also control the charging of the battery 28 of the mobile body 20 based on the power distribution information.

[0049] (Example of the operation of charging management system 1)

[0050] User 80 uses mobile body 20 for transportation. When mobile body 20 is used by user 80 for transportation, the electrical power consumed by the drive unit 26 of mobile body 20 is determined based on the number of passengers or the distance traveled. If the charging power of battery 28 is less than the electrical power consumed during the use of mobile body 20, battery 28 needs to be charged during user 80's use of mobile body 20. To avoid charging battery 28 during use of mobile body 20, the charging power of battery 28 needs to be greater than the electrical power consumed during use of mobile body 20.

[0051] The charging management system 1 manages the charging schedule of battery 28 and controls the charging rate of battery 28 so that user 80 of mobile device 20 does not need to worry about the charging power of battery 28 before using mobile device 20. By doing so, the convenience of user 80 is improved.

[0052] The following describes the scheme by which the server control unit 12 of the server 10 manages the charging schedule of the battery 28. The main body managing the charging schedule of the battery 28 can also be replaced by the mobile unit control unit 22 of the mobile unit 20. In other words, the function of a charging management device can be implemented by either the server control unit 12 or the mobile unit control unit 22.

[0053] The server control unit 12 or the mobile unit control unit 22 can notify the user 80 of information or receive information input from the user 80 using the mobile terminal 25 or the user terminal 70 when the user 80 is riding in the mobile unit 20 or is near the mobile unit 20. When the user 80 leaves the mobile unit 20, the server control unit 12 or the mobile unit control unit 22 can notify the user 80 of information or receive information input from the user 80 using the user terminal 70.

[0054] Charging management based on user 80's schedule

[0055] The charging management system 1 can predict the utilization plan of the mobile device 20 based on the user 80's schedule. Before the user 80 utilizes the mobile device 20, the charging management system 1 can generate or update the charging schedule of the battery 28 of the mobile device 20 based on the predicted utilization plan. The charging management system 1 can generate a charging instruction for the battery 28 based on the charging schedule and control the charging of the battery 28. By managing the charging schedule of the battery 28 based on the user 80's schedule, it is less likely that insufficient charging power of the battery 28 will occur during the utilization of the mobile device 20. As a result, the convenience for the user 80 can be improved. The following describes the scheme by which the server control unit 12 manages the charging schedule of the battery 28 based on the user 80's schedule. The scheme described below can also be executed by the mobile device control unit 22.

[0056] Server control unit 12 uses server I / F 14 to obtain information related to user 80's schedule. Server I / F 14 can accept user 80's schedule input from user 80 itself. Server I / F 14 can obtain information related to user 80's schedule from user terminal 70 or mobile terminal 25 of mobile device 20. Information related to user 80's schedule may include, for example, the time when user 80 starts using mobile device 20, the number of people using mobile device 20, or the distance or range of user 80 using mobile device 20. Information related to user 80's schedule is also called schedule information. Schedule information may also include the purpose of user 80's use of mobile device 20. Schedule information is not limited to these examples and may contain various types of information.

[0057] For example, the server control unit 12 can use the server I / F 14 to receive input from the user 80 regarding the scheduled departure time of the user 80 on a specific date (e.g., tomorrow) using the mobile unit 20. Specifically, the user 80 can input information by saying something like, "I'm going to work tomorrow, so I'll depart at 7:00 AM." The server control unit 12 can generate a charging schedule based on the voice information input from the user 80, such that the mobile unit 20 will be fully charged before 7:00 AM. The server control unit 12 can also notify the user 80 that the mobile unit 20 will be fully charged before 7:00 AM. For example, the server control unit 12 can also notify the user 80 by outputting a voice message such as, "Charged to 80% before 7:00 AM." from the mobile terminal 25 or the user terminal 70.

[0058] Server control unit 12 generates queries related to user 80's schedule and outputs them to server I / F 14, enabling the user 80's schedule to be updated with detailed or accurate information. In other words, server I / F 14 outputs queries related to user 80's schedule.

[0059] Server control unit 12 obtains answers to queries related to user 80's schedule from server I / F 14. That is, server I / F 14 prompts user 80 to input answers to queries related to user 80's schedule, and outputs the received input as an answer to server control unit 12.

[0060] Server control unit 12 updates user 80's schedule based on the received answers.

[0061] Inquiries related to user 80's schedule may include, for example, a request to confirm the scheduled departure time of user 80 on mobile device 20 tomorrow. Specifically, server control unit 12 may generate an inquiry that informs user 80 of the scheduled departure time for tomorrow, which is held by server control unit 12, and confirms whether the scheduled departure time is correct. If user 80 receives an answer such as "the scheduled departure time is incorrect," server control unit 12 may generate an inquiry to confirm the correct scheduled departure time. If user 80 receives an answer such as "the scheduled departure time is correct," server control unit 12 may generate a charging schedule for the battery 28 of mobile device 20 based on the confirmed correct scheduled departure time.

[0062] Inquiries related to user 80's schedule may include, for example, a query to confirm whether user 80 will use mobile device 20 on the weekend. Specifically, server control unit 12 may generate an inquiry to inform user 80 that user 80 has a weekend travel reservation and to confirm whether the reservation is correct. Server control unit 12 may generate an inquiry to confirm a correct reservation if user 80 receives an answer such as "the reservation is incorrect." Server control unit 12 may generate a charging schedule for mobile device 20's battery 28 based on the confirmation that the reservation is correct if user 80 receives an answer such as "the reservation is correct."

[0063] Server control unit 12 can learn user 80's schedule. For example, if information received from user 80 indicates that user 80 departs at 7:00 AM to go to work, server control unit 12 can learn that the departure time on a workday is 7:00 AM. Server control unit 12 can update user 80's schedule based on the learning results.

[0064] Server control unit 12 can predict user 80's schedule. If, for example, information received from user 80 indicates that user 80 departs at 7:00 AM to go to work, server control unit 12 can predict that user 80 also departs at 7:00 AM on other workdays. Server control unit 12 can update user 80's schedule based on this prediction.

[0065] Server control unit 12 can generate queries to confirm whether the learned or predicted schedule of user 80 is correct. Specifically, server control unit 12 can notify user 80 of the learned or predicted schedule, such as user 80 departing at 7:00 AM on a workday, by having mobile terminal 25 or user terminal 70 output a voice message such as "Tomorrow is a workday, so I will depart at 7:00 AM." Alternatively, user 80 can input information by saying a voice message such as "Tomorrow is Tuesday, so I will depart at 6:30 AM." Based on the voice information input by user 80, server control unit 12 can learn that the departure time on Tuesday is 6:30 AM and generate a charging schedule to complete the charging of mobile device 20 before 6:30 AM. Server control unit 12 can notify user 80 of the learned departure time on Tuesday by having mobile terminal 25 or user terminal 70 output a voice message such as "I have learned that the departure time on Tuesday is 6:30 AM." In addition, the server control unit 12 can also notify the user 80 that the charging of the mobile terminal 20 will be completed before 6:30 a.m. by having the mobile terminal 25 or the user terminal 70 output a sound such as "Charging to 80% before 6:30 a.m."

[0066] The server control unit 12 can also notify the user 80 of the charging schedule generated based on the user 80's schedule. For example, the server control unit 12 can notify the user 80 that the user has planned to go out with family on the weekend and has completed charging before departure by having the mobile terminal 25 or the user terminal 70 output a voice message such as "Going out with family on the weekend. Charging." Alternatively, the user 80 can input information confirming the notification from the server control unit 12 by saying a voice message such as "I forgot my plan to go out, but please charge me." The user 80 can also input information to correct the notification from the server control unit 12 by saying a voice message such as "I don't have a plan to go out." The user 80 can input information not only by voice but also by operating the touch panel or other methods.

[0067] Server control unit 12 can estimate the travel distance of user 80 using mobile device 20 based on user 80's schedule. For example, if user 80 uses mobile device 20 to go to work, server control unit 12 can estimate the travel distance based on the distance between user 80's home and workplace. Server control unit 12 can also estimate the travel distance based on the distance to a destination determined using user 80's schedule. Server control unit 12 can also estimate the destination based on user 80's schedule. Server control unit 12 can determine a target value for the charging rate of battery 28 based on the estimated travel distance. The target value for the charging rate of battery 28 is also called the target charging rate.

[0068] The server control unit 12 can set the target charging rate of the battery 28 to the maximum charging rate (e.g., 100%). The server control unit 12 can also set the target charging rate of the battery 28 to a value lower than the maximum charging rate (e.g., 80%) to prevent the battery 28 from deteriorating. The server control unit 12 can also set the target charging rate to the minimum value within a range where the user 80 can move within the target area using the mobile body 20 without charging the battery 28. The server control unit 12 can generate a charging schedule based on the difference between the target charging rate and the charging rate of the battery 28 before charging. The lower the target charging rate, the shorter the time required to complete charging of the battery 28. The server control unit 12 can also set the target charging rate using a charging schedule.

[0069] <Example of charging management method>

[0070] Server control unit 12 can also perform operations including Figure 3 The illustrated flowchart describes a charging management method. This charging management method can also be implemented as a charging management program executed by the processor constituting the server control unit 12.

[0071] Server control unit 12 obtains user 80's schedule information (step S1).

[0072] Server control unit 12 learns or predicts user 80's schedule (step S2).

[0073] Server control unit 12 outputs an inquiry to user 80 (step S3).

[0074] Server control unit 12 obtains user 80's answer (step S4).

[0075] Server control unit 12 updates user 80's schedule based on user 80's response (step S5).

[0076] Based on the user 80's schedule, the server control unit 12 determines the charging schedule of the battery 28 of the mobile body 20 used by the user 80 (step S6).

[0077] The server control unit 12 generates charging instruction information for the battery 28 based on the charging schedule and outputs it to the battery control unit 27 (step S7). The server control unit 12 can terminate execution after performing step S7. Figure 3 The processing of flowcharts.

[0078] Server control unit 12 may also be omitted. Figure 3 The illustrated steps are partial steps. For example, the server control unit 12 may omit the execution of step S2, or it may omit the execution of steps S3 and S4. The server control unit 12 may also be interchanged. Figure 3 The execution order of the illustrated steps. For example, the server control unit 12 may execute the processes of steps S3 and S4 before executing the process of step S2. For example, the server control unit 12 may return to the process of step S5 after determining the charging schedule according to the process of step S6, update the user 80's schedule, and re-determine the charging schedule according to the process of step S6.

[0079] include Figure 3 The charging management method illustrated can also be executed by the mobile unit control unit 22. The charging management method can also be implemented as a charging management program executed by the processor constituting the mobile unit control unit 22.

[0080] As explained above, the charging management system 1 of this embodiment manages the charging schedule of the battery 28 of the mobile body 20 and controls the charging of the battery 28. By doing so, the user 80 does not need to worry about the charging power of the battery 28 before using the mobile body 20. As a result, the convenience for the user 80 is improved.

[0081] (Other implementation methods)

[0082] Charging Management Based on Distribution Network Information

[0083] The charging management system 1 can manage the charging schedule of battery 28 or generate charging instructions for battery 28 based on distribution network information. By managing the charging schedule of battery 28 or generating charging instructions based on distribution network information, the power demand of distribution network 50 can be balanced. The following describes the scheme by which server control unit 12 manages the charging of battery 28 based on distribution network information. The scheme described below can also be executed by mobile unit control unit 22.

[0084] Server control unit 12 obtains power distribution information from power distribution server 54 using server I / F 14. That is, server I / F 14 obtains power distribution information from power distribution server 54 and outputs it to server control unit 12. Server control unit 12 manages the charging schedule of battery 28 based on user 80's schedule and the power distribution information.

[0085] The distribution network information may include information related to the power demand of distribution network 50. Distribution network server 54 can calculate the total amount of power supplied by distribution network 50 as the power demand in distribution network 50. Distribution network server 54 can also predict future power demand.

[0086] The server control unit 12 can determine the charging schedule of the battery 28 of the mobile unit 20 based on information related to power demand. Specifically, the server control unit 12 can determine the charging schedule in a manner that charges the battery 28 during periods of low power demand. By doing so, the power demand of the distribution network 50 can be balanced. Furthermore, when the distribution network 50 is configured to supply power to one street, the power demand of that street can be balanced.

[0087] The distribution network information may include information related to the distribution capacity of distribution network 50. Distribution capacity corresponds to the amount of electricity that can be supplied to distribution network 50. Distribution network server 54 can calculate the difference between the maximum power generation capacity of power generation equipment 52 supplying power to distribution network 50 and the current electricity demand as the current distribution capacity. Distribution network server 54 can also calculate the difference between the predicted future power generation capacity of power generation equipment 52 that generates renewable energy and the predicted future electricity demand as the future distribution capacity. Distribution network server 54 can also calculate the difference between the predicted maximum future power generation capacity that can be increased by operating idle power generation equipment 52 and the predicted future electricity demand as the future distribution capacity.

[0088] The server control unit 12 can determine the charging schedule of the battery 28 of the mobile unit 20 based on information related to power distribution capacity. Specifically, the server control unit 12 can determine the charging schedule in a manner that the battery 28 is charged during periods of high power distribution capacity. By doing so, the power supply of the power distribution network 50 can be stabilized. Furthermore, when the power distribution network 50 is configured to supply power to one street, the power supply in that street can be stabilized.

[0089] The power generation capacity of the renewable energy power generation equipment 52 can vary in response to natural conditions. The renewable energy power generation equipment 52 is also referred to as a renewable energy power generation device. For example, the power generation capacity of a solar power generation device varies in response to solar radiation. Similarly, the power generation capacity of a wind power generation device varies in response to wind speed and direction. The distribution network server 54 can predict the power generation schedule of the renewable energy power generation device based on information about future natural conditions and output this information as related to the distribution capacity of the distribution network 50.

[0090] The server control unit 12 can generate a charging instruction for the battery 28 based on the power generation schedule of the renewable energy power generation equipment. By generating the charging instruction for the battery 28 based on the power generation schedule of the renewable energy power generation equipment, it is easier to utilize renewable energy.

[0091] The server control unit 12 can also determine the charging schedule of the battery 28 of the mobile unit 20 based on the power generation schedule of renewable energy power generation equipment located within a designated area. The designated area can be set to the area where the user 80 of the mobile unit 20 resides, and whose charging schedule is managed by the charging management system 1. The designated area is defined as the region including the location of the charging device 40. The server control unit 12 can determine the charging schedule in a way that increases the proportion of electricity generated by renewable energy power generation equipment located within the designated area in the power charged to the battery 28. By charging the battery 28 with electricity generated by renewable energy power generation equipment located within the designated area, power loss from renewable energy power generation can be reduced. In other words, the utilization efficiency of renewable energy within the designated area can be improved.

[0092] A designated area can also be structured as a single street. By constructing a designated area based on a single street, the energy utilization efficiency within that single street can be improved.

[0093] <Charging Management Based on the Charging Schedule of Other Mobile Bodies 20>

[0094] The charging management system 1 can update the charging schedule of a particular mobile body 20's battery 28 based on the charging schedules of the batteries 28 of other mobile bodies 20 that are different from the mobile body 20. By taking into account the charging schedules of the batteries 28 of multiple mobile bodies 20, the power demand of the distribution network 50 can be balanced.

[0095] For example, the server control unit 12 can determine the charging schedule for the batteries 28 of each mobile unit 20 in a way that balances the number of mobile units 20 charging their batteries 28 simultaneously. For instance, the server control unit 12 can determine the charging schedule for each mobile unit 20 to avoid the simultaneous start of charging of the batteries 28 of mobile units 20 transporting users 80 to their homes during peak home hours (e.g., from 5 PM to 7 PM). Specifically, the server control unit 12 can determine the charging schedule by staggering the start times of charging for the batteries 28 of each mobile unit 20, so that charging can be completed from the time a mobile unit 20 returns to a user 80's home until its next departure. For example, the server control unit 12 can set the start time of charging for the battery 28 of one mobile unit 20 to be later than the time when charging for the battery 28 of another mobile unit 20 is completed. By doing so, the number of batteries 28 charging simultaneously can be reduced. As a result, power demand balancing can be achieved.

[0096] When the mobile control unit 22 of each mobile unit 20 determines the charging schedule, each mobile control unit 22 can output the charging schedule of the battery 28 of the mobile unit 20 to other mobile units 20 in order to share the charging schedule with other mobile units 20. The mobile control unit 22 can output the charging schedule from the mobile unit I / F 24. The mobile control unit 22 can generate the charging schedule in a way that makes it less likely for the charging period of the battery 28 controlled by the mobile control unit 22 itself to overlap with the charging period of the batteries 28 of other mobile units 20. Specifically, the mobile control unit 22 can generate the charging schedule of the battery 28 controlled by the mobile control unit 22 itself by reducing the number of batteries 28 being charged at the same time.

[0097] The server control unit 12 can determine the charging schedule of the batteries 28 of each mobile unit 20 based on the departure time of each mobile unit 20. By doing so, it is possible to complete charging before the departure time of the mobile unit 20 and reduce the number of batteries 28 being charged simultaneously.

[0098] The server control unit 12 can set the target charging rate of the battery 28 of each mobile unit 20 to a smaller value within the range that the user 80 can use the mobile unit 20, and determine the charging schedule of the battery 28 of each mobile unit 20 based on the target charging rate. By doing so, it is easy to charge the mobile unit 20 so that it can be used before the departure time of the mobile unit 20. In addition, the number of batteries 28 charged at the same time can be further reduced.

[0099] The embodiments of this disclosure have been described with reference to the accompanying drawings and examples. However, it should be noted that various modifications and alterations can be made based on this disclosure by those skilled in the art. Therefore, it should be understood that these modifications and alterations are included within the scope of this disclosure. For example, the functions included in each unit or step can be reconfigured in a logically consistent manner, and multiple units or steps can be combined into one or divided.

Claims

1. A charge management apparatus comprising: an interface configured to acquire information related to a schedule of a user; and a control unit configured to manage a charge schedule of a battery of a mobile body used by the user, based on the information related to the schedule of the user, the interface outputs a query related to the schedule of the user, and acquires an answer to the query from the user, the control unit updates the schedule of the user based on the answer of the user, and generates the charge schedule of the battery of the mobile body based on the answer of the user, the interface further acquires information related to a power distribution network that supplies power for charging the battery of the mobile body, the control unit further manages the charge schedule of the battery of the mobile body used by the user, based on the information related to the power distribution network, the control unit estimates a moving distance of the mobile body based on the schedule of the user, and sets a target value of a charge rate of the battery, i.e., a target charge rate, to a minimum value within a range in which the user can move in a target section using the mobile body without charging the battery.

2. The charge management apparatus according to claim 1, wherein the control unit learns or estimates the schedule of the user.

3. The charge management apparatus according to claim 2, wherein the control unit generates a query for confirming a learning result or an estimation result of the schedule of the user, and receives an answer from the user using the interface.

4. The charge management apparatus according to any one of claims 1 to 3, wherein the interface is configured to be connectable to an input device that receives input of information related to the schedule of the user from the user.

5. The charge management apparatus according to any one of claims 1 to 3, wherein the interface is configured to be connectable to an output device that notifies the user of information.

6. The charge management apparatus according to claim 1, wherein the control unit determines the charge schedule of the battery of the mobile body based on information related to a power distribution margin of the power distribution network.

7. The charge management apparatus according to claim 1, wherein the control unit determines the charge schedule of the battery of the mobile body based on information related to a power demand of the power distribution network.

8. The charge management apparatus according to claim 1, wherein the control unit determines the charge schedule of the battery of the mobile body based on a power generation schedule of a renewable energy power generation device that supplies power to the power distribution network.

9. The charge management apparatus according to claim 8, wherein the control unit determines the charge schedule of the battery of the mobile body based on the power generation schedule of the renewable energy power generation device located within a prescribed region.

10. The charge management apparatus according to claim 1, wherein the control unit outputs the charge schedule of the battery of the mobile body from the interface.

11. The charge management apparatus according to claim 1, wherein the control unit updates the charge schedule of the battery of the mobile body based on a charge schedule of a battery of another mobile body different from the mobile body.

12. A charge management method comprising: ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ acquiring information about a schedule of a user; managing charging of a battery of a mobile body used by the user based on the information about the schedule of the user; outputting a query about the schedule of the user; acquiring an answer to the query from the user; and updating the schedule of the user based on the answer of the user and generating a charging schedule of the battery of the mobile body based on the answer of the user, the charging management method further comprising: further acquiring information about a power distribution network that supplies power for charging the battery of the mobile body, managing the charging schedule of the battery of the mobile body used by the user based on the information about the power distribution network, estimating a moving distance of the mobile body based on the schedule of the user, and setting a target value of a charging rate of the battery, i.e., a target charging rate, to a minimum value within a range in which the user can move in a target section using the mobile body without charging the battery. further comprising:

13. The charge management method according to claim 12, wherein, learning or estimating the schedule of the user; generating a query for confirming a learning result or an estimation result of the schedule of the user and receiving an answer from the user. further comprising:

14. The charge management method of claim 12, wherein, determining the charging schedule of the battery of the mobile body based on at least one of information about a power distribution margin of the power distribution network and information about a power demand of the power distribution network.

15. A mobile body that is a mobile body used by a user, the mobile body comprising: a battery; an interface configured to acquire information about a schedule of the user; and a control unit configured to manage charging of the battery based on the information about the schedule of the user, the interface configured to output a query about the schedule of the user and acquire an answer to the query from the user as the information about the schedule of the user, the control unit configured to update the schedule of the user based on the answer of the user and generate a charging schedule of the battery of the mobile body based on the answer of the user, the interface configured to further acquire information about a power distribution network that supplies power for charging the battery of the mobile body, the control unit configured to further manage the charging schedule of the battery of the mobile body used by the user based on the information about the power distribution network, the control unit configured to estimate a moving distance of the mobile body based on the schedule of the user and set a target value of a charging rate of the battery, i.e., a target charging rate, to a minimum value within a range in which the user can move in a target section using the mobile body without charging the battery.

16. The mobile body according to claim 15, wherein the control unit is configured to: learn or estimate the schedule of the user, generate a query for confirming a learning result or an estimation result of the schedule of the user and receive an answer from the user. ​

Images