Method for using battery pack, charging device, and program

Abstract

Provided is a method for using a battery pack (20) that is replaceably connected to a mobile body (10), wherein firmware of the battery pack (20) is reinstalled when the battery pack (20) is connected to a charging device (30) and charged.

Description

Battery pack usage method, charging device and program

[0001] The present disclosure relates to a method for using a battery pack, a charging device, and a program.

[0002] 2. Description of the Related Art Electrically driven vehicles are known. As a battery for an electric vehicle, a battery pack that is replaceably connected to the electric vehicle has attracted attention.

[0003] Patent Document 1 discloses a battery pack that, when attached to an electric vehicle, can smoothly communicate with the vehicle or be connected to a power source.

[0004] Patent No. 7315144

[0005] For example, the firmware of a battery pack can become infected with malware. If you continue to use a battery pack that is infected with malware, it may cause malfunctions in the battery pack.

[0006] The present disclosure provides a method for using a battery pack that can prevent malfunctions from occurring in the battery pack.

[0007] A method of using a battery pack according to one aspect of the present disclosure is a method of using a battery pack that is replaceably connected to a mobile object, and when the battery pack is connected to a charging device and charged, the firmware of the battery pack is reinstalled.

[0008] A charging device according to one aspect of the present disclosure is a charging device for charging a battery of a battery pack that is replaceably connected to a mobile body, and includes a charging instruction unit that instructs charging of the battery, and an installation unit that installs firmware into the battery pack, and the installation unit reinstalls the firmware into the battery pack when the battery is being charged in accordance with the instructions of the charging instruction unit.

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

[0010] According to the method of using the battery pack of the present disclosure, malfunctions in the battery pack can be suppressed.

[0011] FIG. 1 is a block diagram of a battery pack, a charging device, an authentication server, and a distribution server included in a management system according to a first embodiment. FIG. 2 is a diagram showing a mobile object and a battery pack connected to the mobile object. FIG. 3 is a block diagram of the battery pack. FIG. 4 is a diagram showing basic information about the battery pack. FIG. 5 is a diagram showing authentication information about the battery pack registered in the authentication server. FIG. 6 is a diagram showing information about firmware held by the distribution server. FIG. 7 is a diagram showing a charging device and a battery pack connected to the charging device. FIG. 8 is a diagram showing authentication information about the battery pack and information about firmware held by the charging device. FIG. 9 is a diagram showing the operation of the management system according to the first embodiment. FIG. 10 is a diagram showing new authentication information created by the authentication server according to a first variation of the first embodiment. FIG. 11 is a diagram showing the operation of the management system according to the first variation of the first embodiment. FIG. 12 is a diagram showing the operation of the management system according to the second variation of the first embodiment. FIG. 13 is a block diagram of a battery pack, a charging device, an authentication server, and a distribution server included in a management system according to the second embodiment. FIG. 14 is a diagram showing the operation of the management system according to the second embodiment. FIG. 15 is a diagram showing an example of log information about the battery pack according to the first variation of the second embodiment. FIG. 16 is a diagram showing the operation of a management system according to a first modification of the second embodiment. FIG. 17 is a diagram showing a flow for determining whether a battery pack needs to be reset according to the first modification of the second embodiment. FIG. 18 is a diagram showing an example of log information of a battery pack according to the second modification of the second embodiment. FIG. 19 is a diagram showing a flow for determining whether a battery pack needs to be reset according to the second modification of the second embodiment. FIG. 20 is a block diagram showing the configuration of a battery pack, a charging device, an authentication server, a distribution server, and a vulnerability management server included in a management system according to a third embodiment. FIG. 21 is a diagram showing an example of information stored in the distribution server according to the third embodiment. FIG. 22 is a diagram showing an example of information stored in the vulnerability management server according to the third embodiment. FIG. 23 is a diagram showing the operation of a management system according to the third embodiment. FIG. 24 is a diagram showing an example of an image displayed on the display unit of a charging device according to the third embodiment.

[0012] Battery packs are shared and used by many users. As a result, the battery pack firmware can unintentionally become infected with malware. Continuing to use a battery pack infected with malware could cause problems with the battery pack and the electric vehicle to which it is connected. If a battery pack becomes infected with malware, it is necessary to detect the infection and take measures, but if the malware is cleverly designed, it may not be possible to detect the malware infection.

[0013] The present disclosure provides a method for using a battery pack to solve the above problems. Hereinafter, an example of a method for using a battery pack according to one embodiment of the present disclosure will be described.

[0014] The method of using a battery pack in Example 1 is a method of using a battery pack that is replaceably connected to a mobile object, and when the battery pack is connected to a charging device and charged, the firmware of the battery pack is reinstalled.

[0015] In this way, by reinstalling the battery pack firmware when the battery pack is connected to a charging device to charge, it is possible to prevent the battery pack from being used while infected with malware, thereby preventing malfunctions in the battery pack.

[0016] A method of using a battery pack in Example 2 is the method of using a battery pack described in Example 1, and when reinstalling the firmware, the latest version of the firmware may be reinstalled.

[0017] In this way, reinstalling the latest version of firmware can prevent the battery pack from being used while infected with malware, thereby preventing malfunctions in the battery pack.

[0018] A method of using a battery pack in Example 3 is the method of using a battery pack described in Example 1 or 2, and may reinstall the firmware if authentication information of the battery pack matches pre-registered authentication information.

[0019] In this way, by reinstalling the firmware when the authentication information matches, it is possible to prevent a battery pack having authentication information from being used while infected with malware, thereby preventing malfunctions in the battery pack.

[0020] A method of using a battery pack in Example 4 is the method of using the battery pack described in Example 3, and when or after reinstalling the firmware, new authentication information different from the authentication information stored in the battery pack may be output to the battery pack.

[0021] In this way, by outputting new authentication information to the battery pack, it is possible to change the authentication information of the battery pack. This makes it possible to prevent the log information of the battery pack from being tampered with or the battery pack from being hacked. This makes it possible to prevent malfunctions in the battery pack.

[0022] A method of using a battery pack of Example 5 is the method of using the battery pack described in Example 4, wherein the battery pack may switch the authentication information stored in the battery pack to the new authentication information and store the new authentication information in a memory unit.

