Data management apparatus and data management method

Abstract

A data management apparatus and a data management method are provided. The data management method includes providing external version information to a first controller, wherein the external version information corresponds to a data portion stored in a storage circuit of a local device, and the data portion corresponds to local version information; and generating, by the first controller, an update trigger signal according to the external version information and the local version information, and triggering an application to update the data portion through the update trigger signal.

Description

Technical Field

[0001] This invention relates to a data management device and a data management method, and more particularly to a data management device and a data management method for updating data. Background Technology

[0002] In today's information age, with information rapidly changing, updating the data stored in electronic devices is essential. However, updating data in storage circuits like read-only memory (ROM) often requires manual execution of applications, causing considerable inconvenience for users. Therefore, developing data management devices and methods that can automatically update data is indispensable. Summary of the Invention

[0003] This invention relates to a data management device and a data management method that can automatically update storage circuits, such as data in read-only memory (ROM), in a timely manner.

[0004] According to an embodiment of the present invention, a data management method includes: providing external version information to a first controller, wherein the external version information corresponds to a data portion stored in the storage circuit of the local device, and the data portion corresponds to local version information; and the first controller generates an update trigger signal based on the external version information and the local version information, thereby triggering an application to update the data portion through the update trigger signal.

[0005] According to an embodiment of the present invention, a data management device includes a first controller and a storage circuit. The first controller is coupled to a storage device to receive external version information. The storage circuit includes a data portion and local version information. The external version information and the local version information correspond to the data portion. The first controller is further configured to generate an update trigger signal based on the external version information and the local version information, and to trigger an application to update the data portion by means of the update trigger signal.

[0006] Based on the above, the data management device and data management method of the present invention can automatically perform data updates in a timely manner when receiving external version information from an external storage device through the interaction between the control device and the program group, without the need for manual data updates. Attached Figure Description

[0007] Figure 1 A schematic diagram illustrating the data management mechanism of various embodiments of the present invention is shown.

[0008] Figure 2 A schematic diagram illustrating a data management device according to an embodiment of the present invention and its applicable external storage device is shown.

[0009] Figure 3 This diagram illustrates the operation of a data management method according to an embodiment of the present invention.

[0010] Figure 4 A flowchart illustrating a data management method according to an embodiment of the present invention is shown. Detailed Implementation

[0011] Reference will now be made in detail to exemplary embodiments of the invention, examples of which are illustrated in the accompanying drawings. Wherever possible, the same element symbols are used in the drawings and description to denote the same or similar parts.

[0012] Please refer to the following: Figure 1 , Figure 1 Schematic diagrams illustrating data management mechanisms of various embodiments of the present invention are shown. For example... Figure 1 As shown, the data management mechanism of the present invention automatically updates data through the interaction between the control device 110 and the program group 120. The control device 110 may include at least one controller. Furthermore, the program group 120 may include at least an application program 121 for performing data updates. In some embodiments, the program group 120 may also include a basic input / output system (BIOS) 122 and / or an operating system (OS) 123.

[0013] Please refer to the following as well. Figure 1 and Figure 2 , Figure 2 This diagram illustrates a data management device 200 according to an embodiment of the present invention and its applicable external storage device SD. The data management device 200 can be used as a local device. The data management device 200 includes a controller 210 and a storage circuit 220. The controller 210 and the storage circuit 220 are coupled to each other. The controller 210 is also used to couple to the storage device SD. In this embodiment, the storage device SD can be electrically connected to the controller 210 in any form without any limitation. For example, the storage device SD can be a portable solid state drive (PSSD) or a pen drive. As another example, the storage device SD can also be a cloud drive. The storage device SD has external version information of the data portion DP stored in the storage circuit 220 of the local device. Furthermore, in some embodiments, the storage device SD also contains data identified by the external version information. In this embodiment of the present invention, the controller 210 obtains the external version information of the data portion DP stored in the storage circuit 220 by reading the storage device SD.

[0014] Furthermore, in some embodiments, the storage circuit 220 stores not only the data portion DP, but also local version information corresponding to the stored data portion DP, wherein the local version data is used to identify the data portion DP. In other embodiments, the controller 210 itself has a storage function, and the local version information is stored in the controller 210 instead of the storage circuit 220. Additionally, in some embodiments, when the creation time of data identified by external version information is later than the creation time of the data portion DP, the data identified by the external version information is used as update data to replace the data portion DP.

