TWI709041B - Data storage method and device of mobile terminal - Google Patents

Abstract

The invention provides a data storage method and device for a mobile terminal. The method includes: format conversion of the original data to obtain first data in a preset format; creating a first metadata of the first data; according to the correspondence between the key value and the metadata stored in the cache Determine whether the first data is stored in the database; if the first data is not stored in the database, combine the first data, the first metadata of the first data, and the first data The key value of is saved in the cache; when the preset trigger condition is met, the first data in the cache, the first metadata of the first data, and the key value of the first data that have not been stored in the database are saved To the database. The invention can convert original data into data in a preset format and then store it in a database, can eliminate the structural difference of data, and improve the compatibility of data and the efficiency of data reading and writing.

Description

Data storage method and device of mobile terminal

The present invention relates to the field of storage technology, in particular to a data storage method and device of a mobile terminal.

With the development of technology, more and more mobile terminals have entered people's lives, such as smart phones, tablet computers, etc. Users can load various applications in the mobile terminal, and subsequently, more and more data need to be stored locally in the mobile terminal. The diversified formats and frequent structural changes of these data seriously affect the read and write performance of mobile terminals and reduce the efficiency of application development and operation and maintenance.

In view of this, the present invention provides a data storage method and device.

Specifically, the present invention is achieved through the following technical solutions: a data storage method for a mobile terminal, the method comprising: format conversion of original data to obtain first data in a preset format: creating the first data的 first metadata; Determine whether the first data is stored in the database according to the corresponding relationship between the key value stored in the cache and the metadata; If the first data is not stored in the database, then all The first data, the first metadata of the first data, and the key value of the first data are stored in the cache; when the preset trigger condition is met, the cache is not yet stored in the database The first data, the first metadata of the first data, and the key value of the first data are stored in the database.

Optionally, the judging whether the first data is stored in the database according to the corresponding relationship between the key value stored in the cache and the metadata includes: judging whether the first data is in the cache according to the key value of the first data The second metadata corresponding to the key value is saved; if the second metadata corresponding to the key value is not saved in the cache, it is determined that the first data is not stored in the database.

Optionally, the method further includes: if the second metadata corresponding to the key value is stored in the cache, determining whether the second metadata is the same as the first metadata; if the second metadata is If the metadata is different from the first metadata, it is determined that the first data is not stored in the database; the first metadata, the first metadata of the first data, and the Saving the key value of the first data to the cache includes: updating the second metadata corresponding to the key value of the first data stored in the cache to the first metadata, and saving the first data.

Optionally, the determining whether the second metadata is the same as the first metadata includes: determining whether the hash value of the second metadata is the same as the hash value of the first metadata If they are the same, confirm that the second metadata is the same as the first metadata; if they are not the same, then confirm that the second metadata is different from the first metadata.

Optionally, the preset trigger condition includes: reaching a preset time period and the amount of cached data reaching a preset threshold.

Optionally, it also includes: when reading data, searching the cache according to the key value to find whether the corresponding first data is saved; when the first data corresponding to the key value is not saved in the cache, according to the cache The metadata corresponding to the key value stored in the database obtains the first data corresponding to the key value from a database; the first data is converted into original data and the read result is returned.

A data storage device for a mobile terminal, the device comprising: a first conversion unit that performs format conversion on original data to obtain first data in a preset format; and a metadata creation unit that creates a first data of the first data Metadata; a storage judging unit that judges whether the first data is stored in the database according to the correspondence between the key value stored in the cache and the metadata; the data temporary storage unit does not store the first data in the database In the case of a data, the first data, the first metadata of the first data, and the key value of the first data are stored in the cache; the data storage unit, when the preset trigger condition is met, The first data in the cache, the first metadata of the first data and the key value of the first data that have not been stored in the database are saved in the database.

Optionally, the storage judgment unit specifically judges whether the second metadata corresponding to the key value is stored in the cache according to the key value of the first data, and if the key value correspondence is not stored in the cache If the second metadata is determined, the first data is not stored in the database.

