Battery management device

Abstract

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

Description

Technical Field

[0001] The present disclosure relates to a battery management device for managing batteries in a vehicle capable of replacing batteries. Background Art

[0002] Among vehicles such as electric vehicles, there are vehicles capable of replacing batteries. The batteries of such vehicles are replaced at a battery station. In Patent Document 1, a system for guiding a user to a battery station that can replace a battery with less remaining battery capacity in a vehicle with a fully charged battery is disclosed.

[0003] Prior Art Documents

[0004] Patent Documents

[0005] Patent Document 1: International Publication No. 2019 / 163573 Summary of the Invention

[0006] The battery management device according to one embodiment of the present disclosure includes a processing circuit and a communication circuit. The processing circuit can manage data on a plurality of batteries used in a vehicle capable of replacing batteries, and can determine whether a second vehicle can use a first battery based on the remaining battery capacity of the first battery before replacement in a first vehicle that has reserved battery replacement at a first battery station. The communication circuit can, when the second vehicle can use the first battery, send a notification to the second vehicle indicating that the second battery of the second vehicle can be replaced with the first battery at the first battery station. Brief Description of the Drawings

[0007] Drawings are provided to further understand the present disclosure. The drawings are incorporated into and constitute a part of this specification. The drawings illustrate one embodiment and, together with the specification, are used to explain the principles of the present disclosure.

[0008] Figure 1 is a block diagram showing a structural example of a battery management system according to one embodiment of the present invention.

[0009] Figure 2 is a block diagram showing Figure 1 a structural example of the in-vehicle device shown.

[0010] Figure 3 is a block diagram showing Figure 1 a structural example of the battery management device shown.

[0011] Figure 4 is a block diagram showing Figure 3 a structural example of the management data shown.

[0012] Figure 5 is a block diagram showing Figure 1Explanatory diagram of an operation example of the battery management system shown.

[0013] Figure 6 Shows Figure 5 Sequence diagram of an operation example shown.

[0014] Figure 7A Shows Figure 5 Explanatory diagram of an example of management data in an operation example shown.

[0015] Figure 7B Shows Figure 5 Another explanatory diagram of an example of management data in an operation example shown.

[0016] Figure 7C Shows Figure 5 Another explanatory diagram of an example of management data in an operation example shown.

[0017] Figure 8 Shows Figure 1 Explanatory diagram of an operation example of the battery management system shown.

[0018] Figure 9A Shows Figure 8 Sequence diagram of an operation example shown.

[0019] Figure 9B Shows Figure 8 Another sequence diagram of an operation example shown.

[0020] Figure 9C Shows Figure 8 Another sequence diagram of an operation example shown.

[0021] Figure 10A Shows Figure 8 Explanatory diagram of an example of management data in an operation example shown.

[0022] Figure 10B Shows Figure 8 Another explanatory diagram of an example of management data in an operation example shown.

[0023] Figure 10C Shows Figure 8 Another explanatory diagram of an example of management data in an operation example shown.

[0024] Figure 10D Shows Figure 8 Another explanatory diagram of an example of management data in an operation example shown.

[0025] Figure 10E Shows Figure 8 Another explanatory diagram of an example of management data in an operation example shown.

[0026] Figure 11 It is a sequence diagram showing an operation example of a battery management system showing a modified example. Detailed implementation mode

[0027] At a battery station, in order to enable a large number of vehicles to replace batteries, a large number of batteries are usually stored. In this case, the residence time of the batteries may become long. Therefore, it is desirable to shorten the residence time of the batteries at the battery station.

[0028] It is desirable to shorten the residence time of the batteries at the battery station.

[0029] Hereinafter, several exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. It should be noted that the following description shows a 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, components, the positions of the respective components, and the connection methods of the respective components is only an example and should not be construed as limiting the present disclosure. In addition, in the following exemplary embodiments, the components not described in the independent claims of the present disclosure based on the most general concept are arbitrary and can be provided as needed. The drawings are schematic and are not intended to be drawn to the original size. Throughout this specification and the drawings, components having substantially the same function and substantially the same structure are denoted by the same reference numerals, and repeated descriptions are omitted. In addition, components not directly related to one embodiment of the present disclosure are not shown in the drawings.

[0030] <Embodiment>

[0031] [Structural example]

[0032] Figure 1 A structural example of a battery management system 1 including a battery management device according to one embodiment is shown. 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 station 20 and the battery management device 30 are connected to the Internet and can communicate with each other. The plurality of vehicles 10 are each connected to the Internet using wireless communication, and thus can communicate with the battery management device 30.

[0033] The plurality of vehicles 10 are electric vehicles that travel based on power supplied from a battery 11 (described later). The vehicle 10 is configured to be able to detach and attach the battery 11. The battery 11 is removed from the vehicle 10 or attached to the vehicle 10 at a battery station 20. The battery management device 30 manages data on the battery 11. For example, when the remaining battery power of the battery 11 of the vehicle 10 becomes low, the vehicle 10 communicates with the battery management device 30 to confirm at which battery station 20 the battery 11 can be replaced with another battery 11 that can be used by the vehicle 10, and to make a reservation for the replacement of the battery 11. The battery management device 30 manages data on the battery 11 stored in the battery station 20 and data on the battery 11 scheduled to be stored in the battery station 20 in the future. Thus, in the battery management system 1, for example, when a vehicle 10 (a vehicle 10B described later) makes a reservation for the replacement of the battery 11, another vehicle 10 (a vehicle 10C described later) can make a reservation for the use of the battery 11 of the vehicle 10B before the replacement.

[0034] The vehicle 10 includes a battery 11 and an onboard device 12. The battery 11 is detachable from the vehicle 10 and is configured 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 onboard device 12 is an electronic device mounted on the vehicle 10.

[0035] Figure 2 The following is a diagram showing a configuration example of the vehicle-mounted device 12. The vehicle-mounted device 12 includes a navigation unit 13, a communication unit 16, a user interface 17, and a control unit 18.

[0036] The navigation unit 13 is configured to guide the vehicle 10 along the determined route by determining a route (scheduled travel route) to a destination to which the vehicle 10 should travel and 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 obtain the position of the vehicle 10 on the ground using a GNSS such as a GPS (Global Positioning System). The navigation processing unit 15 uses a map information database including information about a road map to determine the scheduled travel route of the vehicle 10. The navigation processing unit 15 may, for example, include a storage unit that stores a map information database, and determine the scheduled travel route using the map information database stored in the storage unit, or the communication unit 16 may determine the scheduled travel route by communicating with a network server that stores a map information database. The navigation unit 13 determines the scheduled travel route to the destination based on information about the destination input by the driver operating a user interface 17, for example, and provides the driver with information about the determined route using the user interface 17.

