Battery operating system, battery operating method, and electronic device comprising battery management device

Abstract

At least one first processor of an electronic device included in a battery operating system, according to one embodiment of the present document, can transmit an encrypted first identification code to a server, receive a second identification code encrypted by the server, and authenticate the validity of a battery management device, and at least one second processor of the server included in the battery operating system can obtain the identifier of the battery management device by decrypting the encrypted first identification code, identify the validity of the battery management device, encrypt the second identification code, and transmit the second identification code to the electronic device.

Description

Electronic device including a battery operating system, a battery operating method, and a battery management device

[0001] Cross-citation with related applications

[0002] This application claims the benefit of priority to Republic of Korea Patent Application No. 10-2024-0122595, filed September 9, 2024, the entire contents of which are incorporated herein by reference.

[0003] Technology field

[0004] Embodiments disclosed in this document relate to an electronic device including a battery operating system, a battery operating method, and a battery management device.

[0005] As electric vehicles (EVs) proliferate, research and development on new vehicle architectures are actively underway. For example, electric vehicles can be powered by secondary batteries, which are rechargeable and include both conventional Ni / Cd and Ni / MH batteries, as well as more recent lithium-ion batteries. Among secondary batteries, lithium-ion batteries have the advantage of having a much higher energy density than conventional Ni / Cd and Ni / MH batteries. Furthermore, lithium-ion batteries can be manufactured in a compact and lightweight form, making them a power source for mobile devices. Recently, their use has expanded to include power sources for electric vehicles, attracting attention as a next-generation energy storage medium.

[0006] Battery cells, battery modules, battery packs, or battery racks like these can be utilized in a variety of devices. For example, batteries can be used in mobile devices such as cell phones, laptops, smartphones, and tablets, as well as in electric vehicles (EVs, HEVs, PHEVs) and large-capacity energy storage systems (ESS).

[0007] These batteries can have their status and operation managed and controlled by a battery management system (BMS). The BMS can be included with the batteries in a single device.

[0008] Meanwhile, as the automotive industry evolves, concepts of future mobility, such as Software Defined Vehicles (SDVs) and Purpose-Built Vehicles (PBVs), are gradually taking shape. For example, SDVs refer to cars whose hardware is controlled and managed by software. Software within SDVs can define not only a car's driving performance but also its convenience and safety features, its emotional quality, and even its brand identity.

[0009] Under the SDV architecture, technologies are being developed to improve the stability of electronic devices by identifying the effectiveness of battery management systems.

[0010] According to embodiments disclosed in this document, it is intended to provide a battery operation system for authenticating the validity of a battery management device, a battery operation method, and an electronic device including a battery management device.

[0011] According to embodiments disclosed in this document, it is intended to provide a battery management system, a battery management method, and an electronic device including a battery management device that restricts specified operations based on authenticating the validity of the battery management device.

[0012] According to embodiments disclosed in this document, it is intended to provide a battery management system, a battery management method, and an electronic device including a battery management device, which restricts specified operations and performs other specified operations even when the validity of the battery management device is not authenticated.

[0013] The technical challenges of this document are not limited to the technical challenges mentioned above, and other technical challenges not mentioned will be clearly understood by those skilled in the art from the descriptions below.

[0014] A battery operation system according to one embodiment of the present document may include an electronic device including a battery management system (BMS), and a server.

[0015] According to one embodiment, at least one first processor included in the electronic device is configured to transmit a first identification code encrypted based on a first asymmetric key from the battery management device to the server, receive a second identification code encrypted from the server, and authenticate the validity of the battery management device based on a correspondence between the second identification code decrypted from the battery management device and the first identification code, and at least one second processor of the server can decrypt the encrypted first identification code to obtain an identifier of the battery management device, identify the validity of the battery management device based on the identifier, encrypt a second identification code corresponding to the first identification code based on a second asymmetric key corresponding to the first asymmetric key, and transmit the second identification code encrypted from the server to the electronic device.

[0016] According to one embodiment, the first identification code may include the identifier and a random code randomly generated by the battery management device, and the second identification code may include the identifier of the server and the random code.

[0017] According to one embodiment, the at least one first processor may limit the output of a battery corresponding to the battery management device or may not provide part or all of the battery status of the battery to the outside if the encrypted second identification code is not received from the server.

[0018] According to one embodiment, the at least one first processor may control the battery to operate after a specific time from the time at which the operation of the battery corresponding to the battery management device is requested, or to retransmit the encrypted first identification code to the server after a specific time from the time at which the encrypted second identification code is not received from the server.

[0019] According to one embodiment, the at least one first processor may limit external provision of a battery status related to a state of health (SOH) of a battery corresponding to the battery management device if an encrypted second identification code is not received from the server.

[0020] According to one embodiment, the at least one first processor can externally provide a battery status related to the state of charge (SOC) of the battery even if the encrypted second identification code is not received from the server.

