Data management system and data management method

Abstract

According to some embodiments, a data management system comprises: a plurality of IoT sensors for measuring battery data from a plurality of battery modules and performing a reporting operation on the battery data according to a data reporting policy; and a management server for diagnosing states of the plurality of battery modules on the basis of the battery data, and adjusting the data reporting policy on the basis of the states of the plurality of battery modules and the results of the reporting operation.

Description

Data management system and data management method

[0001] Cross-citation with related applications

[0002] This application claims the benefit of priority from Republic of Korea Patent Application No. 10-2023-0171978, filed December 1, 2023, the entire contents of which are incorporated herein by reference.

[0003] Technology field

[0004] The embodiments disclosed in this document relate to a data management system and a data management method.

[0005] Recently, active research and development has been conducted on secondary batteries. The term "secondary battery" refers to a rechargeable battery, encompassing both conventional Ni / Cd and Ni / MH batteries, as well as recent lithium-ion batteries. Among secondary batteries, lithium-ion batteries can boast higher energy densities than conventional Ni / Cd and Ni / MH batteries. They can be manufactured in small and lightweight designs, making them highly versatile power sources 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] When manufacturing battery modules, IoT technology can be utilized to diagnose the condition of the cells within the module by measuring their voltage, temperature, and other factors. Sensors attached to the battery module can measure battery data and transmit it to a server via a wireless data network, which can then diagnose the module's condition based on the battery data. In this case, module diagnosis can be hindered by time differences between the sensor and server clocks, data report transmission failures, and other factors.

[0007] One purpose of the embodiments disclosed in this document is to provide a data management system and a data management method capable of adjusting data reporting policies for a plurality of sensors so that status diagnosis through sensors can be smoothly performed during the manufacturing process of a battery module.

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

[0009] According to some embodiments, a data management system includes a plurality of IoT sensors configured to measure battery data from a plurality of battery modules and perform a reporting operation on the battery data according to a data reporting policy; and a management server configured to diagnose the status of the plurality of battery modules based on the battery data and adjust the data reporting policy based on the status of the plurality of battery modules and the results of the reporting operation.

[0010] According to some embodiments, each IoT sensor of the plurality of IoT sensors is configured to measure open circuit voltage (OCV) values ​​from a plurality of battery cells of a corresponding battery module among the plurality of battery modules, and the management server is configured to diagnose whether a low voltage abnormality occurs in the plurality of battery cells based on the OCV values.

[0011] According to some embodiments, the data reporting policy includes a synchronization policy regarding a reporting time of the reporting task, and the management server is configured to modify the synchronization policy based on a difference between an actual reporting time and a reference reporting time of each IoT sensor of the plurality of IoT sensors.

[0012] According to some embodiments, the reference reporting time is a time at which the diagnosis of the low voltage or higher is performed in the current cycle, the management server is configured to transmit a negative response to the first IoT sensor among the plurality of IoT sensors when the actual reporting time of the first IoT sensor is earlier than the reference reporting time, and the first IoT sensor is configured to retransmit the OCV values ​​in the next cycle based on the negative response.

[0013] According to some embodiments, the management server is configured to diagnose low voltage abnormalities of the battery module corresponding to the OCV values ​​retransmitted in the next cycle due to the negative response with greater priority than low voltage abnormalities of other battery modules.

[0014] According to some embodiments, the data reporting policy includes a retransmission policy for data transmission failure of the reporting task, the plurality of IoT sensors are configured to attempt to retransmit the battery data according to the retransmission policy if the reporting task is unsuccessful, and the management server is configured to modify the retransmission policy based on the number of retransmission attempts of the plurality of IoT sensors.

[0015] According to some embodiments, the management server is configured to determine an error count of each of the plurality of IoT sensors based on the execution status of the reporting task, and to generate a defect list for the plurality of IoT sensors based on the error count.

[0016] According to some embodiments, each IoT sensor of the plurality of IoT sensors is configured to be attached to a corresponding battery module among the plurality of battery modules and to operate on power provided from the corresponding battery module, and the management server is configured to provide the defective list to a worker terminal of a worker who manages status diagnosis of the plurality of battery modules.