[0023] In this way, by switching the authentication information stored in the battery pack to new authentication information and storing it, it is possible to prevent the battery pack log information from being tampered with or the battery pack from being hacked, thereby preventing malfunctions in the battery pack.

[0024] A method of using a battery pack in Example 6 is the method of using the battery pack described in Example 3, and may include resetting the battery pack without reinstalling the firmware if the authentication information of the battery pack does not match the pre-registered authentication information.

[0025] By resetting the battery pack in this way, it is possible to suppress the operation of malware in the battery pack, for example, thereby preventing malfunctions in the battery pack.

[0026] A method of using a battery pack of Example 7 is the method of using a battery pack of any of Examples 1 to 5, wherein the firmware may be reinstalled if the time required to reinstall the firmware is equal to or less than the time required to charge the battery of the battery pack.

[0027] This allows the reinstallation to be performed reliably without interruption, which prevents the battery pack from being used while infected with malware, thereby preventing malfunctions in the battery pack.

[0028] A method of using a battery pack in Example 8 is the method of using the battery pack described in Example 7, wherein if the time required to reinstall the firmware is longer than the time required to charge the battery of the battery pack, the battery pack may be reset without reinstalling the firmware.

[0029] By resetting the battery pack in this way, it is possible to suppress the operation of malware in the battery pack, for example, thereby preventing malfunctions in the battery pack.

[0030] The method of using a battery pack of Example 9 is the method of using a battery pack described in any of Examples 6 to 8, and further includes resetting the battery pack if there is a history of the battery pack being detached from the mobile object other than when it was replaced.

[0031] This allows the battery pack to be reset if there is a possibility that the battery pack has been tampered with, thereby preventing malfunctions in the battery pack.

[0032] A method of using a battery pack in Example 10 is the method of using a battery pack according to any one of Examples 6 to 9, and may further include resetting the battery pack when a predetermined time has elapsed since the time of the previous reset.

[0033] This allows the battery pack to be reset before maintenance of the battery pack becomes insufficient, thereby preventing malfunctions in the battery pack.

[0034] The method of using a battery pack of Example 11 is the method of using a battery pack of any of Examples 6 to 10, and may further include resetting the battery pack when a predetermined time has elapsed since the time of the previous reinstallation.

[0035] This allows the battery pack to be reset before maintenance of the battery pack becomes insufficient, thereby preventing malfunctions in the battery pack.

[0036] A method of using a battery pack of Example 12 is the method of using a battery pack of any of Examples 6 to 11, and may further include resetting the battery pack when the mobile object has been connected to a network for a predetermined time or more.

[0037] This allows the battery pack to be reset if there is a risk of the battery pack being infected with malware, thereby preventing malfunctions in the battery pack.

[0038] A method of using a battery pack in Example 13 is the method of using a battery pack according to any one of Examples 6 to 12, and may further include resetting the battery pack when unusual traffic is recorded in the log information of the battery pack.

[0039] This allows the battery pack to be reset if there is a risk of the battery pack being infected with malware, thereby preventing malfunctions in the battery pack.

[0040] The charging device of Example 14 is a charging device for charging a battery of a battery pack that is replaceably connected to a mobile body, and includes a charging instruction unit that instructs charging of the battery, and an installation unit that installs firmware into the battery pack, and the installation unit reinstalls the firmware into the battery pack when the battery is being charged in accordance with the instruction of the charging instruction unit.

[0041] In this way, by reinstalling the battery pack firmware when the battery pack is connected to a charging device to charge, it is possible to prevent the battery pack from being used while infected with malware, thereby preventing malfunctions in the battery pack.

[0042] The program of Example 15 is a program for causing a computer to execute the method of using the battery pack according to any one of Examples 1 to 13.

[0043] This provides the same effect as the above-described method of using the battery pack.

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

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

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

[0047] 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%).

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

[0049] FIG. 1 is a block diagram of a battery pack 20, a charging device 30, an authentication server 41, and a distribution server 42 provided in a management system 1.

[0050] The management system 1 is a system for managing the use of battery packs 20. As shown in Fig. 1 , the management system 1 includes a plurality of battery packs 20, a plurality of charging devices 30, an authentication server 41, and a distribution server 42. Fig. 1 also shows 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.

[0051] 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 charging device 30 and can communicate with the charging device 30 while connected to the charging device 30. The charging device 30 can communicate with the authentication server 41 and the distribution server 42 via a communication network N such as the Internet or wide area Ethernet. The authentication server 41 and the distribution server 42 can communicate with each other via the communication network N. The communication between the charging device 30, the authentication server 41, and the distribution server 42 may be wired or wireless. The mobile object 10 may be able to communicate with an external terminal device via cellular communication or the like.

[0052] The management system 1 of this embodiment is configured to reinstall the firmware of the battery pack 20 when the battery pack 20 is connected to the charging device 30. By reinstalling the firmware, it becomes possible to eliminate malware that has invaded the battery pack 20.

[0053] Note that reinstallation refers to deleting firmware installed in the battery pack 20 and installing firmware of the same type as the deleted firmware. Reinstallation also includes overwriting installed firmware with firmware of the same type. Reinstallation also includes backing up firmware-related data and system settings, performing a clean install, and then restoring the backed-up data and system settings to their original state.

[0054] The reinstallation includes installing the same version of firmware as well as installing the latest version of firmware, and may also include restarting the battery pack 20 after installation.

[0055] The components of the mobile object 10 and the management system 1 will be described below.

[0056] [Configuration of the Mobile Body] The configuration of the mobile body will be described with reference to FIG.

[0057] The mobile object 10 is an electric transportation device 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.

[0058] FIG. 2 is a diagram showing the mobile object 10 and the battery pack 20 connected to the mobile object 10 .

[0059] As shown in FIG. 2, the mobile object 10 includes a plurality of connection ports 12, a mobile object control unit 15, and a storage unit 16.

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

