Battery management device

Abstract

A battery management device according to an embodiment of the present disclosure is capable of managing data about a plurality of batteries used by a vehicle in which a battery can be replaced and comprises: a processing circuit capable of determining, on the basis of a battery remaining amount of a first battery before replacement in a first vehicle scheduled for battery replacement at a first battery station, whether or not a second vehicle can use the first battery; and a communication circuit capable of transmitting, to the second vehicle, a notification that a second battery of the second vehicle can be replaced with the first battery at the first battery station, when the second vehicle can use the first battery.

Description

Battery Management Unit

[0001] The present disclosure relates to a battery management device that manages a battery in a vehicle with a replaceable battery.

[0002] Some vehicles, such as electric vehicles, have replaceable batteries. The batteries in such vehicles are replaced at battery stations. Patent Document 1 discloses a system that guides users to battery stations where a vehicle's battery with low remaining power can be replaced with a charged battery.

[0003] International Publication No. 2019 / 163573

[0004] According to an embodiment of the present disclosure, a battery management device includes a processing circuit and a communication circuit. The processing circuit is capable of managing data on a plurality of batteries used by vehicles having replaceable batteries, and is capable of determining whether a second vehicle can use the first battery based on a remaining battery charge of a first battery in a first vehicle scheduled for battery replacement at a first battery station. When the second vehicle is able to use the first battery, the communication circuit is capable of transmitting a notification to the second vehicle that the second battery of the second vehicle can be replaced with the first battery at the first battery station.

[0005] The accompanying drawings are included to provide a further understanding of the disclosure, and are incorporated in and constitute a part of this specification. The drawings illustrate one embodiment and, together with the description, serve to explain the principles of the disclosure.

[0006] FIG. 1 is a block diagram illustrating an example configuration of a battery management system according to an embodiment of the present disclosure. FIG. 2 is a block diagram illustrating an example configuration of an in-vehicle device illustrated in FIG. 1. FIG. 3 is a block diagram illustrating an example configuration of a battery management device illustrated in FIG. 1. FIG. 4 is an explanatory diagram illustrating an example configuration of management data illustrated in FIG. 3. FIG. 5 is an explanatory diagram illustrating an example operation of the battery management system illustrated in FIG. 1. FIG. 6 is a sequence diagram illustrating the example operation shown in FIG. 5. FIG. 7A is an explanatory diagram illustrating an example of management data in the example operation shown in FIG. 5. FIG. 7B is another explanatory diagram illustrating an example of management data in the example operation shown in FIG. 5. FIG. 7C is another explanatory diagram illustrating an example of management data in the example operation shown in FIG. 5. FIG. 8 is an explanatory diagram illustrating an example operation of the battery management system illustrated in FIG. 1. FIG. 9A is a sequence diagram illustrating the example operation shown in FIG. 8. FIG. 9B is another sequence diagram illustrating the example operation shown in FIG. 8. FIG. 9C is another sequence diagram illustrating the example operation shown in FIG. 8. FIG. 10A is an explanatory diagram illustrating an example of management data in the example operation shown in FIG. 8. Fig. 10B is another explanatory diagram showing an example of management data in the operation example shown in Fig. 8. Fig. 10C is another explanatory diagram showing an example of management data in the operation example shown in Fig. 8. Fig. 10D is another explanatory diagram showing an example of management data in the operation example shown in Fig. 8. Fig. 10E is another explanatory diagram showing an example of management data in the operation example shown in Fig. 8. Fig. 11 is a sequence diagram showing an operation example of a battery management system according to a modified example.

[0007] In order to allow many vehicles to exchange batteries at a battery station, a large number of batteries are generally reserved. In this case, the battery may remain in the battery station for a long time. Therefore, it is desirable to shorten the time that the battery remains in the battery station.

[0008] It is desirable to reduce the residence time of the batteries in the battery station.

[0009] Some exemplary embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. Note that the following description illustrates one specific example of the present disclosure and should not be construed as limiting the present disclosure. For example, each element, including numerical values, shapes, materials, parts, the position of each part, and the connection method of each part, is merely an example and should not be construed as limiting the present disclosure. Furthermore, in the following exemplary embodiments, components not described in independent claims based on the highest concept of the present disclosure are optional and may be provided as needed. The drawings are schematic and are not intended to be drawn to scale. Throughout this specification and the drawings, components having substantially the same function and configuration are designated by the same reference numerals, and redundant description will be omitted. Furthermore, components not directly related to one embodiment of the present disclosure are not shown in the drawings.

[0010] 1 shows an example of the configuration of a battery management system 1 including a battery management device according to an embodiment. The battery management system 1 includes a plurality of vehicles 10, a plurality of battery stations 20, and a battery management device 30. In this example, the battery stations 20 and the battery management device 30 are connected to the Internet and are capable of communicating with each other. Each of the plurality of vehicles 10 is connected to the Internet using wireless communication, thereby enabling communication with the battery management device 30.

[0011] Each of the multiple vehicles 10 is an electric vehicle that runs on power supplied from a battery 11 (described later). The vehicle 10 is configured so that the battery 11 can be attached or detached from the vehicle 10 at a battery station 20. The battery management unit 30 manages data about the battery 11. For example, when the remaining battery charge of the battery 11 of the vehicle 10 becomes low, the vehicle 10 can communicate with the battery management unit 30 to check at which battery station 20 the battery 11 can be replaced with another battery 11 that can be used by the vehicle 10, and can make a reservation for the replacement of the battery 11. The battery management unit 30 manages data about the batteries 11 that are already reserved in the battery stations 20 and data about the batteries 11 that are scheduled to be reserved in the battery stations 20 in the future. As a result, in the battery management system 1, for example, when a vehicle 10 (vehicle 10B described later) reserves the replacement of its battery 11, another vehicle 10 (vehicle 10C described later) can reserve the use of the battery 11 before replacement of vehicle 10B.

[0012] The vehicle 10 has a battery 11 and an on-board device 12. The battery 11 is configured to be detachable from the vehicle 10 and to supply stored power to the vehicle 10. The vehicle 10 runs by operating a motor based on the power supplied from the battery. The on-board device 12 is an electronic device mounted on the vehicle 10.

[0013] 2 shows an example of the configuration of the in-vehicle device 12. The in-vehicle device 12 includes a navigation unit 13, a communication unit 16, a user interface 17, and a control unit .

[0014] The navigation unit 13 is configured to determine a route (planned driving route) to a destination to which the vehicle 10 should travel and to guide the vehicle 10 along the determined route by providing information to the driver. The navigation unit 13 includes a GNSS (Global Navigation Satellite System) receiving unit 14 and a navigation processing unit 15. The GNSS receiving unit 14 is configured to acquire the terrestrial position of the vehicle 10 using a GNSS such as a GPS (Global Positioning System). The navigation processing unit 15 determines a planned driving route for the vehicle 10 using a map information database including information about road maps. The navigation processing unit 15 may, for example, include a memory unit that stores a map information database, and may determine the planned driving route using the map information database stored in the memory unit. Alternatively, for example, the communication unit 16 may determine the planned driving route by communicating with a network server in which the map information database is stored. The navigation unit 13 determines a planned driving route to the destination based on information about the destination input by the driver by operating the user interface 17, and provides information about the determined route to the driver using this user interface 17.

