Data management method of storage device and electronic device

Abstract

The application discloses a data management method of a storage device and an electronic device, and belongs to the technical field of storage. The data management method of the storage device comprises the following steps: when the life of a keeping table area is less than the life of a keeping data area, writing data of a data cache area into a nonvolatile memory, and entering a sleep mode of the storage device; when the life of the keeping table area is greater than the life of the keeping data area, judging whether the size of the data of the data cache area reaches a lower brushing threshold value; if the size of the data reaches the lower brushing threshold value, writing the data into the nonvolatile memory, and entering the sleep mode of the storage device; if the size of the data does not reach the lower brushing threshold value, saving the data into the keeping data area, recording boundary mark information of the data in the keeping data area, writing system management data tables to be migrated in the keeping table area into the nonvolatile memory, and entering the sleep mode of the storage device. The data management method of the storage device and the electronic device can prolong the service life of the storage device.

Description

Technical Field

[0001] This invention relates to the field of storage technology, and in particular to a data management method and electronic device for storage devices. Background Technology

[0002] In storage devices, retention areas are typically configured to prevent data loss during low-power modes. When a storage device needs to enter a low-power sleep mode, all user data in the data cache must be flushed to non-volatile memory. If the storage device frequently enters and exits low-power modes, repeated small data flushing operations will quickly consume the limited erase / write lifespan of the non-volatile memory, leading to a reduction in the overall lifespan of the storage device. Summary of the Invention

[0003] The purpose of this invention is to provide a data management method and electronic device for storage devices, which can extend the service life of storage devices.

[0004] This invention provides a data management method for a storage device, comprising at least: The storage device's retention area is divided into a retention data area and a retention table area; When the lifetime of the holding table area is less than the lifetime of the holding data area, the data in the data cache area is written to the non-volatile memory, and the storage device enters a hibernation mode. When the lifetime of the hold table area is greater than or equal to the lifetime of the hold data area, it is determined whether the data size of the data cache area has reached the refresh threshold; If the data size in the data buffer reaches the refresh threshold, the data in the data buffer is written to the non-volatile memory, and the storage device enters a sleep mode; and If the data size of the data cache does not reach the refresh threshold, the data in the data cache is saved to the hold data area, the boundary marker information of the data in the hold data area is recorded, and the system management data table to be migrated in the hold table area is written to the non-volatile memory, and the storage device enters hibernation mode.

[0005] In one embodiment of the present invention, the boundary marking information includes a start address, an end address, a valid length, and a checksum.

[0006] In one embodiment of the present invention, if the data size of the data cache does not reach the refresh threshold, the data management method of the storage device further includes the following step: updating the flag bit of the hold storage area.

[0007] In one embodiment of the present invention, when the data in the data cache area is saved to the holding data area, the storage space is determined according to the start address and end address of the data writing, and the system management data table located in the storage space in the holding table area is used as the system management data table to be migrated.

[0008] In one embodiment of the present invention, the data management method of the storage device further includes the following steps: when the lifetime of the storage device reaches a threshold, compressing the block management table of the retention table area, and dynamically allocating the storage space released by the retention table area to the retention data area.

[0009] In one embodiment of the present invention, the compression of the block management table is to compress the number of block erases, the number of block reads, and the block access timestamps.

[0010] In one embodiment of the present invention, the data management method of the storage device further includes the following steps: when the lifetime of the data retention area reaches a first threshold and the lifetime of the retention table area reaches a second threshold, the data in the data cache area is divided into hot data and cold data.

[0011] In one embodiment of the present invention, after dividing the data in the data cache into hot data and cold data, the data management method of the storage device further includes the following steps: If the data in the data cache is cold data, determine whether the lifetime of the hold table is less than the lifetime of the hold data area; and If the data in the data cache is hot data, the data in the data cache is saved to the holding data area, the boundary marker information of the data in the holding data area is recorded, the system management data table to be migrated in the holding table area is compressed, and the storage space released by the holding table area is dynamically allocated to the holding data area, and the storage device enters hibernation mode.

[0012] In one embodiment of the present invention, the hot data is data whose mapping relationship has been written more than a preset threshold.