[0015] On the other hand, the storage circuit 220 may also include other data besides the aforementioned data portion DP. Specifically, the storage circuit 220 may be random-access memory (RAM), ROM, or an internal hard disk, without any limitations.

[0016] Furthermore, in operation, the controller 210 can generate an update trigger signal based on external version information and local board information, wherein the update trigger signal is used to trigger... Figure 1 Application 121 in the middle is used to update the above data part DP.

[0017] Furthermore, in this embodiment, the data management device 200 may also include an update device UDH. The update device UDH is used to perform a data update operation in response to the aforementioned update trigger signal. Specifically, the update device UDH includes a controller 230. The controller 230 is coupled to the controller 210. In operation, in response to the update trigger signal, the controller 230 transmits a data update command to the application program 121.

[0018] Furthermore, in this embodiment, the updating device UDH may also include a processor 240. The processor 240 is coupled to the controller 230. The processor 240 is used to drive... Figure 1 The program group 120 transmits data update commands from the controller 230 and updates the data portion DP. For example, the processor 240 drives the basic input / output system 122 to transmit data update commands to the operating system 123. For example, the processor 240 drives the operating system 123 to transmit data update commands to the application program 121. For example, the processor 240 drives the application program 121 to update the aforementioned data portion DP in response to the data update commands.

[0019] In some implementations, controllers 210 and 230 can be constructed from any form of digital circuitry without specific limitations. Processor 240 can be a central processing unit (CPU), micro control unit (MCU), microprocessor, digital signal processor (DSP), programmable controller, application-specific integrated circuit (ASIC), graphics processing unit (GPU), arithmetic logic unit (ALU), complex programmable logic device (CPLD), field-programmable gate array (FPGA), or other similar components without certain limitations.

[0020] Incidentally, the controller 210 and storage circuit 220 and / or update device UDH in the data management device 200 may be disposed on the circuit board CB. In this embodiment, the circuit board CB may be various circuit boards well known to those skilled in the art, such as printed circuit boards (PCBs) and printed circuit board assemblies (PCBAs).

[0021] Please refer to the following as well. Figure 2 , Figure 3 and Figure 4 . Figure 3 This diagram illustrates the operation of a data management method according to an embodiment of the present invention. Figure 4 A flowchart illustrating a data management method according to an embodiment of the present invention is shown. In step S410, external version information ExV is provided to controller 210, wherein external version information ExV corresponds to data portion DP stored in storage circuit 220, and data portion DP corresponds to local version information hostV; in step S420, controller 210 generates update trigger signal TriUD based on external version information ExV and local version information hostV, and triggers application 121 to update data portion DP by updating update trigger signal TriUD.

[0022] In detail, step S410 can be performed by the following steps: causing the controller 210 to generate an update trigger signal TriUD by comparing the version date of the external version information ExV with the local version information hostV.

[0023] More specifically, in some implementations, the external version information ExV includes the creation time of the data identified by the external version information ExV, and the local version information hostV includes the creation time of the data portion DP, wherein the creation time can be the version date. When the version date of the external version information ExV is later than the version date of the local version information hostV, an update trigger signal TriUD is generated.

[0024] Furthermore, in this embodiment, the storage device SD can provide external version information (ExV) via an electrical connection or a communication network. Those skilled in the art can configure the method by which the storage device SD provides external version information (ExV) according to actual needs or the hardware specifications of the data management device 200; there are no fixed limitations.

[0025] Furthermore, in this embodiment, the storage circuit 220 can provide the local version information hostV to the controller 210. Alternatively, when the storage circuit 220 stores the data portion DP, the controller 210, which has its own storage function, records the local version information hostV. Those skilled in the art can configure the components providing the local version information hostV according to actual needs or the hardware specifications of the data management device 200, without any certain limitations.

[0026] Furthermore, in this embodiment, the update trigger signal TriUD can be written in a language understandable by the application 121. Thus, the update trigger signal TriUD can be directly transmitted from the controller 210 to the application 121; the application 121 can, in response to the update trigger signal TriUD, update the data portion DP in the storage circuit 220 via the read / write path RW. Here, the read / write path RW is the data transmission path when the application 121 performs read / write operations on the storage circuit 220. Figure 3As shown, the read / write path RW is bidirectional. When application 121 reads certain data (e.g., data portion DP) from storage circuit 220, data portion DP is transferred from storage circuit 220 to application 121 via read / write path RW. When application 121 writes updated data identified by external version information ExV to storage circuit 220 to overwrite data portion DP (i.e., update data portion DP), the updated data is transferred to storage circuit 220 via the following two implementations involving read / write path RW. In one implementation, updated data is transferred from application 121 to storage circuit 220 via read / write path RW. In another implementation, updated data is first transferred from storage device SD to controller 210; then, application 121 instructs controller 210 to transfer the updated data to storage circuit 220 via read / write path RW.