[0061] The mobile object control unit 15 is configured with a CPU (Central Processing Unit) and a communication device. The mobile object control unit 15 is capable of communicating with a plurality of battery packs 20 using a communication bus within the mobile object 10. The mobile object control unit 15 requests the battery packs 20 for the power required to drive the mobile object 10.

[0062] The storage unit 16 is configured by a semiconductor memory, etc. The storage unit 16 also stores a computer program for operating the mobile object control unit 15.

[0063] The moving body 10 is driven by the power supplied from the battery pack 20 when the battery pack 20 is connected.

[0064] [Configuration of Battery Pack] The configuration of the battery pack 20 will be described with reference to FIG.

[0065] The battery pack 20 is a replaceable battery device 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 a plurality of mobile objects 10.

[0066] When the remaining battery power of the battery pack 20 connected to the mobile body 10 becomes low, the battery pack 20 is removed from the mobile body 10 and replaced with another charged battery pack 20. The battery pack 20 that is removed due to a low remaining battery power is attached to a charging device 30 and charged.

[0067] FIG. 3 is a block diagram of the battery pack 20.

[0068] 3, 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.

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

[0070] 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 terminals for transmitting power and terminals 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.

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

[0072] The battery control unit 25 is configured by, 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 vehicle 10. The battery control unit 25 also controls the operation of the battery pack 20 based on a control signal output from the charging device 30.

[0073] The storage unit 26 is configured by, for example, a semiconductor memory. The storage unit 26 stores log information indicating the operation history of the battery pack 20. The storage unit 26 also stores a computer program for operating the battery control unit 25. The computer program also includes firmware embedded in the battery pack 20.

[0074] The storage unit 26 also stores basic information about the battery pack 20, including firmware.

[0075] FIG. 4 is a diagram showing basic information of the battery pack 20.

[0076] 4, the basic information of the battery pack 20 includes identification information of the battery pack 20, and information about the maximum charge capacity and maximum output value of the battery 21 of the battery pack 20. The basic information also includes authentication information of the battery pack 20 and information about the firmware installed in the battery pack 20. The basic information of the battery pack 20 is not erased when the firmware is reinstalled, but is maintained in the storage unit 26.

[0077] The identification information of the battery pack 20 is an ID (identity) unique to the battery pack 20. This identification information is, for example, an identifier such as a physical address.

[0078] 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 can be output from the battery 21. These maximum charge capacity and maximum output value indicate the inherent characteristics of the battery pack 20.

[0079] The authentication information of the battery pack 20 is information indicating that the charging device 30 is permitted to perform software maintenance on the battery pack 20. Software maintenance means, for example, installing firmware in the battery pack 20. The authentication information is, for example, an identifier such as a logical address, and is rewritable as necessary.

[0080] The firmware-related information includes the firmware name and the firmware version. In this embodiment, the firmware of the battery pack 20 is rewritable and erasable. Accordingly, the firmware-related information is also rewritable.

[0081] When the battery pack 20 is connected to the charging device 30, the basic information of the battery pack 20 is output from the battery pack 20 to the charging device 30. The charging device 30 performs various processes on the battery pack 20 based on the information acquired from the authentication server 41 and the distribution server 42.

[0082] [Configuration of Authentication Server and Distribution Server] The configuration of the authentication server 41 and distribution server 42 will be described with reference to FIGS. 1, 5 and 6. FIG.

[0083] The authentication server 41 and the distribution server 42 are installed in a building or facility. The authentication server 41 and the distribution server 42 may be cloud servers provided on the communication network N.

[0084] The authentication server 41 is a server that manages authentication information of the battery pack 20. The authentication server 41 includes a control unit and a storage unit (not shown).

[0085] FIG. 5 is a diagram showing the authentication information of the battery pack 20 registered in the authentication server 41. As shown in FIG.

[0086] 5 , the authentication server 41 stores authentication information for all registered battery packs 20. The authentication information for the battery packs 20 is registered in the authentication server 41 by a terminal device such as a mobile terminal, a tablet terminal, or a computer terminal. When authentication information for a battery pack 20 is newly registered, the authentication server 41 outputs the newly registered authentication information to each charging device 30.

[0087] The distribution server 42 is a server that provides firmware for the battery pack 20. The distribution server 42 includes a control unit and a storage unit (not shown).

[0088] FIG. 6 is a diagram showing information relating to firmware held by the distribution server 42. As shown in FIG.

[0089] 6 , the distribution server 42 stores information regarding the type, firmware name, and firmware version of the battery pack 20. The distribution server 42 outputs firmware to be installed in the battery pack 20 to each charging device 30. If the firmware has been updated, the distribution server 42 outputs the latest firmware to each charging device 30.

[0090] [Configuration of Charging Device] The configuration of the charging device 30 will be described with reference to FIGS. 1, 7, and 8. FIG.

[0091] The charging device 30 is a charging device for charging electricity into the battery pack 20. The charging device 30 is also a device for reinstalling firmware for the battery pack 20, etc.

[0092] FIG. 7 is a diagram showing the charging device 30 and the battery pack 20 connected to the charging device 30.

[0093] The charging device 30 is installed in a battery station in, for example, a store, a facility, a service area, etc. A plurality of battery packs 20 are detachably attached to the charging device 30.

[0094] 7 , the charging device 30 includes a connection port unit 32, a control unit 35, and a storage unit 36. The control unit 35 includes a charge instruction unit 35a that instructs charging of the battery 21, and an installation unit 35b that installs firmware into the battery pack 20. The control unit 35 may also include a reset unit 35c that resets (or restarts) the battery pack 20. The charging device 30 may also include a display unit 38 such as a display.

[0095] 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 charging device 30 transmits power and transmits and receives communication signals to and from the battery pack 20 via the connection port 32.

[0096] The control unit 35 is configured by, for example, a CPU and a communication device, and the storage unit 36 ​​is configured by, for example, a semiconductor memory.

[0097] The storage unit 36 ​​stores a computer program for operating the control unit 35. The storage unit 36 ​​also stores authentication information for the battery pack 20 and information related to firmware.

[0098] FIG. 8 is a diagram showing authentication information and firmware-related information of the battery pack 20 stored in the charging device 30. As shown in FIG.