[0013] The present invention also provides an electronic device, the electronic device comprising: Memory, which stores computer programs; and The processor runs the computer program to implement the data management method for the storage device as described in any one of the above descriptions.

[0014] In summary, this invention provides a data management method and electronic device for a storage device. By dynamically dividing the storage area into a hold data area and a hold table area, and dynamically selecting a data temporary storage or flushing strategy based on the comparison of the lifespans of the hold data area and the hold table area and the overall lifespan status of the storage device, the overall lifespan of the storage device can be extended. By temporarily storing data that has not reached the flushing threshold in the hold data area, write amplification can be significantly reduced, extending the lifespan of the storage device. By compressing the block management table when the overall lifespan of the storage device approaches the threshold, and reallocating the freed space to the hold data area for temporary storage of more data, the overall lifespan of the storage device can be extended. By dividing the data into hot data and cold data when the lifespan of the hold data area reaches a first threshold and the lifespan of the hold table area reaches a second threshold, and temporarily storing the hot data in the hold data area while compressing the block management table and reallocating the freed space to the hold data area, the limited remaining write cycles can be reserved for more hot data, extending the lifespan of the storage device.

[0015] Of course, any product implementing this invention does not necessarily need to achieve all of the advantages described above at the same time. Attached Figure Description

[0016] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0017] Figure 1 This is a schematic diagram of a data management method for a storage device in one embodiment.

[0018] Figure 2 This is a schematic diagram illustrating the specific steps of a data management method for a storage device in one embodiment.

[0019] Figure 3 This is a schematic diagram of an electronic device in one embodiment.

[0020] Label Explanation: 11. Processor; 12. Memory. Detailed Implementation

[0021] To facilitate understanding of this application, a more complete description will be provided below with reference to the accompanying drawings. Preferred embodiments of this application are shown in the drawings. However, this application can be implemented in many different forms and is not limited to the embodiments described herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the disclosure of this application.

[0022] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein in the specification of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application.

[0023] In the description of this invention, it should be understood that the terms "center," "upper," "lower," "front," "rear," "left," and "right," etc., indicating orientation or positional relationships, are based on the orientation or positional relationships shown in the accompanying drawings and are only for the convenience of describing the invention and simplifying the description, and do not indicate or imply that the device or component referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of the invention. Similarly, the terms "high" and "low," indicating degree, are only for the convenience of describing the invention and simplifying the description, and do not indicate or imply that the device or component referred to must have a high or low position, and therefore should not be construed as a limitation of the invention. Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance.

[0024] In storage devices, it is crucial to ensure that the internal data in the storage area is not lost when the storage device enters hibernation, standby, or other low-power modes. Currently, metadata such as block management tables and address mapping tables are typically placed in this area to ensure rapid recovery of the storage state after system wake-up. Simultaneously, before the storage device enters a low-power hibernation mode, all user data in the data cache needs to be flushed to non-volatile memory to prevent data loss. However, when the amount of user data to be flushed is small, the non-volatile memory still needs to perform a complete page programming operation, resulting in the actual amount of physical data written being much larger than the effective data amount, causing write amplification. In scenarios where the storage device needs to frequently enter and exit low-power modes, repeated small data flushing operations will rapidly consume the limited erase / write lifespan of the non-volatile memory, significantly reducing the overall lifespan of the storage device. Therefore, this invention provides a data management method and electronic device for storage devices, which can extend the lifespan of storage devices.

[0025] Please see Figure 1 As shown, the present invention provides a data management method for a storage device, which includes at least steps S110 to S150.

[0026] Step S110: Divide the storage area of ​​the storage device into a storage data area and a storage table area.

[0027] Step S120: Determine whether the lifetime of the hold table area is less than the lifetime of the hold data area. If the lifetime of the hold table area is less than the lifetime of the hold data area, proceed to step S130. If the lifetime of the hold table area is greater than or equal to the lifetime of the hold data area, proceed to step S140.

[0028] Step S130: Write the data in the data buffer to the non-volatile memory, and the storage device enters hibernation mode.

[0029] Step S140: Determine whether the data size in the data buffer has reached the flush threshold. If the data size in the data buffer has reached the flush threshold, proceed to step S130. If the data size in the data buffer has not reached the flush threshold, proceed to step S150.

