Confirmation method, confirmation device, power storage device, confirmation system, program, and computer-readable storage medium

Abstract

The invention provides a confirmation method. The confirmation method comprises: a step of transmitting first verification information to a device to be confirmed; a step of converting the first verification information on the basis of the second verification information and generating third verification information; and a step of receiving fifth verification information or sixth verification information from the device to be verified, in which (i) the fifth verification information is information generated by the device to be verified by converting the first verification information on the basis of fourth verification information satisfying a first mathematical relationship with the second verification information; (ii) the sixth verification information is derived from the first verification information and the fourth verification information or from the fifth verification information by the device to be confirmed using a second mathematical relationship that the third verification information and the fifth verification information should satisfy when the device to be confirmed is a legal device; and a step of determining whether the device to be confirmed is a legal device based on the third verification information and the fifth verification information or the sixth verification information.

Description

Technical Field

[0001] The present invention relates to a confirmation method, a confirmation device, a power storage device, a confirmation system, a program, and a computer-readable storage medium. Background Art

[0002] Patent Document 1 discloses a management device that authenticates batteries by comparing an authentication key stored in a battery returned to a battery station with an authentication key stored in the battery station. Patent Document 2 discloses a battery station that uses a whitelist method to determine whether to accept a battery.

[0003] Patent Document 1: International Publication No. 2019 / 181661

[0004] Patent Document 2: International Publication No. 2020 / 059833 Summary of the invention

[0005] In the first mode of the present invention, a confirmation method is provided. The above confirmation method is, for example, a confirmation method used by a confirmation device to confirm whether the device to be confirmed is a legitimate device. The above confirmation method, for example, has a step of sending first verification information to the device to be confirmed. The above confirmation method, for example, has a step of transforming the first verification information based on the second verification information to generate third verification information. The above confirmation method, for example, has a step of receiving fifth verification information or sixth verification information from the device to be confirmed, wherein (i) the fifth verification information is information generated by the device to be confirmed by transforming the first verification information based on the fourth verification information that satisfies the first mathematical relationship with the second verification information, and (ii) the sixth verification information is information derived from the first verification information and the fourth verification information or derived from the fifth verification information by the device to be confirmed using the second mathematical relationship that the third verification information and the fifth verification information should satisfy when the device to be confirmed is a legitimate device. The above confirmation method, for example, has a step of determining whether the device to be confirmed is a legitimate device based on the third verification information, and the fifth verification information or the sixth verification information. In the above confirmation method, the step of determining includes, for example: (a) when the fifth verification information is received, determining whether the third verification information and the fifth verification information satisfy the second mathematical relationship, or (b) when the sixth verification information is received, determining whether the third verification information and the sixth verification information are consistent. In the above confirmation method, the second mathematical relationship is determined based on the first mathematical relationship.

[0006] In any of the above confirmation methods, the step of determining whether the third verification information and the fifth verification information satisfy the second mathematical relationship may include: the step of processing the third verification information and the fifth verification information according to the first verification algorithm to generate the seventh verification information. In any of the above confirmation methods, the step of determining may include the step of acquiring the eighth verification information from the device to be confirmed, the eighth verification information representing the calculation result obtained by processing the third verification information and the fifth verification information according to the first verification algorithm when the second verification information and the fourth verification information satisfy the first mathematical relationship. In any of the above confirmation methods, the step of determining may include the step of determining whether the seventh verification information and the eighth verification information are consistent.

[0007] In any of the above confirmation methods, there may also be a step of: in the case where it is determined that the third verification information and the fifth verification information do not satisfy the second mathematical relationship, or in the case where it is determined that the third verification information and the sixth verification information are inconsistent, confirming that the device to be confirmed is not a legal device, or that the device to be confirmed is an illegal device. In any of the above confirmation methods, there may also be a step of: in the case where it is determined that the third verification information and the fifth verification information satisfy the second mathematical relationship, or in the case where it is determined that the third verification information and the sixth verification information are consistent, confirming that the device to be confirmed is a legal device, or that the device to be confirmed is not an illegal device.

[0008] In any of the above confirmation methods, there may also be a step of: (i) obtaining the second verification information from the manufacturer or transferor of the confirmation device, or the issuer of the second verification information and the fourth verification information, or (ii) obtaining the second verification information from a first external device that is configured to be able to communicate wirelessly with the confirmation device and confirm that the confirmation device is a legitimate device. In any of the above confirmation methods, there may also be a step of saving the obtained second verification information to a first storage device configured in the confirmation device. In any of the above confirmation methods, there may also be a step of: (i) obtaining the fourth verification information from the manufacturer or transferor of the device to be confirmed, or the issuer of the second verification information and the fourth verification information, or (ii) obtaining the fourth verification information from a second external device that is configured to be able to communicate wirelessly with the device to be confirmed and confirm that the device to be confirmed is a legitimate device. In any of the above confirmation methods, there may also be a step of saving the obtained fourth verification information to a second storage device configured in the device to be confirmed.

[0009] In any of the above confirmation methods, there may be a step of receiving the second verification information encrypted by the first private key from the device to be confirmed. In any of the above confirmation methods, there may be a step of decrypting the encrypted second verification information by using the first public key corresponding to the first private key. In any of the above confirmation methods, there may be a step of receiving the unencrypted second verification information from the device to be confirmed. In any of the above confirmation methods, there may be a step of determining whether the unencrypted second verification information and the decrypted second verification information are consistent. The step of generating the third verification information may include: if it is determined in the step of determining that the unencrypted second verification information and the decrypted second verification information are consistent, the step of transforming the first verification information based on the second verification information to generate the third verification information. In any of the above confirmation methods, there may be a step of obtaining the second verification information signed by the first private key from the device to be confirmed. In any of the above confirmation methods, there may be a step of verifying the signature by using the first public key corresponding to the first private key. In any of the above confirmation methods, the step of obtaining the signed second verification information may include: obtaining the second verification information encrypted by the first private key and the unencrypted second verification information. In any of the above confirmation methods, the step of verifying the signature may include: the step of decrypting the encrypted second verification information using the first public key. In any of the above confirmation methods, the step of verifying the signature may include the step of determining whether the unencrypted second verification information and the decrypted second verification information are consistent. In any of the above confirmation methods, the step of generating the third verification information may include: if it is determined in the step of determining that the unencrypted second verification information and the decrypted second verification information are consistent, the step of transforming the first verification information based on the second verification information to generate the third verification information.

[0010] In any of the above confirmation methods, the second verification information may be a public key. In any of the above confirmation methods, the fourth verification information may be a private key corresponding to the public key. In any of the above confirmation methods, there may also be a step of generating a random number. In any of the above confirmation methods, there may also be a step of generating the first verification information based on the random number.

[0011] In any of the above confirmation methods, there may also be a step in which the device to be confirmed receives the first verification information from the confirmation device. In any of the above confirmation methods, there may also be a step in which the device to be confirmed generates the fifth verification information based on the first verification information and the fourth verification information. In any of the above confirmation methods, there may also be a step in which the device to be confirmed sends the generated fifth verification information to the confirmation device.

[0012] In any of the above confirmation methods, the device to be confirmed may include a power storage device. In any of the above confirmation methods, the confirmation device may include a charging and discharging device that can be installed and removed relative to the power storage device of the device to be confirmed, and charges and / or discharges the power storage device. In any of the above confirmation methods, the confirmation device may be a first power device having a first terminal. In any of the above confirmation methods, the device to be confirmed may be a second power device having a second terminal that can be installed with the first terminal. In any of the above confirmation methods, there may also be a step of determining to prohibit or inhibit the input and output of power between the first power device and the second power device when it is determined that the third verification information and the fifth verification information do not satisfy the second mathematical relationship, or when it is determined that the third verification information and the sixth verification information are inconsistent.

[0013] In any of the above confirmation methods, the confirmation device may be a storage device that stores the device to be confirmed as a device to be kept. In any of the above confirmation methods, the storage device may have an installation portion for installing the device to be kept. In any of the above confirmation methods, there may also be: (a) when it is determined that the third verification information and the fifth verification information do not satisfy the second mathematical relationship, or when it is determined that the third verification information and the sixth verification information are inconsistent, it is decided not to continue the installation of the device to be kept relative to the installation portion, or to keep the device to be kept in a manner different from that of a legitimate device, and / or (b) when it is determined that the third verification information and the fifth verification information satisfy the second mathematical relationship, or when it is determined that the third verification information and the sixth verification information are consistent, it is decided to continue the installation of the device to be kept relative to the installation portion, or to keep the device to be kept as a legitimate device.

[0014] In any of the above confirmation methods, the storage device is configured to store at least one of the plurality of storage devices. In any of the above confirmation methods, there may be a step of obtaining common use identification information for identifying the storage device that can be used by multiple users among the plurality of storage devices. In any of the above confirmation methods, there may be a step of determining whether the storage device to be confirmed is a storage device that can be used by multiple users based on the common use identification information when it is determined that the third verification information and the fifth verification information satisfy the second mathematical relationship or when it is determined that the third verification information and the sixth verification information are consistent. In any of the above confirmation methods, there may be a step of (c) when it is determined that the storage device to be confirmed is not a storage device that can be used by multiple users, deciding not to continue to install the storage device to the installation unit or to store the storage device in a manner different from that of a legitimate device, and / or (d) when it is determined that the storage device to be confirmed is a storage device that can be used by multiple users, deciding to continue to install the storage device to the installation unit or to store the storage device as a legitimate device.

[0015] In the second mode of the present invention, a confirmation device is provided. The above-mentioned confirmation device, for example, confirms whether the device to be confirmed is a legitimate device. The above-mentioned confirmation device, for example, has a first verification information sending unit, which sends the first verification information to the device to be confirmed. The above-mentioned confirmation device, for example, has a third verification information generating unit, which transforms the first verification information based on the second verification information to generate the third verification information. The above-mentioned confirmation device, for example, has a response receiving unit, which receives the fifth verification information or the sixth verification information from the device to be confirmed, wherein (i) the fifth verification information is information generated by the device to be confirmed by transforming the first verification information based on the fourth verification information that satisfies the first mathematical relationship with the second verification information, and (ii) the sixth verification information is information derived from the first verification information and the fourth verification information or derived from the fifth verification information by the device to be confirmed using the second mathematical relationship that the third verification information and the fifth verification information should satisfy when the device to be confirmed is a legitimate device. The above-mentioned confirmation device, for example, has a determination unit, which determines whether the device to be confirmed is a legitimate device based on the third verification information, and the fifth verification information or the sixth verification information. In the above-mentioned confirmation device, the determination unit, for example, performs the following processing: (a) when receiving the fifth verification information, determines whether the third verification information and the fifth verification information satisfy the second mathematical relationship. In the above-mentioned confirmation device, the determination unit, for example, (b) when receiving the sixth verification information, determines whether the third verification information and the sixth verification information are consistent.

[0016] In a third aspect of the present invention, a power storage device is provided. The power storage device, for example, includes a power storage unit that stores electric energy. The power storage device, for example, includes an electric terminal that is used to send and receive electric power to and from a first power device. In the power storage device, the first power device, for example, charges the power storage unit. In the power storage device, the first power device, for example, uses the electric power discharged by the power storage unit. The power storage device, for example, includes a storage unit that stores fourth verification information. The power storage device, for example, includes a first verification information acquisition unit that acquires first verification information from the first power device. The power storage device, for example, includes a response unit that transforms the first verification information acquired by the first verification information acquisition unit based on the fourth verification information stored in the storage unit to generate fifth verification information, or generates sixth verification information obtained by transforming the first verification information based on the second verification information that satisfies a first mathematical relationship with the fourth verification information.

[0017] In any of the above-mentioned power storage devices, the response unit may transmit the fifth verification information or the sixth verification information to the first power device.

[0018] In a fourth aspect of the present invention, a confirmation system is provided. The above-mentioned confirmation system, for example, includes an electric power device. In the above-mentioned confirmation system, for example, the electric power device includes any of the electric storage devices involved in the second aspect. The above-mentioned confirmation system, for example, includes any of the electric storage devices involved in the third aspect. In the above-mentioned confirmation system, for example, the confirmation device confirms that the electric storage device, which is the confirmation object of the confirmation device, that is, the device to be confirmed, is a legitimate device.

[0019] In a fifth aspect of the present invention, a program is provided. The program may be a program for causing a computer to execute any of the confirmation methods involved in the first aspect. The program may be a program for causing a computer to function as the confirmation device involved in the second aspect. The program may be a program for causing a computer to function as the power storage device involved in the third aspect.

[0020] In a sixth aspect of the present invention, a computer-readable storage medium is provided. The computer-readable storage medium stores, for example, any program according to the fifth aspect. The computer-readable storage medium may be a non-volatile computer-readable medium.

[0021] In addition, the above summary of the invention does not list all the features of the present invention. In addition, a sub-combination of these feature groups may also be an invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 An example of the system configuration of the battery management system 100 is schematically shown.

[0023] Figure 2 An example of the internal structure of the mobile battery 20 is schematically shown.

[0024] Figure 3 An example of the internal structure of the battery exchange unit 120 is schematically shown.

[0025] Figure 4 An example of the authentication flow of the mobile battery 20 is schematically shown.

[0026] Figure 5 An example of the internal structure of the battery authentication unit 378 is schematically shown.

[0027] Figure 6 An example of the internal structure of the authentication handling unit 232 is schematically shown.

[0028] Figure 7 An example of the internal structure of the mounted device 330 is schematically shown.

[0029] Figure 8 An example of the internal structure of the mounted device 370 is schematically shown.

[0030] Fig. 9 An example of the internal structure of the mobile battery 920 is schematically shown.

[0031] Fig.10 An example of the acquisition flow of the authentication public key 74 is schematically shown.

[0032] Fig.11 An example of the acquisition flow of the authentication public key 74 is schematically shown.

[0033] Fig.12 Another example of the authentication flow of the mobile battery 20 is schematically shown.

[0034] Fig.13 An example of the relationship between the response code and the verification code is schematically shown.

[0035] Fig.14 An example of the verification process of the response code and the verification code is schematically shown.

[0036] Fig.15 Another example of the verification flow of the response code and the verification code is schematically shown.

[0037] Fig.16 An example of the internal structure of the computer 5000 is schematically shown. DETAILED DESCRIPTION

[0038] The present invention is described below by the embodiments of the invention, but the following embodiments do not limit the claimed invention. In addition, all combinations of the features described in the embodiments are not necessarily necessary for the solution of the present invention. In addition, in the drawings, the same reference numerals are sometimes given to the same or similar parts and repeated descriptions are omitted.

[0039] (Overview of Battery Management System 100)

[0040] Figure 1 An example of the system configuration of the battery management system 100 is schematically shown. In the present embodiment, the battery management system 100 includes one or more (sometimes simply referred to as one or more) battery switches 120 and a management server 140. In the present embodiment, the battery switch 120 has one or more storage units 122 and a communication unit 126. In the present embodiment, the storage unit 122 includes one or more slots 124. In the present embodiment, the communication unit 126 includes a communication interface 128. The battery switch 120 is sometimes referred to as a battery station.

[0041] In the present embodiment, each unit of the battery management system 100 operates by consuming power received from the power system 12. In addition, each unit of the battery management system 100 can send and receive information to and from each other via the communication network 14. One or more storage units 122 and communication units 126 can send and receive information to and from each other via a wired or wireless communication line (not shown).

[0042] In this embodiment, the battery management system 100 manages one or more (sometimes referred to as more than one) mobile batteries 20. In order to simplify the description, in this embodiment, the battery management system 100 will be described in detail by taking the case where the battery management system 100 provides a sharing service of the mobile battery 20 to the user 40 of the electric bicycle 30 as an example.

[0043] In this embodiment, each of the one or more slots 124 provided in the storage unit 122 of the battery exchanger 120 can store one or more mobile batteries 20. In addition, each of the one or more slots 124 provided in the storage unit 122 of the battery exchanger 120 can charge one or more mobile batteries 20.

[0044] For example, a user 40 who joins the sharing service of the mobile battery 20 uses the communication terminal 42 to access the battery management system 100 and request to borrow the mobile battery 20. The user 40 can reserve the loan of the mobile battery 20 by specifying the date, time and place at which the mobile battery 20 is desired to be loaned and the number of mobile batteries 20 desired to be loaned. The communication terminal 42 can access the battery management system 100 via the communication network 14, and can also access the battery management system 100 via the battery exchange 120. Note that the user 40 can operate the battery exchange 120 to request to loan the mobile battery 20.

[0045] When receiving the above request, the user 40 can take out the mobile battery 20 accommodated in the battery exchanger 120 (sometimes referred to as the expenditure of the mobile battery 20). Therefore, the user 40 can replace the mobile battery 20 mounted on the electric bicycle 30 and the mobile battery 20 accommodated in the battery exchanger 120.

[0046] More specifically, the user 40 removes the mobile battery 20 mounted on the electric bicycle 30 from the electric bicycle 30. The user 40 returns the mobile battery 20 removed from the electric bicycle 30 to the battery exchange 120. When the user 40 returns the mobile battery 20, the battery exchange 120 pays out the charged mobile battery 20 accommodated in the battery exchange 120. The user 40 receives the charged mobile battery 20 from the battery exchange 120 and mounts the charged mobile battery 20 on the electric bicycle 30. Thus, the mobile battery 20 is replaced between the electric bicycle 30 and the battery exchange 120.

[0047] Authentication of the mobile battery 20 in the battery management system 100

[0048] In the present embodiment, the battery switch 120 may be set in a lockable building or site, or may be set outdoors in an unlocked state. Considering the convenience of the user 40, the battery switch 120 is preferably set in an environment where multiple users 40 can freely use it. On the other hand, when the battery switch 120 is set in an environment where multiple users 40 can freely use it, the mobile battery 20 (sometimes referred to as an irregular mobile battery 20) that is not managed by the battery management system 100 may be inserted into the slot 124 of the battery switch 120.

[0049] When an informal mobile battery 20 having specifications different from those of an informal mobile battery 20 is inserted into the slot 124 and the electrical terminals of the informal mobile battery 20 and the electrical terminals of the slot 124 are mounted together, the use condition of the informal mobile battery 20 may deviate from the appropriate range. In addition, since the battery exchanger 120 is used by a plurality of users 40, the informal mobile battery 20 may be paid out to another user 40 different from the user 40 who inserted the informal mobile battery 20 into the slot 124.

[0050] The non-compliant mobile battery 20 is not limited to a mobile battery 20 having different specifications from the mobile battery 20 managed by the battery management system 100 (sometimes referred to as a compliant mobile battery 20). The non-compliant mobile battery 20 may have the same specifications as the compliant mobile battery 20, or may have specifications corresponding to the compliant mobile battery 20.

[0051] For example, in the case where the user 40 of the electric bicycle 30 purchases the mobile battery 20, if the user 40 does not join the charging service of the mobile battery 20 or the exchange service of the mobile battery 20 based on the battery management system 100, the mobile battery 20 purchased by the user 40 is regarded as an informal mobile battery 20 having the same specifications as the formal mobile battery 20. According to the present embodiment, the battery management system 100 manages the degradation state of the formal mobile battery 20 and performs maintenance or exchange of the mobile battery 20 at an appropriate timing. As a result, the user 40 can use the mobile battery 20 safely. In addition, since the mobile battery 20 with less degradation is provided, the use experience of the user 40 is improved.

[0052] On the other hand, the battery management system 100 cannot grasp the maintenance management status of the non-regular mobile battery 20. Therefore, when the mobile battery 20 that is not properly maintained is mixed in the mobile batteries 20 stored in the battery exchanger 120, the user 40's usage experience may be reduced. Therefore, according to the present embodiment, when the mobile battery 20 is installed in the slot 124, the battery exchanger 120 performs the authentication process of the mobile battery 20.

[0053] The authentication method for the mobile battery 20 includes: (i) a method in which the electric bicycle 30 or the battery switch 120 obtains identification information (sometimes referred to as a battery ID) of the mobile battery 20 to be authenticated, and compares the battery ID of the mobile battery 20 to be authenticated with a list of battery IDs of regular mobile batteries 20 (sometimes referred to as a white list); and (ii) a method in which the electric bicycle 30 or the battery switch 120 authenticates the mobile battery 20 by sending and receiving an authentication code using public key encryption.

