Battery pack management method, battery pack, management server, management system, and program

Abstract

In this battery pack management method for managing battery packs (20) that are exchangeably connected to a mobile body (10), log information for a first battery pack among a plurality of battery packs (20) connected to the mobile body (10) and log information for at least one second battery pack different from the first battery pack are stored in a storage unit (26) of the first battery pack.

Description

Battery pack management method, battery pack, management server, management system and program

[0001] The present disclosure relates to a battery pack management method, a battery pack, a management server, a management system, and a program.

[0002] Electrically powered vehicles are well known. Battery packs, which are replaceable and connected to electric vehicles, are attracting attention as batteries for electric vehicles. Furthermore, with the introduction of a battery passport as a future initiative, information on battery usage is expected to attract attention.

[0003] Patent Document 1 discloses an information processing device that appropriately acquires information on the usage status of a portable storage battery at a rental location, appropriately identifies the connected electrical equipment and usage method, and reduces deterioration of the storage battery.

[0004] JP 2019-164692 A

[0005] When a battery pack is used in an electric vehicle, for example, if a malicious user tampers with the battery pack's log information, it becomes impossible to correctly grasp the battery's usage status. If the log information is tampered with or otherwise fraudulently altered, it is necessary to take action, but before that, it is necessary to detect that an inconsistency has occurred in the log information.

[0006] The present disclosure provides a battery pack management method and the like that can detect when an inconsistency occurs in the log information of a battery pack.

[0007] A battery pack management method according to one aspect of the present disclosure is a method for managing a battery pack that is replaceably connected to a mobile body, and stores log information of a first battery pack among a plurality of battery packs connected to the mobile body, and log information of at least one second battery pack different from the first battery pack, in a memory unit of the first battery pack.

[0008] A battery pack management method according to one aspect of the present disclosure is a method for managing a battery pack that is replaceably connected to a mobile body, and stores log information of a first battery pack among a plurality of battery packs connected to the mobile body, and log information of at least one second battery pack different from the first battery pack, in a management server.

[0009] A battery pack according to one aspect of the present disclosure is a battery pack that is replaceably connected to a mobile body, and includes a battery and a memory unit that stores information related to the battery pack, and the memory unit stores log information for the battery pack itself among multiple battery packs connected to the mobile body, as well as log information for other battery packs that are different from the battery pack itself.

[0010] A management server according to one aspect of the present disclosure is a management server that manages battery packs that are interchangeably connected to a mobile body, and includes an information acquisition unit that acquires log information of a first battery pack among a plurality of battery packs connected to the mobile body, and log information of at least one second battery pack that is different from the first battery pack, and a memory unit that stores the log information of the first battery pack and the log information of at least one of the second battery packs.

[0011] A management system according to one aspect of the present disclosure includes a plurality of battery packs that are interchangeably connected to a mobile body, and a management server that manages the plurality of battery packs, and the plurality of battery packs share their respective log information among themselves.

[0012] A program according to one aspect of the present disclosure is a program for causing a computer to execute the above-described battery pack management method.

[0013] According to the battery pack management method and the like of the present disclosure, it is possible to detect an inconsistency in the log information of the battery pack.

[0014] FIG. 1 is a diagram illustrating an overall configuration of a management system according to a first embodiment. FIG. 2 is a diagram illustrating a power management system and a battery pack provided in a mobile object. FIG. 3 is a diagram illustrating identification information, etc., of a battery pack connected to a mobile object. FIG. 4 is a diagram illustrating an example of battery control information output from a mobile object. FIG. 5 is a diagram illustrating a configuration of a battery pack according to the first embodiment. FIG. 6 is a diagram illustrating an example of basic information of a battery pack. FIG. 7 is a diagram illustrating an example of battery control information stored in a battery pack. FIG. 8A is a diagram illustrating an example of log information of a battery pack stored in a storage unit. FIG. 8B is a diagram illustrating an example of log information of another battery pack stored in a storage unit. FIG. 9 is a diagram illustrating a configuration of a battery station according to the first embodiment. FIG. 10 is a diagram illustrating a configuration of a management server according to the first embodiment. FIG. 11A is a diagram illustrating an example of first log set information stored in the management server. FIG. 11B is a diagram illustrating an example of second log set information stored in the management server. FIG. 11C is a diagram illustrating another example of second log set information stored in the management server. FIG. 12 is a diagram illustrating an example of a blacklist of battery packs. FIG. 13 is a sequence diagram showing an example of the operation of the management system when the log information of the battery pack is normal. FIG. 14 is a sequence diagram showing an example of the operation of the management system when there is an inconsistency in the log information of the battery pack. FIG. 15 is a diagram showing an example of log information with an inconsistency. FIG. 16 is a sequence diagram showing another example of the operation of the management system when there is an inconsistency in the log information of the battery pack. FIG. 17 is a diagram showing another example of log information with an inconsistency. FIG. 18 is a flowchart showing an example of the operation of the battery pack when acquiring log information. FIG. 19 is a flowchart showing an example of the operation of the battery pack when acquiring identification information. FIG. 20 is a flowchart showing an example of the operation of the battery pack when sharing log information. FIG. 21 is a flowchart showing an example of the operation of the battery station. FIG. 22 is a flowchart showing the basic operation of the management server. FIG. 23 is a diagram showing in detail a part of the basic operation shown in FIG. 22. FIG. 24 is a diagram showing in detail another part of the basic operation shown in FIG. 22.FIG. 25 is a diagram showing the overall configuration of a management system according to a second embodiment. FIG. 26 is a diagram showing a power management system and a battery pack provided in a mobile object. FIG. 27 is a sequence diagram showing an example of the operation of the management system. FIG. 28 is a diagram showing an example of battery control information output from a mobile object. FIG. 29 is a flowchart showing an example of the operation of the battery pack. FIG. 30 is a diagram showing the overall configuration of a management system according to a third embodiment. FIG. 31 is a diagram showing a power management system and a battery pack provided in a mobile object. FIG. 32 is a diagram showing the configuration of a battery pack according to the third embodiment. FIG. 33 is a diagram showing identification information, etc., of a battery pack connected to a mobile object. FIG. 34 is a sequence diagram showing an example of the operation of the management system. FIG. 35 is a flowchart showing an example of the operation of the battery pack when acquiring log information. FIG. 36 is a flowchart showing an example of the operation of the battery pack when acquiring identification information.

[0015] When a battery pack is used in an electric vehicle, there is a risk that a malicious user may tamper with the battery pack's log information. For example, if an electric vehicle is infected with malware, the battery pack's log information may be tampered with. Furthermore, the battery pack's log information may be tampered with between the time the battery pack is removed from the electric vehicle and the time it is returned to the battery station. If the log information is tampered with in this way, it becomes impossible to accurately grasp the battery's usage status. If the log information is tampered with or otherwise fraudulent, it is necessary to take action, but before that can happen, it is necessary to detect that an inconsistency has occurred in the log information.

[0016] The present disclosure provides a battery pack management method, etc. for solving the above-mentioned problems. Hereinafter, an example of a battery pack management method, etc. according to an embodiment of the present disclosure will be described.

[0017] The battery pack management method of Example 1 is a method for managing a battery pack that is replaceably connected to a mobile body, and stores log information of a first battery pack among a plurality of battery packs connected to the mobile body, and log information of at least one second battery pack different from the first battery pack, in a memory unit of the first battery pack.

[0018] This makes it possible to detect an inconsistency in the log information of the first battery pack based on the log information stored in the first battery pack. By this detection, it is possible to verify whether the first battery pack has been tampered with before the second battery pack is returned to the battery station, for example.

[0019] A battery pack management method of Example 2 is the battery pack management method described in Example 1, and may further include acquiring log information of the second battery pack output from the second battery pack before storing the log information of the second battery pack in the memory unit.

[0020] This makes it possible to detect an inconsistency in the log information of the first battery pack based on the log information stored in the first battery pack. By this detection, it is possible to verify whether the first battery pack has been tampered with before the second battery pack is returned to the battery station, for example.

[0021] A battery pack management method of Example 3 is the battery pack management method described in Example 2, and may further include outputting log information of the first battery pack to the second battery pack.

[0022] This makes it possible to detect an inconsistency in the log information of the first battery pack based on the log information stored in the first battery pack. By this detection, it is possible to verify whether the first battery pack has been tampered with before the second battery pack is returned to the battery station, for example.

[0023] A battery pack management method of Example 4 is the battery pack management method described in any of Examples 1 to 3, wherein the log information of the first battery pack may include information on the remaining battery capacity of the first battery pack, and the log information of the second battery pack may include information on the remaining battery capacity of the second battery pack.

[0024] This allows multiple battery packs to share information about their remaining battery power levels, making it possible to detect inconsistencies in the information about the remaining battery power levels of the battery packs.

[0025] A battery pack management method of Example 5 is the battery pack management method described in Example 4, and may further verify log information of the first battery pack by comparing the remaining battery capacity of the first battery pack with information related to a battery control value of the first battery pack.

[0026] This makes it possible to verify whether the log information shared between multiple battery packs has been tampered with during sharing.

[0027] A battery pack management method of Example 6 is the battery pack management method described in Example 5, wherein the battery control value of the first battery pack may be a discharge amount required for the first battery pack.

[0028] This allows the log information of the battery pack to be accurately verified based on the remaining battery charge and the discharge amount required for the battery pack, thereby making it possible to detect any inconsistencies in the log information of the battery pack.

[0029] A battery pack management method of Example 7 is the battery pack management method described in any of Examples 3 to 6, in which, when the moving body is in a parked state, log information of the second battery pack output from the second battery pack is acquired, and log information of the first battery pack is output to the second battery pack.

