Data management device and operation method thereof

Abstract

A data management device according to an embodiment disclosed in the present document may include: a data acquisition unit for acquiring battery data including shadow battery data from a vehicle; a storage unit including a plurality of partitions and storing the battery data; and a controller for storing the battery data in each of the plurality of partitions on the basis of a generation time at which the battery data is generated in the vehicle, generating temporary battery data including the shadow battery data and battery data corresponding to the generation time of the shadow battery data among the battery data stored in the storage unit, and dividing the temporary battery data to re-store the divided temporary battery data in a partition corresponding to the generation time among the multiple partitions.

Description

Data management device and its operating method

[0001] Cross-citation with related applications

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

[0003] Technology field

[0004] Various embodiments disclosed in this document relate to a data management device and a method of operating the same.

[0005] Research and development on secondary batteries has been actively conducted recently. Secondary batteries are rechargeable and dischargeable, and can include both conventional Ni / Cd and Ni / MH batteries, as well as more recent lithium-ion batteries. Lithium-ion batteries have the advantage of a much higher energy density than conventional Ni / Cd and Ni / MH batteries. Furthermore, lithium-ion batteries can be manufactured in a compact and lightweight form, making them ideal 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] A separate data management device may be used to analyze battery data. This data management device may collect battery data regarding the condition of the battery from a battery management device connected to the battery or battery pack containing the battery. Additionally, the data management device may collect battery data from a server.

[0007] As the amount of battery data collected increases, the importance of managing battery data increases, and the costs of managing battery data can increase. Therefore, the need to manage collected data to reduce management costs and ensure efficient management is emerging.

[0008] One object of various embodiments of the present invention is to provide a data management device for managing data stored in a database and an operating method thereof.

[0009] One object of various embodiments of the present invention is to provide a data management device and its operating method based on an algorithm for preventing distribution distortion of data stored in a database.

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

[0011] A data management device according to an embodiment disclosed in the present document may include a data acquisition unit that acquires battery data including shadow battery data from a vehicle; a storage unit that includes a plurality of partitions and stores the battery data; and a controller that stores the battery data in each of the plurality of partitions based on a generation time when the battery data is generated in the vehicle, generates battery data corresponding to the generation time of the shadow battery data among the battery data stored in the storage unit, and generates temporary battery data including the shadow battery data, and divides the temporary battery data and re-stores it in a partition corresponding to the generation time among the plurality of partitions.

[0012] According to an embodiment, the shaded battery data may be generated at the same time as the battery data stored in the storage unit and may be battery data acquired by the data acquisition unit after the stored battery data is stored in the storage unit.

[0013] According to an embodiment, the controller may store the battery data by dividing it into equal-sized portions in each of the plurality of partitions.

[0014] According to an embodiment, the controller may divide the battery data based on the number of computing nodes of the data management device.

[0015] According to an embodiment, the controller may store the temporary battery data in a buffer, and before re-storing the temporary battery data in the storage, delete the battery data corresponding to the generation time of the shaded battery data stored in the storage.

[0016] According to an embodiment, the controller may divide the temporary battery data into partitions of equal size and re-store them in a partition corresponding to the generation time.

[0017] According to an embodiment, the controller may divide the temporary battery data based on the number of computing nodes of the data management device.

[0018] According to an embodiment, the controller may divide the temporary battery data in chronological order.

[0019] A data management method according to an embodiment disclosed in the present document may include the steps of: obtaining battery data including shadow battery data from a vehicle; storing the battery data in each of the plurality of partitions based on a generation time when the battery data was generated in the vehicle in a storage unit including a plurality of partitions; generating battery data corresponding to the generation time of the shadow battery data and temporary battery data including the shadow battery data among the battery data stored in the storage unit; and dividing the temporary battery data and re-storing it in a partition corresponding to the generation time among the plurality of partitions.

[0020] According to an embodiment, the shaded battery data may be generated at the same time as the battery data stored in the storage unit and may be battery data acquired after the stored battery data is stored in the storage unit.