[0037] 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) etc. The communication unit 16 can communicate with the battery management device 30 connected to the Internet via the base station.

[0038] The user interface 17 is configured to include, for example, a display panel, a touch panel, various buttons, etc., and accepts operations from a user such as a driver and provides information to the user.

[0039] 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 .

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

[0041] The battery management device 30 is configured to manage data on the batteries 11. Specifically, the battery management device 30 manages data on the batteries 11 already stored in the battery station 20 and data on the batteries 11 scheduled to be stored in the battery station 20 in the future.

[0042] Figure 3 Shows a structural example of the battery management device 30. The battery management device 30 includes a communication unit 31, a storage unit 32, and a processing unit 33.

[0043] The communication unit 31 is configured to connect to, for example, the Internet and communicate with the processing devices 21 of a plurality of vehicles 10 and a plurality of battery stations 20.

[0044] The storage unit 32 is configured using, for example, an HDD (Hard Disk Drive) or an SSD (Solid State Drive) and is configured to store management data DT regarding the battery 11.

[0045] Figure 4 Shows an example of the management data DT. The management data DT includes data regarding a battery identifier, battery information, SOC (State Of Charge), a station identifier, an inventory flag, a predetermined date and time when the battery 11 is deposited, vehicle information, a predetermined date and time when the battery 11 is taken, and vehicle information. The battery identifier is an identifier of the battery 11. The battery information includes information regarding characteristics and specifications of the battery 11, such as the maximum charge amount of the battery 11. The SOC is the charge rate of the battery 11. When the battery 11 is stored at the battery station 20, the SOC is the charge rate of the battery 11. When the battery 11 is scheduled to be stored at the battery station 20 in the future, the SOC is an estimated value of the SOC at the predetermined date and time when the battery 11 is deposited at the battery station 20. The station identifier is an identifier of the battery station 20. The inventory flag is a flag indicating whether the battery 11 is stored at the battery station 20. In this example, when the inventory flag is "1", it indicates that the battery 11 is stored at the battery station 20. When the inventory flag is "0", it indicates that the battery 11 is scheduled to be stored at the battery station 20 in the future. The predetermined date and time when the battery 11 is deposited is the predetermined date and time when the battery 11 is deposited at the battery station 20 in the future. The vehicle information when the battery 11 is deposited is information of the vehicle 10 that deposits the battery 11, and includes, for example, an identifier of the vehicle 10, address information of the vehicle 10 during communication, and information regarding characteristics and specifications of the vehicle 10. The vehicle information includes information regarding the power consumption of the vehicle 10. The power consumption of the vehicle 10 is, for example, the distance [km] that can be traveled with 1 kWh of electric power. The predetermined date and time when the battery 11 is taken is the predetermined date and time when the battery 11 is taken from the battery station 20 in the future. The vehicle information when the battery 11 is taken is information of the vehicle 10 that takes the battery 11, and includes, for example, an identifier of the vehicle 10, address information of the vehicle 10 during communication, and information regarding characteristics and specifications of the vehicle 10.

[0046] In thisFigure 4 In the management data DT shown, for example, the record in the first row shows data regarding the battery 11 with the battery identifier "IDB1". The station identifier is "IDS1" and the inventory flag is "1". Therefore, the battery 11 has been stored in the battery station 20 with the station identifier "IDS1". The SOC of the battery 11 is 90%.

[0047] For example, the record in the second row shows data regarding the battery 11 with the battery identifier "IDB2". Since the station identifier is "IDS2" and the inventory flag is "1", the battery 11 has been stored in the battery station 20 with the station identifier "IDS2". The SOC of the battery 11 is 90%. In this example, the scheduled date and time for retrieval is "YYYYMMDD 9:00" and the vehicle information is "INFC1". Here, "YYYYMMDD" represents the year, month, and day. Therefore, the battery 11 is scheduled to be installed in the vehicle 10 with the vehicle information "INFC1" at this scheduled date and time and retrieved from the battery station 20 with the station identifier "IDS2".

[0048] For example, the record in the third row shows data regarding the battery 11 with the battery identifier "IDB3". Since the inventory flag is "0", the battery 11 has not been stored in the battery station 20. In this example, the scheduled date and time for deposit is "YYYYMMDD 13:00", the vehicle information is "INFC2", and the station identifier is "IDS3". Therefore, the battery 11 is scheduled to be removed from the vehicle 10 with the vehicle information "INFC2" and deposited in the battery station 20 with the station identifier "IDS3" at this scheduled date and time. The estimated value of the SOC when the battery 11 is deposited is 40%.

[0049] For example, the record in the fourth row shows data regarding the battery 11 with the battery identifier "IDB4". Since the inventory flag is "0", the battery 11 has not been stored in the battery station 20. In this example, the scheduled date and time for deposit is "YYYYMMDD 11:00", the vehicle information is "INFC3", and the station identifier is "IDS4". Therefore, the battery 11 is scheduled to be removed from the vehicle 10 with the vehicle information "INFC3" and deposited in the battery station 20 with the station identifier "IDS4" at this scheduled date and time. The estimated value of the SOC when the battery 11 is deposited is 60%. Additionally, in this example, the scheduled date and time for retrieval is "YYYYMMDD 16:00" and the vehicle information for retrieval is "INFC4". Therefore, the battery 11 is scheduled to be installed in the vehicle 10 with the vehicle information "INFC4" at this scheduled date and time and retrieved from the battery station 20 with the station identifier "IDS4".

[0050] The processing unit 33 is constituted by, for example, one or more processors, one or more memories, etc., and is configured to perform processing by executing a program. The processing unit 33 includes a replacement determination unit 34, a battery inquiry unit 35, a reservation processing unit 36, a storage processing unit 37, and a retrieval processing unit 38.

[0051] 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.

[0052] The battery inquiry unit 35 is configured to, when the battery 11 of the vehicle 10 should be replaced, use the management data DT to investigate the battery 11 that can be used by the vehicle 10 among the batteries 11 already stored in the battery station 20 and the batteries 11 to be stored in the battery station 20 in the future.

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

