TW200839568A - Incremental transparent file updating - Google Patents

Abstract

A system and method to protect a target file from data damage wherein a wrapper application transparently intercepts a write call operative to affect the target file and stores the pertinent data in a delta file. Occasionally the target file is backed up in a temporary file and then updated. The wrapper application also intercepts a read call operative to access the target file and merges the update information with data from the target file in a temporary file. The resulting merged data is returned as read results data.

Description

200839568 IX. Description of the invention: [Technical field of the invention] Various methods and systems for protecting a target file from damage are possible, and in particular, the method and system prevent the target broadcast from being opened for writing Data corruption due to interference. [Prior Art] Flash memory devices are well known in computer engineering. The usual way of storing information in such memory is in the data file managed by the operating system. ... The known feature of flash storage systems is that data files are vulnerable to data corruption if a specific incident such as a power failure or a software crash occurs while the file is open for writing. This creates a serious problem because it is routinely required; and the file must be opened for writing to be updated. A solution has been developed for special handling of the software to remedy the risk. This solution can be implemented in many word processing applications, which periodically generate backup copies of open broadcasts. Or, when the damage of the file has been detected, the public j ut ty) is executed (4). However, these solutions reduce the development of the application for the k of the application, and the solution is solved. Approach the source of other types of problems due to programming errors. In addition, the heart: Apply the original version of the private protection file and keep the access violations too late (if different applications call which files they will access?). The inconvenience of this need to broadcast the case (4) 1 protection = I27085.doc 200839568 The law can also be used for the system-wide file protection mechanism, which constantly updates the entire data storage device or a permanent backup copy of specific important data. Keeping a permanent backup requires a large amount of data storage and system resources to check and update the schedule frequently. Therefore, it is widely believed that it is highly desirable to have a solution that allows any application to use any data file without the risk of damaging the talented case due to the above reasons and does not maintain a permanent backup copy. [Summary of the Invention]

Used to protect against the target; to prevent the data from being damaged by various methods and systems. The 'and specific' methods and systems prevent the target file from being opened for writing due to interference. The data is damaged. An embodiment of a system for storing a target file and protecting the target file from data corruption may comprise: a) a processor configured to retrieve and execute a code of the packaged application 'the code includes The following program f 'at least the file command intercepting the at least one configuration command issued by the second application is operable to affect the target file, Π) a program for storing update information related to at least the broadcast command The code, and the private code for updating the target broadcast case by using the update information, the first memory jade, which is used for storing the target file; and for storing the update information. The package should be the second application. % private can be independent of the issue of file commands in a computer readable code example, computer readable code for the care: the media - implementation ψ ^, , /, 拓 拓 file to protect against data damage, The code may include: a code for intercepting at least one file command issued by the application and 127085.doc 200839568 operable to affect the target file; (2) for storing update information related to at least the file command without modifying the target slot The procedure of the case; and e) use (4) to update the target file with the update message. The computer readable code can be independent of the application that issued the command. A method of using a wrapper to protect a target file from data corruption - the embodiment may include the following steps: a) intercepting at least the right command issued by the application by the wrapper to affect the target target The interception step is transparent to the application; b) storing the update information related to at least one file command without modifying the target file; and e) updating the target file with the update information. An embodiment of a system for reading data from a text protection target file can include a processor configured to retrieve and execute a code of a packaged application, the code including the following: A code that is independent of at least the broadcast command issued by the application that wraps the application, the file print is operable to access the text protection target file; and the code for reading the update information related to the file command . The system may also include a first memory space for storing the text file of the text file and a '"""" memory space for storing updated information. An embodiment of a method for using a wrapper to read a protected object file can include the steps of: intercepting at least one file command issued by the application by a wrapper program operable to access the protected object file. The interception step can be transparent to the application. The method can also include the step of reading the updated information associated with the at least one file command from the incremental file. The incremental file can be independent of the protected target file. The method can be further advanced as 127085.doc 200839568 includes the steps of merging the information and update information from the target rights and returning the combined information as a response to the file order. An embodiment of a system for storing a target file and protecting the target file from data corruption can include a first memory space for storing the target file. The system can also include a second memory space for storing updated information relating to at least one file command operable to affect the target broadcast. The system can also include a program configured to fetch and execute a packaged application, the code comprising the following: a code for intercepting at least one file command operable; Comes with: * a code for the memory space; and a code for updating the target file with the update information. The application of the package. The L-clothing formula can be independent of the issuing file: in the system for storing the target file, the first memory space can be resident in the non-volatile example of the data processing device, the second memory space; = the middle. In:: some of the non-volatile memory, the same in the same body as the 222, and the updated information library in the memory; in other embodiments, the second memory space Neutral volatile memory. In other embodiments, the singular space may be resident in the data stored in the non-volatile or non-volatile. The memory of the storage device (the system used to store the target file is stored in the portable data storage #晋). A brother's memory space can be stored in the memory of the storage device. The portable data storage device Examples include removable media (eg, magnetic disks) or portable disks (eg, Iraq, or photon κ discs, external hard disks, or Wisdom 127085.doc 200839568 cards). In some embodiments, the second memory The volume space can reside in the same memory as the first memory space, where the target file and the update information are stored in separate locations in the memory. In other embodiments, the second memory space can reside in f In the memory (volatile or non-volatile) of the material processing device. In other embodiments, the second memory space may reside in the volatile memory of the portable lean storage device. In the system, the update information may only include information related to at least one file command. In particular, the update data, the second memory space, and the incremental file may not contain the copy from the target file. The data port, even after the command issued by the application and operable to affect the target file has been stored, only a copy of the data in the target file will be kept (the copy of the target file is only stored in the first memory) a copy of the updated information relating to the stored file order (the data related to the stored file command is only stored in the second memory space). The data from the target file is only used after the merge event. The second copy is placed in the temporary broadcast. An embodiment of the system for storing the target file may further include a third memory space for storing the temporary file, and the package application may be improved to include the target file At least a portion of the code is copied to the temporary file. In an alternative embodiment, the temporary file is a temporary file or a temporary allocation location in an existing file or a temporary allocation location in a volatile memory package application may further include Applying the stored update information to a temporary file to generate an updated version of the target file The packaging application may further include a code for replacing a portion of the file with the temporary file 127085.doc -11- 200839568. According to an alternative embodiment, the third memory space may reside in the same In a memory having the same memory space, in another alternative embodiment, the third memory space may reside in the same memory as the second memory jade. In another alternative embodiment, The three memory spaces may reside in any of the memory devices listed above. Therefore, it should be understood that the second memory space may be resident in a data processing device or a data storage device that is volatile or non-volatile. Memory and third memory space