[0021] According to an embodiment, the step of storing the battery data in each of the plurality of partitions may include storing the battery data by dividing it into equal sizes in each of the plurality of partitions.

[0022] According to an embodiment, the battery data can be divided based on the number of computing nodes of the data management method.

[0023] According to an embodiment, the method may further include a step of storing the temporary battery data in a buffer; and a step of deleting battery data corresponding to the generation time of the shaded battery data stored in the storage unit before re-storing the temporary battery data in the storage unit.

[0024] According to an embodiment, the step of restoring the temporary battery data may divide the temporary battery data into equal-sized pieces and restoring them in a partition corresponding to the generation time.

[0025] According to an embodiment, the temporary battery data can be divided based on the number of computing nodes of the data management method.

[0026] According to an embodiment, the step of restoring the temporary battery data may include the step of dividing the temporary battery data in chronological order.

[0027] A data management device and its operating method according to an embodiment disclosed in this document can manage data stored in a database.

[0028] A data management device and its operating method according to an embodiment disclosed in this document may be based on an algorithm for preventing distribution distortion of data stored in a database.

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

[0030] FIG. 1 is a diagram showing a data management system according to one embodiment disclosed in this document.

[0031] FIG. 2 is a block diagram illustrating the configuration of a data management device according to one embodiment disclosed in this document.

[0032] FIG. 3 is a diagram showing data stored in a data management device according to one embodiment disclosed in this document.

[0033] FIG. 4 is a diagram showing data stored in a data management device according to one embodiment disclosed in this document.

[0034] FIG. 5 is a diagram showing data stored in a data management device according to one embodiment disclosed in this document.

[0035] FIG. 6 is a diagram showing a buffer of a data management device according to one embodiment disclosed in this document.

[0036] FIG. 7 is a flowchart illustrating the operation of a data management device according to one embodiment disclosed in this document.

[0037] FIG. 8 is a block diagram showing the hardware configuration of a computing system for performing an operation method of a data management device according to one embodiment disclosed in this document.

[0038] Hereinafter, various embodiments of the present invention will be described with reference to the accompanying drawings. However, this is not intended to limit the present invention to specific embodiments, and it should be understood that various modifications, equivalents, and / or alternatives of the embodiments of the present invention are included.

[0039] The various embodiments and terminology used in this document are not intended to limit the technical features described in this document to specific embodiments, but should be understood to encompass various modifications, equivalents, or alternatives of the embodiments. 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 items, unless the context clearly indicates otherwise.

[0040] 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 element from other corresponding elements, and do not limit the corresponding elements in any other respect (e.g., importance or order) unless specifically stated otherwise.

[0041] In this document, whenever 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), wirelessly, or via a third component.

[0042] According to one embodiment, the method 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 user devices. In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily generated in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or an intermediary server.

[0043] According to various embodiments, 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 various embodiments, one or more components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (e.g., a module or a program) may be integrated into a single component. In such a case, the integrated component may perform one or more functions of each of the plurality of components identically or similarly to those performed by the corresponding component among the plurality of components prior to the integration. According to various embodiments, the operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.

[0044] FIG. 1 is a diagram showing a data management system according to one embodiment disclosed in this document.

[0045] Referring to FIG. 1, a data management system (1) according to one embodiment disclosed in this document may include a battery management device (20) that manages a battery (not shown) included in a vehicle (10) and a data management device (100). In FIG. 1, the data management system (1) is illustrated as including a vehicle (10), but is not limited thereto, and the data management system (1) may include any device including a battery, such as an Energy Storage System (ESS), in addition to the vehicle (10).

[0046] According to an embodiment, the vehicle (10) may include an electrical, electronic, or mechanical vehicle that operates by receiving power from a battery (not shown). For example, the vehicle (10) may include an electric vehicle (EV) and / or a two-wheeled electric vehicle.

[0047] According to an embodiment, the vehicle (10) may include one or more batteries (not shown). Here, the battery may supply power to a target device (e.g., a vehicle). According to an embodiment, the battery may include one or more battery cells. Here, the battery cell may be a basic unit of a battery cell that can charge and discharge electrical energy. For example, the battery cell may be a lithium-ion (Li-ion) battery, a lithium-ion polymer (Li-ion polymer) battery, a nickel-cadmium (Ni-Cd) battery, a nickel-metal hydride (Ni-MH) battery, etc., but is not limited thereto.