Optionally, the storage determining unit specifically determines whether the second metadata is the same as the first metadata when the second metadata corresponding to the key value is saved in the cache, if If the second metadata is not the same as the first metadata, it is determined that the first data is not stored in the database; the data temporary storage unit specifically stores the first data in the cache The second metadata corresponding to the key value is updated to the first metadata, and the first data is saved.

Optionally, the storage determining unit specifically determines whether the hash value of the second metadata is the same as the hash value of the first metadata, and if they are the same, confirms that the second metadata is the same as the hash value of the first metadata. The first metadata is the same; if they are not the same, it is confirmed that the second metadata is different from the first metadata.

Optionally, the preset trigger condition includes: reaching a preset time period and the amount of cached data reaching a preset threshold.

Optionally, the device further includes: a first reading unit, when reading the data, according to the key value in the cache to find whether the corresponding first data is stored; the second reading unit, when there is no When saving the first data corresponding to the key value, obtain the first data corresponding to the key value from the database according to the metadata corresponding to the key value stored in the cache; the second conversion unit converts the After the first data is converted into the original data, the read result is returned.

It can be seen from the above description that the present invention can convert original data into data in a preset format and then store it in a non-relational database based on Key-Value, which can eliminate data structure differences, improve data compatibility and data The efficiency of reading and writing.

300‧‧‧Data storage device for mobile terminal

301‧‧‧The first conversion unit

302‧‧‧Metadata Creation Unit

303‧‧‧Storage Judgment Unit

304‧‧‧Data Temporary Storage Unit

305‧‧‧Data storage unit

306‧‧‧First reading unit

307‧‧‧Second reading unit

308‧‧‧Second conversion unit

Fig. 1 is a schematic flowchart of a data storage method for a mobile terminal according to an exemplary embodiment of the present invention.

Fig. 2 is a schematic diagram of a process for determining whether the first data is stored in a database according to an exemplary embodiment of the present invention.

Fig. 3 is a schematic diagram showing a structure of a mobile terminal according to an exemplary embodiment.

FIG. 4 is a schematic structural diagram of a data storage device of a mobile terminal according to an exemplary embodiment of the present invention.

The exemplary embodiments will be described in detail here, and examples thereof are shown in the drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings indicate the same or similar elements. The implementation manners described in the following exemplary embodiments do not represent all implementation manners consistent with the present invention. On the contrary, they are only examples of devices and methods consistent with some aspects of the present invention as detailed in the scope of the appended application.

The terms used in the present invention are only for the purpose of describing specific embodiments, and are not intended to limit the present invention. The singular forms of "a", "said" and "the" used in the scope of the present invention and the appended applications are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and/or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

It should be understood that although the terms first, second, third, etc. may be used in the present invention to describe various information, the information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of the present invention, the first information can also be referred to as second information, and similarly, the second information can also be referred to as first information. Depending on the context, the word "if" as used herein can be interpreted as "when" or "when" or "in response to certainty".

Fig. 1 is a schematic flowchart of a data storage method for a mobile terminal according to an exemplary embodiment of the present invention.

Please refer to FIG. 1, the data storage method can be applied to a mobile terminal, and the terminal can include smart devices such as a smart phone, a tablet computer, and a PDA (Personal Digital Assistant, palmtop computer). The data storage method may include the following steps: Step 101: Perform format conversion on the original data to obtain the first data in a preset format.

In this embodiment, the original data is data that needs to be stored in the local database of the mobile terminal, and the original data includes local news, lists, information and other data that each application needs to cache locally. The format of the original data may be text format, XML format, etc.

In this step, after receiving the original data that needs to be stored, the mobile terminal performs format conversion on the original data and converts it into data in a preset format. The preset format can be set by the manager, such as: Binary, decimal, etc. In the present invention, for ease of description, the data obtained after format conversion of the original data is called the first data.