[0054] However, according to the above method, it is difficult to effectively suppress the leakage of the battery ID and the like due to eavesdropping, repetitive attacks, etc. For example, in the case of authenticating the mobile battery 20 using a white list of battery IDs, if the battery ID registered in the white list is leaked, it is difficult to suppress the circulation of counterfeit mobile batteries 20. In addition, in the case of authenticating the mobile battery 20 by a public key encryption method, when the public key is leaked, it is difficult to suppress the circulation of counterfeit mobile batteries 20. In particular, when the public keys of a plurality of batteries are the same, the damage caused by imitation increases.

[0055] Therefore, in this embodiment, the battery management system 100 authenticates the mobile battery 20 by public key encryption. Thus, the battery management system 100 can solve the above problem and confirm whether the mobile battery 20 installed in the slot 124 is a legitimate mobile battery 20.

[0056] In addition, according to the present embodiment, the battery exchanger 120 authenticates the mobile battery 20 by public key encryption. As the public key encryption, a known method can be adopted. As the cipher of the public key encryption, RSA cipher, elliptic curve cipher, etc. can be exemplified.

[0057] Since the computing performance of the processor mounted on the mobile battery 20 or the electric bicycle 30 is relatively low, it is difficult to perform complex calculations on the mobile battery 20 or the electric bicycle 30 side. On the other hand, the battery switch 120 can be equipped with a processor having better computing power than the processor mounted on the mobile battery 20 or the electric bicycle 30. Compared with the public key encryption method, the calculation load of the public key encryption method is large. Therefore, in the case of authenticating the mobile battery 20 by the public key encryption method, the processor that performs the authentication process needs to perform complex calculations at high speed. In this regard, the battery switch 120 can use a high-performance processor to authenticate the mobile battery 20 by the public key encryption method.

[0058] Specifically, first, the key issuer 50 issues a pair of authentication private key 72 and authentication public key 74 for each of the more than one mobile battery 20. The key issuer 50 may be a manufacturer or transferor of the mobile battery 20, a manufacturer or transferor of the battery switch 120, or an administrator or operator of the battery management system 100. The key issuer 50 may be a natural person, a legal person, an organization, a member of the legal person or organization, an employee, etc. The key issuer 50 may use the communication terminal 52 to issue a pair of authentication private key 72 and authentication public key 74.

[0059] Next, the key issuer 50 causes the authentication private key 72 of each of the more than one mobile batteries 20 to be stored in a storage device (not shown) of each of the more than one mobile batteries 20. In one embodiment, the key issuer 50 can connect the communication terminal 52 and the mobile battery 20 in a communicative manner, and cause the communication terminal 52 to send the authentication private key 72 corresponding to the mobile battery 20 connected to the communication terminal 52 to the mobile battery 20. The communication terminal 52 and the mobile battery 20 can send and receive information through wired communication or wireless communication. In another embodiment, the key issuer 50 can input the authentication private key 72 into an input device provided in the mobile battery 20, or can install a storage device storing the authentication private key 72 on the mobile battery 20.

[0060] In addition, the key issuer 50 stores the authentication public key 74 of the one or more mobile batteries 20 in a storage device (not shown) of the one or more battery switches 120. In one embodiment, the key issuer 50 sets the authentication public key 74 of each of the one or more mobile batteries 20 to a state that can be obtained by each of the one or more battery switches 120. For example, the key issuer 50 operates the communication terminal 52 to set so that each of the one or more battery switches 120 can access a database, which stores the battery ID and the authentication public key 74 in association with each of the one or more mobile batteries 20. The above database can be stored in the communication terminal 52, and can also be stored in the management server 140.

[0061] In another embodiment, the key issuer 50 can communicatively connect the communication terminal 52 and the battery switch 120, and transmit the above-mentioned database from the communication terminal 52 to the battery switch 120. The communication terminal 52 and the battery switch 120 can send and receive information through wired communication or wireless communication. In another embodiment, the key issuer 50 can input the above-mentioned database from an input device provided in the battery switch 120, or a storage device storing the above-mentioned database can be installed on the battery switch 120. When the battery switch 120 is manufactured, shipped, transferred or installed, the above-mentioned database is stored in the storage device of the battery switch 120. In addition, the above-mentioned database can be appropriately updated.

[0062] In this state, when the user 40 inserts the mobile battery 20 into the slot 124 of the battery switch 120 and the mobile battery 20 is installed in the slot 124, the battery switch 120 first acquires the battery ID of the mobile battery 20 installed in the slot 124. The battery switch 120 may acquire the battery ID of the mobile battery 20 from the mobile battery 20, or may acquire the battery ID of the mobile battery 20 from the communication terminal 42.

[0063] Next, the battery switch 120 obtains the authentication public key 74 of the mobile battery 20 installed in the slot 124 based on the battery ID. In one embodiment, the battery switch 120 uses the battery ID as a key, refers to a database stored in a storage device of the battery switch 120, and obtains the authentication public key 74 of the mobile battery 20 installed in the slot 124. In another embodiment, the battery switch 120 accesses the communication terminal 52 or the management server 140, uses the battery ID as a key, refers to a database stored in the communication terminal 52 or the management server 140, and obtains the authentication public key 74 of the mobile battery 20 installed in the slot 124.

[0064] Next, the battery switch 120 prepares a code (sometimes referred to as an authentication code) for authenticating the mobile battery 20 installed in the slot 124. The authentication code may be a combination of numbers, characters, and symbols. The authentication code may be image data or audio data. The authentication code may be generated at each authentication, or may be generated each time a predetermined validity period has passed. The authentication code may be a code predetermined for each mobile battery 20. For example, whenever an authentication process is performed, the battery switch 120 generates a random number and uses the random number as the authentication code.

[0065] Next, the battery switch 120 transforms the authentication code based on the authentication public key 74 of the mobile battery 20 installed in the slot 124. Specifically, the battery switch 120 encrypts the authentication code using the authentication public key 74 of the mobile battery 20 installed in the slot 124. Thus, a challenge code including the encrypted authentication code is generated.

[0066] The battery switch 120 sends the generated challenge code to the mobile battery 20 and requests the mobile battery 20 to respond to the challenge code. As a response to the challenge code, a response code including information indicating that the mobile battery 20 successfully decrypted the authentication code encrypted with the authentication public key 74 is sent.

[0067] As information indicating that the mobile battery 20 has successfully decrypted the authentication code encrypted with the authentication public key 74, (i) the decrypted authentication code and (ii) information generated by performing information processing on the decrypted authentication code according to a predetermined algorithm (sometimes referred to as a first algorithm) are exemplified. Examples of the first algorithm include an algorithm related to arithmetic processing using a predetermined function (sometimes referred to as a first function), an algorithm related to encryption processing using predetermined information, and the like. As the above-mentioned function, a hash function is exemplified.

[0068] The encryption process may be a public key encryption process using a public key or a public key encryption process using a public key and a private key. Examples of the public key encryption process include the RSA cryptography and elliptic curve cryptography.

[0069] When the mobile battery 20 receives the challenge code and the response request to the challenge code (sometimes referred to as an authentication response request), the authentication code encrypted by the authentication public key 74 is decrypted using the authentication private key 72 of the mobile battery 20. When the mobile battery 20 successfully decrypts the authentication code encrypted with the authentication public key 74, the decrypted authentication code is obtained. Thus, the mobile battery 20 can generate a decrypted authentication code using the challenge code or the authentication code encrypted by the authentication public key 74 contained in the challenge code and the authentication private key 72 of the mobile battery 20.

[0070] Then, the mobile battery 20 generates a response code according to a predetermined rule. The above rule may be information indicating the type or generation process of information indicating that the mobile battery 20 successfully decrypts the authentication code encrypted by the authentication public key 74. In addition, the mobile battery 20 sends the generated response code to the battery switch 120 as a response to the authentication response request.

[0071] In one embodiment, the above rule indicates using the decrypted authentication code as information indicating that the mobile battery 20 successfully decrypts the authentication code encrypted by the authentication public key 74. In this case, the mobile battery 20 generates a response code including the decrypted authentication code.

[0072] In another embodiment, the above rule indicates that information generated by performing information processing on the decrypted authentication code according to the first algorithm (sometimes referred to as the first processed value of the decrypted authentication code) is used as information indicating that the mobile battery 20 successfully decrypted the authentication code encrypted with the authentication public key 74. In this case, the mobile battery 20 generates the above first processed value by performing information processing on the decrypted authentication code according to the first algorithm. In addition, the mobile battery 20 generates a response code including the above first processed value. By using the response code including the above first processed value, leakage of the authentication code due to eavesdropping, repeat attacks, etc., reverse analysis of the authentication algorithm, etc. can be suppressed.

[0073] For example, in the case where the first algorithm is an algorithm related to arithmetic processing using a hash function, the mobile battery 20 generates a response code including a hash value of the decrypted authentication code. When the first algorithm is a public key encryption processing using a public key, the mobile battery 20 generates a response code including a ciphertext obtained by encrypting the decrypted authentication code using the public key. When the first algorithm is a public key encryption processing using a public key and a private key, the mobile battery 20 generates a response code including a ciphertext obtained by encrypting the decrypted authentication code using the private key or the public key.

[0074] Next, the battery switch 120 receives the response code from the mobile battery 20. Based on the response code, the battery switch 120 confirms that the mobile battery 20 successfully decrypts the authentication code encrypted with the authentication public key 74.

[0075] In one embodiment, when the above-mentioned response code includes the decrypted authentication code, the battery switch 120 compares the authentication code generated by the battery switch 120 with the authentication code included in the response code. For example, the battery switch 120 determines whether the authentication code generated by the battery switch 120 matches the authentication code included in the response code. In addition, the battery switch 120 confirms whether the mobile battery 20 successfully decrypts the authentication code encrypted by the authentication public key 74 based on the comparison result. Thus, the battery switch 120 can confirm whether the mobile battery 20 installed in the slot 124 is a regular mobile battery 20.

[0076] For example, when the authentication code generated by the battery switch 120 matches the restored authentication code included in the response code, the battery switch 120 confirms that the mobile battery 20 installed in the slot 124 is a regular mobile battery 20. On the other hand, when the authentication code generated by the battery switch 120 does not match the restored authentication code included in the response code, the battery switch 120 confirms that the mobile battery 20 installed in the slot 124 is not a regular mobile battery 20, or the mobile battery 20 installed in the slot 124 is an irregular mobile battery 20.

[0077] In another embodiment, when the above-mentioned response code includes the first processed value of the decrypted authentication code, the battery switch 120 compares the information generated by performing information processing on the authentication code generated by the battery switch 120 according to the first algorithm (sometimes referred to as the first processed value of the authentication code generated by the battery switch 120) with the first processed value of the decrypted authentication code included in the response code. For example, the battery switch 120 determines whether the first processed value of the authentication code generated by the battery switch 120 matches the first processed value of the decrypted authentication code. In addition, the battery switch 120 confirms whether the mobile battery 20 has successfully decrypted the authentication code encrypted by the authentication public key 74 based on the comparison result. Thus, the battery switch 120 can confirm whether the mobile battery 20 installed in the slot 124 is a regular mobile battery 20.

[0078] For example, when the first processed value of the authentication code generated by the battery switch 120 matches the first processed value of the restored authentication code included in the response code, the battery switch 120 confirms that the mobile battery 20 installed in the slot 124 is a regular mobile battery 20. On the other hand, when the first processed value of the authentication code generated by the battery switch 120 does not match the first processed value of the restored authentication code included in the response code, the battery switch 120 confirms that the mobile battery 20 installed in the slot 124 is not a regular mobile battery 20, or the mobile battery 20 installed in the slot 124 is an irregular mobile battery 20.

[0079] In another embodiment, when the response code includes the first processed value of the decrypted authentication code, the battery switch 120 compares the authentication code generated by the battery switch 120 with information (sometimes referred to as the second processed value of the restored authentication code) generated by performing information processing on the first processed value of the decrypted authentication code included in the response code according to the second algorithm. For example, the battery switch 120 determines whether the authentication code generated by the battery switch 120 matches the second processed value of the decrypted authentication code. In addition, the battery switch 120 confirms whether the mobile battery 20 has successfully decrypted the authentication code encrypted by the authentication public key 74 based on the comparison result. Thus, the battery switch 120 can confirm whether the mobile battery 20 installed in the slot 124 is a regular mobile battery 20.

[0080] The second algorithm may be an algorithm related to an operation process using a second function that is an inverse function of the first function, or an algorithm related to a decryption process for decrypting information encrypted by an encryption process of the first algorithm. The decryption process may be a decryption process using key information used to encrypt the first algorithm or key information paired with the key information.

[0081] For example, when the authentication code generated by the battery switch 120 matches the second processed value of the restored authentication code included in the response code, the battery switch 120 confirms that the mobile battery 20 installed in the slot 124 is a regular mobile battery 20. On the other hand, when the authentication code generated by the battery switch 120 does not match the second processed value of the restored authentication code included in the response code, the battery switch 120 confirms that the mobile battery 20 installed in the slot 124 is not a regular mobile battery 20, or that the mobile battery 20 installed in the slot 124 is an irregular mobile battery 20.

[0082] As described above, the battery switch 120 can confirm that the mobile battery 20 is a regular mobile battery 20 while effectively suppressing the leakage of the authentication code. In addition, the battery switch 120 can confirm that the mobile battery 20 installed in the slot 124 is not a regular mobile battery 20, or that the mobile battery 20 installed in the slot 124 is an irregular mobile battery 20 while effectively suppressing the leakage of information such as the authentication code used to authenticate a legitimate device.

[0083] As described above, the battery switch 120 is configured to be able to exchange the mobile battery 20. Therefore, the battery switch 120 can determine whether to exchange the mobile battery 20 based on the above-mentioned confirmation result. The battery switch 120 can determine whether to exchange the mobile battery 20 based on information (sometimes referred to as a white list) for identifying mobile batteries 20 that can be used in common among a plurality of mobile batteries 20. The battery switch 120 can determine whether to exchange the mobile battery 20 based on the above-mentioned confirmation result and the white list.

[0084] Similarly, the battery switch 120 is configured to be able to charge or discharge the mobile battery 20. Therefore, the battery switch 120 can determine whether the mobile battery 20 is charged or discharged based on the above confirmation result. The battery switch 120 can determine whether the mobile battery 20 is charged or discharged based on the white list. The battery switch 120 can determine whether the mobile battery 20 is charged or discharged based on the above confirmation result and the white list.

[0085] Overview of each unit related to the battery management system 100

[0086] In this embodiment, the communication network 14 transmits information. The communication network 14 may be a transmission line for wired communication, a transmission line for wireless communication, or a combination of a transmission line for wireless communication and a transmission line for wired communication. The communication network 14 may include a wireless packet communication network, the Internet, a P2P network, a dedicated line, a VPN, a power line communication line, etc.

[0087] The communication network 14 may include (i) a mobile communication network such as a cellular phone line network and (ii) a wireless communication network such as a wireless MAN (e.g., WiMAX (registered trademark)), a wireless LAN (e.g., WiFi (registered trademark)), Bluetooth (registered trademark), Zigbee (registered trademark), and NFC (Near Field Communication). Wireless LAN, Bluetooth (registered trademark), Zigbee (registered trademark), and NFC may be examples of short-range wireless communications.

[0088] In the present embodiment, the mobile battery 20 stores electric energy. The mobile battery 20 may be configured to be detachably connected to the electric bicycle 30 (sometimes referred to as detachable). The mobile battery 20 may be configured to be detachably connected to the battery exchanger 120. Thus, the user 40 can exchange the mobile battery 20 mounted on the electric bicycle 30 and the mobile battery 20 accommodated in the battery exchanger 120.

[0089] In one embodiment, the mobile battery 20 is mounted on the electric bicycle 30 and supplies power to the electric bicycle 30. As described above, the mobile battery 20 may be detachably mounted on the electric bicycle 30. In another embodiment, when the mobile battery 20 is accommodated in the battery exchanger 120, the mobile battery 20 is charged by the battery exchanger 120.

[0090] Note that when the mobile battery 20 is accommodated in the battery switch 120, the mobile battery 20 can supply power to the battery switch 120. Thus, the battery switch 120 can use a part of the mobile battery 20 accommodated in the battery switch 120 as, for example, an uninterruptible power supply device (sometimes referred to as UPS).

[0091] In the present embodiment, the mobile battery 20 stores the authentication private key 72. The authentication private key 72 may be stored in any type of storage device (not shown) provided in the mobile battery 20. The mobile battery 20 may store various keys for various encryption processes and / or decryption processes performed with the battery switch 120. Examples of the above keys include a private key for electronic signature, a public key for electronic signature, and the like.

[0092] In the present embodiment, the electric bicycle 30 is equipped with the mobile battery 20. The electric bicycle 30 may be equipped with a plurality of mobile batteries 20. The electric bicycle 30 uses the power stored in the mobile battery 20. For example, the electric bicycle 30 consumes the power supplied from the mobile battery 20 to travel.

[0093] In this embodiment, the communication terminal 42 sends and receives information to each unit of the battery management system 100 via the communication network 14. The communication terminal 42 can be used as a user interface when the user 40 accesses the battery management system 100. The communication terminal 42 can be used for user authentication processing of the battery management system 100.

[0094] Examples of the communication terminal 42 include a personal computer, a portable terminal, etc. Examples of the portable terminal include a mobile phone, a smartphone, a PDA, a tablet computer, a notebook computer or a laptop computer, a wearable computer, etc.

[0095] In the present embodiment, the communication terminal 52 transmits and receives information to each unit of the battery management system 100 via the communication network 14. When the key issuer 50 accesses the battery management system 100, the communication terminal 52 may be used as a user interface.

[0096] The communication terminal 52 may be used for the process of generating various keys such as the authentication private key 72 and the authentication public key 74. The communication terminal 52 may store the generated authentication private key 72 in the storage device of the mobile battery 20 corresponding to the key. After the authentication private key 72 is stored in the mobile battery 20, the communication terminal 52 may erase the authentication private key 72 from the storage device of the communication terminal 52. The communication terminal 52 may store the generated authentication public key 74 in the storage device of one or more battery switches 120. For each of the one or more mobile batteries 20, the communication terminal 52 may have a database storing the battery ID in association with the above-mentioned various public keys. The above-mentioned database may store the battery ID of each of the one or more mobile batteries 20 in association with the authentication public key 74 of each of the one or more mobile batteries 20.

[0097] The communication terminal 52 may be configured to be able to wirelessly communicate with one or more battery switches 120. The communication terminal 52 may be an information processing device that has confirmed at least one of the one or more battery switches 120 as being legitimate. The communication terminal 52 may be an information processing device that can be trusted for one or more battery switches 120. The communication terminal 52 may be configured to be able to wirelessly communicate with one or more mobile batteries 20. The communication terminal 52 may be an information processing device that has confirmed at least one of the one or more mobile batteries 20 as being legitimate. The communication terminal 52 may be an information processing device that can be trusted for one or more mobile batteries 20.

[0098] Examples of the communication terminal 52 include a personal computer, a portable terminal, etc. Examples of the portable terminal include a mobile phone, a smartphone, a PDA, a tablet computer, a notebook computer or a laptop computer, a wearable computer, etc.

[0099] In the present embodiment, the battery switch 120 accommodates the mobile battery 20. The battery switch 120 may accommodate a plurality of mobile batteries 20. Thus, the battery switch 120 may store more than one mobile battery 20. In the present embodiment, the battery switch 120 charges at least one of the more than one mobile batteries 20. The battery switch 120 may charge the mobile battery 20 until the charging rate or voltage of the mobile battery 20 reaches a predetermined setting value.

[0100] In the present embodiment, the battery switch 120 allows the mobile battery 20 that has been fully charged to be in a removable state (sometimes referred to as disbursement). The battery switch 120 can disburse the mobile battery 20 that matches the request in response to a request from the user 40. The battery switch 120 can obtain information indicating a disbursement condition that is a condition related to the mobile battery 20 to be disbursed from the management server 140, and determine the mobile battery 20 that is actually to be disbursed from the mobile batteries 20 that satisfy the disbursement condition.

