Data management apparatus and method of operation thereof

Abstract

The data management apparatus according to the embodiments disclosed herein may include: a data acquisition unit for acquiring battery data including shadow battery data from a vehicle; a storage unit including multiple partitions and storing the battery data; and a controller for storing battery data in each of the multiple partitions based on the generation time of generating battery data in the vehicle, generating battery data corresponding to the generation time of shadow battery data in the battery data stored in the storage unit and temporary battery data including shadow battery data, and dividing the temporary battery data to re-store the divided temporary battery data in the partitions corresponding to the generation time in the multiple partitions.

Description

Technical Field

[0001] Cross-references to related applications

[0002] This application claims priority to Korean Patent Application No. 10-2023-0181027, filed with the Korean Intellectual Property Office on December 13, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The various embodiments disclosed herein relate to data management devices and their operating methods. Background Technology

[0004] In recent years, research and development on rechargeable batteries has been actively underway. A rechargeable battery is a battery capable of being charged and discharged, and includes all the latest lithium-ion batteries in addition to traditional nickel-cadmium (Ni / Cd) and nickel-metal hydride (Ni / MH) batteries. Lithium-ion batteries have the advantage of higher energy density compared to traditional Ni / Cd and Ni / MH batteries. Furthermore, because lithium-ion batteries can be manufactured in small, lightweight forms, they are used as power sources for mobile devices, and recently, their application has expanded to power electric vehicles, making them a promising next-generation energy storage medium.

[0005] A separate data management device can be used to analyze battery data. This device can collect battery data about the battery's state from a battery management device connected to the battery or a battery pack containing the battery. Alternatively, the data management device can collect battery data from a server.

[0006] As the amount of battery data collected recently increases, the importance of managing battery data also increases, and the cost of managing battery data may also increase. Therefore, it is necessary to manage the collected data to reduce the cost of battery data management and to manage battery data effectively. Summary of the Invention

[0007] Technical issues

[0008] Various embodiments of the present invention aim to provide a data management device and its operating method for managing data stored in a database.

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

[0010] The technical objectives of the embodiments disclosed herein are not limited to those described above, and other objectives not described herein will be clearly understood by those skilled in the art from the following description.

[0011] Technical solution

[0012] The data management apparatus according to the embodiments disclosed herein may include: a data acquisition unit configured to acquire battery data including shadow battery data from a vehicle; a memory including a plurality of partitions and storing the battery data; and a controller configured to: store the battery data in each of the plurality of partitions based on a generation time, which is the time when the battery data is generated from the vehicle; generate battery data in the battery data stored in the memory corresponding to the generation time of the shadow battery data and temporary battery data including the shadow battery data; and partition the temporary battery data and restore it in the partition of the plurality of partitions corresponding to the generation time.

[0013] According to an implementation, the shadow battery data may be battery data generated at the same generation time as the battery data stored in the memory, and acquired by the data acquisition unit after the stored battery data is stored in the memory.

[0014] According to an implementation method, the controller can divide the battery data into equal sizes and store them in each of the plurality of partitions.

[0015] According to an implementation, the controller can partition the battery data based on the number of computing nodes of the data management device.

[0016] According to one implementation, the controller can be configured to store the temporary battery data in a buffer; and to delete battery data stored in the memory corresponding to the generation time of the shadow battery data before storing the temporary battery data in the memory.

[0017] According to an implementation method, the controller can divide the temporary battery data into equal-sized portions and then restore them in a partition corresponding to the generation time.

[0018] According to an implementation, the controller can partition the temporary battery data based on the number of computing nodes of the data management device.

[0019] According to an implementation, the controller can divide the temporary battery data in a time-series order.

[0020] The data management method according to the embodiments disclosed herein may include the following steps: acquiring battery data including shadow battery data from a vehicle; storing the battery data in each of the plurality of partitions of a memory comprising a plurality of partitions based on a generation time, which is the time when the battery data is generated from the vehicle; generating battery data in the battery data stored in the memory corresponding to the generation time of the shadow battery data and temporary battery data including the shadow battery data; and dividing the temporary battery data and re-storing it in the partition of the plurality of partitions corresponding to the generation time.