[0030] This allows the moving objects to share log information with each other when they are parked, thereby reducing the number of times the log information is shared and the amount of power consumed to share the log information.

[0031] A battery pack management method of Example 8 is the battery pack management method described in any of Examples 3 to 7, in which log information of the second battery pack output from the second battery pack is acquired using short-range wireless communication, and log information of the first battery pack is output to the second battery pack.

[0032] In this way, by acquiring and sharing log information using short-range wireless communication, it becomes difficult for the mobile device to tamper with the log information.

[0033] The battery pack management method of Example 9 is a method for managing a battery pack that is replaceably connected to a mobile body, and stores log information of a first battery pack among a plurality of battery packs connected to the mobile body, and log information of at least one second battery pack different from the first battery pack, in a management server.

[0034] This allows, for example, the log information of multiple battery packs to be shared by the management server, which makes it possible to detect inconsistencies in the log information of the battery packs.

[0035] A battery pack management method of Example 10 may be the battery pack management method described in Example 9, in which the management server acquires first log set information including log information of the first battery pack and log information of at least one of the second battery packs based on information output from the first battery pack, acquires second log set information including the log information of the first battery pack and log information of at least one of the second battery packs based on information output from the second battery pack, and stores the first log set information and the second log set information in a memory unit of the management server.

[0036] In this way, by storing the first log set information and the second log set information, it becomes possible to share the log information of multiple battery packs on the management server, which makes it possible to detect an inconsistency in the log information of the battery packs.

[0037] A battery pack management method of Example 11 is the battery pack management method of Example 10, and may further include verifying log information of the first battery pack.

[0038] In this way, by verifying the log information of the battery pack, it is possible to detect that an inconsistency has occurred in the log information of the battery pack.

[0039] A battery pack management method of Example 12 is the battery pack management method described in Example 11, and when verifying the log information of the first battery pack, if the first log set information includes information indicating that the log information of the first battery pack is inconsistent, the log information of the first battery pack may be determined to be incorrect.

[0040] This makes it possible to extract battery packs with incorrect log information.

[0041] A battery pack management method of Example 13 is the battery pack management method described in Example 11, and when verifying the log information of the first battery pack, the log information of the first battery pack included in the first log set information may be compared with the log information of the first battery pack included in the second log set information to verify the log information.

[0042] In this way, by comparing the log information of the battery packs, the log information of the battery packs can be easily verified, and it is thereby possible to detect any inconsistency in the log information of the battery packs.

[0043] The battery pack management method of Example 14 is the battery pack management method described in Example 13, and may determine that the log information of the first battery pack included in the first log set information is incorrect when the log information of the first battery pack included in the first log set information is different from the log information of the first battery pack included in two or more pieces of second log set information.

[0044] This makes it possible to extract battery packs with incorrect log information.

[0045] The battery pack management method of Example 15 is the battery pack management method described in Example 12 or 14, and may further include, when it is determined that the log information of the first battery pack is incorrect, outputting information indicating that there is fraud in the log information of the first battery pack.

[0046] This allows information indicating that there has been fraud in the battery pack's log information to be shared with an external device.

[0047] The battery pack management method of Example 16 is the battery pack management method described in Example 12 or 14, and may further include, when it is determined that the log information of the first battery pack is incorrect, listing the first battery pack and creating a blacklist that includes the first battery pack.

[0048] This makes it possible to present to an external device a list of battery packs with incorrect log information.

[0049] A battery pack management method of Example 17 is the battery pack management method of Example 16, further comprising suspending use of the first battery pack included in the blacklist.

[0050] This makes it possible to prevent battery packs included in the blacklist from being distributed.

[0051] The battery pack of Example 18 is a battery pack that is connectable to a mobile body in an exchangeable manner, and includes a battery and a memory unit that stores information about the battery pack, and the memory unit stores log information about the battery pack itself among multiple battery packs connected to the mobile body, as well as log information about other battery packs different from the battery pack itself.

[0052] This allows, for example, multiple battery packs to share their log information with each other, which makes it possible to detect inconsistencies in the log information of the battery packs.

[0053] The management server of Example 19 is a management server that manages battery packs that are replaceably connected to a mobile body, and includes an information acquisition unit that acquires log information of a first battery pack among a plurality of battery packs connected to the mobile body, and log information of at least one second battery pack different from the first battery pack, and a memory unit that stores the log information of the first battery pack and the log information of at least one of the second battery packs.

[0054] This allows, for example, the log information of multiple battery packs to be shared by the management server, which makes it possible to detect inconsistencies in the log information of the battery packs.

[0055] The management system of Example 20 is a management system comprising a plurality of battery packs that are interchangeably connected to a mobile body, and a management server that manages the plurality of battery packs, and the plurality of battery packs share their respective log information among themselves.

[0056] This allows multiple battery packs to share their log information with each other, which makes it possible to detect inconsistencies in the log information of the battery packs.

[0057] The program of Example 21 is a program for causing a computer to execute the battery pack management method according to any one of Examples 1 to 8.

[0058] This provides the same effect as the battery pack management method described above.

[0059] The program of Example 22 is a program for causing a computer to execute the battery pack management method according to any one of Examples 9 to 14.

[0060] This provides the same effect as the battery pack management method described above.

[0061] Hereinafter, the embodiments will be specifically described with reference to the drawings.

[0062] The embodiments described below are all comprehensive or specific examples. The numerical values, shapes, components, component placement and connection configurations, steps, and step order shown in the following embodiments are merely examples and are not intended to limit the present disclosure. Furthermore, among the components in the following embodiments, components not described in independent claims are described as optional components.

[0063] Furthermore, each figure is a schematic diagram and is not necessarily an exact illustration. Therefore, for example, the scales of the figures do not necessarily match. Furthermore, in each figure, substantially the same components are given the same reference numerals, and redundant explanations are omitted or simplified.

[0064] Furthermore, in this specification, terms indicating relationships between elements such as "same," as well as numerical values ​​and numerical ranges, are not expressions that only express a strict meaning, but are expressions that also include a substantially equivalent range, for example, a difference of about several percent (or about 10%).

[0065] First Embodiment [Configuration of Management System] The configuration of a management system according to this embodiment will be described with reference to FIG.

[0066] FIG. 1 is a diagram showing the overall configuration of a management system 1 according to the first embodiment.

[0067] The management system 1 is a system that manages log information of a battery pack 20 used in a mobile object 10 such as a vehicle.

[0068] 1, the management system 1 includes a plurality of battery packs 20a, 20b, and 20c, a plurality of battery stations 30a and 30b, and a plurality of management servers 40a and 40b. Hereinafter, all or some of the plurality of battery packs 20a to 20c may be referred to as battery packs 20, all or some of the plurality of battery stations 30a and 30b may be referred to as battery stations 30, and the plurality of management servers 40a and 40b may be referred to as management servers 40.

[0069] 1 shows an example in which the battery packs 20 and the battery stations 30 are managed by a plurality of management servers 40, but the number of management servers 40 is not limited to a plurality and may be one. Also shown in FIG. 1 is a mobile object 10 that is powered by the power of the battery pack 20. The management system 1 may be configured to include a plurality of mobile objects 10.

[0070] The battery pack 20 is detachable from the mobile object 10 and can communicate with the mobile object 10 while connected to the mobile object 10. The battery pack 20 is detachable from the battery station 30 and can communicate with the battery station 30 while connected to the battery station 30. The battery station 30 can communicate with the management server 40 via a communication network N such as the Internet or wide area Ethernet. The management servers 40a and 40b can communicate with each other via the communication network N. The communication between the battery station 30 and the management servers 40a and 40b may be wired communication or wireless communication.

[0071] [Configuration of the Moving Body] The configuration of the moving body will be described with reference to FIGS.

[0072] The mobile object 10 is an electric transport vehicle that runs on battery power. For example, the mobile object 10 includes electric vehicles such as electric motorbikes, electric bicycles, electric kick scooters, electric cars, electric buses, electric trucks, and trains. The mobile object 10 may also include aircraft such as drones and electric helicopters, and ships such as electric motorboats. The mobile object 10 of this embodiment can be driven by power supplied from the battery pack 20 when the battery pack 20 is connected.

[0073] FIG. 2 is a diagram showing a power management system 11 and a battery pack 20 provided in the vehicle 10.

[0074] The power management system 11 is a system that manages the power related to the battery installed in the mobile object 10. As shown in Figure 2, the power management system 11 of the mobile object 10 includes a plurality of connection ports 12, a control unit 15, and a memory unit 16.

[0075] A plurality of battery packs 20 are connected to the power management system 11. In this example, the power management system 11 has three connection ports 12a, 12b, and 12c, and three battery packs 20 are connected to the three connection ports 12a, 12b, and 12c in a one-to-one correspondence. The number of connection ports 12 and the number of battery packs 20 connected to the connection ports 12 are appropriately selected from the range of 2 to 8.

[0076] The connection port 12 is a port that is connected to the battery pack 20. The connection port 12 is, for example, a connector, and is connected to a connection port 22 of the battery pack 20. The connection port 12 is provided with a terminal for transmitting power and a terminal for transmitting and receiving communication signals (not shown). The power management system 11 transmits power and transmits and receives communication signals to and from the battery pack 20 via the connection port 12.

[0077] The control unit 15 is configured with a CPU (Central Processing Unit) and a communication device. The storage unit 16 is configured with a semiconductor memory, etc. The storage unit 16 also stores a computer program for operating the control unit 15.

[0078] The control unit 15 is capable of communicating with a plurality of battery packs 20 using a communication bus within the vehicle 10 .

[0079] 3 is a diagram showing identification information and the like of the battery pack 20 connected to the moving object 10. In the following tables, the reference numerals in the diagram may be shown as identification information.