[0101] Note that, in another embodiment, the battery switch 120 may discharge at least a portion of the plurality of mobile batteries 20. The battery switch 120 may use the power output by the discharge of the mobile batteries 20. For example, the battery switch 120 operates by consuming the power output by the discharge of the mobile batteries 20. When the battery switch 120 operates by consuming the power output by the discharge of one mobile battery 20, the charging operation of another mobile battery 20 may be stopped or interrupted. Even in this case, the battery switch 120 may continue the discharging operation of the mobile batteries 20.

[0102] Thus, the battery switch 120 can use a part of the mobile battery 20 accommodated in the battery switch 120 as an uninterruptible power supply device. According to the battery switch 120 of the present embodiment, for example, even in the case where an abnormality occurs in the power supply from the power system 12 to the battery switch 120, power can continue to be supplied to the control device. As a result, for example, the battery switch 120 can continue to pay out the mobile battery 20. Therefore, even in the case where, for example, the battery switch 120 is installed in an area where the frequency of power outages is relatively high, an environment in which batteries can be stably exchanged can be provided.

[0103] In the present embodiment, the storage unit 122 holds a plurality of slots 124. In the present embodiment, the storage unit 122 is formed independently of the communication unit 126. The storage unit 122 may be installed separately from the communication unit 126, or may be installed adjacent to the communication unit 126.

[0104] In addition, in the present embodiment, the storage unit 122 generates a processing flow including one or more processes for controlling the operation of at least one of the plurality of slots 124 based on the first command sent from the communication unit 126. For each of the one or more processes, the storage unit 122 determines whether each process can be executed. For the process determined to be executable, the storage unit 122 generates a second command for controlling the slot 124 that is the object of the process. The storage unit 122 controls the operation of the above-mentioned slot 124 based on the generated second command. Thus, the execution of a part of the instruction represented by the first command can be restricted.

[0105] For example, in the case where one or more of the above-mentioned processes include operations related to the safety of the mobile battery 20 or the safety of the user 40 or the maintenance personnel of the battery switch 120, the storage unit 122 determines whether the conditions for allowing the execution of the safety-related operations are satisfied. When it is determined that the above-mentioned conditions are satisfied, the storage unit 122 determines that the process can be executed. Thus, the operation of the slot 124 is controlled based on the second command related to the above-mentioned process. On the other hand, when it is determined that the above-mentioned conditions are not satisfied, the storage unit 122 determines that the process cannot be executed. In this case, the second command related to the above-mentioned process is not sent to the slot 124.

[0106] Thus, even in the case where the communication unit 126 outputs the first command based on the request from the management server 140, the safety of the mobile battery 20, the user 40, or the above-mentioned maintenance personnel can be ensured. For example, even in the case where the state of the battery switch 120 changes after the management server 140 sends the above-mentioned request, the management server 140 can cancel the above-mentioned request when the communication environment of the battery switch 120 is good. However, it is also considered that it takes time for the management server 140 to cancel the above-mentioned request when the communication environment of the battery switch 120 is not satisfactory. According to the present embodiment, since the storage unit 122 determines whether the second command can be executed based on the state of the battery switch 120, the battery switch 120 can stop or interrupt the execution of part of the processing without waiting for the cancellation request from the management server 140.

[0107] In the present embodiment, each of the plurality of slots 124 is configured to be able to store at least one of the one or more mobile batteries 20. At least one of the one or more mobile batteries 20 is mounted on each of the plurality of slots 124. In addition, each of the plurality of slots 124 is provided with an electrical terminal (not shown) electrically connected to an electrical terminal (not shown) of the one or more mobile batteries 20. Thus, each of the plurality of slots 124 can charge or discharge the mobile battery 20 stored in each slot.

[0108] Note that "electrical connection" is not limited to the case where two elements are directly physically connected. A third element can be inserted between the above two elements. In addition, the case where the above two elements are physically connected is not limited. For example, the input winding and the output winding of the transformer are not physically connected, but electrically connected. Thus, in the slot 124, not only the wired charging and discharging of the mobile battery 20 can be supported, but also the wireless charging and discharging of the mobile battery 20 can be supported.

[0109] Each of the plurality of slots 124 may be provided with a communication terminal that can be communicatively connected to the communication terminal of one or more mobile batteries 20. The communication method between the communication terminal of the slot 124 and the communication terminal of the mobile battery 20 may be a wired communication method or a wireless communication method. Thus, each of the plurality of slots 124 can read information from a storage device (not shown) of the mobile battery 20 stored in each slot or write information to the storage device.

[0110] In the present embodiment, the communication unit 126 is responsible for information processing involving at least one of the user 40 and the management server 140 in the information processing in the battery switch 120. For example, the communication unit 126 receives a request from at least one of the user 40 and the management server 140 and responds to the request. When the communication unit 126 determines that the storage unit 122 is required in order to process the request from at least one of the user 40 and the management server 140, the communication unit 126 sends a command (sometimes referred to as an instruction) to the storage unit 122. The above-mentioned first command may be an example of a command.

[0111] When the communication unit 126 can process a request from at least one of the user 40 and the management server 140 without cooperating with the storage unit 122, the communication unit 126 may not send a command to the storage unit 122. Thus, information processing in the storage unit 122 is simplified. For example, the communication unit 126 can perform communication control processing with the outside of the battery switch 120, authentication processing of the user 40, selection processing of the slot 124, etc. without cooperating with the storage unit 122.

[0112] As described above, in the present embodiment, the communication unit 126 is formed independently of the storage unit 122. The storage unit 122 may be installed separately from the communication unit 126, or may be installed adjacent to the communication unit 126.

[0113] The communication interface 128 is configured to be able to communicate with an information processing device outside the battery switch 120. The communication interface 128 can support multiple communication methods. The communication interface 128 can support a wired communication method or a wireless communication method. In one embodiment, the communication interface 128 sends and receives information with the communication terminal 42 used by the user 40. In another embodiment, the communication interface 128 sends and receives information with the management server 140.

[0114] In the present embodiment, the management server 140 is provided outside the battery switch 120. In addition, the management server 140 can transmit and receive information with the communication unit 126 of the battery switch 120 via the communication network 14.

[0115] In the present embodiment, the management server 140 manages more than one mobile battery 20. For example, the management server 140 manages the state of each of the more than one mobile battery 20. The management server 140 can manage the return and payment of each of the more than one mobile battery 20. The management server 140 can send various requests for managing the mobile battery 20 to at least one of the more than one battery switches 120.

[0116] The management server 140 may manage more than one battery switch 120. The management server 140 may manage the state of each of the more than one battery switch 120. As the state of the battery switch 120, the supply state of external power, the number of acceptable mobile batteries 20, the number of expendable mobile batteries 20, the presence or absence of mobile batteries 20 that can be used as an uninterruptible power supply, the number or identification information thereof, the charging state of the above-mentioned mobile batteries 20, etc. are exemplified. The management server 140 may send various requests for managing the battery switch 120 to at least one of the more than one battery switches 120.

[0117] The management server 140 may determine a payment condition for at least a part of the one or more battery switches 120, the payment condition being a condition related to the mobile battery 20 to be paid. As payment conditions, priority related to the payment of each of the plurality of mobile batteries 20 accommodated in the battery switch 120, identification information of the mobile battery 20 to be paid preferentially, characteristics of the mobile battery 20 to be paid preferentially, etc. are exemplified.

[0118] In the present embodiment, the management server 140 may be used for distribution processing of various keys such as the authentication public key 74. The management server 140 may have a database that stores the battery ID and the various keys in association with each of the one or more mobile batteries 20. The database may store the battery ID of each of the one or more mobile batteries 20 in association with the authentication public key 74 of each of the one or more mobile batteries 20. The management server 140 may extract the authentication public key 74 of the mobile battery 20 indicated by the request from each of the one or more battery switches 120, and transmit the extracted authentication public key 74.

[0119] The management server 140 may be configured to be able to wirelessly communicate with one or more battery switches 120. The management server 140 may be an information processing device that has confirmed that at least one of the one or more battery switches 120 is legitimate. The management server 140 may be an information processing device that can be trusted for the one or more battery switches 120. The management server 140 may be configured to be able to wirelessly communicate with one or more mobile batteries 20. The management server 140 may be an information processing device that has confirmed that at least one of the one or more mobile batteries 20 is legitimate. The management server 140 may be an information processing device that can be trusted for the one or more mobile batteries 20.

[0120] The mobile battery 20 may be an example of a device to be confirmed, a second power device, or a power storage device. The key issuer 50 may be an example of a manufacturer or transferor of a confirmation device, a manufacturer or transferor of a device to be confirmed, or an issuer of the second information and the fourth information. The communication terminal 52 may be an example of a first external device or a second external device. The battery management system 100 may be an example of a confirmation device or a confirmation system. The battery switch 120 may be an example of a confirmation device, a first power device, or a storage device. The storage unit 122 may be an example of a first power device or a storage device. The slot 124 may be an example of a first power device, a storage device, or an installation unit. The management server 140 may be an example of a first external device or a second external device.

[0121] The authentication code may be an example of the first information. The authentication public key 74 may be an example of the second information. The authentication code encrypted by the authentication public key 74 may be an example of the third information. The challenge code may be an example of the third information. The authentication private key 72 may be an example of the fourth information. The decrypted authentication code may be an example of the fifth information. The first processed value of the decrypted authentication code may be an example of the sixth information. The first processed value of the authentication code generated by the battery switch 120 may be an example of the seventh information. The second processed value of the restored authentication code may be an example of the eighth information. The information encrypted for the first algorithm may be an example of the ninth information. The information decrypted for the second algorithm may be an example of the ninth information or the tenth information.

[0122] Encryption may be an example of transformation of information. Decryption may be an example of inverse transformation of information. A regular mobile battery 20 may be an example of a legitimate device. An irregular mobile battery 20 may be an example of an illegal device. A whitelist may be an example of commonly used identification information. A method of authenticating the mobile battery 20 may be an example of a method of confirming the mobile battery 20.

[0123] The authentication code may be an example of the first authentication information. The authentication public key 74 may be an example of the second authentication information. The authentication code encrypted with the authentication public key 74 may be an example of the third authentication information. The authentication private key 72 may be an example of the fourth authentication information. The authentication private key 72 may be an example of the first private key. The authentication public key 74 may be an example of the first public key corresponding to the first private key.

[0124] Another Example of Implementation

[0125] In this embodiment, the battery management system 100 is described in detail by taking the case where the battery management system 100 provides a shared service for the mobile battery 20 as an example. However, the service provided by the battery management system 100 is not limited to this embodiment. In another embodiment, the battery management system 100 can provide a charging service for the mobile battery 20 to the user 40 of the mobile battery 20.

[0126] In the present embodiment, the battery switch 120 is described in detail by taking the case where the battery switch 120 is operated using the power received from the power system 12 as an example. However, the battery switch 120 is not limited to the present embodiment. In another embodiment, for example, when at least one of the one or more slots 124 provided in the battery switch 120 includes a bidirectional DC / DC converter, the battery switch 120 can be operated using the power discharged from at least one of the one or more mobile batteries 20 stored in the battery switch 120.

[0127] In this embodiment, the battery management system 100 is described in detail by taking the case where the battery switch 120 includes more than one storage unit 122 and a single communication unit 126 as an example. However, the battery switch 120 is not limited to this embodiment. In another embodiment, the battery switch 120 may include multiple storage units 122 and multiple communication units 126. In this case, the number of storage units 122 may be greater than the number of communication units 126.

[0128] In this embodiment, the battery management system 100 is described in detail by taking the case where each of the more than one battery switches 120 obtains the authentication public key 74 of the more than one mobile battery 20 from the key issuer 50, the communication terminal 52 or the management server 140 as an example. However, the method of obtaining the authentication public key 74 in the battery switch 120 is not limited to this embodiment. In another embodiment, each of the more than one battery switches 120 can obtain the authentication public key 74 of the mobile battery from the mobile battery 20 installed in the slot 124.

[0129] In the present embodiment, an example of a method for authenticating the mobile battery 20 is described by taking as an example a case where (i) the battery switch 120 generates an authentication code, (ii) the battery switch 120 encrypts the generated authentication code with the authentication public key 74 to generate a challenge code, and (iii) the mobile battery 20 decrypts the encrypted authentication code contained in the challenge code with the authentication private key 72 to generate a response code. However, the method for authenticating the mobile battery 20 is not limited to the present embodiment. According to another embodiment, an electronic signature or an electronic certificate is used to authenticate the mobile battery 20. An example of an authentication process using an electronic signature is as follows.

[0130] For example, the mobile battery 20 first generates an authentication code. Next, the mobile battery 20 signs the authentication code using a private key. Specifically, the mobile battery 20 encrypts the authentication code using a private key. At this time, the mobile battery 20 can encrypt data (sometimes referred to as a message) containing the authentication code and information and / or temporary information (e.g., time information indicating the time when the signature was signed) sent from the battery switch 120 using a private key. Thus, damage caused by repeated attacks is suppressed.

[0131] For example, the mobile battery 20 sends the battery ID, the generated authentication code (plain text) and the encrypted information (sometimes referred to as cipher text) to the battery switch 120 in association. As described above, the cipher text may be data in which the authentication code is encrypted. The cipher text may be data in which the message is encrypted.

[0132] Next, when the battery switch 120 receives the above data from the mobile battery 20, the battery switch 120 performs a process for acquiring the public key of the mobile battery 20. For example, the battery switch 120 accesses a database of public keys stored in an arbitrary storage device to acquire the public key associated with the battery ID of the mobile battery 20. The battery switch 120 decrypts the ciphertext of the authentication code included in the data received from the mobile battery 20 using the public key of the mobile battery 20.

[0133] The battery switch 120 compares the decrypted authentication code with the authentication code (plain text) received from the mobile battery 20. For example, the battery switch 120 determines whether the decrypted authentication code matches the authentication code (plain text) received from the mobile battery 20. When the two match, the battery switch 120 confirms that the mobile battery 20 is authentic.

[0134] In this embodiment, the example of the method of the confirmation device authenticating the device to be confirmed is described by taking the case of generating a challenge code containing an encrypted authentication code as an example. However, the challenge code is not limited to this embodiment. In another embodiment, the challenge code may contain an unencrypted authentication code.

[0135] Another example of implementation of the subject of confirmation processing

[0136] In this embodiment, the case where the battery switch 120 authenticates the mobile battery 20 is taken as an example to describe in detail the confirmation method for the confirmation device to confirm whether the device to be confirmed is a legitimate device. However, the confirmation method is not limited to this embodiment.

[0137] Those skilled in the art who are familiar with the description of this specification can understand that, regardless of the specific combination of the confirmation device and the device to be confirmed, the confirmation device can confirm the device to be confirmed through the same process as the process of the battery switch 120 confirming the mobile battery 20. For example, in the case where the confirmation device is the mobile battery 20 and the device to be confirmed is the battery switch 120, the mobile battery 20 can confirm whether the battery switch 120 is a legitimate device through the same process as the process of the battery switch 120 confirming the mobile battery 20.

[0138] For example, the confirmation device is not limited to the battery switch 120. The subject of authenticating the mobile battery 20 may be (i) a device configured to be electrically connectable to the mobile battery 20, (ii) a device configured to supply power to the mobile battery 20, or (iii) a device configured to receive power from the mobile battery 20 (these devices are sometimes referred to as power devices). Similarly, the device to be confirmed is not limited to the mobile battery 20. For example, in the case where the mobile battery 20 authenticates another device, the object authenticated by the mobile battery 20 may be (i) a device configured to be electrically connectable to the mobile battery 20, (ii) a device configured to supply power to the mobile battery 20, or (iii) a device configured to receive power from the mobile battery 20 (these devices are sometimes referred to as power devices).

[0139] Examples of the power device include the electric bicycle 30, the battery exchanger 120, etc. Another example of the power device includes (a) a charger having a function of charging the mobile battery 20 but not having a function of supplying power to the outside, (b) a power supply device that is equipped with one or more mobile batteries 20 and supplies power stored in the one or more mobile batteries 20 to the outside, and (c) a device having both a function of charging the mobile battery 20 (or a function of receiving power from the outside) and a function of discharging the mobile battery 20 (or a function of supplying power to the outside).

[0140] In another embodiment, the confirmation device may be the mobile battery 20, and the device to be confirmed may be the electric bicycle 30, the communication terminal 52, or the battery switch 120. In yet another embodiment, the confirmation device may be the electric bicycle 30, and the device to be confirmed may be the mobile battery 20. In yet another embodiment, the confirmation device may be the battery switch 120, and the device to be confirmed may be the communication terminal 52 or the management server 140. In yet another embodiment, the confirmation device may be the communication terminal 52, and the device to be confirmed may be the mobile battery 20, the battery switch 120, or the management server 140. In yet another embodiment, the confirmation device may be the management server 140, and the device to be confirmed may be the communication terminal 52 or the battery switch 120. In yet another embodiment, in the case where the mobile battery 20 and the management server 140 can send and receive information to each other, the confirmation device is the mobile battery 20, and the device to be confirmed may be the management server 140. In addition, the confirmation device may be the management server 140, and the device to be confirmed may be the mobile battery 20.

[0141] As described above, the mobile battery 20 may be an example of a confirmation device. The battery switch 120 may be an example of a device to be confirmed. The electric bicycle 30 may be an example of a confirmation device or a device to be confirmed. A regular battery switch 120 may be an example of a legal device. A regular electric bicycle 30 may be an example of a legal device. An authentication method for one device to authenticate another device may be an example of a confirmation method. A battery switch 120 that is not a legal device (sometimes referred to as an informal battery switch 120) may be an example of an informal device. An electric bicycle 30 that is not a legal device (sometimes referred to as an informal electric bicycle 30) may be an example of an informal device.

[0142] The confirmation device may be an example of one of the first device and the second device, and the device to be confirmed may be an example of the other of the first device and the second device. The confirmation device may be an example of one of the information processing device and the other information processing device, and the device to be confirmed may be an example of the other of the information processing device and the other information processing device.

[0143] The power device may be an example of an appliance. The storage device of the mobile battery 20 may be an example of a storage section.

[0144] Figure 2 The figure schematically shows an example of the internal structure of the mobile battery 20. In the present embodiment, the mobile battery 20 includes a power connector 212, a communication connector 214, a power storage unit 220, a control unit 230, an authentication corresponding unit 232, a sensing unit 240, and a storage unit 250. In the present embodiment, the storage unit 250 includes a battery ID storage unit 252 and an authentication private key storage unit 254.

[0145] In the present embodiment, the power connector 212 includes an electric terminal for transmitting and receiving power with the tank 124 or the electric bicycle 30. In the present embodiment, the communication connector 214 includes a communication terminal for transmitting and receiving information with the tank 124 or the electric bicycle 30. In the present embodiment, the power storage unit 220 includes a power storage unit for storing electric energy.

[0146] In the present embodiment, the control unit 230 controls the operation of the mobile battery 20. When the mobile battery 20 is stored in the slot 124, the control unit 230 may transmit and receive information with the storage unit 122.

[0147] In the present embodiment, the authentication corresponding part 232 corresponds to the authentication response request from the battery switch 120. For example, when the mobile battery 20 is installed in one slot 124 of the battery switch 120, the authentication corresponding part 232 receives the challenge code and the authentication response request from the battery switch 120. The authentication corresponding part 232 sends a response code to the battery switch 120 in response to the authentication response request. The details of the authentication corresponding part 232 will be described later.

[0148] In this embodiment, the sensing unit 240 acquires information indicating the state of the mobile battery 20. The sensing unit 240 may include various types of sensors. Examples of the sensors included in the sensing unit 240 include a temperature sensor, a voltage sensor, a current sensor, and the like.

[0149] The storage unit 250 stores various information about the mobile battery 20. For example, the storage unit 250 stores identification information of the mobile battery 20. The storage unit 250 may store identification information of the electric bicycle 30, the battery switch 120, or the slot 124 electrically connected to the mobile battery 20. The storage unit 250 may store an operation history of the mobile battery 20. For example, the storage unit 250 stores time in association with the measurement result of the sensing unit 240 as the operation history of the mobile battery 20.

[0150] In the present embodiment, the battery ID storage unit 252 stores the battery ID of the portable battery 20. In the present embodiment, the authentication key storage unit 254 stores the authentication key 72 of the portable battery 20.