[0015] The communication unit 16 is configured to communicate with a base station by performing mobile communication such as 4G (4th Generation) or 5G (5th Generation). The communication unit 16 is capable of communicating with a battery management device 30 connected to the Internet via the base station.

[0016] The user interface 17 has, for example, a display panel, a touch panel, various buttons, and the like, and is configured to accept operations by a user such as a driver and to provide information to the user.

[0017] The control unit 18 is configured using, for example, one or more processors, one or more memories, etc., and is configured to control the operations of the navigation unit 13 , the communication unit 16 , and the user interface 17 .

[0018] Each of the plurality of battery stations 20 is a facility where the battery 11 of the vehicle 10 can be replaced. A processing device 21 is provided in the battery station 20. The processing device 21 is connected to the Internet, for example, and is configured to supply data related to the replacement to the battery management device 30 via the Internet when the battery 11 of the vehicle 10 is replaced at the battery station 20.

[0019] The battery management device 30 is configured to manage data about the battery 11. Specifically, the battery management device 30 manages data about the battery 11 that has already been secured in the battery station 20 and data about the battery 11 that is scheduled to be secured in the battery station 20 in the future.

[0020] 3 shows an example of the configuration of the battery management unit 30. The battery management unit 30 includes a communication unit 31, a storage unit 32, and a processing unit 33.

[0021] The communication unit 31 is connected to, for example, the Internet, and is configured to communicate with the processing devices 21 of the multiple vehicles 10 and the multiple battery stations 20 .

[0022] The storage unit 32 is configured using, for example, a hard disk drive (HDD) or a solid state drive (SSD), and is configured to store management data DT for the battery 11 .

[0023] FIG. 4 shows an example of the management data DT. The management data DT includes data on a battery identifier, battery information, SOC (State of Charge), station identifier, inventory flag, the scheduled date and time for depositing the battery 11, vehicle information, and the scheduled date and time for dispensing the battery 11. The battery identifier is an identifier for the battery 11. The battery information includes information on the characteristics and specifications of the battery 11, such as the maximum charge amount of the battery 11. The SOC is the charging rate of the battery 11. If the battery 11 is already secured at the battery station 20, the SOC is the charging rate of the battery 11. If the battery 11 is scheduled to be secured at the battery station 20 in the future, the SOC is an estimated SOC value at the scheduled date and time for depositing the battery 11 at the battery station 20. The station identifier is an identifier for the battery station 20. The inventory flag is a flag indicating whether the battery 11 is already secured at the battery station 20. In this example, if the inventory flag is "1", it indicates that the battery 11 has already been secured at the battery station 20, and if the inventory flag is "0", it indicates that the battery 11 is scheduled to be secured at the battery station 20 in the future. The scheduled date and time for depositing the battery 11 is the scheduled date and time for depositing the battery 11 at the battery station 20 in the future. The vehicle information for depositing the battery 11 is information about the vehicle 10 for depositing the battery 11, and includes, for example, an identifier of the vehicle 10, address information of the vehicle 10 for communication, and information about the characteristics and specifications of the vehicle 10. The vehicle information includes information about the electricity consumption of the vehicle 10. The electricity consumption of the vehicle 10 is, for example, the distance [km] that can be traveled with 1 kWh of power. The scheduled date and time for discharging the battery 11 is the scheduled date and time for discharging the battery 11 from the battery station 20 in the future. The vehicle information when issuing a battery 11 is information about the vehicle 10 from which the battery 11 is issued, and includes, for example, an identifier of the vehicle 10, address information of the vehicle 10 when communicating, and information about the characteristics and specifications of the vehicle 10.

[0024] In the management data DT shown in Fig. 4, for example, the record on the first line shows data about the battery 11 whose battery identifier is "IDB1." The station identifier is "IDS1," and the inventory flag is "1." Therefore, this battery 11 has already been secured in the battery station 20 whose station identifier is "IDS1." The SOC of this battery 11 is 90%.

[0025] For example, the record on the second line shows data about a battery 11 whose battery identifier is "IDB2." The station identifier is "IDS2" and the inventory flag is "1," so this battery 11 has already been secured at a battery station 20 whose station identifier is "IDS2." The SOC of this battery 11 is 90%. In this example, the scheduled delivery date and time is "YYYYMMDD 9:00," and the vehicle information is "INFC1." Here, "YYYYMMDD" indicates the year, month, and day. Therefore, this battery 11 is scheduled to be installed in a vehicle 10 whose vehicle information is "INFC1" on this scheduled date and time, and to be delivered from a battery station 20 whose station identifier is "IDS2."

[0026] For example, the record on the third line shows data about a battery 11 whose battery identifier is "IDB3." Because the inventory flag is "0," this battery 11 has not yet been secured at a battery station 20. In this example, the scheduled deposit date and time is "YYYYMMDD 13:00," the vehicle information is "INFC2," and the station identifier is "IDS3." Therefore, this battery 11 is scheduled to be removed from the vehicle 10 whose vehicle information is "INFC2" on this scheduled date and time, and deposited at a battery station 20 whose station identifier is "IDS3." The estimated SOC of this battery 11 when it is deposited is 40%.

[0027] For example, the record on the fourth line shows data about a battery 11 whose battery identifier is "IDB4." Because the inventory flag is "0," this battery 11 has not yet been secured at a battery station 20. In this example, the scheduled deposit date and time is "YYYYMMDD 11:00," the vehicle information is "INFC3," and the station identifier is "IDS4." Therefore, this battery 11 is scheduled to be removed from a vehicle 10 whose vehicle information is "INFC3" on this scheduled date and time, and deposited at a battery station 20 whose station identifier is "IDS4." The estimated SOC value at the time this battery 11 is deposited is 60%. Also, in this example, the scheduled withdrawal date and time is "YYYYMMDD 16:00," and the vehicle information for withdrawal is "INFC4." Therefore, this battery 11 is scheduled to be attached to a vehicle 10 whose vehicle information is "INFC4" and to be dispensed from a battery station 20 whose station identifier is "IDS4" on this scheduled date and time.

[0028] The processing unit 33 is configured to perform processing by executing a program, and includes an exchange determination unit 34, a battery inquiry unit 35, a reservation processing unit 36, a deposit processing unit 37, and a withdrawal processing unit 38.

[0029] The replacement determination unit 34 is configured to determine whether the battery 11 of the vehicle 10 should be replaced based on the data supplied from the vehicle 10 .

[0030] When the vehicle 10 needs to replace its battery 11, the battery inquiry unit 35 is configured to use the management data DT to check which batteries 11 are already reserved in the battery station 20 and which batteries 11 will be reserved in the future and which can be used by the vehicle 10.

[0031] The reservation processing unit 36 ​​is configured to accept a reservation for battery exchange and update the management data DT.

[0032] The deposit processing unit 37 is configured to update the management data DT when the battery 11 is removed from the vehicle 10 at the battery station 20 and deposited at the battery station 20 .

[0033] The payout processing unit 38 is configured to update the management data DT when the battery 11 is attached to the vehicle 10 at the battery station 20 and the battery 11 is paid out from the battery station 20 .