[0080] 3 shows the multiple connection ports 12 that the power management system 11 has, the identification information of the battery packs 20 connected to each connection port 12, and information on the management server 40 that manages the battery packs 20. The identification information of the battery packs 20 and the information on the management server 40 are output to the power management system 11 of the mobile object 10 when the battery pack 20 is connected to the mobile object 10, and are stored in the memory unit 16 of the mobile object 10.

[0081] The control unit 15 requests the battery pack 20 for the power required to drive the vehicle 10. That is, the control unit 15 outputs a power request signal, which is a signal requesting power, to the battery pack 20. The power request signal includes battery control information.

[0082] FIG. 4 is a diagram showing an example of battery control information output from the moving object 10. As shown in FIG.

[0083] 4 shows, at each time, the control information output from each connection port 12, i.e., the control information output to each battery pack 20. The figure also shows information related to the battery control value of the battery pack 20 as an example of the control information.

[0084] The battery control value is, for example, the amount of discharge required for the battery pack 20. The control unit 15 calculates each amount of discharge required for each battery pack 20 based on the amount of power expected to be consumed by the mobile object 10. Specifically, this amount of discharge is the amount of discharge per unit time, i.e., the discharge rate. The unit time is, for example, one minute, but is not limited to this and may be appropriately selected from a range of 10 seconds or more and less than 60 seconds.

[0085] The control unit 15 stores battery control information including the battery control value in the storage unit 16. The control unit 15 also outputs a control signal including the battery control information to the battery pack 20.

[0086] [Configuration of Battery Pack] The configuration of the battery pack 20 will be described with reference to FIGS. 5 to 8B.

[0087] FIG. 5 is a diagram showing the configuration of the battery pack 20. As shown in FIG.

[0088] The battery pack 20 is a replaceable battery that is replaceably connected to the mobile object 10. Being replaceably connected means that the battery pack 20 can be removed from the mobile object 10 and another battery pack 20 can be attached to the mobile object 10 without destroying the battery pack 20 and the mobile object 10. The battery pack 20 is shared and used by multiple mobile objects 10.

[0089] When the remaining battery power of the battery pack 20 connected to the mobile object 10 becomes low, the battery pack 20 is removed from the mobile object 10 and replaced with another charged battery pack 20. The battery pack 20 that is removed due to low remaining battery power is attached to the battery station 30 and charged.

[0090] 5 , the battery pack 20 includes a battery 21, a connection port 22, a battery control unit 25, a storage unit 26, and a housing (not shown). The battery 21, the battery control unit 25, and the storage unit 26 are housed in the housing, and the connection port 22 is provided on the surface of the housing. The battery control unit 25 includes a verification unit 25a for verifying the log information of the battery pack 20.

[0091] The battery 21 is a secondary battery and is configured, for example, by one or more battery cells (for example, a lithium-ion battery or an all-solid-state battery). The battery control unit 25 and the storage unit 26 can be driven using the power of the battery 21.

[0092] The connection port 22 is a port connected to the power management system 11 of the mobile object 10. The connection port 22 is, for example, a connector, and is connected to the connection port 12 of the mobile object 10. The battery pack 20 is attachable to and detachable from the mobile object 10 via the connection port 22. The connection port 22 is provided with a terminal for transmitting power and a terminal for transmitting and receiving communication signals (not shown). The battery pack 20 transmits power and transmits and receives communication signals to and from the mobile object 10 via the connection port 22.

[0093] The connection port 22 is also a port that is connected to the battery station 30. The battery pack 20 is attachable to and detachable from the battery station 30 via the connection port 22. The battery pack 20 transmits power and transmits and receives communication signals to and from the battery station 30 via the connection port 22.

[0094] The battery control unit 25 is configured with, for example, a CPU and a communication device. The battery control unit 25 controls the power of the battery 21 based on a control signal output from the control unit 15 of the mobile object 10. The battery control unit 25 also uses a communication bus within the mobile object 10 to communicate with the mobile object 10 or other battery packs 20 different from itself.

[0095] The storage unit 26 is configured by, for example, a semiconductor memory, etc. The storage unit 26 stores a computer program for operating the battery control unit 25.

[0096] The storage unit 26 also stores basic information, control information, and log information of the battery pack 20.

[0097] FIG. 6 is a diagram showing an example of basic information of the battery pack 20. As shown in FIG.

[0098] 6 will be described by taking the battery pack 20a as an example of the plurality of battery packs 20. For example, the basic information of the battery pack 20a includes identification information of the battery pack 20a, information on the management server 40a, and information on the maximum charge capacity and maximum output value of the battery 21 of the battery pack 20a.

[0099] The identification information of the battery pack 20a is a number unique to the battery pack 20a. The identification information of the battery pack 20a may be a physical address or a logical address.

[0100] The information of the management server 40a is identification information of the management server 40a that manages the battery pack 20. The identification information of the management server 40a may be a physical address or a logical address.

[0101] The maximum charge capacity is the maximum power capacity that can be charged into the battery 21. The maximum output value is the maximum power value that the battery 21 can output.

[0102] These pieces of basic information are information that are preset for the battery pack 20. When the battery pack 20 is connected to the mobile object 10, the basic information of the battery pack 20 is output to the power management system 11 of the mobile object 10 and stored in the memory unit 16 of the mobile object 10. The power management system 11 performs battery control based on the basic information of the battery pack 20 stored in the memory unit 16.

[0103] FIG. 7 is a diagram showing an example of control information of the battery 21 stored in the battery pack 20. As shown in FIG.

[0104] The battery control unit 25 stores the control information of the battery 21 output from the power management system 11 of the mobile object 10 in the storage unit 26. The control information of the battery 21 indicates information related to the battery control values ​​of the battery pack 20. In Fig. 7, the battery pack 20a out of the multiple battery packs 20 will be described as an example.

[0105] The battery control value is, for example, the discharge amount of the battery pack 20a. The discharge amount of the battery pack 20a is calculated based on the amount of power that the battery pack 20a will bear out of the amount of power that is planned to be discharged to the vehicle 10. Specifically, this discharge amount is the amount of power discharged per unit time, i.e., the discharge rate. The control information of the battery 21 is used when the battery control unit 25 verifies the log information of the battery pack 20.

[0106] In order to verify the log information of the battery pack 20, the battery control unit 25 acquires the log information as follows.

[0107] The battery control unit 25 outputs a sharing instruction signal for sharing the log information of each of the multiple battery packs 20 with each other. For example, the battery control unit 25 outputs a signal (the above-mentioned sharing instruction signal) to another battery pack 20 different from itself to instruct it to return the log information of the other battery pack 20. The battery control unit 25 inputs and outputs signals to the other battery packs 20 via the communication bus of the power management system 11, and acquires the log information of the other battery packs 20. The battery control unit 25 stores this log information in the storage unit 26. Furthermore, the battery control unit 25 stores the log information of its own battery pack 20 in the storage unit 26 and outputs it to the other battery packs 20.

[0108] 8A is a diagram showing an example of log information of the battery pack 20 stored in the storage unit 26. FIG. 8B is a diagram showing an example of log information of another battery pack 20 stored in the storage unit 26.

[0109] For example, the log information includes information regarding the remaining battery capacity of each of the multiple battery packs 20. The remaining battery capacity is, for example, battery capacity (unit: kWh), but is not limited thereto and may be expressed as a percentage of the maximum charge capacity. Note that the log information includes various information such as time in addition to the remaining battery capacity. The log information also includes part of the control information of the battery 21.

[0110] In this embodiment, the battery pack itself is referred to as a first battery pack, and another battery pack different from the first battery pack is referred to as a second battery pack. For example, if the battery pack 20a itself is referred to as the first battery pack, the other battery packs 20b and 20c are referred to as the second battery packs, if the battery pack 20b itself is referred to as the first battery pack, the other battery packs 20a and 20c are referred to as the second battery packs, and if the battery pack 20c itself is referred to as the first battery pack, the other battery packs 20a and 20b are referred to as the second battery packs.

[0111] 8A and 8B, an example will be described in which the own battery pack is the first battery pack 20a and the other battery packs are the second battery packs 20b and 20c.

[0112] 8A shows information about the remaining battery charge, battery control value, and verification result of the first battery pack 20a at each time point. Also shown in FIG. 8A is identification information for the mobile object 10 to which the first battery pack 20a is connected, and identification information for the second battery packs 20b and 20c simultaneously connected to the mobile object 10.

[0113] 8B shows identification information of the mobile object 10 to which the second battery packs 20b and 20c are connected. In this example, the first battery pack 20a and the second battery packs 20b and 20c are connected to the same mobile object 10. Also, FIG. 8B shows information on the remaining battery capacity, battery control value, and verification result of each of the second battery packs 20b and 20c for each time.

[0114] 8A and 8B, the storage unit 26 of the first battery pack 20a stores log information for its own battery pack 20a and log information for the other battery packs 20b and 20c. The log information for each battery pack 20 is stored in a time-related manner.

[0115] Similarly, the storage unit 26 of the battery pack 20b stores log information for its own battery pack 20b and log information for the other battery packs 20a and 20c. The storage unit 26 of the battery pack 20c stores log information for its own battery pack 20c and log information for the other battery packs 20a and 20b.

[0116] In this embodiment, the plurality of battery packs 20 share their own log information with each other. By sharing the log information of each battery pack 20 in this way, it becomes possible to easily detect, for example, the occurrence of an inconsistency in the log information of a specific battery pack 20.

[0117] The battery control unit 25 shares the log information at a predetermined time interval. The predetermined time interval is, for example, one minute, but is not limited to this and may be selected appropriately from the range of 10 seconds to less than 60 seconds. The predetermined time interval may be shorter than the time interval at which the discharge rate of the battery pack 20 is changed.