[0151] The power connector 212 may be an example of an electric terminal or a second terminal. The power storage unit 220 may be an example of a power storage device. The authentication private key storage unit 254 may be an example of a preservation unit. The authentication corresponding unit 232 may be an example of a third information acquisition unit, a fifth information generation unit, or a response unit. The preservation unit 250 may be an example of a storage unit. The preservation of information may be an example of storage of information.

[0152] Figure 3 An example of the internal configuration of the battery switch 120 is schematically shown. In the present embodiment, the battery switch 120 includes one or more storage units 122, a communication unit 126, a communication line 310, an uninterruptible power supply device 312, and a router 314. In the present embodiment, each of the one or more storage units 122 includes a housing 320 and a mounted device 330. In the present embodiment, the mounted device 330 includes one or more slots 124, a sensor 332, a setting storage unit 334, and a control unit 336. In the present embodiment, the communication unit 126 includes a housing 360 and a mounted device 370. In the present embodiment, the mounted device 370 includes a communication interface 128, a user interface 372, a user identification unit 374, a control unit 376, and a battery authentication unit 378.

[0153] In the present embodiment, each of the one or more slots 124 is configured to be detachably connected to the mobile battery 20. In addition, each of the one or more slots 124 supplies power to the mobile battery 20 and charges the power storage unit 220 of the mobile battery 20. Each of the one or more slots 124 can receive power output from the mobile battery 20.

[0154] In the present embodiment, the communication line 310 connects each of the one or more storage units 122 to the communication unit 126. In the present embodiment, the uninterruptible power supply device 312 is provided between the power system 12 and the communication unit 126. For example, when an abnormality occurs in the power supply from the power system 12, the uninterruptible power supply device 312 supplies power to the communication unit 126. In the present embodiment, the router 314 relays or forwards the communication between the communication unit 126 and the communication network 14.

[0155] In this embodiment, the housing 320 holds the mounted device 330. There is no particular limitation on the shape and material of the housing 320. The housing 320 may have a box shape, a plate shape, or a frame shape.

[0156] In this embodiment, the mounted device 330 is mounted on the housing 320. The mounting mode of the mounted device 330 is not particularly limited. The mounted device 330 may be accommodated inside the housing 320, or may be mounted on the surface of the housing 320.

[0157] In this embodiment, the sensing unit 332 acquires information indicating the state of the slot 124 or the mobile battery 20 stored in the slot 124. The sensing unit 332 may include various types of sensors. Examples of sensors included in the sensing unit 240 include temperature sensors, voltage sensors, current sensors, and the like.

[0158] In this embodiment, the setting storage unit 334 stores various settings related to the storage unit 122. The setting storage unit 334 may include a physical switch or any type of storage medium, such as a memory or a hard disk. The above settings may be represented by (i) the on / off of a physical switch, or (ii) may be stored in a storage medium as electronic data. Examples of the above settings include settings regarding the ID of the storage unit 122, settings regarding the location of the storage unit 122, settings regarding whether various operations in the storage unit 122 can be performed, and the like.

[0159] In this embodiment, the control unit 336 controls the operation of the storage unit 122. Examples of the above-mentioned operation include attachment or detachment of the mobile battery 20 to the slot 124, charging or discharging of the mobile battery 20, and the like.

[0160] In one embodiment, the control section 336 controls the installation or removal of the mobile battery 20 relative to the slot 124. As the above-mentioned control, there are exemplified the locking control of a gate (not shown) provided in the slot 124, the control of a removal prevention member (not shown) provided in the slot 124, the control of a mechanism (not shown) for restraining the mobile battery 20 provided in the slot 124, the control of a movable connector (not shown) provided in the slot 124, etc. The movable connector may be a mechanical connector or an electric connector.

[0161] In another embodiment, the control unit 336 controls the charging or discharging of the mobile battery 20 stored in the slot 124. Examples of the above control include confirming the connection of the electrical terminal, adjusting the charging voltage, adjusting the charging current, adjusting the discharging voltage, adjusting the discharging current, etc. Thus, the charging or discharging of the mobile battery 20 via the electrical terminal can be controlled.

[0162] The control unit 336 can control the operation of the storage unit 122 based on the command received from the control unit 376. For example, based on the command received from the control unit 376, the control unit 336 generates a processing flow including one or more processes for controlling the operation of at least one of the plurality of slots 124. For each of the one or more processes, the control unit 336 determines whether each process can be executed. The control unit 336 generates a command for the process determined to be executable, and sends the command to the slot 124 that is the control object. On the other hand, for the process determined to be unexecutable, the above-mentioned command is not generated and sent.

[0163] The control unit 336 may send information indicating the result of the operation based on the command received from the control unit 376 to the control unit 376. For example, the control unit 336 sends information indicating whether the storage unit 122 has performed the operation based on the command received from the control unit 376 to the control unit 376.

[0164] In this embodiment, the housing 360 holds the mounted device 370. There is no particular limitation on the shape and material of the housing 360. The housing 360 may have a box shape, a plate shape, or a frame shape.

[0165] In this embodiment, the mounted device 370 is mounted on the housing 360. The mounting mode of the mounted device 370 is not particularly limited. The mounted device 370 may be accommodated inside the housing 360, or may be mounted on the surface of the housing 360.

[0166] In the present embodiment, the user interface 372 provides various information to the user 40 who uses the battery switch 120. In addition, the user interface 372 receives input from the user 40 who uses the battery switch 120. Examples of the user interface 372 include a display, a speaker, a keyboard, a pointing device, a touch panel, a microphone, a camera, a voice input system, a gesture input system, and the like.

[0167] In the present embodiment, the user identification unit 374 identifies the user 40 who uses the battery switch 120. As a method of identifying the user 40, a well-known method can be adopted. For example, the user identification unit 374 identifies the user 40 by analyzing an image of the user 40 and performing an authentication process of the user 40. The user identification unit 374 can identify the user 40 by performing an authentication process of the user 40 using an ID card held by the user 40. The user identification unit 374 can identify the user 40 by performing an authentication process of the user 40 using the communication terminal 42 carried by the user 40.

[0168] In the present embodiment, the control unit 376 is responsible for information processing involving at least one of the user 40 and the management server 140 in the information processing in the battery switch 120. For example, the control unit 376 receives a request from at least one of the user 40 and the management server 140 and responds to the request. When the control unit 376 determines that the storage unit 122 is required to process the request from at least one of the user 40 and the management server 140, the control unit 376 sends a command (for example, the above-mentioned first command) to the storage unit 122.

[0169] When the control section 376 can process a request from at least one of the user 40 and the management server 140 without cooperating with the storage unit 122, the control section 376 may not send a command to the storage unit 122. For example, the control section 376 may perform a communication control process with the outside of the battery switch 120, an authentication process of the user 40, a selection process of the slot 124, and the like without cooperating with the storage unit 122.

[0170] More specifically, when the control unit 376 receives a request from at least one of the user 40 and the management server 140, the control unit 376 first generates a processing flow including one or more processes for processing the request. Next, the control unit 376 extracts the processes including the processes in the storage unit 122 from the one or more processes. The control unit 376 generates a command indicating the content of the process in the storage unit 122 for each extracted process.

[0171] The command may include information indicating the storage unit 122 (sometimes referred to as the target unit) to be controlled. The command may include information indicating the slot 124 (sometimes referred to as the target slot) to be controlled. The command may include identification information of the target slot and information indicating the operation content in the target slot.

[0172] Thereafter, the control unit 376 transmits the command to the storage unit 122 that is the target of the command. The control unit 376 may acquire information indicating the execution result of the command from the storage unit 122 that has received the command.

[0173] The control unit 376 may determine the storage mode of the mobile battery 20 based on the output of the battery authentication unit 378. The control unit 376 may determine the charging mode of the mobile battery 20 based on the authentication result of the battery authentication unit 378. The control unit 376 may determine the discharging mode of the mobile battery 20 based on the authentication result of the battery authentication unit 378.

[0174] As described later, the battery authentication unit 378 outputs, for example, information indicating whether the specific mobile battery 20 is a legitimate device. For example, the battery authentication unit 378 outputs information indicating whether to continue to install the specific mobile battery 20 into the slot 124. For example, the battery authentication unit 378 outputs information indicating whether the specific mobile battery 20 is kept in a manner different from that of a legitimate device. For example, the battery authentication unit 378 outputs information indicating whether the specific mobile battery 20 is kept as a legitimate device. For example, the battery authentication unit 378 outputs information indicating whether charging and / or discharging of the specific mobile battery 20 is performed. For example, the battery authentication unit 378 outputs information indicating that the authentication process of the specific mobile battery 20 has failed.

[0175] When the control unit 376 obtains information indicating that a specific mobile battery 20 is not a legitimate device, the control unit 376 may prohibit the charging of the specific mobile battery 20, or may not allow the charging of the specific mobile battery 20. In the case where the specific mobile battery 20 is not a legitimate device, the control unit 376 may control the charging of the specific mobile battery 20 so that the allowable value of the charging current or the charging power is less than the case where the specific mobile battery 20 is a legitimate device. In the case where the specific mobile battery 20 is not a legitimate device, the control unit 376 may allow the specific mobile battery 20 to discharge, or may not prohibit the discharge. In the case where the specific mobile battery 20 is not a legitimate device, the control unit 376 may control the discharge of the specific mobile battery 20 so that the allowable value of the discharge current or the discharge power is less than the case where the specific mobile battery 20 is a legitimate device.

[0176] In another embodiment, when the confirmation device is the electric bicycle 30 and the device to be confirmed is the mobile battery 20, the computer of the electric bicycle 30 can be used as the control unit 376 and the battery authentication unit 378. In this case, the mobile battery 20 can be charged by regenerative power.

[0177] When the control unit 376 obtains information indicating that the authentication process of a specific mobile battery 20 has failed, the control unit 376 may perform the same process as the case where the mobile battery 20 is not determined to be a legitimate device. When the control unit 376 obtains information indicating that the authentication process of a specific mobile battery 20 has failed, the battery authentication unit 378 may determine to store the mobile battery 20 in a manner different from that of a legitimate device. For example, the battery authentication unit 378 stores the mobile battery 20 only during a time period that satisfies special conditions. Examples of the above-mentioned period include a period until the manager of the mobile battery 20 collects the mobile battery 20, a period during which the conditions for disbursement of the mobile battery 20 are relaxed due to the occurrence of an abnormal or emergency situation, for example.

[0178] When the control section 376 acquires information indicating that the authentication process of a specific mobile battery 20 has failed, the control section 376 may prohibit the charging of the specific mobile battery 20, or may not allow the charging of the specific mobile battery 20. When the authentication process of a specific mobile battery 20 has failed, the control section 376 may control the charging of the specific mobile battery 20 so that the allowable value of the charging current or the charging power is less than the allowable value when the authentication process of the specific mobile battery 20 is successful. When the control section 376 acquires information indicating that the authentication process of a specific mobile battery 20 has failed, the control section 376 may prohibit the discharging of the specific mobile battery 20, or may not allow the discharging of the specific mobile battery 20. When the authentication process of a specific mobile battery 20 has failed, the control section 376 may control the discharging of the specific mobile battery 20 so that the allowable value of the discharge current or the discharge power is less than the allowable value when the authentication process of the specific mobile battery 20 is successful.

[0179] When the control unit 376 obtains information indicating that the authentication process of a specific mobile battery 20 has failed, the control unit 376 can access the storage unit 250 of the specific mobile battery 20 to obtain specific information stored in the storage unit 250. For example, the control unit 376 can access the storage unit 250 of the specific mobile battery 20 to obtain identification information of a battery switch 120 (sometimes referred to as the immediately preceding battery switch 120) installed before the specific mobile battery 20 is installed in the current battery switch 120. For example, the control unit 376 can access the storage unit 250 of the specific mobile battery 20 to obtain identification information of an electric power device (an electric power device other than the battery switch 120, such as an electric bicycle 30) installed before the specific mobile battery 20 is installed in the current battery switch 120.

[0180] The control unit 376 may send the identification information of the immediately preceding battery switch 120 and / or the identification information of the power device to the management server 140. Thus, the management server 140 may detect a fault or abnormality of the immediately preceding battery switch 120. The management server 140 may determine the immediately preceding battery switch 120 based on the identification information of the power device and the movement history or battery exchange history of the power device.

[0181] The battery authentication unit 378 performs authentication processing of the mobile battery 20. For example, the battery authentication unit 378 confirms whether the mobile battery 20 installed in the slot 124 is a regular mobile battery 20. When the authentication processing of a specific mobile battery 20 fails, the battery authentication unit 378 can re-execute the authentication processing of the specific mobile battery 20. The number of re-executions can be predetermined. The mode of re-execution is not particularly limited, and re-execution can be started from the generation of the authentication code, or the authentication processing can be re-executed using the previously generated authentication code. The details of the battery authentication unit 378 will be described later.

[0182] The battery authentication unit 378 may be an example of a confirmation device. The tank 124 may be an example of a charging device. The tank 124 may be an example of a charging and discharging device.

[0183] Will refer to Figure 4 , Figure 5 and Figure 6 An example of the authentication process of the mobile battery 20 in the battery switch 120 is described in detail. Figure 4 An example of the authentication process of the mobile battery 20 is schematically shown. Figure 5 The schematic diagram shows the reference Figure 4 An example of the internal configuration of the battery authentication section 378 of the authentication process is described. Figure 6 The schematic diagram shows the method for implementing the reference Figure 4 An example of the internal configuration of the authentication correspondence section 232 of the authentication process is described. Note that the authentication process of the mobile battery 20 in the battery switch 120, the authentication correspondence section 232, and the battery authentication section 378 are not limited to the present embodiment.

[0184] In reference Figure 4 In the described embodiment, an example of the authentication process of the mobile battery 20 is described by taking as an example the case where the mobile battery 20 has completed the step of acquiring the authentication private key 72 of the mobile battery 20 from the key issuer 50, the communication terminal 52, or the management server 140. In the above acquisition process, the mobile battery 20 stores the authentication private key 72 in the authentication private key storage unit 254, for example.

[0185] In addition, in reference Figure 4In the described embodiment, an example of the authentication process of the mobile battery 20 is described by taking as an example the case where the battery switch 120 has completed the step of acquiring the database related to the authentication public key 74 of the above-mentioned one or more mobile batteries 20 from the key issuer 50, the communication terminal 52, or the management server 140. In the above-mentioned acquisition process, the battery switch 120 stores the database related to the authentication public key 74 of the above-mentioned one or more mobile batteries 20 in a storage device provided in, for example, the battery authentication unit 378 or the onboard device 370.

[0186] In this embodiment, at the start of the authentication process of the mobile battery 20, the authentication private key 72 of the mobile battery 20 is stored in the authentication private key storage unit 254. Similarly, the battery authentication unit 378 of the battery exchanger 120 includes a database related to one or more authentication public keys 74 of the mobile battery 20.

[0187] like Figure 4 As shown, according to the present embodiment, first, in step 420 (step is sometimes abbreviated as S), the battery authentication unit 378 of the battery switch 120 detects that the mobile battery 20 is installed in the slot 124. When the battery authentication unit 378 of the battery switch 120 detects that the mobile battery 20 is installed in the slot 124, the battery authentication unit 378 of the battery switch 120 sends an activation signal to the mobile battery 20.

[0188] In S422, when the control unit 230 of the mobile battery 20 receives the activation signal, for example, the control unit 230 and the authentication corresponding unit 232 are activated. At this time, the control unit 230 can send an activation confirmation signal to the battery exchange unit 120 indicating that the authentication corresponding unit 232 has been activated.

[0189] Next, in S424, the battery authentication unit 378 sends a signal requesting the mobile battery 20 to send the battery ID (sometimes referred to as an ID sending request). For example, in S426, when the control unit 230 of the mobile battery 20 receives the ID sending request signal, the control unit 230 sends the battery ID stored in the battery ID storage unit 252 to the battery switch 120.

[0190] Next, in S430, when the battery authentication unit 378 obtains the battery ID of the mobile battery 20, the battery authentication unit 378 uses the battery ID as a keyword to refer to the database related to the above-mentioned authentication public key 74, and extracts the authentication public key 74 that matches the battery ID. When the authentication public key 74 that matches the battery ID is not extracted, the battery authentication unit 378 can access the communication terminal 52 or the management server 140 to obtain the authentication public key 74 that matches the battery ID.

[0191] In addition, the battery authentication section 378 prepares an authentication code. For example, the battery authentication section 378 generates a random number and determines to use the random number as the authentication code.

[0192] Next, the battery authentication unit 378 transforms the authentication code based on the authentication public key 74 of the mobile battery 20, and generates a challenge code including the transformed authentication code. For example, the battery authentication unit 378 encrypts the authentication code using the authentication public key 74 of the mobile battery 20. In addition, the battery authentication unit 378 generates a challenge code including the encrypted authentication code.

[0193] In addition, in this embodiment, the battery authentication unit 378 prepares a verification code. For example, the battery authentication unit 378 performs a calculation process using a hash function to generate a hash value of the verification code. The battery authentication unit 378 determines to use the generated hash value as the verification code.

[0194] Next, in S432, the battery authentication section 378 sends a challenge code to the mobile battery 20. The battery authentication section 378 may send the challenge code and an authentication response request to the mobile battery 20.

[0195] In S434, when the authentication corresponding unit 232 receives the challenge code, the authentication corresponding unit 232 reversely transforms the encrypted authentication code contained in the challenge code based on the authentication private key 72 stored in the authentication private key storage unit 254. Specifically, the authentication corresponding unit 232 decrypts the encrypted authentication code contained in the challenge code using the authentication private key 72 stored in the authentication private key storage unit 254. Since the authentication private key 72 is paired with the authentication public key 74, if the mobile battery 20 is a legitimate mobile battery 20, the authentication corresponding unit 232 successfully decrypts the encrypted authentication code.

[0196] Next, in S436, the authentication corresponding unit 232 generates a response code including information indicating that the mobile battery 20 has successfully decrypted the authentication code encrypted with the authentication public key 74. For example, the authentication corresponding unit 232 performs a calculation process using a hash function to generate a hash value of the decrypted authentication code. The authentication corresponding unit 232 generates a response code including the hash value of the decrypted authentication code. In addition, the authentication corresponding unit 232 sends the response code to the battery switch 120.

[0197] Next, in S438, when the battery authentication section 378 receives the response code, the battery authentication section 378 compares the hash value contained in the response code with the hash value generated as the verification code. For example, the battery authentication section 378 determines whether the hash value contained in the response code matches the hash value generated as the verification code. Furthermore, in S440, based on the above comparison result, the battery authentication section 378 determines whether the mobile battery 20 is a regular mobile battery 20 (sometimes referred to as a legitimate device).

[0198] According to this embodiment, in S450, the battery authentication unit 378 may determine whether to replace the mobile battery 20 based on the determination result in S440. For example, if the mobile battery 20 is not determined to be a legitimate device, the battery authentication unit 378 determines not to install the mobile battery 20 into the slot 124.

[0199] The above installation may not include temporary installation for authentication processing. For example, when the battery switch 120 and the mobile battery 20 communicate via wire, the mobile battery 20 may be temporarily installed on the battery switch 120 so that the battery authentication unit 378 authenticates the mobile battery 20. For example, the above installation means that the mobile battery 20 continues to be installed on the battery switch 120. The above installation may mean that the mobile battery 20 is kept as a legitimate device.

[0200] In one embodiment, when it is not determined that the mobile battery 20 is a legitimate device, the battery authentication unit 378 may determine not to continue to install the mobile battery 20 into the slot 124. In the case where it is not determined that the mobile battery 20 is a regular mobile battery 20, the battery authentication unit 378 may determine to store the mobile battery 20 in a manner different from that of a legitimate device. For example, the battery authentication unit 378 stores the mobile battery 20 only during a period of time that satisfies special conditions. Examples of the above period include a period until the manager of the mobile battery 20 reclaims the mobile battery 20, for example, a period during which the conditions for spending the mobile battery 20 are relaxed due to the occurrence of an abnormal or emergency situation.

[0201] In another embodiment, when it is determined that the mobile battery 20 is a legitimate device, the battery authentication unit 378 determines to install the mobile battery 20 into the slot 124. When it is determined that the mobile battery 20 is a legitimate device, the battery authentication unit 378 may determine to continue to install the mobile battery 20 into the slot 124. When it is determined that the mobile battery 20 is a legitimate device, the battery authentication unit 378 may determine to keep the mobile battery 20 as a legitimate device.