[0034] Here, the processing unit 33 corresponds to a specific example of a "processing circuit" in an embodiment of the present disclosure. The communication unit 31 corresponds to a specific example of a "communication circuit" in an embodiment of the present disclosure. The vehicle 10 corresponds to a specific example of a "first vehicle" and a "second vehicle" in an embodiment of the present disclosure. The battery 11 corresponds to a specific example of a "first battery" and a "second battery" in an embodiment of the present disclosure. The battery station 20 corresponds to a specific example of a "first battery station" in an embodiment of the present disclosure.

[0035] [Operation and Function] Next, the operation and function of the battery management system 1 of the present embodiment will be described.

[0036] (Overall Operation Overview) First, the operation of the battery management system 1 will be described with reference to Figures 1 and 3. The battery management unit 30 manages data on the batteries 11 already secured in the battery station 20 and data on the batteries 11 to be secured in the battery station 20 in the future. For example, when the remaining battery charge of the battery 11 of the vehicle 10 becomes low, the vehicle 10 communicates with the battery management unit 30. The replacement determination unit 34 of the battery management unit 30 determines whether the battery 11 of the vehicle 10 should be replaced based on the data supplied from the vehicle 10. If the battery 11 of the vehicle 10 should be replaced, the battery inquiry unit 35 of the battery management unit 30 uses the management data DT to check which of the batteries 11 already secured in the battery station 20 and which batteries 11 will be secured in the future are usable by the vehicle 10. Then, if the battery 11 of the vehicle 10 is to be replaced, the reservation processing unit 36 ​​of the battery management unit 30 accepts a reservation for battery replacement and updates the management data DT. Thereafter, when the vehicle 10 arrives at the battery station 20, the battery station 20 removes the battery 11 from the vehicle 10, and the deposit processing unit 37 of the battery management unit 30 updates the management data DT based on the data from the processing unit 21 of the battery station 20. Thereafter, the battery station 20 attaches another battery 11 to the vehicle 10, and the payout processing unit 38 of the battery management unit 30 updates the management data DT based on the data from the processing unit 21 of the battery station 20.

[0037] (Detailed Operation) An example of the operation of the battery management system 1 will be described in detail below with some examples.

[0038] (Operation Example E1) Fig. 5 shows an operation example E1 that is an operation example of the battery management system 1. In Fig. 5, the battery 11 is shown using a battery symbol that indicates the remaining battery capacity.

[0039] In this example, a vehicle 10 (hereinafter referred to as vehicle 10A) is traveling along a planned travel route toward a destination. The battery identifier of the battery 11 of vehicle 10A is "IDB13," the remaining battery charge is 30%, and the remaining travel distance is 100 km. Vehicle 10A plans to travel a distance of 200 km to the destination. Therefore, vehicle 10A cannot reach the destination using the current battery 11.

[0040] In this example, a battery station 20 with a station identifier "IDS11" is located on the planned driving route of vehicle 10A. This battery station 20 has a battery 11 with a battery identifier "IDB11" secured therein. The remaining battery charge of this battery 11 is 90%, and the driving range is 300 km. By exchanging the battery for this battery 11 at this battery station 20, vehicle 10A can reach the destination.

[0041] The operation of the battery management system 1 in such an example will be described below.

[0042] 6 shows an example of an operation of the battery management system 1 in the operation example E1. FIGS. 7A to 7C show an example of the management data DT in the operation example E1.

[0043] First, based on instructions from the control unit 18, the communication unit 16 of the vehicle 10A transmits to the battery management unit 30 the planned driving route of the vehicle 10A, the current driving position of the vehicle 10A, vehicle information of the vehicle 10A, a battery identifier of the battery 11 attached to the vehicle 10A, battery information of the battery 11, and data on the SOC of the battery 11 (step S101). The vehicle 10A may transmit such data based on instructions from the driver, for example, or may transmit such data when the remaining battery charge of the battery 11 of the vehicle 10A falls below a predetermined level. The communication unit 31 of the battery management unit 30 receives this data.

[0044] Next, the replacement determination unit 34 of the battery management unit 30 determines whether or not battery replacement is necessary based on the data received by the communication unit 31 (step S102). Specifically, the replacement determination unit 34 calculates the planned future travel distance of the vehicle 10A based on data on the planned travel route of the vehicle 10A and the travel position of the vehicle 10A. The replacement determination unit 34 also calculates the remaining travel distance of the vehicle 10A based on data on the maximum charge amount of the battery 11, the SOC of the battery 11 of the vehicle 10A, and the electricity consumption of the vehicle 10A, which are included in the battery information. The replacement determination unit 34 then compares the planned travel distance with the remaining travel distance to determine whether the battery of the vehicle 10A should be replaced.

[0045] In this operation example E1, as shown in FIG. 5, the driving range of the vehicle 10A (100 km) is shorter than the planned driving range (200 km), so the replacement determination unit 34 determines that the vehicle 10A should perform a battery replacement.

[0046] Next, the communication unit 31 of the battery management unit 30 transmits a notification to the vehicle 10A that the battery needs to be replaced based on the instruction from the processing unit 33 (step S103). The communication unit 16 of the vehicle 10A receives this notification.

[0047] Next, the communication unit 16 of the vehicle 10A transmits a battery inquiry request to the battery management unit 30 based on an instruction from the control unit 18 (step S104). That is, the control unit 18 of the vehicle 10A requests a battery inquiry to check whether there are any batteries 11 that the vehicle 10A can use at the multiple battery stations 20 along the planned travel route. The communication unit 31 of the battery management unit 30 receives this battery inquiry request.

[0048] Next, the battery inquiry unit 35 of the battery management unit 30 performs a battery inquiry process (step S105). Specifically, the battery inquiry unit 35 uses the management data DT to check for batteries 11 available for use by the vehicle 10A at multiple battery stations 20 along the planned driving route of the vehicle 10A. For example, if the available driving distance of the battery 11 is longer than the planned driving distance of the vehicle 10A, the battery inquiry unit 35 can determine that the battery 11 is available for use by the vehicle 10A. The available battery 11 may be a battery 11 already reserved in the battery station 20, or a battery 11 that will be reserved in the battery station 20 after being used by another vehicle 10.

[0049] Specifically, in this operation example E1, as shown in Fig. 7A, two batteries 11 in two battery stations 20 are available for use by the vehicle 10A. The battery 11 with the battery identifier "IDB11" has already been secured in the battery station 20 with the station identifier "IDS11" and has an SOC of 90%. The battery 11 with the battery identifier "IDB12" has already been secured in the battery station 20 with the station identifier "IDS12" and has an SOC of 70%. These two battery stations 20 are located on the planned driving route of the vehicle 10A.

[0050] Next, the communication unit 31 of the battery management unit 30 transmits the results of the battery inquiry process based on the instruction from the processing unit 33 (step S106). In this example, data on the two battery stations 20 and data on the two batteries 11 shown in Fig. 7A are transmitted. The communication unit 16 of the vehicle 10A receives the results of this battery inquiry process.

[0051] Next, the user interface 17 of the vehicle 10A accepts a selection operation for a battery replacement location based on an instruction from the control unit 18 (step S107). Specifically, the user interface 17 displays data about the battery station 20 and data about the available battery 11 included in the result of the battery inquiry process received by the communication unit 16. For example, the driver determines at which battery station 20 the battery 11 should be replaced based on the display content of the user interface 17, and performs an operation to select the battery station 20 at which the battery 11 should be replaced. The user interface 17 accepts this selection operation by the driver. This selection operation selects the battery station 20 where the battery replacement will be performed and the battery 11 to be attached to the vehicle 10A.