[0099] The authentication information stored in the charging device 30 is authentication information transmitted from the authentication server 41. The storage unit 36 ​​stores the authentication information of all pre-registered battery packs 20. This authentication information is used to authenticate the battery pack 20 connected to the charging device 30.

[0100] The firmware stored in the charging device 30 is firmware transmitted from the distribution server 42. For example, when the firmware is updated, the latest firmware is stored in the storage unit 36. This firmware is used when reinstalling the firmware of the battery pack 20.

[0101] The control unit 35 in this embodiment reinstalls the firmware when a predetermined reinstallation condition is met. Note that the control unit 35 executes the reinstallation when the predetermined reinstallation condition is met, regardless of whether the battery pack 20 is infected with malware or not.

[0102] For example, if the authentication information of the battery pack 20 acquired from the battery pack 20 matches the authentication information stored in the storage unit 36, that is, if the authentication information matches the pre-registered authentication information, the control unit 35 reinstalls the firmware of the battery pack 20. Note that the firmware stored in the storage unit 36 ​​is always the latest version of firmware, so the control unit 35 reinstalls the latest version of firmware for the battery pack 20.

[0103] Furthermore, the installation unit 35b of the control unit 35 reinstalls the firmware in the battery pack 20 while the battery 21 is being charged by the charging instruction unit 35a. Note that, because the terminals for transmitting power and the terminals for transmitting and receiving communication signals of the charging device 30 and the battery pack 20 are different, the battery pack 20 can reinstall the firmware while charging the battery 21. Furthermore, when the remaining battery power is low, the battery pack 20 can reinstall the firmware using power output from the charging device 30.

[0104] In this way, by reinstalling the firmware of the battery pack 20 while the battery pack 20 is connected to the charging device 30, it is possible to prevent the battery pack 20 from being used while infected with malware, thereby preventing malfunctions from occurring in the battery pack 20. Furthermore, by reinstalling the firmware while the battery pack 20 is being charged, it is possible to perform the reinstallation without setting aside additional time for the reinstallation.

[0105] In the above description, an example has been given in which the authentication information of the battery pack 20 matches pre-registered authentication information. However, if the authentication information does not match the pre-registered authentication information or if the battery pack 20 does not originally have authentication information, the charging device 30 does not need to reinstall the firmware. In this case, the charging device 30 may reset (or restart) the battery pack 20 instead of reinstalling the firmware. Resetting the battery pack 20 will be described in embodiment 2.

[0106] [Operation of Management System] The operation of the management system 1 according to the first embodiment will be described with reference to FIG.

[0107] FIG. 9 is a diagram illustrating the operation of the management system 1 according to the first embodiment.

[0108] First, the battery pack 20 is connected to the charging device 30 (S101).

[0109] When the charging device 30 detects the connection of the battery pack 20, it starts charging the battery 21 (S102). The connection of the battery pack 20 may be detected by hot plugging or the like.

[0110] Furthermore, when the charging device 30 detects the connection of the battery pack 20, it acquires from the battery pack 20 authentication information of the battery pack 20 and information about the firmware installed in the battery pack 20 (S103).

[0111] The charging device 30 determines whether the authentication information acquired from the battery pack 20 matches pre-registered authentication information (S104).

[0112] If the authentication information acquired from the battery pack 20 does not match the pre-registered authentication information (No in S104), the charging device 30 does not reinstall the firmware in the battery pack 20 and proceeds to step S107.

[0113] On the other hand, if the authentication information matches the pre-registered authentication information (Yes in S104), the charging device 30 reinstalls the firmware in the battery pack 20 (S105) and proceeds to step S107. For example, the charging device 30 selects firmware of the same type as the firmware installed in the battery pack 20 from multiple firmware versions stored in the storage unit 36, and reinstalls the selected firmware in the battery pack 20. If the firmware version has been updated, the charging device 30 installs the latest updated version in the battery pack 20.

[0114] When the battery pack 20 finishes reinstalling the firmware, it outputs a reinstallation completion signal to the charging device 30 (S106).

[0115] The charging device 30 determines whether charging of the battery 21 is complete (S107). If charging is not complete (No in S107), the process returns to step S107 and waits until charging is complete. If charging of the battery 21 is complete (Yes in S107), the charging device 30 ends these processes.

[0116] By performing these processes, it is possible to reinstall the firmware in the battery pack 20 in which the authentication information has been registered in advance. This makes it possible to prevent the battery pack 20 from being used while infected with malware, thereby preventing malfunctions in the battery pack 20.

[0117] Although the above example shows that the charging device 30 has pre-registered authentication information, the charging device 30 does not necessarily have to have authentication information. For example, when the battery pack 20 is connected, the charging device 30 may transmit authentication information of the battery pack 20 to the authentication server 41, and the authentication server 41 may check whether the authentication information matches pre-registered authentication information, and if the authentication information matches, reinstall the battery pack 20.

[0118] Although the above example shows that the charging device 30 stores firmware to be reinstalled, the charging device 30 does not necessarily have to store firmware. For example, when the battery pack 20 is connected, the charging device 30 may download firmware from the distribution server 42 and reinstall the firmware in the battery pack 20. Note that if the firmware has been updated, the charging device 30 may download the latest version of the firmware and reinstall the latest version of the firmware. After reinstalling the firmware in the battery pack 20, the charging device 30 may discard the firmware downloaded from the distribution server 42.

[0119] [First Modification of First Embodiment] A management system 1 according to a first modification of the first embodiment will be described with reference to Fig. 10 and Fig. 11. In this first modification, an example will be described in which authentication information of the battery pack 20 is changed when firmware is reinstalled. Note that in the first modification, it is assumed that the battery pack 20 has authentication information before the reinstallation.

[0120] The management system 1 of the first modification includes a plurality of battery packs 20, a plurality of charging devices 30, an authentication server 41, and a distribution server 42.

[0121] When the battery pack 20 is connected, the charging device 30 transmits authentication information of the battery pack 20 to the authentication server 41. Furthermore, the charging device 30 of this modification outputs a request signal to the authentication server 41 to request a change of the authentication information.

[0122] Based on the request signal, the authentication server 41 creates new authentication information that is different from the authentication information stored in the battery pack 20 .