[0118] The sharing of the log information is not limited to a sharing instruction signal output from the battery control unit 25, and may be performed based on a control signal output from the power management system 11 of the mobile object 10. For example, in the management system 1, the control unit 15 of the mobile object 10 may be configured to output a control signal to the plurality of battery packs 20 to cause the battery packs 20 to share their log information with each other, and the control signal may trigger the plurality of battery packs 20 to share their log information with each other.

[0119] Furthermore, the battery control unit 25 verifies the log information of the battery pack 20 by using the log information and control information of the battery pack 20. For example, to check whether the log information of the battery pack 20 has been tampered with while the battery pack 20 is connected to the vehicle 10, the verification unit 25a of the battery control unit 25 verifies whether an inconsistency has occurred in the log information of the battery pack 20.

[0120] The verification unit 25a verifies whether there is any inconsistency in the log information by comparing the log information and the control information stored in the storage unit 26. For example, the verification unit 25a verifies the log information of the first battery pack 20a by comparing the remaining battery capacity of the first battery pack 20a with information related to the battery control value of the first battery pack 20a. As described above, the battery control value of the first battery pack 20a is the discharge amount requested for the first battery pack 20a.

[0121] The verification unit 25a compares the remaining battery capacity at each time with the battery control value and checks whether the remaining battery capacity fluctuates according to the battery control value. If there is no inconsistency between the remaining battery capacity and the battery control value, the verification unit 25a determines that the log information is consistent. If there is an inconsistency, the verification unit 25a determines that the log information is inconsistent. In this way, the battery control unit 25 detects whether there is an inconsistency in the log information of the battery pack 20.

[0122] Although the above example shows the first battery pack 20a verifying its own log information, the present invention is not limited to this. The first battery pack 20a verifies the log information of the second battery pack 20b by checking the remaining battery capacity and battery control value of the second battery pack 20b shown in FIG. 8B . Furthermore, the first battery pack 20a verifies the log information of the second battery pack 20c by checking the remaining battery capacity and battery control value of the second battery pack 20c.

[0123] Although the first battery pack 20a has been described above as an example, the second battery packs 20b and 20c are also similarly verified.

[0124] Information indicating that an inconsistency has occurred in the log information of the battery pack 20 is stored as a verification result of the log information in the storage unit 26. In addition, information indicating that an inconsistency has occurred in the log information of the battery pack 20 is also transmitted to the battery station 30 and the management server 40.

[0125] [Configuration of Battery Station] The configuration of the battery station 30 will be described with reference to FIG.

[0126] The battery station 30 is a charging device for charging electricity into the battery pack 20. The battery station 30 is also an information processing device that acquires log information of the battery pack 20 and transfers it to the management server 40.

[0127] A plurality of battery stations 30 are installed, for example, in parking lots of stores, facilities, service areas, etc. The battery stations 30 may be from different service companies or service providers, but by standardizing the battery packs 20, it is possible to charge the battery packs 20 of different companies at each battery station 30.

[0128] FIG. 9 is a diagram showing the configuration of the battery station 30.

[0129] 9, the battery station 30 includes a connection port unit 32, a station control unit 35, and a storage unit 36. A plurality of battery packs 20 are detachably attached to the battery station 30.

[0130] The connection port 32 is a connector connected to the connection port 22 of the battery pack 20. The connection port 32 is provided with a terminal for power transmission and a terminal for transmitting and receiving communication signals. The connection port 32 has the same connector specifications (same number of terminals, same shape) as the connection port 12 of the mobile object 10. The battery station 30 transmits power and transmits and receives communication signals to and from the battery pack 20 via the connection port 32.

[0131] The station control unit 35 is configured with, for example, a CPU and a communication device. The storage unit 36 ​​is configured with, for example, a semiconductor memory. The storage unit 36 ​​also stores a computer program for operating the station control unit 35.

[0132] The log information of the battery pack 20 is output from the battery pack 20 to the battery station 30 when the battery pack 20 is connected to the battery station 30 .

[0133] The station control unit 35 receives the log information from the battery pack 20 via the connection port unit 32 and stores it in the storage unit 36. The storage unit 36 ​​stores the log information of the battery pack 20.

[0134] The station control unit 35 also transmits the log information received from the battery pack 20 to the management server 40. The station control unit 35 also receives information indicating that there is an inconsistency in the log information from the management server 40, and stores the information in the storage unit 36. The information indicating that there is an inconsistency in the log information will be described later.

[0135] [Configuration of Management Server] The configuration of the management server 40 will be described with reference to FIGS. 10 to 12. FIG.

[0136] The management server 40 is a server that manages the battery pack 20. The management server 40 acquires and stores log information of the battery pack 20 via the battery station 30. The management server 40 is installed in a building or facility, but is not limited to this, and may be a cloud server provided on a communication network N. The management server 40 may be managed in a distributed manner by multiple management servers 40a, 40b. The multiple management servers 40a, 40b may be from different service companies or service providers, but are able to share information owned by each other via the communication network N.

[0137] FIG. 10 is a diagram showing the configuration of the management server 40.

[0138] The management server 40 includes an information acquisition unit 43, a server control unit 45, and a storage unit 46. The server control unit 45 includes a verification unit 45a for verifying the log information of the battery pack 20.

[0139] The information acquisition unit 43 is a communication interface for communicating with the battery station 30. The communication method of the information acquisition unit 43 may be, for example, wired communication or wireless communication.

[0140] The server control unit 45 is configured with, for example, a CPU and a communication device. The storage unit 46 is configured with, for example, a semiconductor memory. The storage unit 46 also stores computer programs for operating the server control unit 45 and the information acquisition unit 43.

[0141] The server control unit 45 acquires the log information of the battery pack 20 via the battery station 30 .

[0142] Fig. 11A is a diagram showing an example of first log set information stored in the management server 40. Fig. 11B is a diagram showing an example of second log set information stored in the management server 40. Fig. 11C is a diagram showing another example of second log set information stored in the management server 40.

[0143] 11A to 11C, an example will be described in which the own battery pack is the first battery pack 20a and the other battery packs are the second battery packs 20b and 20c.

[0144] 11A shows information on the remaining battery charge, battery control value, and verification result of the first battery pack 20a for each time. The first log set information also shows identification information of the mobile object 10 to which the first battery pack 20a is connected and the second battery packs 20b and 20c simultaneously connected to the mobile object 10. The identification information of the simultaneously connected battery packs is stored in order to identify the existence of other battery packs that share log information.

[0145] 11A based on the information output from the first battery pack 20a. For example, the information acquiring unit 43 acquires the log information of the first battery pack 20a and the log information of the second battery packs 20b and 20c based on the information output from the first battery pack 20a, i.e., based on the information held by the first battery pack 20a, and acquires the first log set information that is a collection of this log information. The server control unit 45 stores the first log set information acquired by the information acquiring unit 43 in the storage unit 46.

[0146] 11B shows information on the remaining battery capacity, battery control value, and verification result of the second battery pack 20b for each time. The second log set information also shows log information on the mobile object 10 to which the second battery pack 20b is connected, the first battery pack 20a simultaneously connected to the mobile object 10, and the second battery pack 20c.

[0147] 11B based on the information output from the second battery pack 20b. For example, the information acquiring unit 43 acquires the log information of the second battery pack 20b, the log information of the first battery pack 20a, and the log information of the second battery pack 20c based on the information output from the second battery pack 20b, i.e., based on the information held by the second battery pack 20b, and acquires the second log set information that is a collection of these pieces of log information. The server control unit 45 stores the second log set information acquired by the information acquiring unit 43 in the storage unit 46.

[0148] 11C shows information on the remaining battery charge, battery control value, and verification result of the second battery pack 20c for each time. The second log set information also shows log information on the mobile object 10 to which the second battery pack 20c is connected, the first battery pack 20a that is simultaneously connected to the mobile object 10, and the second battery pack 20b.

[0149] 11C based on the information output from the second battery pack 20c. For example, the information acquiring unit 43 acquires the log information of the second battery pack 20c, the log information of the first battery pack 20a, and the log information of the second battery pack 20b based on the information output from the second battery pack 20c, i.e., based on the information held by the second battery pack 20c, and acquires the second log set information that is a collection of these pieces of log information. The server control unit 45 stores the second log set information acquired by the information acquiring unit 43 in the storage unit 46.

[0150] As a result, the memory unit 46 stores first log set information based on battery pack 20a (see Figure 11A), second log set information based on battery pack 20b (see Figure 11B), and second log set information based on battery pack 20c (see Figure 11C).

[0151] By having the management server 40 store the log information of each battery pack 20 in this way, it becomes possible to easily detect, for example, the occurrence of an inconsistency in the log information of a specific battery pack 20 .

[0152] Furthermore, the server control unit 45 verifies the log information of the battery packs 20 using the log information of each battery pack 20. For example, to check whether the log information of the battery packs 20 has been tampered with between the time the battery packs 20 are removed from the vehicle 10 and the time they are returned to the battery station 30, the verification unit 45a of the server control unit 45 verifies whether an inconsistency has occurred in the log information of the battery packs 20.

[0153] The verification unit 45a verifies whether or not there is an inconsistency in the log information by comparing multiple pieces of log information stored in the storage unit 46. For example, the verification unit 45a verifies the log information of the first battery pack 20a by comparing the log information of the first battery pack 20a stored in the first log set information with the log information of the first battery pack 20a stored in the second log set information.