[0052] Specifically, in this operation example E1, the driver performs a selection operation to replace the battery 11 in the battery station 20 having the station identifier "IDS11" shown in Fig. 7A. As a result, the battery 11 reserved in this battery station 20 and having the battery identifier "IDB11" is selected as the battery 11 to be used.

[0053] Next, based on an instruction from the control unit 18, the communication unit 16 of the vehicle 10A transmits to the battery management unit 30 data on the battery identifier of the selected battery 11, the scheduled date and time when the vehicle 10A will arrive at the selected battery station 20, and the estimated SOC of the battery 11 currently being used by the vehicle 10A (step S108). This estimated SOC is the estimated SOC when the vehicle 10A will arrive at the battery station 20, and is calculated using the current traveling position of the vehicle 10A, the position of the battery station 20, the current SOC, and the electricity consumption of the vehicle 10A. The communication unit 31 of the battery management unit 30 receives this data.

[0054] Next, the reservation processing unit 36 ​​of the battery management unit 30 performs a reservation process for the battery exchange (step S109). Specifically, the reservation processing unit 36 ​​updates the management data DT based on the data received by the communication unit 31 in steps S101 and S108. For example, the reservation processing unit 36 ​​registers the scheduled date and time for discharging the battery 11 and vehicle information in the record of the battery 11 to be installed in the vehicle 10A in the management data DT. The reservation processing unit 36 ​​also newly registers a record of the battery 11 used by the vehicle 10A in the management data DT. In this record, the scheduled date and time for depositing the battery 11 and vehicle information are registered.

[0055] Specifically, in this operation example E1, as shown in Fig. 7B, the reservation processing unit 36 ​​registers data on the scheduled date and time for dispensing the battery 11 and vehicle information in the record of the battery 11 with the battery identifier "IDB11" that is scheduled to be installed in the vehicle 10A. In this example, the scheduled date and time for dispensing is "YYYYMMDD 16:00" and the vehicle information is "INFC13." This vehicle information is the vehicle information for the vehicle 10A.

[0056] The reservation processing unit 36 ​​also newly registers in the management data DT a record of the battery 11 used by the vehicle 10A, whose battery identifier is "IDB13." The battery information for this battery 11 is "INFB13." The vehicle 10A will have its battery replaced at a battery station 20, whose station identifier is "IDS11," where the battery 11 to be installed in the vehicle 10A is reserved. In this example, the scheduled date and time of deposit is "YYYYMMDD 16:00," and the vehicle information is "INFC13."

[0057] In this way, the battery exchange of the vehicle 10A is reserved in the battery management system 1. Thereafter, the vehicle 10A continues traveling along the planned traveling route and arrives at the battery station 20 with the station identifier "IDS11" where the battery exchange will be performed.

[0058] At the battery station 20, for example, an employee operates the vehicle 10A and the processing device 21 of the battery station 20. Based on the employee's operation, the processing device 21 of the vehicle 10A and the battery station 20 performs a battery removal process to remove the battery 11 from the vehicle 10A (step S111). In this process, the processing device 21 obtains data on the actual SOC of the battery 11.

[0059] Next, the processing device 21 of the battery station 20 transmits the battery identifier of the battery 11 removed in step S111 and data on the SOC of this battery 11 to the battery management unit 30 (step S112). The communication unit 31 of the battery management unit 30 receives this data.

[0060] Next, the deposit processing unit 37 of the battery management unit 30 performs deposit processing for the removed battery 11 (step S113). Specifically, the deposit processing unit 37 updates the management data DT based on the data received by the communication unit 31 in step S112. For example, the deposit processing unit 37 deletes the scheduled date and time for depositing the battery 11 and the vehicle information from the record of the removed battery 11 in the management data DT, and sets the inventory flag to "1." In other words, because this battery 11 has already been secured at this battery station 20, the deposit processing unit 37 deletes the scheduled date and time and the vehicle information and sets the inventory flag to "1." The deposit processing unit 37 also registers data on the actual SOC of the removed battery 11 in this record.

[0061] 7C, in this operation example E1, the deposit processing unit 37 deletes the scheduled date and time for depositing the battery 11 and the vehicle information in the record of the battery 11 with the battery identifier "IDB13" that was removed from the vehicle 10A, and sets the inventory flag to "1." Then, the deposit processing unit 37 registers data on the actual SOC of the removed battery 11 in this record.

[0062] Furthermore, the processing device 21 of the vehicle 10A and the battery station 20 performs a battery installation process to install a battery in the vehicle 10A based on the operation of the employee (step S114).

[0063] Next, the processing device 21 of the battery station 20 transmits data on the battery identifier of the battery 11 attached in step S114 to the battery management unit 30 (step S115). The communication unit 31 of the battery management unit 30 receives this data.

[0064] Next, the payout processing unit 38 of the battery management unit 30 performs a payout process for the installed battery 11 (step S116). Specifically, the payout processing unit 38 updates the management data DT based on the data received by the communication unit 31 in step S115. For example, the payout processing unit 37 deletes the record of the installed battery 11 from the management data DT. That is, the battery 11 installed in vehicle 10A will be used by this vehicle 10A for a while, and will not be used by other vehicles 10. Therefore, the payout processing unit 38 deletes the record of the battery 11 installed in vehicle 10A to remove this battery 11 from the management targets.

[0065] Specifically, in this operation example E1, as shown in FIG. 7C, the payout processing unit 38 deletes the record (FIG. 7B) of the battery 11 attached to the vehicle 10A and having the battery identifier "IDB11."

[0066] This completes the operation.

[0067] (Operation Example E2) FIG. 8 shows operation example E2, which is another operation example of the battery management system 1. In this example, two vehicles 10 (hereinafter, vehicles 10B and 10C) are traveling along a planned travel route toward a destination. The battery identifier of the battery 11 of vehicle 10B is "IDB22," the remaining battery charge is 30%, and the remaining driving distance is 100 km. Vehicle 10B plans to travel a distance of 200 km to the destination. Therefore, vehicle 10B cannot reach the destination using the current battery 11. Vehicle 10C also has a battery identifier of "IDB23," the remaining battery charge is 5%, and the remaining driving distance is 20 km. Vehicle 10C plans to travel a distance of 70 km to the destination. Therefore, vehicle 10C cannot reach the destination using the current battery 11.

[0068] In this example, a battery station 20 with a station identifier "IDS21" is located on the planned driving route of vehicles 10B and 10C. This battery station 20 has a battery 11 with a battery identifier "IDB21". The remaining battery charge of this battery 11 is 90%, and the driving range is 300 km. Vehicle 10B can reach the destination by replacing it with this battery 11 at this battery station 20. As a result of this battery replacement, vehicle 10B removes the battery 11 with a battery identifier "IDB22". The remaining battery charge of this battery 11 is 30%, and the driving range is 100 km. Vehicle 10C can reach the destination by replacing it with the battery 11 removed from vehicle 10B at this battery station 20.

[0069] The operation of the battery management system 1 in such an example will be described below.