[0021] An electronic device according to another embodiment of the present document may include a battery management system (BMS) and at least one first processor.

[0022] According to one embodiment, the at least one first processor is configured to transmit a first identification code encrypted based on a first asymmetric key from the battery management device to a server, receive a second identification code encrypted from the server in response to the server identifying the validity of the battery management device, and authenticate the validity of the battery management device based on a correspondence between the second identification code decrypted in the battery management device and the first identification code, wherein the second identification code may be encrypted using a second asymmetric key corresponding to the first asymmetric key and correspond to the first identification code based on the identification of the validity of the battery management device according to an identifier of the battery management device obtained by decrypting the encrypted first identification code.

[0023] According to one embodiment, the first identification code may include the identifier and a random code randomly generated by the battery management device, and the second identification code may include the identifier of the server and the random code.

[0024] According to one embodiment, the at least one first processor may limit the output of a battery corresponding to the battery management device or may not provide part or all of the battery status of the battery to the outside if the encrypted second identification code is not received from the server.

[0025] According to one embodiment, the at least one first processor may control the battery to operate after a specific time from the time at which the operation of the battery corresponding to the battery management device is requested, or to retransmit the encrypted first identification code to the server after a specific time from the time at which the encrypted second identification code is not received from the server.

[0026] According to one embodiment, the at least one first processor may limit external provision of a battery status related to a state of health (SOH) of a battery corresponding to the battery management device if an encrypted second identification code is not received from the server.

[0027] According to one embodiment, the at least one first processor can externally provide a battery status related to a state of charge (SOC) of the battery even if an encrypted second identification code is not received from the server.

[0028] According to another embodiment of the present document, a battery management method may include an operation of transmitting, by an electronic device, a first identification code encrypted based on a first asymmetric key from a battery management device included in the electronic device to a server, an operation of decrypting, by the server, the encrypted first identification code to obtain an identifier of the battery management device, an operation of identifying, by the server, the validity of the battery management device based on the identifier, an operation of encrypting, by the server, a second identification code corresponding to the first identification code based on a second asymmetric key corresponding to the first asymmetric key, an operation of transmitting, by the server, the encrypted second identification code to the electronic device, an operation of receiving, by the electronic device, the second identification code encrypted from the server, and an operation of authenticating, by the electronic device, the validity of the battery management device based on a correspondence between the decrypted second identification code from the battery management device and the first identification code.

[0029] According to one embodiment, the first identification code may include the identifier and a random code randomly generated by the battery management device, and the second identification code may include the identifier of the server and the random code.

[0030] According to one embodiment, the battery operation method may further include an operation of limiting the output of a battery corresponding to the battery management device or not providing part or all of the battery status of the battery to the outside when an encrypted second identification code is not received from the server.

[0031] According to one embodiment, the battery operation method may further include an operation of retransmitting the encrypted first identification code to the server after a specified time from the time at which the encrypted first identification code is transmitted to the server, if the encrypted second identification code is not received from the server, or controlling the battery to operate the battery after a specified time from the time at which the operation of the battery corresponding to the battery management device is requested.

[0032] According to one embodiment, the battery operation method may further include an operation of limiting external provision of a battery status related to a state of health (SOH) of a battery corresponding to the battery management device when an encrypted second identification code is not received from the server.

[0033] According to one embodiment, the battery operation method may further include an operation of providing a battery status related to a state of charge (SOC) of the battery to an external party even when an encrypted second identification code is not received from the server.

[0034] This technology can authenticate the validity of a battery management device.

[0035] Additionally, the present technology can restrict specified operations based on authenticating the validity of a battery management device.

[0036] Additionally, the present technology can restrict specified operations and perform other specified operations even when the validity of the battery management device is not verified.

[0037] In addition, various effects may be provided, either directly or indirectly, through this document.

[0038] FIG. 1 is a conceptual diagram showing the structure of a vehicle including an electronic device in an electronic device including a battery operation system, a battery operation method, and a battery management device according to one embodiment of the present document.

[0039] FIG. 2 is a conceptual diagram showing the structure of a vehicle including an electronic device in an electronic device including a battery operation system, a battery operation method, and a battery management device according to one embodiment of the present document.

[0040] FIG. 3 is a block diagram showing the configuration of a battery operation system in an electronic device including a battery operation system, a battery operation method, and a battery management device according to one embodiment of the present document.

[0041] FIG. 4 is a block diagram showing the configuration of an electronic device including a battery operation system, a battery operation method, and a battery management device according to one embodiment of the present document.

[0042] FIG. 5 illustrates an example of an electronic device, including a battery operation system, a battery operation method, and a battery management device according to one embodiment of the present document.

[0043] FIG. 6 illustrates an example of signaling between an electronic device and a server in an electronic device including a battery operation system, a battery operation method, and a battery management device according to one embodiment of the present document.