[0030] Step S150: Save the data in the data cache area to the holding data area, record the boundary marking information of the data in the holding data area, and write the system management data table to be migrated in the holding table area to the non-volatile memory. The storage device enters hibernation mode.

[0031] Please see Figure 1 As shown, in one embodiment of the present invention, in step S110, the holding storage area of ​​the storage device is dynamically divided into a holding data area and a holding table area. The holding data area is used to temporarily store data in the data cache area, and the holding table area is used to store system management data tables necessary for operation, such as address mapping tables, block management tables, etc. A flag bit in the holding storage area is set to indicate the status of the holding table area.

[0032] Please see Figure 2 As shown, in one embodiment of the present invention, when the lifetime of the retention table area is less than the lifetime of the retention data area, the data management method of the storage device further includes updating the flag bit of the retention storage area. Specifically, it includes step S131.

[0033] Step S131: Update the flags of the storage area.

[0034] Please see Figure 2 As shown, in one embodiment of the present invention, in steps S130 and S131, when the lifetime of the hold table is less than the lifetime of the hold data area, it indicates that the hold table is relatively more worn, and continuing to write to the hold table will accelerate its failure. Therefore, the data in the data buffer is directly flushed to the non-volatile memory. During this process, the contents of the hold table remain unchanged, and no address mapping or management information is updated. The flag bit of the hold storage area is also updated to indicate that the hold table is in an unupdated state. When the storage device is woken up, the system management data table of the hold table is updated according to the flag bit, and then the data in the non-volatile memory is read into the data buffer. Through this method, the lifetime of the hold table is extended, and the recoverability of the data after wake-up is ensured.

[0035] Please see Figure 1As shown, in one embodiment of the present invention, in steps S140 and S150, the flush threshold is the size of a physical write page in the non-volatile memory, specifically, the flush threshold is, for example, 32K. When the lifetime of the hold table area is greater than or equal to the lifetime of the hold data area, if it is determined that the data size in the data buffer is less than the size of a physical write page, the data is temporarily stored in the hold data area. At the same time, the boundary marker information of the data in the hold data area is recorded. The boundary marker information includes the start address, end address, effective length, and checksum, which are used to accurately locate and recover the data during subsequent wake-up. The storage space is determined according to the start address and end address of the data write, and the system management data table located in the storage space in the hold table area is taken as the system management data table to be migrated. Therefore, the system management data table to be migrated in the hold table area is flushed to the non-volatile memory. If it is determined that the data size in the data buffer is greater than the size of a physical write page, the data in the data buffer area is directly written to the non-volatile memory. At this time, the flag bit of the hold storage area is not updated, because a conventional write process is adopted, and no special marking is required. This mechanism reduces the write amplification factor, protecting the erase / write life of non-volatile memory.

[0036] Please see Figure 2 As shown, in one embodiment of the present invention, when the data size of the data cache does not reach the flush threshold, the data management method of the storage device further includes updating the flag bit of the retention storage area. Specifically, this includes step S151.

[0037] Step S151: Update the flags of the storage area.

[0038] Please see Figure 2 As shown, in one embodiment of the present invention, in step S151, the flag bit of the storage area is used to indicate that when the storage device wakes up, the system management data table in the storage area and the non-volatile memory needs to be merged and loaded to ensure that the system management data table is consistent before and after hibernation.

[0039] Please see Figure 2As shown, in one embodiment of the present invention, after executing steps S151 and S150, when the storage device is woken up, the system management data table in the non-volatile memory is first loaded into the holding table area according to the flag bit. Then, according to the start address and end address in the boundary marker information, the data is read from the holding data area into the data buffer area. Next, it is verified whether bit flipping or data corruption occurred during the low-power sleep period. The checksum of the data is recalculated, and the recalculated checksum is compared with the previously recorded checksum. If the recalculated checksum matches the previously recorded checksum, the data recovery is considered successful. If the recalculated checksum does not match the recorded checksum, it indicates that the data was corrupted during the sleep period. The corresponding data recovery process is executed, such as rereading, ECC error correction, or restoration from backup, to ensure the absolute security and accuracy of the data during dynamic reuse.