[0070] 9A to 9C show an example of an operation of the battery management system 1 in the operation example E2. FIGS. 10A to 10E show an example of the management data DT in the operation example E2.

[0071] First, in steps S201 to S209, the vehicle 10B makes a reservation for battery exchange, as in the case of the operation example E1.

[0072] First, based on instructions from the control unit 18, the communication unit 16 of the vehicle 10B transmits to the battery management unit 30 the planned driving route of the vehicle 10B, the current driving position of the vehicle 10B, vehicle information of the vehicle 10B, the battery identifier of the battery 11 attached to the vehicle 10B, battery information of the battery 11, and data regarding the SOC of the battery 11 (step S201).

[0073] Next, the replacement determination unit 34 of the battery management unit 30 determines whether or not battery replacement is necessary based on the data received by the communication unit 31 (step S202). In this operation example E2, as shown in Fig. 8, the remaining driving distance (100 km) of the vehicle 10B is shorter than the planned driving distance (200 km), so the replacement determination unit 34 determines that the battery of the vehicle 10B should be replaced.

[0074] Next, the communication unit 31 of the battery management unit 30 transmits a notification to the vehicle 10B that the battery needs to be replaced, based on the instruction from the processing unit 33 (step S203).

[0075] Next, the communication unit 16 of the vehicle 10B transmits a battery inquiry request to the battery management unit 30 based on an instruction from the control unit 18 (step S204).

[0076] Next, the battery inquiry unit 35 of the battery management unit 30 performs a battery inquiry process (step S205). In this operation example E2, as shown in Fig. 10A, the battery 11 having the battery identifier "IDB21" has already been secured in the battery station 20 having the station identifier "IDS21", and the SOC is 90%. This battery station 20 is provided on the planned driving route of the vehicle 10B.

[0077] Next, the communication unit 31 of the battery management unit 30 transmits the result of the battery inquiry process based on the instruction from the processing unit 33 (step S206).

[0078] Next, the user interface 17 of the vehicle 10B accepts a selection operation for a battery exchange location based on an instruction from the control unit 18 (step S207). In this operation example E2, the driver performs a selection operation to exchange the battery 11 at the battery station 20 with the station identifier "IDS21" shown in Fig. 10A. As a result, the battery 11 secured at this battery station 20 with the battery identifier "IDB21" is selected as the battery 11 to be used.

[0079] Next, based on instructions from the control unit 18, the communication unit 16 of the vehicle 10B transmits to the battery management unit 30 data regarding the battery identifier of the selected battery 11, the scheduled date and time of arrival of the vehicle 10B at the selected battery station 20, and the estimated SOC value of the battery 11 currently being used by the vehicle 10B (step S208).

[0080] Next, the reservation processing unit 36 ​​of the battery management unit 30 performs reservation processing for battery replacement (step S209).

[0081] 10B, in this operation example E2, the reservation processing unit 36 ​​registers data on the scheduled date and time for dispensing the battery 11 and vehicle information in the record of the battery 11 with the battery identifier "IDB21" that is to be installed in the vehicle 10B. In this example, the scheduled date and time for dispensing the battery 11 is "YYYYMMDD 16:00," and the vehicle information is "INFC22." This vehicle information is the vehicle information for the vehicle 10B.

[0082] The reservation processing unit 36 ​​also newly registers in the management data DT a record of the battery 11 used by vehicle 10B, whose battery identifier is "IDB22." The battery information for this battery 11 is "INFB22." Vehicle 10B will have its battery replaced at a battery station 20, whose station identifier is "IDS21," where the battery 11 to be installed in vehicle 10B is reserved. In this example, the scheduled date and time of deposit is "YYYYMMDD 16:00," and the vehicle information is "INFC22."

[0083] In this manner, the battery management system 1 reserves the battery replacement for the vehicle 10B.

[0084] Next, the vehicle 10C similarly makes a reservation for battery exchange in steps S211 to S219.

[0085] First, based on instructions from the control unit 18, the communication unit 16 of the vehicle 10C transmits to the battery management unit 30 the planned driving route of the vehicle 10C, the current driving position of the vehicle 10C, vehicle information of the vehicle 10C, the battery identifier of the battery 11 attached to the vehicle 10C, battery information of the battery 11, and data regarding the SOC of the battery 11 (step S211).

[0086] Next, the replacement determination unit 34 of the battery management unit 30 determines whether or not battery replacement is necessary based on the data received by the communication unit 31 (step S212). In this operation example E2, as shown in Fig. 8, the remaining driving distance (20 km) of the vehicle 10C is shorter than the planned driving distance (70 km), so the replacement determination unit 34 determines that the battery of the vehicle 10C should be replaced.

[0087] Next, the communication unit 31 of the battery management unit 30 transmits a notification to the vehicle 10C that the battery needs to be replaced, based on the instruction from the processing unit 33 (step S213).

[0088] Next, the communication unit 16 of the vehicle 10C transmits a battery inquiry request to the battery management unit 30 based on an instruction from the control unit 18 (step S214).

[0089] Next, the battery inquiry unit 35 of the battery management unit 30 performs a battery inquiry process (step S215). In this operation example E2, as shown in FIG. 10B , the battery 11 with the battery identifier "IDB22" is available for use. That is, the battery 11 with the battery identifier "IDB22" is scheduled to be secured at 4:00 p.m. on this day at the battery station 20 with the station identifier "IDS21," and has an SOC of 30%. Although the SOC of the battery 11 is not high, the mileage of the battery 11 (100 km) is sufficiently longer than the planned mileage of the vehicle 10C (20 km), so the vehicle 10C can use the battery 11. The battery 11 with the battery identifier "IDB21" is scheduled for withdrawal on this day and is reserved, so the vehicle 10C cannot use the battery 11.

[0090] Next, the communication unit 31 of the battery management unit 30 transmits the result of the battery inquiry process based on the instruction from the processing unit 33 (step S216).

[0091] Next, the user interface 17 of the vehicle 10C accepts a selection operation for a battery exchange location based on an instruction from the control unit 18 (step S217). In this operation example E2, the driver performs a selection operation to exchange the battery 11 at the battery station 20 with the station identifier "IDS21" shown in Fig. 10B. As a result, the battery 11 with the battery identifier "IDB22" that is scheduled to be secured at this battery station 20 at 4:00 PM on that day is selected as the battery 11 to be used.

[0092] Next, based on instructions from the control unit 18, the communication unit 16 of the vehicle 10C transmits to the battery management unit 30 data regarding the battery identifier of the selected battery 11, the scheduled date and time of arrival of the vehicle 10C at the selected battery station 20, and the estimated SOC value of the battery 11 currently being used by the vehicle 10C (step S218).

[0093] Next, the reservation processing unit 36 ​​of the battery management unit 30 performs reservation processing for battery replacement (step S219).

[0094] 10C, the reservation processing unit 36 ​​registers data on the scheduled date and time for dispensing the battery 11 and vehicle information in the record of the battery 11, which is scheduled to be installed in the vehicle 10C and has a battery identifier of "IDB22." In this example, the scheduled date and time for dispensing the battery 11 is "YYYYMMDD 18:00," and the vehicle information is "INFC23." This vehicle information is the vehicle information for the vehicle 10C.