[0021] According to an implementation, the shadow battery data may be battery data generated at the same generation time as the battery data stored in the memory, and acquired after the stored battery data is stored in the memory.

[0022] According to an implementation method, the step of storing the battery data in each of the plurality of partitions may include the following steps: in each of the plurality of partitions, the battery data is divided into equal sizes and then stored.

[0023] According to an implementation, the data processing method may include the following steps: dividing the battery data based on the number of computing nodes in the data management method.

[0024] According to an embodiment, the data management method may further include the following steps: storing the temporary battery data in a buffer; and deleting battery data stored in the memory corresponding to the generation time of the shadow battery data before storing the temporary battery data in the memory.

[0025] According to an implementation, the step of re-storing the temporary battery data may include the following steps: dividing the temporary battery data into equal sizes and then re-storing it in a partition corresponding to the generation time.

[0026] According to an implementation, the data management method may include the following steps: partitioning the temporary battery data based on the number of computing nodes in the data management method.

[0027] According to an implementation, the step of re-storing the temporary battery data may include the following steps: dividing the temporary battery data in chronological order.

[0028] Beneficial effects

[0029] The data management apparatus and its operating method according to the embodiments disclosed herein can manage data stored in a database.

[0030] The data management apparatus and its operating method according to the embodiments disclosed herein can be based on an algorithm for preventing the distribution distortion of data stored in a database.

[0031] In addition, various effects that can be directly or indirectly identified through this disclosure may be provided. Attached Figure Description

[0032] Figure 1 This is a view illustrating a data management system according to one embodiment disclosed herein.

[0033] Figure 2 This is a block diagram illustrating a data management apparatus according to one embodiment disclosed herein.

[0034] Figure 3 This is a view showing data stored in a data management device according to one embodiment disclosed herein.

[0035] Figure 4 This is a view showing data stored in a data management device according to one embodiment disclosed herein.

[0036] Figure 5 This is a view showing data stored in a data management device according to one embodiment disclosed herein.

[0037] Figure 6 This is a view showing the buffer of a data management apparatus according to one embodiment disclosed herein.

[0038] Figure 7 This is a flowchart describing the operation of a battery management device according to one embodiment disclosed herein.

[0039] Figure 8 This is a block diagram illustrating the hardware configuration of a computing system for performing an operation method of a data management apparatus according to an embodiment disclosed herein. Detailed Implementation

[0040] Hereinafter, various embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that this is not intended to limit the present disclosure to a particular embodiment, but rather to include various modifications, equivalents, and / or alternatives to the embodiments of the present disclosure.

[0041] It should be understood that the various embodiments of this disclosure and the terminology used herein are not intended to limit the technical features described herein to specific embodiments, but rather to include various modifications, equivalents, or alternatives to the corresponding embodiments. In the description of the drawings, similar reference numerals may be used for similar or related components. Unless the relevant context clearly indicates otherwise, the singular form of a noun corresponding to an item may include one item or more items.

[0042] In this disclosure, each of the phrases such as “A or B,” “at least one of A and B,” “at least one of A or B,” “A, B or C,” “at least one of A, B and C,” and “at least one of A, B or C” may include any one of the items listed together in the respective phrases of these phrases or all possible combinations thereof. Terms such as “first,” “second,” “A,” “B,” “(a),” or “(b)” may be used simply to distinguish one component from another without otherwise limiting the component (e.g., in terms of importance or order).

[0043] In this disclosure, when a component (e.g., a first) is described as “connected,” “linked,” or “joined” to another component (e.g., a second), whether or not the terms “functionally” or “communically” are used, it means that the component can be connected to the other component directly (e.g., via wired), wirelessly, or via a third component.

[0044] According to one embodiment, the methods according to the various embodiments disclosed herein can be provided by being included in a computer program product. The computer program product can be traded as a commodity between a seller and a buyer. The computer program product can be distributed in the form of a device-readable storage medium (e.g., an optical disc read-only memory (CD-ROM)) or via an app store (e.g., the Play Store). TM Computer program products can be distributed online (e.g., downloaded or uploaded) or directly between two user devices (e.g., smartphones). They can be distributed in the form of a device-readable storage medium (e.g., an optical disc read-only memory (CD-ROM)), or through an app store (e.g., downloaded or uploaded) or directly between two user devices. In the case of online distribution, at least some of the computer program products may be at least temporarily stored or temporarily generated in a device-readable storage medium, such as the memory of a manufacturer's server, an app store's server, or a relay server.