[0044] FIG. 7 illustrates an example of a flow of operations of an electronic device for authenticating the validity of a battery management device in an electronic device including a battery management system, a battery management method, and a battery management device according to an embodiment of the present document.

[0045] FIG. 8 is a block diagram showing the hardware configuration of a computing system that performs a battery operation method in an electronic device including a battery operation system, a battery operation method, and a battery management device according to one embodiment of the present document.

[0046] Hereinafter, some embodiments disclosed in this document are described with reference to the accompanying drawings, which illustrate various embodiments of this document. However, this is not intended to limit the present technology to specific embodiments, and it should be understood that various modifications, equivalents, and / or alternatives of the embodiments of this technology are included.

[0047] When assigning reference numerals to components in each drawing, it should be noted that identical components are assigned the same numerals whenever possible, even if they are shown in different drawings. Furthermore, when describing various embodiments disclosed in this document, if a detailed description of a related known configuration or function is deemed to hinder understanding of the embodiments of the present invention, the detailed description will be omitted. The singular form of a noun corresponding to an item may include one or more items, unless the context clearly indicates otherwise.

[0048] In describing the components of the embodiments of this document, terms such as first, second, A, B, (a), (b), etc. may be used. These terms are only intended to distinguish the components from other components, and the nature, order, or sequence of the components may not be limited by the terms. In addition, unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by a person of ordinary skill in the art to which the embodiments disclosed in this document belong. Terms defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning they have in the context of the relevant technology, and shall not be interpreted in an idealized or overly formal sense unless explicitly defined in this application.

[0049] In addition, in the present disclosure, expressions such as "more than" or "less than" may be used to determine whether a specific condition is satisfied or fulfilled. However, this is merely a description for expressing an example and does not exclude descriptions such as "more than" or "less than." Conditions described as "more than" may be replaced with "more than," conditions described as "less than," and conditions described as "more than and less than" may be replaced with "more than and less than." In addition, hereinafter, "A" to "B" mean at least one of the elements from A (including A) to B (including B).

[0050] In this document, each of the phrases "A or B", "at least one of A and B", "at least one of A or B", "A, B, or C", "at least one of A, B, and C", and "at least one of A, B, or C" may include any one of the items listed together in that phrase, or all possible combinations thereof.

[0051] In this document, when a component (e.g., a first component) is referred to as being “connected,” “coupled,” or “connected,” with or without the terms “functionally” or “communicatively,” or is referred to as being “coupled” or “connected,” it means that the component can be connected to the other component directly (e.g., wired), wirelessly, or through a third component.

[0052] According to one embodiment, the method according to the various embodiments disclosed in the present document may be provided as included in a computer program product. The computer program product may be traded as a product between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., compact disc read-only memory (CD-ROM)), or may be distributed online (e.g., downloaded or uploaded) through an application store or directly between two user devices. In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily generated in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or an intermediary server.

[0053] According to various embodiments, each component (e.g., a module or a program) of the described components may include one or more entities, and some of the entities may be separated and placed in other components. According to various embodiments, one or more components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (e.g., a module or a program) may be integrated into a single component. In such a case, the integrated component may perform one or more functions of each of the plurality of components identically or similarly to those performed by the corresponding component among the plurality of components prior to integration. According to various embodiments, the operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.

[0054] Hereinafter, embodiments of the present document will be described in detail with reference to FIGS. 1 to 8.

[0055] FIG. 1 is a conceptual diagram showing the structure of a vehicle including an electronic device in an electronic device including a battery operation system, a battery operation method, and a battery management device according to one embodiment of the present document.

[0056] Referring to FIG. 1, a vehicle (110) including an electronic device (e.g., an electronic device (203) of FIG. 3) may include at least one of a first zone controller (121), a second zone controller (122), a third zone controller (123), a fourth zone controller (124), a first terminal device (131), a second terminal device (132), a third terminal device (133), a fourth terminal device (134), a first actuator (141), a second actuator (142), a high performance computer (HPC) (150) (e.g., at least one first processor (305) of FIG. 4), a transmit / receive path (160), an additional element (170), or any combination thereof.

[0057] According to one embodiment, the electronic device (203) may include at least some of the components included in a vehicle (110) according to a software defined vehicle (SDV) architecture.

[0058] For example, the electronic device (203) may obtain a first identification code encrypted based on an asymmetric key from components of the vehicle (110) in the battery management device, and transmit the encrypted first identification code to a server (e.g., server (205) of FIG. 3).

[0059] At least one first processor (e.g., at least one first processor (305) of FIG. 4) included in the electronic device (203) may include an HPC (150).

[0060] At least one third processor that may be included in the electronic device (203) may include a zoning controller (e.g., a first zoning controller (121), a second zoning controller (122), a third zoning controller (123), and a fourth zoning controller (124)).

[0061] According to one embodiment, a battery management device (301) mounted on a vehicle (110) may include at least some of the components included in the vehicle (110).