[0048] In an embodiment, the battery management device (20) can manage, diagnose, and test the battery. In an embodiment, the battery management device (20) can be included in any one of a battery management system (BMS) within a battery pack, a battery management server, a computer, and a cloud server. In another embodiment, the battery management device (20) can also be included in a device for charge and discharge testing, such as a charge and discharge cycler.

[0049] According to an embodiment, the data management device (100) can acquire and manage data through the battery management device (20). For example, the data management device (100) may include a portable communication device (e.g., a smartphone), a computer device, a portable multimedia device, a wearable device, or a server (e.g., a cloud server), but various embodiments are not limited thereto. Details related to the data management device (100) according to the embodiment may be described in detail through the following drawings.

[0050] FIG. 2 is a block diagram illustrating the configuration of a data management device according to one embodiment disclosed in this document. FIGS. 3 to 5 are diagrams showing data stored in a data management device according to one embodiment disclosed in this document. FIG. 6 is a diagram showing a buffer of a data management device according to one embodiment disclosed in this document.

[0051] First, referring to FIG. 2, the data management device (100) may include a data acquisition unit (110), a storage unit (120), and a controller (130). However, this is merely exemplary, and various embodiments are not limited thereto. For example, at least one of the components of the aforementioned data management device (100) may be omitted, or one or more other components may be added to the configuration of the data management device (100). Furthermore, at least one of the aforementioned components may be integrated with another component.

[0052] Referring to FIGS. 2 and 3, the data acquisition unit (110) can acquire battery data (D1, D2, D3, ..., D11_SH, ..., Dn) included in the vehicle (10). Here, the battery data (D1, D2, D3, ..., D11_SH, ..., Dn) may refer to data regarding the state of the battery. For example, the battery data (D1, D2, D3, ..., D11_SH, ..., Dn) may include measured values ​​such as voltage, current, and temperature of the battery. In addition, the battery data (D1, D2, D3, ..., D11_SH, ..., Dn) may include information regarding the state of the battery calculated based on the measured values. For example, the information regarding the state of the battery may include SOC (State of Charge), SOH (State of Health), resistance, current cycle, remaining predicted cycle, and C-rate.

[0053] According to an embodiment, the data acquisition unit (110) can acquire battery data (D1, D2, D3, ..., D11_SH, ..., Dn) in the driving state and the inactive state (or the parking state) of the vehicle (10). In another aspect, the data acquisition unit (110) can acquire battery data (D1, D2, D3, ..., D11_SH, ..., Dn) in the charging section, the post-charge rest section, the discharging section, and the post-discharging rest section of the battery included in the vehicle (10).

[0054] According to an embodiment, the data acquisition unit (110) can acquire battery data (D1, D2, D3, ..., D11_SH, ..., Dn) in real time. Here, real time may mean acquiring data at the actual time when the battery data is generated. According to another embodiment, the data acquisition unit (110) can acquire battery data (D1, D2, D3, ..., D11_SH, ..., Dn) at predetermined time intervals. For example, the data acquisition unit (110) can acquire battery data at predetermined unit time intervals (e.g., 1 second, 1 minute, 10 minutes, 1 hour, or 1 day, etc.).

[0055] According to an embodiment, the data acquisition unit (110) can acquire battery data (D1, D2, D3, ..., D11_SH, ..., Dn) from a battery management device (20), a user terminal, a server, a cloud server, or a database. However, the present invention is not limited thereto, and the data acquisition unit (110) can acquire battery data (D1, D2, D3, ..., D11_SH, ..., Dn) from another system or platform connected via a wired and / or wireless network.