Step 102: Create a first metadata of the first data.

Based on the foregoing step 101, the mobile terminal creates the metadata of the first material after converting the original material into the first material. In the present invention, the created metadata of the first material is called The first metadata.

Step 103: Determine whether the first data is stored in the database according to the corresponding relationship between the key value stored in the cache and the metadata. If the first data is not stored in the database, perform step 104.

In this embodiment, in order to improve the efficiency of reading and writing, a non-relational database based on Key-Value storage can be used as the underlying storage medium of the mobile terminal. The non-relational database includes the format conversion of each original data. After the first data, the first metadata and the key value (Key). The cache of the mobile terminal stores the corresponding relationship between each piece of first metadata and its key value in the non-relational database. In this embodiment, to facilitate distinction, the first metadata stored in the cache is called the second metadata. Specifically, the mobile terminal may save the corresponding relationship between each piece of first metadata and its key value in the non-relational database (hereinafter referred to as the database) to the cache after restarting, such as: memory . The mobile terminal can also, after receiving the original data that needs to be stored in the database, if it is determined that the original data after format conversion is not stored in the database, that is, the first data of the original data is not stored in the database. At the time, the first metadata and its key value corresponding to the original data are saved to the cache, and the specific implementation process can be detailed in the subsequent description.

In this step, the mobile terminal can determine whether the first data is already stored in the database according to the key value of the first data and the corresponding relationship between the key value and the metadata stored in the cache. Wherein, the key value of the first data is also the key value of the original data.

Please refer to FIG. 2, in an alternative embodiment of the present invention, determining whether the first data is stored in the data may include the following steps: Step 1031, determining whether the key is stored in the cache according to the key value of the first data The second metadata corresponding to the value. If the second metadata corresponding to the key value is saved in the cache, step 1032 is executed, and if the second metadata corresponding to the key value is not saved in the cache, step 1033 is executed.

Step 1032: Determine whether the second metadata is the same as the first metadata. If the second metadata is different from the first metadata, step 1033 is executed, and if the second metadata is the same as the first metadata, step 1034 is executed.

Based on the judgment result of the aforementioned step 1031, if the second metadata corresponding to the key value is stored in the cache, it means that the first data corresponding to the key value is stored in the underlying database, but it cannot be known. Whether the first data is the latest version of the first data, so in this step, it can be determined whether the second metadata is the same as the created first metadata.

In this embodiment, it is possible to determine whether the second metadata is the same as the first metadata by comparing each byte of the second metadata with the first metadata . Optionally, it is also possible to determine whether the second metadata is the same as the first metadata by determining whether the hash value of the second metadata is the same as the hash value of the first metadata . Specifically, the second metadata includes the hash value corresponding to the first data stored in the database. In this step, the first data converted in step 101 can be used to calculate the hash value of the first data. The hash value is used as the hash value of the first metadata, and then the calculated hash value is compared with the hash value contained in the second metadata. If they are not the same, it is determined If the second metadata is different from the first metadata, step 1033 is executed; if they are the same, it is determined that the second metadata is the same as the first metadata, and step 1034 is executed.

Step 1033: Determine that the first data is not stored in the database.

In this embodiment, based on the judgment result of the foregoing step 1031, if the second metadata corresponding to the key value is not stored in the cache, it can be determined that the first data is not stored in the database.

Based on the judgment result of the foregoing step 1032, if the second metadata is not the same as the first metadata, it means that the first data with the same key value is stored in the database, but the first data is the same as the previous step The first data converted in 101 is not the same, so the metadata of the two are different. This may be because the first data stored in the data is not the latest data and needs to be updated, so it can also be determined at this time The first data converted in step 101 is not stored in the database.

Step 1034: Determine that the first data has been stored in the database.

Based on the judgment result of the aforementioned step 1032, if the second metadata is the same as the first metadata, it means that the first data with the same key value is stored in the database, and the first data is the same as the aforementioned step 101 The first data obtained by the conversion is the same, and no update is required at this time. The mobile terminal may delete the original data received in the foregoing step 101, the converted first data, and the first metadata created in the foregoing step 102.