[0017] According to some embodiments, a data management method includes: measuring battery data from a plurality of battery modules through a plurality of IoT sensors; performing a reporting task on the battery data through the plurality of IoT sensors according to a data reporting policy; diagnosing a status of the plurality of battery modules based on the battery data through a management server; and adjusting the data reporting policy based on the status of the plurality of battery modules and a result of the reporting task through the management server.

[0018] According to some embodiments, the step of measuring the battery data includes a step of measuring open circuit voltage (OCV) values ​​from a plurality of battery cells of a corresponding battery module among the plurality of battery modules through each IoT sensor of the plurality of IoT sensors, and the step of diagnosing the status of the plurality of battery modules includes a step of diagnosing, through the management server, whether a low voltage abnormality occurs in the plurality of battery cells based on the OCV values.

[0019] According to some embodiments, the data reporting policy includes a synchronization policy regarding a reporting time of the reporting task, and the step of adjusting the data reporting policy includes a step of modifying the synchronization policy based on a difference between an actual reporting time and a reference reporting time of each IoT sensor of the plurality of IoT sensors through the management server.

[0020] According to some embodiments, the reference reporting time is a time at which the diagnosis of the low voltage or higher is performed in the current cycle, and the step of modifying the synchronization policy includes the step of transmitting a negative response to a first IoT sensor among the plurality of IoT sensors through the management server when the actual reporting time of the first IoT sensor is earlier than the reference reporting time; and the step of retransmitting the OCV values ​​in the next cycle based on the negative response through the first IoT sensor.

[0021] According to some embodiments, the data management method further includes a step of diagnosing a low voltage abnormality of a battery module corresponding to the OCV values ​​retransmitted in the next cycle due to the negative response through the management server with greater priority than low voltage abnormalities of other battery modules.

[0022] According to some embodiments, the data reporting policy includes a retransmission policy for data transmission failure of the reporting task, and the step of modifying the synchronization policy includes the step of attempting to retransmit the battery data according to the retransmission policy when the reporting task is not successful through the plurality of IoT sensors; and the step of modifying the retransmission policy based on the number of retransmission attempts of the plurality of IoT sensors through the management server.

[0023] According to some embodiments, the data management method further includes: determining an error count of each of the plurality of IoT sensors based on the performance status of the reporting task through the management server; and generating a defect list for the plurality of IoT sensors based on the error count through the management server.

[0024] According to some embodiments, each IoT sensor of the plurality of IoT sensors is attached to a corresponding battery module among the plurality of battery modules and configured to operate on power provided from the corresponding battery module, and the defective list is provided to a worker terminal of a worker who manages status diagnosis of the plurality of battery modules.

[0025] According to the embodiments disclosed in this document, a data management system and a data management method capable of adjusting data reporting policies for a plurality of sensors can be provided so that status diagnosis through sensors can be smoothly performed during the manufacturing process of a battery module.

[0026] The technical effects according to the embodiments disclosed in this document are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art according to the disclosure of this document.

[0027] FIG. 1 may illustrate a process by which a data management system according to some embodiments operates.

[0028] FIG. 2 may illustrate a structure for diagnosing the status of multiple battery modules according to some embodiments.

[0029] FIG. 3 may illustrate elements that constitute a data management system according to some embodiments.

[0030] FIG. 4 may illustrate specific types of data reporting policies according to some embodiments.

[0031] FIG. 5 may illustrate how an IoT sensor operates according to a synchronization policy and a retransmission policy according to some embodiments.

[0032] FIG. 6 may illustrate steps that constitute a data management method according to some embodiments.

[0033] Hereinafter, embodiments described in this document are described with reference to the attached drawings. However, this is not intended to limit the disclosure of this document to specific embodiments, and it should be understood that various modifications, equivalents, and / or alternatives of the embodiments described in this document are included.

[0034] The embodiments and terminology used in this document are not intended to limit the technical features described in this document to a specific embodiment, but should be understood to encompass various modifications, equivalents, or alternatives of the embodiment. In connection with the description of the drawings, similar reference numerals may be used to refer to similar or related components. The singular form of a noun corresponding to an item may include one or more of the item, unless the context clearly indicates otherwise.

