System and method for managing battery history information
By attaching a unique number and sequence information to the battery system to generate token information, and using a controller and database to manage battery history information, the reliability problem of battery reuse is solved, and safe reuse of batteries and effective resource management are realized.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- LG ENERGY SOLUTION LTD
- Filing Date
- 2025-09-05
- Publication Date
- 2026-06-09
Smart Images
Figure CN122180984A_ABST
Abstract
Description
Technical Field
[0001] Cross-references to related applications
[0002] This application claims priority and benefit to Korean Patent Application No. 10-2024-0135394, filed with the Korean Intellectual Property Office on October 7, 2024, the entire contents of which are incorporated herein by reference.
[0003] This disclosure relates to a battery history information management system and a battery history information management method using the battery history information management system. Background Technology
[0004] The reuse and recycling of batteries is a key challenge that must be addressed for future sustainable development. Modern society relies heavily on battery technology, which plays a crucial role in various fields, including electric vehicles, smart devices, and energy storage systems (ESS).
[0005] Even after batteries have reached the end of their lifespan, assessing their reusability and proper management is a crucial task. In particular, high-performance batteries such as lithium-ion batteries should be considered for reuse to maximize their remaining capacity and performance, rather than simply discarding them. Reuse reduces resource waste and minimizes environmental impact, as there may still be usable resources within the battery.
[0006] For batteries to be reused, a system that can reliably manage the condition and history of each battery is necessary. A thorough analysis of the battery's initial performance, the presence of damage during use, and remaining charge cycles is required to determine its reusability. In other words, for the safe reuse of batteries, comprehensive management of the battery's entire lifecycle is needed. A system is required to record and track all information about each battery, from its manufacturing stage to its use, including performance changes, replacement times, damage history, and final disposal. Summary of the Invention
[0007] Technical issues
[0008] The purpose of this disclosure is to provide a system and method for managing battery history information by using information about the appearance of the battery system that is attached to the battery system during manufacturing.
[0009] Technical solution
[0010] A battery history information management system according to an embodiment of the present invention includes: a database storing historical information generated for each battery system by organizing state information and component information of the battery system; and a controller that generates token information by combining a unique number and sequence information of a specific battery system, retrieves the historical information of the specific battery system from the database in response to a query request signal for historical information of the specific battery system received from a user terminal, and provides the retrieved historical information of the specific battery system, wherein, in response to a request signal received from the user terminal for checking whether the specific battery system has been tampered with or forged, the controller generates an information transmission request signal requesting the transmission of the unique number, sequence information and token information assigned to the specific battery system and transmits it to an identification module, and uses a first unique number, first sequence information and first token information received from the identification module for the specific battery system to check whether the specific battery system has been tampered with or forged.
[0011] The controller can determine whether to use the entire unique number or a portion of the unique number to generate the token information based on the number of characters contained in the unique number.
[0012] The controller can determine whether to use all or part of the sequence information to generate the token information based on the number of characters contained in the sequence information.
[0013] The controller can generate the token information by combining the unique number and the sequence information according to a predetermined generation rule.
[0014] The controller can add query details of historical information of a specific battery system retrieved from the database to the historical information of the corresponding battery system to update the historical information.
[0015] The controller can retrieve the generation rules used to generate the token information of the specific battery system from the historical information of the specific battery system stored in the database, apply the retrieved generation rules in reverse to obtain the second unique number and the second sequence information from the first token information, and determine whether the specific battery system has been tampered with or forged based on whether the first unique number and the second unique number are consistent and whether the first sequence information and the second sequence information are consistent.
[0016] If the first unique number and the second unique number are inconsistent, or if the first sequence information and the second sequence information are inconsistent, the controller can determine that the specific battery system has been tampered with or forged.
[0017] The controller can transmit the inspection results of whether the specific battery system has been tampered with or forged to the user terminal; A battery history information management method implemented through a battery history information management system according to an embodiment of the present invention includes: in response to a request signal received from the user terminal to check whether a specific battery system has been tampered with or forged, a controller generates an information transmission request signal requesting the transmission of a unique number, sequence information, and token information assigned to the specific battery system, and the controller transmits the information transmission request signal to an identification module; the controller checks whether the specific battery system has been tampered with or forged by using a first unique number, first sequence information, and first token information of the specific battery system received from the identification module; and the controller transmits the check result and historical information on whether the specific battery system has been tampered with or forged to the user terminal, and adds the check details and check result on whether the specific battery system has been tampered with or forged to the historical information of the specific battery system to update the historical information.
[0018] Checking whether a specific battery system has been tampered with or forged may include: retrieving information about the generation rules used when generating token information for the specific battery system from historical information of the specific battery system stored in a database; obtaining a second unique number and a second sequence information from the first token information by applying the generation rules in reverse; and determining whether the specific battery system has been tampered with or forged based on whether the first unique number and the second unique number are consistent and whether the first sequence information and the second sequence information are consistent.
[0019] The battery history information management method may further include generating token information for a specific battery system by utilizing the unique number and sequence information of the specific battery system received from the user terminal.
[0020] Generating the token information may include: the controller determining whether to generate the token information using all or a portion of the unique number based on the number of characters contained in the unique number; determining whether to generate the token information using all or a portion of the sequence information based on the number of characters contained in the sequence information; and generating the token information by combining the unique number and the sequence information according to a preset generation rule.
[0021] The battery history information management method may further include generating history information by organizing and listing the status information and component information received from the user terminal for each battery system.
[0022] Generating the historical information may include: each time the status information and component information are generated in the battery system, additionally receiving the status information and component information from the user terminal, and updating the historical information by adding the additionally received status information and component information to the historical information of the corresponding battery system.
[0023] The battery history information management method may further include: in response to a historical information query request signal for a specific battery system received from the user terminal, the controller retrieves the historical information of the specific battery system from the database and provides it.
[0024] Retrieving and providing historical information from the database may include adding query details of retrieving historical information of a specific battery system from the database to the historical information of the corresponding battery system to update the historical information.
[0025] Beneficial effects
[0026] According to one embodiment of the present invention, by tracking and managing the entire history of batteries from production to disposal, battery reliability can be increased and safe reuse can be ensured.
[0027] The effects that can be obtained from this disclosure are not limited to those described above, and other effects not mentioned will be clearly understood by those skilled in the art from the following description. Attached Figure Description
[0028] Figure 1 This is a diagram illustrating the communication process between a battery history information management system, a battery system, a user terminal, and an identification module according to an embodiment of this disclosure.
[0029] Figure 2 This is a block diagram of a battery history information management system according to an embodiment of the present disclosure.
[0030] Figure 3 This is a flowchart illustrating the process of creating and managing historical information in a battery history information system.
[0031] Figure 4 This is a flowchart illustrating the process by which a battery history information management system checks for tampering with a battery system based on historical information stored in a database.
[0032] Figure 5 This is a flowchart of a battery history information management method according to an embodiment of the present disclosure.
[0033] Figure 6 This is a flowchart of a tampering inspection step according to an embodiment of the present disclosure.
[0034] Figure 7 This is a flowchart of a battery history information management method according to an embodiment of the present disclosure.
[0035] Figure 8 This is a flowchart of the token information generation steps according to an embodiment of the present disclosure. Detailed Implementation
[0036] In describing embodiments of this specification, detailed descriptions of well-known technologies related to this disclosure will be omitted if it is determined that such detailed descriptions may obscure the essential points of this disclosure. Furthermore, the accompanying drawings are provided merely to facilitate understanding of the exemplary embodiments disclosed herein, and the technical concepts disclosed herein are not limited to the drawings. It should be understood that all modifications, equivalents, or substitutions included within the concept and scope of this disclosure are permitted.
[0037] Terms including ordinal numbers such as first, second, etc., are used only to describe various constituent elements and should not be interpreted as limiting these constituent elements. These terms are only used to distinguish one constituent element from other constituent elements.
[0038] Furthermore, it should be understood in this specification that when a component is referred to as "connected" or "linked" to another component, it can be directly connected or linked to the other component, or it can be connected or linked to another component, with another component intervening in between. On the other hand, it should be understood in this specification that when a component is referred to as "connected or directly linked" to another component, it can be connected or linked to the other component without another component intervening in between.
[0039] It should also be understood that the terms "comprising" and "having" as used in this specification specify the presence of the said feature, number, step, operation, component, part or combination thereof, but do not exclude the presence or addition of one or more other features, numbers, steps, operations, components, parts or combinations thereof.
[0040] The embodiments disclosed in this specification will be described in detail below with reference to the accompanying drawings.
[0041] Figure 1 This is a diagram illustrating the communication process between a battery history information management system 100 and a battery system 200, a user terminal 300, and an identification module 400 according to an embodiment of the present disclosure.
[0042] refer to Figure 1 The battery history information management system 100 can communicate with the user terminal 300 and the identification module 400 via a network.
[0043] The battery history information management system 100 is a system for storing and managing historical information about the battery system 200. Here, historical information means the organizational and listing information about the battery system 200 from the time the battery system 200 was manufactured to the present.
[0044] Historical information may include status information about the state of the battery system 200 and component information about the components included in the battery system 200. Status information refers to information about the state of the battery system 200 generated through its operation, and may include battery cell temperature, SOH, number of fast charge cycles, number of slow charge cycles, etc. Component information may include information about which components are included in the battery system 200, the manufacturing date of each component, whether each component needs to be replaced, and the replacement date, etc.
[0045] At this time, status information can be generated in the battery system 200, and component information can be generated in both the battery system 200 and the user terminal 300.
[0046] According to one embodiment, a battery history information management system 100 can receive status information and component information of a battery system 200 from a user terminal 300. The battery history information management system 100 can create, store, and manage historical information by organizing and listing the status information and component information. The battery history information management system 100 can receive a signal from the user terminal 300 requesting a query for historical information of a specific battery system 200 (hereinafter referred to as a "historical information query request signal"). In response to the historical information query request signal, the battery history information management system 100 can retrieve historical information about the corresponding battery system 200 from the database 120 and provide the retrieved information to the user terminal 300.
[0047] According to one embodiment, a battery history information management system 100 can receive a signal from a user terminal 300 requesting to check whether a specific battery system 200 has been tampered with or forged (hereinafter referred to as a "tampering check request signal"). The battery history information management system 100 can respond to the tampering check request signal to check whether the corresponding battery system 200 has been tampered with or forged, and provide the check result to the user terminal 300.
[0048] The battery history information management system 100 may include a controller 110, a database 120, and a communication unit 130. The following... Figure 2 The configuration of the battery history information management system 100 is described in detail.
[0049] Battery system 200 may include a battery pack and a battery management system (BMS). The battery pack may include multiple battery modules, and each battery module may include multiple battery cells. The BMS may be electrically connected to multiple battery modules as a configuration for monitoring and controlling the battery pack.
[0050] For example, the BMS can measure or predict the state of the battery cells and transmit the battery cell state information to the battery history information management system 100. The BMS can use the battery cell state information to control the operation of the battery module. For example, the BMS can use the battery module's cell voltage, temperature, etc., to perform power limiting, cell balancing, cooling control, etc.
[0051] According to one embodiment, a security sticker 210 (security seal) with a unique number can be attached to the outside of the battery system 200. According to the embodiment, the security sticker 210 can be an RFID tag composed of an antenna, a chip, etc.
[0052] Here, the safety sticker 210 is a safety device used to ensure the integrity of the battery system 200, and may be a label in the form of a sticker designed to check whether the battery system 200 has been opened or manipulated. The safety sticker 210 leaves a mark when physically damaged or removed, thereby preventing and warning of unauthorized opening or modification of the battery system 200.
[0053] A unique serial number is a unique number used to identify each safety sticker 210 and can be used to verify the authenticity of the battery system 200 to which the safety sticker 210 is attached. The unique serial number can be generated along with the safety sticker 210 during its manufacture. For example, the manufacturer of the safety sticker 210 can create a unique serial number during manufacturing and assign a unique serial number to each safety sticker 210. The unique serial number can be generated based on certain rules and formats specified by the manufacturer of the safety sticker 210.
[0054] The unique number assigned to the external safety sticker 210 attached to a specific battery system 200 can be transmitted to the battery history information management system 100 via the user terminal 300 and stored by the battery history information management system 100 in the historical information of the corresponding battery system 200.
[0055] For example, the battery system manufacturer can input information about a unique number assigned to the external safety sticker 210 attached to a specific battery system 200, as well as information about the battery system 200 with the safety sticker 210 attached, into the user terminal 300. The user terminal 300 can then transmit the information about the unique number and the information about the battery system 200 with the safety sticker 210 to the battery history information management system 100. The battery history information management system 100 can then store the information about the unique number assigned to the safety sticker 210 attached to the specific battery system 200 in the historical information of the battery system 200.
[0056] In other words, since a unique number is assigned to each safety sticker 210, and the unique number assigned to the safety sticker 210 is stored in the battery history information management system 100 along with information about the battery system 200 to which the safety sticker 210 is attached, the battery history information management system 100 can identify the battery system 200 by using the safety sticker 210, and based on this, can track and manage the battery system 200.
[0057] According to an embodiment, the safety sticker 210 can be attached to the exterior of each component included in the battery system 200. For example, the safety sticker 210 can be attached to all components of the battery system 200, such as the battery cells, battery modules, battery packs, and BMS included in the battery system 200, as well as the battery system 200 itself.
[0058] According to one embodiment, a barcode area 220 in which sequence information and token information are written can be provided on the exterior of the battery system 200. For example, the sequence information and token information in barcode form can be written into the barcode area 220 located on the exterior of the battery system 200.
[0059] Here, the sequence information is a unique serial number used to identify each battery system 200 and can indicate the order in which the battery systems 200 were manufactured. The sequence information can be generated for each battery system 200 during manufacturing. For example, the battery system manufacturer can create and record the sequence information for each battery system 200 during manufacturing. The sequence information can be generated based on certain rules and formats specified by the battery system manufacturer.
[0060] The sequence information written into the barcode area 220 of a specific battery system 200 can be transmitted to the battery history information management system 100 via the user terminal 300, and stored by the battery history information management system 100 in the historical information of the corresponding battery system 200.
[0061] For example, a battery system manufacturer can input sequence information written in the barcode area 220 of a specific battery system 200, along with information about the battery system 200 written in that sequence information, into a user terminal 300. The user terminal 300 can then transmit the sequence information and the information about the battery system 200 written therein to a battery history information management system 100. The battery history information management system 100 can then store the sequence information assigned to the specific battery system 200 in the historical information of the battery system 200.
[0062] In other words, the sequence information can be used to identify and track a specific battery system 200 among battery systems of the same model.
[0063] The token information is generated by combining a unique number and sequence information, and can be used to identify the battery system 200 or check for tampering with the battery system 200. The token information can be generated by the battery history information management system 100, and the battery history information management system 100 can store the token information assigned to a specific battery system 200 in the historical information of the corresponding battery system 200.
[0064] For example, a battery system manufacturer can input a unique number from a safety sticker 210 attached to the battery system 200 and serial information written in the barcode area 220 into a user terminal 300, and the user terminal 300 can transmit the input unique number and serial information to a battery history information management system 100. The battery history information management system 100 can then transmit token information generated by combining the unique number and serial information to the user terminal 300 and provide it to the battery system manufacturer. The battery system manufacturer can then input the provided token information into the barcode area 220 of the battery system 200. The following... Figure 2 The document describes in detail the process of generating token information by combining a unique number and sequence information in the battery history information management system 100.
[0065] According to an embodiment, sequence information and token information can be described for each component included in the battery system 200. For example, sequence information and token information can be described not only in the battery system 200, but also in all components of the battery system 200, such as battery cells, battery modules, battery packs, and BMS included in the battery system 200.
[0066] According to one embodiment, the battery system 200 can generate information about the battery system 200, namely, state information and component information. For example, the BMS can generate a history of battery cell state information obtained by measuring or predicting the state of the battery cells, and a history of using the battery cell state information as state information to control the operation of the battery module. As another example, when a component included in the battery system 200 is replaced, the BMS can generate replacement details as component information, such as the replacement target and replacement date.
[0067] User terminal 300 can be a device capable of communicating with battery history information management system 100. For example, user terminal 300 can be a computer, tablet PC, cordless phone, mobile phone, smartphone, smartwatch, smart glasses, portable game console, navigation device, etc.
[0068] According to one embodiment, the user terminal 300 can receive a command (hereinafter referred to as an "information storage command") from the battery system manufacturer to store the status information and component information of a specific battery system 200 in the historical information of the battery system 200. For example, the user terminal 300 can control the transmission of the status information and component information stored in the battery system 200 to the battery historical information management system 100. Furthermore, the user terminal 300 can generate a signal requesting the battery historical information management system 100 to store the status information and component information of a specific battery system 200 in the historical information of the battery system 200 in response to the information storage command input by the user.
[0069] According to one embodiment, the user terminal 300 can receive a command (hereinafter referred to as a "historical information query command") from a user to query historical information of a specific battery system 200. For example, a user can input a historical information query command by clicking a historical information query button provided by the display unit 310 of the user terminal 300 and entering information about one of the specified battery systems 200. The user terminal 300 can generate a historical information query request signal for the corresponding battery system 200 in response to the historical information query command input by the user. The user terminal 300 can provide the user with the historical information received from the battery historical information management system 100 through the display unit 310.
[0070] According to one embodiment, the user terminal 300 can receive a command from the user to check whether a specific battery system 200 has been tampered with or forged (hereinafter referred to as a "tampering check command"). For example, the user can input the tampering check command by clicking a tampering check button provided by the display unit 310 of the user terminal 300 and entering information about one of the specified battery systems 200. The user terminal 300 can generate a tampering check request signal for the corresponding battery system 200 in response to the tampering check command input by the user. The user terminal 300 can provide the user with the tampering check results of the specific battery system 200 received from the battery history information management system 100 through the display unit 310.
[0071] The identification module 400 is a device for identifying information attached to or written to the battery system 200. Here, the information attached to the battery system 200 refers to the unique number assigned to the security sticker 210, and the information written to the battery system 200 may refer to serial information and token information.
[0072] According to one embodiment, the identification module 400 can receive a signal (hereinafter referred to as an "information transmission request signal") from the battery history information management system 100 requesting the transmission of a unique number, sequence information, and token information assigned to a specific battery system 200. In response to the information transmission request signal, the identification module 400 can obtain a unique number from a security sticker 210 attached to the exterior of the specific battery system 200, and obtain the sequence information and token information described in the specific battery system 200. Hereinafter, the unique number, sequence information, and token information obtained by the identification module 400 are defined as a first unique number, a first sequence information, and a first token information, respectively. The identification module 400 can transmit the first unique number, the first sequence information, and the first token information to the battery history information management system 100.
[0073] According to an embodiment, the identification module 400 may be an RFID reader 410. For example, if the safety sticker 210 attached to the outside of the battery system 200 is an RFID tag consisting of an antenna and a chip, the RFID reader 410 can identify the RFID tag and obtain a first unique number included in the RFID tag.
[0074] According to an embodiment, the identification module 400 may be a barcode reader 420. For example, if the sequence information and token information described in the battery system 200 are barcodes, the barcode reader 420 may identify the barcodes described in the battery system 200 to obtain the first sequence information and the first token information.
[0075] According to an embodiment, the identification module 400 may be a device for acquiring images of the battery system 200. The identification module 400 may analyze the images of the battery system 200 to obtain a first unique number, first sequence information, and first token information. In this case, the identification module 400 may be a user terminal 300 or an image analysis device including a camera.
[0076] Network 500 refers to a connection structure that enables information exchange between various nodes (such as the battery history information management system 100, user terminal 300, and identification module 400). For example, Network 500 may include a local area network (LAN), a wide area network (WAN), the Internet (WWW), wired or wireless data communication networks, telephone networks, wired or wireless television communication networks, etc. Wireless data communication networks include, but are not limited to, 3G, 4G, 5G, 3GPP (3rd Generation Partnership Project), LTE (Long Term Evolution), WIMAX (World Interoperability for Microwave Access), Wi-Fi, Bluetooth communication, infrared communication, ultrasonic communication, visible light communication (VLC), LiFi, etc.
[0077] Figure 2 This is a block diagram of a battery history information management system 100 according to an embodiment of the present invention.
[0078] refer to Figure 2 According to one embodiment of the present disclosure, a battery history information management system 100 may include a controller 110, a database 120, and a communication unit 130.
[0079] The controller 110 can generate token information by combining the unique number and sequence information of a specific battery system 200 received from the user terminal 300. The token information generated in the controller 110 can be transmitted to the user terminal 300 and provided to the battery system manufacturer, and can be recorded in the battery system 200 by the battery system manufacturer. That is, the token information is information that links the identification information (i.e., sequence information) of a specific battery system 200 and the identification information (i.e., unique number) of the security sticker 210 attached to the battery system 200.
[0080] In an exemplary embodiment, controller 110 may determine whether to use the entire unique number or only a portion thereof to generate token information based on the number of characters contained in the unique number. For example, if the unique number contains ten or fewer characters (e.g., "1234567890"), controller 110 may use the entire unique number ("1234567890") as is. If the unique number contains more than ten characters (e.g., "234890678902"), that is, eleven or more characters, it may use the characters from the third to the tenth position of the unique number ("48906789") to generate token information.
[0081] According to an embodiment, controller 110 can determine whether to use all or part of the sequence information to generate token information based on the number of characters contained in the sequence information. For example, if the sequence information contains 17 or fewer characters (e.g., if the sequence information is 'AEK348KIO3WE234'), controller 110 can use the entire sequence information ('AEK348KIO3WE234') as is. If the sequence information contains more than 17 characters (e.g., if the sequence information is 'AEK34845KIO3321WE23344'), i.e., 18 or more, controller 110 can use the characters from the sixth to the seventeenth position of the sequence information ('845KIO3321WE') to generate token information. As another example, if the sequence information contains 18 or more characters, controller 110 can use the value obtained by one-way encryption of the sequence information using an initialization vector (IV) to generate token information.
[0082] According to an embodiment, the controller 110 can generate a token by combining a unique number and sequence information according to a predetermined generation rule. Here, the generation rule refers to the rule used when generating the token, and different generation rules can be applied to each battery system 200. The controller 110 can store information about the generation rules applied to generate the token assigned to a specific battery system 200 in the historical information of the battery system 200.
[0083] For example, controller 110 can generate token information ('ABCDEFGHIJKL-1234567890') by using a generation rule that lists the sequence information ('ABCDEFGHIJKL') after the unique number ("1234567890'"). As another example, controller 110 can divide the unique number ('1234567890') and the sequence information ('ABCDEFGHIJKL') into two parts respectively, and generate token information using a generation rule that lists the first part of the unique number ('12345') - the first part of the sequence information ('ABCDEF') - the last part of the unique number ('67890') - the last part of the sequence information ('GHIJKL') in that order.
[0084] The controller 110 can receive status information and component information of the battery system 200 from the user terminal 300. The controller 110 can organize and list the status information and component information of each battery system 200 to create historical information for each battery system 200, and can manage the created historical information by distinguishing the historical information created for each battery system 200.
[0085] For example, the status information and component information generated in the battery system 200 can be transmitted to the battery history information management system 100 via the user terminal 300. The controller 110 of the battery history information management system 100 can generate historical information for each battery system 200 by classifying the status information and component information of each battery system 200 and storing them in the database 120. Furthermore, the controller 110 can receive additional status information and component information generated from the battery system 200 and can add this additional information to the historical information of the corresponding battery system 200 to update the historical information stored in the database 120.
[0086] In other words, the battery history information management system 100 can receive information (status information, component information) about a specific battery system 200 from the battery system manufacturer when manufacturing the specific battery system 200, and can create and store historical information about the corresponding battery system 200. When additional information about the corresponding battery system 200 is received from the owner or user of the battery system 200 at any point during the sale, transportation or use of the corresponding battery system 200, the additional information can be added to the historical information of the corresponding battery system 200 to update the historical information stored in the database 120.
[0087] Controller 110 can retrieve historical information about a specific battery system 200 from database 120 in response to a historical information query request signal for that specific battery system 200 received from user terminal 300. Controller 110 can transmit the historical information retrieved from database 120 to user terminal 300. Controller 110 can update the historical information by adding details of the historical information retrieved from database 120 (hereinafter referred to as "query details") to the historical information of the corresponding battery system 200. Here, query details may include the date on which controller 110 received the historical information query request signal from user terminal 300 and the query result (e.g., historical information query failure, success, etc.).
[0088] The controller 110 can receive a request signal from the user terminal 300 to check for tampering of a specific battery system 200. In response to the tampering check request signal, the controller 110 can generate an information transmission request signal requesting the transmission of a unique number, sequence information, and token information assigned to the corresponding battery system 200, and transmit it to the identification module 400. The controller 110 can receive a first unique number, first sequence information, and first token information of the specific battery system 200 from the identification module 400. The controller 110 can use the first unique number, first sequence information, and first token information to check whether the battery system 200 has been tampered with or counterfeited.
[0089] According to an embodiment, controller 110 can retrieve information about the generation rules used when generating token information for a specific battery system 200, which is subject to checks for tampering or forgery, from historical information of the corresponding battery system 200 stored in database 120. Controller 110 can obtain a second unique number and second sequence information from the first token information by applying the retrieved generation rules in reverse. Controller 110 can determine whether the battery system 200 has been tampered with or forged based on whether the first unique number and the second unique number match and whether the first sequence information and the second sequence information match.
[0090] For example, if the first unique number and the second unique number do not match, the controller 110 can determine that the battery system 200 has been tampered with or counterfeited. The fact that the first unique number obtained from the safety sticker 210 attached to the battery system 200 does not match the second unique number obtained based on historical information stored in the database 120 means that the change to the safety sticker 210 attached to the battery system 200 has not been reported to the battery history information management system 100, that is, the safety sticker 210 attached to the battery system 200 has been changed by an unauthorized user, and therefore the controller 110 can determine that the battery system 200 has not been legally opened and that the battery system 200 has been tampered with or counterfeited.
[0091] As another example, if the first sequence information and the second sequence information are inconsistent, the controller 110 can determine that the battery system 200 has been tampered with or forged. The fact that the first sequence information described in the battery system 200 and the second sequence information obtained based on historical information stored in the database 120 are inconsistent means that changes to the battery system 200 have not yet been reported to the battery history information management system 100. Therefore, if the first sequence information and the second sequence information are inconsistent, the controller 110 can determine that the battery system 200 has been altered by an unauthorized user and that the battery system 200 has been tampered with or forged.
[0092] The controller 110 can transmit the results of checking whether the battery system 200 has been tampered with or counterfeited, along with historical information, to the user terminal 300. At this time, the owner or manufacturer of the battery system 200 can replace the battery system 200 determined to have been tampered with or counterfeited based on the inspection results with a normal battery system 200. The controller 110 can update the historical information by adding the tampering inspection details and results of a specific battery system 200 to the historical information of the battery system 200.
[0093] The controller 110 can communicate with the user terminal 300 and the identification module 400 via a network.
[0094] Historical information can be stored in database 120. At this point, historical information can be stored separately for each battery system 200. In database 120, the unique number, sequence information, and token information assigned to each battery system 200 can be stored separately. In database 120, the generation rules used when generating the token information for each battery system 200 can be stored separately for each battery system 200.
[0095] The communication unit 130 is configured to communicate with the user terminal 300 and the identification module 400 via a network.
[0096] According to an embodiment, the communication unit 130 can receive unique numbers, sequence information, status information, component information, historical information query request signals, etc., from the user terminal 300. The communication unit 130 can transmit token information and historical information about a specific battery system 200 retrieved from the database 120 to the user terminal 300.
[0097] According to an embodiment, the communication unit 130 can receive a tampering check request signal for a specific battery system 200 from the user terminal 300, and can receive a first unique number, a first sequence information, and a first token information from the identification module 400. The communication unit 130 can transmit an information transmission request signal to the identification module 400, and can transmit the check result and historical information about whether the specific battery system 200 has been tampered with or forged to the user terminal 300.
[0098] Figure 3 This is a flowchart illustrating the process of creating and managing historical information in the battery history information management system.
[0099] Reference Figure 3 The process of generating token information through the battery history information management system 100 (S3110 to S3170), the process of generating history information by using information received from the user terminal 300 (S3210 to S3230), and the process of retrieving and transmitting history information according to the user's request (S3310 to S3340) are shown.
[0100] The battery system manufacturer can attach the safety sticker 210 to the manufactured battery system 200 and write serial information onto it (S3110). At this time, a unique number can be assigned to the safety sticker 210. The unique number is generated by the manufacturer of the safety sticker 210 and refers to the identification information assigned to the safety sticker 210. The serial information is generated by the battery system manufacturer and refers to the identification information assigned to the battery system 200.
[0101] Battery system manufacturers can input the unique number and serial information of a specific battery system 200 into the user terminal 300 (S3120).
[0102] The user terminal can transmit the unique number and sequence information of the specific battery system 200 received to the battery history information management system 100 (S3130). At this time, the battery system manufacturer can request token information generation from the battery history information management system 100 through the user terminal 300.
[0103] The battery history information management system 100 can generate token information for a specific battery system 200 by using a unique number and sequence information (S3140). For example, the battery history information management system 100 can generate token information by simply combining sequence information and a unique number.
[0104] The battery history information management system 100 can transmit the generated token information to the user terminal 300 (S3150). At this time, the battery history information management system 100 can store the generated token information for a specific battery system 200 together with the generation rules used to generate the token information in the historical information of the battery system 200.
[0105] User terminal 300 can provide token information of a specific battery system 200 to the battery system manufacturer (S3160).
[0106] The battery system manufacturer can record the provided token information in the corresponding battery system 200 (S3170).
[0107] The battery system 200 can generate status information and component information (S3210). The status information and component information can be generated continuously when the battery system 200 is manufactured, when the battery system 200 is sold and transported, and when the owner uses the battery system 200.
[0108] User terminal 300 can transmit the status information and component information of battery system 200 to battery history information management system 100 (S3220).
[0109] The battery history information management system 100 can generate and manage historical information for each battery system 200 by organizing and listing the status information and component information received from the user terminal 300 (S3230).
[0110] Users can enter a historical information query command for a specific battery system 200 that they own or use through the user terminal 300 (S3310).
[0111] User terminal 300 can generate a historical information query request signal corresponding to battery system 200 in response to the historical information query command input by the user, and transmit the signal to battery historical information management system 100 (S3320).
[0112] The battery history information management system 100 can retrieve the historical information of the corresponding battery system 200 from the database 120 in response to the historical information query request signal received from the user terminal 300 (S3330).
[0113] The battery history information management system 100 can transmit historical information retrieved from the database 120 to the user terminal 300 (S3340). At this time, the user terminal 300 can provide the user with the historical information received from the battery history information management system 100.
[0114] The battery history information management system 100 can update the history information by adding the retrieval details obtained by retrieving history information in the database 120 to the history information of the corresponding battery system 200 (S3350).
[0115] Figure 4 This is a flowchart explaining the process by which the battery history information management system 100 checks for tampering in the battery system 200 based on historical information stored in the database 120.
[0116] refer to Figure 4 This illustrates the process of checking for tampering with the battery system 200 in the battery history information management system 100 by using historical information stored in the database 120.
[0117] Users can input tampering check commands for a specific battery system 200 into user terminal 300 (S4100).
[0118] User terminal 300 can generate a tamper check request signal for the corresponding battery system 200 in response to a tamper check command received from the user, and transmit it to the battery history information management system 100 (S4200).
[0119] The battery history information management system 100 can generate an information transmission request signal in response to a tampering check request signal, requesting the transmission of a unique number, sequence information and token information assigned to the corresponding battery system 200, and transmit it to the identification module 400 (S4300).
[0120] The identification module 400 can obtain a unique number from the external security sticker 210 attached to the specific battery system 200 in response to an information transmission request signal, and obtain the sequence information and token information described in the specific battery system 200 (S4400). At this time, the unique number, sequence information and token information obtained by the identification module 400 are defined as the first unique number, the first sequence information and the first token information, respectively.
[0121] The identification module 400 can transmit the first unique number, first sequence information and first token information of a specific battery system 200 to the battery history information management system 100 (S4500).
[0122] The battery history information management system 100 can use the first unique number, the first sequence information and the first token information to check whether the battery system 200 has been tampered with or forged (S4600).
[0123] According to an embodiment, the battery history information management system 100 can check whether the battery system 200 has been tampered with or forged through the following process.
[0124] First, the battery history information management system 100 can retrieve information about the generation rules used when generating token information for a specific battery system 200 (S4610) from the historical information of the corresponding battery system 200 stored in the database 120, which is checked for tampering or forgery.
[0125] Next, the battery history information management system 100 can obtain the second unique number and the second sequence information from the first token information by applying the retrieved generation rules in reverse (S4620).
[0126] Next, the battery history information management system 100 can determine whether the battery system 200 has been tampered with or forged based on whether the first unique number and the second unique number are consistent and whether the first sequence information and the second sequence information are consistent (S4630).
[0127] The battery history information management system 100 can transmit the inspection results and historical information on whether the battery system 200 has been tampered with or forged to the user terminal 300 (S4700).
[0128] According to an embodiment, the owner or manufacturer of the battery system 200 who has received the inspection results for tampering through the user terminal 300 can replace the battery system 200 that has been determined to be tampered or counterfeited based on the inspection results with a normal battery system 200 (S4710).
[0129] The battery history information management system 100 can update the history information by adding the tampering inspection details and inspection results of a specific battery system 200 to the history information of the battery system 200 (S4800).
[0130] Figure 5 This is a flowchart of a battery history information management method according to an embodiment of the present invention.
[0131] refer to Figure 5 According to one embodiment of the present disclosure, the battery history information management method may include a tampering check request (S5100), a tampering check (S5200), and a check result transmission (S5300).
[0132] In the tamper check request (S5100), the controller 110 can receive a tamper check request signal for a specific battery system 200 from the user terminal 300. In response to the tamper check request signal, the controller 110 can generate an information transmission request signal requesting the transmission of a unique number, sequence information, and token information assigned to the specific battery system 200. The controller 110 can then transmit the information transmission request signal to the identification module 400.
[0133] In the tamper check (S5200), the controller 110 can receive a first unique number, a first sequence information, and a first token information for a specific battery system 200 from the identification module 400. The controller 110 can use the first unique number, the first sequence information, and the first token information to check whether the specific battery system 200 has been tampered with or counterfeited.
[0134] Figure 6 This is a flowchart of a tampering check according to an embodiment of the present invention.
[0135] The tampering inspection step (S5200) may include: retrieving information on the generation rules used when generating token information for the specific battery system 200 from the historical information of the specific battery system 200 stored in the database 120 (S5210); obtaining a second unique number and a second sequence information from the first token information by applying the retrieved generation rules in reverse (S5220); and determining whether the specific battery system has been tampered with or counterfeited based on whether the first unique number and the second unique number are consistent and whether the first sequence information and the second sequence information are consistent (S5230).
[0136] In the inspection result transmission (S5300), the controller 110 can transmit the inspection results and historical information on whether the battery system 200 has been tampered with or falsified to the user terminal 300. The controller 110 can update the historical information by adding the tampering inspection details and inspection results of a specific battery system 200 to the historical information of the battery system.
[0137] Figure 7 This is a flowchart of a battery history information management method according to an embodiment of the present invention.
[0138] refer to Figure 7 The battery history information management method may also include token information generation (S5400), history information generation (S5500) and / or history information provision (S5600).
[0139] In token information generation (S5400), the controller 110 can generate token information for a specific battery system 200 by using the unique number and sequence information of the specific battery system 200 received from the user terminal 300.
[0140] Figure 8 This is a flowchart of token information generation according to an embodiment of the present invention.
[0141] The token information generation (S5400) may include: the controller 110 determining whether to use the entire unique number or a part of the unique number to generate the token information based on the number of characters contained in the unique number (S5410); the controller determining whether to use the entire sequence information or a part of the sequence information to generate the token information based on the number of characters contained in the sequence information (S5420); and combining the unique number and the sequence information according to a preset generation rule to generate the token information (S5430).
[0142] In the historical information generation (S5500), the controller 110 can generate historical information for each battery system 200 by organizing and listing the status information and component information received from the user terminal 300.
[0143] According to an embodiment, historical information generation (S5500) may include additionally receiving status information and component information from user terminal 300 whenever status information and component information are generated in battery system 200, and adding the additionally received status information and component information to the historical information of the corresponding battery system 200 by controller 110 to update the historical information.
[0144] In the historical information provision (S5600), the controller 110 may, in response to a historical information query request signal for a specific battery system 200 received from the user terminal 300, retrieve historical information of the specific battery system 200 from the database 120 and provide the historical information.
[0145] Historical information provision (S5600) may include adding the retrieval details of historical information of a specific battery system 200 retrieved by the controller 110 from the database 120 to the historical information of the corresponding battery system 200 to update the historical information.
[0146] Furthermore, the above methods can be written as programs that can be executed on a computer, and can be implemented in a general-purpose digital computer that operates the program using a computer-readable recording medium. Computer-readable recording media can include storage media such as magnetic storage media such as ROM, RAM, USB, floppy disks, hard disks, or optically readable media such as CD-ROMs or DVDs.
[0147] The scope of this disclosure is indicated by the claims described below rather than the detailed description above, and all changes or modifications derived from the meaning and scope of the claims and their equivalents should be interpreted as being included within the scope of this invention.
Claims
1. A battery history information management system, the battery history information management system comprising: A database that stores historical information generated for each battery system by organizing the battery system's state information and component information; as well as A controller configured to generate token information by combining a unique number and sequence information of a specific battery system, retrieve historical information of the specific battery system from the database in response to a historical information query request signal received from a user terminal for the specific battery system, and provide the retrieved historical information of the specific battery system. In response to a request signal received from the user terminal for checking whether the specific battery system has been tampered with or forged, the controller generates an information transmission request signal for requesting the transmission of a unique number, sequence information and token information assigned to the specific battery system and transmits it to the identification module. The controller then uses the first unique number, first sequence information and first token information received from the identification module for the specific battery system to check whether the specific battery system has been tampered with or forged.
2. The battery history information management system according to claim 1, wherein, The controller determines whether to generate the token information using the entire unique number or a portion of the unique number based on the number of characters contained in the unique number.
3. The battery history information management system according to claim 1, wherein, The controller determines whether to generate the token information using all or only a portion of the sequence information based on the number of characters contained in the sequence information.
4. The battery history information management system according to claim 1, wherein, The controller generates the token information by combining the unique number and the sequence information according to a predetermined generation rule.
5. The battery history information management system according to claim 1, wherein, The controller adds the query details of the historical information of the specific battery system retrieved from the database to the historical information of the corresponding battery system to update the historical information.
6. The battery history information management system according to claim 1, wherein, The controller retrieves the generation rules used to generate the token information of the specific battery system from the historical information of the specific battery system stored in the database, applies the retrieved generation rules in reverse to obtain the second unique number and the second sequence information from the first token information, and determines whether the specific battery system has been tampered with or forged based on whether the first unique number and the second unique number are consistent and whether the first sequence information and the second sequence information are consistent.
7. The battery history information management system according to claim 6, wherein, If the first unique number and the second unique number are inconsistent, or if the first sequence information and the second sequence information are inconsistent, the controller determines that the specific battery system has been tampered with or forged.
8. The battery history information management system according to claim 1, wherein, The controller transmits the results of its checks on whether the specific battery system has been tampered with or falsified to the user terminal.
9. A method for managing battery history information through a battery history information management system, the method comprising: In response to a request signal received from the user terminal to check for tampering of a specific battery system, the controller generates an information transmission request signal requesting the transmission of a unique number, sequence information, and token information assigned to the specific battery system, and the controller transmits the information transmission request signal to the identification module. The controller checks whether the specific battery system has been tampered with or counterfeited by using the first unique number, first sequence information and first token information of the specific battery system received from the identification module; as well as The controller transmits the inspection results and historical information on whether the specific battery system has been tampered with or forged to the user terminal, and adds the inspection details and results on whether the specific battery system has been tampered with or forged to the historical information of the specific battery system to update the historical information.
10. The battery history information management method according to claim 9, wherein, Checking whether the specific battery system has been tampered with or counterfeited includes: Retrieve information about the generation rules used when generating token information for the specific battery system from historical information stored in the database for the specific battery system; The second unique number and second sequence information are obtained from the first token information by applying the generation rule in reverse; and The determination of whether the specific battery system has been tampered with or counterfeited is based on whether the first unique number and the second unique number are consistent, and whether the first sequence information and the second sequence information are consistent.
11. The battery history information management method according to claim 9, further comprising: The token information for the specific battery system is generated by utilizing the unique number and sequence information of the specific battery system received from the user terminal.
12. The battery history information management method according to claim 11, wherein, Generating the token information includes: The controller determines whether to use the entire unique number or a portion of the unique number to generate the token information based on the number of characters contained in the unique number. The token information is generated using either the entire sequence information or a portion of it, based on the number of characters contained in the sequence information; and The token information is generated by combining the unique number and the sequence information according to the preset generation rules.
13. The battery history information management method according to claim 9, further comprising: Historical information is generated by organizing and listing the status and component information received from the user terminal for each of the battery systems.
14. The battery history information management method according to claim 13, wherein, Generating the historical information includes: Each time the status information and component information are generated in the battery system, the status information and component information are additionally received from the user terminal, and the historical information is updated by adding the additionally received status information and component information to the historical information of the corresponding battery system.
15. The battery history information management method according to claim 9, further comprising: In response to a historical information query request signal for a specific battery system received from the user terminal, the controller retrieves the historical information of the specific battery system from the database and provides it.
16. The battery history information management method according to claim 15, wherein: Retrieving and providing historical information from the database includes: The query details of retrieving historical information of the specific battery system from the database are added to the historical information of the corresponding battery system to update the historical information.