In this embodiment, it is possible to confirm whether the received original data has been stored in the database according to the correspondence between the key value stored in the cache and the metadata, which greatly reduces the system consumption caused by accessing the database.

Step 104: Save the first data, the first metadata of the first data, and the key value of the first data in the cache.

Based on the judgment result of the foregoing step 103, if the first data is not stored in the database, the first data needs to be stored in the database. In this embodiment, the first data, the first metadata of the first data, and the key value of the first data may be stored in the cache first.

In view of the two cases where the first data is not stored in the database in step 103, the following two implementation methods can be used in this step: Method one, the second data corresponding to the key value of the first data is not stored in the cache. Metadata. In this case, it is stated that the first data of the original data received in step 101 is not stored in the database, then the mobile terminal can firstly store the first data, the first metadata of the first data, and The key value of the first data is saved in the cache and marked as unsaved. Wherein, the mobile terminal may set an identification bit for marking the storage state for the entire data of the first data, the first metadata of the first data, and the key value of the first data, such as: If the flag bit is 0, it means it is not stored, and the flag bit is 1 it means it has been stored. The mobile terminal can also set a key value list, and store the key value of the first data that is not stored in the data in the key value list. Of course, those skilled in the art can also use other methods to mark whether the data stored in the cache is It has been stored in the database, and the present invention does not impose special restrictions on this.

Manner 2: The second metadata corresponding to the key value of the first data is stored in the cache, but the second metadata is different from the first metadata of the first data. In this case, it means that the first data with the same key value is stored in the database, but the first data is not the latest first data and needs to be updated. The mobile terminal may update the second metadata corresponding to the key value of the first data stored in the cache to the first metadata, and save the first data, so that for a key value, save in the cache There is an up-to-date metadata. In addition, as with method 1, in this method, the updated data will also be marked as unsaved.

Step 105: When a preset trigger condition is met, save the first data in the cache, the first metadata of the first data, and the key value of the first data that have not been stored in the database in the database.

In this embodiment, the mobile terminal can save the first data in the cache, the first metadata of the first data, and the key value of the first data that have not been stored in the database when the preset trigger condition is satisfied. To the database, that is, to save the data marked as unsaved in the cache to the database.

In this embodiment, the trigger condition can be set by an administrator. For example, the trigger condition can be a preset time period, and the trigger condition can also be that the amount of cached data reaches a preset threshold. The present invention does not impose special restrictions on this.

It can be seen from the above description that the present invention can convert original data into data in a preset format and then store it in a non-relational database based on Key-Value, which can eliminate data structure differences, improve data compatibility and data The efficiency of reading and writing.

In another embodiment of the present invention, the mobile terminal can also store the first data with a higher reading frequency in the cache to improve reading efficiency. Therefore, when the mobile terminal receives the data read instruction, it can first search the cache according to the key value carried in the read command to find out whether the corresponding first data is stored, and when the corresponding first data is stored in the cache , The first data in the cache can be converted to the opposite format, converted to the original data, and the read result will be returned. When the first data corresponding to the key value is not saved in the cache, the metadata corresponding to the key value stored in the cache (second metadata) can be searched first, and then the data can be retrieved from the data according to the metadata. The first data corresponding to the key value is acquired from the library, and then the acquired first data is converted in the opposite format, converted into original data, and the read result is returned.

In another embodiment of the present invention, the mobile terminal deletes the first data stored in the cache when a preset condition is met. For example, the first data stored in the cache can be deleted periodically, or the first data can be read in the cache. When the frequency is less than the threshold, the first data stored in the cache is deleted, and the present invention does not impose special restrictions on this.

In addition, according to related technologies, the data storage solution provided by the present invention can also support encrypted storage. For example, after the mobile terminal converts the original data into the first data in the preset format, the first data can be encrypted and stored. . Correspondingly, after the mobile terminal reads the first data, it decrypts the first data, and then converts it to the original data to return the reading result.