[0062] For example, components according to the SDV architecture may include a hierarchy of HPC (150), zoning controller, and end device order.

[0063] For example, the HPC (150) is connected to the first zoning controller (121), the second zoning controller (122), the third zoning controller (123), and the fourth zoning controller (124), and can transmit and receive various types of data with each zoning controller.

[0064] For example, a first zoning controller (121) can control a first terminal device (131), a second zoning controller (122) can control a second terminal device (132), a third zoning controller (123) can control a third terminal device (133), and a fourth zoning controller (124) can control a fourth terminal device (134).

[0065] For example, the terminal device may include at least one of the batteries (or, a battery management system (BMS)) mounted on the vehicle (110). For example, if one of the second terminal devices (132) is a BMS, the additional element (170) may be defined as a battery pack included in the first battery. For example, the first zoning controller (121) may control the first actuator (141), and the second zoning controller (122) may control the second actuator (142). For example, the first actuator (141) and the second actuator (142) may include at least one driving device for driving the vehicle (110).

[0066] For example, the components described above can perform communication based on a specified path (e.g., a transmission / reception path (160)) via automotive Ethernet.

[0067] For example, the HPC (150) or the zoning controller (e.g., the first zoning controller (121), the second zoning controller (122), the third zoning controller (123), the fourth zoning controller (124)) can communicate via the vehicle Ethernet.

[0068] At least one first processor (305) of an electronic device (203) according to one embodiment may include an HPC (150), or a zoning controller (e.g., a first zoning controller (121), a second zoning controller (122), a third zoning controller (123), a fourth zoning controller (124)).

[0069] In FIG. 1, the electronic device (203) is described as a vehicle (110), but this is merely an example, and the embodiments of this document may not be limited thereto. According to one embodiment, the electronic device (203) may be an electronic device other than a vehicle.

[0070] FIG. 2 is a conceptual diagram showing the structure of a vehicle including an electronic device in an electronic device including a battery operation system, a battery operation method, and a battery management device according to one embodiment of the present document.

[0071] In Fig. 2, the description of components defined with the same names as in Fig. 1 may be replaced with the description of Fig. 1 described above.

[0072] Referring to FIG. 2, the vehicle (210) may include at least one of a first terminal device (231), a second terminal device (232), a third terminal device (233), a fourth terminal device (234), a first actuator (241), a second actuator (242), a high performance computer (HPC) (250), a transmit / receive path (260), an additional element (270), or any combination thereof.

[0073] According to one embodiment, the electronic device (203) may include at least some of the components included in a vehicle (110) according to a software defined vehicle (SDV) architecture.

[0074] For example, the vehicle (210) according to FIG. 2 may not include a zoning controller compared to FIG. 1. That is, even if the SDV architecture is adopted, the vehicle (210) may be implemented with a structure in which the HPC (250) directly controls at least one terminal device, as in FIG. 2.

[0075] In FIG. 2, the electronic device (203) is described as a vehicle (210), but this is merely an example, and the embodiments of the present document may not be limited thereto. According to one embodiment, the electronic device (203) may be an electronic device other than a vehicle.

[0076] FIG. 3 is a block diagram showing the configuration of a battery operation system in an electronic device including a battery operation system, a battery operation method, and a battery management device according to one embodiment of the present document.

[0077] FIG. 4 is a block diagram showing the configuration of an electronic device including a battery operation system, a battery operation method, and a battery management device according to one embodiment of the present document.

[0078] Referring to FIGS. 3 and 4, a battery operation system (201) may include an electronic device (203) and a server (205). The electronic device (203) may include a battery management device (301) and at least one first processor (305). The at least one first processor (305) may execute at least one instruction stored in a memory.

[0079] According to one embodiment, the electronic device (203) may include a battery management device (301) that manages a battery.

[0080] According to one embodiment, the electronic device (203) may identify the validity of the battery management device (301) for safety purposes before operating the electronic device (203). Since additional devices can be detached in the SDV structure, the importance of verifying the validity of the battery management device (301) included in the electronic device (203) with the SDV structure may be higher than the importance of verifying the validity of the battery management device included in the electronic device without the SDV structure.

[0081] In one embodiment, even if the validity of the battery management device (301) is not confirmed and authentication is not performed, the battery management device (301) can move the vehicle or provide only a portion of the battery status to the outside in case of an emergency that requires the vehicle to move.

[0082] According to one embodiment, before the electronic device (203) is operated, at least one first processor (305) included in the electronic device (203) may transmit a first identification code encrypted based on a first asymmetric key from the battery management device (301) to the server (205).

[0083] A first asymmetric key may be stored in the battery management device (301) during the manufacturing process of the battery management device (301) to identify the validity of the battery management device (301). The first asymmetric key may correspond to a second asymmetric key stored in a server. A code encrypted using the first asymmetric key may be decrypted based on the second asymmetric key, and a code encrypted based on the second asymmetric key may be decrypted based on the first asymmetric key.