[0027] On the other hand, when the update trigger signal TriUD is not written in a language that the application 121 can understand, after the data management device 200 is restarted, the controller 230 can respond to the update trigger signal TriUD by transmitting the data update command UDO to the application 121 through at least one system program (e.g., the basic input / output system 122 and the operating system 123).

[0028] For example, after the data management device 200 restarts, the basic input / output system 122 can receive a data update command UDO from the controller 230. Then, the operating system 123 can receive the data update command UDO from the basic input / output system 122 and transmit the data update command UDO to the application program 121.

[0029] Next, in response to the data update command UDO, the application 121 can perform an update on the data portion DP.

[0030] In this embodiment, after application 121 completes the update of the data portion DP, controller 230 transmits an update completion signal CUD to controller 210. Then, in response to the update completion signal CUD, controller 210 retrieves the update trigger signal TriUD. Thus, after the data management device 200 restarts, the operations related to controller 230, application 121, basic input / output system 122, and operating system 123 will no longer be executed, thereby ending the data update process.

[0031] Please refer to the following: Figure 1 And refer to them together Figure 2 It is worth noting that the above data management method involves controller 210, and may further involve controller 230. Therefore, Figure 1The control device 110 includes at least a controller 210, and in some embodiments, may also include a controller 230. In the data management mechanism of the present invention, the data portion DP in the storage circuit 220 is updated through interaction between the controller 210 and the application program 121. Alternatively, the data portion DP in the storage circuit 220 is updated through interaction between the controller 210 and the controller 230 and the program group 120.

[0032] In summary, the data management device and data management method of the present invention can update the data in the local device in a timely and automatic manner through the interaction between the control device and the program group, thus solving the problem of user inconvenience caused by the need to manually update the data in the storage circuit of the local device, which is common knowledge.

[0033] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A data management method, characterized in that, include: External version information is provided to a first controller, wherein the external version information corresponds to the data portion stored in the storage circuitry of the local device, and the data portion corresponds to the local version information; as well as The first controller generates an update trigger signal based on the external version information and the local version information, and triggers the application to update the data portion through the update trigger signal.

2. The data management method according to claim 1, characterized in that, The step of generating the update trigger signal based on the external version information and the local version information includes: The first controller generates the update trigger signal by comparing the version date of the external version information with the version date of the local version information.

3. The data management method according to claim 2, characterized in that, The step of enabling the first controller to generate the update trigger signal by comparing the version date of the external version information with the version date of the local version information includes: When the version date of the external version information is later than the version date of the local version information, the update trigger signal is generated.

4. The data management method according to claim 1, characterized in that, Also includes: The storage circuit provides the local version information to the first controller.

5. The data management method according to claim 1, characterized in that, Also includes: After the local device restarts, the second controller, in response to the update trigger signal, transmits a data update command to the application through at least one system program; as well as In response to the data update command, the application performs an update on the data portion.

6. The data management method according to claim 5, characterized in that, The step of the second controller transmitting the data update command to the application through the at least one system program includes: The basic input / output system receives the data update command from the second controller.

7. The data management method according to claim 6, characterized in that, The step of the second controller transmitting the data update command to the application through the at least one system program further includes: The operating system receives the data update command from the basic input / output system and transmits the data update command to the application.

8. The data management method according to claim 5, characterized in that, Also includes: After the application completes updating the data portion, the second controller transmits an update completion signal to the first controller; as well as In response to the update completion signal, the first controller retracts the update trigger signal.

9. A data management device, characterized in that, include: The first controller is used to couple to the storage device to receive external version information; as well as The storage circuit includes a data section and local version information, wherein the external version information corresponds to the local version information in the data section. The first controller is further configured to generate an update trigger signal based on the external version information and the local version information, and trigger the application to update the data portion through the update trigger signal.

10. The data management device according to claim 9, characterized in that, Also includes: A second controller, coupled to the first controller, is used to transmit a data update command to the application in response to the update trigger signal.

11. The data management device according to claim 10, characterized in that, The second controller is further configured to transmit an update completion signal to the first controller when the application completes updating the data portion, and the first controller is further configured to respond to the update completion signal and retract the update trigger signal.

Images