[0040] Please see Figure 2 As shown, in one embodiment of the present invention, before executing step S120, the data management method for the storage device further includes determining whether the lifetime of the storage device has reached a threshold. If the lifetime of the storage device has reached the threshold, the block management table of the retention table area is compressed, and the released storage space is allocated to the retention data area. Then, it is determined whether the lifetime of the retention data area has reached a first threshold and whether the lifetime of the retention table area has reached a second threshold. If the lifetime of the retention data area has reached the first threshold and the lifetime of the retention table area has reached the second threshold, the data in the data cache area is divided into hot data and cold data. If the lifetime of the storage device has not reached the threshold, it is directly determined whether the lifetime of the retention data area has reached the first threshold and whether the lifetime of the retention table area has reached the second threshold, and then subsequent operations continue. Specifically, this includes steps S111 to S114.

[0041] Step S111: Determine whether the storage device's lifespan has reached the threshold. If the storage device's lifespan has reached the threshold, proceed to step S112. If the storage device's lifespan has not reached the threshold, proceed to step S113.

[0042] Step S112: Compress the block management table of the holding table area and dynamically allocate the storage space released by the holding table area to the holding data area.

[0043] Step S113: Determine whether the lifetime of the data area has reached the first threshold and whether the lifetime of the table area has reached the second threshold. If the lifetime of the data area has reached the first threshold and the lifetime of the table area has reached the second threshold, proceed to step S114. If the lifetime of the data area has not reached the first threshold or the lifetime of the table area has not reached the second threshold, proceed to step S120.

[0044] Step S114: Divide the data in the data cache into hot data and cold data.

[0045] Please see Figure 2 As shown, in one embodiment of the present invention, in steps S111 to S112, the block management table is used to record the number of erases, the number of reads, and the access timestamp for each physical block. When the overall lifespan of the storage device has reached a threshold, such as 98% of the initial lifespan, the block management table of the retention table area can be compressed, and the storage space released by the compression can be dynamically allocated to the retention data area. Specifically, the compression of the block management table is to compress the number of erases, the number of reads, and the access timestamp of the blocks. In this embodiment, for example, only half of the physical blocks with the largest number of erases are compressed. The total number of physical blocks is, for example, 2000. Each block's erase count, read count, and access timestamp each occupy 4 bytes, so each block's table entry occupies 12 bytes, and the entire table occupies 24000 bytes. During compression, all blocks are first sorted from largest to smallest erase count, and the top 1000 blocks with the largest erase count are selected as compression targets. For these 1000 compressed blocks, instead of retaining individual 12-byte records for each block, the average number of erases, average number of reads, and average access timestamps of these 1000 blocks are calculated, using 12 bytes to represent the overall statistical characteristics of these 1000 blocks. Simultaneously, a 1000-bit bitmap table (250 bytes) is constructed, with each bit indicating whether the corresponding block has been compressed (e.g., 1 for compressed, 0 for uncompressed). Therefore, the total space occupied after compression is 12262 bytes, compared to 24000 bytes before compression, freeing up 11738 bytes of storage space, achieving a compression rate of nearly 50%. This mechanism achieves ultimate storage space reuse and on-demand elastic allocation at the end of the device's lifespan.

[0046] Please see Figure 2 As shown, in one embodiment of the present invention, in steps S113 to S114, when it is detected that the lifetime of the data retention area has reached a first threshold and the lifetime of the table retention area has reached a second threshold, it indicates that both areas have entered the end of their lifespan, and continuing to write data to either area will accelerate their failure. Therefore, the data in the data cache is divided into hot data and cold data. In this embodiment, the data in the data cache is divided into hot data and cold data based on characteristics such as the data access frequency, modification frequency, or number of mapping relationship updates. Hot data is data whose mapping relationship write count exceeds a preset threshold, such as file system metadata and log records. Cold data is data whose mapping relationship write count does not exceed the preset threshold, such as archived user files and static configuration information. By classifying and processing hot data and cold data, optimal utilization of storage resources can be achieved, extending the overall effective working time of the device. In this embodiment, the first threshold and the second threshold can be configured according to the actual storage medium parameters.