[0154] Specifically, when the log information for the first battery pack 20a included in the first log set information differs from the log information for the first battery pack 20a included in one piece of second log set information, the verification unit 45a determines that the log information for the first battery pack 20a included in the first log set information may be incorrect. Furthermore, when the log information for the first battery pack 20a included in the first log set information differs from the log information for the first battery pack 20a included in two or more pieces of second log set information, the verification unit 45a determines that the log information for the first battery pack 20a included in the first log set information is incorrect. In this way, the verification unit 45a may determine the accuracy of the log information based on the number of matching log information pieces.

[0155] In addition, when verifying the log information of the first battery pack 20a, the verification unit 45a may determine that the log information of the first battery pack 20a is incorrect if the first log set information contains information indicating an inconsistency in the log information of the first battery pack 20a.

[0156] As a result, the management server 40 detects whether or not there is an inconsistency in the log information of the battery pack 20. Note that although the above description has been given using the first battery pack 20a as an example, similar verification is also performed for each of the second battery packs 20b and 20c.

[0157] The server control unit 45 stores information indicating that there is an inconsistency in the log information of the battery pack 20 in the storage unit 46 as a verification result of the log information. The server control unit 45 also outputs information indicating that there is an inconsistency in the log information of the battery pack 20.

[0158] FIG. 12 is a diagram showing an example of the blacklist of the battery pack 20. As shown in FIG.

[0159] 12 shows a blacklist of battery packs 20 indicating that there was an inconsistency in the log information. The server control unit 45 stores this blacklist in the memory unit 46 and displays it on the display of the management server 40. From then on, the management server 40 will not verify log information using battery packs 20 on the blacklist, but will verify log information using battery packs 20 that are not on the blacklist.

[0160] The server control unit 45 also outputs this blacklist to other management servers 40. The server control unit 45 also outputs this blacklist to multiple battery stations 30. In this way, the blacklist is shared among multiple management servers 40 and multiple battery stations 30.

[0161] Each battery station 30 stores the blacklist output from the server control unit 45 in the storage unit 36 ​​and displays it on the display of the battery station 30. The battery station 30 may suspend use of battery packs 20 that are on the blacklist.

[0162] [Operation of Management System] The operation of the management system 1 will be described with reference to FIGS.

[0163] First, the operation when the log information of the battery pack 20 is normal will be described.

[0164] FIG. 13 is a sequence diagram showing an example of the operation of the management system 1 when the log information of the battery pack 20 is normal.

[0165] 13 shows the processing contents of the battery packs 20a to 20c, the mobile object 10, the battery station 30, and the management server 40. In FIG. 13, the processing contents when the battery pack 20a is connected to the mobile object 10 and when the battery pack 20a is removed from the mobile object 10 and connected to the battery station 30 will be described.

[0166] First, the battery pack 20a is connected to the mobile object 10 (S101).

[0167] Next, the mobile object 10 and the battery packs 20a to 20c exchange their respective identification information (S102). Communication for exchanging the identification information is performed using the communication bus of the mobile object 10. As a result of this exchange of identification information, new identification information for the battery pack 20a is stored in the mobile object 10. Furthermore, new identification information for the mobile object 10 and new identification information for the battery packs 20b and 20c are stored in the battery pack 20a. Furthermore, new identification information for the battery pack 20a is stored in each of the battery packs 20b and 20c.

[0168] Next, the mobile object 10 transmits control information to each of the battery packs 20a to 20c (S103). The control information is, for example, a battery control value for each of the battery packs 20a to 20c. The mobile object 10 outputs all of the control information for the battery packs 20 to each of the battery packs 20a to 20c. Note that the mobile object 10 may output each piece of control information that corresponds one-to-one to each of the battery packs 20a to 20c to each of the battery packs 20a to 20c.

[0169] Next, each of the battery packs 20a to 20c collects log information of the other battery packs different from itself (S104).

[0170] For example, battery pack 20a outputs its own log information to other battery packs 20b and 20c, and the other battery packs 20b and 20c that receive this output store the log information of battery pack 20a. Battery pack 20b also outputs its own log information to other battery packs 20a and 20c, and the other battery packs 20a and 20c that receive this output store the log information of battery pack 20b. Battery pack 20c also outputs its own log information to other battery packs 20a and 20b, and the other battery packs 20a and 20b that receive this output store the log information of battery pack 20c. By each battery pack 20 outputting its own log information and storing log information output from others in this way, battery packs 20a to 20c share each other's log information (S105).

[0171] Next, each of the battery packs 20a to 20c verifies the log information of the other battery packs (S106). For example, the battery packs 20a to 20c verify the log information of the battery packs 20a to 20c by comparing the remaining battery capacity and battery control value of the battery packs 20a to 20c. In this example, a verification result indicating that the log information is normal is stored in each of the battery packs 20a to 20c.

[0172] Next, the battery pack 20a is removed from the moving body 10 and connected to the battery station 30 (S107).

[0173] The battery station 30 acquires the log information from the battery pack 20a (S108), and transfers the log information of the battery pack 20a to the management server 40 (S109).

[0174] The management server 40 verifies the log information of the battery pack 20a (S110). The management server 40 performs the verification based on the verification result stored in the battery pack 20a, and stores information indicating that the log information of the battery pack 20a is normal in the storage unit 46. The management server 40 may also perform a new verification using the remaining battery capacity and battery control value of the battery pack 20a, and store the verification result in the storage unit 46.

[0175] This allows the management server 40, the battery station 30, and the battery packs 20a to 20c to share the fact that the log information of the battery pack 20a is normal.

[0176] Although the above description has been given using the battery pack 20a as an example, the same processing is performed when the battery packs 20b and 20c are connected to the mobile body 10 and when they are connected to the battery station 30.

[0177] Next, a description will be given of the operation when there is an inconsistency in the log information of the battery pack 20. In this example, an example will be described in which an inconsistency occurs in the log information when the battery pack 20 is connected to the mobile object 10.

[0178] FIG. 14 is a sequence diagram showing an example of the operation of the management system 1 when there is an inconsistency in the log information of the battery pack 20.

[0179] 14 shows the processing contents of the battery packs 20a to 20c, the mobile object 10, the battery station 30, and the management server 40. Also in FIG. 14, the processing contents when the battery pack 20a is connected to the mobile object 10 and when the battery pack 20a is removed from the mobile object 10 and connected to the battery station 30 will be described.

[0180] The processing contents of steps S101 to S104 are the same as those in FIG.

[0181] In this example, when the battery pack 20a is connected to the mobile object 10, the log information of the battery pack 20a is tampered with (S201).

[0182] Next, in a state where the log information of the battery pack 20a has been tampered with, the battery packs 20a to 20c share their log information with each other (S202).

[0183] Next, the battery packs 20a to 20c verify each other's log information (S203).

[0184] For example, the battery packs 20a to 20c verify the log information of the battery packs 20a to 20c by checking the remaining battery capacity and the battery control value of the battery packs 20a to 20c.

[0185] FIG. 15 is a diagram illustrating an example of log information having an inconsistency.

[0186] 15(a) shows the remaining battery power of each of the battery packs 20a to 20c held by the battery pack 20a, and FIG. 15(b) shows the battery control value of each battery pack 20. In FIG. 15(b), the battery control value of the battery pack 20a at times 10:02 and 10:03 is 0 kWh / min, whereas in FIG. 15(a), the remaining battery power of the battery pack 20a at times 10:02 and 10:03 is reduced. Therefore, each of the battery packs 20a to 20c determines that there is an inconsistency in the log information of the battery pack 20a.

[0187] In this example, a verification result indicating that there is an inconsistency in the log information of the battery pack 20a is stored in each of the battery packs 20a to 20c (S204).

[0188] Next, the battery pack 20a is removed from the moving object 10 and connected to the battery station 30 (S205).

[0189] The battery station 30 acquires the log information from the battery pack 20a and transfers the log information to the management server 40 (S206). The log information includes a verification result indicating that there is an inconsistency in the log information of the battery pack 20a.

[0190] The management server 40 verifies the log information of the battery pack 20a again with reference to the above verification result (S207). The management server 40 performs verification using the remaining battery capacity and battery control value of the battery pack 20a, and determines that the log information of the battery pack 20a is incorrect (S208).

[0191] The management server 40 lists the battery packs 20a whose log information has been determined to be incorrect, and creates a blacklist that includes the battery packs 20a (S209).The management server 40 then outputs the blacklist to the other management servers 40 and the battery station 30 (S210).

[0192] This allows information indicating that the log information of the battery pack 20a is incorrect to be shared between the management server 40 and the battery station 30. This makes it possible, for example, to suspend use of the battery pack 20a whose log information is incorrect.

[0193] Next, a description will be given of another example of the operation when there is an inconsistency in the log information of the battery pack 20. In this example, an example will be described in which an inconsistency in the log information occurs between the time when the battery pack 20 is removed from the mobile object 10 and the time when the battery pack 20 is connected to the battery station 30.

[0194] FIG. 16 is a sequence diagram showing another example of the operation of the management system 1 when there is a mismatch in the battery pack 20. In FIG.

[0195] 16 shows the processing contents of the battery packs 20a to 20c, the mobile object 10, the battery station 30, and the management server 40. Also in FIG. 16, the processing contents when the battery pack 20a is connected to the mobile object 10 and when the battery pack 20a is removed from the mobile object 10 and connected to the battery station 30 will be described.

[0196] The processing contents of steps S101 to S106 are the same as those in FIG.

[0197] In this example, the log information is tampered with between the time when the battery pack 20a is removed from the moving object 10 and the time when the battery pack 20a is connected to the battery station 30 (S301).

[0198] Then, the battery pack 20a whose log information has been tampered with is connected to the battery station 30 (S302). The battery station 30 acquires the log information from the battery pack 20a and transfers the log information to the management server 40 (S303). The management server 40 verifies the log information of the battery pack 20a (S304).