[0084] The first identification code may include a random code randomly generated by the battery management device (301) and an identifier of the battery management device (301).

[0085] According to one embodiment, at least one second processor of the server (205) can obtain an identifier of the battery management device (301) by decrypting the encrypted first identification code.

[0086] According to one embodiment, at least one second processor of the server (205) may identify the validity of the battery management device (301) based on the identifier of the battery management device (301). The identified validity of the battery management device (301) may indicate that the battery management device (301) is a genuine battery management device (301) manufactured by an authorized manufacturer.

[0087] For example, at least one second processor of the server (205) can identify the validity of the battery management device (301) by searching for the identifier of the battery management device (301) in a database. The database can include identifiers of each of the registered battery management devices.

[0088] According to one embodiment, at least one second processor of the server (205) may encrypt a second identification code corresponding to a first identification code based on a second asymmetric key corresponding to the first asymmetric key when an identifier of a battery management device (301) is searched in the database.

[0089] The second identification code may include a random code included in the first identification code and an identifier of the server (205).

[0090] According to one embodiment, at least one second processor of the server (205) can transmit a second identification code encrypted in the server (205) to the electronic device (203).

[0091] According to one embodiment, at least one first processor (305) of the electronic device (203) may receive an encrypted second identification code from the server (205). At least one first processor (305) of the electronic device (203) may decrypt the received encrypted second identification code, thereby obtaining a random code included in the second identification code and an identifier of the server (205).

[0092] According to one embodiment, at least one first processor (305) of the electronic device (203) can identify whether a random code included in a second identification code decrypted by the battery management device (301) corresponds to a random code generated by the battery management device (301).

[0093] According to one embodiment, at least one first processor (305) of the electronic device (203) may authenticate the validity of the battery management device (301) based on whether the random code included in the decrypted second identification code corresponds to a random code generated by the battery management device (301).

[0094] According to one embodiment, at least one first processor (305) of the electronic device (203) can authenticate the validity of the server (205) based on the identifier of the server (205) included in the decrypted second identification code corresponding to an identifier of a valid server (205) stored in the battery management device (301).

[0095] According to one embodiment, at least one first processor (305) of the electronic device (203) may operate the electronic device (203) by operating the battery based on the fact that the random code included in the decrypted second identification code corresponds to a random code generated by the battery management device (301) and the identifier of the server (205) included in the decrypted second identification code corresponds to an identifier of a valid server (205) stored in the battery management device (301).

[0096] According to one embodiment, at least one first processor (305) of the electronic device (203) may limit the output of the battery corresponding to the battery management device (301) or may not provide part or all of the battery status of the battery to the outside if the encrypted second identification code is not received from the server (205).

[0097] In one embodiment, operating the electronic device (203) when the battery management device (301) is not authenticated as when the battery management device (301) is authenticated may result in an accident.

[0098] According to one embodiment, at least one first processor (305) of the electronic device (203) may retransmit the encrypted first identification code to the server (205) after a specified time from the time at which the encrypted first identification code was transmitted to the server (205) if the encrypted second identification code is not received from the server (205). This is because there is a possibility that the second identification code was not received due to a communication problem between the electronic device (203) and the server (205).

[0099] According to one embodiment, at least one first processor (305) of the electronic device (203) may control the battery to operate after a specific time (e.g., a time between about 30 seconds and about 1 minute) from the time when the operation of the battery corresponding to the battery management device (301) is requested if the encrypted second identification code is not received from the server (205), thereby limiting the operation of the electronic device (203) including the unauthenticated battery management device (301).

[0100] According to one embodiment, at least one first processor (305) of the electronic device (203) may reduce personal information leakage by limiting the external provision of battery status related to the state of health (SOH) of the battery corresponding to the battery management device (301) if the encrypted second identification code is not received from the server (205). The external may include a user of the electronic device (203) or an external electronic device.

[0101] According to one embodiment, at least one first processor (305) of the electronic device (203) may externally provide a battery status related to the state of charge (SOC) of the battery corresponding to the battery management device (301) even when the encrypted second identification code is not received from the server (205). This is because there is a need to minimize personal information leakage while preparing for emergency situations.

[0102] FIG. 5 illustrates an example of an electronic device, including a battery operation system, a battery operation method, and a battery management device according to one embodiment of the present document.

[0103] Referring to FIG. 5, a vehicle (510) may include a battery (401), a battery management device (301), and at least one first processor (305). The vehicle (510) may represent one example of an electronic device (203).

[0104] In Fig. 5, the description of components defined with the same names as in Figs. 3 and 4 may be replaced with the description of Figs. 3 and 4 described above.

[0105] According to one embodiment, before the vehicle (510) is driven, at least one first processor (305) included in the vehicle (510) may transmit a first identification code encrypted based on a first asymmetric key from the battery management device (301) to the server (205).