[0095] The reservation processing unit 36 ​​also newly registers in the management data DT a record of the battery 11 used by the vehicle 10C, whose battery identifier is "IDB23." The battery information for this battery 11 is "INFB23." The vehicle 10C will exchange its battery at a battery station 20, whose station identifier is "IDS21," where the battery 11 to be installed in the vehicle 10C is reserved. In this example, the scheduled date and time of deposit is "YYYYMMDD 18:00," and the vehicle information is "INFC23."

[0096] In this manner, the battery management system 1 reserves the battery replacement for the vehicle 10C.

[0097] Thereafter, vehicle 10B arrives at battery station 20, whose station identifier is "IDS21," as scheduled, at about 4:00 PM. Then, vehicle 10B performs battery exchange in steps S221 to S228.

[0098] At the battery station 20, for example, an employee operates the vehicle 10B and the processing device 21 of the battery station 20. Based on the employee's operation, the processing device 21 of the vehicle 10B and the battery station 20 performs a battery removal process to remove the battery 11 from the vehicle 10B (step S221). In this process, the processing device 21 obtains data on the actual SOC of the battery 11.

[0099] Next, the processing device 21 of the battery station 20 transmits the battery identifier of the battery 11 removed in step S221 and data on the SOC of this battery 11 to the battery management device 30 (step S222).

[0100] Next, the deposit processing unit 37 of the battery management unit 30 performs deposit processing for the removed battery 11 (step S223). In this operation example E2, as shown in FIG. 10D , the deposit processing unit 37 deletes the scheduled date and time for depositing the battery 11 and vehicle information from the record of the battery 11 with the battery identifier "IDB22" that was removed from the vehicle 10B, and sets the inventory flag to "1." Then, the deposit processing unit 37 registers data on the actual SOC of the removed battery 11 in this record.

[0101] Next, the communication unit 31 of the battery management unit 30 transmits a notification to the vehicle 10C that the battery 11 has been secured based on an instruction from the processing unit 33 (step S224). The communication unit 16 of the vehicle 10C receives this notification.

[0102] Next, based on an instruction from the control unit 18, the user interface 17 of the vehicle 10C displays a message indicating that the battery 11 to be installed has been secured at the battery station 20 (step S225). This allows the driver of the vehicle 10C to confirm that the battery 11 can be replaced at the battery station 20.

[0103] Furthermore, the processing device 21 of the vehicle 10B and the battery station 20 performs a battery installation process to install a battery in the vehicle 10B based on the operation of the employee (step S226).

[0104] Next, the processing device 21 of the battery station 20 transmits data on the battery identifier of the battery 11 attached in step S226 to the battery management device 30 (step S227).

[0105] Next, the payout processing unit 38 of the battery management unit 30 performs a payout process for the attached battery 11 (step S228). In this operation example E2, as shown in Fig. 10D, the payout processing unit 38 deletes the record (Fig. 10C) of the battery 11 attached to the vehicle 10B, which has the battery identifier "IDB21".

[0106] Thereafter, vehicle 10C arrives at battery station 20, whose station identifier is "IDS21," as scheduled, at about 6:00 PM. Then, vehicle 10C performs battery exchange in steps S231 to S236.

[0107] At the battery station 20, for example, an employee operates the vehicle 10C and the processing device 21 of the battery station 20. Based on the employee's operation, the processing device 21 of the vehicle 10C and the battery station 20 performs a battery removal process to remove the battery 11 from the vehicle 10C (step S231). In this process, the processing device 21 obtains data on the actual SOC of the battery 11.

[0108] Next, the processing device 21 of the battery station 20 transmits the battery identifier of the battery 11 removed in step S231 and data on the SOC of this battery 11 to the battery management device 30 (step S232).

[0109] Next, the deposit processing unit 37 of the battery management unit 30 performs deposit processing for the removed battery 11 (step S233). In this operation example E2, as shown in FIG. 10E, the deposit processing unit 37 deletes the scheduled date and time for depositing the battery 11 and vehicle information from the record of the battery 11 with the battery identifier "IDB23" that was removed from the vehicle 10C, and sets the inventory flag to "1." Then, the deposit processing unit 37 registers data on the actual SOC of the removed battery 11 in this record.

[0110] Furthermore, the processing device 21 of the vehicle 10C and the battery station 20 performs a battery installation process to install a battery in the vehicle 10C based on the operation of the employee (step S234).

[0111] Next, the processing device 21 of the battery station 20 transmits data on the battery identifier of the battery 11 attached in step S234 to the battery management device 30 (step S235).

[0112] Next, the payout processing unit 38 of the battery management unit 30 performs a payout process for the attached battery 11 (step S236). In this operation example E2, as shown in Fig. 10E, the payout processing unit 38 deletes the record (Fig. 10D) of the battery 11 attached to the vehicle 10C and having the battery identifier "IDB22".

[0113] This completes the operation.

[0114] Here, vehicle 10B corresponds to a specific example of a "first vehicle" in an embodiment of the present disclosure. Vehicle 10C corresponds to a specific example of a "second vehicle" in an embodiment of the present disclosure. Battery 11 with a battery identifier "IDB22" corresponds to a specific example of a "first battery" in an embodiment of the present disclosure. Battery 11 with a battery identifier "IDB23" corresponds to a specific example of a "second battery" in an embodiment of the present disclosure.

[0115] In this way, the battery management device 30 can manage data on the multiple batteries 11 used by the vehicles 10 whose batteries 11 can be replaced, and is provided with a processing circuit (processing unit 33) that can determine whether the second vehicle 10 can use the first battery 11 based on the remaining battery charge of the first battery 11 before replacement in the first vehicle 10 (e.g., vehicle 10B) that is scheduled to have its battery replaced at the first battery station 20, and a communication circuit (communication unit 31) that can, when the second vehicle 10 (e.g., vehicle 10C) can use the first battery, send a notification to the second vehicle 10 (e.g., vehicle 10C) that the second battery 11 of the second vehicle 10 can be replaced with the first battery 11 at the first battery station 20. As a result, for example, the battery station 20 does not need to secure a battery 11 that can be used by vehicle 10C in advance, and vehicle 10C can use the battery 11 that vehicle 10B was using until just before, for example, thereby shortening the residence time of the batteries 11 at the battery station 20.

[0116] That is, it is conceivable that a battery station reserves many batteries 11 in advance and prepares for reservations for battery exchange. In this case, the batteries 11 will remain at the battery station for a long time. For example, if many batteries 11 remain at the battery station for a long time, it will be time-consuming for battery station employees to manage many batteries 11. Furthermore, it will be necessary to store many batteries 11 at the battery station, which will result in a large facility.

[0117] On the other hand, with the battery management unit 30, for example, vehicle 10C can use the battery 11 that vehicle 10B was using immediately beforehand, thereby shortening the time that the batteries 11 stay in the battery station 20. This allows a reduction in the number of batteries 11 that need to be secured in advance in the battery station 20, thereby reducing the workload of battery station employees. Furthermore, since the number of batteries 11 stored in the battery station can be reduced, the equipment can be made smaller.