Each of the alternate locations can be combined with each of the alternate locations of the first and second memory spaces. A computer readable storage medium embodying a computer readable program code for protecting a target file from data corruption - an embodiment may include a code for intercepting at least the file command issued by the right j, the code An application that is independent of the command of the file. In the embodiments described below, the process: 1 can be executed independently of any particular application and from any application: intercept file commands. The file command is operable to affect the target (4). It also includes the option to store update information related to the file command without modifying the target file. + Update the target file with the update information. In the alternative 1 private horse can mean ^: will be executed according to a fixed time schedule "new two or will respond to - or multiple termination events to perform the update; will be based on _ fixed time schedule and - a termination event The combination to perform the update. An example of a readable medium may include a removable device included in a package that is included in a portable storage device, and a removable computer or a computer readable medium included in the package may be installed on the feeding device via the Internet. Hard drive. The code can be used as a stand-alone program to wait for information on 127085.doc -12· 200839568 side-by-side or on any storage device. Alternatively, the program drink may include the implementation of the == in the data processing device, and the interface between the driver and the device. Alternatively, the code can be incorporated into the operating system or within the file server application. In another 16 cases, the code is executed by a processor inside the f-storage device.

, "Intercepting the file command and storing the information of the update information" - the embodiment can be intercepted and stored in a visible or multiple conditions. For example, the application can be intercepted and stored only when the application of the command is "multiple" included in the ft application. In the content described in this article, the "included" application can be used. The program is defined as an application that has been designated as a package program from which the package program will be modified to modify the file file of the target file. The application included in the package is an application that stores important standards without power output protection. [For example, Mic_ft is (1). 8]). In an alternative example, if the command is not issued, the excluded application of the application can intercept the file command and store the update information. In the content described in this ft, the "excluded" application can be defined as an application that has been intercepted by the file to modify the target file. For example, Mi(10)so line Word8 can be:, the excluded application • Wang style, because it has its own automatic file protection; or Microsoft lnternet EXpi〇rer8 can be excluded because it stores a large number of temporary files, but usually does not store Modify the file). In an alternative m example, if the file command is operable to affect a file that is not a temporary file, the file command can be intercepted and the update information stored. In an alternative example 127085.doc •13-200839568, if the file command is operable to affect the belonging, the included "file type file" can intercept the file command and store the update information. In the content described herein, The "included" file type can be a file type that has been designated as protected by a packaged application [for example, a .txt file can be a included broadcast type]. In the alternative example, if the file command is operable to affect a file that is not of the "excluded" file type, the file command can be intercepted and the update information stored. In the context of the description herein, the "excluded" file type may be a file type that has been designated as not protected by the packaged application [eg, the .doc and .tmp file types may be excluded], and in one In the alternative example, if the file command is operable to affect the file stored in the included storage device, the file command can be intercepted and the update information stored. The included device may be defined in the context of the description herein as a device designated to protect a file on a device that will be protected. The computer readable code can further include, for example, executing each of the write commands operable to record the target file after executing the code for storage and before executing the code for updating The code. An embodiment of the fine code can further include a code for detecting a termination event and for updating the destination file with updated information after the termination event. Some examples of termination events may include the issuance of np 7 to close the target file, the closing of the application accessing the target file, and the occurrence of conditions depending on the statistics associated with the plurality of file commands [eg, if issued Eighty-eight percent of the file orders to the target file change small: 1 kilobytes of data can be triggered when the file command is issued, and when the target file & becomes greater than 10 kilobytes of data Termination event], 127085.doc -14- 200839568 and the maximum time threshold since the previous update of the target file. An embodiment of the computer readable code can further include: copying the - part of the target file to the temporary file (4) the program mother, and the code for applying the stored update information to the temporary file. In an alternate embodiment, a code for opening a temporary file and copying the material immediately after storing the updated information may be provided. In a second alternative embodiment, a code for copying the temporary broadcast and immediately copying the material prior to updating the target file may be provided. The computer readable code - the embodiment may include a code for notifying the stored update to the temporary file after the occurrence of the merge event. According to other features of the described preferred embodiment, some examples of merge events include: i) issue of a command to close a target file, π) access = application of a file % closed, U1) dependent on and plural (4) of the conditions of the statistics related to the file order [for example, if 80% of the file orders issued to the target file change the information of less than 1 〇 , ,

The order is issued 5 so that the day is removed and the termination event is triggered when the data in the directory is changed by more than 10 kilobytes], iv) the size of the incremental slot containing the updated information is the maximum size threshold. The value of the super ', , ) performance of the system to the minimum activity threshold below the clockcast ·, A Shan I change, V1) the maximum time threshold since the previous merger event, 戎丨彳, The application of the updated information to the temporary file of the commander of the order of the target file will be taken immediately before the simulation is executed. Because &, the temporary update file contains the information, and the work update data will be sent back to the application that issued the read command. The application of the file file to the temporary file can be next to the target file. Before the update. ?曰 127085.doc -15- 200839568, according to other features of the described preferred embodiment, the computer step-by-step includes detecting 终止 for the termination event; 4. after the event is used to utilize the stored update information =New and: detected the termination of the target file for deleting the target file 临< _ _ 八 八 目 目 且 且 且 且 且 且 且 且 且 且 且 或 或 或 或 或 或 或 或 或 或 或 或 或 或 或 或 或 或 或 或 或 或 或 或 或For example, at least one of the files of the packaged program can be included in the file. The file is operative to affect the target command. _ 4 ^ 私 私 独立 独立 独立 独立 独立 独立The wrapper stores the updated information related to at least the file command without changing the steps of the project. The update information may contain the information necessary to perform at least the command. The method can also include the step of updating the target file with the update information. According to other features of the described preferred embodiment, the application in the plurality of included applications can be intercepted and stored in the time interval between the end of storing the update information and the end of updating the target file using the stored update information. Each command initiated by the program and operable to affect the target file. According to still further features in the described preferred embodiments, updating the target file may include the sub-step of copying at least a portion of the target file into the temporary file and applying the stored update information to the temporary file, and utilizing the temporary file, all or - Partially replaces all or part of the target file, thus effectively updating the target slot and deleting the temporary file. According to still further features of the described preferred embodiment, the increment 127085.doc -16-200839568 slot containing the update information can be deleted after the step of applying the stored update message to the temporary file. In accordance with other features of the described preferred embodiment, the updating step can be performed upon occurrence of one or more termination events. Examples of termination events include: i) the issuance of a command to close a target file with H.1), the closing of an application to access a target rights, and iii) the statistics related to a plurality of file commands. Appears [for example, if the application accesses the target broadcast at least once every five minutes in a half-hour period, the application that does not access the target file in the ten-minute period is the update of the trigger target file. Termination event], 1V: transition from the activity level of the industry system to the minimum activity threshold, v) the maximum time threshold since the issuance of the previously stored file command, and the maximum time since the previous merge event Exceeded the threshold. In accordance with other features of the described preferred embodiment, the steps of intercepting the rights command and storing the updated information may be conditional. For example, interception and storage can only occur in the following months: when the file command is issued by a plurality of applications included in the application private, the command is issued by the application other than the (4) application. When the program is issued, when the file command is operable to affect the file different from the temporary file, when the file command is operable to affect the type of case, when the file command is inoperable to affect the arrangement, ', g In the case of a case of dust, or when the file order is operable to affect the storage - in the file in the storage device included. An embodiment of a system for reading data from a text protection target file can include: a processor configured to retrieve a code of a package I application from a storage medium and configured to execute the code. The packaged application can include a code for intercepting at least one of the commands issued by the application independent of the packaged application 127085.doc -17-200839568. The file command is operable to access the protected target slot. The wrapper application can also include code for reading update information related to the file command. The system may also include - a first memory for storing the protected target file (4) and a second physical space for storing updated information. ~ According to other features described in the preferred implementation, the package (4) program for the system for reading from the protected target file may also include the purpose of incorporating the information from the protected target file and the updated information into the temporary file. Code. The temporary file can be a file containing updated information, or the temporary file can be a separate temporary file. Temporary files and update information can be stored on the same memory device as the target file or on a separate memory shelf. An embodiment of a method for reading a protected target building using a package type may include the steps of: intercepting at least a slot command issued by the application by a wrapper program, the play command being operable to access Protected target file. The interception step can be transparent to the application that issued the command. The method can also include the step of reading updated information associated with at least the archive command and stored in the incremental file. Incremental files can be independent of protected target files. The method further includes the step of merging the data from the target file with the update information and returning the merged data as a response to the file command (responding to reading the result data). Terminology The following terms are used in the present application in light of their obvious meaning, and the meanings such as shai are understood to be known to those skilled in the art. However, for the further clarification of the subject matter of the present invention, the following explanations, scrutiny and 127085.doc -18 - 200839568 examples are given as to how such terms may be used or applied herein. The following explanations, explanations, and illustrations should be considered as illustrative or representative and should not be considered as exclusive or limiting. Rather, the terms discussed below should be interpreted as broadly as possible consistent with their general meaning and the following discussion. 〇 Merging: (for example) applying the updated information stored in the incremental file to the self-targeting & copying case to the Pro B Temple (for example, the temporary standard can be an incremental broadcast or a separate temporary file) The process of content. 〇 Merge event: An event that triggers the merge process. Events can be based on system events, such as time bases, _checks, or system instructions. 〇Update target file: The process of applying update information to the target file (see above) In the car-friendly embodiment (below), updating the target file is done by copying one part of the target file _$ 稷1 to l The file is applied to the temporary file and the replacement portion of the target file is replaced by the corresponding updated data of the temporary file T. , 〇 Incremental file: can be used for (for example) 系; 系 /, the temporary file of the file to be changed to update the relevant information. 〇Target ································································································· Refers to the files that are protected from data damage. 〇 Intercepting, monitoring, inspecting, changing, and/or 戋 “ “ ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( 或 或 或 或 或 或Communication between the dishes and the cooking system 0 127085.doc -19- 200839568 〇 Standalone application: “—The application does not depend on the second application (ie, no second application is required) Intended to work) 'The first application is said to be independent of the second application. · ο Packaging: monitoring, intercepting and/or controlling (for example) another application and computer system or one or more applications Application of communication with the device, program. 〇 〇 料 储存 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 〜 〜 〜 〜 〜 〜 〜 , hard drive) or Removable (for example, flash disc) or removable media (for example, compact disc or tape) 〇 Save command: For the case, "Save the command in the incremental file" can be used to refer to The operation of storing the update information related to the command in the incremental file, the update information contains the necessary materials to apply the command in the future. [Embodiment] • , can refer to the schema and accompanying description to better understand according to various The principle and operation of the addition of the transmissive file update of the embodiment. ± Various preferred embodiment examples - by keeping the file open for minimization of the write, thus causing an accident to occur when the file is opened Risks • Minimize the system to minimize the risk of damaging data files. Also according to a preferred embodiment, the application implements a read and write command operable to access a protected data file (target file), and the target The file is kept open for reading purposes only. The file is not put in risk. The smaller service storage area (hereinafter referred to as the incremental file) remains open and used. Storage ^ 127085.doc -20- 200839568