[0056] According to an embodiment, the battery data (D1, D2, D3, ..., D11_SH, ..., Dn) may include shadow battery data (D11_SH). Here, the shadow battery data (D11_SH) may refer to data collected by the battery management device (20) that was not transmitted to the data management device (100) in a timely manner due to reasons such as communication failure. Accordingly, the shadow battery data (D11_SH) may refer to a case where battery data that should have been acquired by the data acquisition unit (110) at a specific point in the past was acquired later by the data acquisition unit (110).

[0057] According to an embodiment, the storage unit (120) may store data used by at least one component (e.g., controller (130)) of the data management device (100). According to an embodiment, the storage unit (120) may refer to a storage space that stores big data. For example, the storage unit (120) may refer to a data warehouse.

[0058] According to an embodiment, the controller (130) can store battery data (D1, D2, D3, ..., D11_SH, ..., Dn) in the storage unit (120). In addition, the controller (130) can process and manage the battery data (D1, D2, D3, ..., D11_SH, ..., Dn).

[0059] According to an embodiment, the storage unit (120) can store battery data (D1, D2, D3, ..., D11_SH, ..., Dn) acquired from the data acquisition unit (110). Here, the battery data (D1, D2, D3, ..., D11_SH, ..., Dn) can include voltage, current, and / or temperature change profiles according to the state of charge of the battery. The types of battery data (D1, D2, D3, ..., D11_SH, ..., Dn) stored in the storage unit can be added or changed.

[0060] According to an embodiment, the storage unit (120) may include a short-term storage unit (S1) and a long-term storage unit (S2). Here, the short-term storage unit (S1) may refer to a space for storing data in the short term, and the long-term storage unit (S2) may refer to a space for storing data in the long term. According to an embodiment, the controller (130) may divide and store battery data in the short-term storage unit (S1) and the long-term storage unit (S2) based on the storage period of the battery data. For example, battery data (D1, D2, D3, ..., D11_SH, ..., Dn) acquired by the data acquisition unit (110) may be stored in the short-term storage unit (S1) for a predetermined period of time from the time of being stored in the data management device (100), and thereafter may be moved to and stored in the long-term storage unit (S2).

[0061] According to an embodiment, the predetermined period of time may be determined by the controller (130). For example, the controller (130) may determine the predetermined period of time to be 10 days. In this case, the controller (130) may store battery data (e.g., D1, D2, D3, ..., D10) stored in the data management device (100) for a period of time less than 10 days in the short-term storage (S1), and may store battery data (e.g., D11, D12, D13, ..., Dn) stored for a period of time older than 10 days in the long-term storage (S2).

[0062] According to an embodiment, the storage unit (120) may include a plurality of partitions (P1, P2, P3, ..., Pn). Here, the partitions (P1, P2, P3, ..., Pn) may mean storage units for dividing and managing a database. A portion of the storage unit (120) including a plurality of partitions (P1, P2, P3, ..., Pn) may be a long-term storage unit (S2).

[0063] According to an embodiment, the controller (130) may create partitions (P1, P2, P3, ..., Pn) in the storage (120) using any partitioning technique. For example, the controller (130) may create partitions (P1, P2, P3, ..., Pn) in the storage (120) using techniques such as range partitioning, multicolumn range partitioning, hash partitioning, list partitioning, composite partitioning, reference partitioning, interval partitioning, and system partitioning.

[0064] According to an embodiment, the controller (130) may store the battery data (D1, D2, D3, ..., D11_SH, ..., Dn) in each of a plurality of partitions (P1, P2, P3, ..., Pn) based on the attributes of the battery data (D1, D2, D3, ..., D11_SH, ..., Dn). Here, the attributes of the data may include any attributes related to the data, such as the time when the data was generated, the type of vehicle from which the data was collected, and the type of data. Through this, the controller (130) may group and store the battery data (D1, D2, D3, ..., D11_SH, ..., Dn), thereby saving data storage space and increasing the ease of data access.