[0045] According to various embodiments, each of the above components (e.g., a module or program) may include a single object or one or more objects, and some of the objects may be separately located in another component. According to various embodiments, one or more of the corresponding components or their operations may be omitted, or one or more other components or operations may be added. Alternatively or additionally, multiple components (e.g., modules or programs) may be integrated into one component. In this case, the integrated component may perform one or more functions of each of the multiple components, the functions being the same as or similar to the functions performed by the corresponding components in the multiple components before integration. According to various embodiments, the operations performed by a module, program, or other component may be performed sequentially, in parallel, repeatedly, or heuristically, or one or more operations may be performed in a different order or omitted, or one or more other operations may be added.

[0046] Figure 1 This is a view illustrating a data management system according to one embodiment disclosed herein.

[0047] Reference Figure 1 According to one embodiment disclosed herein, the data management system 1 may include a battery management device 20 and a data management device 100 for managing a battery (not shown) included in a vehicle 10. Although Figure 1 The data management system 1 is shown to include a vehicle 10, but this disclosure is not limited thereto. The data management system 1 may include any battery-integrated device other than the vehicle 10, such as an energy storage system (ESS).

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

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

[0050] According to one embodiment, the battery management device 20 can manage, diagnose, and test batteries. According to another embodiment, the battery management device 20 may be included in one of a battery management system (BMS), a battery management server, a computer, and a cloud server within a battery pack. According to yet another embodiment, the battery management device 20 may be included in a device for charge-discharge testing (such as a charge-discharge cycler).

[0051] According to various embodiments, 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), and various embodiments are not limited thereto. The contents related to the data management device 100 according to the embodiments can be described in detail in the following figures.

[0052] Figure 2 This is a block diagram illustrating a data management apparatus according to one embodiment disclosed herein. Figures 3 to 5 This is a view showing data stored in a data management device according to one embodiment disclosed herein. Figure 6 This is a view showing the buffer of a data management apparatus according to one embodiment disclosed herein.

[0053] First, refer to Figure 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 an example, and various implementations are not limited thereto. For example, at least one of the aforementioned components of the 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. Additionally, at least one of the aforementioned components may be integrated with another component.

[0054] Reference Figure 2 and Figure 3 The data acquisition unit 110 can acquire battery data D1, D2, D3, ..., D11_SH, ..., and Dn included in the vehicle 10. Here, the battery data D1, D2, D3, ..., D11_SH, ..., and Dn can be data related to the battery state. For example, the battery data D1, D2, D3, ..., D11_SH, ..., and Dn can include measurements such as battery voltage, current, and temperature. Additionally, the battery data D1, D2, D3, ..., D11_SH, ..., and Dn can include information related to the battery state calculated based on the measurements. For example, information related to the battery state can include state of charge (SOC), state of health (SOH), resistance, current cycle, remaining predicted cycles, C-rate, etc.

[0055] According to the implementation, the data acquisition unit 110 can acquire battery data D1, D2, D3, ..., D11_SH, ..., and Dn in the driving state and inactive state (or parked state) of the vehicle 10. On the other hand, the data acquisition unit 110 can acquire battery data D1, D2, D3, ..., D11_SH, ..., and Dn in the charging interval, the idle interval after charging, the discharging interval, and the idle interval after discharging of the battery included in the vehicle 10.

[0056] According to one embodiment, the data acquisition unit 110 can acquire battery data D1, D2, D3, ..., D11_SH, ..., and Dn in real time. Here, real time can mean acquiring the data at the actual time the battery data is generated. According to another embodiment, the data acquisition unit 110 can acquire battery data D1, D2, D3, ..., D11_SH, ..., and 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).

[0057] According to the implementation, the data acquisition unit 110 can acquire battery data D1, D2, D3, ..., D11_SH, ..., and Dn from the battery management device 20, the user terminal, the server, the cloud server, or the database. However, this disclosure is not limited thereto; the data acquisition unit 110 can acquire battery data D1, D2, D3, ..., D11_SH, ..., and Dn from another system or platform connected via a wired and / or wireless network.