[0199] Furthermore, the battery pack 20b is removed from the vehicle 10 and connected to the battery station 30 (S305). The battery station 30 acquires log information from the battery pack 20b and transfers the log information to the management server 40 (S306). The management server 40 verifies the log information of the battery pack 20b (S307). If the log information of the battery pack 20a output from the battery pack 20a differs from the log information of the battery pack 20a output from the battery pack 20b, the management server 40 determines that the log information of the battery pack 20a may be incorrect and detects an abnormality (S308).

[0200] Furthermore, battery pack 20c is removed from vehicle 10 and connected to battery station 30 (S309). Battery station 30 acquires log information from battery pack 20c and transfers the log information to management server 40 (S310). Management server 40 verifies the log information of battery pack 20c (S311). If the log information of battery pack 20a output from battery pack 20a differs from the log information of battery pack 20a output from battery packs 20b and 20c, management server 40 determines that the log information of battery pack 20a is incorrect (S312).

[0201] FIG. 17 is a diagram illustrating another example of log information having an inconsistency.

[0202] (a) of Figure 17 shows information regarding the remaining battery capacity of battery packs 20a to 20c held by battery pack 20a, (b) shows information regarding the remaining battery capacity of battery packs 20a to 20c held by battery pack 20b, and (c) shows information regarding the remaining battery capacity of battery packs 20a to 20c held by battery pack 20c.

[0203] 17(b) and (c), the remaining battery charge of battery pack 20a is 50 kWh at times 10:02 and 10:03, whereas in FIG. 17(a), the remaining battery charge of battery pack 20a is less than 50 kWh at times 10:02 and 10:03. In this example, two battery packs have a remaining battery charge of 50 kWh and one battery pack has a remaining battery charge of less than 50 kWh, so management server 40 determines that the information held by battery packs 20b and 20c is more accurate than that of battery pack 20a. Then, management server 40 determines that the information held by battery pack 20a regarding the remaining battery charge of battery pack 20a is incorrect.

[0204] The management server 40 lists the battery packs 20a whose log information has been determined to be incorrect, and creates a blacklist that includes the battery packs 20a (S313).The management server 40 then outputs the blacklist to the other management servers 40 and the battery station 30 (S314).

[0205] This allows information indicating that the log information of the battery pack 20a is incorrect to be shared among multiple management servers 40 and multiple battery stations 30. This makes it possible, for example, to suspend use of a battery pack 20a with incorrect log information.

[0206] [Operation of Battery Pack] The operation of the battery pack 20 will be described with reference to FIGS.

[0207] FIG. 18 is a flowchart showing an example of the operation of the battery pack 20 when acquiring log information.

[0208] 18, the battery packs 20 exchange identification information (S401). The battery packs 20 recognize other battery packs 20 connected to the moving object 10 by performing processing related to the identification information.

[0209] Next, the battery pack 20 controls the battery 21 in accordance with the control information output from the moving object 10 (S402).

[0210] Next, the battery pack 20 acquires log information of its own battery pack 20 and log information of the other battery packs 20 (S403). Each battery pack 20 saves the log information acquired in step S403, thereby sharing the log information of the multiple battery packs 20 connected to the mobile object 10 (S404).

[0211] The battery pack 20 repeatedly executes these steps S401 to S404 while the battery pack 20 is connected to the mobile object 10. This allows a plurality of battery packs 20 to share each other's log information.

[0212] FIG. 19 is a flowchart showing an example of the operation of the battery pack 20 when acquiring identification information.

[0213] 19, the battery packs 20 exchange identification information (S401). The battery packs 20 recognize other battery packs 20 connected to the moving object 10 by performing processing related to the identification information.

[0214] Next, the battery pack 20 determines whether or not it is a battery pack 20 that has been newly connected to the moving object 10 (S501).

[0215] If it is a newly connected battery pack 20 (Yes in S501), it transmits its own identification information to the other battery packs 20 (S502).

[0216] On the other hand, if the battery pack 20 is not a newly connected battery pack (No in S501), it is determined whether or not identification information has been received from another battery pack 20 (S503).

[0217] If the identification information has not been received from another battery pack 20 (No in S503), the battery pack 20 does not need to transmit the identification information again, and therefore ends this flow.

[0218] On the other hand, if the identification information has been received from another battery pack 20 (Yes in S503), the battery pack 20 determines whether or not its own identification information has been transmitted to the other battery pack 20 (S504).

[0219] If the battery pack 20 has already transmitted its own identification information (Yes in S504), the battery pack 20 does not need to transmit its identification information again, and therefore ends this flow.

[0220] On the other hand, if its own identification information has not been transmitted (No in S504), the process proceeds to step S502, and its own identification information is transmitted to the other battery packs 20 (S502).

[0221] By executing these steps S401 and S501 to S504, a plurality of battery packs 20 can share each other's identification information.

[0222] FIG. 20 is a flowchart showing an example of the operation of the battery pack 20 when sharing log information.

[0223] As shown in FIG. 20, the battery packs 20 share each other's log information by executing S401 to S404.

[0224] Next, the battery pack 20 determines whether there is another battery pack 20 connected to the same moving object 10 (S601).

[0225] If there are no other battery packs 20 (No in S601), there is no need to share the log information, and this flow ends.

[0226] If another battery pack 20 exists (Yes in S601), the battery pack 20 transmits its own log information to the other battery pack 20 (S602). Also, the battery pack 20 acquires log information output from the other battery pack 20 (S603).

[0227] Then, the battery pack 20 compares the log information with the control information (S604). For example, the battery pack 20 compares the remaining battery capacity with the battery control value.

[0228] Next, the battery pack 20 determines whether the comparison result is within a predetermined threshold value (S605). Specifically, the battery pack 20 determines whether the difference between the remaining battery charge and the battery control value is within a predetermined threshold value.

[0229] If the difference between the remaining battery capacity and the battery control value is within the threshold (Yes in S605), the battery pack 20 outputs information indicating that the log information is normal (S606).If the difference between the remaining battery capacity and the battery control value is not within the threshold (No in S605), the battery pack 20 outputs information indicating that the log information is abnormal (S607).

[0230] By executing these steps S401 to S404 and S601 to S607, it is possible to verify whether the log information of the battery pack 20 is normal.

[0231] [Operation of Battery Station] The operation of the battery station 30 will be described with reference to FIG.

[0232] FIG. 21 is a flowchart showing an example of the operation of the battery station 30.

[0233] First, the battery pack 20 is connected to the battery station 30 (S701).

[0234] Next, the battery station 30 acquires log information held by the battery pack 20 (S702). Then, the battery station 30 transmits the log information acquired from the battery pack 20 to the management server 40 (S703). At this time, the battery station 30 transmits the log information held by the battery pack 20a to the management server 40a that manages the battery pack 20a, transmits the log information held by the battery pack 20b to the management server 40a that manages the battery pack 20b, and transmits the log information held by the battery pack 20c to the management server 40b that manages the battery pack 20c.

[0235] If the management server 40 determines that there is an inconsistency in the log information, the battery station 30 obtains a blacklist of battery packs 20 from the management server 40. The battery station 30 suspends use of the battery packs 20 that are on the blacklist. This makes it possible to prevent the distribution of battery packs 20 with incorrect log information.

[0236] [Operation of Management Server] The basic operation of the management server 40 will be described with reference to FIG.

[0237] FIG. 22 is a flowchart showing the basic operation of the management server 40.

[0238] 22 , the management server 40 acquires log information of the battery packs 20 from the battery station 30 (S800). Next, the management server 40 verifies the log information of the battery packs 20 (S900). Next, the management server 40 lists the battery packs 20 whose log information is inconsistent, and creates a blacklist that includes the battery packs 20 (S1000).

[0239] Here, the processing content of step S900 will be described in detail.

[0240] FIG. 23 is a diagram showing in detail a part of the basic operation shown in FIG.

[0241] The management server 40 executes the following process to perform the verification in step S900.

[0242] The management server 40 determines whether the log information of the battery pack 20 held by a battery pack 20 and the log information of the battery pack 20 held by another battery pack 20 are from the same time (S901). If the log information is not from the same time (No in S901), the log information cannot be verified, and the flow ends.

[0243] On the other hand, if the log information exists at the same time (Yes in S901), the management server 40 compares these pieces of log information (S902) and determines whether there is a difference between the pieces of log information (S903).

[0244] If there is no difference in the log information (No in S903), it is determined that the log information is normal (S907).

[0245] If there is a difference in the log information (Yes in S903), it is determined whether the number of different pieces of log information among the two or more other battery packs 20 accounts for a majority of the total (S904). If the number of different pieces of log information accounts for a majority of the total (Yes in S904), it is determined that the log information of the specified battery pack 20 held by the specified battery pack 20 is abnormal (S905). The management server 40 stores the determination result that the log information of the specified battery pack 20 is abnormal in the storage unit 46.

[0246] On the other hand, if the number of different pieces of log information is not a majority of the total (No in S904), it is determined that there is a possibility of an abnormality in the log information of the specified battery pack 20 held by the specified battery pack 20 (S906). The management server 40 stores in the storage unit 46 the determination result that the log information of the specified battery pack 20 is a log that requires caution.

[0247] Next, the processing content of step S1000 will be described in detail.

[0248] FIG. 24 is a diagram showing in detail another part of the basic operation shown in FIG.

[0249] The management server 40 executes the following process to perform the verification in step S1000.

[0250] The management server 40 counts the number of times an abnormality has occurred in a specific battery pack 20 (S1001). The number of times an abnormality has occurred is the number of times an abnormality has occurred in the specific battery pack 20 from when the specific battery pack 20 was connected to the mobile object 10 until when the specific battery pack 20 was removed from the mobile object 10. The number of times an abnormality has occurred is counted up by one each time an abnormality has occurred, and is stored in the storage unit 46 of the management server 40.