[0065] According to an embodiment, the controller (130) may store the battery data (D1, D2, D3, ..., D11_SH, ..., Dn) in each of a plurality of partitions (P1, P2, P3, ..., Pn) based on the generation time of the battery data (D1, D2, D3, ..., D11_SH, ..., Dn). Here, the generation time of the battery data (D1, D2, D3, ..., D11_SH, ..., Dn) may mean the time when the battery data (D1, D2, D3, ..., D11_SH, ..., Dn) is generated in the vehicle (10). In this case, each of the plurality of partitions (P1, P2, P3, ..., Pn) may correspond to a specific time. For example, the controller (130) may store battery data generated on different dates in different partitions based on the generation time (unit: day) of the battery data.

[0066] According to an embodiment, the controller (130) may store some of the battery data, excluding the shaded battery data (D11_SH), in a plurality of partitions (P1, P2, P3, ..., Pn). In another aspect, the controller (130) may store battery data, excluding the shaded battery data (D11_SH), whose storage period is longer than a predetermined period, in a long-term storage (S2).

[0067] According to an embodiment, the controller (130) can manage the shaded battery data (D11_SH) together with the battery data (D11), which is data that was generated at the same generation time as the shaded battery data and is already stored in the partition (P1). Here, the operation of the controller (130) can be described with reference to FIGS. 5 and 6. Through this, the controller (130) can efficiently manage the shaded battery data (D11_SH) and the battery data stored in each of the plurality of partitions (P1, P2, P3, ..., Pn).

[0068] Referring to FIG. 3, the controller (130) can store battery data acquired by the data management device (100) after a predetermined period of time in each of a plurality of partitions (P1, P2, P3, ..., Pn). Here, the predetermined period of time may be the same as the predetermined period of time (e.g., 10 days) that is a standard for storing battery data in the long-term storage (S2) described above. For example, the controller (130) can store battery data acquired after 10 days (D11, D12, D13, ..., Dn) in each of the plurality of partitions (P1, P2, P3, ..., Pn). Through this, the controller (130) can efficiently manage battery data by dividing and storing battery data that requires long-term storage in each of the plurality of partitions (P1, P2, P3, ..., Pn).

[0069] Referring to FIG. 4, the controller (130) may divide and store battery data (Dn) in each of a plurality of partitions (P1, P2, P3, ..., Pn). In another aspect, each of the plurality of partitions (P1, P2, P3, ..., Pn) may include divided battery data (Dn_1, Dn_2, Dn_3, ..., Dn_4). For example, the controller (130) may divide the battery data (Dn) into one or more battery data (Dn_1, Dn_2, Dn_3, ..., Dn_4) and store the divided battery data (Dn_1, Dn_2, Dn_3, ..., Dn_4) in the partition (Pn).

[0070] According to an embodiment, the controller (130) can use a plurality of computing nodes to distribute and process divided battery data (Dn_1, Dn_2, Dn_3, ..., Dn_4). Here, the computing node may refer to an operation or processing unit in which the controller (130) processes data. Therefore, the controller (130) can process the divided battery data (Dn_1, Dn_2, Dn_3, ..., Dn_4) in a distributed manner, thereby simultaneously and in parallel processing the battery data and improving the data processing speed.

[0071] According to an embodiment, the controller (130) may divide the battery data (Dn) into equal-sized portions and store them in each of a plurality of partitions (P1, P2, P3, ..., Pn). Here, the size of the data may refer to the size of the data file. In this case, when the controller (130) processes the battery data (Dn_1, Dn_2, Dn_3, ..., Dn_4) divided into equal-sized portions, the load on each of the plurality of computing nodes may be equal.

[0072] According to various embodiments, when the controller (130) divides the battery data (Dn) into different sizes, large-sized data may be concentrated on specific computing nodes. In this case, the processing speed of specific computing nodes may be delayed, and data distribution distortion may occur. In contrast, when the controller (130) divides the battery data (Dn) into equal sizes, as in the present invention, all computing nodes can process data of the same size. Therefore, the distributed processing speed of the controller (130) can be improved. Furthermore, the performance of the controller (130) can be optimized.

[0073] According to an embodiment, the controller (130) can divide the battery data (Dn) based on the number of computing nodes of the data management device (100). Here, the number of computing nodes may vary depending on the specifications of the data management device (100). For example, if the data management device (100) has four computing nodes, the controller (130) can divide the battery data (Dn) into four (Dn_1, Dn_2, Dn_3, Dn_4). Accordingly, each computing node can process one divided battery data. Through this, the controller (130) can improve the data distribution processing speed without data distribution distortion.