[0035] In this document, 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" can each include any one of the items listed together in that phrase, or all possible combinations thereof. Terms such as "first", "second", "first", "second", "A", "B", "(a)", or "(b)" may be used merely to distinguish the corresponding component from other corresponding components, and do not limit the corresponding components in any other respect (e.g., importance or order) unless specifically stated otherwise.

[0036] 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 “coupled” or “connected,” it means that the component can be connected to the other component directly (e.g., wired or wirelessly), or indirectly (e.g., via a third component).

[0037] The methods according to various embodiments disclosed in this document may be provided as a computer program product. The computer program product may be traded as a commodity 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 driver 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 a relay server.

[0038] According to the embodiments disclosed in this document, each component (e.g., a module or a program) of the above-described components may include one or more entities, and some of the entities may be separated and placed in other components. According to the embodiments disclosed in this document, 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 this 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 the integration. According to the embodiments disclosed in this document, 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.

[0039] FIG. 1 may illustrate a process by which a data management system according to some embodiments operates.

[0040] Referring to FIG. 1, the data management system (200) can collect battery data from a plurality of battery modules (100), and can perform status diagnosis for the plurality of battery modules (100) and policy adjustment for reporting of battery data based on the battery data.

[0041] The data management system (200) may include a system for managing the transmission / reception and / or reporting procedures of data required to diagnose the status of a plurality of battery modules (100) during the manufacturing process of the plurality of battery modules (100). The data management system (200) may collect battery data regarding a plurality of battery modules (100) based on a data reporting policy, and may modify the data reporting policy according to the collection status of the battery data.

[0042] FIG. 2 may illustrate a structure for diagnosing the status of multiple battery modules according to some embodiments.

[0043] Referring to FIG. 2, a structure (10) for diagnosing the status of a plurality of battery modules may include a plurality of battery modules (110, 120, 130, ...), a plurality of IoT sensors (211, 212, 213, ...), a management server (220), an AP (20), a worker terminal (30), and an MES (40).

[0044] Various Internet of Things (IoT) technologies can be utilized to implement smart factories. During the manufacturing process of multiple battery modules (100), multiple IoT sensors (210) can be utilized for status diagnosis. Each IoT sensor can have its own processing capabilities and periodically collect battery cell voltage, temperature, state of charge (SOC), state of health (SOH), etc., and provide these data to a management server (220).

[0045] A plurality of IoT sensors (210) can communicate with a management server (220) via wireless communication through an access point (AP) 20. The management server (220) and a manufacturing execution system (MES) 40 can determine whether a plurality of battery modules (100) are defective based on battery data collected through the plurality of IoT sensors (210). However, if the data collection process is not performed smoothly, the efficiency and accuracy of the defect determination may be reduced. For example, problems in data reporting may occur due to loss of communication packets, poor time synchronization between the sensor and the server, and limitations of sensors that do not allow two-way communication. To resolve this, the data management system (200) can adjust the data reporting policy.

[0046] The management server (220) can integrate data provided from multiple IoT sensors (210). The management server (220) can transmit the integrated data to the MES (40). The MES (40) can perform various management functions related to the production of multiple battery modules (100). For this purpose, data monitoring, tracking, control, etc. can be performed. The AP (20) can provide a wired / wireless communication network between the multiple IoT sensors (210), the management server (220), and the worker terminal (30). For example, the AP (20) can be implemented in the form of WLAN, WiFi, etc.

[0047] The worker terminal (30) may be a worker terminal that manages a status diagnosis process in a production line of a plurality of battery modules (100). The data management system (200) may select a defective sensor among a plurality of IoT sensors (210) based on the data reporting status of the plurality of battery modules (100) and provide the selected defective sensor to the worker terminal (30). The worker may identify a defective sensor through the worker terminal (30) and replace it with another sensor.

[0048] A plurality of IoT sensors (210) may be attached to a plurality of battery modules (100). Each IoT sensor may periodically measure data such as voltage, current, and temperature from a corresponding battery module, and may derive battery data such as open circuit voltage (OCV), state of charge (SOC), and state of health (SOH). The plurality of IoT sensors (210) may operate based on power provided from the plurality of battery modules (100). To reduce power loss, the plurality of IoT sensors (210) may periodically wake up to perform data reporting tasks and then enter a sleep state again.