[0123] FIG. 10 is a diagram showing new authentication information created by the authentication server 41. As shown in FIG.

[0124] 10 , the authentication server 41 creates new authentication information that is different from the authentication information stored in the battery pack 20. The authentication information stored in the battery pack 20 is the authentication information before the reinstallation, and the new authentication information is the authentication information after the reinstallation. The authentication server 41 associates the authentication information stored in the battery pack 20 with the new authentication information and stores them. The new authentication information created by the authentication server 41 is output to the charging device 30.

[0125] The charging device 30 outputs the new authentication information output from the authentication server 41 to the battery pack 20 and stores it in the storage unit 36. Based on the new authentication information output from the charging device 30, the battery pack 20 switches the authentication information stored in the battery pack 20 to the new authentication information and stores it in the storage unit 26.

[0126] FIG. 11 illustrates the operation of the management system according to the first modification of the first embodiment.

[0127] As shown in FIG. 11, the battery pack 20 is connected to the charging device 30 (S111).

[0128] When the charging device 30 detects the connection of the battery pack 20, it starts charging the battery 21 (S112).

[0129] Furthermore, when the battery pack 20 is connected, the charging device 30 acquires authentication information of the battery pack 20 and information about the firmware installed in the battery pack 20 (S113).

[0130] The charging device 30 determines whether the authentication information acquired from the battery pack 20 matches pre-registered authentication information (S114).

[0131] If the authentication information acquired from the battery pack 20 does not match the pre-registered authentication information (No in S114), the charging device 30 does not reinstall the firmware in the battery pack 20, and proceeds to step S122.

[0132] On the other hand, if the authentication information matches the pre-registered authentication information (Yes in S114), the charging device 30 reinstalls the firmware in the battery pack 20 (S115).

[0133] The battery pack 20 reinstalls the firmware of the battery pack 20 based on the firmware output from the charging device 30 (S115).

[0134] The charging device 30 also transmits the acquired authentication information to the authentication server 41 (S116). At this time, the charging device 30 outputs a request signal to the authentication server 41 requesting a change of the authentication information.

[0135] Based on the request signal, the authentication server 41 creates new authentication information different from the authentication information transmitted from the charging device 30, and returns the new authentication information to the charging device 30 that output the request signal (S117). The authentication server 41 outputs the new authentication information not only to the charging device 30 that output the request signal, but also to other charging devices 30. The authentication server 41 also stores the authentication information transmitted from the charging device 30 in association with the new authentication information.

[0136] The charging device 30 stores the new authentication information output from the authentication server 41 in the storage unit 36, and outputs the new authentication information to the battery pack 20 (S118).

[0137] The battery pack 20 switches the authentication information stored in the battery pack 20 to the new authentication information (S119) and stores the new authentication information in the storage unit 26. When the battery pack 20 has completed switching of the authentication information and the reinstallation of the firmware, it outputs a completion signal to the charging device 30 (S120).

[0138] The charging device 30 transfers the end signal output from the battery pack 20 to the authentication server 41 (S121).

[0139] Next, the charging device 30 determines whether charging of the battery 21 has finished (S122). If charging has not finished (No in S122), the charging device 30 returns to step S122 and waits until charging has finished. If charging of the battery 21 has finished (Yes in S122), the charging device 30 ends these processes.

[0140] In this way, by changing the authentication information of the battery pack 20 when reinstalling the battery pack 20, it is possible to prevent the log information of the battery pack 20 from being tampered with or the battery pack 20 from being hacked.

[0141] Although the above example shows the case where the authentication information of the battery pack 20 is changed when the firmware is reinstalled, the present invention is not limited to this example, and the authentication information of the battery pack 20 may be changed after the firmware is reinstalled. For example, after confirming that the reinstallation of the battery pack 20 has been completed, the charging device 30 may request the authentication server 41 to change the authentication information of the battery pack 20, and then output the new authentication information output from the authentication server 41 to the battery pack 20.

[0142] [Second Modification of First Embodiment] A management system 1 according to a second modification of the first embodiment will be described with reference to Fig. 12. In this second modification, an example will be described in which reinstallation is performed when the time required for reinstallation is equal to or less than the time required to charge the battery 21.

[0143] The management system 1 of the second modification includes a plurality of battery packs 20, a plurality of charging devices 30, an authentication server 41, and a distribution server 42.

[0144] FIG. 12 is a diagram illustrating the operation of the management system 1 according to the second modification of the first embodiment.

[0145] First, the battery pack 20 is connected to the charging device 30 (S131).

[0146] When the charging device 30 detects the connection of the battery pack 20, it starts charging the battery 21 (S132).

[0147] Furthermore, when the battery pack 20 is connected, the charging device 30 acquires authentication information of the battery pack 20 and information about the firmware installed in the battery pack 20 (S133).

[0148] The charging device 30 of the second modification determines whether the reinstallation time, which is the time required to reinstall the firmware, is equal to or less than the scheduled charging time, which is the time required to charge the battery 21 (S134).

[0149] The reinstallation time depends on the processing power of the computer and the file size of the firmware, but is, for example, the time determined when the firmware corresponding to a specific battery pack 20 was created. Information regarding the reinstallation time is output in advance from the distribution server 42 to the charging device 30 and stored in the storage unit 36 ​​of the charging device 30.

[0150] The estimated charging time is, for example, the time required for the battery 21 to be fully charged. The estimated charging time may be determined based on a charging time set by the user or a remaining battery capacity set by the user. The estimated charging time is calculated based on the remaining battery capacity stored in the log information of the battery 21, the power receiving capacity of the battery 21, and the power supply capacity of the charging device 30. The remaining battery capacity of the battery pack 20 can also be measured by the charging device 30.

[0151] If the reinstallation time is not equal to or less than the scheduled charging time (No in S134), the charging device 30 does not reinstall the firmware in the battery pack 20, and proceeds to step S137.

[0152] On the other hand, if the reinstallation time is equal to or less than the scheduled charging time (Yes in S134), the charging device 30 reinstalls the firmware in the battery pack 20 (S135), and the process proceeds to step S137.