Update information relating to the file order of the operationally------------------------------------------------------------------------------------- At the same time, the application file is used to simulate the reading and writing of the target file. Packaging application start-up, monitoring, interception and emulation of the basic elements of the communication towel between the application and the device or between the functional application and the system. All update information for a particular statement is accumulated in one or more incremental criteria. If necessary (the second column is 4 if the simulation is updated to read the target broadcast or when the target is updated), the stored update information and the information read from the target file. And to the temporary file. During the merge process, the temporary file is opened for writing and some or all of the target file is copied to the temporary file. The package is then based on the file stored in the quantity (4) of the update f. Occasionally, the target file is also updated. When updating the target file, first close and check the temporary file. Then replace one of the target files with a temporary file: points. This process protects the target file from data corruption by opening the target file and being vulnerable to data corruption: Small: In addition, if the power failure occurs when the target: case: system is made to the temporary file, the target file is kept complete. If a power failure occurs while updating the part of the target file, the temporary file remains intact. Both the file system and the functional application cannot see the packaging process, 苴 for both. Wei should rely on ^ when the shirt works in the package == program. The file system handles all file commands that arrive at the file system just in the absence of a packaged application. Therefore, the functional application designer writes its program according to the (4) system standard, so that the program adapts or even becomes aware of the file protection routine. Similarly, the program sets the ancient +畐, °, and does not want to design an application-dependent routine to prevent data corruption due to interruptions when writing for storage. The function of the wrapper is for the function application and the file system is 'transparent' so that the wrapper can be independent of any specific function application: so the 'package program can be used as a protection for any function application The stand-alone program of the accessed file is independently sold f. Since the package f is independent of any special function application, the package program can be included in the device driver or in an operating system that must be commanded from any program that the user can install. Figure 18 shows a prior art data processing device 120a (such as a personal computer) having a processor 111a. The processor ma executes an application 122a (such as the Micr〇s〇ft Wind〇ws8 text editor) and a file manager system 124a (such as FAT324NTFS). The application and file management system 124a is illustrated as executing the application 22a and the file management system 124a with the instruction processor 121a within the processor 121 & The application 122a issues an archive command, for example, operable to access the read call 134a of the archive 130a. The file 13A is stored in the portable data storage device 126a. The read call 134a is processed directly by the file management system 12A. The building management system 124a opens the file 130a for reading, and reads 135a data from the slot 13A and sends 137a to the application 12a. In the next four, the application private 122a issues the second instance command (which can be operated to change the write call 136a of the building 130a). As is known to those skilled in the art, archives typically do not reside in a single contiguous memory address set, but are composed of a partial string associated with a set of memory address metrics by the 127085.doc -22-200839568. Specifically, the production case UOa consists of three sections 13_, 13 (^ and 13 () _, "When archiving, it may be necessary to add memory that is not suitable for the current configuration to the file: information. Under this condition, 'no It is necessary to move the entire file to the new memory fc t exactly and 5, so that the new address is associated with the broadcast and the new data is written into the new memory space. The file management line ma receives the write call 136a, opens the file 130& for writing and writing data directly to 13% to file 13Oa. This is the state of the art. It is well known that when writing to a device such as portable data storage device 12 (eg, power failure, When the portable data storage device 126a is removed from the slot, or the software fails, valuable information may be lost from the opened file. Therefore, whenever an application such as the application 122a issues a write command, for example. At the time of the write command, the file i30a of the system of Figure 1A is in serious data loss risk. Figure 1B shows a first embodiment of a system for adding a transmissive file update, including data processing. A 120b (such as a personal computer) containing an execution application 122b (such as Microsoft Windows Notepad text editing), a packaging application 150 (also executed on processor i2ib), and a rights management system 124b (such as The processor 121b of the FAT32 or NTFS). The application 122b and the wrapper application 150 are presented in FIG. 1B as executing the application i22b and the wrapper application 150 inside the processor 121b with the instruction processing instrument 121b. 'Application 122b issues the file The command, for example, is operable to affect the write call 136b of the file 130b stored on the mobile storage device 126b. The application 127085.doc -23 - 200839568 program 122b is a standard application, and all file commands (including write calls 13 6b) ) is issued in accordance with the standard operating system agreement. The target file 130b consists of two parts labeled 130b-i, 13〇b-ii and 130b_iii. Each part 13〇bi, 130b-ii and 130b-iii occupy a continuous The memory address string. The last byte of each part 13〇1^ and 13〇1)4 is an indicator pointing to the first address of a part of the target file 13〇b. Part 1 The last bit of 30b-iii is the stop bit representing the end of the file 13〇b. The write call 136b is intercepted by the wrapper application 150. In this example, the write call 136b is operable to affect the portion 13〇νΗ. When the wrapper application 150 detects a write call to i36b, the wrapper application 15 checks to determine whether to intercept and redirect the write call 136b. In the example of the embodiment of FIG. 1B, the intercept and redirect write call 13 The contempt depends on all of the following conditions: the storage device 126b is of the type included in the type of storage device to be protected and the type of the file 130b is included in the file type to be protected. In this example, since the user specifies that all portable storage devices should be protected during the setting of the packaging application 15b, and the portable storage device 12b is defined as portable storage due to the driving routine of the portable storage device 126b The device, therefore, the portable storage device 126b is the included storage device. Similarly, the file 13〇b is the included file type (txt file), so the wrapper application 150 intercepts and redirects the write call 13讣. The interception of system calls can be done in many ways known to the programmer, such as, for example, Nitesh Dhanjani and Gustavo R〇drigUez-Rivera published in Linux Journal 2006 "Loadable Keme!

Module Pr〇gramming and System Call Plus (10) Coffee Fair's computer I27085.doc • 24 - 200839568 The programming textbook is described in detail. In particular, the wrapper application 150 prevents the direct transfer of the write call 136b to the file management system. The fact is that the 'packaging application 15' indicates that the 152b file management system _ stores the update information associated with the call 136b in the incremental slot 158. The file management system 124b writes 139b to the incremental file 158 for the update information necessary to update the target file 130b. In the example of Fig. (7), the update information includes the material to be added to the target file 13〇b. It will be appreciated that the update information may be an edit message (eg, an instruction to move the data ghost from the target file i3Gb: position to another location, or an instruction to remove the data block from the target file) In this case, the update information may not include the new data of the target file 130b. Alternatively, if there is no incremental file 158, the file management system will first create an incremental file 158 before writing the 139b data. The wrapper application 15 reports back to the execution application as if the target file 130b has been updated, thus emulating the 13-value write to the target file. During the emulation write process, all writes have reached the incremental play 158. The target file 130b has not been modified, and the target file 13〇b has not been opened for writing. It should be emphasized that the packaging application 15 receives the file command in accordance with the standard operating system protocol and passes the response and data back to the application 122b' to accurately simulate the operating system response and data. Thus, the activity of the packaged application 150 is transmissive to the application 122b, and thus the activity of the application 122b is based on operational criteria and is due to the presence of the packaged application 150 without modification. In the example of Figure IB, the wrapper application 150 and the application are both executed by a single processor 12 lb. Therefore, to facilitate command interception, package 127085.doc -25- 200839568 installs the application wrapper application i 22b. The 11 package &quot;application 122b means that the application (10) is not executed independently. More specifically, when the user requests to start the application 122b, the request is passed through the package application 15. The wrapper application 150 invokes the application 122b (which is packaged by the wrapper application 150) in the wrapper application 15&quot; (i.e., all input and output to and from the application mode 122b via the wrapper application) 150) At a later time, the application 122b issues a second file command (read φ for 134b). The read call 134b accesses the target file 130b; and specifically accesses at portions 130b-ii. The wrapper application 15 Then, the read call 13 servant is redirected, and the data is read from the target file l30b by issuing the first read call 134c of the access target file 130b. The read call 13 is processed by the file management system 124b. The management system 12 opens the file 13 for reading, and reads the l35e data from the portion 130b-ii of the file 130b and sends the read result data 137c to the packaging application 15〇. The packaging application 150 then checks for the presence and absence. The target file 13 is complemented by the associated incremental file 158 and the updated information in the incremental file 158 is applied to the range of 134b. In the example of the figure, there is an incremental right. 158 and the portion of the file i3〇b, 13〇ι^π, contains the range of the read call 13 servant, and the incremental file 158 does contain the update of the range of the read call 134b. • Therefore, in order to implement the read call 134b And the latest read result data (simulation read information) is transmitted back to the application program 122b, it is necessary to merge the update information related to the file command 152b stored in the incremental file 158 with the data from the target file 130b. Therefore, read The fetch 13 servant constitutes a merge event that triggers the merge of the command stored in the delta file 158 with the 127085.doc -26-200839568 stored in the target file n〇b. To perform the merge, the wrap application i5〇 A second read call 134d is issued to access the delta file 158. The read call 134d is processed by the file management system 12. The file management system </ br> opens the Zengli Cup case 158 for reading, and the self-increment file 158 Read 13% of the data and send the read result data to 137d to the packaging application 15〇. The reading result data from the feeding 135c-d is applied by the packaging application 15〇 by applying the updated information from the 135d From the data of the read 135c, and the merged data is sent 137b to the execution application 122b, so that the simulation returns in response to the read result data of the read request 13. Therefore, the packaged application has been simulated from the target. The file 13b reads the updated data. The application 122b is unaware that it has not yet communicated directly with the file management system 124b. At this point, the merged material from the read l35c_d constitutes an updated version of the 13 〇ι of the target file 130b. . Since the activity on data processing device 120b is currently low (there is a lot of free processing capability) such that update target archive 130 will not interfere with any other process in this example, wrapper application 150 updates target archive i30b. It will be appreciated that it is not necessary to update the target file 每次3〇b each time the data is merged into the temporary file. In order to update the target file 130b, the wrapper application 15 first instructs 15 to write the merged data to 139c into the delta file 158 by the file system 124b (and thus replace the command information previously stored in the delta file 158). Next, the package utility 150 instructs the file system 124b to update the target target 130b by replacing the 193 portion 130b-ii with the merged material now stored in the incremental broadcast 158. Since both the target file 130b and the incremental file 158 already exist on 127085.doc -27-200839568 on the same storage device 126b, the kili 4 field case 158 is then merged into the target file only by changing the address index. Substitution 193 is implemented in i3〇b instead of part 130b-ii. In particular, in the example of Figure 1-8, the address of the deduction k at the end of the delta file 158 is set to point to the beginning of the portion I30b-iii of the archive, and then the delta file 158 is closed. When the packaging application 15 verifies that the incremental file 158 has been closed] τ opens the target file for writing, and sets the indicator at the end of the target file mb to point to the beginning of the enhanced file 158 At the address, and then close the target file u〇b. Finally, the memory space of part i3〇b_H of the target file 130b is free for future write commands. Since the incremental file 158 has been completely reconfigured to the target file, the memory index # at the beginning of the incremental file 158 is removed from the directory of the health storage device (10), thereby effectively deleting the incremental file 158. When there is a future write command, the wrapper application 150 will need to create a new volume file. In the example of Fig. 4, the command to merge the data fish copied from the target file 1 into the incremental file 158 is triggered by the read tone. The merger is also triggered whenever there is a need to update the target (4) coffee termination event. Before updating the target file i, the update information stored in the ~Li 4 Tian case 158 and the data stored in the target file 13 are merged into the temporary rights (as in the above, the incremental rights case 158 can serve as a temporary slot case) ). In this way, the temporary file serves as a backup of the target file. If a power failure occurs while updating the target file, thereby destroying the target (4) side, the hidden data of the target file can be restored from the temporary file. The person may also be triggered any time after the time limit has expired since the last merge. 127085.doc -28- 200839568 Source [Memory Space and Processor Time] is triggered. Many events can trigger an update of the target file. Updates may be triggered periodically (e.g., target archive 130b may be updated every 15 minutes), or may be triggered by a termination event. Examples of termination events include the closing of the application 122b that has accessed the target file, or the incremental file 158 becoming too large (beyond the size threshold), or a combined event (one instance of the combined event is at