[0118] Furthermore, in the battery management system 1 equipped with the battery management device 30, the battery 11 is not necessarily fully charged when it is dispensed. This eliminates the need for the battery 11 to be fully charged each time, thereby shortening the time the battery 11 remains in the battery station 20. Furthermore, since the battery 11 is not necessarily fully charged, the number of times the battery 11 is charged can be reduced, thereby extending the life of the battery 11. Note that, since the battery 11 is not necessarily fully charged, the driver may feel some inconvenience. Therefore, for example, an incentive such as points may be provided to drivers who exchange their battery for such a battery 11. By accumulating these points, drivers can receive various services.

[0119] Furthermore, in the battery management device 30, the communication circuit (communication unit 31) is configured to transmit a notification to the second vehicle 10 (e.g., vehicle 10C) when the second vehicle 10 (e.g., vehicle 10C) is able to use the first battery, informing the second vehicle 10 (e.g., vehicle 10C) that the second battery 11 can be replaced with the first battery 11 at the first battery station 20. This allows the driver of vehicle 10C to know that battery replacement can be performed at the first battery station 20. This allows the driver of vehicle 10C to drive vehicle 10C with peace of mind.

[0120] In the battery management device 30, the processing circuit (processing unit 33) is configured to be able to determine whether the second vehicle 10 (e.g., vehicle 10C) can use the first battery 11 based on the remaining battery charge of the first battery 11 and the planned future travel distance of the second vehicle 10 (e.g., vehicle 10C) on the planned travel route. This allows the processing unit 33 to more accurately determine whether the vehicle 10C can use the battery 11 before replacement of vehicle 10B, even if the remaining battery charge of the battery 11 is low.

[0121] In the battery management unit 30, the processing circuit (processing unit 33) can determine whether the second vehicle (e.g., vehicle 10C) can reach the destination based on the remaining battery charge of the second battery 11 and the planned future travel distance of the planned travel route of the second vehicle. If the second vehicle (e.g., vehicle 10C) cannot reach the destination, the processing circuit (processing unit 33) can determine whether the second vehicle (e.g., vehicle 10C) can use the first battery 11. As a result, the battery management unit 30 can suggest battery replacement to the driver of vehicle 10C based on the remaining battery charge of the battery 11 of vehicle 10C when battery replacement is necessary. This allows the driver of vehicle 10C to drive vehicle 10C with peace of mind.

[0122] In the battery management unit 30, the multiple batteries 11 include batteries already secured in the first battery station 20 and batteries scheduled to be secured in the first battery station in the future. This allows the battery management unit 30 to suggest to the driver of the second vehicle (e.g., vehicle 10C) whether to replace the battery 11 with a fully charged battery 11 already secured in the first battery station 20, or to replace the battery 11 used by the first vehicle (e.g., vehicle 10B) before replacement. This allows the driver to select an appropriate battery 11 to replace depending on their plans after arriving at the destination.

[0123] [Effects] As described above, in this embodiment, it is possible to manage data about multiple batteries used by vehicles whose batteries can be replaced, and it is provided with a processing circuit that can determine whether a second vehicle can use the first battery based on the remaining battery charge of the first battery before replacement in a first vehicle that is scheduled to have its battery replaced at a first battery station, and a communication circuit that, if the second vehicle can use the first battery, can send a notification to the second vehicle 10 that the second battery of the second vehicle can be replaced with the first battery at the first battery station, thereby shortening the residence time of batteries at the battery station.

[0124] In this embodiment, the processing circuit is able to determine whether the second vehicle can use the first battery based on the remaining battery charge of the first battery and the planned future distance traveled on the second vehicle's planned driving route, thereby making it possible to determine with greater accuracy whether the vehicle can use its battery.

[0125] In this embodiment, the processing circuit can determine whether the second vehicle can reach the destination based on the remaining battery charge of the second battery 11 and the planned future distance traveled on the planned driving route of the second vehicle, and if the second vehicle cannot reach the destination, can determine whether the second vehicle can use the first battery.Therefore, if a battery replacement is necessary, a suggestion about battery replacement can be made to the driver.

[0126] In this embodiment, the multiple batteries include batteries that are already secured at the first battery station and batteries that are scheduled to be secured at the first battery station in the future, so that the driver of the second vehicle can be offered, for example, a choice between replacing the battery with a battery that is already secured at the first battery station and is fully charged, or replacing the battery with the battery that was used by the first vehicle before replacement.

[0127] 8, in the above embodiment, the battery 11 used by the vehicle 10B is directly transferred to the vehicle 10C at the battery station 20. However, this is not limited to this. Instead, for example, the battery 11 used by the vehicle 10B may be charged at the battery station 20, and the charged battery 11 may be transferred to the vehicle 10C.

[0128] [Variation 2] In the above embodiment, in operation example E2, vehicles 10B and 10C performed battery exchange at the battery station 20 selected by the driver of vehicle 10B, but this is not limited to this. For example, the battery station 20 where the battery exchange is performed may be changed. The battery station 20 is changed based on, for example, traffic conditions around the battery station 20 where the battery exchange was scheduled to be performed or a request from vehicle 10C.

[0129] 11 shows an example of the operation of the battery management system 1 according to this modification. This process is performed in the battery management system 1 after a reservation for battery exchange of the vehicles 10B and 10C is made.

[0130] First, the communication unit 31 of the battery management unit 30 transmits a transmission request for the planned driving route and driving position of the vehicle 10B to the vehicle 10B based on an instruction from the processing unit 33 (step S301). The communication unit 16 of the vehicle 10B receives this transmission request.

[0131] Next, the communication unit 16 of the vehicle 10B transmits data on the planned driving route and driving position of the vehicle 10B to the battery management unit 30 based on an instruction from the control unit 18 (step S302). The communication unit 31 of the battery management unit 30 receives this data.

[0132] Next, the communication unit 31 of the battery management unit 30 transmits a transmission request for the planned driving route and driving position of the vehicle 10C to the vehicle 10C based on the instruction from the processing unit 33 (step S303). The communication unit 16 of the vehicle 10C receives this transmission request.

[0133] Next, the communication unit 16 of the vehicle 10C transmits data on the planned driving route and driving position of the vehicle 10C to the battery management unit 30 based on an instruction from the control unit 18 (step S304). The communication unit 31 of the battery management unit 30 receives this data.

[0134] Next, the battery inquiry unit 35 of the battery management unit 30 performs a battery inquiry process using the management data DT (S305). Specifically, the battery inquiry unit 35 uses the management data DT to check for batteries 11 available for use by the vehicle 10B at multiple battery stations 20 along the planned driving routes of the vehicles 10B and 10C. The available batteries 11 may be batteries 11 already reserved in the battery stations 20, or batteries 11 that will be reserved in the battery stations 20 after being used by another vehicle 10.

[0135] Next, the communication unit 31 of the battery management unit 30 transmits a request to change the battery exchange location based on the instruction from the processing unit 33 (step S306). Specifically, the communication unit 31 transmits the data on the battery 11 that can be used by the vehicle 10B, which were inquired about in step S305, and the data on the battery station 20 that can exchange the battery 11, and also transmits the request to change the battery exchange location. The communication unit 16 of the vehicle 10B receives this data.