[0153] When the battery pack 20 finishes reinstalling the firmware, it outputs a reinstallation completion signal to the charging device 30 (S136).

[0154] The charging device 30 determines whether charging of the battery 21 is complete (S137). If charging is not complete (No in S137), the process returns to step S137 and waits until charging is complete. If charging of the battery 21 is complete (Yes in S137), the charging device 30 ends these processes.

[0155] This allows the reinstallation to be performed reliably without interruption. This prevents the battery pack 20 from being used while infected with malware. This prevents malfunctions in the battery pack 20. Furthermore, by reinstalling the firmware while the battery 21 is being charged, there is no need to set aside additional time for the reinstallation.

[0156] In the above, an example is shown in which whether or not to reinstall is determined based only on the judgment item of whether the reinstallation time is less than the scheduled charging time, but this is not limited to this, and whether or not to reinstall may be determined by adding the judgment item of whether the authentication information matches.

[0157] For example, similar to step S104 in embodiment 1, the charging device 30 may determine whether the authentication information acquired from the battery pack 20 matches the pre-registered authentication information, and if the authentication information matches, may execute the processing from step S134 onwards. Alternatively, the charging device 30 may execute step S134 above, and if the reinstallation time is equal to or less than the scheduled charging time, may execute the processing from step S104 onwards in embodiment 1.

[0158] Second Embodiment [Configuration of Management System] The configuration of a management system 1A according to a second embodiment will be described with reference to Fig. 13. In the second embodiment, an example will be described in which the battery pack 20 is reset when firmware is not reinstalled.

[0159] Note that resetting refers to returning the firmware to its initial state by initializing the configuration file, adding necessary files, deleting unnecessary files, etc., without reinstalling the firmware.

[0160] FIG. 13 is a block diagram of the battery pack 20, the charging device 30, the authentication server 41, and the distribution server 42 included in the management system 1A.

[0161] 13, the management system 1A includes a plurality of battery packs 20, a plurality of charging devices 30, an authentication server 41, and a distribution server 42. In the second embodiment, a reset unit 35c is provided in the control unit 35 of the charging device 30 to reset the battery pack 20 (see FIG. 7). The resetting is performed by turning off the power to the battery pack 20 and then restarting it.

[0162] For example, in the first embodiment, if the authentication information of the battery pack 20 does not match the pre-registered authentication information (No in S104 in FIG. 9 ), the charging device 30 resets the battery pack 20 without reinstalling the firmware. Also, in the second modification of the first embodiment, if the reinstallation time is longer than the planned charging time (No in S134 in FIG. 12 ), the charging device 30 resets the battery pack 20 without reinstalling the firmware.

[0163] By resetting the battery pack 20 in this manner, it is possible to suppress the operation of malware in the battery pack 20.

[0164] [Operation of Management System] The operation of the management system 1A will be described with reference to FIG.

[0165] FIG. 14 is a diagram showing the operation of the management system 1A according to the second embodiment.

[0166] First, the battery pack 20 is connected to the charging device 30 (S201).

[0167] When the charging device 30 detects the connection of the battery pack 20, it starts charging the battery 21 (S202).

[0168] Furthermore, when the charging device 30 detects the connection of the battery pack 20, it acquires from the battery pack 20 authentication information of the battery pack 20 and information about the firmware installed in the battery pack 20 (S203).

[0169] The charging device 30 determines whether the authentication information acquired from the battery pack 20 matches the pre-registered authentication information (S204). In the second embodiment, a case where the authentication information does not match will be described.

[0170] If the authentication information of the battery pack 20 does not match the pre-registered authentication information (No in S204), the charging device 30 resets the battery pack 20 (S218) and proceeds to step S237.

[0171] When the reinstallation or resetting is completed, the battery pack 20 outputs a completion signal to the charging device 30 (S236).

[0172] The charging device 30 determines whether charging of the battery 21 is complete (S237). If charging is not complete (No in S237), the process returns to step S237 and waits until charging is complete. If charging of the battery 21 is complete (Yes in S237), the charging device 30 ends these processes.

[0173] In the above description, the battery pack 20 is reset when the authentication information of the battery pack 20 does not match the pre-registered authentication information, but this is not limiting. For example, the charging device 30 may reset the battery pack 20 when the reinstallation time is longer than the scheduled charging time.

[0174] [First Modification of Second Embodiment] A management system 1A according to a first modification of the second embodiment will be described with reference to Figures 15 to 17. In this first modification, an example will be described in which the battery pack 20 is reset when a predetermined reset condition is satisfied.

[0175] FIG. 15 is a diagram showing log information of the battery pack 20 in the management system 1A according to the first modification of the second embodiment.

[0176] 15 shows, as log information, the number of times the battery pack 20 has been detached, the time of the last reset, and the time of the last reinstallation. The number of times the battery pack 20 has been detached from the mobile object 10 and reconnected to the same mobile object 10 other than when it was replaced. This log information is stored in the memory unit 26 of the battery pack 20.

[0177] For example, the control unit 35 resets the battery pack 20 when the number of times the battery pack 20 has been detached is equal to or greater than a predetermined number. This predetermined number may be set to 1. In other words, the control unit 35 resets the battery pack 20 when there is a history of the battery pack 20 being detached from the vehicle 10 other than when it was replaced.

[0178] Furthermore, the control unit 35 resets the battery pack 20 when a predetermined time has elapsed since the previous reset time. Furthermore, the control unit 35 resets the battery pack 20 when a predetermined time has elapsed since the previous reinstallation time. Furthermore, the control unit 35 may reset the battery pack 20 when the detachment time is longer than a predetermined time. The number of detachments refers to the time from when the battery pack 20 is detached from the mobile object 10 other than when it is replaced until it is reconnected to the same mobile object 10.

[0179] FIG. 16 is a diagram showing the operation of the management system 1A according to the first modification of the second embodiment.

[0180] Steps S201 to S203 are the same as those in the above-described embodiment 2. Note that in the first modification of embodiment 2 as well, a case where the authentication information does not match will be described.

[0181] The charging device 30 determines whether the authentication information acquired from the battery pack 20 matches pre-registered authentication information (S204).