There is a combination of available resources (memory space and processing time) after the time limit has been exceeded since the last update. Those skilled in the art will appreciate that the delta file 158 may also be comprised of a number of portions, the first portion of the enhanced file 158 may include a portion of the file order of 13 〇&gt;_ϋ, and the second portion of the additional S file 158 contains a portion of the file 〇 Ϊ́3_ίη file command. In this case, it is possible to merge the portion 13 of the seventh and the first portion of the delta file 158 and then update the portion 13〇1) seven, so that the portion 13b-iii of the file 13 is maintained in the original state, thereby making the increment (four) 158 only Contains the second part. Similarly, it will be understood that the _th or last part of (4) can be changed by changing the archive directory address indicator or the stop bit. Those skilled in the art will understand other existing ways of exchanging portions of the archive. In the embodiment of Fig. 1B, the incremental weight 158 is stored on the same memory (portable memory device) as the target standard. It should be understood that the incremental file 158 may be a non-volatile memory that resides in the fast volatile memory of the ostrich of the f-processing device or in the hard disk or in the virtual memory of the device (10): or another portable device A type of temporary storage in a type of storage device or removable media (for example, a writeable compact disc). Similarly, in the embodiment of FIG. 1B, the packaging application 15 will merge the data of the item 135c_d into the space 127085.doc -29. 200839568 (volatile memory of the computing device 120b). Effectively redirects the read call mb to the space containing the merged data. It should be understood that the combined information can be stored on any memory device, for example, in a non-volatile memory stored in a hard disk or data processing device 120b or in another portable storage device or in removable media (eg, writable) Tight disc). 2 shows a data processing device 22 (such as a network of parallel processors) that executes an application 222 (such as Micr〇s〇 〇 〇 8), a wrapper application 250, and an archive management system (such as fat NTFS) The application 222 issues a file command (a writer 236 operable to affect the file 23() stored in the storage device 226). The person invokes the coffee package by the package application 25. In the implementation of Figure 2, the package application (10) is executed by process 11221b, and the application (2) is executed on the processor in the network that independently processes the data processing device 220. The wrapper application 250 is hunted by the indication 252 to store the money information associated with the caller 236 in the delta file 258 to redirect the caller to invoke the coffee. The file management system 224 only writes 239 to the increment (four) 258 for the update information needed to update the target file. The update information related to the caller's call to the coffee is stored in the incremental file 258, and the target file remains unchanged. The wrapper application 250 reports back to the execution application as if the target broadcast 230 has been updated - thus emulating the writer of the file 23(). In the example of Figure 2, the additional file 258 is stored in the volatile memory of the data processing device. Later, after detecting the occurrence of the "terminating event" 288 (in the example of FIG. 2, 127085.doc 200839568 termination event 288 is the closing of the application 222, the application 222 has issued an action to affect the target file 230. Write call 236), the wrapper application 250 updates the target file 230. Since the delta file 258 is not stored on the same storage device 226 as the play case 230, it is not possible to copy the data into the delta file 258 and The update information is applied to the replicated material in the incremental file 258 and the indicator is changed (as in the example of Figure IB) to update the target file 230. In order to update the target file 230, the package application 250 must first come from the incremental file 258. The stored update information and the data from the target file 23 are merged into the temporary file 292 on the storage device 226. Thus, the package application 250 instructs 290 the file system 224 to create 294 temporary slots 292, which will be from the target file 230. The content is copied 296 into the temporary file 292 and the file command stored in the incremental file 258 (the update information related to the call 236 is applied) is applied to the temporary file 298. File 292. Once the merge successfully ends the 'packaging application 250, the file system 224 is instructed to close the temporary rights 292 and replace the 293 target file 230 with the temporary file 292. Because both the target case 230 and the temporary file 292 have been Existing on the same storage device 226' so the replacement is performed only by the self-posting directory to remove the indicator to the temporary building 292 and the target file 230 (the stored address) is changed to the address of the temporary broadcast 292. 293 (thus effectively updating the target file 23 and deleting the temporary file 292). In the example of FIG. 2, since the application 222 is not executed by the same processor 221 as the package application 250, the package application 25〇 The application 222 (which controls all input and output of the application 222) cannot be wrapped. Thus the 'packaging application 250 wraps the file system 224 so that all calls to the file system 127085.doc -31 - 200839568 224 pass the wrapper application 25 . Thus, the wrapper application 250 effectively wraps the storage device 226. It should be understood that the archive 230 can be accessed by multiple applications. Each application's write command is intercepted by the wrapper application 25 and redirected to the Zengli file 258. Similarly, attempts to read the file 230 by any application will be intercepted and trigger the merge event. The skilled artisan will appreciate that unlike prior art single application composition assurance mechanisms (such as those used by Microsoft 8 Word) that must lock access to protected files, the wrapper application 250 allows multiple applications to target The file 230 performs simultaneous read and write access. Those skilled in the art will also understand the possibility of locking file access and file access conflicts. In particular, in the embodiment of FIG. 1 (wherein the packaging application 15 is only packaging one or more specific applications (eg, application 222), but not the packaging file system 124b), it is possible to make a standalone application (not packaged) The application 150 wraps the file 130b without going through the wrapper application 15〇. Under these conditions, there are prior art solutions (such as locking file 130b) (for example, such as 1997 Jeffery Richter at Microsoft