[0054] The storage 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 the battery 11 is stored at the battery station 20.

[0055] The retrieval processing unit 38 is configured to update the management data DT when the battery 11 is installed in the vehicle 10 at the battery station 20 and the battery 11 is retrieved from the battery station 20.

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

[0057] [Operations and Functions]

[0058] Next, the operations and functions of the battery management system 1 of the present embodiment will be described.

[0059] (Overall Operation Summary)

[0060] First, refer to Figure 1 、 3, the operation of the battery management system 1 will be described. The battery management device 30 manages data on the battery 11 stored in the battery station 20 and data on the battery 11 scheduled to be stored in the battery station 20 in the future. For example, when the battery remaining amount of the battery 11 of the vehicle 10 becomes low, the vehicle 10 communicates with the battery management device 30. The replacement determination unit 34 of the battery management device 30 determines whether the battery 11 of the vehicle 10 should be replaced based on the data supplied from the vehicle 10. When the battery 11 of the vehicle 10 should be replaced, the battery query unit 35 of the battery management device 30 uses the management data DT to check the battery 11 that can be used by the vehicle 10 among the batteries 11 stored in the battery station 20 and the batteries 11 that will be stored in the battery station 20 in the future. Furthermore, when the battery 11 of the vehicle 10 is replaced, the reservation processing unit 36 ​​of the battery management device 30 receives the reservation for battery replacement and updates the management data DT. Thereafter, if the vehicle 10 arrives at the battery station 20, the battery station 20 removes the battery 11 from the vehicle 10, and the storage processing unit 37 of the battery management device 30 updates the management data DT based on the data from the processing device 21 of the battery station 20. Thereafter, the battery station 20 installs another battery 11 to the vehicle 10, and the use processing unit 38 of the battery management device 30 updates the management data DT based on the data from the processing device 21 of the battery station 20.

[0061] (Detailed actions)

[0062] Hereinafter, an operation example of the battery management system 1 will be described in detail by giving several examples.

[0063] (Action Example E1)

[0064] Figure 5 An operation example E1 is shown as an operation example of the battery management system 1. Figure 5 In FIG. 1 , the battery 11 is represented by a symbol of a battery indicating the remaining battery level.

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

[0066] In this example, there is a battery station 20 with a station identifier of "IDS11" on the predetermined driving route of the vehicle 10A. A battery 11 with a battery identifier of "IDB11" is stored in the battery station 20. The remaining battery level of the battery 11 is 90%, and the available driving distance is 300 km. By replacing the battery in the vehicle 10A with the battery 11 at the battery station 20, the vehicle 10A can reach the target location.

[0067] Hereinafter, the operation of the battery management system 1 in such an example will be described.

[0068] Figure 6 An operation example of the battery management system 1 in the operation example E1 is shown. Figures 7A to 7C An example of the management data DT in the operation example E1 is shown.

[0069] First, the communication unit 16 of the vehicle 10A, based on an instruction from the control unit 18, sends data regarding the predetermined driving route of the vehicle 10A, the driving position where the vehicle 10A is currently driving, the vehicle information of the vehicle 10A, the battery identifier of the battery 11 installed in the vehicle 10A, the battery information of the battery 11, and the SOC of the battery 11 to the battery management device 30 (step S101). The vehicle 10A can send such data, for example, based on an instruction from the driver, or can send such data when the remaining battery level of the battery 11 in the vehicle 10A is below a predetermined amount. The communication unit 31 of the battery management device 30 receives this data.

[0070] Next, the replacement determination unit 34 of the battery management device 30 determines whether a battery replacement is required based on the data received by the communication unit 31 (step S102). Specifically, the replacement determination unit 34 calculates the future predetermined driving distance of the vehicle 10A based on the data regarding the predetermined driving route of the vehicle 10A and the driving position of the vehicle 10A. In addition, the replacement determination unit 34 calculates the available driving distance of the vehicle 10A based on the data regarding the maximum charge amount of the battery 11 included in the battery information, the SOC of the battery 11 of the vehicle 10A, and the power consumption of the vehicle 10A included in the vehicle information of the vehicle 10A. Then, the replacement determination unit 34 determines whether the vehicle 10A should perform a battery replacement by comparing the predetermined driving distance and the available driving distance.

[0071] As Figure 5 shown, in this operation example E1, since the available driving distance (100 km) of the vehicle 10A is shorter than the predetermined driving distance (200 km), the replacement determination unit 34 determines that the vehicle 10A should perform a battery replacement.

[0072] Next, the communication unit 31 of the battery management device 30 sends a notification indicating the need for battery replacement to the vehicle 10A based on an instruction from the processing unit 33 (step S103). The communication unit 16 of the vehicle 10A receives this notification.

[0073] Next, the communication unit 16 of the vehicle 10A sends a battery inquiry request to the battery management device 30 based on an instruction from the control unit 18 (step S104). That is, the control unit 18 of the vehicle 10A requests an investigation of whether there is a battery 11 that the vehicle 10A can use at multiple battery stations 20 on the predetermined driving route. The communication unit 31 of the battery management device 30 receives this battery inquiry request.

[0074] Next, the battery inquiry unit 35 of the battery management device 30 performs battery inquiry processing (step S105). Specifically, the battery inquiry unit 35 uses the management data DT to investigate the batteries 11 that the vehicle 10A can use at multiple battery stations 20 on the predetermined driving route of the vehicle 10A. For example, the battery inquiry unit 35 can determine that the vehicle 10A can use the battery 11 when the available driving distance of the battery 11 is longer than the predetermined driving distance of the vehicle 10A. The available battery 11 can be a battery 11 stored at the battery station 20 or a battery 11 that is scheduled to be stored at the battery station 20 after being used by another vehicle 10.

[0075] Specifically, as Figure 7A shown, in this operation example E1, two batteries 11 located at two battery stations 20 can be used by the vehicle 10A. The battery 11 with the battery identifier "IDB11" is stored at the battery station 20 with the station identifier "IDS11", and the SOC is 90%. The battery 11 with the battery identifier "IDB12" is stored at the battery station 20 with the station identifier "IDS12", and the SOC is 70%. These two battery stations 20 are set on the predetermined driving route of the vehicle 10A.

[0076] Next, the communication unit 31 of the battery management device 30 sends the result of the battery inquiry processing based on an 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 as Figure 7A shown are sent. The communication unit 16 of the vehicle 10A receives the result of this battery inquiry processing.