[0106] According to one embodiment, at least one second processor of the server (205) can obtain an identifier of the battery management device (301) by decrypting the encrypted first identification code.

[0107] According to one embodiment, at least one second processor of the server (205) may identify the validity of the battery management device (301) based on the identifier of the battery management device (301). The identified validity of the battery management device (301) may indicate that the battery management device (301) is a genuine battery management device (301) manufactured by an authorized manufacturer.

[0108] According to one embodiment, at least one second processor of the server (205) may encrypt a second identification code corresponding to a first identification code based on a second asymmetric key corresponding to the first asymmetric key when an identifier of a battery management device (301) is searched in the database.

[0109] According to one embodiment, at least one second processor of the server (205) can transmit a second identification code encrypted in the server (205) to the vehicle (510).

[0110] According to one embodiment, at least one first processor (305) of the vehicle (510) can receive an encrypted second identification code from the server (205). At least one first processor (305) of the vehicle (510) can obtain a random code included in the second identification code and an identifier of the server (205) by decrypting the received encrypted second identification code.

[0111] According to one embodiment, at least one first processor (305) of the vehicle (510) can authenticate the validity of the battery management device (301) based on whether the random code included in the decrypted second identification code corresponds to a random code generated by the battery management device (301).

[0112] According to one embodiment, at least one first processor (305) of the vehicle (510) can authenticate the validity of the server (205) based on whether the identifier of the server (205) included in the decrypted second identification code corresponds to an identifier of a valid server (205) stored in the battery management device (301).

[0113] FIG. 6 illustrates an example of signaling between an electronic device and a server in an electronic device including a battery operation system, a battery operation method, and a battery management device according to one embodiment of the present document.

[0114] Hereinafter, it is assumed that at least one first processor (305) included in the electronic device (203) of FIG. 4 and at least one second processor included in the server (205) perform the process of FIG. 6. In addition, in the description of FIG. 6, an operation described as being performed by the electronic device (203) can be understood as being controlled by at least one first processor (305) of the electronic device (203), and an operation described as being performed by the server (205) can be understood as being controlled by at least one second processor of the server (205).

[0115] Referring to FIG. 6, in a first operation (501), according to one embodiment, at least one first processor (305) of the electronic device (203) may obtain a first identification code encrypted based on a first asymmetric key from the battery management device (301).

[0116] In a second operation (503), according to one embodiment, at least one first processor (305) of the electronic device (203) may transmit an encrypted first identification code to the server (205). According to one embodiment, at least one second processor of the server (205) may receive an encrypted first identification code from the electronic device (203).

[0117] In a third operation (505), according to one embodiment, at least one second processor of the server (205) can obtain an identifier of the battery management device (301) by decrypting the encrypted first identification code.

[0118] In the fourth operation (507), according to one embodiment, at least one second processor of the server (205) can identify the validity of the battery management device (301).

[0119] In the fifth operation (509), according to one embodiment, at least one second processor of the server (205) may encrypt the second identification code based on the second asymmetric key.

[0120] In the sixth operation (511), according to one embodiment, at least one second processor of the server (205) can transmit an encrypted second identification code to the electronic device (203). According to one embodiment, at least one first processor (305) of the electronic device (203) can obtain the encrypted second identification code from the server (205).

[0121] In the seventh operation (513), according to one embodiment, at least one first processor (305) of the electronic device (203) can decrypt the encrypted second identification code.

[0122] In the eighth operation (515), according to one embodiment, at least one processor (305) of the electronic device (203) may authenticate the validity of the battery management device (301) based on the correspondence between the decrypted second identification code and the first identification code.

[0123] FIG. 7 illustrates an example of a flow of operations of an electronic device for authenticating the validity of a battery management device in an electronic device including a battery management system, a battery management method, and a battery management device according to an embodiment of the present document.

[0124] Hereinafter, it is assumed that at least one first processor (305) of the electronic device (203) of FIG. 4 performs the process of FIG. 7. Furthermore, in the description of FIG. 7, the operations described as being performed by the electronic device (203) can be understood as being controlled by at least one first processor (305) of the electronic device (203).

[0125] Referring to FIG. 7, in a first operation (601), according to one embodiment, the electronic device (203) may transmit a first identification code encrypted based on a first asymmetric key from a battery management device (301) included in the electronic device (203) to a server.

[0126] In the second operation (603), according to one embodiment, the server (205) can decrypt the encrypted first identification code to obtain the identifier of the battery management device (301).

[0127] In the third operation (605), according to one embodiment, the server (205) can identify the validity of the battery management device (301) based on the identifier of the battery management device (301).

[0128] In the fourth operation (607), according to one embodiment, the server (205) may encrypt the second identification code corresponding to the first identification code based on the second asymmetric key corresponding to the first asymmetric key.