Press, Advanced Windows 3rd by Redmond Washington

Edition and especially as described on pages 711 to 715). It should be understood that in an alternate embodiment, the data may be copied 296 from the target file 23 to the temporary file 292 as part of intercepting the first write call 236. In this embodiment, the temporary file 292 will be a frequently updated version of the target file 23, and the update target file 230 will only be moved by closing the temporary file 292 and moving the address of the target building 230 to the temporary building 292. The address is 127085.doc -32- 200839568. In the example of FIG. 2, processors 221a-b are components of a multiprocessor network of data processing devices 22. Those skilled in the art will appreciate that there are various alternatives to the processor configuration and that are compatible with the systems and methods used to protect the files; For example, the processor 221b can be within the data storage device 226. The component, or the processor 221b can be a component of a dedicated file system server on the network. 3 shows a simplified flow chart of the reading process of the embodiment of FIG. 2. The wrapper application 250 intercepts 301 a read command from the application 222. The wrapper application 250 first tests 302 if there is an incremental file containing updated information for the file 230 to which the read command is directed. If there is no incremental file, then control is passed back to the file management system 224, which typically processes the read command according to prior art: by reading the 3-6 request range directly from the target file 23〇 and The read result data is returned to 3〇9 to the request application 222 〇φ The right test 302 returns the positive result (ie, there is an incremental file 258 containing the update information of the file to be read 23), then the package application 25 Further checking whether the update information of the 304 incremental file 258 is operational to affect the extent of the read command. If there is no update information for the requested range, then control is passed back to the file management system 224, which typically processes the read command according to prior art: by reading 3〇6 directly from the target file 23〇 The scope is requested and the data is passed back 309 to the requesting application 222. If test 304 returns a positive result (incremental file 258 contains updated information for the range of data to be read), then wrapper application 250 merges 308 the data to be read from the range of 127085.doc -33 - 200839568 file read and Update information from the target file (by copying the range to be read from the target file 230 to the temporary file 292 and applying the updated information from the Pong i file 25 8 to the copy material in the temporary broadcast 292)' and will come from The merged data of the requested range is passed back to the requesting application 222. Figure 4 shows a simplified flow chart of the merging process not according to the embodiment of Figure 2. The package application 250 detects 410 the occurrence of a termination event 288 indicating the need to begin the merge process (before updating the directory file 203). In particular, in the example of FIG. 4, the user closes the application 222, and the application 222 has issued at least one command to modify the target file 230 in the current session. When the wrapper application private 250 detects that the operating system of the device 220 closes the application 222, the wrapper application 250 instructs the 290 file system 224 to open the 294 empty temporary file 292 and copy 296 the content from the target file to the temporary file. Within 292. Particularly in the example of Figure 4, the data to be copied to the temporary 'archive 292' is the range of data to be accessed in the write call 236. The wrapper application 25 further commands the file system 224 to apply 298 the update information stored in the delta file 258 to the temporary file 292. In particular, in the example of FIG. 4, the delta file 25 8 contains updated information related to the write call 236. Once the update information stored in the delta file 258 has been applied 298 to the temporary file 292, the wrapper application 250 issues an order to close the 411 temporary file 292 and is used in the indicator of the portion of the target file 230. The address is changed to the address of the temporary file 292 and the temporary file 292 is used to replace the command of the portion of the 293 target building 230. The packaging application 25〇 then proceeds to the memory of the replacement part of the target 2 2 0 and the increment of the 127085.doc -34- 200839568 broadcast case 258. The space report is free space to abolish the 413 target file 230, the second file, and the incremental file 258 because it is no longer needed. If the separate application writes the human-to-incremental broadcast 258, the merge event is triggered to temporarily suspend the merge process before the write operation. If there is a new call to the target broadcast 23g after completing the port and smuggling, then 414 will be opened. Or '彳 automatically open the 414 new volume file immediately after the merge process.