[0136] Next, the user interface 17 of the vehicle 10B accepts a decision operation to change the battery replacement location based on an instruction from the control unit 18 (step S307). Specifically, the user interface 17 displays the data about the battery station 20 and the data about the available battery 11 received by the communication unit 16. For example, the driver performs an operation to decide to change the battery replacement location based on the display content of the user interface 17. The user interface 17 accepts this decision operation by the driver.

[0137] Next, the communication unit 16 of the vehicle 10B transmits a change acceptance notification of the battery station 20 to the battery management unit 30 based on the instruction from the control unit 18 (step S308). The communication unit 31 of the battery management unit 30 receives this notification.

[0138] Next, the reservation processing unit 36 ​​of the battery management unit 30 registers the change of the battery replacement location in the management data DT (step S309). Specifically, the reservation processing unit 36 ​​updates the record of the battery 11 that is scheduled to be used by vehicle 10B and that was queried in step S305, the record of the battery 11 that has been removed from vehicle 10B and that is scheduled to be used by vehicle 10C, and the record of the battery 11 that will be removed from vehicle 10B.

[0139] Next, the communication unit 31 of the battery management unit 30 transmits a battery change location change notification to the vehicle 10C based on an instruction from the processing unit 33 (step S310). The communication unit 16 of the vehicle 10C receives this notification.

[0140] Then, the user interface 17 of the vehicle 10C displays the change of the battery replacement location based on an instruction from the control unit 18 (step S311).

[0141] This completes the operation.

[0142] In the battery management unit 30 according to this modification, the processing circuit (processing unit 33) can further check whether a second battery station is available where the first vehicle (e.g., vehicle 10B) can perform a battery exchange. If the second battery station is available, the communication circuit (communication unit 31) can request the first vehicle (e.g., vehicle 10B) to change the location of the battery exchange from the first battery station to the second battery station and receive a notification of acceptance from the first vehicle (e.g., vehicle 10B). When the communication circuit (communication unit 31) receives the notification of acceptance from the first vehicle (e.g., vehicle 10B), the processing circuit (processing unit 33) can transmit a notification to the second vehicle (e.g., vehicle 10C) that the second battery can be exchanged for the first battery at the second battery station. This allows the battery management unit 30 to change the battery exchange location, so that, for example, even if an unexpected problem occurs, the battery can be exchanged by changing the battery exchange location.

[0143] Although several embodiments of the present disclosure have been described above by way of example with reference to the accompanying drawings, the present disclosure is by no means limited to the above-described embodiments. Those skilled in the art will understand that various modifications and variations can be made without departing from the scope defined by the appended claims. The present disclosure is intended to encompass such modifications and variations to the extent that they fall within the scope of the appended claims and their equivalents.

[0144] For example, in the above embodiment, the management data DT shown in Figure 4 was used, but this is not limited to this, and some of the data contained in the management data DT may not be included, or other data may be included.

[0145] For example, the processing sequences shown in FIGS. 6 and 9A to 9C in the above embodiments are merely examples, and processing sequences different from these sequences may be used.

[0146] The effects described in this specification are merely examples, and the effects of the present disclosure are not limited to the effects described in this specification. Therefore, other effects may be obtained with respect to the present disclosure.

[0147] Furthermore, the present disclosure may take the following aspects.

[0148] (1) A battery management device comprising: a processing circuit capable of managing data on a plurality of batteries used by a vehicle having a replaceable battery, and capable of determining whether a second vehicle can use the first battery based on a remaining battery charge of a first battery in a first vehicle that is scheduled to have its battery replaced at a first battery station, and a communication circuit capable of, when the second vehicle can use the first battery, transmitting a notification to the second vehicle that the second battery of the second vehicle can be replaced with the first battery at the first battery station. (2) The battery management device described in (1), wherein the processing circuit is capable of determining whether the second vehicle can use the first battery based on the remaining battery charge of the first battery and a future planned travel distance on a planned travel route of the second vehicle. (3) The battery management device according to any one of (1) to (3), wherein the processing circuit is capable of determining whether the second vehicle can reach a destination point based on a remaining battery charge of the second battery and a planned distance to be traveled in the future on a planned travel route of the second vehicle, and when the second vehicle cannot reach the destination point, the processing circuit is capable of determining whether the second vehicle can use the first battery. (4) The battery management device according to any one of (1) to (3), wherein the plurality of batteries include batteries already secured in the first battery station and batteries to be secured in the first battery station in the future.(5) The battery management device according to any of (1) to (4), wherein the processing circuit is further capable of checking whether there is a second battery station where the first vehicle can perform battery replacement; the communication unit, if there is the second battery station, is capable of requesting the first vehicle to change the location of the battery replacement from the first battery station to the second battery station and is capable of receiving a notification of acceptance from the first vehicle; and when the communication circuit receives a notification of acceptance from the first vehicle, the processing circuit is capable of sending a notification to the second vehicle that the second battery can be replaced with the first battery at the second battery station.

[0149] The processing unit 33 shown in FIG. 3 can be implemented by circuitry including at least one semiconductor integrated circuit, such as at least one processor (e.g., a central processing unit (CPU)), at least one application-specific integrated circuit (ASIC), and / or at least one field-programmable gate array (FPGA). The at least one processor can be configured to perform all or a portion of the various functions of the processing unit 33 shown in FIG. 3 by reading instructions from at least one non-transitory, tangible computer-readable medium. Such media can take various forms, including, but not limited to, various magnetic media such as hard disks, various optical media such as CDs or DVDs, and various semiconductor memories (i.e., semiconductor circuits) such as volatile or non-volatile memories. Volatile memories can include DRAM and SRAM. Non-volatile memories can include ROM and NVRAM. An ASIC is an integrated circuit (IC) specialized to perform all or a portion of the various functions of the processing unit 33 shown in FIG. 3. An FPGA is an integrated circuit designed to be configurable after manufacture to perform all or a portion of the various functions of the processing unit 33 shown in FIG. 3.

Claims

1. A processing circuit capable of managing data on multiple batteries used by a vehicle with replaceable batteries, and capable of determining whether a second vehicle can use the first battery based on the remaining battery charge of the first battery before replacement in a first vehicle scheduled for battery replacement at a first battery station, A communication circuit capable of sending a notification to the second vehicle that the second battery of the second vehicle can be replaced with the first battery at the first battery station when the second vehicle is able to use the first battery, Equipped with, The processing circuit can further determine whether there is a second battery station where the first vehicle can have its battery replaced. The communication circuit can, when the second battery station is present, request the first vehicle to change the location where the battery is replaced from the first battery station to the second battery station, and can receive a notification of acceptance from the first vehicle. The communication circuit, upon receiving a notification of acceptance from the first vehicle, can send a notification to the second vehicle stating that the second battery can be replaced with the first battery at the second battery station. Battery management device.

2. The processing circuit can determine whether the second vehicle can use the first battery based on the remaining battery charge of the first battery and the planned remaining distance traveled on the second vehicle's planned route. The battery management device according to claim 1.

3. The processing circuit can determine whether the second vehicle can reach the target location based on the remaining battery charge of the second battery and the planned remaining distance traveled along the second vehicle's planned route. If the second vehicle cannot reach the target location, the circuit can determine whether the second vehicle can use the first battery. The battery management device according to claim 1.

4. The plurality of batteries include batteries already secured in the first battery station and batteries that are planned to be secured in the first battery station in the future. The battery management device according to claim 1.