[0202] The battery authentication unit 378 can determine whether to replace the mobile battery 20 based on the determination result in S440 and the above white list. For example, when it is determined that the mobile battery 20 is a regular mobile battery 20, the battery authentication unit 378 determines whether the mobile battery 20 is a mobile battery 20 that can be used by multiple users 40.

[0203] Specifically, the battery authentication unit 378 confirms whether the battery ID of the mobile battery 20 is disclosed in the white list. When the battery ID of the mobile battery 20 is disclosed in the white list, the battery authentication unit 378 determines that the mobile battery 20 is a mobile battery 20 that can be used by a plurality of users 40. On the other hand, when the battery ID of the mobile battery 20 is not disclosed in the white list, the battery authentication unit 378 determines that the mobile battery 20 is not a mobile battery 20 that can be used by a plurality of users 40.

[0204] When it is determined that the mobile battery 20 is not a mobile battery 20 that can be used by a plurality of users 40, the battery authentication unit 378 may determine not to install the mobile battery 20 in the slot 124. Thus, for example, even if the mobile battery 20 is a legitimate mobile battery 20, when the user 40 of the mobile battery 20 has not joined the mobile battery 20 charging service or the mobile battery 20 exchange service based on the battery management system 100, the mobile battery 20 is prevented from being stored in the battery exchanger 120.

[0205] When it is determined that the mobile battery 20 is not installed in the slot 124, even if the mobile battery 20 is installed in the slot 124 in order to perform the authentication process of the mobile battery 20, the battery exchanger 120 may release the installation of the mobile battery 20 and return the mobile battery 20 to the user 40. In addition, there is no particular limitation on the manner in which the mobile battery 20 is installed in the slot 124. It may be a manner in which the mobile battery 20 is accommodated inside the slot 124, or it may be a manner in which the mobile battery 20 is placed on the slot 124.

[0206] In the case where it is determined not to continue to install the mobile battery 20 in the slot 124, the same information processing as the case where it is determined not to install the mobile battery 20 in the slot 124 can be performed. When it is determined that the mobile battery 20 is kept in a manner different from that of a legitimate device, the same information processing as the case where it is determined not to install the mobile battery 20 in the slot 124 can be performed.

[0207] In addition, according to the present embodiment, in S450, the battery authentication unit 378 can determine whether the mobile battery 20 is charged and / or discharged based on the determination in S440. For example, in the case where the mobile battery 20 is not determined to be a regular mobile battery 20, it is determined not to charge and / or discharge the mobile battery 20. Thus, the input / output of power between the slot 124 and the mobile battery 20 can be prohibited or suppressed. The battery authentication unit 378 can determine whether the mobile battery 20 is charged and / or discharged based on the determination result in S440 and the above-mentioned white list through a process similar to the above process.

[0208] In addition, the processing in the mobile battery 20 can be performed by a single processor, or can be performed by a plurality of processors in cooperation. Similarly, the processing in the battery switch 120 can be performed by a single processor, or can be performed by a plurality of processors in cooperation. This further improves safety.

[0209] For example, the mobile battery 20 includes a control CPU for controlling various operations of the mobile battery 20 and a security IC for performing encryption processing and decryption processing. S422 and S426 are executed by the above-mentioned control CPU. In addition, in S434, when the control CPU receives the challenge code, the control CPU transmits the challenge code to the security IC. The security IC decrypts the challenge code in S434 and generates a response code in S436. In addition, in S436, the security IC outputs the generated response code to the control CPU. In S436, the control CPU sends the response code generated by the security IC to the battery switch 120.

[0210] The case where the mobile battery 20 is determined or confirmed to be not a legitimate device may be an example of the case where the mobile battery 20 is not determined to be a legitimate device. The case where the mobile battery 20 is determined or confirmed to be a non-compliant mobile battery 20 may be an example of the case where the mobile battery 20 is not determined to be a legitimate device.

[0211] The case where the mobile battery 20 is not determined to be a legitimate device may be an example of a case where the third verification information and the fifth verification information are determined not to satisfy the second mathematical relationship, or an example of a case where the third verification information and the sixth verification information do not match. The case where the mobile battery 20 is determined to be a legitimate device may be an example of a case where the third verification information and the fifth verification information are determined to satisfy the second mathematical relationship, or an example of a case where the third verification information and the sixth verification information match.

[0212] like Figure 5 As shown, in this embodiment, the battery authentication unit 378 includes a storage unit 520, a battery ID acquisition unit 530, an authentication code generation unit 540, a verification code generation unit 550, a challenge code generation unit 560, a challenge code sending unit 562, a response code acquisition unit 570, a comparison unit 582 and a determination unit 584. In this embodiment, the storage unit 520 includes a public key database 522 and a white list 524.

[0213] In the present embodiment, the storage unit 520 stores various information. In the present embodiment, the public key database 522 stores the battery ID of each of the one or more mobile batteries 20 managed by the battery management system 100 and the authentication public key 74 of each of the one or more mobile batteries 20 in association with each other. The white list 524 stores the battery ID of the one or more mobile batteries 20 managed by the battery management system 100. In another embodiment, the public key database 522 can be used as the white list 524.

[0214] In one embodiment, the battery authentication unit 378 obtains the public key database 522 from the key issuer 50. The battery authentication unit 378 stores the public key database 522 obtained from the key issuer 50 in the storage unit 520. In another embodiment, the battery authentication unit 378 obtains the public key database 522 from the communication terminal 52 or the management server 140. The battery authentication unit 378 stores the public key database 522 obtained from the communication terminal 52 or the management server 140 in the storage unit 520.

[0215] In the present embodiment, the battery ID acquisition unit 530 acquires the battery ID of the mobile battery 20 accommodated in the slot 124 or the battery ID of the mobile battery 20 accommodated in the slot 124. The battery ID acquisition unit 530 may acquire the battery ID of the mobile battery 20 installed in the slot 124. The battery ID acquisition unit 530 may acquire the battery ID of the mobile battery 20 from the communication terminal 42 or the mobile battery 20.

[0216] In this embodiment, the authentication code generation unit 540 generates the authentication code 502. The authentication code generation unit 540 can generate the authentication code 502 by generating a random number.

[0217] In this embodiment, the verification code generation unit 550 generates the verification code. The verification code generation unit 550 generates the verification code according to the rule for generating the response code by the mobile battery 20. When generating a response code including the authentication code itself restored by the mobile battery 20, the verification code generation unit 550 may not generate the verification code, or may determine to use the authentication code as the verification code.

[0218] In this embodiment, the verification code generation unit 550 performs arithmetic processing using a hash function 552 to generate a hash value 504 of the authentication code 502. The verification code generation unit 550 determines to use the generated hash value 504 as the verification code. The verification code generation unit 550 outputs the hash value 504 to the comparison unit 582 as the verification code.

[0219] In this embodiment, the challenge code generation unit 560 generates the challenge code 512. For example, the challenge code generation unit 560 encrypts the authentication code 502 using the authentication public key 74 of the mobile battery 20. Thus, the battery authentication unit 378 can generate the challenge code 512 including the encrypted authentication code 502.

[0220] In this embodiment, the challenge code sending unit 562 sends the challenge code 512 generated by the challenge code sending unit 562 to the mobile battery 20. The challenge code sending unit 562 may send the challenge code 512 and the authentication response request to the mobile battery 20.

[0221] In this embodiment, the response code acquisition unit 570 acquires the response code 516 corresponding to the challenge code 512 from the mobile battery 20. In this embodiment, the response code 516 includes the hash value 506 of the authentication code 502 restored in the mobile battery 20. The response code acquisition unit 570 outputs the hash value 506 of the restored authentication code 502 to the comparison unit 582.

[0222] In the present embodiment, the comparison unit 582 acquires the hash value 504 as the verification code from the verification code generation unit 550. In addition, the comparison unit 582 acquires the hash value 506 included in the response code 516 from the response code acquisition unit 570. The comparison unit 582 compares the hash value 504 as the verification code with the hash value 506 included in the response code 516. For example, the comparison unit 582 determines whether the hash value 504 as the verification code and the hash value 506 included in the response code 516 match. The comparison unit 582 outputs information indicating the comparison result to the determination unit 584.

[0223] In the present embodiment, the determination unit 584 acquires information indicating the comparison result of the comparison unit 582. The determination unit 584 determines whether the mobile battery 20 is a normal mobile battery 20 based on the comparison result of the comparison unit 582.

[0224] The determination section 584 may determine whether to exchange the mobile battery 20 based on the determination result as to whether the mobile battery 20 is a regular mobile battery 20. The determination section 584 may determine whether to exchange the mobile battery 20 based on the determination result as to whether the mobile battery 20 is a regular mobile battery 20 and the white list 524.

[0225] The determination unit 584 may determine whether the mobile battery 20 is charged and / or discharged based on the determination result as to whether the mobile battery 20 is a regular mobile battery 20. Thus, the power input / output between the slot 124 and the mobile battery 20 may be prohibited or suppressed. The determination unit 584 may determine whether the mobile battery 20 is charged and / or discharged based on the determination result as to whether the mobile battery 20 is a regular mobile battery 20 and the white list 524.

[0226] The storage unit 520 may be an example of a first storage device. The challenge code generation unit 560 may be an example of a third information generation unit. The challenge code transmission unit 562 may be an example of a third information transmission unit. The response code acquisition unit 570 may be an example of a response receiving unit. The comparison unit 582 may be an example of a comparison unit.

[0227] like Figure 6 In this embodiment, the authentication corresponding unit 232 includes a request receiving unit 620 , an ID sending unit 630 , a challenge code acquiring unit 640 , a challenge code decrypting unit 650 , a response code generating unit 660 and a response code sending unit 670 .

[0228] In the present embodiment, the request receiving unit 620 receives various types of requests from the battery switch 120. Examples of the above requests include an ID transmission request, an authentication response request, etc. In the present embodiment, when the request receiving unit 620 receives the ID transmission request from the battery switch 120, the ID transmitting unit 630 transmits the battery ID of the mobile battery 20 to the battery switch 120.

[0229] In the present embodiment, when the request receiving unit 620 receives the authentication response request from the battery switch 120, the challenge code acquiring unit 640 acquires the challenge code 512 sent by the battery switch 120. In the present embodiment, the challenge code decrypting unit 650 decrypts the encrypted authentication code 502 included in the challenge code 512 using the authentication private key 72. In addition, the challenge code decrypting unit 650 outputs the decrypted authentication code 502 to the response code generating unit 660.

[0230] In this embodiment, the response code generation unit 660 generates the response code 516 based on the decrypted authentication code 502. The response code generation unit 660 can generate the response code 516 in any format according to the above rules.

[0231] According to the present embodiment, the response code generation unit 660 performs arithmetic processing using a hash function 662 to generate a hash value 506 of the restored authentication code 502. The response code generation unit 660 generates a response code 516 including the hash value 506 of the restored authentication code 502. In the present embodiment, the response code transmission unit 670 transmits the response code 516 to the battery switch 120.

[0232] The challenge code acquisition unit 640 may be an example of a third information acquisition unit. The challenge code decryption unit 650 may be an example of a fifth information generation unit. The response code transmission unit 670 may be an example of a response unit.

[0233] Another Example of Implementation

[0234] In this embodiment, Figure 4An example of information processing in the battery switch 120 is described by taking as an example the case where, in S450 of the embodiment, it is determined that the mobile battery 20 installed in the slot 124 is not a mobile battery 20 that can be used by multiple users 40, the battery authentication unit 378 determines not to install the mobile battery 20 in the slot 124 or not to charge or discharge the mobile battery 20. However, the information processing when it is determined that the mobile battery 20 is not a mobile battery 20 that can be used by multiple users 40 is not limited to this embodiment. In another embodiment, when it is determined that the mobile battery 20 is not a mobile battery 20 that can be used by multiple users 40, the battery authentication unit 378 may perform the process of installing the mobile battery 20 in the slot 124 according to a predetermined first rule, and may also perform the charging process or the discharging process of the mobile battery 20 according to a predetermined second rule.

[0235] As a first rule, a rule is exemplified that allows the mobile battery 20 to be installed in the slot 124, but does not allow a user 40 other than the user 40 who installed the mobile battery 20 in the slot 124 to remove the mobile battery 20. As a second rule, a rule is exemplified that allows the mobile battery 20 to be charged or discharged until the number of times the mobile battery 20 is installed in the slot 124 reaches a predetermined number of times or frequency, but does not allow the mobile battery 20 to be charged or discharged when the number of times the mobile battery 20 is installed in the slot 124 exceeds the aforementioned number of times or frequency.

[0236] In this embodiment, an example of the authentication process of the mobile battery 20 is described by taking the case where the battery switch 120 obtains the authentication public key 74 of the mobile battery 20 from the key issuer 50, the communication terminal 52, or the management server 140 as an example. However, the method of obtaining the authentication public key 74 in the battery switch 120 is not limited to this embodiment. In another embodiment, the battery switch 120 may obtain the authentication public key 74 from the mobile battery 20.

[0237] In the present embodiment, an example of the authentication process of the mobile battery 20 is described by taking the case where the comparison process of the authentication code and the response code is performed by comparing the verification code generated from the authentication code with the response code as an example. However, the process of comparing the authentication code and the response code is not limited to the present embodiment. Figure 1 Describes various methods to compare authentication codes and response codes.

[0238] Figure 7 An example of the internal configuration of the mounted device 330 is schematically shown. In the present embodiment, in order to simplify the description, the mounted device 330 is described in detail using the case where the slot 124 does not have the function of discharging the mobile battery 20 as an example. However, those skilled in the art who are familiar with the description of the specification of the present application can understand that the slot 124 can be changed to a configuration capable of charging / discharging the mobile battery 20.

[0239] In this embodiment, the onboard device 330 includes one or more slots 124, a circuit breaker 710, a power line 712, an AC / DC power supply 714, a distributor 716, a power line 718, a main control board 730, a communication hub 732, a communication line 734, a temperature adjustment unit 742, a buzzer 744, a sensor unit 746, and a maintenance door 748. In this embodiment, the slot 124 includes an AC / DC charger 760, a power connector 762, a slot control board 770, a communication connector 772, a drive unit 774, a gate 776, a locking unit 778, a temperature adjustment unit 782, a status display unit 784, and a sensor unit 786.

[0240] In the present embodiment, the circuit breaker 710 receives power from the power system 12. The circuit breaker 710 provides the power received from the power system 12 to the AC / DC charger 760 of each of the more than one slots 124 via the power line 712. The circuit breaker 710 provides the power received from the power system 12 to the AC / DC power source 714. Examples of the circuit breaker 710 include a circuit breaker, a residual current circuit breaker with overcurrent protection, and the like.

[0241] In the present embodiment, the AC / DC power supply 714 is used as a power supply for providing control power. For example, the AC / DC power supply 714 converts the AC power received from the circuit breaker 710 into DC power having an appropriate voltage. The AC / DC power supply 714 provides the converted DC power to the slot control board 770 of each of the more than one slots 124 via the distributor 716 and the power line 718. In addition, the AC / DC power supply 714 provides the converted DC power to the main control board 730.

[0242] In the present embodiment, the main control board 730 controls the operation of each unit of the storage unit 122. The main control board 730 is connected to the CPU board 820 via the communication line 310. The main control board 730 can function as the control section 336. The main control board 730 can function as the control section 336 in cooperation with the tank control board 770.

[0243] The main control board 730 sends and receives information with the slot control board 770 of each of the one or more slots 124 via the communication hub 732 and the communication line 734. The main control board 730 can control the operation of the temperature adjustment part 742, the buzzer 744, the sensing part 746, and the maintenance door 748. The main control board 730 can obtain information indicating the status of the temperature control part 742, the buzzer 744, the sensing part 746, and the maintenance door 748.

[0244] For example, the main control board 730 acquires information indicating the measurement result of the sensing section 746 from the sensing section 746. In addition, the main control board 730 acquires information indicating the open / closed state of the maintenance door 748 from the maintenance door 748.

[0245] In the present embodiment, the temperature adjustment unit 742 adjusts the temperature inside the housing 320 of the storage unit 122. Examples of the temperature adjustment unit 742 include a fan, a water-cooled cooler, and the like.

[0246] In this embodiment, the buzzer 744 notifies the user 40 of the state of the storage unit 122. The buzzer 744 can output a warning sound. The buzzer 744 can output a warning designated by the main control board 730 from a plurality of warning sounds having different warning patterns.

[0247] In this embodiment, the sensor unit 746 acquires information indicating the state of the storage unit 122. The sensor unit 746 may include various types of sensors. Examples of sensors included in the sensor unit 746 include a temperature sensor, a vibration sensor, a leakage sensor, etc. The sensor unit 746 may constitute at least a part of the sensor unit 332.

[0248] In this embodiment, the maintenance door 748 is provided at the opening portion (not shown) of the housing 320, and is used for the maintenance personnel of the battery switch 120 to maintain and manage the battery switch 120. The maintenance door 748 can output information indicating the open / closed state to the main control board 730. For example, when the maintenance door 748 is opened, the maintenance door 748 outputs a signal indicating that the maintenance door 748 has been opened.

[0249] In this embodiment, the AC / DC charger 760 charges the mobile battery 20 electrically connected to the power connector 762. The AC / DC charger 760 adjusts at least one of the voltage and current applied to the mobile battery 20 electrically connected to the power connector 762 according to the instruction from the slot control board 770.

[0250] In the present embodiment, the power connector 762 includes an electrical terminal that is electrically connected to the power connector 212 of the mobile battery 20 when the mobile battery 20 is accommodated in the slot 124. In the present embodiment, the power connector 762 is configured to be movable by the driving portion 774. In addition, in another embodiment, the power connector 762 may be fixed inside the slot 124.

[0251] In the present embodiment, the tank control board 770 controls the operation of each unit of the tank 124. The tank control board 770 can control the operation of the tank 124 according to the instruction from the main control board 730. The tank control board 770 can be used as the control section 336. The tank control board 770 can be used as the control section 336 in cooperation with the main control board 730.

[0252] The slot control board 770 can send and receive information with the control unit 230 of the mobile battery 20 stored in the slot 124 via the communication connector 772. For example, the slot control board 770 can read information stored in the storage unit 250 of the mobile battery 20. In addition, the slot control board 770 can write information to the storage unit 250 of the mobile battery 20.

[0253] In the present embodiment, the communication connector 772 includes a communication terminal that is communicatively connected to the communication connector 214 of the mobile battery 20 when the mobile battery 20 is accommodated in the slot 124. In the present embodiment, the communication connector 772 is configured to be movable by the driving portion 774. In addition, in another embodiment, the communication connector 772 may be fixed inside the slot 124.

[0254] In the present embodiment, the driving section 774 drives various movable members provided in the slot 124. The driving section 774 can drive the above-mentioned movable members according to the instruction from the slot control board 770. Examples of the movable members include the power connector 762, the communication connector 772, the gate 776, the locking section 778, the removal prevention member provided in the slot 124, the mechanism for restraining the mobile battery 20 provided in the slot 124, and the like.

[0255] In this embodiment, the shutter 776 is provided at the opening portion (not shown) of the slot 124 and controls whether the mobile battery 20 is available to the user 40. The shutter 776 can be controlled to open / close according to the instruction from the slot control board 770.

[0256] For example, when the shutter 776 is in an open state, the user 40 can insert the mobile battery 20 into the slot 124 or remove the mobile battery 20 from the slot 124. On the other hand, when the shutter 776 is in a closed state, the mobile battery 20 cannot be inserted into the slot 124 or removed from the slot 124.

[0257] In the present embodiment, the locking portion 778 switches between the locked state and the unlocked state of the shutter 776. The locking portion 778 can switch between the locked state and the unlocked state of the shutter 776 according to the instruction from the slot control board 770.

[0258] In this embodiment, the temperature regulator 782 regulates the temperature in the tank 124. In this embodiment, the temperature regulator 782 may regulate the temperature in the tank 124 according to a command from the tank control board 770. Examples of the temperature regulator 782 include a fan, a water-cooled cooler, and the like.

