Battery system and battery management server
By using secure component verification and transmission technology in the battery management unit, the security and data integrity problems in the re-use of the battery module are solved, and the security, authorized re-use and anti-theft protection of the battery module are achieved.
Patent Information
- Application Number
- CN202410608923.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-06-06
- Filing Date
- 2024-05-16
- Publication Date
- 2024-12-06
AI Technical Summary
The prior art cannot ensure the safety, authorized reuse of the battery module, and the integrity of the battery-specific data for trusted reuse, resulting in the stolen battery potentially reuse in the thief's smart home battery system.
By introducing secure elements into the battery management unit, verifying signed requests from external servers using public keys, and transmitting status information and password keys to external servers, ensuring the authenticity and authorization of the secure decoupling and recoupling process of the battery modules, the authenticity and authorization of the safe decoupling and recoupling process of the battery module is achieved using public keys, and the status information and password keys are transmitted to external servers. sex.
It realizes the safety and authorized reuse of the battery module, ensures the integrity of battery-specific data, prevents unauthorized reuse and anti-theft protection, and enhances user satisfaction, security and performance.
Smart Images

Figure CN119092848A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to a first battery system, a second battery system, and corresponding methods of configuring the first battery system and the second battery system. In addition, the present disclosure relates to a battery management server, and corresponding methods of operating the battery management server. Background Art
[0002] Battery modules can be used in different systems and applications. A battery module can be defined as a component of a battery pack, which includes one or more battery cells and a battery module controller coupled to the battery cells. For example, an electric vehicle typically includes a battery pack, which in turn includes a plurality of battery modules. In addition, battery modules can be used in a smart home environment. It is desirable to reuse such battery modules. For example, when battery modules reach a certain age, these battery modules can no longer be used in electric vehicles, but can still be used in smart homes. In this reuse scenario, it is important that the reuse is safe. In addition, it may be important to ensure the integrity of battery-specific data (e.g., life cycle, recharge cycle, health status, manufacturer). However, it is currently impossible to ensure the safe, authorized reuse of battery modules. Therefore, stolen batteries can, for example, be easily reused in a thief's smart home battery system. In addition, current solutions do not ensure the integrity of battery-specific data for trusted reuse. Summary of the invention
[0003] According to a first aspect of the present disclosure, there is provided a first battery system, comprising: a plurality of battery modules; a battery management unit, the battery management unit being operably coupled to the battery modules, wherein the battery management unit comprises a security element; wherein the battery management unit is configured to receive a signed request from an external server, wherein the signed request is a request to decouple at least one of the battery modules from the system, and wherein the battery management unit is configured to verify the signed request using a public key stored in the security element.
[0004] In one or more embodiments, the signed request has been encrypted by the external server, and the battery management unit is further configured to decrypt the request using a decryption key stored in the secure element.
[0005] In one or more embodiments, the battery management unit is further configured to transmit status information to the external server, wherein the status information indicates the status of one or more of the battery modules, and wherein the battery management unit has read the status information from a safety element included in the battery module.
[0006] In one or more embodiments, the status information includes data indicating a life cycle, data indicating a recharge cycle, data indicating a health state of the battery module, and / or data indicating a manufacturer of the battery module.
[0007] In one or more embodiments, the battery management unit is further configured to receive cryptographic keys and / or cryptographic credentials from the external server, and the battery management unit is configured to store the cryptographic keys and / or cryptographic credentials in a security element of at least one of the battery modules to be decoupled in the battery module.
[0008] According to a second aspect of the present disclosure, a method for configuring a first battery system is contemplated, comprising: providing a plurality of battery modules to the system; providing a battery management unit operably coupled to the battery modules to the system, wherein the battery management unit includes a security element; wherein the battery management unit is configured to receive a signed request from an external server, wherein the signed request is a request to decouple at least one of the battery modules from the system, and wherein the battery management unit is configured to verify the signed request using a public key stored in the security element.
[0009] According to a third aspect of the present disclosure, a second battery system comprises: a plurality of battery modules; a battery management unit, which is operably coupled to the battery modules; wherein the battery management unit is configured to detect that a new battery module is inserted into the system, wherein the battery management unit is configured to read an identifier from a safety element included in the new battery module during or after the detection, and wherein the battery management unit is configured to transmit the identifier to an external server.
[0010] In one or more embodiments, the battery management unit is configured to receive a cryptographic key and / or cryptographic credentials in response to transmitting the identifier, and the battery management unit is configured to couple the new battery module to the system using the cryptographic key and / or cryptographic credentials.
[0011] In one or more embodiments, the cryptographic key and / or cryptographic credential has been pre-provisioned by the external server in the secure element of the new battery module.
[0012] In one or more embodiments, the battery management unit is further configured to transmit condition information to be verified to the external server, wherein the condition information indicates a condition of the new battery module.
[0013] In one or more embodiments, the battery management unit is configured to couple the new battery module to the system after receiving a positive verification result from the external server, wherein the positive verification result indicates that the condition information matches an expected condition.
[0014] According to a fourth aspect of the present disclosure, a method for configuring a second battery system is contemplated, comprising: providing a plurality of battery modules to the system; providing a battery management unit operably coupled to the battery modules to the system; wherein the battery management unit is configured to detect insertion of a new battery module into the system, wherein the battery management unit is configured to read an identifier from a safety element included in the new battery module during or after the detection, and wherein the battery management unit is configured to transmit the identifier to an external server.
[0015] According to a fifth aspect of the present disclosure, a battery management server is provided, which is configured to: transmit a signed request to an external first battery system, wherein the signed request is a request to decouple at least one of a plurality of battery modules from the first battery system; transmit a cryptographic key and / or a cryptographic credential to an external second battery system, wherein the cryptographic key and / or the cryptographic credential enables the second battery system to couple a battery module that has been decoupled from the first battery system to the second battery system.
[0016] According to a sixth aspect of the present disclosure, a method for operating a battery management server is contemplated, comprising: transmitting a signed request to an external first battery system, wherein the signed request is a request to decouple at least one of a plurality of battery modules from the first battery system; transmitting a cryptographic key and / or a cryptographic credential to an external second battery system, wherein the cryptographic key and / or the cryptographic credential enable the second battery system to couple a battery module that has been decoupled from the first battery system to the second battery system. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] The embodiments will be described in more detail with reference to the accompanying drawings.
[0018] Figure 1 An example of an electric vehicle is shown.
[0019] Figure 2 An example of a smart home is shown.
[0020] Figure 3A An illustrative embodiment of a battery management architecture is shown.
[0021] Figure 3B An illustrative embodiment of a method of configuring a first battery system is shown.
[0022] Figure 3CAn illustrative embodiment of a method of configuring a second battery system is shown.
[0023] Figure 3D An illustrative embodiment of a method of operating a battery management server is shown.
[0024] Figure 4 Another illustrative embodiment of a battery management architecture is shown.
[0025] Figure 5 Illustrate the different roles in a public key infrastructure scheme. DETAILED DESCRIPTION
[0026] Figure 1 An example of an electric vehicle 100 is shown. The vehicle 100 includes a battery pack 106 and a battery management system 102 that are operably coupled to each other. The battery pack 106 includes two or more battery modules 108, 116. Each of the battery modules 108, 116 includes two or more battery cells 112, 114, 120, 122 and a battery module controller 110, 118 that is operably coupled to the battery cells 112, 114, 120, 122. In addition, the battery management system 102 includes a microcontroller 104. It is desirable to reuse the battery modules 108, 116. For example, when the battery modules 108, 116 reach a certain age, these battery modules can no longer be used in the electric vehicle 100, but can still be used in another system or application, for example, in a smart home.
[0027] Figure 2 An example of a smart home 200 is shown. The smart home 200 includes a battery pack 206 and a battery management system 202 that are operably coupled to each other. The battery pack 206 includes two or more battery modules 208, 216. Each of the battery modules 208, 216 includes two or more battery cells 212, 214, 220, 222 and a battery module controller 210, 218 that is operably coupled to the battery cells 212, 214, 220, 222. In addition, the battery management system 202 includes a microcontroller 204. The battery modules 208, 216 may be modules that have been used in another system or application, for example, as a power source for an electric vehicle. However, currently, it is not possible to ensure safe, authorized reuse of battery modules. In addition, it is currently not possible to ensure battery-specific data integrity for trusted reuse. More specifically, the battery module may be easily replaced or manipulated by an unauthorized party. In addition, anti-theft protection is limited. It should be noted that counterfeit batteries may present safety risks (e.g., the battery may catch fire).
[0028] A battery system, a corresponding method of configuring the battery system, a battery management server, and a corresponding method of operating the battery management server are now discussed, which facilitate safe, authorized reuse of battery modules. The system, server, and corresponding method can be used in different scenarios. For example, they can help to safely transfer a battery module from an electric car to a smart home environment. In another example, they can help to safely transfer a battery module from an electric scooter to a portable mobile power source with a large capacity. The skilled person will understand that other use cases are also contemplated.
[0029] Figure 3A An illustrative embodiment of a battery management architecture 300 is shown. The architecture 300 includes a first battery system 302, a second battery system 310, and a battery management server 318. The first battery system 302 includes a plurality of battery modules 306, 308 operatively coupled to each other and a battery management unit 304 (e.g., a so-called battery management system). The battery management unit 304 includes a security element 338. In addition, the battery management unit 304 is configured to receive a signed request from the battery management server 318. In particular, the signed request is a request to decouple at least one of the battery modules 306, 308 from the first battery system 302. In addition, the battery management unit 304 is configured to verify the signed request using a public key stored in the security element 338. In this way, the authenticity of the request to decouple the battery modules 306, 308 - more specifically, the request sent for reusing the battery modules 306, 308 in another system or application - can be easily verified. This in turn facilitates the safe, authorized reuse of the battery modules 306, 308. It should be noted that the term "decoupling" may refer to unpairing the battery modules 306, 308 from the first battery system 302. In addition, it should be noted that a secure element may be defined as a tamper-resistant integrated circuit with an installed or pre-installed application having a specified function and a specified security level. In addition, the secure element may implement security functions, such as cryptographic functions and authentication functions.
[0030] The signed request may have been encrypted by the battery management server 318. In this case, the battery management unit 304 may be further configured to decrypt the request using a decryption key stored in the security element 338. In this way, the security level can be increased because it will be more difficult to manipulate the request. In addition, the battery management unit 304 may be further configured to transmit status information to the battery management server 318. This status information may indicate the status of one or more of the battery modules 306, 308. In particular, the battery management unit 304 may have read the status information from the security elements 340, 342 included in the battery modules 306, 308. In this way, the first battery system 302 may provide information related to the proper reuse of the battery modules 306, 308 to the battery management server 318. For example, the relevant status information may include data indicating a life cycle, data indicating a recharging cycle, data indicating a health state of the battery module, and / or data indicating the manufacturer of the battery modules 306, 308. It should be noted that the term "life cycle" may refer to one or more of the following parameters: the age of the battery module, one or more previous applications in which the battery modules have been used, how the battery modules have been used (e.g., whether the battery modules have been used in high performance mode), and other relevant parameters.
[0031] The battery management unit 304 may be further configured to receive cryptographic keys and / or cryptographic credentials from the battery management server 318. These cryptographic keys and / or cryptographic credentials may have been securely stored in a security element 344 included in the battery management server 318. In this case, the battery management unit 304 may be configured to store the cryptographic keys and / or cryptographic credentials in the security elements 340, 342 of one or more battery modules 306, 308 to be decoupled. In this way, the decoupled battery modules 306, 308 are ready for use in another second battery system. More specifically, inserting the cryptographic keys and / or cryptographic credentials into the security elements 340, 342 of the modules 306, 308 makes it easier for the second battery system to verify the authenticity of the modules 306, 308.
[0032] The second battery system 310 includes a plurality of battery modules 314, 316 operably coupled to each other and a battery management unit 312 (e.g., a battery management system). The battery management unit 312 is configured to detect that a new battery module (not shown) is inserted into the system. In addition, the battery management unit 312 is configured to read an identifier from a security element contained in the new battery module upon or after the detection and transmit the identifier to a battery management server 318. In this way, the battery management server 318 may be triggered to provide information about the inserted battery module to the second battery system 310. For example, the information may enable the battery management unit 312 of the second battery system 310 to authenticate the inserted battery module. This in turn facilitates safe, authorized reuse of the inserted battery module.
[0033] The battery management unit 312 of the second battery system 310 may be configured to receive a cryptographic key and / or cryptographic credential from the battery management server 318 in response to transmitting the identifier. In this case, the battery management unit 312 may be configured to couple the new battery module to the system using the cryptographic key and / or cryptographic credential. In this way, the authenticity of the inserted new battery module can be easily verified. This further contributes to the safe, authorized reuse of the inserted battery module. It should be noted that the term "coupling" may refer to pairing the new battery module with the second battery system 310. In a practical embodiment, the cryptographic key and / or cryptographic credential have been pre-provided by the battery management server 318 in the security element of the new battery module. Alternatively, the cryptographic key and / or cryptographic credential and other customer-specific and application-specific data may be written into the security element during the manufacture of the element. For example, a security element manufacturer can flash the credentials into the security element in a manufacturing location and process certified by Common Criteria (CC) by applying a trust provisioning service. The provisioning may also be performed in a two-step approach whereby credentials are written into the secure element by the secure element manufacturer and subsequently linked to the battery module by the battery management server 318 .
[0034] The battery management unit 312 of the second battery system 310 may be further configured to transmit condition information to be verified to the battery management server 318, wherein the condition information indicates the condition of the new battery module. Therefore, the battery management server 318 may use the information transmitted by the battery management unit 312 to verify whether the inserted battery module meets the predefined condition. It should be noted that the condition information may be embodied as battery-specific data, the integrity of which may be verified by the battery management server 318. Therefore, by transmitting the condition information to the battery management server 318, the integrity of the condition information may be ensured. Examples of battery-specific data are data indicating a life cycle, data indicating a recharge cycle, data indicating a health state of the inserted battery module, and / or data indicating a manufacturer of the inserted battery module. In addition, the battery management unit 312 may be configured to couple the new battery module to the second battery system 310 after receiving a positive verification result from the battery management server 318, wherein the positive verification result indicates that the condition information matches the expected condition. In this way, it can be ensured that only battery modules that meet the predefined condition are coupled to the second battery system 310.
[0035] The battery management server 318 is configured to transmit a signed request to the first battery system 302, wherein the signed request is a request to decouple at least one of the plurality of battery modules 306, 308 from the first battery system 302. In addition, the battery management server 318 is configured to transmit a cryptographic key and / or cryptographic credential to the second battery system 310, wherein the cryptographic key and / or cryptographic credential enables the second battery system 310 to couple the battery modules 306, 308 that have been decoupled from the first battery system 302 to the second battery system 310. In this way, safe, authorized reuse of the battery modules 306, 308 in the second battery system 310 is facilitated.
[0036] Figure 3B An illustrative embodiment of a method 320 for configuring a first battery system is shown. The method 320 includes the following steps. At 322, a plurality of battery modules are provided to the first battery system. Additionally, at 324, a battery management unit operably coupled to the battery modules is provided to the first battery system, wherein the battery management unit includes a security element, wherein the battery management unit is configured to receive a signed request from an external server (i.e., a battery management server), wherein the signed request is a request to decouple at least one of the battery modules from the first battery system, and wherein the battery management unit is configured to verify the signed request using a public key stored in the security element.
[0037] Figure 3CAn illustrative embodiment of a method 326 for configuring a second battery system is shown. The method 326 includes the following steps. At 328, a plurality of battery modules are provided to the second battery system. In addition, at 330, a battery management unit operably coupled to the battery module is provided to the second battery system, wherein the battery management unit is configured to detect insertion of a new battery module into the second battery system, wherein the battery management unit is configured to read an identifier from a safety element included in the new battery module upon or after the detection, and wherein the battery management unit is configured to transmit the identifier to an external server (i.e., a battery management server).
[0038] Figure 3D An illustrative embodiment of a method 332 of operating a battery management server is shown. The method 332 includes the following steps. At 334, the battery management server transmits a signed request to an external first battery system, wherein the signed request is a request to decouple at least one of the plurality of battery modules from the first battery system. In addition, at 336, the battery management server transmits a cryptographic key and / or cryptographic credential to an external second battery system, wherein the cryptographic key and / or cryptographic credential enables the second battery system to couple the battery module that has been decoupled from the first battery system to the second battery system.
[0039] Figure 4 Another illustrative embodiment of a battery management architecture 400 is shown. In particular, Figure 4 Show Figure 3A An example of an implementation of the architecture shown in . The electric vehicle 402 includes a first battery system, which includes a battery pack 410 and a battery management unit implemented as a so-called battery management system (BMS) 404. The battery pack 410 includes two or more battery modules 412, 422. Each battery module 412, 422 includes two or more battery cells 418, 420, 428, 430 and a battery module controller 416, 426. In addition, each battery module 412, 422 includes a security element (SE) 414, 424 having an applet installed thereon. The applet can be used to perform functions related to safety. In addition, the BMS 404 also includes a SE 406 on which an applet for performing functions related to safety is installed, and a microcontroller 408.
[0040] In addition, the smart home 432 includes a second battery system including a battery pack 438 and a battery management unit implemented as a BMS 466. The battery pack 438 includes two or more battery modules 440, 450. Each battery module 440, 450 includes two or more battery cells 446, 448, 456, 458 and a battery module controller 444, 454. In addition, each battery module 440, 450 includes a SE 442, 452 on which a small program is installed. The small program can be used to perform functions related to security. In addition, the BMS 466 also includes a SE 434 on which a small program for performing functions related to security is installed, and a microcontroller 436. In addition, the secure cloud server 460 includes a SE 462 on which a small program for performing functions related to security is installed, and a server PC 464. The secure cloud server 460 implements a battery management server of the type described.
[0041] The battery system and battery management server disclosed in the present invention help prevent unauthorized reuse of battery modules. In addition, the integrity of the reused battery module can be verified. More specifically, the battery module can be decoupled from the first battery system and coupled to the second battery system in a safe manner, that is, the coupling is performed by an entity that can be authenticated. If a battery module reaches a certain age, the battery module may no longer be suitable for some applications, but may still be suitable for other applications. Figure 3A and 4 The architecture shown in can only allow authorized stakeholders to utilize the purchased batteries. This in turn can also provide anti-theft protection for the battery modules. In addition, the battery system and battery management server disclosed in the present invention provide trust in reused battery modules. The integrity of battery-specific data (health status, manufacturer credentials, life cycle, etc.) can be ensured. This data is directly related to the value of the battery. Therefore, when a battery module is reused, the value and appropriate functionality of the battery module can be trusted to enhance overall user satisfaction, safety and performance.
[0042] The architecture includes different interrelated systems and devices, in particular, a first battery system, a second battery system, and a battery management server. The first battery system can be used, for example, in an electric vehicle, while the second battery system can be used in a smart home. Each of the first battery system and the second battery system includes a plurality of battery modules and a battery management unit operably coupled to the battery module. The battery management unit can be implemented as a so-called battery management system (BMS). The BMS may have a built-in SE on which a BMS applet is installed. In addition, the BMS applet may have been pre-provided with security keys and credentials in a trusted security environment. The trusted security environment can be implemented, for example, as the trust provision service mentioned above or as a trusted environment implemented by a module manufacturer. In addition, the status (life cycle, recharge cycle, health status, etc.) of each battery module can be frequently updated in the BMS applet. The battery system can be configured to transmit the battery module status to a battery management server (e.g., a secure cloud server). This information can be used by retailers to sell modules and by potential buyers to monitor the current status of the modules. In addition, the battery system can support pairing and unpairing of battery modules via a secure over-the-air (OTA) service. Using these services, specific battery modules may also be provisioned and / or prepared for re-pairing.
[0043] In addition, the multiple battery modules included in each battery system may be integrated into a so-called battery pack. Each battery module may have a SE on which a BMS applet is installed. In addition, each battery module may be identified by the BMS applet using an identifier of the module, which may also be stored in the SE of the module. In addition, the applet installed on the module SE may also securely store the status of the module (life cycle, recharge cycle, health status, etc.). In addition, the applet may have been pre-provided with security keys and credentials in a trusted security environment. A battery management server, which may be implemented as a secure cloud server managed by a service provider (SP), may also include a SE on which a BMS cloud service applet is installed. The battery management server may regularly monitor the status or condition of the battery module via synchronization with the battery management system of the battery system based on a configurable synchronization schedule. The battery management server facilitates the transfer of battery modules from a first battery system to a second battery system, in particular the pairing and unpairing of battery modules with the battery system.
[0044] The battery system and battery management server disclosed in the present invention can support several use cases. An example of such a use case is the reuse of old electric vehicle battery packs in smart homes. In such a use case, the owner of the vehicle can see all the characteristics (life cycle, recharge cycle, health status, etc.) of each battery module present in the electric vehicle and smart home via an online client. The owner should then remind the cloud service that they intend to reuse a specific battery module from the vehicle in the smart home. Therefore, the secure cloud server can initiate a depairing mechanism. In this step, the corresponding module can receive new credentials and keys that will be used to pair the battery module with the smart home. The current BMS host applet can also be updated accordingly. The smart home host can also receive similar password objects and details about the module it will receive. Then, the battery module can be simply unplugged from the vehicle and reinserted into the battery pack of the smart home. Once the new battery module is inserted into the battery pack of the smart home, an overall system check can be performed, and end-to-end authentication can be performed between the SE in the battery module and the SE in the BMS of the smart home. If the battery module is successfully authenticated, and if the status of the battery module is the same as it was at the last check (performed by the electric vehicle), the battery module can be added to the smart home's battery pack.
[0045] Another example of a use case is the reuse of old third-party vehicle battery packs in smart homes. In such use cases, the battery module is not only transferred from one battery system to another, but the owner of the battery module will change. In such use cases, the owner of the electric vehicle can sell its old battery pack or specific module to a third party online or via a registered entity. Therefore, a third party can enhance the smart home battery system by adding the used vehicle battery pack or module to its own smart home battery system. Because the battery module contains a SE with a BMS applet installed on it, all the characteristics of these battery modules are known and can be easily monitored via a secure cloud. After an agreement (e.g., payment) between the current owner and the new owner, the battery pack / module manufacturer can help unpair the battery pack from the vehicle and pair the battery pack with the smart home battery system by using the keys and credentials present in the SE. Since the battery module already contains a SE with a BMS applet, only remote provision of keys / credentials may be required. This can be done while the unpairing process is being performed using a secure cloud.
[0046] Another example of a use case is reusing a vehicle battery pack to charge a vehicle. In such a use case, a vehicle battery pack of its specific module can be added to an existing solar vehicle charging battery system. More specifically, the module's vehicle battery pack can be unpaired from the vehicle's battery system, allowing the vehicle battery pack to then be paired directly to the vehicle charging station using the secure cloud. Once connected, SE to SE authentication can take place, and the reused battery pack or module can help increase the storage capacity of the charging system.
[0047] Figure 5 Different roles 500 in a public key infrastructure (PKI) scheme are shown. The root certificate authority (CA) 502 may be, for example, an original equipment manufacturer (OEM) that produces a vehicle, a battery manufacturer, a smart home module manufacturer, a semiconductor company, or a consortium of government departments (e.g., the EU Drive Alliance). Battery OEM 504 may be a company that produces battery modules. In addition, SE manufacturer 508 may be a semiconductor company that applies secure trust supply. Cloud (SP) 506 may be a root entity that selects and authorizes service providers to sign and authenticate requests from SE manufacturers 508 and battery OEM 504. Users A and X 510, 512 may be end users who purchase battery modules (which may also be assembled inside a vehicle or in a complete smart home mobile power bank). Vehicle OEMs or smart home battery system suppliers may also be users and sell their systems to end users. In this example, user A 510 may be a vehicle manufacturer that owns many vehicles, and user X 512 may be an end user who owns a vehicle (produced by user A 510) and / or a home (purchased from another user). Although Figure 5 Only two users 510, 512 are shown in FIG. 1 , but the skilled person will appreciate that the scheme can be extended to include more than two users.
[0048] Based on the aforementioned roles, the following implementation scheme of the battery module transfer scheme can be envisioned. It can be assumed that the battery manufacturer is a member of the alliance or a similar entity driven by the root CA 502. In addition, it can be assumed that the SE manufacturer 508 is registered as an official entity at the alliance as the only issuer of the signed request and credentials confirmed by the service provider defined by the alliance. The battery manufacturer can then sign the battery manufacturing agreement with the alliance. The battery manufacturer can also confirm that the SE manufacturer 508 will manage the credentials and provide SE for the corresponding battery module. When the battery pack is produced, the certified and supplied SE can be embedded in each battery module. The battery manufacturer can query the service provider 506 to verify the SE and also register the battery module. The current battery status (life cycle, recharge cycle, health status, etc.) that can be stored in the BMS applet (within the SE) of each module can also be synchronized using the cloud.
[0049] The first user may have to register the battery module separately with the service provider 506. This registration can be done via the battery manufacturer or separately. For example, the vehicle manufacturer can also register all battery modules in its newly produced vehicles. At the time of the first registration, the battery condition can be checked and then mapped to the legitimate owner. This information can be saved in the cloud and in the BMS applet installed on the SE. The user has full access to this information via the cloud and can also ask the service provider 506 to publish battery characteristics for safe reuse. In the event of an application change, the user has the possibility of requesting a battery module application change via the service provider 506. For example, in this way, one or more battery modules from a vehicle can be safely reused in a smart home. Therefore, the mapping of the battery module can be updated in the cloud, and the BMS applet on the SE of the battery module can receive new credentials, which can be used for secure pairing with the battery system of the smart home. This process is relatively easy because the ownership of the battery module remains unchanged.
[0050] In the event of a change in ownership, a user who wants to sell or transfer ownership of a battery module may send a request to the service provider 506. The service provider 506 may then publish the battery module characteristics on a website that is accessible to all registered users. Any interested user may then request a quote, and if the buyer and seller reach an agreement, the service provider 506 may begin the process of ownership transfer. The service provider 506 may send a signed request to the current BMS connected to the battery module. This request may include a new key pair that can be used for authentication of the battery module by the new BMS. The current battery profile may also be synchronized using the cloud to prevent any tampering during the transfer phase. The service provider 506 may also share a key pair with the new BMS for authentication of the battery module. The battery module may then be unpaired from the current battery system and may be locked for use in a new battery system. If the battery is lost or misused in another battery system, the authentication will fail and the module will be unavailable. Once the module is inserted into the correct battery system, the authentication is successfully performed, and the battery characteristics may then be acquired and compared to the last entry. If everything is synchronized, the battery module may be used in the new battery system.
[0051] An example of a certificate that can be used is an X.509 certificate. In addition, an example of a key that can be used is an elliptic curve cryptography (ECC) key pair for encryption and signature verification. In addition, the trust provision of the certificate (signed by the root CA 502) to the SE can be implemented by the SE manufacturer 508 based on the mutual agreement between the battery OEM 504 and the root CA 502 and the mutual agreement between the SE manufacturer 508 and the root CA 502.
[0052] The PKI scheme mentioned above can be used in the case of a change of ownership in the following manner. After receiving the ownership transfer request from user A 510, the service provider 506 can send a signed and encrypted request (i.e., encrypted using its private key) to the BMS of the vehicle registered to user A 506. The request can also contain a new key pair that will be used to authenticate to the BMS of user X 512. The BMS of user A 506 can verify and decrypt the request using the pre-provided public key and decryption key. According to the request, the battery module can be unpaired and the new key can be provisioned in the BMS applet on the SE installed on the battery module. This will prepare the battery module for pairing with the new battery system (i.e., pairing with the battery system of user X 512). The current battery module characteristics (i.e., status information) can also be obtained in a secure manner and sent to the cloud (i.e., SP 506). Once user X 512 connects the new battery module to his BMS, the system can scan the complete battery pack and share the details of the newly attached module with SP 506. SP 506 may check the received battery module characteristics again, and if everything is correct, SP 506 may share the same key with the BMS of User X 512. The BMS of User X 512 may then perform a pairing operation with the new battery module, and after the final authentication, the BMS may again send an encrypted and signed message to SP 506, thereby confirming that the pairing was successful and informing SP 506 that it should update its registry accordingly.
[0053] It should be noted that the above embodiments have been described with reference to different subject matters. In particular, some embodiments may have been described with reference to method-type claims, while other embodiments may have been described with reference to apparatus-type claims. However, a person skilled in the art will appreciate from the above that, unless otherwise stated, any combination of features relating to different subject matters, in particular a combination of features of a method-type claim with features of an apparatus-type claim, in addition to any combination of features belonging to one type of subject matter, is also considered to be disclosed with this document.
[0054] In addition, it should be noted that the drawings are schematic. In different drawings, similar or identical elements are represented by the same figure mark. In addition, it should be noted that in order to provide a concise description of the illustrative embodiments, the implementation details that belong to the customary practices of technicians may not be described. It should be understood that in the development of any such implementation scheme, as in any engineering or design project, a large number of implementation scheme-specific decisions must be made in order to achieve the specific goals of the developer, such as complying with system-related and business-related constraints, which may be different in different implementation schemes. In addition, it should be understood that such development work may be complex and time-consuming, but it is nothing more than a routine task for those skilled in the art to design, manufacture and produce.
[0055] Finally, it should be noted that a person skilled in the art will be able to design many alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claims. The words "comprise(s)" or "comprising" do not exclude the presence of elements or steps other than those listed in the claims. The words "a" or "an" preceding an element do not exclude the presence of a plurality of such elements. The measures recited in the claims may be implemented by means of hardware comprising several different elements and / or by means of a suitably programmed processor. In a device claim listing several components, several of these components may be embodied by the same item in hardware. The mere fact that certain measures are recited in different dependent claims does not indicate that a combination of these measures cannot be used to advantage.
[0056] Reference numerals list
[0057] 100 Electric vehicles
[0058] 102 Battery Management System
[0059] 104 Microcontroller
[0060] 106 Battery Pack
[0061] 108 battery module 1
[0062] 110 battery module controller 112 battery unit 1
[0063] 114 battery cells x
[0064] 116 battery modules x
[0065] 118 battery module controller 120 battery unit 1
[0066] 122 battery cells x
[0067] 200 Smart Home
[0068] 202 Battery Management System
[0069] 204 Microcontroller of battery management system 206 Battery pack 208 Battery module 1
[0070] 210 battery module controller 212 battery unit 1
[0071] 214 battery cells x
[0072] 216 battery modules x
[0073] 218 battery module controller 220 battery unit 1
[0074] 222 battery cells x
[0075] 300 Battery Management Architecture
[0076] 302 First Battery System
[0077] 304 Battery Management Unit
[0078] 306 Battery Module
[0079] 308 Battery Module
[0080] 310 Second Battery System
[0081] 312 Battery Management Unit
[0082] 314 Battery Module
[0083] 316 Battery Module
[0084] 318 Battery Management Server
[0085] 320 Method for configuring the first battery system
[0086] 322 provides a plurality of battery modules to a first battery system 324 provides a battery management unit operably coupled to the battery modules to the first battery system, wherein the battery management unit includes a security element, wherein the battery management unit is configured to receive a signed request from an external server, wherein the signed request is a request to decouple at least one of the battery modules from the first battery system, and wherein the battery management unit is configured to verify the signed request using a public key stored in the security element
[0087] 326 Method for configuring a second battery system
[0088] 328 providing a plurality of battery modules to the second battery system 330 providing a battery management unit operably coupled to the battery module to the second battery system, wherein the battery management unit is configured to detect insertion of a new battery module into the second battery system, wherein the battery management unit is configured to read an identifier from a safety element included in the new battery module upon or after the detection, and wherein the battery management unit is configured to transmit the identifier to an external server
[0089] 332 Method for operating a battery management server
[0090] 334 transmitting a signed request to an external first battery system, wherein the signed request is a request to decouple at least one of the plurality of battery modules from the first battery system 336 transmitting a cryptographic key and / or cryptographic credential to an external second battery system, wherein the cryptographic key and / or cryptographic credential enables the second battery system to couple the battery module that has been decoupled from the first battery system to the second battery system
[0091] 338 Security Element
[0092] 340 Security Element
[0093] 342 Security Element
[0094] 344 Security Element
[0095] 346 Security Element
[0096] 348 Security Element
[0097] 350 Safety Elements
[0098] 400 Battery Management Architecture 402 Electric Vehicles
[0099] 404 Battery Management System 406 Safety Component
[0100] 408 microcontroller 410 battery pack 412 battery module 1
[0101] 414 Safety element 416 Battery module controller 418 Battery unit 1
[0102] 420 battery cell x422 battery module x424 safety element 426 battery module controller 428 battery cell 1
[0103] 430 battery unit x432 Smart Home
[0104] 434 Security Element
[0105] 436 Microcontroller 438 Battery pack 440 Battery module 1
[0106] 442 Safety element 444 Battery module controller 446 Battery unit 1
[0107] 448 battery cells x450 battery modules x
[0108] 452 Security Element
[0109] 454 Battery module controller 456 Battery unit 1
[0110] 458 battery cells x
[0111] 460 Secure Cloud Server
[0112] 462 Secure Element 464 Server PC
[0113] 466 Battery Management System
[0114] 500 Roles in Public Key Infrastructure Scenarios 502 Root Certificate Authority 504 Battery OEM 506 Cloud (Service Provider)
[0115] 508 Secure Element Manufacturer 510 User A 512 User X 514 Vehicle
[0116] 516 Home
[0117] 518 Vehicle 520 Home.
Claims
1. A first battery system, characterized in that: include: Multiple battery modules; a battery management unit operably coupled to the battery module, wherein the battery management unit includes a safety element; The battery management unit is configured to receive a signed request from an external server, wherein the signed request is a request to decouple at least one of the battery modules from the system, and wherein the battery management unit is configured to verify the signed request using a public key stored in the secure element.
2. The system according to claim 1, characterized in that The signed request has been encrypted by the external server, and wherein the battery management unit is further configured to decrypt the request using a decryption key stored in the secure element.
3. The system according to claim 1 or 2, characterized in that: The battery management unit is further configured to transmit status information to the external server, wherein the status information indicates a status of one or more of the battery modules, and wherein the battery management unit has read the status information from a safety element included in the battery module.
4. The system according to claim 3, characterized in that The condition information includes data indicating a life cycle, data indicating a recharge cycle, data indicating a state of health of the battery module, and / or data indicating a manufacturer of the battery module.
5. A system according to any of the preceding claims, characterised in that The battery management unit is further configured to receive a cryptographic key and / or cryptographic credential from the external server, and wherein the battery management unit is configured to store the cryptographic key and / or cryptographic credential in a secure element of at least one of the battery modules to be decoupled in the battery module.
6. A method for configuring a first battery system, characterized in that: include: providing the system with a plurality of battery modules; providing the system with a battery management unit operably coupled to the battery module, wherein the battery management unit includes a safety element; The battery management unit is configured to receive a signed request from an external server, wherein the signed request is a request to decouple at least one of the battery modules from the system, and wherein the battery management unit is configured to verify the signed request using a public key stored in the secure element.
7. A second battery system, characterized in that: include: Multiple battery modules; a battery management unit operably coupled to the battery module; The battery management unit is configured to detect insertion of a new battery module into the system, wherein the battery management unit is configured to read an identifier from a security element included in the new battery module upon or after the detection, and wherein the battery management unit is configured to transmit the identifier to an external server.
8. A method for configuring a second battery system, characterized in that: include: providing the system with a plurality of battery modules; providing the system with a battery management unit operably coupled to the battery module; The battery management unit is configured to detect insertion of a new battery module into the system, wherein the battery management unit is configured to read an identifier from a security element included in the new battery module upon or after the detection, and wherein the battery management unit is configured to transmit the identifier to an external server.
9. A battery management server, characterized in that: Configured to: transmitting a signed request to an external first battery system, wherein the signed request is a request to decouple at least one of the plurality of battery modules from the first battery system; The cryptographic key and / or cryptographic credential are transmitted to an external second battery system, wherein the cryptographic key and / or cryptographic credential enable the second battery system to couple the battery module that has been decoupled from the first battery system to the second battery system.
10. A method for operating a battery management server, characterized in that: include: transmitting a signed request to an external first battery system, wherein the signed request is a request to decouple at least one of the plurality of battery modules from the first battery system; The cryptographic key and / or cryptographic credential are transmitted to an external second battery system, wherein the cryptographic key and / or cryptographic credential enable the second battery system to couple the battery module that has been decoupled from the first battery system to the second battery system.