[0058] According to the implementation, battery data D1, D2, D3, ..., D11_SH, ..., and Dn may include shadowed battery data D11_SH. Here, shadowed battery data D11_SH may be data that was not sent to data management device 100 in a timely manner due to reasons such as communication failures in the data collected in battery management device 20. Therefore, shadowed battery data D11_SH may mean a situation where battery data that data acquisition unit 110 should have acquired at a specific point in the past was later acquired by data acquisition unit 110.

[0059] According to one embodiment, the memory 120 may store data used by at least one component of the data management device 100 (e.g., controller 130). According to another embodiment, the memory 120 may be a storage space for storing large amounts of data. For example, the memory 120 may be a data warehouse.

[0060] According to the implementation, the controller 130 can store battery data D1, D2, D3, ..., D11_SH, ..., and Dn in the memory 120. Furthermore, the controller 130 can process and manage the battery data D1, D2, D3, ..., D11_SH, ..., and Dn.

[0061] According to an embodiment, the memory 120 may store battery data D1, D2, D3, ..., D11_SH, ..., and Dn acquired from the data acquisition unit 110. Here, the battery data D1, D2, D3, ..., D11_SH, ..., and Dn may include voltage, current, and / or temperature change curves based on the battery's state of charge (SOC). The types of the battery data D1, D2, D3, ..., D11_SH, ..., and Dn stored in the memory can be added or changed.

[0062] According to an embodiment, the memory 120 may include a short-term memory S1 and a long-term memory S2. Here, the short-term memory S1 may be a space for short-term data storage, and the long-term memory S2 may be a space for long-term data storage. According to an embodiment, the controller 130 may store battery data in the short-term memory S1 and the long-term memory S2 respectively based on the storage period of the battery data. For example, battery data D1, D2, D3, ..., D11_SH, ... and Dn acquired from the data acquisition unit 110 may be stored in the short-term memory S1 for a predetermined period of time starting from the time point stored in the data management device 100, and then stored by moving it to the long-term memory S2.

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

[0064] According to an implementation, the memory 120 may include multiple partitions P1, P2, P3, ..., and Pn. Here, partitions P1, P2, P3, ..., and Pn may be storage units used for partitioning and managing a database. A portion of the memory 120 including multiple partitions P1, P2, P3, ..., and Pn may be long-term storage S2.

[0065] According to the implementation, the controller 130 can use any partitioning technique to generate partitions P1, P2, P3, ..., Pn in the memory 120. For example, the controller 130 can use techniques such as range partitioning, multi-column range partitioning, hash partitioning, list partitioning, composite partitioning, reference partitioning, interval partitioning, and system partitioning to generate partitions P1, P2, P3, ..., Pn in the memory 120.

[0066] According to the implementation, the controller 130 can store the battery data D1, D2, D3, ..., D11_SH, ..., and Dn in multiple partitions P1, P2, P3, ..., and Pn respectively based on the attributes of the battery data D1, D2, D3, ..., D11_SH, ..., and Dn. Here, the attributes of the data can include any attributes related to the data, such as the time when the data was generated, the type of vehicle that collected the data, and the type of data. Therefore, the controller 130 can group and store the battery data D1, D2, D3, ..., D11_SH, ..., and Dn, thereby saving data storage space and improving the convenience of data access.

[0067] According to the implementation, the controller 130 can store the battery data D1, D2, D3, ..., D11_SH, ..., Dn in multiple partitions P1, P2, P3, ..., Pn respectively, 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 can be the time when the battery data D1, D2, D3, ..., D11_SH, ..., Dn was generated in the vehicle 10. In this case, each of the multiple partitions P1, P2, P3, ..., Pn can correspond to a specific time. For example, the controller 130 can store battery data generated on different dates in different partitions based on the generation time of the battery data (in days).

[0068] According to one implementation, the controller 130 may store some battery data, excluding the shadow battery data D11_SH, in multiple partitions P1, P2, P3, ..., Pn. Alternatively, the controller 130 may store battery data, excluding the shadow battery data D11_SH, whose storage period exceeds a predetermined time period, in long-term memory S2.