[0047] Please see Figure 2As shown, in one embodiment of the present invention, after dividing the data in the data cache into hot data and cold data, the data management method of the storage device further includes, when the data is hot data, before the storage device enters hibernation, writing the data into the holding data area, compressing the system management data table to be migrated in the holding table area, and allocating the storage space released by the holding table area to the holding data area. When the storage device is woken up, the system management data table is decompressed and loaded, and the data is read into the data cache area. Specifically, this includes steps S115 to S116.

[0048] Step S115: Determine whether the data in the data cache is cold data. If the data in the data cache is cold data, proceed to step S120. If the data in the data cache is hot data, proceed to step S116.

[0049] Step S116: Save the data in the data cache area to the holding data area, record the boundary marking information of the data in the holding data area, compress the system management data table to be migrated in the holding table area, and dynamically allocate the storage space released by the holding table area to the holding data area. The storage device enters hibernation mode.

[0050] Please see Figure 2 As shown, in one embodiment of the present invention, in step S116, for data determined to be hot data, even if the amount of hot data in the data cache already meets the size of a physical write page, the hot data is still written to the holding data area. This interception mechanism avoids frequent erasure and writing of frequently updated hot data in non-volatile memory, thereby reducing the overall number of erasure and write operations of non-volatile memory. Since writing hot data to the holding data area will occupy the storage space originally belonging to the holding table area, it will lead to insufficient storage space for the system management data table. To resolve this space conflict, the system management data table occupied by the holding table area is compressed to release storage space. By dynamically allocating this compressed and released storage space to the holding data area, the physical boundary of the holding data area is expanded, and the lifespan of the holding data area is extended.

[0051] Please see Figure 2 As shown, in one embodiment of the present invention, after executing step S116, when the storage device is woken up, the system management data table is first decompressed and loaded into the holding table area according to the flag bit. Then, according to the start address and end address in the boundary marker information, the data is read from the holding data area into the data cache area. Next, the checksum of the data is recalculated, and the recalculated checksum is compared with the previously recorded checksum. If the recalculated checksum matches the previously recorded checksum, the data recovery is considered successful. If the recalculated checksum does not match the recorded checksum, it indicates that the data was corrupted during hibernation, and the corresponding data recovery process is executed, such as rereading, ECC error correction, or restoration from backup.

[0052] Please see Figure 3 As shown, the present invention provides an electronic device, which includes a processor 11, a memory 12, and a computer program stored on the memory 12 and executable on the processor 11. The processor 11 executes a data management method for the aforementioned memory device.

[0053] Please see Figure 3 As shown, the memory 12 includes at least one type of readable storage medium, including flash memory, portable hard drive, multimedia card, card-type memory (e.g., SD or DX memory), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 12 can be an internal storage unit of an electronic device, such as a portable hard drive. In other embodiments, the memory 12 can be an external storage device of the electronic device, such as a plug-in portable hard drive, Smart Media Card (SMC), Secure Digital (SD) card, Flash Card, etc. Furthermore, the memory 12 can include both internal and external storage units of the electronic device. The memory 12 can be used not only to store application software and various types of data installed on the electronic device, but also to temporarily store data that has been output or will be output.

[0054] Please see Figure 3 As shown, in some embodiments, the processor 11 can be composed of integrated circuits, such as a single packaged integrated circuit or multiple integrated circuits packaged with the same or different functions, including combinations of one or more central processing units, microprocessors, digital processing chips, graphics processors, and various control chips. The processor 11 is the control unit of the electronic device, connecting various components of the entire electronic device through various interfaces and lines. It executes programs or modules stored in the memory 12 and calls data stored in the memory 12 (such as programs for data management methods of storage devices) to perform various functions of the electronic device and process data.

[0055] In some embodiments, the processor 11 executes the operating system of the electronic device and various installed applications. The processor 11 executes the applications to implement the steps in the data management method for the storage device described above.

[0056] In some embodiments, the computer program may be divided into one or more modules, one or more of which are stored in the memory 12 and executed by the processor 11 to perform the present invention. The one or more modules may be a series of computer program instruction segments capable of performing a specific function, which describe the execution process of the computer program in an electronic device.