[0049] FIG. 3 may illustrate elements that constitute a data management system according to some embodiments.

[0050] Referring to FIG. 3, the data management system (200) may include a plurality of IoT sensors (210) and a management server (220). However, the present invention is not limited thereto, and some configurations may be omitted from the data management system (200) or other general-purpose configurations may be further included in the data management system (200).

[0051] A plurality of IoT sensors (210) may include a communication module for communicating with a management server (220) via an AP (20), a processing module for checking a data reporting policy and applying the same to perform a data collection operation, etc. Since the plurality of IoT sensors (210) perform a reporting operation using power from the plurality of battery modules (100) and then enter a sleep state again, they can perform one-way communication in a relationship with the management server (220).

[0052] The management server (220) may include memory and a processor. The processor of the management server (220) may be implemented in the form of at least one of a microprocessor, a CPU, a GPU, and an AP. The memory of the management server (220) may be implemented as a non-volatile device such as a ROM, a PROM, an EPROM, an EEPROM, a flash memory, a PRAM, an MRAM, an RRAM, an FRAM, or the like, or a volatile device such as a DRAM, an SRAM, an SDRAM, a PRAM, or the like, and may be implemented in the form of an HDD, an SSD, an SD, a Micro-SD, or the like, or a combination thereof. The processor may execute various data, commands, software, mobile applications, computer programs, etc. stored in the memory to process necessary operations.

[0053] A plurality of IoT sensors (210) may be configured to measure battery data from a plurality of battery modules (100). Each IoT sensor may measure voltage, current, temperature, etc. from a plurality of battery cells of a corresponding battery module, and based on these, estimate a state of charge (SOC), state of health (SOH), etc. The battery data may include open circuit voltage (OCV) data.

[0054] A plurality of IoT sensors (210) may be configured to perform reporting tasks on battery data according to a data reporting policy. The data reporting policy may include rules, recommendations, restrictions, etc. to be followed for reporting battery data regarding a plurality of battery modules (100) to a management server (220). The data reporting policy may be changed according to the operating status of the plurality of IoT sensors (210). The plurality of IoT sensors (210) may query the current status of the data reporting policy to report battery data.

[0055] The management server (220) may be configured to diagnose the status of a plurality of battery modules (100) based on battery data. For example, the status of each battery module may be diagnosed based on the OCV values ​​of the plurality of battery cells of the respective battery module. An OCV deviation value may be calculated based on the difference between each OCV value and the OCV average value, and a defect such as a low voltage of each battery module may be diagnosed through various processing processes for the OCV deviation values. According to an embodiment, instead of the management server (220), the MES (40) may be configured to diagnose the status of the plurality of battery modules (100).

[0056] The management server (220) may be configured to adjust a data reporting policy based on the status of the plurality of battery modules (100) and the results of the reporting task. The result of the reporting task may be determined based on whether the battery data provided by the plurality of IoT sensors (210) is smoothly received by the management server (220). If the result of the reporting task is not satisfactory, the data reporting policy may be adjusted to resolve the issue. Meanwhile, if the status of the plurality of battery modules (100) is poor, the data reporting policy may be modified to be more stringent to more thoroughly perform a fault diagnosis.

[0057] According to an embodiment, each IoT sensor of the plurality of IoT sensors (210) may be configured to measure open circuit voltage (OCV) values ​​from a plurality of battery cells of a corresponding battery module among the plurality of battery modules (100), and the management server (220) may be configured to diagnose whether a low voltage abnormality occurs in the plurality of battery cells based on the OCV values. For example, a low voltage abnormality may be determined based on deviation values ​​of the OCV values ​​from an average value in each battery module. Meanwhile, other types of battery data may be utilized in addition to the OCV value, and other indicators such as lithium deposition or increased internal resistance may be analyzed in addition to the low voltage abnormality.