[0069] According to the implementation method, the controller 130 can manage the shadow battery data D11_SH together with the battery data D11 that was generated at the same generation time as the shadow battery data and is already stored in partition P1. Here, the operation of the controller 130 can be referred to Figure 5 and Figure 6The following description is provided. Therefore, the controller 130 can efficiently manage the shadow battery data D11_SH and the battery data stored in each of the multiple partitions P1, P2, P3, ..., and Pn.

[0070] Reference Figure 3 The controller 130 can store battery data that has been acquired by the data management device 100 for a predetermined period of time in each of multiple partitions P1, P2, P3, ..., and Pn. Here, the predetermined period of time can be the same as the base predetermined period of time (e.g., 10 days) used to store battery data that has been acquired for 10 days in the long-term storage S2. For example, the controller 130 can store battery data D11, D12, D13, ..., and Dn that has been acquired for 10 days in the multiple partitions P1, P2, P3, ..., and Pn, respectively. Therefore, the controller 130 can efficiently manage battery data by dividing and storing the battery data that needs to be stored for a long time in each of the multiple partitions P1, P2, P3, ..., and Pn.

[0071] Reference Figure 4 The controller 130 can divide and store battery data Dn in each of a plurality of partitions P1, P2, P3, ..., and Pn. Alternatively, each of the plurality of partitions P1, P2, P3, ..., and Pn can include the divided battery data Dn_1, Dn_2, Dn_3, ..., and Dn_4. For example, the controller 130 can divide battery data Dn into one or more battery data Dn_1, Dn_2, Dn_3, and Dn_4, and store the divided battery data Dn_1, Dn_2, Dn_3, and Dn_4 in partition Pn.

[0072] According to the implementation method, the controller 130 can use multiple computing nodes to perform allocation processing on the partitioned battery data Dn_1, Dn_2, Dn_3, and Dn_4. Here, the computing node can be an operation unit or processing unit of the controller 130 for processing data. Therefore, the controller 130 can perform allocation processing on the partitioned battery data Dn_1, Dn_2, Dn_3, and Dn_4, thereby processing the battery data in parallel and improving the data processing speed.

[0073] According to the implementation, the controller 130 can divide the battery data Dn into equal-sized portions and store the divided battery data in each of the multiple partitions P1, P2, P3, ..., Pn. Here, the data size can be the size of a data file. In this case, when the controller 130 processes the battery data Dn_1, Dn_2, Dn_3, and Dn_4 divided into equal-sized portions, the load on each of the multiple computing nodes can be the same.

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

[0075] According to the implementation, the controller 130 can partition the battery data Dn based on the number of computing nodes of the data management device 100. Here, the number of computing nodes can vary depending on the specifications of the data management device 100. For example, when the data management device 100 has four computing nodes, the controller 130 can partition the battery data Dn into four battery data sets: Dn_1, Dn_2, Dn_3, and Dn_4. Therefore, each computing node can process one partitioned battery data set. Thus, the controller 130 can improve the data allocation processing speed without data allocation distortion.

[0076] According to one implementation, the controller 130 can divide the battery data Dn in a time-series order. Alternatively, the controller 130 can divide the battery data Dn in the time sequence in which it was generated. Therefore, the controller 130 can manage the battery data Dn in a time-series order.

[0077] Reference Figure 5 The controller 130 can integrate and manage the shadow battery data D11_SH with the battery data stored in the memory 120. Here, the shadow battery data D11_SH may be battery data that was lost when some battery data was sent from the vehicle 10, etc. to the data management device 100 due to communication failure or other reasons. According to the embodiment, one or more shadow battery data may exist.

[0078] According to one embodiment, the shadow battery data D11_SH may be battery data generated at the same time as the battery data (e.g., D11) stored in memory 120 and acquired by the data acquisition unit 110 after the stored battery data D11 is stored in memory 120. On the other hand, when the shadow battery data D11_SH is stored in short-term memory S1, the shadow battery data D11_SH may be battery data generated at the same time as the battery data (e.g., D11) stored in long-term memory S2 and acquired by the data acquisition unit 110 after the stored battery data D11 is stored in long-term memory S2.