[0074] According to an embodiment, the controller (130) can segment the battery data (Dn) in chronological order. Alternatively, the controller (130) can segment the battery data (Dn) in the chronological order in which the battery data (Dn) were generated. Through this, the controller (130) can manage the battery data (Dn) in chronological order.

[0075] Referring to FIG. 5, the controller (130) can manage the shaded battery data (D11_SH) by integrating it with the battery data stored in the storage unit (120). Here, the shaded battery data (D11_SH) may refer to missing battery data when a portion of the battery data is transmitted from the vehicle (10) to the data management device (100) due to reasons such as communication failure. According to an embodiment, there may be one or more shaded battery data.

[0076] According to an embodiment, the shaded battery data (D11_SH) may be generated at the same generation time as the battery data (e.g., D11) stored in the storage unit (120), and may mean battery data acquired by the data acquisition unit (110) after the stored battery data (D11) is stored in the storage unit (120). In another aspect, when the shaded battery data (D11_SH) is stored in the short-term storage unit (S1), the shaded battery data (D11_SH) may be generated at the same generation time as the battery data (e.g., D11) stored in the long-term storage unit (S2), and may mean battery data acquired by the data acquisition unit (110) after the stored battery data (D11) is stored in the long-term storage unit (S2).

[0077] According to an embodiment, the controller (130) can manage the shaded battery data (D11_SH) by integrating it with the battery data (D11) that was generated at the same time as the shaded battery data (D11_SH) and stored in the storage unit (120).

[0078] According to various embodiments, when the controller (130) stores the shaded battery data (D11_SH) in the partition (P1) containing the battery data (D11) stored in the storage unit (120), the shaded battery data (D11_SH) may be additionally stored as a separate file from the battery data (D11) already stored in the partition (P1). Accordingly, the shaded battery data (D11_SH) may have a different size from the already stored battery data (D11). In addition, as the number of shaded battery data (D11_SH) increases, the diversity of the sizes of the battery data stored in the partition (P1) may increase. In this case, there is a problem that data distribution distortion may occur and the data processing speed may be delayed.