[0129] In the fifth operation (609), according to one embodiment, the server (205) may transmit an encrypted second identification code to the electronic device (203).

[0130] In the sixth operation (611), according to one embodiment, the electronic device (203) may receive an encrypted second identification code from the server (205).

[0131] In the seventh operation (613), according to one embodiment, the electronic device (203) can authenticate the validity of the battery management device (301) based on the correspondence between the second identification code decrypted in the battery management device (301) and the first identification code.

[0132] According to one embodiment, the electronic device (203) can operate the electronic device (203) based on the validity of the battery management device (301) being authenticated.

[0133] According to one embodiment, the electronic device (203) may retransmit the encrypted first identification code to the server (205) after a specified time from the time at which the encrypted first identification code is transmitted to the server (205) based on the fact that the validity of the battery management device (301) is not authenticated, control the battery to operate after a specified time from the time at which the operation of the battery corresponding to the battery management device (301) is requested, or restrict providing the battery status related to the state of health (SOH) of the battery corresponding to the battery management device (301) to the outside. According to one embodiment, the electronic device (203) may provide the battery status related to the state of charge (SOC) of the battery to the outside even when the validity of the battery management device (301) is not authenticated.

[0134] FIG. 8 is a block diagram showing the hardware configuration of a computing system that performs a battery operation method in an electronic device including a battery operation system, a battery operation method, and a battery management device according to one embodiment of the present document.

[0135] Referring to FIG. 8, a computing system (700) according to an embodiment disclosed in the present document may include an MCU (710), a memory (720), an input / output I / F (730), and a communication I / F (740).

[0136] The MCU (710) may be at least one processor that executes various programs stored in the memory (720) (e.g., a battery cell data collection program, a graph generation program, a data analysis program, a data decomposition algorithm, a normalization program, a battery cell diagnosis program, etc.), processes various information including battery cell characteristic data, latent variables, etc. through these programs, and performs functions of the electronic device (203) or server (205) shown in the above-described FIGS. 1 to 7.

[0137] The memory (720) can store various programs such as a battery cell data collection program, a graph generation program, a data analysis program, a data decomposition algorithm, a normalization program, and a battery cell diagnosis program.

[0138] Such memories (720) may be provided in multiples as needed. The memories (720) may be volatile memories or non-volatile memories. As volatile memories (720), RAM, DRAM, SRAM, etc. may be used. As non-volatile memories (720), ROM, PROM, EAROM, EPROM, EEPROM, flash memories, etc. may be used. The examples of the memories (720) listed above are merely examples and are not limited to these examples.

[0139] The input / output I / F (730) can provide an interface that enables data transmission and reception between an input device (not shown) such as a keyboard, mouse, or touch panel, and an output device (not shown) such as a display and the MCU (710).

[0140] The communication I / F (740) is a component capable of transmitting and receiving various data with the server, and may be any device capable of supporting wired or wireless communication. For example, the diagnostic device can transmit and receive various information, including battery cell shape models, from a separately provided external server via the communication I / F (740).

[0141] In this way, a computer program according to an embodiment disclosed in this document may be implemented as a module that is recorded in a memory (720) and processed by an MCU (710) to perform each function illustrated in FIGS. 2 to 3, for example.

[0142] In the above, although all components constituting the embodiments disclosed in this document have been described as being combined or operating in combination as one, the embodiments disclosed in this document are not necessarily limited to such embodiments. That is, within the scope of the purpose of the embodiments disclosed in this document, all of the components may be selectively combined and operated one or more times.

[0143] In addition, terms such as "include," "comprise," or "have" described above, unless specifically stated to the contrary, should be interpreted to imply the inclusion of the corresponding component, and thus should not be interpreted to exclude other components, but rather to include other components. All terms, including technical or scientific terms, have the same meaning as commonly understood by a person of ordinary skill in the art to which the embodiments disclosed in this document belong, unless otherwise defined. Commonly used terms, such as terms defined in a dictionary, should be interpreted to be consistent with the contextual meaning of the relevant technology, and shall not be interpreted in an idealized or overly formal sense, unless explicitly defined in this document.

[0144] The foregoing disclosure outlines features of several embodiments to enable those skilled in the art to better understand the aspects of the present disclosure. Those skilled in the art will readily appreciate that the present disclosure can be readily used as a basis for designing or modifying other structures to achieve the same purposes or advantages of the embodiments introduced herein. Furthermore, those skilled in the art will recognize that such equivalent structures do not depart from the scope of the present disclosure, and that various changes, substitutions, and modifications can be made herein without departing from the scope of the present disclosure.

Claims