[0182] If the authentication information of the battery pack 20 does not match the pre-registered authentication information (No in S204), the charging device 30 determines whether or not the battery pack 20 needs to be reset (S205).

[0183] The flow of determining whether or not resetting of the battery pack 20 is necessary will be described with reference to FIG.

[0184] FIG. 17 is a diagram showing a flow of determining whether or not resetting of the battery pack 20 is necessary according to the second embodiment.

[0185] The charging device 30 determines whether or not there is a history of the battery pack 20 being detached from the moving object 10 other than at the time of replacement (S211).

[0186] If there is a history of the battery pack being detached from the moving object 10 (Yes in S211), the charging device 30 determines that the battery pack 20 needs to be reset (S217).

[0187] On the other hand, if there is no history of the battery being detached from the moving object 10 (No in S211), the charging device 30 next determines whether a predetermined time has elapsed since the previous reset time (S212).

[0188] If a predetermined time has elapsed since the previous reset time (Yes in S212), the charging device 30 determines that the battery pack 20 needs to be reset (S217).

[0189] On the other hand, if the predetermined time has not elapsed since the previous reset time (No in S212), charging device 30 next determines whether a predetermined time has elapsed since the previous reinstallation time (S213).

[0190] If a predetermined time has elapsed since the previous reinstallation time (Yes in S213), the charging device 30 determines that the battery pack 20 needs to be reset (S217).

[0191] On the other hand, if the predetermined time has not elapsed since the previous reinstallation time (No in S213), the charging device 30 determines that resetting of the battery pack 20 is not necessary (S219).

[0192] If the charging device 30 determines in the above-mentioned necessity determination flow that resetting is necessary, it resets the battery pack 20 (S218) and proceeds to step S237. On the other hand, if the charging device 30 determines in the above-mentioned necessity determination flow that resetting is not necessary, it does not reset the battery pack 20 and proceeds to step S237.

[0193] When the resetting is completed, the battery pack 20 outputs a reset completion signal to the charging device 30 (S236).

[0194] The charging device 30 determines whether charging of the battery 21 is complete (S237). If charging is not complete (No in S237), the process returns to step S237 and waits until charging is complete. If charging of the battery 21 is complete (Yes in S237), the charging device 30 ends these processes.

[0195] In the above description, if the authentication information of the battery pack 20 does not match the pre-registered authentication information (No in S204), it is determined whether or not to reset the battery pack 20 (S205), but this is not limiting. For example, if the reinstallation time is longer than the planned charging time, the charging device 30 may determine whether or not to reset the battery pack 20, and execute the steps from S211 onwards shown in Fig. 17 as a flow for determining whether or not to reset the battery pack 20.

[0196] [Second Modification of Second Embodiment] A management system 1A according to a second modification of the second embodiment will be described with reference to Figures 18 and 19. In this second modification, in addition to the necessity determination of the first modification, an example will be described in which the necessity of resetting is determined using the state of the mobile object 10. The mobile object 10 is capable of communicating with an external terminal device via cellular communication or the like.

[0197] FIG. 18 is a diagram showing an example of log information of the battery pack 20 according to the second modification of the second embodiment.

[0198] FIG. 18 shows, as log information, the number of times the battery pack 20 has been removed and attached, the time of the previous reset, the time of the previous reinstallation, the time of connection to the network, and whether or not there has been any suspicious traffic.

[0199] The network connection time is the time that the mobile object 10 using the battery pack 20 accessed the network. The presence of suspicious traffic means that unusual communication data is recorded in the log information of the battery pack 20. The network connection time and log information related to the suspicious traffic are transmitted to the battery pack 20 via the communication bus in the mobile object 10 and stored in the memory unit 26 of the battery pack 20.

[0200] For example, the control unit 35 resets the battery pack 20 when the connection time to the network is equal to or longer than a threshold value. The control unit 35 also resets the battery pack 20 when there is suspicious traffic.

[0201] FIG. 19 is a diagram showing a flow of determining whether or not resetting of the battery pack 20 is necessary in the second modification of the second embodiment.

[0202] Steps S211 and S212 are the same as in the first modification example.

[0203] If a predetermined time has elapsed since the previous reinstallation time (Yes in S213), the charging device 30 determines that the battery pack 20 needs to be reset (S217).

[0204] On the other hand, if the predetermined time has not elapsed since the previous reinstallation time (No in S213), charging device 30 next determines whether the connection time to the network is equal to or longer than a threshold value (S214).

[0205] If the connection time to the network is equal to or longer than the threshold value (Yes in S214), the charging device 30 determines that the battery pack 20 needs to be reset (S217).

[0206] On the other hand, if the connection time to the network is not equal to or longer than the threshold (No in S214), charging device 30 next determines whether or not there is suspicious traffic (S215).

[0207] If there is suspicious traffic (Yes in S215), the charging device 30 determines that the battery pack 20 needs to be reset (S217).

[0208] On the other hand, if there is no suspicious traffic (No in S215), the charging device 30 determines that resetting of the battery pack 20 is not necessary (S219).

[0209] If the charging device 30 determines in the above-mentioned necessity determination flow that resetting is necessary, it resets the battery pack 20 (S218) and proceeds to step S237. On the other hand, if the charging device 30 determines in the above-mentioned necessity determination flow that resetting is not necessary, it does not reset the battery pack 20 and proceeds to step S237.

[0210] Steps S236 and S237 are the same as those in the above-described embodiment 2. By resetting the battery pack 20 in this manner, it is possible to prevent malfunctions in the battery pack 20.

[0211] Third Embodiment A management system 1B according to a third embodiment will be described with reference to Fig. 20 to Fig. 24. In the third embodiment, a case where vulnerability remains in the firmware of the battery pack 20 will be described.

[0212] FIG. 20 is a block diagram of the battery pack 20, the charging device 30, the authentication server 41, the distribution server 42, and the vulnerability management server 43 included in the management system 1B of the third embodiment.

[0213] The vulnerability management server 43 is a server for managing vulnerabilities in the firmware of the battery pack 20 .

[0214] FIG. 21 is a diagram showing an example of information stored in the distribution server 42.