Corresponding to the foregoing embodiment of the data storage method of the mobile terminal, the present invention also provides an embodiment of the data storage device of the mobile terminal.

The embodiment of the data storage device of the mobile terminal of the present invention can be applied to the mobile terminal. The device embodiments can be implemented through software, or through hardware or a combination of software and hardware. Taking software implementation as an example, as a logical device, it is formed by reading the corresponding computer program instructions in the non-volatile memory into the memory through the processor of the mobile terminal where it is located. From the perspective of hardware, as shown in FIG. 3, it is a hardware structure diagram of the mobile terminal where the data storage device of the present invention is located, except for the processor, memory, network interface, and non-volatile memory shown in FIG. 3 In addition to the memory, the mobile terminal where the device is located in the embodiment may also include other hardware according to the actual functions of the mobile terminal, which will not be repeated here.

Please refer to FIG. 4 for a schematic structural diagram of a data storage device of a mobile terminal according to an exemplary embodiment of the present invention.

4, the data storage device 300 of the mobile terminal may include: a first conversion unit 301, a metadata creation unit 302, a storage judgment unit 303, a data temporary storage unit 304, a data storage unit 305, and a first read The unit 306, the second reading unit 307, and the second conversion unit 308.

Wherein, the first conversion unit 301 performs format conversion on the original data to obtain first data in a preset format; the metadata creation unit 302 creates the first metadata of the first data; The storage judging unit 303 judges whether the first data is stored in the database according to the correspondence between the key value stored in the cache and the metadata; the data temporary storage unit 304 does not store the first data in the database In the case of the first data, the first data, the first metadata of the first data, and the key value of the first data are stored in the cache; the data storage unit 305 meets the preset requirements When the condition is triggered, the first data in the cache, the first metadata of the first data, and the key value of the first data that have not been stored in the database are saved in the database.

Optionally, the storage judging unit 303 specifically judges whether the second metadata corresponding to the key value is stored in the cache according to the key value of the first data, and if the key value is not stored in the cache Corresponding to the second metadata, it is determined that the first data is not stored in the database.

Optionally, the storage determining unit 303, specifically, when the second metadata corresponding to the key value is stored in the cache, determines whether the second metadata is the same as the first metadata, If the second metadata is different from the first metadata, it is determined that the first data is not stored in the database; the data temporary storage unit 304 specifically stores the first data in the cache. The second metadata corresponding to the key value of the data is updated to the first metadata, and the first data is saved.

Optionally, the storage determining unit 303 specifically determines whether the hash value of the second metadata is the same as the hash value of the first metadata, and if they are the same, confirms that the second metadata and The first metadata is the same; if they are not the same, it is confirmed that the second metadata is different from the first metadata.

Optionally, the preset trigger condition includes: reaching a preset time period and the amount of cached data reaching a preset threshold.

The first reading unit 306 searches for the corresponding first data in the cache according to the key value when reading the data; the second reading unit 307, when the key is not saved in the cache Value corresponding to the first data, the first data corresponding to the key value is obtained from the database according to the metadata corresponding to the key value stored in the cache; the second conversion unit 308 converts the first data One data is converted into original data and the read result is returned.

For the implementation process of the functions and roles of each unit in the above-mentioned device, please refer to the implementation process of the corresponding steps in the above-mentioned method for details, which will not be repeated here.

For the device embodiment, since it basically corresponds to the method embodiment, the relevant part can refer to the part of the description of the method embodiment. The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in One place, or it can be distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the objectives of the solution of the present invention. Those of ordinary skill in the art can understand and implement it without creative work.

The above are only preferred embodiments of the present invention and are not intended to limit the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the present invention Within the scope of protection.

Claims (10)