[0079] According to the implementation, the controller 130 can integrate and manage the shadow battery data D11_SH with the battery data D11 generated at the same time as the shadow battery data D11_SH and stored in the memory 120.

[0080] According to various implementations, when the controller 130 stores the shadow battery data D11_SH in partition P1, which includes the battery data D11 stored in memory 120, the shadow battery data D11_SH can be stored separately as a file from the battery data D11 already stored in partition P1. Therefore, the size of the shadow battery data D11_SH can differ from the size of the already stored battery data D11. Furthermore, as the number of shadow battery data D11_SH entries increases, the size of the battery data stored in partition P1 can increase in various ways. In this case, there is a possibility of data allocation distortion and potential delays in data processing speed.

[0081] In contrast, the controller 130 according to this embodiment can integrate battery data D11 and shadow battery data D11_SH to generate temporary battery data D11', and then re-store the temporary battery data D11' as integrated battery data in partition P1. Here, battery data D11 can be battery data stored in memory 120 that corresponds to the generation time of shadow battery data D11_SH. Furthermore, partition P1, where the temporary battery data D11' is re-stored, can be one of multiple partitions corresponding to the generation time. Therefore, the controller 130 can prevent the aforementioned data allocation distortion and improve data processing speed.

[0082] Reference Figure 6 The controller 130 can use a temporary table (or buffer) S3 to generate temporary battery data D11'. Here, the temporary table or buffer S3 can be temporary data storage.

[0083] According to the implementation, the controller 130 can load the shadow battery data D11_SH from the short-term memory S1 and the battery data D11 from the long-term memory S2 into the buffer S3, and integrate the two data sets D11_SH and D11 into a single data group. Here, the integrated data group can be referred to as temporary battery data D11'.

[0084] According to one embodiment, the controller 130 can load battery data D11 from the long-term storage S2 into a buffer S3, which serves as a data table, and then load shadow battery data D11_SH into the same table. Therefore, the controller 130 can store temporary battery data D11' in the buffer S3. According to another embodiment, the controller 130 can list battery data D11 and shadow battery data D11_SH in the data table in chronological order.

[0085] According to one embodiment, the controller 130 can re-store the temporary battery data D11' into the long-term memory S2 of the memory 120. Here, the file size of the temporary battery data D11' can be larger than the file size of the battery data D11. According to another embodiment, the controller 130 can re-store the temporary battery data D11' into partition P1, where the battery data D11 generated at the same generation time as the shadow battery data D11_SH is stored. Therefore, the controller 130 can re-store the temporary battery data D11' while maintaining multiple partitions P1, P2, P3, ... and Pn.

[0086] According to one implementation, the controller 130 can delete the battery data D11 stored in partition P1 before re-storing the temporary battery data D11'. Alternatively, the controller 130 can delete the battery data D11 stored in memory 120 corresponding to the generation time of the shadow battery data D11_SH before re-storing the temporary battery data D11'. Therefore, the controller 130 can reduce the possibility of losing battery data D11 before generating the temporary battery data D11'. Furthermore, the controller 130 can re-store the temporary battery data D11' while maintaining multiple partitions P1, P2, P3, ..., Pn without needing to generate a new partition.

[0087] According to the implementation method, the controller 130 can partition the temporary battery data D11' and re-store the partitioned temporary battery data in partition P1. Here, the controller 130 can use the battery data partitioning method described above to partition the temporary battery data D11'. For example, the controller 130 can partition the temporary battery data D11' into equal-sized partitions. Furthermore, the controller 130 can partition the temporary battery data D11' based on the number of computing nodes in the data management device 100. Additionally, the controller 130 can partition the temporary battery data D11' in time sequence. Details related to partitioning have been referenced. Figure 4 The description is already provided, so it will not be repeated here. Therefore, controller 130 prevents data distribution distortion and improves data processing speed.

[0088] Figure 7 This is a flowchart describing the operation of a battery management device according to one embodiment disclosed herein.

[0089] Figure 7 The operations shown can be performed via Figure 1 and Figure 2 The data management device 100 performs the operation. Each operation in the following embodiments may be performed sequentially, but not necessarily sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. Furthermore, according to the embodiments, at least one of the following operations may be omitted.