[0057] This invention provides a data management method and electronic device for a storage device. By dynamically dividing the storage area into a hold data area and a hold table area, and dynamically selecting a data pausing or flushing strategy based on a comparison of the lifespans of the hold data area and the hold table area and the overall lifespan of the storage device, the overall lifespan of the storage device can be extended. By pausing data that has not reached the flushing threshold in the hold data area, write amplification can be significantly reduced, extending the lifespan of the storage device. By compressing the block management table when the overall lifespan of the storage device approaches the threshold, the freed storage space is reallocated to the hold data area for pausing more data, extending the overall lifespan of the storage device. By dividing the data into hot data and cold data when the lifespan of the hold data area reaches a first threshold and the lifespan of the hold table area reaches a second threshold, and pausing the hot data in the hold data area while compressing the system management data table and reallocating the freed storage space to the hold data area, the limited remaining write cycles can be reserved for more hot data, extending the lifespan of the storage device.

[0058] The embodiments of the present invention disclosed above are merely illustrative of the invention. The embodiments do not exhaustively describe all details, nor do they limit the invention to the specific implementations described. Clearly, many modifications and variations can be made based on the content of this specification. This specification selects and specifically describes these embodiments to better explain the principles and practical applications of the invention, thereby enabling those skilled in the art to better understand and utilize the invention. The invention is limited only by the claims and their full scope and equivalents.

Claims

1. A data management method for a storage device, characterized in that, The data management method for the storage device includes at least the following: The storage device's retention area is divided into a retention data area and a retention table area; When the lifetime of the holding table area is less than the lifetime of the holding data area, the data in the data cache area is written to the non-volatile memory, and the storage device enters a hibernation mode. When the lifetime of the hold table area is greater than or equal to the lifetime of the hold data area, it is determined whether the data size of the data cache area has reached the refresh threshold; If the data size in the data buffer reaches the refresh threshold, the data in the data buffer is written to the non-volatile memory, and the storage device enters a sleep mode; and If the data size of the data cache does not reach the refresh threshold, the data in the data cache is saved to the hold data area, the boundary marker information of the data in the hold data area is recorded, and the system management data table to be migrated in the hold table area is written to the non-volatile memory, and the storage device enters hibernation mode.

2. The data management method for a storage device according to claim 1, characterized in that, The boundary marking information includes the start address, end address, effective length, and checksum.

3. The data management method for a storage device according to claim 1, characterized in that, If the data size of the data cache does not reach the refresh threshold, the data management method of the storage device further includes the following step: updating the flag bit of the hold storage area.

4. The data management method for a storage device according to claim 1, characterized in that, When the data in the data cache is saved to the holding data area, the storage space is determined according to the start address and end address of the data writing, and the system management data table located in the storage space in the holding table area is taken as the system management data table to be migrated.

5. The data management method for a storage device according to claim 1, characterized in that, The data management method for the storage device further includes the following steps: when the lifespan of the storage device reaches a threshold, compressing the block management table of the retention table area, and dynamically allocating the storage space released by the retention table area to the retention data area.

6. The data management method for a storage device according to claim 5, characterized in that, The compression of the block management table involves compressing the number of block erases, the number of block reads, and the block access timestamps.

7. The data management method for a storage device according to claim 1, characterized in that, The data management method for the storage device further includes the following steps: when the lifetime of the data retention area reaches a first threshold and the lifetime of the retention table area reaches a second threshold, the data in the data cache area is divided into hot data and cold data.

8. The data management method for a storage device according to claim 7, characterized in that, After dividing the data in the data cache into hot data and cold data, the data management method of the storage device further includes the following steps: If the data in the data cache is cold data, determine whether the lifetime of the hold table is less than the lifetime of the hold data area; and If the data in the data cache is hot data, the data in the data cache is saved to the holding data area, the boundary marker information of the data in the holding data area is recorded, the system management data table to be migrated in the holding table area is compressed, and the storage space released by the holding table area is dynamically allocated to the holding data area, and the storage device enters hibernation mode.

9. The data management method for a storage device according to claim 7, characterized in that, The hot data refers to data whose mapping relationship has been written more than a preset threshold.

10. An electronic device, characterized in that, The electronic device includes: Memory, which stores computer programs; and The processor runs the computer program to implement the data management method for the storage device as described in any one of claims 1 to 9.

Images