[0251] Next, the management server 40 determines whether the number of abnormality occurrences is equal to or greater than the threshold value (S1002). If the number of abnormality occurrences is not equal to or greater than the threshold value (No in S1002), the management server 40 ends this flow.

[0252] On the other hand, if the number of abnormality occurrences is equal to or greater than the threshold value (Yes in S1002), the management server 40 determines that the specified battery pack 20 is an unauthorized battery pack and creates a blacklist (S1003). The management server 40 outputs the blacklist to other management servers 40 and the battery station 30 (S1004). Note that the management server 40 will not use the battery pack 20 on the blacklist to verify log information in the future, but will verify log information using a battery pack 20 that is not on the blacklist.

[0253] This allows information indicating that a specific battery pack 20 is an unauthorized battery pack to be shared between the management server 40 and the battery station 30. This allows the unauthorized battery pack 20 to be suspended from use.

[0254] Second Embodiment A management system 1A according to a second embodiment will be described with reference to Fig. 25 to Fig. 29. In the second embodiment, an example will be described in which, when mobile objects 10 are in a parking state, the mobile objects 10 share log information with each other.

[0255] Fig. 25 is a diagram showing the overall configuration of a management system 1A according to embodiment 2. Fig. 26 is a diagram showing a power management system 11 and a battery pack 20 provided in a moving object 10.

[0256] As shown in FIG. 25, the management system 1A includes a plurality of battery packs 20, a plurality of battery stations 30, and a plurality of management servers 40.

[0257] The configurations of the battery pack 20, the battery station 30, and the management server 40 are the same as those in the first embodiment. The configuration of the mobile object 10 is also substantially the same as that in the first embodiment, but in the second embodiment, the mobile object 10 includes a shift state acquisition unit 14.

[0258] The shift state acquisition unit 14 acquires information indicating whether the mobile object 10 is in a parking state. For example, when the mobile object 10 is in drive, reverse, or neutral, it is not in a parking state, and when the mobile object 10 is in a state other than drive, reverse, or neutral and the parking brake is applied, it is in a parking state.

[0259] In this embodiment, when the shift state acquisition unit 14 acquires information indicating that the vehicle 10 is in the parking state from the vehicle 10, a predetermined battery pack 20 acquires log information of the other battery packs 20 output from the other battery packs 20, and outputs the log information of the predetermined battery pack 20 to the other battery packs 20. In this way, the log information of the plurality of battery packs 20 is shared with each other.

[0260] FIG. 27 is a sequence diagram showing an example of the operation of the management system 1A.

[0261] First, the battery pack 20a is connected to the mobile object 10 (S101).

[0262] Next, the mobile object 10 and the battery packs 20a to 20c exchange their respective identification information (S102).

[0263] For example, when the vehicle 10 is in the drive state (D) (S102A), the vehicle 10 outputs control information for the battery 21 to each of the battery packs 20a to 20c (S102B). However, since the vehicle 10 is not in the parking state (P), each of the battery packs 20a to 20c does not acquire or share log information.

[0264] On the other hand, when the mobile body 10 is in a parking state (P) (S102C), the mobile body 10 outputs control information for the battery 21 to each battery pack 20a to 20c, and also outputs information indicating that the mobile body 10 is in a parking state to each battery pack 20a to 20c (S103A).

[0265] FIG. 28 is a diagram showing an example of control information for the battery 21 output from the moving object 10. In FIG.

[0266] 28 shows the control information output from each connection port 12 at each time. The figure also shows, as an example of the control information, information related to the battery control value of the battery pack 20. Furthermore, in the second embodiment, the control information includes information indicating whether the vehicle 10 is in a parking state.

[0267] After step S103, each battery pack 20a to 20c collects log information from the other battery packs (S104). Each battery pack 20 outputs its own log information and stores log information output from others, allowing the battery packs 20a to 20c to share each other's log information (S105). The subsequent processing is the same as that shown in FIG. 13 of the first embodiment.

[0268] FIG. 29 is a flowchart showing an example of the operation of the battery pack.

[0269] First, the battery pack 20 exchanges identification information (S401), and then the battery pack 20 controls the battery 21 in accordance with the control information output from the moving object 10 (S402).

[0270] In the second embodiment, when the moving object 10 is in a parking state, the battery pack 20 acquires log information of its own battery pack 20 and log information of the other battery packs 20 (S403A). Then, each battery pack 20 saves the log information acquired in step S403A, thereby sharing the log information of the multiple battery packs 20 connected to the moving object 10 (S404).

[0271] In this way, when the mobile objects 10 are in the parking state, the log information is shared with each other, thereby reducing the number of times the log information is shared and the amount of power consumption required for sharing the log information. Furthermore, when the mobile objects 10 are in the driving state, where power is likely to be tight, the log information is not shared, thereby reducing power consumption.

[0272] (Embodiment 3) A management system 1B according to embodiment 3 will be described with reference to Fig. 30 to Fig. 36. In embodiment 3, an example will be described in which each battery pack 20 acquires and shares each other's log information using short-range wireless communication.

[0273] Fig. 30 is a diagram showing the overall configuration of a management system 1B according to embodiment 3. Fig. 31 is a diagram showing a power management system 11 and a battery pack 20 provided in a moving object 10. Fig. 32 is a diagram showing the configuration of the battery pack 20.

[0274] As shown in FIG. 30 , the management system 1B includes a plurality of battery packs 20 , a plurality of battery stations 30 , and a plurality of management servers 40 .

[0275] The configurations of the battery station 30 and the management server 40 are the same as those in embodiment 1. The configuration of the moving object 10 is also the same as that in embodiment 1. In embodiment 3, as shown in Fig. 32 , the battery control unit 25 of the battery pack 20 includes a wireless communication unit 25b.

[0276] The communication method used by the wireless communication unit 25b is short-range wireless communication (for example, Wi-Fi (registered trademark), Bluetooth (registered trademark) communication).

[0277] FIG. 33 is a diagram showing identification information etc. of the battery pack 20 connected to the moving object 10.

[0278] 33 shows the multiple connection ports 12 that the power management system 11 has, the identification information of the battery packs 20 connected to each connection port 12, and information on the management server 40 that manages the battery packs 20. Furthermore, Fig. 33 shows whether each battery pack 20 has a wireless function.

[0279] Each battery pack 20 checks the wireless function of each battery pack 20 based on the identification information shown in Fig. 33. Log information is shared through wireless communication with battery packs 20 that have wireless functionality. Note that if the battery pack 20 does not have wireless functionality, it may acquire and share log information via the connection port 22 shown in the first embodiment.

[0280] In this embodiment, a predetermined battery pack 20 acquires log information of other battery packs 20 output from the other battery packs 20 using short-range wireless communication, and outputs the log information of the predetermined battery pack 20 to the other battery packs 20. In this way, the log information of the plurality of battery packs 20 is shared with each other.

[0281] FIG. 34 is a sequence diagram showing an example of the operation of the management system 1B.

[0282] First, the battery pack 20a is connected to the mobile object 10 (S101).

[0283] Next, the mobile object 10 and the battery packs 20a to 20c exchange their respective identification information (S102).

[0284] Based on the exchanged identification information, the battery packs 20a to 20c establish wireless connections with each other that have wireless communication capabilities (S102H).

[0285] The mobile object 10 outputs the control information of the battery 21 to each of the battery packs 20a to 20c (S103).

[0286] Next, each battery pack 20a to 20c wirelessly collects log information from the other battery packs (S104). Each battery pack 20 outputs its own log information and stores log information output from others, allowing the battery packs 20a to 20c to share each other's log information (S105). The subsequent processing is the same as that shown in FIG. 13 of the first embodiment.

[0287] FIG. 35 is a flowchart showing an example of the operation of the battery pack when acquiring log information.

[0288] As shown in FIG. 35, the battery packs 20 exchange identification information (S401).

[0289] Next, the battery pack 20 controls the battery 21 in accordance with the control information output from the moving object 10 (S402).

[0290] Next, the battery pack 20 acquires log information of its own battery pack 20 and log information of the other battery packs 20 (S403B). In the third embodiment, the battery pack 20 acquires the log information of the other battery packs 20 through wireless communication. Each battery pack 20 saves the log information acquired in step S403B, thereby sharing the log information of the multiple battery packs 20 connected to the mobile object 10 (S404).

[0291] The battery pack 20 repeatedly executes these steps S401 to S404 while the battery pack 20 is connected to the mobile object 10. This allows a plurality of battery packs 20 to share each other's log information.

[0292] FIG. 36 is a flowchart showing an example of the operation of the battery pack 20 when acquiring identification information.

[0293] Note that the communications in steps S501 to S504 shown below are performed by wired communications using a communications bus, and the processes from step S510 onwards are performed by wireless communications.

[0294] As shown in FIG. 36, the battery packs 20 exchange identification information (S401).

[0295] Next, the battery pack 20 determines whether or not it is a battery pack 20 that has been newly connected to the moving object 10 (S501).

[0296] If it is a newly connected battery pack 20 (Yes in S501), it transmits its own identification information to the other battery packs 20 (S502).

[0297] On the other hand, if the battery pack 20 is not a newly connected battery pack (No in S501), it is determined whether or not identification information has been received from another battery pack 20 (S503).

[0298] If the identification information has not been received from another battery pack 20 (No in S503), the battery pack 20 ends this flow.

[0299] On the other hand, if the identification information has been received from another battery pack 20 (Yes in S503), the battery pack 20 determines whether or not its own identification information has been transmitted to the other battery pack 20 (S504).