[0259] In the present embodiment, the state display unit 784 notifies the user 40 of the state of the slot 124. Examples of the state of the slot 124 include the presence or absence of the mobile battery 20, the presence or absence of an abnormality, etc. For example, the state display unit 784 can notify the user 40 of the state of the slot 124 by a lighting pattern, a flashing pattern, or a display pattern specified by the slot control board 770 among a plurality of lighting patterns, flashing patterns, or display patterns. Examples of the state display unit 784 include an LED, a display, and the like.

[0260] In the present embodiment, the sensing unit 786 acquires information indicating the state of the slot 124. The sensing unit 786 may include various types of sensors. Examples of sensors included in the sensing unit 786 include temperature sensors, voltage sensors, current sensors, and the like. For example, the sensing unit 786 includes at least one of (i) a temperature sensor for measuring the temperature inside the slot 124 or near the mobile battery 20, (ii) a voltage sensor for measuring the voltage of the power connector 762, and (iii) a current sensor for measuring the current flowing through the power connector 762. The sensing unit 786 may constitute at least a portion of the sensing unit 332.

[0261] The main control board 730 may be an example of a confirmation device. The power connector 762 may be an example of a first terminal. The slot control board 770 may be an example of a confirmation device.

[0262] Figure 8 The figure schematically shows an example of the internal configuration of the onboard device 370. In the present embodiment, the onboard device 370 includes an AC / DC power supply 814, a service socket 816, a CPU board 820, an Ethernet interface (Ethernet I / F) 830 which is a communication interface of Ethernet (registered trademark), an NFC reader 842, a camera 844, a touch panel 852, a display 854, and a speaker 856.

[0263] In the present embodiment, the AC / DC power supply 814 and the AC / DC power supply 714 are used as power supplies for providing control power. The AC / DC power supply 814 receives power from the power system 12 via the uninterruptible power supply device 312, for example. The AC / DC power supply 814 converts the AC power received from the power system 12 into DC power having an appropriate voltage. The AC / DC power supply 814 provides the converted DC power to the CPU board 820.

[0264] In the present embodiment, the service outlet 816 supplies power to a device external to the communication unit 126. An example of the external device is the router 314.

[0265] The service socket 816 receives power from the power system 12, for example, via the uninterruptible power supply device 312. The service socket 816 can control the power supply to the external device according to the instruction from the CPU board 820. The service socket 816 can send information about the power supplied to the external device to the CPU board 820.

[0266] The CPU board 820 controls the operation of each unit of the communication unit 126. The CPU board 820 is connected to the main control board 730 via the communication line 310. The CPU board 820 can function as the control section 376.

[0267] In the present embodiment, the Ethernet interface 830 is connected to the communication network 14 via the router 314. The Ethernet interface 830 may be used as the communication interface 128.

[0268] In the present embodiment, the NFC reader 842 transmits and receives information with the communication terminal 42 via short-range wireless communication. The NFC reader 842 may be used as the communication interface 128. The NFC reader 842 may be used as the user identification unit 374.

[0269] In this embodiment, the camera 844 captures the user 40. The camera 844 may be used as the user interface 372. The camera 844 may be used as the user identification unit 374.

[0270] In the present embodiment, the touch panel 852 accepts touch input from the user 40. The touch panel 852 can be used as the user interface 372. In the present embodiment, the display 854 presents information to the user 40 by outputting images. The display 854 can be used as the user interface 372. In the present embodiment, the speaker 856 presents information to the user 40 by outputting sounds. The speaker 856 can be used as the user interface 372.

[0271] The CPU board 820 may be an example of the confirmation device. The touch panel 852 may be an example of the above-mentioned input device.

[0272] refer to Fig. 9 , Fig.10 and Fig.11 , another example of a process in which the battery switch 120 acquires the authentication public key 74 will be described. Fig. 9 An example of the internal configuration of the mobile battery 920 is schematically shown. Fig.10 An example of a process of acquiring the authentication public key 74 is schematically shown. Fig.11 An example of a process of acquiring the authentication public key 74 is schematically shown.

[0273] In reference Figures 1 to 6In the described embodiment, the battery management system 100 is described in detail by taking the case where the battery switch 120 obtains a database storing the authentication public key 74 of more than one mobile battery 20 from the key issuer 50, the communication terminal 52 or the management server 140 as an example. Fig. 9 , Fig.10 and Fig.11 The described embodiments, combined with Figures 1 to 6 The embodiment described differs in that the battery switch 120 obtains the authentication public key 74 of the mobile battery 20 from the mobile battery 20 installed in the slot 124. Fig. 9 , Fig.10 and Fig.11 The described embodiments may have similarities to those described in the reference Figures 1 to 6 The same configuration as described is implemented.

[0274] like Fig. 9 As shown, in this embodiment, the mobile battery 920 is different from the mobile battery 20 in that the storage unit 250 includes a battery ID storage unit 252, an authentication private key storage unit 254, an authentication public key storage unit 955, a signature private key storage unit 956, and a signature verification public key storage unit 957. Except for the above differences, the mobile battery 920 can have the same configuration as the mobile battery 20.

[0275] In reference Fig. 9 In the described embodiment, the mobile battery 920 may not include the signature verification public key 84 and the signature verification public key storage unit 957. For example, in the case where the battery switch 120 stores the signature verification public key 84 of the mobile battery 920, or the battery switch 120 can obtain the signature verification public key 84 of the mobile battery 920, the mobile battery 920 may not include the signature verification public key 84 and the signature verification public key storage unit 957.

[0276] The mobile battery 920 may not include the signature private key 82 and the signature private key storage unit 956. In this case, for example, the mobile battery 920 may store at least one of (i) the authentication public key 74 encrypted with the signature private key 82, (ii) information in which the authentication public key 74 and arbitrary information are encrypted with the signature private key 82, and (iii) an electronic certificate of the authentication public key 74 in any storage device provided in the mobile battery 920.

[0277] The authentication public key 74 encrypted with the signature private key 82 and the authentication public key 74 and any information encrypted with the signature private key 82 are sometimes referred to as electronic signatures. For example, a series of processes for digital signatures using elliptic curve cryptography is called an elliptic curve digital signature algorithm.

[0278] The electronic certificate of the authentication public key 74 includes, for example, the authentication public key 74 and the authentication public key 74 encrypted with the signature private key 82. The electronic certificate of the authentication public key 74 includes, for example, the authentication public key 74 (or the authentication public key 74 and any information), and information obtained by encrypting the authentication public key 74 and the arbitrary information with the signature private key 82. Figures 1 to 6 In the described embodiment, the mobile battery 920 and the reference Fig. 9 The embodiment described differs in that the mobile battery 920 does not include the signature private key 82 and the signature private key storage unit 956 , and the signature verification public key 84 and the signature verification public key storage unit 957 .

[0279] In this embodiment, the authentication public key storage unit 955 stores the authentication public key 74. In this embodiment, the signature private key storage unit 956 stores the signature private key 82 used by the mobile battery 20 to provide an electronic signature. The signature verification public key storage unit 957 stores the signature verification public key 84, which is used by the battery switch 120 to verify the authenticity of the information containing the electronic signature of the mobile battery 20 (for example, the electronic certificate obtained by the battery switch 120 from the mobile battery 20).

[0280] The signature verification public key 84 is used to decrypt information encrypted using the signature private key 82. As described above, the electronic signature of the mobile battery 20 is generated by encrypting arbitrary information using the signature private key 82. In addition, the electronic certificate contains the plain text of arbitrary information and the cipher text of the arbitrary information encrypted using the signature private key 82. The signature verification public key 84 is used to decrypt information encrypted using the signature private key 82. By comparing the plain text information contained in the electronic certificate and the information decrypted using the signature verification public key 84, the authenticity of the plain text information contained in the electronic certificate can be verified.

[0281] Fig.10 An example of the acquisition process of the authentication public key 74 is schematically shown. In the present embodiment, the battery authentication unit 378 has acquired the signature verification public key 84 of the mobile battery 20 from, for example, the key issuer 50, the communication terminal 52, or the management server 140. For example, a database that stores the battery ID of one or more mobile batteries 20 and the signature verification public key 84 of one or more mobile batteries 20 correspondingly is stored in the storage unit 520. Note that the signature verification public keys 84 of a plurality of mobile batteries 20 may be the same, and the signature verification public keys 84 of all mobile batteries 20 may also be the same.

[0282] In this embodiment, the authentication handling unit 232 further includes a public key transmission unit 1012. In addition, the battery authentication unit 378 further includes a public key acquisition unit 1014.

[0283] According to this embodiment, first, in S1020, for example, the public key acquisition unit 1014 of the battery switch 120 detects that the mobile battery 20 has been installed in the slot 124. When the public key acquisition unit 1014 detects that the mobile battery 20 is installed in the slot 124, the public key acquisition unit 1014 sends an activation signal to the mobile battery 20.

[0284] In S1022, for example, when the public key transmission unit 1012 of the mobile battery 20 receives the activation signal, for example, the control unit 230 and the authentication corresponding unit 232 are activated. At this time, the public key transmission unit 1012 can send an activation confirmation signal to the battery exchange unit 120 indicating that the authentication corresponding unit 232 has been activated.

[0285] Next, in S1024, the public key acquisition unit 1014 sends a signal (sometimes referred to as a public key transmission request) requesting the mobile battery 20 to transmit the battery ID and the authentication public key 74. In S1030, for example, when the public key transmission unit 1012 of the mobile battery 20 receives the public key transmission request, the public key transmission unit 1012 encrypts the authentication public key 74 using the signature private key 82. In S1032, the public key transmission unit 1012 transmits the battery ID stored in the battery ID storage unit 252, the unencrypted authentication public key 74, and the authentication public key 74 encrypted with the signature private key 82 to the battery exchanger 120.

[0286] The process of encrypting the authentication public key 74 using the signature private key 82 can be an example of the process of signing the authentication public key 74 using the signature private key 82 (sometimes referred to as signature processing). In the signature processing, various public key encryption methods or public key encryption infrastructure (PKI) can be used. As the method of signature processing, RSA encryption method, DSA signature method, ECDAS signature method, EdDSA signature method, etc. are exemplified. In the ECDAS signature method, an encryption method using an elliptic curve is used. The process of transforming plain text into cipher text using the public key of a public key cipher is sometimes called encryption. The process of transforming cipher text into plain text using a private key paired with the public key used for encryption is sometimes called decryption. The process of processing plain text with the private key of a public key cipher is sometimes called signing. The process of transforming a signature into original information using the public key of a public key cipher is sometimes called verification.

[0287] Next, in S1040, when the public key acquisition unit 1014 receives the battery ID, the unencrypted authentication public key 74, and the authentication public key 74 encrypted with the signature private key 82 from the public key transmission unit 1012, the public key acquisition unit 1014 refers to a database that stores the battery IDs of one or more mobile batteries 20 and the signature verification public keys 84 of one or more mobile batteries 20 correspondingly, and extracts the signature verification public key 84 corresponding to the battery ID transmitted by the public key transmission unit 1012. In addition, the public key acquisition unit 1014 decrypts the authentication public key 74 encrypted by the signature private key 82 using the extracted signature verification public key 84. Note that in the case where the signature verification public keys 84 of all mobile batteries 20 are the same, the step of extracting the signature verification public key 84 by the public key acquisition unit 1014 with reference to the above-mentioned database can be omitted.

[0288] Next, in S1042, the public key acquisition section 1014 compares the unencrypted authentication public key 74 sent by the public key transmission section 1012 with the authentication public key 74 decrypted in S1040. For example, the public key acquisition section 1014 determines whether the unencrypted authentication public key 74 sent by the public key transmission section 1012 matches the authentication public key 74 decrypted in S1040. When the unencrypted authentication public key 74 sent by the public key transmission section 1012 matches the authentication public key 74 decrypted in S1040, in S1044, the public key acquisition section 1014 stores the authentication public key 74 sent by the public key transmission section 1012 in the preservation section 520 or the public key database 522 as the authentic authentication public key 74 of the mobile battery 20. The above-mentioned comparison process may be an example of a process of verifying the signature of the authentication public key 74 (sometimes referred to as a verification process).

[0289] The authentication public key 74 may be an example of the eleventh information. The signature private key 82 may be an example of the twelfth information. The authentication public key 74 encrypted using the signature private key 82 may be an example of the thirteenth information. The signature verification public key 84 may be an example of the fourteenth information. The authentication public key 74 decrypted using the signature verification public key 84 may be an example of the fifteenth information. The signature process may be an example of the transformation of the information. The verification process may be an example of the transformation or inverse transformation of the information.

[0290] Another Example of Implementation

[0291] In this embodiment, the case where the mobile battery 20 is installed on the battery switch 120 is taken as an example, and the process of the battery switch 120 obtaining the authentication public key 74 of the mobile battery 20 is described in detail. However, the subject that obtains the authentication public key 74 of the mobile battery 20 is not limited to the battery switch 120. In another embodiment, the subject that obtains the authentication public key 74 of the mobile battery 20 can be the above-mentioned power device.

[0292] In addition, as described above, the confirmation device is not limited to the battery switch 120. Any confirmation device can obtain the authentication public key of any device to be confirmed through the same process as the present embodiment. For example, when the mobile battery 20 authenticates the battery switch 120, the mobile battery 20 obtains the authentication public key of the battery switch 120 through the same process as the present embodiment.

[0293] In this embodiment, the process of the battery switch 120 acquiring the authentication public key 74 of the mobile battery 20 is described in detail by taking the example of encrypting the authentication public key 74 using the signature private key 82 in S1030 and sending the battery ID stored in the battery ID storage unit 252, the unencrypted authentication public key 74, and the authentication public key 74 encrypted with the signature private key 82 from the mobile battery 20 to the battery switch 120 in S1032. However, the process of the battery switch 120 acquiring the authentication public key 74 of the mobile battery 20 is not limited to this embodiment. For example, in S1030, the information encrypted using the signature private key 82 is not limited to the authentication public key 74.

[0294] According to another embodiment, in S1030, an arbitrary code is encrypted using the signature private key 82. The above code may have the same configuration as the above authentication code. The above code may be a battery ID. In this case, for example, in S1032, the battery ID stored in the battery ID storage unit 252, the unencrypted authentication public key 74, the unencrypted above code, and the above code encrypted with the signature private key 82 are sent from the mobile battery 20 to the battery switch 120.

[0295] Next, in S1040, the public key acquisition unit 1014 extracts the signature verification public key 84 corresponding to the battery ID sent by the public key transmission unit 1012, and uses the extracted signature verification public key 84 to decrypt the code encrypted by the signature private key 82. In addition, in S1042, the public key acquisition unit 1014 compares the unencrypted code sent by the public key transmission unit 1012 with the code decrypted in S1040. For example, the public key acquisition unit 1014 determines whether the unencrypted code sent by the public key transmission unit 1012 matches the code decrypted in S1040. When the two match, the public key acquisition unit 1014 stores the authentication public key 74 sent by the public key transmission unit 1012 as the authentic authentication public key 74 of the mobile battery 20 in the storage unit 520 or the public key database 522. According to the above embodiment, as in the present embodiment, the battery switch 120 can confirm that the authentication public key 74 received from the battery 20 is a legitimate authentication public key.

[0296] According to another embodiment, in S1030, the hash value of the above arbitrary code is encrypted using the signature private key 82. Then, in S1032, the battery ID stored in the battery ID storage unit 252, the unencrypted authentication public key 74, the unencrypted hash value of the above arbitrary code, and the hash value of the above arbitrary code encrypted with the signature private key 82 are sent from the mobile battery 20 to the battery switch 120. In this case, the difference from the other embodiments described above is that in S1042, the public key acquisition unit 1014 derives the hash value of the code decrypted in S1040. In addition, the difference from the other embodiments described above is that the public key acquisition unit 1014 compares the hash value of the unencrypted code sent by the public key sending unit 1012 with the hash value of the code decrypted in S1040.

[0297] According to another embodiment, the authentication public key 74 of the mobile battery 20 is sent from the mobile battery 20 to the battery switch 120 using any electronic signature method or electronic certificate method. Thus, the battery switch 120 can confirm that the authentication public key 74 received from the mobile battery 20 is a legitimate authentication public key.

[0298] As described above, in the present embodiment, in S1030, the authentication public key 74 is encrypted using the signature private key 82. In S1032, the process of the battery switch 120 acquiring the authentication public key 74 of the mobile battery 20 is described in detail, taking the case where the battery ID stored in the battery ID storage unit 252, the unencrypted authentication public key 74, and the authentication public key 74 encrypted with the signature private key 82 are sent from the mobile battery 20 to the battery switch 120 as an example. However, the process of the battery switch 120 acquiring the authentication public key 74 of the mobile battery 20 is not limited to the present embodiment.

[0299] In another embodiment, the storage unit 250 of the mobile battery 20 stores an electronic certificate of the authentication public key 74. The electronic certificate of the authentication public key 74 includes, for example, an unencrypted authentication public key 74 and an authentication public key 74 encrypted with a signature private key 82. The electronic certificate of the authentication public key 74 includes, for example, an unencrypted battery ID and the authentication public key 74, and a battery ID and the authentication public key 74 encrypted with the signature private key 82. When the public key acquisition unit 1014 of the battery switch 120 requests to send a public key, the public key sending unit 1012 of the mobile battery 20 sends the electronic certificate of the authentication public key 74 to the public key acquisition unit 1014. As a result, the process of the mobile battery 20 encrypting the authentication public key 74 using the signature private key 82 is omitted. In this case, the mobile battery 20 may not store the signature private key 82.

[0300] In the present embodiment, the process of the battery exchange unit 120 acquiring the authentication public key 74 of the mobile battery 20 is described in detail by taking the case where the public key acquisition unit 1014 extracts the signature verification public key 84 corresponding to the battery ID sent by the public key transmission unit 1012 by referring to the database that stores the signature verification public key 84 of one or more mobile batteries 20 correspondingly as an example. However, the process of the battery exchange unit 120 acquiring the authentication public key 74 of the mobile battery 20 is not limited to the present embodiment.

[0301] In another embodiment, the storage unit 250 of the mobile battery 20 stores an electronic certificate of the signature verification public key 84. The electronic certificate of the signature verification public key 84 includes, for example, an unencrypted signature verification public key 84 and a signature verification public key 84 encrypted with a private key of a certification authority. The electronic certificate of the signature verification public key 84 includes, for example, an unencrypted ID and signature verification public key 84, and an ID and signature verification public key 84 encrypted with a signature private key 82. The above-mentioned ID may be a battery ID, an ID of a manufacturer of the mobile battery 20, or an ID of a manufacturer of a control CPU or a security IC of the mobile battery 20. When the public key acquisition unit 1014 of the battery switch 120 requests to send a public key, the public key sending unit 1012 of the mobile battery 20 sends the electronic certificate of the signature verification public key 84 to the public key acquisition unit 1014. The public key sending unit 1012 acquires a public key corresponding to a private key. The public key corresponding to the private key of the certification authority may be stored in the battery switch 120 , or may be sent from the server of the certification authority to the battery switch 120 in response to a request from the battery switch 120 .

[0302] Fig.11 An example of the process of obtaining the authentication public key 74 is schematically shown. According to this embodiment, the process of obtaining the authentication public key 74 is similar to that of the reference Fig.10 The difference described is that S1132 is executed after S1030 instead of S1032, and S1134 is executed after S1132. For features other than the above differences, refer to Fig.11 The acquisition process of the authentication public key 74 described in the reference Fig.10 The acquisition process of the authentication public key 74 described above is the same configuration.

[0303] According to the present embodiment, in S1132, the public key sending unit 1012 sends the battery ID stored in the battery ID storage unit 252, the unencrypted authentication public key 74, the authentication public key 74 encrypted with the signature private key 82, and the signature verification public key 84 to the battery switch 120. The public key sending unit 1012 can send an electronic certificate including the signature verification public key 84 to the battery switch 120, thereby sending the signature verification public key 84 to the battery switch 120.

[0304] As described above, the public key sending unit 1012 can send the battery ID stored in the battery ID storage unit 252, the electronic certificate of the authentication public key 74, and the electronic certificate of the signature verification public key 84 to the battery exchanger 120 in response to a request from the public key acquisition unit 1014. The public key acquisition unit 1014 can request the sending of the electronic certificate instead of the public key request or together with the public key request. As described above, the electronic certificate of the authentication public key 74 contains, for example, the unencrypted battery ID and the authentication public key 74, and the battery ID and the authentication public key 74 encrypted with the signature private key 82. In this case, the public key sending unit 1012 can send the electronic certificate of the authentication public key 74 and the electronic certificate of the signature verification public key 84 to the battery exchange unit 120 in response to a request from the public key acquisition unit 1014.