[0058] According to an embodiment, the data reporting policy may include a synchronization policy regarding the reporting time of the reporting task, and the management server (220) may be configured to modify the synchronization policy based on the difference between the actual reporting time and the reference reporting time of each IoT sensor of the plurality of IoT sensors (210). As the plurality of IoT sensors (210) operate, time differences may occur for each sensor, and if such differences accumulate, the deviation in reporting times for each sensor may increase from the perspective of the management server (220). If the deviation in reporting times for each sensor increases, the performance for diagnosing faults such as low voltage abnormalities may deteriorate. In order to reduce such reporting time deviation, the plurality of IoT sensors (210) may be synchronized with each other by modifying the synchronization policy.

[0059] In an embodiment, the reference reporting time may be the time at which a low voltage or higher diagnosis is performed in the current cycle, and the management server (220) may be configured to transmit a negative response to the first IoT sensor among the plurality of IoT sensors (210) if the actual reporting time of the first IoT sensor is earlier than the reference reporting time, and the first IoT sensor may be configured to retransmit OCV values ​​in the next cycle based on the negative response. If data of the first IoT sensor is additionally reported at the time of the low voltage diagnosis, diagnostic data for each cycle may be mixed. To prevent this, a negative response may be provided to the IoT sensor if an actual report is made before the reference reporting time. An IoT sensor that receives a negative response may re-report the data that was reported earlier. In an embodiment, the negative response may be configured to be provided if the actual reporting time is later than the reference reporting time.

[0060] According to an embodiment, the management server (220) may be configured to diagnose low voltage abnormalities of a battery module corresponding to OCV values ​​retransmitted in the next cycle due to a negative response with higher priority than low voltage abnormalities of other battery modules. When the number of battery modules (100) is 10, low voltage diagnostics may be performed 10 times, and the diagnostics for the module reported first may be performed first. However, if there is a retransmission for a negative response, the diagnostics for the retransmitting module may be performed before the other modules. In this manner, the diagnostic procedure may proceed in a normal order again from the next cycle.

[0061] In an embodiment, the data reporting policy may include a retransmission policy for data transmission failure of a reporting task, and the plurality of IoT sensors (210) may be configured to attempt retransmission of battery data according to the retransmission policy if the reporting task is not successful, and the management server (220) may be configured to modify the retransmission policy based on the number of retransmission attempts of the plurality of IoT sensors (210). For example, the retransmission policy may define a maximum number of retransmission attempts as 12, 24, or some other value, and each IoT sensor may attempt retransmission of battery data within the range of the maximum number of attempts. If each IoT sensor successfully retransmits before reaching the maximum number of attempts, it may not attempt retransmission for the remaining attempts. Alternatively, each IoT sensor may attempt retransmission up to the maximum number of attempts of the retransmission policy, regardless of whether the retransmission is successful before reaching the maximum number of attempts. Meanwhile, the maximum number of retransmission attempts may be modified based on the number of retransmission attempts made by multiple IoT sensors (210). For example, if three IoT sensors (211, 212, and 213) have attempted retransmission 0, 2, and 6 times, respectively, the retransmission policy may be adjusted based on the values ​​0, 2, and 6.

[0062] According to an embodiment, the management server (220) may be configured to determine an error count of each of a plurality of IoT sensors (210) based on the execution status of a reporting task, and to generate a defect list for the plurality of IoT sensors (210) based on the error count. The error count may start from 0 and increase by 1, 2, or another value whenever there is a reason for increase. According to an embodiment, the reasons for increase of the error count may include a sensor component error, a sensor reset, a connection failure with the AP (20), OCV measurement NG, a change in the order of a state machine, a change in the order of a communication protocol, a retransmission due to a failure in report time synchronization, maintenance of a sleep state due to a failure of a periodic wake-up, etc. Meanwhile, the error count may decrease if no reason for increase occurs during a specific cycle. If the accumulated value of the error count exceeds a threshold, the IoT sensor may be registered in a blacklist, and the worker may check the IoT sensor registered in the blacklist through the worker terminal (30).

[0063] According to an embodiment, each IoT sensor of the plurality of IoT sensors (210) may be configured to be attached to a corresponding battery module among the plurality of battery modules (100) and to operate with power provided from the corresponding battery module, and the management server (220) may be configured to provide a list of defective items to a worker terminal (30) of a worker who manages status diagnosis of the plurality of battery modules (100). The plurality of IoT sensors (210) may not have their own power source, but may operate with power from the plurality of battery modules (100). Accordingly, the plurality of IoT sensors (210) may periodically wake up for data collection and reporting, and enter a sleep state again after completing the operation. Since the plurality of IoT sensors (210) re-enter a sleep state for power efficiency, communication between the plurality of IoT sensors (210) and the management server (220) may be interpreted as one-way communication rather than two-way communication. Meanwhile, the worker can check the blacklist (defective list) through the worker terminal (30) and replace the IoT sensor determined to be defective.