[0300] If its own identification information has already been transmitted (Yes in S504), the battery pack 20 ends this flow.

[0301] On the other hand, if its own identification information has not been transmitted (No in S504), the process proceeds to step S502, and its own identification information is transmitted to the other battery packs 20 (S502).

[0302] Next, the battery pack 20 determines whether or not there is an unconnected wireless-compatible battery pack 20 (S510).

[0303] If there is no unconnected wireless-compatible battery pack 20 (No in S510), the battery pack 20 ends this flow.

[0304] If there is an unconnected wireless-compatible battery pack 20 (Yes in S510), the battery pack 20 wirelessly connects to that battery pack 20 (S511). After that, the wirelessly connected battery packs 20 share log information and the like with each other.

[0305] In this way, by acquiring and sharing log information using short-range wireless communication, it becomes difficult for the mobile object 10 to tamper with the log information.

[0306] (Other Embodiments) While the battery pack management method according to one or more aspects has been described above based on the first, second, and third embodiments, the present disclosure is not limited to these embodiments, etc. As long as it does not deviate from the spirit of the present disclosure, various modifications conceivable by a person skilled in the art to the present embodiments and embodiments constructed by combining components of different embodiments may also be included in the present disclosure.

[0307] Although the above example shows that the blacklist of battery packs 20 is shared by multiple management servers 40 and multiple battery stations 30, this is not limiting. For example, if the mobile object 10 and the management server 40 have cellular wireless communication devices, the blacklist of battery packs 20 may be transmitted to the mobile object 10 by wireless communication. In other words, information regarding the blacklist of battery packs 20 may also be shared with the mobile object 10.

[0308] Furthermore, the management server in each of the above embodiments is realized as a hardware configuration including a non-volatile memory in which a program is stored, a volatile memory that is a temporary storage area for executing the program, an input / output port, a communication interface, and a processor that executes the program. Each component of the management server is realized by a processor that executes the program stored in the memory. The management server may be realized by a stationary personal computer (PC), a mobile terminal such as a smartphone or tablet, a dedicated computer, or a server (e.g., a cloud server), or a combination thereof.

[0309] Each component may be configured with dedicated hardware, or may be realized by executing a software program suitable for that component. Each component may be realized by a program execution unit such as a CPU or processor reading and executing a software program recorded on a recording medium such as a hard disk or semiconductor memory.

[0310] The order in which the steps in the flowchart are executed is merely an example for specifically explaining the present disclosure, and other orders may be used. Some of the steps may be executed simultaneously (in parallel) with other steps, or some of the steps may not be executed.

[0311] The division of functional blocks in the block diagram is an example, and multiple functional blocks may be realized as a single functional block, one functional block may be divided into multiple blocks, or some functions may be moved to another functional block.Furthermore, the functions of multiple functional blocks having similar functions may be processed in parallel or in time-sharing by a single piece of hardware or software.

[0312] Furthermore, the management server according to each of the above embodiments may be realized as a single device or may be realized by multiple devices. When the management server is realized by multiple devices, the components of the management server may be distributed in any manner among the multiple devices. When the management server is realized by multiple devices, the communication method between the multiple devices is not particularly limited, and may be wireless communication or wired communication. Furthermore, wireless communication and wired communication may be combined between the devices.

[0313] Furthermore, each component described in the above embodiments may be implemented as software or, typically, as an LSI, which is an integrated circuit. These components may be individually integrated into a single chip, or some or all of them may be integrated into a single chip. While the term "LSI" is used here, it may also be referred to as an IC, system LSI, super LSI, or ultra LSI depending on the level of integration. Furthermore, the integrated circuit implementation is not limited to LSIs; it may also be implemented using dedicated circuits (general-purpose circuits that execute dedicated programs) or general-purpose processors. Field programmable gate arrays (FPGAs), which can be programmed after LSI fabrication, or reconfigurable processors, which allow the connection or settings of circuit cells within an LSI to be reconfigured, may also be used. Furthermore, if an integrated circuit implementation technology that replaces LSIs emerges due to advances in semiconductor technology or other derivative technologies, that technology may naturally be used to integrate the components.

[0314] A system LSI is an ultra-multifunctional LSI manufactured by integrating multiple processing units on a single chip. Specifically, it is a computer system that includes a microprocessor, ROM (Read Only Memory), RAM (Random Access Memory), etc. Computer programs are stored in the ROM. The system LSI achieves its functions when the microprocessor operates in accordance with the computer program.

[0315] Furthermore, one aspect of the present disclosure may be a computer program that causes a computer to execute each of the characteristic steps included in the battery pack management method.

[0316] Furthermore, for example, the program may be a program to be executed by a computer. Another aspect of the present disclosure may be a computer-readable non-transitory recording medium on which such a program is recorded. For example, such a program may be recorded on a recording medium and distributed or circulated. For example, the distributed program may be installed in a device having another processor, and the program may be executed by the processor, thereby causing the device to perform each of the above processes.

[0317] The present disclosure is useful for a management method for a replaceable battery that manages log information of the replaceable battery, and the like.

[0318] 1, 1A, 1B Management system 10 Mobile body 11 Power management system 12, 12a, 12b, 12c Connection port unit 14 Shift status acquisition unit 15 Control unit 16 Storage unit 20, 20a, 20b, 20c Battery pack 21 Battery 22 Connection port unit 25 Battery control unit 25a Verification unit 25b Wireless communication unit 26 Storage unit 30, 30a, 30b Battery station 32 Connection port unit 35 Station control unit 36 ​​Storage unit 40, 40a, 40b Management server 43 Information acquisition unit 45 Server control unit 45a Verification unit 46 Storage unit

Claims

1. A method for managing battery packs that are replaceably connected to a mobile body, the method comprising storing log information of a first battery pack among a plurality of battery packs connected to the mobile body, and log information of at least one second battery pack different from the first battery pack, in a memory unit of the first battery pack.

2. A battery pack management method as described in claim 1, wherein the log information of the second battery pack output from the second battery pack is acquired before storing the log information of the second battery pack in the memory unit.

3. The battery pack management method according to claim 2, further comprising outputting log information of the first battery pack to the second battery pack.

4. A battery pack management method according to any one of claims 1 to 3, wherein the log information of the first battery pack includes information relating to the remaining battery capacity of the first battery pack, and the log information of the second battery pack includes information relating to the remaining battery capacity of the second battery pack.

5. The battery pack management method according to claim 4, further comprising verifying the log information of the first battery pack by comparing the remaining battery capacity of the first battery pack with information relating to the battery control value of the first battery pack.

6. The battery pack management method according to claim 5, wherein the battery control value of the first battery pack is a discharge amount required for the first battery pack.

7. A battery pack management method as described in claim 3, wherein when the mobile body is in a parked state, log information of the second battery pack output from the second battery pack is acquired, and log information of the first battery pack is output to the second battery pack.

8. A battery pack management method as described in claim 3, wherein log information of the second battery pack output from the second battery pack is acquired using short-range wireless communication, and log information of the first battery pack is output to the second battery pack.

9. A method for managing battery packs that are replaceably connected to a mobile body, the method comprising storing, in a management server, log information of a first battery pack among a plurality of battery packs connected to the mobile body, and log information of at least one second battery pack different from the first battery pack.

10. The battery pack management method described in claim 9, wherein the management server: acquires first log set information including log information of the first battery pack and log information of at least one of the second battery packs based on information output from the first battery pack; acquires second log set information including log information of the first battery pack and log information of at least one of the second battery packs based on information output from the second battery pack; and stores the first log set information and the second log set information in a memory unit of the management server.

11. The battery pack management method according to claim 10, further comprising verifying log information of the first battery pack.

12. A battery pack management method as described in claim 11, wherein when verifying the log information of the first battery pack, if the first log set information includes information indicating that the log information of the first battery pack is inconsistent, it is determined that the log information of the first battery pack is incorrect.

13. A battery pack management method as described in claim 11, wherein when verifying the log information of the first battery pack, the log information of the first battery pack contained in the first log set information is compared with the log information of the first battery pack contained in the second log set information to verify the log information.

14. A battery pack management method as described in claim 13, wherein if the log information of the first battery pack included in the first log set information differs from the log information of the first battery pack included in two or more pieces of second log set information, it is determined that the log information of the first battery pack included in the first log set information is incorrect.

15. A battery pack management method as described in claim 12 or 14, further comprising, if it is determined that the log information of the first battery pack is incorrect, outputting information indicating that there is fraud in the log information of the first battery pack.

16. A battery pack management method as described in claim 12 or 14, further comprising, if it is determined that the log information of the first battery pack is incorrect, listing the first battery pack and creating a blacklist including the first battery pack.

17. The battery pack management method according to claim 16, further comprising suspending use of the first battery pack included in the blacklist.

18. A battery pack that is replaceably connected to a mobile body, comprising: a battery; and a memory unit that stores information about the battery pack, wherein the memory unit stores log information about the battery pack itself and log information about other battery packs different from the battery pack itself, among a plurality of battery packs connected to the mobile body.

19. A management server that manages battery packs that are replaceably connected to a mobile body, comprising: an information acquisition unit that acquires log information of a first battery pack among a plurality of battery packs connected to the mobile body, and log information of at least one second battery pack different from the first battery pack; and a memory unit that stores the log information of the first battery pack and the log information of at least one of the second battery packs.

20. A management system comprising: a plurality of battery packs that are interchangeably connected to a mobile object; and a management server that manages the plurality of battery packs, wherein the plurality of battery packs share their respective log information among themselves.

21. A program for causing a computer to execute the battery pack management method according to any one of claims 1 to 3.

22. A program for causing a computer to execute the battery pack management method according to any one of claims 9 to 14.

Images