Other instances of the merged event that are interpreted as merge events, in addition to or in addition to the application 222, include: (1) the issuance of an order to close the target file 23; and (2) the condition of the statistics associated with the plurality of file commands. The occurrence of 'for example, when the application has accessed the data on the storage device 226 every minute for a predetermined period of hours, and then the average access is not accessed by the application without accessing the storage device 226. Ten times the time ^ interval (1 minute 3G times the money minute), _ automatically triggers the merged private, (3) increases the size of the file 258 to the maximum size threshold (for example, the second file 258 The information stored in the store exceeds the information of the kilobytes), (4) the conversion from the activity level of the operating system to the minimum activity threshold (example b' when the memory and processor are within 1 second period When less than 5〇% is occupied); or (5) the maximum time threshold has elapsed since the previous merge event (for example, the wrapper application 250 may have the following rule: the helmet is based on any broadcast since the previous merge event 15 In the minute period, it is opened: the new merge process. Another trigger that can trigger the merge event is to issue a command to grab the target file 230 (as explained in the description of Figure 3, in order to read the updated data) Combine the information from the target file with: 127085.doc • 35- 200839568 Update file 258 update information. Figure 5 shows a simplified flow chart of the write process. The application issues a write call to the target system 224. &amp; application load test _ write call 236 and check 542 to determine whether the broadcast case 23 (the write command is directed to the broadcast case 230) is the file to be protected. Specifically in the graphical example, the storage device w is the protected library device. More specifically, the target file 23〇 will protect the text 'because the target file 23〇 meets the following conditions. The target file 23〇 is stored on the device 226, and the device 226 is subject to the attribution. Early removal of the removable portable storage device that suddenly does not predict interference. [Therefore, packaging application

The formula 250 protects the cake in the storage device 226, and the user in the A is "not long-term (4) user broadcasts more specific" by default to intercept and redirect all write commands to the storage device 226 unless Ex-excluded applications (for example, rMic p々's application is forbidden (for example, Mlcroso (10) is excluded from the application type 2 because it has internal Tan file protection and injury; Adobe read ϋ is also excluded Because AdGbe A(10)ba_ fetch == how to modify the user profile), or unless the write command can be operated by two:: file type (eg 'type of temporary file for excluded' because it comes from the monument g聋 earning W ^ The data loss of the file is very == 222 is the excluded application or write command is directed: = the type of the broadcast or the write command is not directed at 1; in use, the file The system can be written to the file directly. The conditions for: and the file command can be included in the file. The second file can be issued by the included application (the application included is included in the file). Command to be wrapped by the application 250 127085.doc -36 - 200839568

Intercept the list of applications or the application on the M group; the file command is twisted by the application that is not excluded. ap 7 field is not an application that belongs to the file command); file command Can be used as an early or group application to make a file that is not a temporary file; the file command can be operated to change the file type included in the white rainbow &amp; ua system a (the file type included is The file ρ 7 having the type included in the target of the to-be-protected σ 茱 茱 ι ι ι ι 群 可 可 可 可 可 可 可 可 可 影响 ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( In the case of an unprotected type of type early or in the group of files and (4) orders can be broadcast in the protected storage device. Depending on the above conditions - or; = reach, the packaged application will intercept 5 〇1 and redirect 548 write calls, or wrapper application 25, will allow the file system to write 549 directly to the file' as described above for the file system of the prior art. Figure 3, in the example of Figure 5, the file 23〇 is the storage device 226 (which is packaged The .txt file in the storage device (which is not the excluded type and the application 222 is Micr〇s〇ft Visual Studi〇8 (which is not the excluded application). Therefore, the wrapper application intercepts 501 Write call 236. The wrapper application 250 then checks if the merge operation of file 23() is in the line. If the merge operation is in progress, the 546 write command process is temporarily aborted before the merge operation is completed. When the merge operation is completed, the write operation of restarting, suspending, and aborting is resumed, and the content of the 548 write command is redirected by storing the update information related to the write call 2% to the delta file 258. If the operation is not in progress, the wrapper application 250 redirects 548 to write 5 weeks with 236 and saves the update information to the delta file 258. If the 127085.doc -37-200839568 is written to the delta file 258, the merge event is triggered. Then, the merge event is temporarily suspended before the write operation is completed. In summary, although various embodiments and their preferred versions have been described in considerable detail, other types are possible. The spirit and scope of the scope should not be limited to the description of the preferred embodiments contained herein. [FIG. 1A is a schematic illustration of a prior art file storage system; FIG. 1B is for storing and protecting a target file. 2 is a schematic illustration of a second embodiment of a system for storing and protecting a target file; FIG. 3 is a diagram illustrating interception and redirection of a read command and reading of a target file Figure 4 is a flow chart illustrating the application of update information to a temporary file; and Figure 5 is a flow chart illustrating the process of intercepting and redirecting a write call to a target file. [Description of main component symbols] 120a Data processing device 120b data processing device 121a processor 121b processor 122a application program 122b application program 124a file management system 127085.doc -38- 200839568

124b file management system 126a portable data storage device 126b storage device 130a file 13 Oa-i segment 130a-ii segment 130a-iii segment 130b file 130b-i portion 130b-ii portion 130b-iii portion 134a read call 134b Read call 134c First read call 134d Second read call 135a Read 135c Read 135d Read 136a Write call 136b Write § Week with 137a Send 13 7b Send 137c Send 137d Send 127085.doc -39- 200839568

139a write 139b write 139c write 150 package application 152b indication 152c indication 158 incremental file 193 replacement 220 data processing device 221a processor 221b processor 222 application 224 file management system 226 storage device 230 target file 236 write call 239 Write 250 Package Application 252 Refers to 258 Incremental File 288 Termination Event 290 Instruction/Command 292 Temporary File 293 Replacement 127085.doc 200839568 294 Create/Open 296 Copy 298 Application

127085.doc -41 -

Claims (1)

200839568 X. Patent Application Scope: A system for storing a target file and protecting the target file from data corruption, comprising: a) a process, which is configured to capture and execute a packaged application a code comprising: ·) for intercepting a code of at least one file 7 issued by another application, the at least one file command operable to affect the subscript "and the packaging application The program is independent of the other application; a program code for storing update information related to the at least one audit command; and 1U) a program code for updating the target file based on the update information; a space for storing the target file; and a first memory space for storing the update information. The system of claim 1, wherein the first memory space resides in a non-volatile memory of a data processing device. 3. The system of claim 2, wherein the second memory space resides in at least one memory selected from the list of the following components: the non-volatile memory of the data processing device, the data One of the processing devices is a non-volatile memory, and one of the data processing devices is a volatile memory. • The system of claim 1, wherein the first memory space resides in a non-volatile memory of a portable data storage device. The system of claim 4, wherein the second memory space resides in a material selected from the list consisting of I27085.doc 200839568 and is stored in the list of the following items: &nbsp; The non-volatile memory of the carrying type of two-piece clothing is 愔骅 愔骅 愔骅 Γ 己 己 己 ^ 、 、 、 、 、 、 、 体 体 体 体 体 体 体 体 体 体 体 体 体 体 体 体 体 体 U U U U U U U U U U : Set one of the volatile memories. , 糸 ’ ', the update information only includes information related to the at least one file. 7. If the system for requesting items' further includes: The second memory three memory space 'which is used to store the temporary file, and the eight-package application further includes: iv) a program for compressing at least one of the target files into the temporary file a code; V) a code for applying the update information to the temporary file; and vi) a code for replacing the at least a portion of the target file with the temporary file. 8. A method of protecting a target file from data corruption by using a wrapper program, the method comprising: intercepting, by the wrapper, at least one of the commands issued by an application, the at least one file command Operable to affect the target file, the intercepting step is transparent to the application; b) storing updated information related to the at least one file command without changing the target file; and c) updating the updated information The target file. 9. The method of claim 8, wherein the at least one file command includes each write command operable to affect the target file and issued by the application between one of the storage and the end of the update . 127085.doc 200839568 1 The method of claim 8, wherein the updating step comprises: 0 copying at least a portion of the target file to the temporary file; applying the updated information to the temporary file; and, within the file, (1)) replacing at least a portion of the temporary file with at least a portion of the temporary file. To view the file η• as in the method of claim 10, further comprising: d) deleting the _ containing the case after the response. The increment of Beixun refers to 12. The method of claim 8 wherein the update step is performed after at least one termination event of the group consisting of: a free command to close the target file - Issue. π) A close of the application; Long, 110 a close to the application accessing the target file; IV) - Dependent on a file associated with a plurality of file commands; 1 <conditional V) The activity level of the operating system to __minimum live_conversion; 4 under one two::::*: let it, ... time pro V11) one of the maximum time thresholds since the previous merge event. 13 · If the request item 8: , '/, the interception step and the storage step are selected... 'Depending on at least one condition of the group of components, the application is a hard number of included applications. The application is not @127085.doc 200839568 in the excluded application; the at least one file command is operable to affect a file different from a temporary file; the at least one file command is operable to affect an included file type; At least one file command is operative to affect a file that is different from an excluded file type; and the at least one file command is operative to affect - stored in the stored file. 14. A system for reading data from a protected target broadcast, the package #4 a processor configured to acquire and execute a packaged application code, the code comprising: For intercepting a code to a file command issued by an application independent of the package application, the at least one file command operable to access the protected target file; (1) for reading with the at least The code of the update information related to the file command; and • b) a first memory space for storing the protected object structure; and c) a first-memory space for storing the update information. If the request item 14 is pure, the package application further includes: a code for adding the information from the protected target file and the update information to a temporary file. A method of reading a protected target file using a wrapper program, ^ 15 16 a) at least 127085.doc 200839568 file command issued by m by the wrapper program, the at least one file command operable to access The protected target file, the intercepting step is transparent to the application; b) reading the update information stored in an incremental file related to the at least one file command, the incremental file may be independent of the The protected target file&apos; and *c) merge the information from the target file with the updated information; d) return a result of the merge as a response to one of the at least one configuration order. 127085.doc