An electronic device including a battery management system (BMS); and Including servers, At least one first processor included in the electronic device, The battery management device transmits a first identification code encrypted based on a first asymmetric key to the server, Receive a second identification code encrypted by the server from the server, It is configured to authenticate the validity of the battery management device based on the correspondence between the second identification code decrypted in the battery management device and the first identification code, At least one second processor of the above server, Decrypting the encrypted first identification code to obtain an identifier of the battery management device, Based on the above identifier, identify the validity of the battery management device, Encrypting a second identification code corresponding to the first identification code based on a second asymmetric key corresponding to the first asymmetric key, configured to transmit an encrypted second identification code from the server to the electronic device; Battery operating system. In claim 1, The above first identification code is, The identifier and a random code randomly generated from the battery management device, The above second identification code is, an identifier of the server, and including the random code, Battery operating system. In claim 1, At least one first processor, If the encrypted second identification code is not received from the server, configured to limit the output of a battery corresponding to the battery management device, or not to provide part or all of the battery status of the battery to the outside, Battery operating system. In claim 1, At least one first processor, If the encrypted second identification code is not received from the server, the encrypted first identification code is retransmitted to the server after a specified time from the time the encrypted first identification code is transmitted to the server, or configured to control the battery so that the battery operates after a specific time from the time when the operation of the battery corresponding to the battery management device is requested, Battery operating system. In claim 1, At least one first processor, If the encrypted second identification code is not received from the server, configured to limit external provision of a battery status related to the state of health (SOH) of a battery corresponding to the above battery management device; Battery operating system. In claim 1, At least one first processor, Even if the encrypted second identification code is not received from the server, configured to externally provide a battery status related to the SOC (state of charge) of the above battery, Battery operating system. Battery management system (BMS); and comprising at least one first processor, At least one first processor, The battery management device transmits a first identification code encrypted based on a first asymmetric key to the server, In response to the server identifying the validity of the battery management device, the server receives an encrypted second identification code from the server, It is configured to authenticate the validity of the battery management device based on the correspondence between the second identification code decrypted in the battery management device and the first identification code, The above second identification code is, Based on the identification of the validity of the battery management device according to the identifier of the battery management device obtained by decrypting the encrypted first identification code, the second asymmetric key corresponding to the first asymmetric key is encrypted and corresponds to the first identification code. Electronic devices. In claim 7, The above first identification code is, The identifier and a random code randomly generated from the battery management device, The above second identification code is, an identifier of the server, and including the random code, Electronic devices. In claim 7, At least one first processor, If the encrypted second identification code is not received from the server, configured to limit the output of a battery corresponding to the battery management device, or not to provide part or all of the battery status of the battery to the outside, Electronic devices. In claim 7, At least one first processor, If the encrypted second identification code is not received from the server, the encrypted first identification code is retransmitted to the server after a specified time from the time the encrypted first identification code is transmitted to the server, or configured to control the battery so that the battery operates after a specific time from the time when the operation of the battery corresponding to the battery management device is requested, Electronic devices. In claim 7, At least one first processor, If the encrypted second identification code is not received from the server, configured to limit external provision of a battery status related to the state of health (SOH) of a battery corresponding to the above battery management device; Electronic devices. In claim 7, At least one first processor, Even if the encrypted second identification code is not received from the server, configured to externally provide a battery status related to the state of charge (SOC) of the battery; Electronic devices. An operation of transmitting a first identification code encrypted based on a first asymmetric key from a battery management device included in the electronic device to a server by an electronic device; An operation of decrypting the encrypted first identification code by the server to obtain an identifier of the battery management device; An operation of identifying the validity of the battery management device based on the identifier by the server; An operation of encrypting a second identification code corresponding to the first identification code based on a second asymmetric key corresponding to the first asymmetric key by the server; An action of transmitting the encrypted second identification code to the electronic device by the server; An operation of receiving a second identification code encrypted by the server from the server by the electronic device; and configured to include an operation of authenticating the validity of the battery management device based on the correspondence between the second identification code decrypted by the battery management device and the first identification code by the electronic device; How to operate the battery. In claim 13, The above first identification code is, The identifier and a random code randomly generated from the battery management device, The above second identification code is, an identifier of the server, and including the random code, How to operate the battery. In claim 13, If the encrypted second identification code is not received from the server, Further comprising an operation of limiting the output of a battery corresponding to the battery management device or not providing part or all of the battery status of the battery to the outside. How to operate the battery. In claim 13, If the encrypted second identification code is not received from the server, the encrypted first identification code is retransmitted to the server after a specified time from the time the encrypted first identification code is transmitted to the server, or Further comprising an action of controlling the battery so that the battery operates after a specific time from the time when the operation of the battery corresponding to the battery management device is requested. How to operate the battery. In claim 13, If the encrypted second identification code is not received from the server, Further comprising an action of limiting external provision of a battery status related to the state of health (SOH) of a battery corresponding to the battery management device. How to operate the battery. In claim 13, Even if the encrypted second identification code is not received from the server, Further comprising an operation of providing a battery status related to the SOC (state of charge) of the battery to the outside. How to operate the battery.

Images