[0064] FIG. 4 may illustrate specific types of data reporting policies according to some embodiments.

[0065] Referring to FIG. 4, the data reporting policy (400) may include a synchronization policy (410), a retransmission policy (420), and a blacklist policy (430). In addition, other policies may be additionally defined to facilitate the smooth collection of battery data required for status diagnosis of multiple battery modules (100).

[0066] In the case of the synchronization policy (410), multiple IoT sensors (210) can report battery data to the management server (220), and the management server (220) can perform OCV low voltage judgment at a specific time or transmit data required for OCV low voltage judgment to the MES (40). In general, the time of multiple IoT sensors (210) may differ by several minutes per day. In the case of a discharge process that takes a relatively long time, the accumulation of time differences may affect the low voltage judgment algorithm. In this regard, instead of performing time synchronization for multiple IoT sensors (210) each time, a method of granting additional correction time to the reporting time of each IoT sensor can be utilized. That is, the synchronization policy (410) may include a policy for correcting the reporting time of each IoT sensor.

[0067] For example, if the reporting time of a specific IoT sensor (Si) is inappropriate, the value of the reporting time can be stored as quick_report_time. The difference between quick_report_time and the reference reporting time, ocv_time, can be stored as ocv_time_diff. When the additional correction time for the sensor (Si) is x, the maximum value of x can be designated as ocv_plus_time. ocv_plus_time can be calculated as follows.

[0068] [Formula 1]

[0069]

[0070] In Equation 1, N_negative_response may be the number of sensors that received negative responses among the plurality of IoT sensors (210). sum(ocv_time_diff) may be the sum total of ocv_time_diff for the plurality of IoT sensors (210). max(ocv_time_diff) may be the maximum value of ocv_time_diff for the plurality of IoT sensors (210). When ocv_plus_time is calculated in this way, the reporting time of the sensor (Si) may be adjusted by ocv_plus_time.

[0071] The retransmission policy (420) can cause multiple IoT sensors (210) to retransmit data reports a set number of times when a negative response is received or when the battery data reporting task is unsuccessful. Since communication with the management server (220) is unidirectional except for negative responses, the retransmission policy (420) can be implemented. For example, the number of retransmission attempts (retry_count) according to the retransmission policy (420) can be set to 12 or more and 24 or less in the following manner.

[0072] [Formula 2]

[0073]

[0074] In Equation 2, the upper limit 24 and the lower limit 12 can be changed to other values ​​as needed. The maximum value of the number of retransmissions max_retransmission can be the maximum value of the number of retransmissions in the plurality of IoT sensors (210), and the minimum value of the number of retransmissions min_retransmission can be the minimum value of the number of retransmissions in the plurality of IoT sensors (210). For example, when the numbers of retransmissions of three IoT sensors (211, 212, 213) are 0, 18, and 6, respectively, the number of retransmission attempts retry_count according to the retransmission policy (420) can be set to min(24, 21) = 21.

[0075] FIG. 5 may illustrate how an IoT sensor operates according to a synchronization policy and a retransmission policy according to some embodiments.

[0076] Referring to FIG. 5, a graph (500) illustrating how an IoT sensor operates according to a synchronization policy and a retransmission policy may be illustrated.

[0077] In the graph (500), the reporting time of the third IoT sensor (213) may be earlier than the reference reporting time of the management server (220). In response, the management server (220) may provide a negative response to the third IoT sensor (213) in the current cycle. In response to the negative response, the third IoT sensor (213) may re-report the data reported in the current cycle in the next cycle.

[0078] Depending on the synchronization policy, the reporting time of the third IoT sensor (213) may be adjusted. For example, in the same manner as Equation 1 described above, an additional delay time may be applied to the reporting time of the third IoT sensor (213), and accordingly, from the next cycle onwards, the reporting time of the third IoT sensor (213) may be later than the standard reporting time of the management server (220).