[0305] In S1134, the public key acquisition unit 1014 requests a trusted certification authority (not shown) to confirm the validity or authenticity of the signature verification public key 84. When the validity or authenticity of the signature verification public key 84 is confirmed, the public key acquisition unit 1014 executes S1040, S1042, and S1044. The signature verification public key 84 is obtained by, for example, a reference Figure 4 Therefore, according to another embodiment, the public key acquisition unit 1014 may acquire the signature verification public key 84 from the manufacturer or seller of the control CPU or security IC, for example.

[0306] The above-mentioned trusted certification authority may be the management server 140, or may be a server different from the management server 140. The above-mentioned trusted certification authority may be a server managed or operated by a manufacturer or seller of a control CPU or a security IC. The signature verification public key 84 may have a validity period. The above-mentioned trusted certification authority may manage the validity period of the signature verification public key 84. For example, when the certification authority receives a request from the public key sending unit 1012 to confirm the validity or authenticity of the signature verification public key 84, the certification authority may determine whether the validity period of the signature verification public key 84 has expired. When the validity period of the signature verification public key 84 expires, the certification authority sends information indicating that the signature verification public key 84 is invalid to the public key sending unit 1012 in response to the above-mentioned request. On the other hand, if the signature verification public key 84 has not expired, the certification authority sends information indicating that the signature verification public key 84 is valid to the public key sending unit 1012 in response to the above-mentioned request.

[0307] Another Example of Implementation

[0308] In this embodiment, the case where the mobile battery 20 is installed on the battery switch 120 is taken as an example, and the process of the battery switch 120 obtaining the authentication public key 74 of the mobile battery 20 is described in detail. However, the subject that obtains the authentication public key 74 of the mobile battery 20 is not limited to the battery switch 120. In another embodiment, the subject that obtains the authentication public key 74 of the mobile battery 20 can be the above-mentioned power device.

[0309] In addition, as described above, the confirmation device is not limited to the battery switch 120. Any confirmation device can obtain the authentication public key of any device to be confirmed through the same process as the present embodiment. For example, when the mobile battery 20 authenticates the battery switch 120, the mobile battery 20 obtains the authentication public key of the battery switch 120 through the same process as the present embodiment.

[0310] In the present embodiment, in S1030, the authentication public key 74 is encrypted using the signature private key 82. In S1132, the process of the battery switch 120 acquiring the authentication public key 74 of the mobile battery 20 is described in detail, taking the case where the battery ID stored in the battery ID storage unit 252, the unencrypted authentication public key 74, the authentication public key 74 encrypted with the signature private key 82, and the signature verification public key 84 are sent from the mobile battery 20 to the battery switch 120 as an example. However, the process of the battery switch 120 acquiring the authentication public key 74 of the mobile battery 20 is not limited to the present embodiment. For example, in S1030, the information encrypted using the signature private key 82 is not limited to the authentication public key 74.

[0311] According to another embodiment, in S1030, an arbitrary code is encrypted using the signature private key 82. The above code may have the same configuration as the above authentication code. The above code may be a battery ID. In this case, for example, in S1032, the battery ID stored in the battery ID storage unit 252, the unencrypted authentication public key 74, the unencrypted above code, the above code encrypted with the signature private key 82, and the signature verification public key 84 are sent from the mobile battery 20 to the battery switch 120.

[0312] Next, in S1040, the public key acquisition unit 1014 decrypts the code encrypted by the signature private key 82 using the signature verification public key 84 whose validity or authenticity was confirmed in S1134. In addition, in S1042, the public key acquisition unit 1014 compares the unencrypted code sent by the public key transmission unit 1012 with the code decrypted in S1040. For example, the public key acquisition unit 1014 determines whether the unencrypted code sent by the public key transmission unit 1012 matches the code decrypted in S1040. When the two match, the public key acquisition unit 1014 stores the authentication public key 74 sent by the public key transmission unit 1012 as the authentic authentication public key 74 of the mobile battery 20 in the storage unit 520 or the public key database 522. According to the above-mentioned embodiment, as in the present embodiment, the battery switch 120 can confirm that the authentication public key 74 received from the mobile battery 20 is a legitimate authentication public key.

[0313] According to another embodiment, in S1030, the hash value of the arbitrary code is encrypted using the signature private key 82. Then, the execution is combined with Fig.10 A process similar to the process described in another embodiment.

[0314] According to another embodiment, the authentication public key 74 of the mobile battery 20 is sent from the mobile battery 20 to the battery switch 120 using any electronic signature method or any electronic authentication method. Thus, the battery switch 120 can confirm that the authentication public key 74 received from the mobile battery 20 is a legitimate authentication public key.

[0315] In combination Fig.11 In the described embodiment, it is also possible to combine Fig.10 The same changes as those in another embodiment described above. For example, in another embodiment, the storage unit 250 of the mobile battery 20 can store an electronic certificate for the authentication public key 74. When the public key acquisition unit 1014 of the battery switch 120 requests to send the public key, the public key sending unit 1012 of the mobile battery 20 can send the electronic certificate stored in the storage unit 250 to the public key acquisition unit 1014 without newly creating an electronic certificate for the authentication public key 74. As a result, the process of the mobile battery 20 encrypting the authentication public key 74 using the signature private key 82 is omitted. In this case, the mobile battery 20 may not store the signature private key 82. Similar changes may be made in any of the embodiments described below.

[0316] Will refer to Fig.12 , Fig.13 , Fig.14 and Fig.15 Another example of the authentication process of the mobile battery 20 is described. Fig.12 Another example of the authentication process of the mobile battery 20 is schematically shown. Fig.13An example of the relationship between the response code and the verification code is schematically shown. Fig.14 An example of a verification process of a response code and a verification code is schematically shown. Fig.15 Another example of the verification process of the response code and the verification code is schematically shown.

[0317] Combination Fig.12 Describe the authentication process in conjunction with Figure 4 The authentication process described in this paper differs in that the plain text authentication code is sent as the challenge code. Figure 4 The same or similar certification process as described is given to Figure 4 The same reference numerals are used, and the description of the process is sometimes omitted. Figure 4 The same or similar authentication process as described in the reference Figure 4 The authentication process described is the same as the configuration.

[0318] In this embodiment, the case where the battery switch 120 authenticates the mobile battery 20 is taken as an example to describe an example of information processing for confirming whether the device to be confirmed is a legitimate device. However, the above information processing is not limited to this embodiment. In another embodiment, the mobile battery 20 can authenticate the battery switch 120 through the same process as this embodiment.

[0319] like Fig.12 As shown, according to the present embodiment, when the battery authentication unit 378 obtains the battery ID of the mobile battery 20 in S3130, in S3130, the battery authentication unit 378 uses the battery ID as a keyword to refer to the database related to the above-mentioned authentication public key 74, and extracts the authentication public key 74 that matches the battery ID. When the authentication public key 74 that matches the battery ID is not extracted, the battery authentication unit 378 can access the communication terminal 52 or the management server 140 to obtain the authentication public key 74 that matches the battery ID.

[0320] Furthermore, when the battery authentication section 378 acquires the battery ID of the mobile battery 20 in S3130, the battery authentication section 378 generates a challenge code in S3130 and transmits the challenge code to the mobile battery 20. For example, the generation and transmission of the challenge code are performed by the following process.

[0321] The battery authentication unit 378 first prepares an authentication code. For example, the battery authentication unit 378 generates a random number and determines to use the random number as the authentication code. The battery authentication unit 378 can use the above random number to generate the authentication code. The battery authentication unit 378 can generate the authentication code based on the above random number and any parameter used in the public key encryption method. The parameters used in the public key encryption method are shared between the confirmation device and the device to be confirmed, and public parameters are exemplified. Examples of public parameters include the elliptic curve E of the elliptic curve cryptography, the generation source P of the elliptic curve E, etc.

[0322] The battery authentication unit 378 sends the authentication code as a challenge code to the mobile battery 20. The battery authentication unit 378 sends the authentication code that is not encrypted by the authentication public key 74 as a challenge code to the mobile battery 20. For example, the battery authentication unit 378 sends the authentication code in plain text as a challenge code to the mobile battery 20.

[0323] In S3132, the battery authentication section 378 generates a verification code using the above-mentioned authentication code and the authentication public key 74 of the mobile battery 20. In the case where the authentication code is generated based on a random number and a public parameter, the battery authentication section 378 can generate the same verification code as described above using the random number used to generate the authentication code and the authentication public key 74 of the mobile battery 20. The process of generating the verification code will be described in detail later.

[0324] In S3134, when the control section 230 of the mobile battery 20 receives the challenge code, the control section 230 generates a response code using the authentication code included in the challenge code and the authentication private key 72 of the mobile battery 20. The process of generating the response code will be described in detail later. In addition, in S3136, the control section 230 sends the response code to the battery switch 120. Thus, the control section 230 ends the process corresponding to the authentication process of the battery switch 120 (sometimes referred to as the authentication corresponding process).

[0325] In S3138, when the battery authentication unit 378 receives the response code, the battery authentication unit 378 verifies whether the response code and the verification code have a predetermined mathematical relationship. The details of the above verification process will be described later. Thereafter, in S440, the battery authentication unit 378 determines or confirms whether the mobile battery 20 is a legitimate device based on the above verification result.

[0326] Fig.13An example of the relationship between the response code and the verification code is schematically shown. In the present embodiment, the response code and the verification code are generated by using the authentication public key and the authentication private key of the device to be confirmed. When the device to be confirmed is the mobile battery 20, the response code and the verification code are generated using the authentication public key 74 and the authentication private key 72. The authentication private key 72 is stored in the storage unit 250, for example. Even in the case where the device to be confirmed is the battery switch 120, the response code and the verification code can be generated by the same process as the case where the device to be confirmed is the mobile battery 20.

[0327] The authentication public key and the authentication private key of the device to be authenticated are generated to satisfy the mathematical relationship 3212. As the mathematical relationship 3212, the relationship used in encryption using an elliptic curve (sometimes referred to as elliptic curve cryptography or ECC) is illustrated. The following formula 1 illustrates the above relationship. In formula 1, each of p, a, and b is a parameter of the elliptic curve.

[0328] (Formula 1)

[0329] y 2 =x 3 +a×+bmodp

[0330] The point nG(x, y) obtained by scalar multiplication of the base point G(x, y) on the elliptic curve represented by Formula 1 by an integer n (sometimes referred to as the order) is located on the elliptic curve represented by Formula 1. At this time, a sufficiently large order n is used as a private key, and nG(x, y) is used as a public key.

[0331] When the device to be confirmed is a legitimate device, a response code and a verification code are generated so that the response code and the verification code satisfy the mathematical relationship 3214. The mathematical relationship 3214 is determined based on the mathematical relationship 3212. In one embodiment, the response code and the verification code may be the same. In this case, the mathematical relationship 3214 is response code = verification code or response code ÷ verification code = 1. In other embodiments, the response code and the verification code may be different. 1 as the above calculation result may be an example of a predetermined value.

[0332] In reference Fig.13 In the described embodiment, the battery authentication unit 378 includes an authentication code generation unit 3220, a verification code generation unit 3230, and a verification unit 3250. The control unit 230 includes a response code generation unit 3240.

[0333] In this embodiment, the authentication code generation unit 3220 generates the authentication code 3222. For example, the authentication code generation unit 3220 causes a random number generator to generate a random number, and generates the authentication code 3222 based on the random number. The authentication code generation unit 3220 can output the random number as the authentication code 3222. For example, the authentication code generation unit 3220 outputs the authentication code 3222 in plain text to the response code generation unit 3240 and the verification code generation unit 3230.

[0334] In the present embodiment, the verification code generation unit 3230 obtains the verification code 3222. The verification code generation unit 3230 obtains the authentication public key. The verification code generation unit 3230 uses the authentication code 3222 to derive the verification code 3232. For example, the verification code generation unit 3230 transforms the verification code 3222 based on the authentication public key and generates the verification code 3232. The verification code generation unit 3230 outputs the verification code 3232 to the verification unit 3250. The verification code generation unit 3230 will be described in detail later.

[0335] In this embodiment, the response code generation unit 3240 obtains the authentication code 3222. The response code generation unit 3240 obtains the authentication secret key. The response code generation unit 3240 generates the response code 3242 based on the authentication code 3222 and the authentication secret key. The response code generation unit 3240 transforms the authentication code 3222 based on the authentication secret key, for example, and generates the response code 3242.

[0336] The response code generation unit 3240 can generate the same information as the information obtained by transforming the authentication code 3222 based on the authentication public key (i.e., the verification code 3232). The response code generation unit 3240 generates the same information as the verification code 3232 based on the authentication code 3222, the authentication private key, and the mathematical relationship 3212 and / or the mathematical relationship 3214, for example.

[0337] The response code generation section 3240 outputs a response code 3242 to the verification section 3250. The response code generation section 3240 will be described in detail later.

[0338] In this embodiment, the verification unit 3250 obtains the verification code 3232 from the verification code generation unit 3230. The verification unit 3250 obtains the response code 3242 from the response code generation unit 3240. The verification unit 3250 determines whether the device to be confirmed is a legitimate device based on the verification code 3232 and the response code 3242.

[0339] When the response code generation unit 3240 outputs information obtained by transforming the authentication code 3222 based on the authentication secret key as the response code 3242, the verification unit 3250 can determine whether the authentication code 3232 and the response code 3242 satisfy the mathematical relationship 3214. When the response code generation unit 3240 outputs the same information as the authentication code 3232 as the response code 3242, the verification unit 3250 can compare the authentication code 3232 and the response code 3242. The details of the verification unit 3250 will be described later.

[0340] Mathematical relation 3212 may be an example of a first mathematical relation. Mathematical relation 3214 may be an example of a second mathematical relation. Authentication code generation unit 3220 may be an example of a first verification information generation unit. Authentication code 3222 may be an example of a first verification information. Authentication code generation unit 3230 may be an example of a third verification information generation unit. Verification code 3232 may be an example of a third verification information. Response code generation unit 3240 may be an example of a first verification information acquisition unit or a response unit. Response code 3242 may be an example of a fifth verification information or a sixth verification information. Verification unit 3250 may be an example of a response receiving unit or a determination unit.

[0341] The output of the authentication code 3222 may be an example of the transmission of the first verification information. The process in which the response code generation unit 3240 obtains the authentication code 3222 may be an example of the step in which the device to be confirmed receives the first verification information from the confirmation device or the step in which the first verification information is obtained from the first power device. The process in which the response code generation unit 3240 outputs the response code 3242 to the verification unit 3250 may be an example of the step in which the device to be confirmed generates the fifth verification information based on the first verification information and the fourth verification information. The public key used to generate the verification code 3232 may be an example of the second verification information. The private key used to generate the response code 3242 may be an example of the fourth verification information.

[0342] Fig.14 An example of the verification process of the response code and the verification code is schematically shown. In this embodiment, in order to facilitate the understanding of this embodiment, the verification process of the response code and the verification code will be described in detail by taking the case where the device to be confirmed is the mobile battery 20 as an example. Those skilled in the art who are familiar with the specification of this application can understand that, for example, even in the case where the confirmed device is the battery switch 120, the response code and the verification code can be verified by the same process as in this embodiment. In this embodiment, taking the case where the response code generation unit 3240 outputs the information obtained by transforming the authentication code 3222 based on the authentication private key as the response code 3242 as an example, the verification process of the response code and the verification code is described in detail.

[0343] In this embodiment, the verification code generation unit 3230 includes, for example, a first operation unit 3310. The response code generation unit 3240 includes, for example, a first operation unit 3310, a second operation unit 3320, and a third operation unit 3330. The verification unit 3250 includes, for example, a third operation unit 3330 and a determination unit 3350.

[0344] In this embodiment, the first operation unit 3310 obtains the authentication code 3222 and the authentication public key 74. For example, the first operation unit 3310 transforms the authentication code 3222 based on the authentication public key 74 and generates the verification code 3232. The first operation unit 3310 can generate the verification code 3232 by encrypting the authentication code 3222 using the authentication public key 74. The first operation unit 3310 outputs the verification code 3232 to the third operation unit 3330.

[0345] In this embodiment, the second operation unit 3320 obtains the authentication code 3222 and the authentication secret key 72. For example, the second operation unit 3320 transforms the authentication code 3222 based on the authentication secret key 72 and generates a response code 3242. The first operation unit 3310 can generate the response code 3242 by encrypting the authentication code 3222 using the authentication secret key 72. The second operation unit 3320 outputs the response code 3242 to the third operation unit 3330.

[0346] In this embodiment, the third operation unit 3330 obtains the verification code 3232 and the response code 3242. The third operation unit 3330 performs information processing on the verification code 3232 and the response code 3242 according to the first verification algorithm, and outputs the operation result of the information processing. The first verification algorithm may be an algorithm for verifying whether the verification code 3232 and the response code 3242 satisfy the mathematical relationship 3214. The first verification algorithm may include a process of deriving the parameter p of the above-mentioned elliptic curve. The first verification algorithm may include a process of outputting a value determined according to the mathematical relationship 3214 when the verification code 3232 and the response code 3242 are input and the device to be confirmed is a legitimate device.

[0347] The third operation unit 3330 of the response code generation unit 3240 performs information processing on the verification code 3232 output by the first operation unit 3310 of the response code generation unit 3240 and the response code 3242 output by the second operation unit 3320 of the response code generation unit 3240 according to the first verification algorithm. The third operation unit 3330 of the response code generation unit 3240 outputs the operation result 3332 to the determination unit 3350.

[0348] In the case where the mobile battery 20 is a legitimate device, the operation result 3332 represents the operation result that can be obtained when the verification code 3232 and the response code 3242 are processed according to the first verification algorithm when the authentication private key 72 and the authentication public key 74 satisfy the mathematical relationship 3212. As described above, when the device to be confirmed is a legitimate device, the verification code 3232 and the response code 3242 satisfy the mathematical relationship 3212.

[0349] The third operation unit 3330 of the verification unit 3250 performs information processing on the verification code 3232 output by the first operation unit 3310 of the verification code generation unit 3230 and the response code 3242 output by the second operation unit 3320 of the response code generation unit 3240 according to the first verification algorithm. The third operation unit 3330 of the verification unit 3250 outputs the operation result to the determination unit 3350.

[0350] In the present embodiment, the determination unit 3350 determines whether the verification code 3232 output by the verification code generation unit 3230 and the response code 3242 output by the response code generation unit 3240 satisfy the mathematical relationship 3214. For example, the determination unit 3350 compares the operation result 3332 of the third operation unit 3330 of the response code generation unit 3240 with the operation result of the third operation unit 3330 of the verification unit 3250. The determination unit 3350 may determine whether the operation result 3332 of the third operation unit 3330 of the response code generation unit 3240 matches the operation result of the third operation unit 3330 of the verification unit 3250. The determination unit 3350 may determine whether the mobile battery 20 is regular based on the comparison result.

[0351] When the two match, the determination unit 3350 can determine that the verification code 3232 output by the verification code generation unit 3230 and the response code 3242 output by the response code generation unit 3240 satisfy the mathematical relationship 3214. In this case, the determination unit 3350 can determine that the mobile battery 20 is regular. When the two do not match, the determination unit 3350 can determine that the verification code 3232 output by the verification code generation unit 3230 and the response code 3242 output by the response code generation unit 3240 do not satisfy the mathematical relationship 3214. In this case, the determination unit 3350 can determine that the mobile battery 20 is not regular or the mobile battery 20 is non-regular.

[0352] Information indicating the calculation result of the third calculation unit 3330 of the response code generation unit 3240 may be an example of the eighth verification information. Information indicating the calculation result of the third calculation unit 3330 of the verification unit 3250 may be an example of the seventh verification information.

[0353] Fig.15Another example of the verification process of the response code and the verification code is schematically shown. In this embodiment, in order to facilitate the understanding of this embodiment, the verification process of the response code and the verification code will be described in detail by taking the case where the device to be confirmed is a mobile battery 20 as an example. Those skilled in the art who are familiar with the specification of this application can understand that, for example, even in the case where the device to be confirmed is a battery switch 120, the response code and the verification code can be verified by the same process as in this embodiment. In this embodiment, taking the case where the response code generation unit 3240 outputs the same information as the verification code 3232 as the response code 3242 as an example, the verification process of the response code and the verification code is described in detail.