[0079] In contrast, the controller (130) according to the embodiment can integrate the battery data (D11) and the shadow battery data (D11_SH) to generate temporary battery data (D11') and re-store the integrated battery data, the temporary battery data (D11'), in the partition (P1). Here, the battery data (D11) may refer to battery data corresponding to the generation time of the shadow battery data (D11_SH) among the battery data stored in the storage unit (120). In addition, the partition (P1) in which the temporary battery data (D11') is re-stored may refer to a partition corresponding to the generation time among a plurality of partitions. Through this, the controller (130) can prevent the above-described data distribution distortion and improve the data processing speed.

[0080] Referring to FIG. 6, the controller (130) can generate temporary battery data (D11') using a temporary table (or buffer) (S3). Here, the temporary table or buffer (S3) may mean a temporary data storage.

[0081] According to an embodiment, the controller (130) may load the shaded battery data (D11_SH) of the short-term storage (S1) and the battery data (D11) of the long-term storage (S2) into a buffer (S3), and integrate the two data (D11_SH and D11) into one data group. Here, the integrated data group may be referred to as temporary battery data (D11').

[0082] According to an embodiment, the controller (130) can load the battery data (D11) of the long-term storage (S2) into a buffer (S3), which is a data table, and subsequently load the shadow battery data (D11_SH) into the same table. Thus, the controller (130) can store the temporary battery data (D11') in the buffer (S3). According to an embodiment, the controller (130) can list the battery data (D11) and the shadow battery data (D11_SH) in chronological order in the data table.

[0083] According to an embodiment, the controller (130) can re-store the temporary battery data (D11') in the long-term storage (S2) of the storage (120). Here, the file size of the temporary battery data (D11') may be larger than the file size of the battery data (D11). According to an embodiment, the controller (130) can re-store the temporary battery data (D11') in the partition (P1) where the battery data (D11) generated at the same generation time as the shadow battery data (D11_SH) was stored. Through this, the controller (130) can re-store the temporary battery data (D11') while maintaining a plurality of partitions (P1, P2, P3, ..., Pn).

[0084] According to an embodiment, the controller (130) may delete the battery data (D11) stored in the partition (P1) before restoring the temporary battery data (D11'). In another aspect, the controller (130) may delete the battery data (D11) corresponding to the generation time of the shaded battery data (D11_SH) stored in the storage unit (120) before restoring the temporary battery data (D11'). Through this, the controller (130) may reduce the possibility of the battery data (D11) being lost before the temporary battery data (D11') is generated. In addition, the controller (130) may restore the temporary battery data (D11') while maintaining a plurality of partitions (P1, P2, P3, ..., Pn) without having to create a new partition.

[0085] According to an embodiment, the controller (130) can divide the temporary battery data (D11') and re-store it in the partition (P1). Here, the controller (130) can divide the temporary battery data (D11') using the battery data division method described above. For example, the controller (130) can divide the temporary battery data (D11') into parts of the same size. In addition, the controller (130) can divide the temporary battery data (D11') based on the number of computing nodes of the data management device (100). In addition, the controller (130) can divide the temporary battery data (D11') in chronological order. Details related to the division have been described with reference to FIG. 4 and may not be repeated herein. Through this, the controller (130) can prevent data distribution distortion and improve data processing speed.

[0086] FIG. 7 is a flowchart illustrating the operation of a data management device according to one embodiment disclosed in this document.

[0087] The operations illustrated in FIG. 7 may be performed via the data management device (100) of FIGS. 1 and 2. While the operations in the following embodiments may be performed sequentially, they are not necessarily performed sequentially. For example, the order of the operations may be changed, and at least two operations may be performed in parallel. Furthermore, at least one of the operations below may be omitted depending on the embodiment.

[0088] Referring to FIG. 7, a data management device (100) obtains battery data including shaded battery data from a vehicle (S101), stores the battery data in each of the plurality of partitions based on a generation time when the battery data is generated in the vehicle in a storage unit including a plurality of partitions (S102), generates battery data corresponding to the generation time of the shaded battery data among the battery data stored in the storage unit and temporary battery data including the shaded battery data (S103), and divides the temporary battery data and re-stores it in a partition corresponding to the generation time among the plurality of partitions (S104).

[0089] In operation S101, the data management device (100) can acquire battery data (D1, D2, ..., Dn) including shaded battery data (D11_SH) from the vehicle (10) (S101). According to an embodiment, operation S101 can be performed by the data acquisition unit (110).

[0090] In operation S102, the data management device (100) may store the battery data (D1, D2, ..., Dn) in each of the plurality of partitions (P1, P2, P3, ..., Pn) based on the generation time, which is the time when the battery data was generated in the vehicle (10), in the storage unit (120) including the plurality of partitions (P1, P2, P3, ..., Pn) (S102). According to an embodiment, operations S101 to S104 may be performed by the controller (130).

[0091] According to an embodiment, the controller (130) may store battery data, excluding shaded battery data (D11_SH), in each of a plurality of partitions (P1, P2, P3, ..., Pn). A portion of the storage unit (120) including a plurality of partitions (P1, P2, P3, ..., Pn) may be a long-term storage (S2).

[0092] In operation S103, the data management device (100) can generate battery data (D11) corresponding to the generation time of the shaded battery data (D11_SH) among the battery data stored in the storage unit (120) and temporary battery data (D11') including the shaded battery data (S103).

[0093]

[0094] *In operation S104, the data management device (100) can divide the temporary battery data (D11') and re-store it in the partition (P1) corresponding to the generation time among the plurality of partitions (S104).

[0095] FIG. 8 is a block diagram showing the hardware configuration of a computing system for performing an operation method of a data management device according to one embodiment disclosed in this document.

[0096] Referring to FIG. 8, a computing system (200) according to one embodiment disclosed in this document may include an MCU (210), a memory (220), an input / output I / F (230), and a communication I / F (240).

[0097] The MCU (210) may be a processor that executes various programs (e.g., a battery data collection program, a data analysis program, a data processing program, etc.) stored in the memory (220), processes various information including battery data through these programs, and performs the functions of the data management device (100) shown in FIGS. 1 to 7 described above.

[0098] The memory (220) can store various programs such as a battery data collection program, a data analysis program, and a data processing program.

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

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

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

[0102] In this way, a computer program according to one embodiment disclosed in this document may be implemented as a module that performs each function illustrated in FIG. 2, for example, by being recorded in a memory (220) and processed by an MCU (210).

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

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

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

[0106] [Explanation of symbols]

[0107] 1: Data Management System

[0108] 10: Vehicle

[0109] 20: Battery management device

[0110] 100: Data Management Device

[0111] 110: Data Acquisition Unit

[0112] 120: Storage

[0113] 130: Controller

[0114] 200: Computing Systems

[0115] 210: MCU

[0116] 220: Memory

[0117] 230: Input / Output I / F

[0118] 240: Communication I / F

Claims

1. A data acquisition unit for acquiring battery data including shaded battery data from a vehicle; A storage unit including a plurality of partitions and storing the battery data; and Store the battery data in each of the plurality of partitions based on the generation time when the battery data was generated in the vehicle, Generate battery data corresponding to the generation time of the shaded battery data among the battery data stored in the above storage unit and temporary battery data including the shaded battery data, A data management device including a controller that divides the temporary battery data and resaves it in a partition corresponding to the creation time among the plurality of partitions.

2. In claim 1, A data management device in which the shaded battery data is generated at the same time as the battery data stored in the storage unit and the battery data is acquired by the data acquisition unit after the stored battery data is stored in the storage unit.

3. In claim 1, The above controller, A data management device that divides the battery data into equal sizes and stores them in each of the plurality of partitions.

4. In claim 3, The above controller, A data management device that divides the battery data based on the number of computing nodes of the data management device.

5. In claim 1, The above controller, Store the above temporary battery data in a buffer, A data management device that deletes battery data corresponding to the generation time of the shaded battery data stored in the storage unit before re-storing the temporary battery data in the storage unit.

6. In claim 1, The above controller, A data management device that divides the above temporary battery data into partitions of the same size and resaves them in the partition corresponding to the generation time.

7. In claim 6, The above controller, A data management device that divides the temporary battery data based on the number of computing nodes of the data management device.

8. In claim 1, The above controller, A data management device that divides the above temporary battery data into time series.

9. A step of obtaining battery data including shaded battery data from a vehicle; A step of storing the battery data in each of the plurality of partitions based on a generation time when the battery data was generated in the vehicle, in a storage unit including a plurality of partitions; A step of generating battery data corresponding to the generation time of the shaded battery data among the battery data stored in the storage unit and temporary battery data including the shaded battery data; and A data management method comprising a step of dividing the temporary battery data and resaving it in a partition corresponding to the creation time among the plurality of partitions.

10. In claim 9, A data management method wherein the shaded battery data is generated at the same time as the battery data stored in the storage unit and is battery data acquired after the stored battery data is stored in the storage unit.

11. In claim 9, The step of storing the above battery data in each of the plurality of partitions is: A data management method for dividing and storing the battery data into equal sizes in each of the above plurality of partitions.

12. In claim 11, A data management method for dividing the battery data based on the number of computing nodes of the above data management method.

13. In claim 9, A step of storing the temporary battery data in a buffer; and A data management method further comprising a step of deleting battery data corresponding to the generation time of the shaded battery data stored in the storage unit before re-storing the temporary battery data in the storage unit.

14. In claim 9, The steps for restoring the above temporary battery data are: A data management method for dividing the above temporary battery data into equal sizes and resaving them in partitions corresponding to the generation time.

15. In claim 14, A data management method for dividing the temporary battery data based on the number of computing nodes of the above data management method.

16. In claim 9, The steps for restoring the above temporary battery data are: A data management method comprising a step of dividing the above temporary battery data in time series order.

Images