[0079] FIG. 6 may illustrate steps that constitute a data management method according to some embodiments.

[0080] Referring to FIG. 6, the data management method (600) may include steps (610) to (640). However, the present invention is not limited thereto, and some steps may be omitted or other general steps may be added, and the steps of the data management method (600) may be executed in a different order than the illustrated order.

[0081] The data management method (600) may be composed of steps that are processed in a time-series manner in the data management system (200). Therefore, even if the content is omitted below, the content described above for the data management system (200) may be equally applied to the data management method (600).

[0082] Steps (610) to (640) of the data management method (600) can be performed by a plurality of IoT sensors (210) and a management server (220) of the data management system (200).

[0083] In step (610), the data management system (200) can measure battery data from multiple battery modules through multiple IoT sensors.

[0084] In step (620), the data management system (200) can perform a reporting task on battery data according to a data reporting policy through a plurality of IoT sensors.

[0085] In step (630), the data management system (200) can diagnose the status of multiple battery modules based on battery data through the management server.

[0086] In step (640), the data management system (200) can adjust the data reporting policy based on the status of multiple battery modules and the results of the reporting task through the management server.

[0087] According to an embodiment, the data management method (600) may be implemented in the form of a computer program stored on a computer-readable storage medium. That is, the computer program may include instructions for implementing the data management method (600), and the program instructions may be stored on the computer-readable storage medium. The computer program may include a mobile application.

[0088] According to an embodiment, the computer-readable storage medium may include magnetic media such as hard disks, floppy disks, and magnetic tapes, optical media such as CD-ROMs, DVDs, magneto-optical media such as floptical disks, and hardware devices specially configured to store and execute computer program instructions such as ROMs, RAMs, flash memories, and the like. The computer program instructions may include machine language codes generated by a compiler and high-level language codes that can be executed by a computer using an interpreter, etc.

[0089] The terms "include," "comprise," or "have" used herein, unless otherwise specifically stated, imply that the corresponding component may be included, and therefore should be interpreted to include other components rather than to exclude 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 pertain, unless otherwise defined. Commonly used terms, such as terms defined in dictionaries, should be interpreted to be consistent with their contextual meaning in the relevant art, and shall not be interpreted in an idealized or overly formal sense, unless explicitly defined in this document.

[0090] The above description is merely an illustrative description of the technical idea disclosed in this document, and those skilled in the art to which the embodiments disclosed in this document pertain may make various modifications and variations without departing from the essential characteristics of the embodiments disclosed in this document. Therefore, the embodiments disclosed in this document are not intended to limit the technical idea of ​​the embodiments disclosed in this document, but to explain it, and the scope of the technical idea disclosed in this document is not limited by these embodiments. The protection scope of the technical idea disclosed in this document should be interpreted by the claims below, and all technical ideas within a scope equivalent thereto should be interpreted as being included in the scope of rights of this document.

[0091] [Explanation of symbols]

[0092] 100: Multiple battery modules 200: Data management system

[0093] 210: Multiple IoT sensors 220: Management server

[0094] 600: Data Management Methods

Claims

1. A plurality of IoT sensors configured to measure battery data from a plurality of battery modules and perform a reporting task on the battery data according to a data reporting policy; and A data management system comprising a management server configured to diagnose the status of the plurality of battery modules based on the battery data, and adjust the data reporting policy based on the status of the plurality of battery modules and the results of the reporting task.

2. In paragraph 1, Each IoT sensor of the plurality of IoT sensors is configured to measure open circuit voltage (OCV) values ​​from a plurality of battery cells of a corresponding battery module among the plurality of battery modules, A data management system, wherein the management server is configured to diagnose whether a low voltage abnormality occurs in the plurality of battery cells based on the OCV values.

3. In paragraph 2, The above data reporting policy includes a synchronization policy regarding the reporting time of the above reporting task, A data management system, wherein the management server is configured to modify the synchronization policy based on the difference between the actual reporting time and the reference reporting time of each IoT sensor among the plurality of IoT sensors.