[0354] In this embodiment, the verification code generation unit 3230 includes, for example, a first operation unit 3310. The response code generation unit 3240 includes, for example, a fourth operation unit 3440. The verification unit 3250 includes, for example, a determination unit 3350.

[0355] In this embodiment, the fourth operation unit 3440 derives the same information as the verification code 3232 from the authentication code 3222 and the authentication secret key 72. The response code generation unit 3240 may output the same information as the verification code 3232 to the determination unit 3350 as the response code 3242.

[0356] For example, the fourth operation unit 3440 generates the same information as the verification code 3232 based on the authentication code 3222, the authentication secret key 72, and the mathematical relationship 3212 and / or the mathematical relationship 3214. The fourth operation unit 3440 can generate the same information as the verification code 3232 from the authentication code 3222 and the authentication secret key 72 using the mathematical relationship 3214. The fourth operation unit 3440 can generate the same information as the verification code 3232 from the information obtained by transforming the authentication code 3222 based on the authentication secret key 72 using the mathematical relationship 3214.

[0357] The fourth operation unit 3440 may include a reference Fig.14 The fourth operation unit 3440 may generate the same information as the verification code 3232 based on the response code 3242 output from the second operation unit 3320 and the operation result 3332 output from the third operation unit 3330 .

[0358] In this embodiment, the determination unit 3350 compares the verification code 3232 output by the verification code generation unit 3230 with the response code 3242 output by the response code generation unit 3240. For example, the determination unit 3350 determines whether the verification code 3232 output by the verification code generation unit 3230 and the response code 3242 output by the response code generation unit 3240 match. The determination unit 3350 can determine whether the mobile battery 20 is regular based on the comparison result.

[0359] When the two match, the determination unit 3350 may determine that the mobile battery 20 is compliant. When the two do not match, the determination unit 3350 may determine that the mobile battery 20 is not compliant or that the mobile battery 20 is non-compliant.

[0360] Fig.16 An example of a computer 5000 that can implement multiple embodiments of the present invention in whole or in part is shown. At least a portion of the battery management system 100 can be implemented by the computer 5000. For example, the control unit 230 or a portion thereof can be implemented by the computer 5000. For example, the control unit 336 or a portion thereof can be implemented by the computer 5000. For example, the control unit 376 or a portion thereof can be implemented by the computer 5000.

[0361] The program installed in the computer 5000 can make the computer 5000 function as an operation associated with the device involved in the embodiment of the present invention or one or more "units" of the device, or can make the computer 5000 perform the operation or the one or more "units", and / or can make the computer 5000 perform the process involved in the embodiment of the present invention or the steps of the process. Such a program can be executed by the CPU 5012 in order to make the computer 5000 perform specific operations associated with some or all of the functional blocks in the flowcharts and block diagrams described in this specification.

[0362] The computer 5000 of this embodiment includes a CPU 5012, a RAM 5014, a GPU 5016, and a display device 5018, which are connected to each other through a main controller 5010. The computer 5000 also includes input and output units such as a communication interface 5022, a hard disk drive 5024, a DVD-ROM drive 5026, and an IC card drive, which are connected to the main controller 5010 via an input and output controller 5020. The computer also includes a ROM 5030 and a keyboard 5042, which are connected to the input and output controller 5020 via an input and output chip 5040.

[0363] The CPU 5012 controls each unit by operating according to the program stored in the ROM 5050 and the RAM 5014. The GPU 5016 acquires image data generated by the CPU 5012 in a frame buffer or the like provided in the RAM 5014 or in itself, and displays the image data on the display device 5018.

[0364] The communication interface 5022 communicates with other electronic devices via a network. The hard disk drive 5024 stores programs and data used by the CPU 5012 in the computer 5000. The DVD-ROM drive 5026 reads programs or data from the DVD-ROM 5001, etc., and provides the programs or data to the hard disk drive 5024 via the RAM 5014. The IC card drive reads programs and data from an IC card and / or writes programs and data to an IC card.

[0365] The ROM 5030 stores therein a startup program executed by the computer 5000 when activated, and / or a program dependent on the hardware of the computer 5000. The input-output chip 5040 can also connect various input-output units to the input-output controller 5020 via a parallel port, a serial port, a keyboard port, a mouse port, and the like.

[0366] The program is provided by a computer-readable storage medium such as DVD-ROM 5001 or an IC card. The program is read from the computer-readable storage medium, installed in the hard disk drive 5024, RAM 5014 or ROM 5030, which are also examples of computer-readable storage media, and executed by the CPU 5012. The information processing recorded in these programs is read by the computer 5000, and the cooperation between the program and the various types of hardware resources described above is realized. The device or method can be constituted by realizing the operation or processing of information in accordance with the use of the computer 5000.

[0367] For example, when the computer 5000 communicates with an external device, the CPU 5012 can execute a communication program loaded into the RAM 5014, and based on the processing described in the communication program, instruct the communication interface 5022 to perform communication processing. Under the control of the CPU 5012, the communication interface 5022 reads the transmission data stored in the transmission buffer processing area provided in the RAM 5014, the hard disk drive 5024, the DVD-ROM 5001, or a storage medium such as an IC card, and transmits the read transmission data to the network, or writes the reception data received from the network to the reception buffer processing area provided on the storage medium.

[0368] In addition, the CPU 5012 can read all or a required portion of a file or database stored in an external storage medium such as the hard disk drive 5024, the DVD-ROM drive 5026 (DVD-ROM 5001), or an IC card to the RAM 5014, and perform various types of processing on the data on the RAM 5014. The CPU 5012 can then write the processed data back to the external storage medium.

[0369] Various types of information such as programs, data, tables, and databases can be saved to the storage medium and information processing can be accepted. CPU5012 can perform various operations, information processing, conditional judgment, conditional branching, unconditional branching, information retrieval / replacement, etc., which are recorded in various places of this disclosure and specified by the instruction sequence of the program, on the data read from RAM5014, and write the results back to RAM5014. In addition, CPU5012 can retrieve information in files, databases, etc. in the storage medium. For example, when multiple items having attribute values ​​of the first attribute associated with the attribute value of the second attribute are stored in the storage medium, CPU5012 can retrieve the item that specifies the attribute value of the first attribute and is consistent with the condition from the multiple items, read the attribute value of the second attribute stored in the item, and thereby obtain the attribute value of the second attribute associated with the first attribute that meets the pre-set condition.

[0370] The program or software module described above can be stored in a computer-readable storage medium on or near the computer 5000. In addition, a storage medium such as a hard disk or RAM provided in a server system connected to a dedicated communication network or the Internet can be used as a computer-readable storage medium, thereby providing the above-mentioned program to the computer 5000 via the network.

[0371] The present invention has been described above using the embodiments, but the technical scope of the present invention is not limited to the scope described in the above embodiments. It is obvious to those skilled in the art that various changes or improvements can be made to the above embodiments. In addition, within the scope of technical non-contradiction, the matters described for a specific embodiment can be applied to other embodiments. In addition, each constituent element can have the same features as other constituent elements with the same name but different reference symbols. It is obvious from the description of the claims that such changes or improvements can also be included in the technical scope of the present invention.

[0372] Regarding the execution order of each process such as actions, processes, steps and stages in the devices, systems, programs and methods shown in the claims, specifications and drawings, it should be noted that there is no special indication of "before", "preceding" and the like, and that the processes can be implemented in any order as long as the output of the previous process is not used in the subsequent process. Even if the action flow in the claims, specifications and drawings is described using "first" or "next" for convenience, it does not mean that it must be implemented in such an order.

[0373] Description of Reference Numerals

[0374] 12 power system, 14 communication network, 20 mobile battery, 30 electric bicycle, 40 user, 42 communication terminal, 50 key issuer, 52 communication terminal, 72 authentication private key, 74 authentication public key, 82 signature private key, 84 signature verification public key, 100 battery management system, 120 battery switch, 122 storage unit, 124 slot, 126 communication unit, 128 communication interface, 140 management server, 212 power connector, 214 communication connector, 220 power storage unit, 230 control unit, 232 authentication corresponding unit, 240 sensing unit, 250 storage unit, 252 battery ID storage unit, 254 authentication private key storage unit, 310 communication line, 312 uninterruptible power supply device, 314 router, 320 Shell, 330 mounted device, 332 sensing unit, 334 setting storage unit, 336 control unit, 360 shell, 370 mounted device, 372 user interface, 374 user identification unit, 376 control unit, 378 battery authentication unit, 502 authentication code, 504 hash value, 506 hash value, 512 challenge code, 516 response code, 520 storage unit, 522 public key database, 524 white list, 530 battery ID acquisition unit, 540 authentication code generation unit, 550 verification code generation unit, 552 hash function, 560 challenge code generation unit, 562 challenge code sending unit, 570 response code acquisition unit, 582 comparison unit, 584 determination unit, 620 request receiving unit, 630 ID sending unit, 640 challenge code acquisition unit, 650 challenge code decryption unit, 660 response code generation unit, 662 hash function, 670 response code sending unit, 710 circuit breaker, 712 power line, 714 AC / DC power supply, 716 distributor, 718 power line, 730 main control board, 732 communication hub, 734 communication line, 742 temperature adjustment unit, 744 buzzer, 746 sensing unit, 748 maintenance door, 760 AC / DC charger, 762 power connector, 770 slot control board, 772 communication connector, 774 drive unit, 776 gate, 778 locking unit, 782 temperature adjustment unit, 784 status display unit, 786 sensing unit, 814 AC / DC power supply, 816 service socket, 820 CPU board, 830 Ethernet interface, 842NFC reader, 844 camera, 852 touch panel, 854 display, 856 speaker, 920 mobile battery, 955 authentication public key storage unit, 956 signature private key storage unit, 957 signature verification public key storage unit, 1012 public key transmission unit, 1014 public key acquisition unit, 3212 mathematical relationship, 3214 mathematical relationship, 3220 authentication code generation unit, 3222 authentication code, 3230 verification code generation unit, 3232 verification code, 3240 response code generation unit, 3242 response code, 3250 verification unit, 3310 first operation unit, 3320 second operation unit, 3330 third operation unit, 3332 operation result, 3350 determination unit, 3440 fourth operation unit, 5000 computer,5001DVD-ROM, 5010main controller, 5012CPU, 5014RAM, 5016GPU, 5018display device, 5020input and output controller, 5022communication interface, 5024hard disk drive, 5026DVD-ROM drive, 5030ROM, 5040input and output chip, 5042keyboard.

Claims

1. A confirmation method is a confirmation method used by a confirmation device to confirm whether a device to be confirmed is a legitimate device, comprising: The step of sending the first verification information to the device to be verified; A step of generating third verification information by transforming the first verification information based on the second verification information; The step of receiving fifth verification information or sixth verification information from the device to be confirmed, wherein: (i) the fifth verification information is information generated by the device to be confirmed by transforming the first verification information based on the fourth verification information that satisfies the first mathematical relationship with the second verification information; (ii) the sixth verification information is information derived by the device to be confirmed based on the first verification information and the fourth verification information or derived from the fifth verification information using the second mathematical relationship that the third verification information and the fifth verification information should satisfy when the device to be confirmed is a legitimate device; as well as The step of determining whether the device to be confirmed is a legitimate device based on the third verification information and the fifth verification information or the sixth verification information, The step of determining comprises: (a) when the fifth verification information is received, determining whether the third verification information and the fifth verification information satisfy the second mathematical relationship, or, (b) when the sixth verification information is received, determining whether the third verification information and the sixth verification information are consistent with each other, The second mathematical relationship is determined based on the first mathematical relationship.

2. The confirmation method according to claim 1, wherein: The step of determining whether the third verification information and the fifth verification information satisfy the second mathematical relationship comprises: The step of performing information processing on the third verification information and the fifth verification information according to the first verification algorithm to generate seventh verification information; a step of acquiring eighth verification information from the device to be confirmed, wherein the eighth verification information represents a calculation result obtained by processing the third verification information and the fifth verification information according to the first verification algorithm when the second verification information and the fourth verification information satisfy the first mathematical relationship; as well as The step of determining whether the seventh verification information and the eighth verification information are consistent.

3. The confirmation method according to claim 1 or 2, wherein: The method also comprises the steps of: confirming that the device to be confirmed is not a legitimate device, or that the device to be confirmed is an illegitimate device, when it is determined that the third verification information and the fifth verification information do not satisfy the second mathematical relationship, or when it is determined that the third verification information and the sixth verification information are inconsistent.

4. The confirmation method according to any one of claims 1 to 3, wherein: The method also comprises the steps of: when it is determined that the third verification information and the fifth verification information satisfy the second mathematical relationship, or when it is determined that the third verification information and the sixth verification information are consistent, confirming that the device to be confirmed is a legal device, or that the device to be confirmed is not an illegal device.

5. The confirmation method according to any one of claims 1 to 4, wherein: Also features: (i) obtaining the second verification information from a manufacturer or transferor of the confirmation device, or an issuer of the second verification information and the fourth verification information, or (ii) obtaining the second verification information from a first external device configured to be able to communicate wirelessly with the confirmation device and to confirm that the confirmation device is a legitimate device; as well as The step of storing the acquired second verification information in a first storage device configured in the confirmation device.

6. The confirmation method according to any one of claims 1 to 5, wherein: Also features: (i) obtaining the fourth verification information from a manufacturer or transferor of the device to be confirmed, or an issuer of the second verification information and the fourth verification information, or (ii) obtaining the fourth verification information from a second external device configured to be able to communicate wirelessly with the device to be confirmed and confirm that the device to be confirmed is a legitimate device; as well as The step of storing the acquired fourth verification information in a second storage device configured in the device to be confirmed.

7. The confirmation method according to any one of claims 1 to 6, wherein: Also features: A step of receiving the second verification information encrypted using the first private key from the device to be verified; and The step of decrypting the encrypted second verification information using a first public key corresponding to the first private key.

8. The confirmation method according to claim 7, wherein: Also features: The step of receiving the second verification information which is not encrypted from the device to be verified; and a step of determining whether the unencrypted second verification information and the decrypted second verification information are consistent with each other, The step of generating the third verification information comprises: A step of converting the first verification information based on the second verification information to generate the third verification information when it is determined in the determining step that the unencrypted second verification information and the decrypted second verification information are identical.

9. The confirmation method according to any one of claims 1 to 6, wherein: Also features: A step of acquiring the second verification information signed by the first private key from the device to be verified; and The step of verifying the signature using a first public key corresponding to the first private key.

10. The confirmation method according to claim 9, wherein: The step of obtaining the second verification information of the signature comprises: The step of obtaining the second verification information encrypted by using the first private key and the second verification information which is not encrypted, The steps of verifying the signature include: A step of decrypting the encrypted second verification information using the first public key; and a step of determining whether the unencrypted second verification information and the decrypted second verification information are consistent with each other, The step of generating the third verification information comprises: A step of converting the first verification information based on the second verification information to generate the third verification information when it is determined in the determining step that the unencrypted second verification information and the decrypted second verification information are identical.

11. The confirmation method according to any one of claims 1 to 10, wherein: The second verification information is a public key, The fourth verification information is a private key corresponding to the public key.

12. The confirmation method according to any one of claims 1 to 11, wherein: Also features: a step of generating a random number; and The step of generating the first verification information based on the random number.

13. The confirmation method according to any one of claims 1 to 12, wherein: Also features: The device to be confirmed receives the first verification information from the confirmation device; The device to be confirmed generates the fifth verification information based on the first verification information and the fourth verification information; as well as The device to be confirmed sends the generated fifth verification information to the confirmation device.

14. The confirmation method according to any one of claims 1 to 13, wherein: The device to be confirmed includes a power storage device, The confirmation device includes a charge-discharge device configured to be attachable to and detachable from the power storage device and to charge and / or discharge the power storage device.

15. The confirmation method according to any one of claims 1 to 14, wherein: The confirmation device is a first power device having a first terminal, The device to be confirmed is a second power device having a second terminal configured to be mountable with the first terminal. The confirmation method also has: When it is determined that the third verification information and the fifth verification information do not satisfy the second mathematical relationship, or when it is determined that the third verification information and the sixth verification information are inconsistent, a step of prohibiting or suppressing the input and output of power between the first power device and the second power device is determined.

16. The confirmation method according to any one of claims 1 to 15, wherein: The confirmation device is a storage device that stores the device to be confirmed as a device to be stored. The storage device has an installation portion for installing the device to be stored. The confirmation method also has: (a) when it is determined that the third verification information and the fifth verification information do not satisfy the second mathematical relationship, or when it is determined that the third verification information and the sixth verification information are inconsistent, deciding not to continue the step of installing the device to be stored relative to the installation unit, or storing the device to be stored in a manner different from that of a legitimate device, and / or (b) When it is determined that the third verification information and the fifth verification information satisfy the second mathematical relationship, or when it is determined that the third verification information and the sixth verification information are consistent, decide to continue the step of installing the device to be stored relative to the installation part, or to store the device to be stored as a legitimate device.

17. The confirmation method according to claim 16, wherein: The storage device is configured to store at least one of the plurality of devices to be stored. The confirmation method also has: A step of acquiring common use identification information for identifying a device to be stored that can be commonly used by a plurality of users among the plurality of devices to be stored; When it is determined that the third verification information and the fifth verification information satisfy the second mathematical relationship, or when it is determined that the third verification information and the sixth verification information are consistent, a step of determining whether the device to be confirmed is the device to be stored that can be commonly used by a plurality of the users based on the common use identification information; as well as (c) when it is determined that the device to be confirmed is not the device to be kept that can be used together by multiple users, decide not to continue installing the device to be kept relative to the installation portion, or keep the device to be kept in a manner different from that of a legitimate device, and / or (d) when it is determined that the device to be confirmed is the device to be kept that can be used together by multiple users, decide to continue installing the device to be kept relative to the installation portion, or keep the device to be kept as a legitimate device.

18. A confirmation device is a confirmation device for confirming whether a device to be confirmed is a legitimate device, wherein: A first verification information sending unit, which sends the first verification information to the device to be confirmed; a third verification information generating unit, which transforms the first verification information based on the second verification information to generate third verification information; A response receiving unit receives fifth verification information or sixth verification information from the device to be confirmed, wherein: (i) the fifth verification information is information generated by the device to be confirmed by transforming the first verification information based on the fourth verification information that satisfies the first mathematical relationship with the second verification information; (ii) the sixth verification information is information derived by the device to be confirmed based on the first verification information and the fourth verification information, or derived from the fifth verification information, using the second mathematical relationship that the third verification information and the fifth verification information should satisfy when the device to be confirmed is a legitimate device; as well as a determination unit, which determines whether the device to be confirmed is a legitimate device based on the third verification information and the fifth verification information or the sixth verification information, The determination unit performs the following processing: (a) upon receiving the fifth verification information, determining whether the third verification information and the fifth verification information satisfy the second mathematical relationship, or (b) When the sixth verification information is received, determining whether the third verification information and the sixth verification information are consistent with each other.

19. An electric storage device comprising: an electric storage unit for storing electric energy; an electric terminal for transmitting and receiving electric power to and from a first electric power device for charging the electric storage unit or utilizing electric power discharged from the electric storage unit, in, The power storage device further comprises: a storage unit configured to store fourth verification information; a first authentication information acquisition unit that acquires first authentication information from the first power device; and A response unit that generates fifth verification information by transforming the first verification information obtained by the first verification information acquisition unit based on the fourth verification information stored in the storage unit, or generates sixth verification information obtained by transforming the first verification information based on second verification information that satisfies a first mathematical relationship with the fourth verification information.

20. The power storage device according to claim 19, wherein The response unit transmits the fifth authentication information or the sixth authentication information to the first power device.

21. A confirmation system, wherein: have: An electric device comprising the confirmation device according to claim 18; and The power storage device according to claim 19 or claim 20, The verification device verifies that the power storage device, which is a verification target of the verification device, that is, a verification-received device, is a legitimate device.

22. A program, wherein: The program is for causing a computer to execute the confirmation method according to any one of claims 1 to 17.

23. A computer-readable storage medium, wherein: The program according to claim 22 is stored.

Images