[0077] Next, the user interface 17 of the vehicle 10A receives the selection operation of the battery replacement location based on the instruction from the control unit 18 (step S107). Specifically, the user interface 17 displays the data on the battery station 20 and the data on the usable battery 11 contained in the result of the battery query processing received by the communication unit 16. For example, the driver determines which battery station 20 to replace the battery 11 at based on the display content of the user interface 17, and performs the operation of selecting the battery station 20 at which the battery 11 is to be replaced. The user interface 17 receives the selection operation performed by the driver. Through this selection operation, the battery station 20 for battery replacement and the battery 11 installed in the vehicle 10A are selected.

[0078] Specifically, in this action example E1, the driver Figure 7A The battery station 20 whose station identifier is "IDS11" is shown, and a selection operation is performed to replace the battery 11. As a result, the battery 11 whose battery identifier is "IDB11" stored in the battery station 20 is selected as the battery 11 to be used.

[0079] Next, the communication unit 16 of the vehicle 10A transmits data on the battery identifier of the selected battery 11, the scheduled date and time when the vehicle 10A arrives at the selected battery station 20, and the estimated value of the SOC of the battery 11 currently used by the vehicle 10A to the battery management device 30 based on the instruction from the control unit 18 (step S108). The estimated value of the SOC is the estimated value of the SOC when the vehicle 10A arrives at the battery station 20, and is calculated using the current driving position of the vehicle 10A, the position of the battery station 20, the current SOC, and the power consumption of the vehicle 10A. The communication unit 31 of the battery management device 30 receives the data.