[0215] FIG. 21 shows the firmware versions and update files corresponding to each battery pack 20.

[0216] FIG. 22 is a diagram showing an example of information stored in the vulnerability management server 43.

[0217] 22 shows the firmware version and the presence or absence of vulnerabilities corresponding to each battery pack 20. The presence or absence of vulnerabilities may be indicated using three or more ranks.

[0218] The charging device 30 includes a connection port unit 32, a control unit 35, and a storage unit 36. The charging device 30 also includes a display unit 38 (see FIG. 7) for displaying information related to the vulnerability.

[0219] The charging device 30 checks the vulnerability management server 43 for vulnerabilities in the firmware of the battery pack 20, and if it is determined that there is a vulnerability, displays information indicating the vulnerability on the display unit 38 of the charging device 30.

[0220] FIG. 23 is a diagram showing the operation of the management system 1B according to the third embodiment.

[0221] 23 are the same as in embodiment 2. Note that in embodiment 3 as well, a case where the authentication information does not match will be described.

[0222] The charging device 30 determines whether the authentication information acquired from the battery pack 20 matches pre-registered authentication information (S204).

[0223] If the authentication information of the battery pack 20 does not match the pre-registered authentication information (No in S204), the charging device 30 resets the battery pack 20 (S218).

[0224] Next, if an update file exists, the charging device 30 performs the update (S321). If a vulnerability exists in the current version, the charging device 30 displays information indicating the vulnerability on the display unit 38 of the charging device 30 (S322).

[0225] FIG. 24 is a diagram showing an example of an image displayed on the display unit 38 of the charging device 30. As shown in FIG.

[0226] 24 shows the user name, the identification information of the mobile object 10, the usage period, etc., as well as information about the type of vulnerable battery pack 20, the firmware version, the identification information of the battery pack, the usage return date of the battery pack 20, etc. These image displays can warn of vulnerabilities in the firmware of the battery pack 20.

[0227] (Other Embodiments) While the methods of using the battery pack according to one or more aspects have been described above based on Embodiments 1, 2, and 3, the present disclosure is not limited to these respective embodiments, etc. As long as they do 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.

[0228] In the above first to third embodiments, the authentication server 41 and the distribution server 42 are different servers, but the present invention is not limited to this, and the authentication server and the distribution server may be the same management server.

[0229] In the above-described second embodiment, an example has been described in which the battery pack 20 is reset when the firmware is not reinstalled in the first embodiment, but the present invention is not limited to this. For example, it is not necessary to determine whether to reinstall the firmware, and the charging device 30 may immediately reset the battery pack 20.

[0230] In other words, the present disclosure is a method of using a battery pack 20 that is replaceably connected to a mobile object 10, and when a battery pack 20 with installed firmware is connected to a charging device 30 for charging, the battery pack 20 may be reset (or restarted).

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

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

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

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

[0235] Furthermore, the charging device according to each of the above embodiments may be realized as a single device or may be realized by multiple devices. When the charging device is realized by multiple devices, the components of the charging device may be distributed among the multiple devices in any manner. When the charging device 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.

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

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

[0238] 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 method of using a battery pack.

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

[0240] The present disclosure is useful for a method of using a replaceable battery that manages the use of the replaceable battery, and the like.

[0241] 1, 1A, 1B Management system 10 Mobile object 12 Connection port unit 15 Mobile object control unit 16 Memory unit 20 Battery pack 21 Battery 22 Connection port unit 25 Battery control unit 26 Memory unit 30 Charging device 32 Connection port unit 35 Control unit 35a Charging instruction unit 35b Install unit 35c Reset unit 36 ​​Memory unit 38 Display unit 41 Authentication server 42 Distribution server 43 Vulnerability management server N Communication network

Claims

1. A method for using a battery pack that is replaceably connected to a mobile object, the method comprising reinstalling firmware for the battery pack when the battery pack is connected to a charging device and charged.

2. The method of using the battery pack according to claim 1, wherein when the firmware is reinstalled, the latest version of the firmware is reinstalled.

3. The method for using a battery pack according to claim 1, wherein the firmware is reinstalled if the authentication information of the battery pack matches pre-registered authentication information.

4. A method of using a battery pack as described in claim 3, wherein new authentication information different from the authentication information stored in the battery pack is output to the battery pack when or after the firmware is reinstalled.

5. The method of using a battery pack according to claim 4, wherein the battery pack replaces the authentication information stored in the battery pack with the new authentication information and stores the new authentication information in a memory unit.

6. The method for using a battery pack according to claim 3, wherein if the authentication information of the battery pack does not match the pre-registered authentication information, the battery pack is reset without reinstalling the firmware.

7. The method of using a battery pack according to claim 1, wherein the firmware is reinstalled if the time required to reinstall the firmware is equal to or less than the time required to charge the battery of the battery pack.

8. The method of using a battery pack according to claim 7, wherein if the time required to reinstall the firmware is longer than the time required to charge the battery of the battery pack, the battery pack is reset without reinstalling the firmware.

9. A method of using a battery pack according to claim 6 or 8, further comprising resetting the battery pack if there is a history of the battery pack being detached from the mobile unit other than at the time of replacement.

10. A method for using a battery pack according to claim 6 or 8, further comprising resetting the battery pack if a predetermined time has elapsed since the time of the previous reset.

11. The method of using a battery pack according to claim 6 or 8, further comprising resetting the battery pack if a predetermined time has elapsed since the time of the previous reinstallation.

12. The method of using a battery pack according to claim 6 or 8, further comprising resetting the battery pack when the mobile object has been connected to the network for a predetermined period of time or more.

13. A method of using a battery pack according to claim 6 or 8, further comprising resetting the battery pack if unusual traffic is recorded in the log information of the battery pack.

14. A charging device for charging a battery of a battery pack that is replaceably connected to a mobile object, comprising: a charging instruction unit that instructs charging of the battery; and an installation unit that installs firmware into the battery pack, wherein the installation unit reinstalls the firmware into the battery pack when the battery is being charged in accordance with the instruction of the charging instruction unit.

15. A program for causing a computer to execute the method for using a battery pack according to any one of claims 1 to 8.

Images