[0090] Reference Figure 7 The data management device 100 may include: acquiring battery data including shadow battery data from the vehicle (S101); storing the battery data in each of a plurality of partitions in a memory comprising a plurality of partitions based on the generation time, which is the time when the battery data is generated in the vehicle (S102); generating the battery data and temporary battery data including shadow battery data, the battery data being the battery data stored in the memory corresponding to the generation time of the shadow battery data (S103); and dividing the temporary battery data and re-storing the divided temporary battery data in the partitions of the plurality of partitions corresponding to the generation time (S104).

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

[0092] In operation S102, the data management device 100 may store battery data D1, D2, ..., Dn in multiple partitions P1, P2, P3, ..., Pn of a memory 120, which includes multiple partitions P1, P2, P3, ..., Pn, based on the generation time when the battery data is generated in the vehicle 10 (S102). According to the embodiment, operations S101 to S104 may be executed by the controller 130.

[0093] According to an implementation, the controller 130 may store one of the battery data other than the shadow battery data D11_SH in each of a plurality of partitions P1, P2, P3, ..., and Pn. A portion of the memory 120 comprising the plurality of partitions P1, P2, P3, ..., and Pn may be a long-term memory S2.

[0094] In operation S103, the data management device 100 can generate battery data D11 corresponding to the generation time of the shadow battery data D11_SH and temporary battery data D11' including the shadow battery data in the battery data stored in the memory 120 (S103).

[0095] In operation S104, the data management device 100 can divide the temporary battery data D11' and restore the divided temporary battery data to partition P1, which corresponds to the generation time among multiple partitions (S104).

[0096] Figure 8 This is a block diagram illustrating the hardware configuration of a computing system for performing an operation method of a data management apparatus according to an embodiment disclosed herein.

[0097] Reference Figure 8 The computing system 200 according to one embodiment disclosed herein may include a microcontroller unit MCU 210, a memory 220, an input / output I / F 230, and a communication I / F 240.

[0098] MCU 210 can be used to execute various programs (e.g., battery data collection programs, data analysis programs, and data processing programs) stored in memory 220, process various pieces of information including battery data through these programs, and perform other functions. Figures 1 to 7 The processor of the data management device 100 shown has the functions of this device.

[0099] The memory 220 can store various programs such as battery data collection programs, data analysis programs, and data processing programs.

[0100] Multiple memories 220 can be configured as needed. Memories 220 can be volatile or non-volatile. As volatile memories, memories 220 can use RAM, DRAM, SRAM, etc. As non-volatile memories, memories 220 can use ROM, PROM, EAROM, EPROM, EEPROM, flash memory, etc. The examples of memories 220 described above are illustrative only and are not limited to these examples.

[0101] The input / output I / F 230 can be an interface for connecting input devices (not shown) (such as a keyboard, mouse, or touch panel) and output devices (such as a display (not shown)) to the MCU 210 and allowing the input and output devices to send and receive data with the MCU 210.

[0102] The communication I / F 240 is a component capable of sending and receiving various types of data with a server, and can be any device capable of supporting wired or wireless communication. For example, the data management device 100 can send and receive various pieces of information, including battery data, with a separately provided external server via the communication I / F 240.

[0103] As described above, a computer program according to one embodiment disclosed herein can be implemented and executed, for example, by being recorded in memory 220 and processed by MCU 210. Figure 2 The module that provides the indicated function.

[0104] As stated above, although all components of the embodiments disclosed herein are described as interconnected or operated by interconnection, the embodiments disclosed herein are not necessarily limited to these embodiments. In other words, one or more of the components may operate by selective interconnection without departing from the purpose and scope of the embodiments disclosed herein.

[0105] Furthermore, terms such as “comprising,” “constituting,” or “having” as used above imply that the corresponding component may be inherent unless otherwise specified, and should therefore be understood to further include rather than exclude another component. Unless otherwise defined, all terms, including technical or scientific terms, should be meant in the same way as commonly understood by one of ordinary skill in the art to which the embodiments disclosed herein pertain. Commonly used terms, such as those defined in dictionaries, should be interpreted as consistent with their meaning in the context of the relevant field, and should not be interpreted in an ideal or overly formal sense unless explicitly defined herein.