[0080] Next, the reservation processing unit 36 ​​of the battery management device 30 performs reservation processing for battery replacement (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 when the battery 11 is taken out and the vehicle information in the record of the battery 11 scheduled to be installed in the vehicle 10A in the management data DT. In addition, the reservation processing unit 36 ​​newly registers the record of the battery 11 currently being used by the vehicle 10A in the management data DT. In this record, the scheduled date and time when the battery 11 is stored and the vehicle information are registered.

[0081] Specifically, if Figure 7BAs shown, in this operation example E1, the reservation processing unit 36 registers data on the scheduled date and time 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 removal is "YYYYMMDD 16:00", and the vehicle information is "INFC13". This vehicle information is the vehicle information of the vehicle 10A.

[0082] In addition, the reservation processing unit 36 newly registers the record of the battery 11 with the battery identifier "IDB13" that the vehicle 10A is using in the management data DT. The battery information of this battery 11 is "INFB13". The vehicle 10A replaces the battery at the battery station 20 with the station identifier "IDS11" where the battery 11 installed in the vehicle 10A is stored. In this example, the scheduled date and time for storage is "YYYYMMDD 16:00", and the vehicle information is "INFC13".

[0083] In this way, in the battery management system 1, the battery replacement of the vehicle 10A is reserved. Thereafter, the vehicle 10A continues to travel along the predetermined travel route and arrives at the battery station 20 with the station identifier "IDS11" where the battery replacement is to be performed.

[0084] At the battery station 20, for example, the staff operates the vehicle 10A and the processing device 21 of the battery station 20. The vehicle 10A and the processing device 21 of the battery station 20 perform a battery removal process of removing the battery 11 from the vehicle 10A based on the operation of the staff (step S111). The processing device 21 obtains the actual SOC data on this battery 11 in this process.

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

[0086] Next, the storage processing unit 37 of the battery management device 30 performs the storage process of the removed battery 11 (step S113). Specifically, the storage processing unit 37 updates the management data DT based on the data received by the communication unit 31 in step S112. For example, the storage processing unit 37 deletes the scheduled date and time and vehicle information in the case of storing the battery 11 in the record of the removed battery 11 in the management data DT, and sets the inventory flag to "1". That is, since this battery 11 has been stored in this battery station 20, the storage processing unit 37 deletes the scheduled date and time and vehicle information and sets the inventory flag to "1". In addition, the storage processing unit 37 registers the actual SOC data on the removed battery 11 in this record.

[0087] Specifically, if Figure 7C As shown, in this operation example E1, the storage processing unit 37 deletes the scheduled date and time and vehicle information when the battery 11 is stored in the record of the battery 11 with the battery identifier "IDB13" removed from the vehicle 10A, and sets the inventory flag to "1". Then, the storage processing unit 37 registers data on the actual SOC of the removed battery 11 in the record.

[0088] Furthermore, the vehicle 10A and the processing device 21 of the battery station 20 perform a battery mounting process for mounting the battery on the vehicle 10A based on the operation of the worker (step S114 ).

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

[0090] Next, the access processing unit 38 of the battery management device 30 performs access processing of the installed battery 11 (step S116). Specifically, in step S115, the access processing unit 38 updates the management data DT based on the data received by the communication unit 31. For example, the access processing unit 37 deletes the record of the installed battery 11 in the management data DT. That is, the battery 11 installed in the vehicle 10A is temporarily used by the vehicle 10A, so it will not be used by other vehicles 10. Therefore, the removal processing unit 38 deletes the record of the battery 11 installed in the vehicle 10A in order to exclude the battery 11 from the management object.

[0091] Specifically, if Figure 7C As shown, in this action example E1, the access processing unit 38 deletes the record of the battery 11 with the battery identifier "IDB11" installed in the vehicle 10A ( Figure 7B ).

[0092] This completes the action.

[0093] (Action Example E2)

[0094] Figure 8Shows operation example E2 as another operation example of the battery management system 1. In this example, each of the two vehicles 10 (hereinafter, referred to as vehicle 10B and 10C) travels toward a target location on a predetermined travel route. The battery identifier of the battery 11 of vehicle 10B is "IDB22", the remaining battery level is 30%, and the available travel distance is 100 km. This vehicle 10B is scheduled to travel a further 200 km until the target location. Therefore, this vehicle 10B cannot reach the target location using the current battery 11. In addition, the battery identifier of the battery 11 of vehicle 10C is "IDB23", the remaining battery level is 5%, and the available travel distance is 20 km. This vehicle 10C is scheduled to travel a further 70 km until the target location. Therefore, this vehicle 10C cannot reach the target location using the current battery 11.

[0095] In this example, there is a battery station 20 with a station identifier of "IDS21" on the predetermined travel routes of vehicles 10B and 10C. A battery 11 with a battery identifier of "IDB21" is stored in this battery station 20. The remaining battery level of this battery 11 is 90%, and the available travel distance is 300 km. Vehicle 10B can reach the target location by replacing the battery with this battery 11 at this battery station 20. By this battery replacement, vehicle 10B removes the battery 11 with a battery identifier of "IDB22". The remaining battery level of this battery 11 is 30%, and the available travel distance is 100 km. Vehicle 10C can reach the target location by replacing the battery with the battery 11 removed from vehicle 10B at this battery station 20.

[0096] Hereinafter, the operation of the battery management system 1 in such an example will be described.

[0097] Figures 9A to 9C Shows an operation example of the battery management system 1 in operation example E2. Figures 10A to 10E Shows an example of the management data DT in operation example E2.

[0098] First, in steps S201 to S209, vehicle 10B reserves battery replacement in the same manner as in operation example E1.

[0099] First, the communication unit 16 of vehicle 10B, based on an instruction from the control unit 18, sends data on the predetermined travel route of vehicle 10B, the travel position where vehicle 10B is currently traveling, the vehicle information of vehicle 10B, the battery identifier of the battery 11 installed in vehicle 10B, the battery information of this battery 11, and the SOC of this battery 11 to the battery management device 30 (step S201).

[0100] Next, the replacement determination unit 34 of the battery management device 30 determines whether battery replacement is necessary based on the data received by the communication unit 31 (step S202). AsFigure 8 As shown, in this operation example E2, since the available driving distance (100 km) of vehicle 10B is shorter than the predetermined driving distance (200 km), the replacement determination unit 34 determines that vehicle 10B should have its battery replaced.

[0101] Next, based on an instruction from the processing unit 33, the communication unit 31 of the battery management device 30 sends a notification indicating the need to replace the battery to vehicle 10B (step S203).

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

[0103] Next, the battery inquiry unit 35 of the battery management device 30 performs battery inquiry processing (step S205). As Figure 10A shown, in this operation example E2, a battery 11 with a battery identifier of "IDB21" is stored at a battery station 20 with a station identifier of "IDS21", and the SOC is 90%. This battery station 20 is set on the predetermined driving route of vehicle 10B.

[0104] Next, based on an instruction from the processing unit 33, the communication unit 31 of the battery management device 30 sends the result of the battery inquiry processing (step S206).

[0105] Next, based on an instruction from the control unit 18, the user interface 17 of vehicle 10B accepts a selection operation for the battery replacement location (step S207). In this operation example E2, the driver Figure 10A performs a selection operation to indicate the intention to replace the battery 11 at the battery station 20 with the station identifier of "IDS21" as shown. Thereby, the battery 11 with a battery identifier of "IDB21" stored at this battery station 20 is selected as the battery 11 to be used.

[0106] Next, based on an instruction from the control unit 18, the communication unit 16 of vehicle 10B sends data on the battery identifier of the selected battery 11, the estimated value of the SOC of the battery 11 currently used by vehicle 10B, and the scheduled date and time for vehicle 10B to reach the selected battery station 20 to the battery management device 30 (step S208).

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

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

[0109] In addition, the reservation processing unit 36 newly registers the record of the battery 11 with the battery identifier "IDB22" that the vehicle 10B is using in the management data DT. The battery information of this battery 11 is "INFB22". The vehicle 10B replaces the battery at the battery station 20 with the station identifier "IDS21" where the battery 11 installed in the vehicle 10B is stored. In this example, the scheduled date and time for deposit is "YYYYMMDD 16:00", and the vehicle information is "INFC22".

[0110] In this way, in the battery management system 1, the battery replacement of the vehicle 10B is reserved.

[0111] Next, in steps S211 to S219, the vehicle 10C reserves the battery replacement in the same manner.

[0112] First, based on an instruction from the control unit 18, the communication unit 16 of the vehicle 10C sends data on the scheduled driving route of the vehicle 10C, the driving position where the vehicle 10C is currently driving, the vehicle information of the vehicle 10C, the battery identifier of the battery 11 installed in the vehicle 10C, the battery information of this battery 11, and the SOC of this battery 11 to the battery management device 30 (step S211).

[0113] Next, the replacement determination unit 34 of the battery management device 30 determines whether battery replacement is required based on the data received by the communication unit 31 (step S212). As Figure 8 shown, in this operation example E2, since the drivable distance (20 km) of the vehicle 10C is shorter than the scheduled driving distance (70 km), the replacement determination unit 34 determines that the vehicle 10C should perform battery replacement.

[0114] Next, based on an instruction from the processing unit 33, the communication unit 31 of the battery management device 30 sends a notification indicating the need for battery replacement to the vehicle 10C (step S213).

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

[0116] Next, the battery inquiry unit 35 of the battery management device 30 performs a battery inquiry process (step S215). As Figure 10B shown, in operation example E2, the battery 11 with the battery identifier "IDB22" can be used. That is, the battery 11 with this battery identifier "IDB22" is scheduled to be stored at the battery station 20 with the station identifier "IDS21" at 16:00 on this day, and the SOC is 30%. Thus, although the SOC of this battery 11 is not high, the driving distance (100 km) of this battery 11 is long enough compared to the scheduled driving distance (20 km) of the vehicle 10C, so the vehicle 10C can use this battery 11. It should be noted that the battery 11 with the battery identifier "IDB21" is scheduled to be taken and reserved on this day, so the vehicle 10C cannot use this battery 11.

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

[0118] Next, the user interface 17 of the vehicle 10C accepts a selection operation of the battery replacement location based on the instruction from the control unit 18 (step S217). In this operation example E2, the driver makes a selection operation indicating the intention to replace the battery 11 at the battery station 20 with the station identifier "IDS21" as Figure 10B shown. Thereby, at this battery station 20, the battery 11 with the battery identifier "IDB22" that is scheduled to be stored at 16:00 on this day is selected as the battery 11 to be used.

[0119] Next, the communication unit 16 of the vehicle 10C sends data on the battery identifier of the selected battery 11, the scheduled date and time for the vehicle 10C to reach the selected battery station 20, and the estimated value of the SOC of the battery 11 currently used by the vehicle 10C to the battery management device 30 based on the instruction from the control unit 18 (step S218).

[0120] Next, the reservation processing unit 36 of the battery management device 30 performs a reservation process for battery replacement (step S219).

[0121] Specifically, as Figure 10C shown, in this operation example E2, the reservation processing unit 36 registers data on the scheduled date and time and vehicle information in the record of the battery 11 with the battery identifier "IDB22" that is scheduled to be installed in the vehicle 10C in the case of taking the battery 11. In this example, the scheduled date and time for taking is "YYYYMMDD 18:00", and the vehicle information is "INFC23". This vehicle information is the vehicle information of the vehicle 10C.

[0122] In addition, the reservation processing unit 36 newly registers a record of the battery 11 with the battery identifier "IDB23" being used by the vehicle 10C into the management data DT. The battery information of this battery 11 is "INFB23". The vehicle 10C replaces the battery at the battery station 20 with the station identifier "IDS21" that stores the battery 11 installed in the vehicle 10C. In this example, the reserved date and time is "YYYYMMDD 18:00", and the vehicle information is "INFC23".

[0123] In this way, in the battery management system 1, the battery replacement of the vehicle 10C is reserved.

[0124] Thereafter, the vehicle 10B arrives at the battery station 20 with the station identifier "IDS21" at around 16:00 as scheduled. Then, the vehicle 10B performs battery replacement in steps S221 to S228.

[0125] At the battery station 20, for example, the staff operates the vehicle 10B and the processing device 21 of the battery station 20. The vehicle 10B and the processing device 21 of the battery station 20 perform a battery removal process of removing the battery 11 from the vehicle 10B based on the operation of the staff (step S221). The processing device 21 obtains the actual SOC data of the battery 11 in this process.

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

[0127] Next, the storage processing unit 37 of the battery management device 30 performs the storage processing of the removed battery 11 (step S223). As Figure 10D shown, in this operation example E2, the storage processing unit 37 deletes the reserved date and time and vehicle information in the case of storing the battery 11 in the record of the battery 11 with the battery identifier "IDB22" removed from the vehicle 10B, and sets the inventory flag to "1". Then, the storage processing unit 37 registers the actual SOC data of the removed battery 11 in this record.

[0128] Next, the communication unit 31 of the battery management device 30 sends a notice indicating that the battery 11 is saved to the vehicle 10C based on an instruction from the processing unit 33 (step S224). The communication unit 16 of the vehicle 10C receives this notice.

[0129] Next, based on an instruction from the control unit 18, the user interface 17 of the vehicle 10C displays that the battery 11 scheduled to be installed in the future is stored at the battery station 20 (step S225). Thereby, the driver of the vehicle 10C can confirm that the battery 11 can be replaced at the battery station 20.

[0130] In addition, based on the operation of the staff, the processing device 21 of the vehicle 10B and the battery station 20 performs a battery installation process of installing the battery into the vehicle 10B (step S226).

[0131] Next, the processing device 21 of the battery station 20 sends data of the battery identifier regarding the battery 11 installed in step S226 to the battery management device 30 (step S227).

[0132] Next, the withdrawal processing unit 38 of the battery management device 30 performs a withdrawal process of the installed battery 11 (step S228). As Figure 10D shown, in this operation example E2, the withdrawal processing unit 38 deletes the record of the battery 11 with the battery identifier "IDB21" installed in the vehicle 10B that is installed in the vehicle 10B ( Figure 10C ).

[0133] Thereafter, the vehicle 10C arrives at the battery station 20 with the station identifier "IDS21" at around 18:00 as scheduled. Then, the vehicle 10C performs battery replacement in steps S231 to S236.

[0134] At the battery station 20, for example, the staff operates the vehicle 10C and the processing device 21 of the battery station 20. Based on the operation of the staff, the vehicle 10C and the processing device 21 of the battery station 20 perform a battery removal process of removing the battery 11 from the vehicle 10C (step S231). The processing device 21 obtains the actual SOC data regarding the battery 11 in this process.

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

[0136] Next, the storage processing unit 37 of the battery management device 30 performs a storage process of the removed battery 11 (step S233). As Figure 10E shown, in this operation example E2, the storage processing unit 37 deletes the scheduled date and time and vehicle information in the case of storing the battery 11 in the record of the battery 11 with the battery identifier "IDB23" removed from the vehicle 10C, and sets the inventory flag to "1". Then, the storage processing unit 37 registers the actual SOC data regarding the removed battery 11 in this record.

[0137] In addition, the processing device 21 of the vehicle 10C and the battery station 20 performs a battery installation process of installing the battery into the vehicle 10C based on the operation of the staff (step S234).

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

[0139] Next, the acquisition processing unit 38 of the battery management device 30 performs an acquisition process on the installed battery 11 (step S236). As Figure 10E shown, in this operation example E2, the acquisition processing unit 38 deletes the record of the battery 11 with the battery identifier "IDB22" installed in the vehicle 10C ( Figure 10D ).

[0140] The above is the end of this operation.

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

[0142] In this way, in the battery management device 30, a processing circuit (processing unit 33) and a communication circuit (communication unit 31) are provided. The processing circuit (processing unit 33) can manage data on a plurality of batteries 11 used by the vehicle 10 capable of replacing the battery 11, and can determine whether the second vehicle 10 can use the first battery based on the battery remaining amount of the first battery 11 before replacement in the first vehicle 10 (such as the vehicle 10B) that has reserved a battery replacement at the first battery station 20. The communication circuit (communication unit 31) can, when the second vehicle 10 (such as the vehicle 10C) can use the first battery, send a notice indicating that the second battery 11 of the second vehicle 10 can be replaced with the first battery 11 at the first battery station 20 to the second vehicle 10 (such as the vehicle 10C). Thus, for example, the battery station 20 does not need to pre-store the battery 11 that the vehicle 10C can use, and the vehicle 10C can use the battery 11 that the vehicle 10B, for example, has used before, so the residence time of the battery 11 at the battery station 20 can be shortened.

[0143] That is, at the battery station, it is considered that a large number of batteries 11 will be pre-stored for battery replacement reservations. In this case, at the battery station, the residence time of the battery 11 will become longer. For example, when the residence time of a large number of batteries 11 is long, for example, it causes the staff at the battery station to spend time managing a large number of batteries 11. In addition, at the battery station, it is necessary to store a large number of batteries 11, resulting in a bloated facility.

[0144] On the other hand, in the battery management device 30, for example, the vehicle 10C can use the battery 11 previously used by the vehicle 10B, so the residence time of the battery 11 at the battery station 20 can be shortened. Thereby, the number of batteries 11 pre-stored at the battery station 20 can be reduced, and the man-hours of the staff at the battery station can be reduced. In addition, since the number of batteries 11 pre-stored at the battery station can be reduced, the facility can be streamlined.

[0145] In addition, in the battery management system 1 equipped with the battery management device 30, when taking out the battery 11, the battery 11 does not necessarily need to be fully charged. Thus, since the charging time required to fully charge the battery 11 each time is not needed, the residence time of the battery 11 at the battery station 20 can be shortened. In addition, in this way, since the battery 11 does not necessarily need to be fully charged, the charging frequency of the battery 11 can be reduced. As a result, the life of the battery 11 can be extended. It should be noted that, in this way, since the fully charged battery 11 is not necessarily taken out, it may be a little inconvenient for the driver. Therefore, for example, rewards such as additional points can be given to the driver who replaces the battery 11 with such a battery. By accumulating these points, the driver can receive various services.

[0146] In addition, in the battery management device 30, the communication circuit (communication unit 31) can send a notice indicating that the second battery 11 can be replaced with the first battery 11 at the first battery station to the second vehicle 10 (for example, the vehicle 10C) when the second vehicle 10 (for example, the vehicle 10C) can use the first battery. Thereby, the driver of the vehicle 10C can know the situation where the battery can be replaced at the first battery station 20. Therefore, the driver of the vehicle 10C can drive the vehicle 10C with confidence.

[0147] In the battery management device 30, the processing circuit (processing unit 33) can judge whether the second vehicle 10 (for example, the vehicle 10C) can use the first battery 11 based on the remaining battery level of the first battery 11 and the future scheduled driving distance in the scheduled driving route of the second vehicle 10 (for example, the vehicle 10C). Thereby, even when the remaining battery level of the battery 11 before replacement of the vehicle 10B is low, the processing unit 33 can judge with higher accuracy whether the vehicle 10C can use the battery 11.

[0148] In the battery management device 30, the processing circuit (processing unit 33) can determine whether the second vehicle (e.g., vehicle 10C) can reach the target location based on the remaining battery level of the second battery 11 and the future scheduled travel distance in the scheduled travel route of the second vehicle (e.g., vehicle 10C), and can determine whether the second vehicle (e.g., vehicle 10C) can use the first battery 11 when the second vehicle (e.g., vehicle 10C) cannot reach the target location. Thus, in the battery management device 30, when the battery 11 of the vehicle 10C needs to be replaced, it is possible to recommend the driver of the vehicle 10C to replace the battery based on the remaining battery level of the battery 11 of the vehicle 10C. Thus, the driver of the vehicle 10C can drive the vehicle 10C with peace of mind.

[0149] In the battery management device 30, the plurality of batteries 11 include batteries that have been stored in the first battery station 20 and batteries that are scheduled to be stored in the first battery station in the future. Thus, the battery management device 30 can suggest to the driver of the second vehicle (e.g., vehicle 10C) whether to replace the battery 11 with a fully charged battery 11 that has been stored in the first battery station 20 or to replace the battery 11 that has been used by the first vehicle (e.g., vehicle 10B) before replacement. Therefore, the driver can select to replace with an appropriate battery 11 according to the subsequent schedule after arriving at the destination.

[0150] [Effect]

[0151] As described above, in this embodiment, since a processing circuit and a communication circuit are provided, the retention time of the battery at the battery station can be shortened. The processing circuit can manage data on multiple batteries used in vehicles in which the battery can be replaced, and can determine whether the second vehicle can use the first battery based on the battery remaining level of the first battery before replacement in the first vehicle for which battery replacement is scheduled at the first battery station. The communication circuit can send a notification to the second vehicle 10 indicating that the 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.

[0152] In this embodiment, the processing circuit can determine whether the second vehicle can use the first battery based on the remaining battery level of the first battery and the future scheduled driving distance in the second vehicle's scheduled driving route, thereby being able to determine with higher accuracy whether the vehicle can use the battery.

[0153] In this embodiment, the processing circuit can determine whether the second vehicle can reach the target location based on the remaining battery level of the second battery 11 and the future planned driving distance in the planned driving route of the second vehicle. If the second vehicle cannot reach the target location, it can determine whether the second vehicle can use the first battery, and therefore can recommend battery replacement to the driver if battery replacement is necessary.

[0154] In the present embodiment, the plurality of batteries include the batteries stored in the first battery station and the batteries that are scheduled to be stored in the first battery station in the future. Therefore, it is possible to recommend to the driver of the second vehicle, for example, to replace with the batteries stored in the first battery station and fully charged, and to replace with the batteries before replacement used by the first vehicle.

[0155] [Modification Example 1]

[0156] In the above embodiment, as Figure 8 shown, at the battery station 20, the battery 11 used by the vehicle 10B is directly delivered to the vehicle 10C, but it is not limited thereto. Instead, for example, at the battery station 20, the battery 11 used by the vehicle 10B can be charged and the charged battery 11 can be delivered to the vehicle 10C.

[0157] [Modification Example 2]

[0158] In the above embodiment, in the operation example E2, at the battery station 20 selected by the driver of the vehicle 10B, the batteries of the vehicles 10B and 10C are replaced, but it is not limited thereto. For example, it is also possible to further change the battery station 20 at which the battery replacement is performed. For example, the battery station 20 is changed based on the traffic conditions around the battery station 20 where the battery replacement is scheduled and the request from the vehicle 10C.

[0159] Figure 11 An operation example of the battery management system 1 showing this modification example is shown. In the battery management system 1, this process is performed after making an appointment for battery replacement of the vehicles 10B and 10C.

[0160] First, the communication unit 31 of the battery management device 30 sends a transmission request for the scheduled 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.

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

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

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

[0164] Next, the battery query unit 35 of the battery management device 30 performs a battery query process using the management data DT (S305). Specifically, the battery query unit 35 uses the management data DT to check the batteries 11 that can be used by the vehicle 10B in the plurality of battery stations 20 on the scheduled travel route of the vehicles 10B and 10C. The usable batteries 11 may be batteries 11 that have been stored in the battery station 20, or batteries 11 that are scheduled to be stored in the battery station 20 after being used by other vehicles 10.

[0165] Next, the communication unit 31 of the battery management device 30 transmits a request to change the battery replacement location based on the instruction from the processing unit 33 (step S306). Specifically, the communication unit 31 transmits data on the battery 11 that can be used by the vehicle 10B and data on the battery station 20 that can be replaced with the battery 11 found in step S305, and transmits a request to change the battery replacement location. The communication unit 16 of the vehicle 10B receives the data.

[0166] Next, the user interface 17 of the vehicle 10B receives 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 data on the battery station 20 and data on the usable batteries 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 receives the decision operation performed by the driver.

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

[0168] Next, the reservation processing unit 36 ​​of the battery management device 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 queried in step S305 that is scheduled to be used by the vehicle 10B, the record of the battery 11 removed from the vehicle 10B and scheduled to be used by the vehicle 10C, and the record of the battery 11 removed from the vehicle 10B in the management data DT.

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

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

[0171] The above is the end of this operation.

[0172] In the battery management device 30 of this modification, the processing circuit (processing unit 33) can further investigate whether there is a second battery station where the first vehicle (such as vehicle 10B) can replace the battery. If there is a second battery station, the communication circuit (communication unit 31) can request the first vehicle (such as vehicle 10B) to change the battery replacement location from the first battery station to the second battery station, and can receive a consent notice from the first vehicle (such as vehicle 10B). When the communication circuit (communication unit 31) receives a consent notice from the first vehicle (such as vehicle 10B), the processing circuit (processing unit 33) can send a notice indicating that the second battery can be replaced with the first battery at the second battery station to the second vehicle (such as vehicle 10C). Thus, in this battery management device 30, since the battery replacement location can be changed, for example, even in the case of unexpected troubles, the battery can be replaced by changing the battery replacement location.

[0173] The above is an example of several embodiments of the present disclosure with reference to the drawings, but the present disclosure is by no means limited to the above embodiments. Those skilled in the art should understand that various deformations and changes can be made without departing from the scope defined by the appended claims. As long as such various deformations and changes fall within the scope of the appended claims and their equivalents, the present disclosure is intended to include these deformations and changes.

[0174] For example, in the above embodiment, the management data DT Figure 4 shown is used, but it is not limited thereto. It may not include some of the data included in the management data DT, and may also include other data.

[0175] For example, the Figure 6 , 9A processing sequence shown in FIGS. 9A to 9C in the above embodiment is an example, and it may also be a processing sequence different from this sequence.

[0176] The effects described in this specification are only exemplary, and the effects of the present disclosure are not limited to those described in this specification. Therefore, other effects can also be obtained for the present disclosure.

[0177] In addition, the present disclosure can be implemented in the following manner. (1)

[0179] A battery management device, comprising:

[0180] A processing circuit capable of managing data on a plurality of batteries used in a vehicle with replaceable batteries, and capable of determining whether a second vehicle can use the first battery based on the remaining battery capacity of the first battery before replacement in a first vehicle that has scheduled a battery replacement at a first battery station; and

[0181] A communication circuit capable of, when the second vehicle can use the first battery, sending a notification to the second vehicle indicating the intention to replace the second battery of the second vehicle with the first battery at the first battery station. (2)

[0183] The battery management device according to (1) above, wherein

[0184] The processing circuit can determine whether the second vehicle can use the first battery based on the remaining battery capacity of the first battery and the future scheduled driving distance in the scheduled driving route of the second vehicle. (3)

[0186] The battery management device according to (1) or (2) above, wherein

[0187] The processing circuit can determine whether the second vehicle can reach the target location based on the remaining battery capacity of the second battery and the future scheduled driving distance in the scheduled driving route of the second vehicle, and can determine whether the second vehicle can use the first battery when the second vehicle cannot reach the target location. (4)

[0189] The battery management device according to any one of (1) to (3) above, wherein

[0190] The plurality of batteries include batteries already stored at the first battery station and batteries scheduled to be stored at the first battery station in the future. (5)

[0192] The battery management device according to any one of (1) to (4) above, wherein

[0193] The processing circuit can further investigate whether there is a second battery station at which the first vehicle can perform a battery replacement,

[0194] In the presence of the second battery station, the communication unit can request the first vehicle to change the location for battery replacement from the first battery station to the second battery station, and can receive a notice of consent from the first vehicle.

[0195] When the communication circuit receives a notice of consent from the first vehicle, the processing circuit can send a notice to the second vehicle indicating that the second battery can be replaced with the first battery at the second battery station.

[0196] Figure 3 The illustrated processing unit 33 can be implemented by a circuit 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 execute Figure 3 all or part of the various functions in the illustrated processing unit 33 by reading instructions from at least one non-transitory and tangible computer-readable medium. Such a medium can take various forms including 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 memories or non-volatile memories, but is not limited thereto. Volatile memories can include DRAM and SRAM. Non-volatile memories can include ROM and NVRAM. An ASIC is an integrated circuit (IC) dedicated to executing Figure 3 all or part of the various functions in the illustrated processing unit 33. An FPGA is an integrated circuit designed to be configured to execute Figure 3 all or part of the various functions in the illustrated processing unit 33 after manufacture.

Claims

1. A battery management device, It is characterized in that have: a processing circuit capable of managing data on a plurality of batteries used by vehicles capable of battery replacement, and capable of determining whether a second vehicle can use the first battery based on a remaining battery level of a first battery before replacement in a first vehicle for which battery replacement is scheduled at a first battery station; as well as The communication circuit can send 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 can use the first battery.

2. The battery management device according to claim 1, It is characterized in that The processing circuit can determine whether the second vehicle can use the first battery based on the remaining battery level of the first battery and a future scheduled travel distance in a scheduled travel route of the second vehicle.

3. The battery management device according to claim 1, It is characterized in that The processing circuit can determine whether the second vehicle can reach the target location based on the remaining battery level of the second battery and the future planned driving distance of the second vehicle in the planned driving route. If the second vehicle cannot reach the target location, the processing circuit can determine whether the second vehicle can use the first battery.

4. The battery management device according to claim 1, It is characterized in that The plurality of batteries include batteries already stored in the first battery station and batteries scheduled to be stored in the first battery station in the future.

5. The battery management device according to claim 1, It is characterized in that The processing circuit can further investigate whether there is a second battery station where the battery of the first vehicle can be replaced, When the second battery station exists, the communication circuit can request the first vehicle to change the location for battery replacement from the first battery station to the second battery station, and can receive a notification of consent from the first vehicle. When the communication circuit receives a notification of consent from the first vehicle, the processing circuit can send a notification to the second vehicle indicating that the second battery can be replaced with the first battery at the second battery station.

Images