A data storage method for a mobile terminal, wherein the method includes: format conversion of original data to obtain first data in a preset format; creating a first metadata of the first data; according to the key saved in the cache The corresponding relationship between the value and the metadata determines whether the first data is stored in the database; if the first data is not stored in the database, then the first data, the first metadata of the first data, and the The key value of the first data is saved in the cache; when the preset trigger condition is met, the first data in the cache, the first metadata of the first data, and the first data that have not been stored in the database The key value is saved in the database; the judgment of whether the first data is stored in the database according to the corresponding relationship between the key value saved in the cache and the metadata includes: judging whether the first data is in the cache according to the key value of the first data Whether the second metadata corresponding to the key value is saved; if the second metadata corresponding to the key value is saved in the cache, determine whether the second metadata is the same as the first metadata; if If the second metadata is different from the first metadata, it is determined that the first data is not stored in the database; the first data, the first metadata of the first data, and the first data The key value of is saved to the cache, including: The second metadata corresponding to the key value storing the first data in the cache is updated to the first metadata, and the first data is saved. The method according to item 1 of the scope of patent application, further comprising: if the second metadata corresponding to the key value is not stored in the cache, determining that the first data is not stored in the database. The method according to item 1 of the scope of patent application, wherein the determining whether the second metadata is the same as the first metadata includes: determining whether the hash value of the second metadata is the same as that of the first metadata Whether the hash values of the data are the same, if they are the same, confirm that the second metadata is the same as the first metadata; if they are not the same, then confirm that the second metadata is different from the first metadata. The method according to item 1 of the scope of patent application, wherein the preset trigger condition includes: reaching a preset time period and the amount of cached data reaching a preset threshold. The method according to item 1 of the scope of patent application, wherein the method further includes: when reading the data, according to the key value in the cache to find whether the corresponding first data is saved; when the key is not saved in the cache When the value corresponds to the first data, the first data corresponding to the key value is obtained from the database according to the metadata corresponding to the key value stored in the cache; the first data is converted into original data and then sent back to read result. A data storage device for a mobile terminal, wherein the device package Including: the first conversion unit, which converts the format of the original data to obtain the first data in the preset format; the metadata creation unit, which creates the first metadata of the first data; the storage judgment unit, according to the cache The corresponding relationship between the saved key value and the metadata determines whether the first data is stored in the database; the data temporary storage unit, when the first data is not stored in the database, the first data and the first data The first metadata and the key value of the first data are stored in the cache; the data storage unit, when the preset trigger condition is met, will retrieve the first data and the first data that have not been stored in the database. The first metadata of the data and the key value of the first data are stored in the database; the storage judgment unit specifically judges whether the second relay corresponding to the key value is stored in the cache according to the key value of the first data Data, when the second metadata corresponding to the key value is stored in the cache, it is determined whether the second metadata is the same as the first metadata, and if the second metadata is the same as the first metadata If the data is not the same, it is determined that the first data is not stored in the database; the data temporary storage unit specifically updates the second metadata corresponding to the key value of the first data stored in the cache to the first metadata , And save the first information. The device according to item 6 of the scope of patent application, wherein the storage judgment unit does not store the key corresponding to the key in the cache. Second, it is determined that the first data is not stored in the database. The device according to item 6 of the scope of patent application, wherein the storage determination unit specifically determines whether the hash value of the second metadata is the same as the hash value of the first metadata, and if they are the same, confirms the first metadata. The second metadata is the same as the first metadata; if they are not the same, it is confirmed that the second metadata is different from the first metadata. The device according to item 6 of the scope of patent application, wherein the preset trigger condition includes: reaching a preset time period and the amount of cached data reaching a preset threshold. The device according to item 6 of the scope of patent application, wherein the device further includes: a first reading unit, when reading data, searches the cache according to the key value to find whether the corresponding first data is stored; second The reading unit, when the first data corresponding to the key value is not stored in the cache, obtain the first data corresponding to the key value from the database according to the metadata corresponding to the key value stored in the cache; The conversion unit converts the first data into original data and then returns the read result.

Images