[0106] The foregoing disclosure illustrates features of several embodiments in a schematic manner to enable those skilled in the art to better understand various aspects of this disclosure. Those skilled in the art will readily understand that this disclosure can serve as a basis for designing or modifying other structures to achieve the same purpose or attain the same advantages of the embodiments introduced herein. Furthermore, those skilled in the art will recognize that such equivalent constructions do not depart from the scope of this disclosure, and that various changes, substitutions, and modifications may be made herein without departing from the scope of this disclosure.

[0107] [Explanation of reference numerals in the attached figures]

[0108] 1: Data Management System

[0109] 10: Vehicles

[0110] 20: Battery Management Device

[0111] 100: Data Management Device

[0112] 110: Data Acquisition Unit

[0113] 120: Memory

[0114] 130: Controller

[0115] 200: Computing System

[0116] 210: MCU

[0117] 220: Memory

[0118] 230: Input / Output I / F

[0119] 240: Communication I / F

Claims

1. A data management device, the data management device comprising: A data acquisition unit configured to acquire battery data from the vehicle, including shadow battery data; The memory includes multiple partitions and stores the battery data; as well as The controller is configured to: Based on the generation time, which is the time when the battery data is generated from the vehicle, the battery data is stored in each of the plurality of partitions; Generate battery data corresponding to the generation time of the shadow battery data from the battery data stored in the memory, and temporary battery data including the shadow battery data; as well as The temporary battery data is divided and re-stored in the partition corresponding to the generation time among the multiple partitions.

2. The data management device according to claim 1, wherein, The shadow battery data is battery data generated at the same generation time as the battery data stored in the memory, and acquired by the data acquisition unit after the stored battery data is stored in the memory.

3. The data management device according to claim 1, wherein, The controller divides the battery data into equal-sized portions and stores them in each of the multiple partitions.

4. The data management device according to claim 3, wherein, The controller partitions the battery data based on the number of computing nodes in the data management device.

5. The data management device according to claim 1, wherein, The controller is configured to: The temporary battery data is stored in a buffer; as well as Before storing the temporary battery data in the memory, delete the battery data stored in the memory that corresponds to the generation time of the shadow battery data.

6. The data management device according to claim 1, wherein, The controller divides the temporary battery data into equal-sized portions and then restores them in a partition corresponding to the generation time.

7. The data management device according to claim 6, wherein, The controller partitions the temporary battery data based on the number of computing nodes in the data management device.

8. The data management device according to claim 1, wherein, The controller divides the temporary battery data in time sequence.

9. A data management method, the data management method comprising the following steps: Obtain battery data from the vehicle, including shadow battery data; Based on the generation time, which is the time when the battery data is generated from the vehicle, the battery data is stored in each of the plurality of partitions in a memory comprising a plurality of partitions; Generate battery data corresponding to the generation time of the shadow battery data from the battery data stored in the memory, and temporary battery data including the shadow battery data; as well as The temporary battery data is divided and re-stored in the partition corresponding to the generation time among the multiple partitions.

10. The data management method according to claim 9, wherein, The shadow battery data is battery data generated at the same generation time as the battery data stored in the memory, and acquired after the stored battery data is stored in the memory.

11. The data management method according to claim 9, wherein, The step of storing the battery data in each of the plurality of partitions includes the following steps: dividing the battery data into equal sizes and storing it in each of the plurality of partitions.

12. The data management method according to claim 11, wherein the data management method comprises the following steps: The battery data is divided based on the number of computing nodes according to the data management method.

13. The data management method according to claim 9, further comprising the following steps: The temporary battery data is stored in a buffer; as well as Before storing the temporary battery data in the memory, delete the battery data stored in the memory that corresponds to the generation time of the shadow battery data.

14. The data management method according to claim 9, wherein, The step of restoring the temporary battery data includes the following steps: dividing the temporary battery data into equal-sized portions and then restoring them in a partition corresponding to the generation time.

15. The data management method according to claim 14, wherein the data management method comprises the following steps: The temporary battery data is divided based on the number of computing nodes according to the data management method.

16. The data management method according to claim 9, wherein, The step of re-storing the temporary battery data includes the following steps: dividing the temporary battery data in time sequence.

Images