4. In paragraph 3, The above standard reporting time is the time at which the above low voltage or higher diagnosis is performed in the current cycle. The above management server is configured to transmit a negative response to the first IoT sensor when the actual reporting time of the first IoT sensor among the plurality of IoT sensors is earlier than the reference reporting time. A data management system wherein the first IoT sensor is configured to retransmit the OCV values ​​in the next cycle based on the negative response.

5. In paragraph 4, A data management system, wherein the management server is configured to diagnose low voltage abnormalities of a battery module corresponding to the OCV values ​​retransmitted in the next cycle due to the negative response with greater priority than low voltage abnormalities of other battery modules.

6. In paragraph 1, The above data reporting policy includes a retransmission policy for data transmission failure of the above reporting task, The above plurality of IoT sensors are configured to attempt to retransmit the battery data according to the retransmission policy if the above reporting task is not successful. A data management system, wherein the management server is configured to modify the retransmission policy based on the number of retransmission attempts of the plurality of IoT sensors.

7. In paragraph 1, The above management server determines the error count of each of the plurality of IoT sensors based on the performance status of the above reporting task, A data management system configured to generate a bad list for the plurality of IoT sensors based on the above error count.

8. In paragraph 7, Each IoT sensor of the plurality of IoT sensors is attached to a corresponding battery module among the plurality of battery modules and is configured to operate on power provided from the corresponding battery module. A data management system, wherein the management server is configured to provide the defective list to a worker terminal of a worker who manages status diagnosis of the plurality of battery modules.

9. A step of measuring battery data from multiple battery modules through multiple IoT sensors; A step of performing a reporting task on the battery data according to a data reporting policy through the plurality of IoT sensors; A step of diagnosing the status of the plurality of battery modules based on the battery data through the management server; and A data management method, comprising a step of adjusting the data reporting policy based on the status of the plurality of battery modules and the results of the reporting task through the management server.

10. In paragraph 9, The step of measuring the battery data includes a step of measuring open circuit voltage (OCV) values ​​from a plurality of battery cells of a corresponding battery module among the plurality of battery modules through each IoT sensor of the plurality of IoT sensors, A data management method, wherein the step of diagnosing the status of the plurality of battery modules includes a step of diagnosing whether a low voltage abnormality occurs in the plurality of battery cells based on the OCV values ​​through the management server.

11. In paragraph 10, The above data reporting policy includes a synchronization policy regarding the reporting time of the above reporting task, A data management method, wherein the step of adjusting the data reporting policy includes a step of modifying the synchronization policy based on a difference between an actual reporting time and a reference reporting time of each IoT sensor among the plurality of IoT sensors through the management server.

12. In paragraph 11, The above standard reporting time is the time at which the above low voltage or higher diagnosis is performed in the current cycle. The steps to modify the above synchronization policy are: A step of transmitting a negative response to the first IoT sensor when the actual reporting time of the first IoT sensor among the plurality of IoT sensors is earlier than the reference reporting time through the management server; and A data management method comprising the step of retransmitting the OCV values ​​in the next cycle based on the negative response through the first IoT sensor.

13. In paragraph 12, A data management method further comprising a step of diagnosing a low voltage abnormality of a battery module corresponding to the OCV values ​​retransmitted in the next cycle due to the negative response through the management server with greater priority than low voltage abnormalities of other battery modules.

14. In paragraph 9, The above data reporting policy includes a retransmission policy for data transmission failure of the above reporting task, The steps to modify the above synchronization policy are: A step of attempting to retransmit the battery data according to the retransmission policy when the reporting task is not successful through the plurality of IoT sensors; and A data management method, comprising a step of modifying the retransmission policy based on the number of retransmission attempts of the plurality of IoT sensors through the management server.

15. In paragraph 9, A step of determining an error count of each of the plurality of IoT sensors based on the performance status of the reporting task through the management server; and A data management method further comprising the step of generating a fault list for the plurality of IoT sensors based on the error count through the management server.

16. In paragraph 15, Each IoT sensor of the plurality of IoT sensors is attached to a corresponding battery module among the plurality of battery modules and is configured to operate on power provided from the corresponding battery module. A data management method in which the above defective list is provided to a worker terminal of a worker who manages status diagnosis of the above plurality of battery modules.

Images