CN107016123A - File management method and terminal device - Google Patents

Abstract

The embodiment of the present invention discloses a file management method and a terminal device, which are applied in the field of communication technology, wherein the method includes: in response to a file access operation, querying whether there is a file to be accessed pointed to by the file access operation in a preset folder, The preset folder is used to store the cleaned up junk files; if the file to be accessed exists under the preset folder, the file to be accessed is restored from the preset folder to the original storage location, and the run the file to be accessed; if the file to be accessed does not exist in the preset folder, run the file to be accessed according to the storage path pointed to by the file access operation. The embodiment of the invention can simplify file management operations and improve the flexibility of file management.

Description

File management method and terminal device

technical field

The invention belongs to the technical field of communication, and in particular relates to a file management method and terminal equipment.

Background technique

With the development of computer technology, the penetration rate of smart mobile terminals such as mobile phones and tablet computers is getting higher and higher, which greatly facilitates people's life, entertainment and learning, so people's dependence on mobile terminals is becoming stronger and stronger. The operation of the mobile terminal will generate a large amount of data. As the use time increases, the data generated by the installed application program and the data stored by the user will increase. However, the storage space of the mobile terminal is limited and cannot store all the generated data, so the data in the storage space needs to be cleaned up frequently.

At present, the common practice is to put the files specified by the user into the recycle bin according to the cleaning operation of the user. Then, according to the deletion operation of the user, one or more files in the recycle bin are completely deleted. If the user wants to restore a deleted file, he needs to go to the recycle bin to find it and restore it manually. The entire cleaning and recovery process needs to be led by the user, and the operation is cumbersome and inflexible.

Contents of the invention

The invention provides a file management method and terminal equipment, which can simplify file management operations and improve the flexibility of file management.

The first aspect of the embodiments of the present invention provides a file management method, including: in response to a file access operation, query whether there is a file to be accessed pointed to by the file access operation under a preset folder, and the preset folder is used for storing the cleaned up junk files; if there is the file to be accessed under the preset folder, restoring the file to be accessed from the preset folder to the original storage location, and running from the original storage location The file to be accessed; if the file to be accessed does not exist in the preset folder, execute the file to be accessed according to the storage path pointed to by the file access operation.

The second aspect of the embodiment of the present invention provides a terminal device, including: a query module, configured to, in response to a file access operation, query whether there is a file to be accessed pointed to by the file access operation under a preset folder, the preset The folder is used to store the cleaned up junk files; the recovery module is used to restore the file to be accessed from the preset folder to the original storage location if the file to be accessed exists under the preset folder The access module is used to execute the file to be accessed from the original storage location; the access module is also used to perform the file access operation if the file to be accessed does not exist under the preset folder The storage path pointed to runs the file to be accessed.

It can be seen from the above-mentioned embodiments of the present invention that when a file access operation is detected, in response to the file access operation, the corresponding file is first queried under the preset folder specially used for storing junk files. If there is a file pointed to by the file access operation, the file will be restored to the original storage location, which simplifies the steps of file management, so that users no longer need to manually search for the files to be accessed as garbage, and also improves the flexibility of file management features, making file management more intelligent.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only are some embodiments of the present invention.

Fig. 1 is a schematic diagram of the implementation flow of a file management method provided by an embodiment of the present invention;

Fig. 2 is a schematic diagram of the implementation flow of a file management method provided by another embodiment of the present invention;

FIG. 3 is a schematic structural diagram of a terminal device provided by an embodiment of the present invention;

FIG. 4 is a schematic structural diagram of a terminal device provided by another embodiment of the present invention;

Fig. 5 shows a hardware structure diagram of a terminal device.

detailed description

In order to make the purpose, features and advantages of the present invention more obvious and understandable, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described The embodiments are only some of the embodiments of the present invention, but not all of them. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without making creative efforts belong to the protection scope of the present invention.

Please refer to Fig. 1, Fig. 1 is a schematic diagram of the implementation flow of the file management method provided by an embodiment of the present invention, the method can be applied to terminal devices, and the terminal devices include: smart phones, tablet computers, notebook computers, etc. can be used on the move electronic data processing equipment, or other electronic data processing equipment that is not intended for mobile use, such as a desktop computer. The method mainly includes the following steps:

S101. In response to the file access operation, query whether there is a file to be accessed pointed to by the file access operation under the preset folder, and the preset folder is used to store the cleaned-up junk files;

File access operations can be performed by users or by applications. When the file access operation is performed by the user, the accessed file is usually a historical file, for example: the file access operation performed by the user on the historical document file opened by the file processing program such as WPS, OFFICE, or the historical playback file of the audio-visual player program file access operations, etc. When the file access operation is performed by an application program, the application program can execute the file access operation on the file to be called when a certain file needs to be called according to the preset operating logic.

Specifically, in response to the file access operation of the user or application program, according to the identification information of the file to be accessed pointed to by the file access operation, such as: file name, storage path and other information that can uniquely identify the file to be accessed, query the preset Whether there is a file to be accessed pointed to by the file access operation under the folder dedicated to storing the cleaned-up junk files.

In practical applications, it is possible to directly query whether a file with the same file name is stored in the preset folder according to the file name of the file to be accessed.

Optionally, in another embodiment of the present invention, the files stored in the storage space can be cleaned up regularly or regularly, and the files in the storage space that meet the preset size conditions and time conditions can be cleaned up as junk files to the above preset folder. Alternatively, according to the user's cleaning operation, the file pointed to by the cleaning operation may be used as a junk file and cleaned into the above-mentioned preset folder. It can be understood that cleaning in this embodiment refers to moving, rather than copying. After a junk file is cleaned, the junk file will no longer exist in its original storage location. Optionally, when cleaning, the junk files can be directly moved to the aforementioned preset folder, or the junk files can be compressed and then moved to the aforementioned preset folder. Optionally, after the junk file is compressed, the compressed junk file can be renamed, or the file name before compression can continue to be used.

S102. If there is a file to be accessed under the preset folder, restore the file to be accessed from the preset folder to the original storage location, and run the file to be accessed from the original storage location;

If there is a file to be accessed under the preset folder, it means that the file to be accessed has been treated as a junk file, the file to be accessed has been removed from the original storage location, and the storage path pointed to by the file access operation is wrong, then Restore the file to be accessed from the preset folder to the original storage location, and run the file to be accessed from the original storage location. In this embodiment, when the file to be accessed is restored from the default folder to the original storage location, the file to be accessed will no longer exist in the default folder.

S103. If the file to be accessed does not exist in the preset folder, run the file to be accessed according to the storage path pointed to by the file access operation.

If there is no file to be accessed under the preset folder, it means that the file to be accessed has never been processed as a junk file, and the storage path pointed to by the file access operation is a valid path, then run the file to be accessed according to the storage path pointed to by the file access operation .

Optionally, in another embodiment of the present invention, a database can also be created. Through the created database, when the file cleaning operation is performed and the junk files are cleaned to the preset folder, the records are cleaned to the preset folder Information about junk files, such as file name, storage path, cleaning time, etc. And, according to the identification information of the file to be accessed pointed to by the file access operation, it is confirmed whether the file to be accessed exists in the preset folder by querying whether there is a record of the file to be accessed in the created database.

On the one hand, if there is a record of the file to be accessed in the database, then confirm that the file to be accessed exists under the preset folder, restore the file to be accessed from the preset folder to the original storage location, and restore the file to be accessed from the original folder. The storage location executes the file to be accessed. And further, after the file to be accessed is restored from the preset folder to the original storage location, the record of the file to be accessed is deleted in the database.

On the other hand, if there is no record of the file to be accessed in the database, it is confirmed that the file to be accessed does not exist under the preset folder, and the file to be accessed is run according to the storage path pointed to by the file access operation.

In the embodiment of the present invention, when a file access operation is detected, in response to the file access operation, the corresponding file is first searched under the preset folder specially used for storing junk files, if there is a file under the preset folder The file pointed to by the access operation will restore the file to the original storage location, which simplifies the file management steps, so that users no longer need to manually search for the files to be accessed as garbage, and also improves the flexibility of file management. Make file management more intelligent.

Please refer to FIG. 2. FIG. 2 is a schematic diagram of the implementation flow of a file management method provided by another embodiment of the present invention. Electronic data processing equipment used, or other electronic data processing equipment that is not intended for mobile use, such as a desktop computer. The method includes the following steps:

S201. Regularly or periodically scan the locally stored files, obtain and compress target files that meet preset file size conditions and time conditions;

The time condition may include, but is not limited to: the time difference between the last access time or modification time and the current system time is greater than a preset time difference. Specifically, the terminal device periodically or periodically scans the files stored in the storage space, obtains target files whose file size is larger than the preset file size and whose time difference between the last access time and the current system time is larger than the preset time difference, and compresses them.

Optionally, the file size condition and time condition can be user-defined. Specifically, the file size threshold (such as greater than 200M) and time threshold (such as files that have not been accessed within 5 days) input by the user through the preset UI (User Interface, user interface) are obtained, and the file size threshold and time input by the user are followed. Threshold, set the parameter values of the file size condition and time condition.

Optionally, the attribute of the preset folder is a hidden file, that is, the preset folder is invisible to the user. Optionally, the preset folder can be set in the root directory.

Optionally, the storage directory to be scanned can be set according to user-defined operations. That is, the files stored in the local storage directory specified by the user are scanned regularly or regularly, and the target files that meet the preset file size and time conditions are obtained and compressed.

S202. After renaming the compressed target file, clean it into a preset folder as a junk file;

In a practical application example, for example, the user's storage directory can be scanned at a fixed time every day (such as 3:00 every night), and the files that meet the above file size conditions and time conditions are compressed using a compression method such as 7z. In the hidden file reduce of the root directory, and delete the source file of the compressed file to save space.

S203. Delete the source file of the junk file, and record the information of the junk file in a preset database;

It can be understood that before step S201 is executed for the first time, a database with a file index can be created to record the full path of the compressed files cleaned up to the preset folder and the file name information of the compressed files. The full path generally refers to the complete storage path. That is to say, at least the original complete storage path and the compressed file name of the compressed file as the junk file are recorded in the newly created database. Then, after steps S201 and S202 are executed each time, the original full path of the junk file cleaned up to the preset folder and the new file name of the junk file are updated into the database.

Like this, by periodically or periodically automatically compressing the files that meet the preset conditions in the storage space and temporarily clearing them to the preset folder, on the one hand, the file size becomes smaller after compression, so the purpose of saving storage space can be achieved. On the other hand, it is convenient to restore the cleaned files at any time later, thus improving the flexibility of file management and reducing the probability of accidental deletion.

S204. In response to the file access operation, query whether there is a target full path consistent with the full path of the file to be accessed pointed to by the file access operation in the preset database;

File access operations can be performed by users or by applications. When the file access operation is performed by the user, the accessed file is usually a historical file, for example: the file access operation performed by the user on the historical document file opened by the file processing program such as WPS, OFFICE, or the historical playback file of the audio-visual player program file access operations, etc. When the file access operation is performed by an application program, the application program can execute the file access operation on the file to be called when a certain file needs to be called according to the preset operating logic.

Specifically, in response to the file access operation of the user or the application program, according to the full path of the file to be accessed pointed to by the file access operation, whether there is a target full path consistent with the full path is queried in a preset database.

S205. If the full target path exists in the database, confirm that there are files to be accessed under the preset folder, and obtain the compressed file corresponding to the associated file name from the preset folder according to the file name associated with the full target path in the database;

If there is a target full path consistent with the full path of the file to be accessed in the preset database, it means that the file to be accessed has been treated as a junk file, the file to be accessed has been removed from the original storage location, and the file access operation If the storage path pointed to is wrong, query the file name associated with the full path of the target from the database, and obtain the compressed file corresponding to the file name from the preset folder according to the queried file name.

S206. According to the full path of the target, decompress the obtained compressed file and put it into the original storage location corresponding to the full path of the target, and execute the file to be accessed from the original storage location;

Specifically, the original file to be accessed is obtained by decompressing the obtained compressed file, and then according to the target full path of the compressed file (that is, the compressed file to be accessed), the decompressed original file to be accessed is restored to the original storage location, and run. It can be understood that at this time, the access time of the file to be accessed will be updated to the current system time.

S207, delete the compressed file from the preset folder, and delete the record of the file to be accessed in the database;

Understandably, deleting the compressed files that have been restored from the preset folder can avoid duplicate files, thereby preventing storage space from being wasted for no reason. At the same time, delete the record of the file to be accessed in the database, so that when the user or application program accesses the file to be accessed next time, since the record of the file has not been queried in the database, it can be directly run from the original storage location.

In practical applications, the steps of "deleting the compressed file from the preset folder", "deleting the record of the file to be accessed in the database" and "running the file to be accessed from the original storage location" may be executed simultaneously or not at the same time, This embodiment does not make specific limitations.

S208. If the target full path does not exist in the database, confirm that there is no file to be accessed under the preset folder, and run the file to be accessed according to the storage path pointed to by the file access operation;

There is no target full path in the database, which means that there is no file to be accessed under the preset folder, and the file to be accessed has never been treated as a junk file. If the storage path pointed to by the file access operation is a valid path, then follow the Store the path and run the file to be accessed.

S209. Periodically delete the compressed files in the preset folder whose storage duration is longer than the preset duration, and clear the records of the periodically deleted compressed files in the database.

Specifically, the database also records the cleaning time (or compression time) of the compressed files that are cleaned up to the preset folder. Clean up unused compressed files, query the database for files compressed before this time, delete related files in the preset folder reduce, and clear the corresponding data records in the database to free up storage space. Improve storage space utilization.

In the embodiment of the present invention, on the one hand, the purpose of saving space can be achieved by periodically compressing the files stored in the storage space that meet the preset file size conditions and time conditions and putting them into the preset folder; on the other hand, when When a file access operation is detected, in response to the file access operation, first query the database to see if there is a corresponding file in the preset folder specially used to store junk files, and if so, restore the file to the original storage location , simplifies the steps of file management, so that users no longer need to manually search for files to be accessed as garbage, and also improves the flexibility of file management, making file management more intelligent.

Please refer to FIG. 3 . FIG. 3 is a schematic structural diagram of a terminal device provided by an embodiment of the present invention. For ease of description, only parts related to the embodiment of the present invention are shown. The terminal device illustrated in FIG. 3 may be the execution subject of the file management method provided in the embodiment shown in FIG. 1 . The terminal equipment shown in Figure 3 mainly includes:

The query module 301 is configured to, in response to a file access operation, query whether there is a file to be accessed pointed to by the file access operation under a preset folder, where the preset folder is used to store cleaned-up junk files;

A restoring module 302, configured to restore the file to be accessed from the preset folder to the original storage location if the file to be accessed exists under the preset folder;

An access module 303, configured to execute the file to be accessed from the original storage location;

The access module 303 is further configured to run the file to be accessed according to the storage path pointed to by the file access operation if the file to be accessed does not exist in the preset folder.

Specifically, the file access operation may be performed by a user or by an application program. When the file access operation is performed by the user, the accessed file is usually a historical file, for example: the file access operation performed by the user on the historical document file opened by the file processing program such as WPS, OFFICE, or the historical playback file of the audio-visual player program file access operations, etc. When the file access operation is performed by an application program, the application program can execute the file access operation on the file to be called when a certain file needs to be called according to the preset operating logic.

In response to a file access operation by a user or an application program, the query module 301 queries whether there is a file to be accessed pointed to by the file access operation under a preset folder, and the preset folder is used for storing cleaned-up junk files. If the file to be accessed exists under the preset folder, the file to be accessed is restored to the original storage location from the preset folder by the recovery module 302, and then the file to be accessed is run from the original storage location by the access module 303 . If the file to be accessed does not exist in the preset folder, the file to be accessed is run through the access module 303 according to the storage path pointed to by the file access operation.

For details not covered in this embodiment, please refer to the description of the embodiment shown in FIG. 1 above, and details are not repeated here.

It should be noted that, in the embodiment of the terminal device illustrated in FIG. 3 above, the division of each functional module is only an example. In actual applications, it can be considered according to needs, such as the configuration requirements of corresponding hardware or the convenience of software implementation. The above function allocation is completed by different function modules, that is, the internal structure of the terminal device is divided into different function modules, so as to complete all or part of the functions described above. Moreover, in practical applications, the corresponding functional modules in this embodiment may be implemented by corresponding hardware, or may be completed by corresponding hardware executing corresponding software. Each of the embodiments provided in this specification can apply the above-mentioned description principle, which will not be described in detail below.

In the embodiment of the present invention, when a file access operation is detected, in response to the file access operation, the corresponding file is first searched under the preset folder specially used for storing junk files, if there is a file under the preset folder The file pointed to by the access operation will restore the file to the original storage location, which simplifies the file management steps, so that users no longer need to manually search for the files to be accessed as garbage, and also improves the flexibility of file management. Make file management more intelligent.

Please refer to FIG. 4 , which is a schematic structural diagram of a terminal device provided by another embodiment of the present invention. For ease of description, only parts related to the embodiment of the present invention are shown. The terminal device illustrated in FIG. 4 may be the execution subject of the file management method provided in the embodiments shown in FIG. 1 and FIG. 2 . The difference between the terminal device illustrated in Figure 4 and the terminal device in the embodiment shown in Figure 3 mainly lies in:

Further, query module 301 includes:

The database query module 3011 is configured to, in response to the file access operation, query whether there is a record of the file to be accessed in a preset database, and the database is used to record the information of the junk files cleaned up under the preset folder ;

Confirmation module 3012, configured to confirm that the file to be accessed exists under the preset folder if there is a record of the file to be accessed in the database, and if there is no record of the file to be accessed in the database, then confirm that the file to be accessed is Assume that the file to be accessed does not exist under the folder;

The terminal equipment also includes:

The record deletion module 401 is configured to delete the record of the file to be accessed in the database.

Specifically, through the database query module 3011, in response to the file access operation of the user or the application program, in the preset database, query whether there is a record of the file to be accessed, and the database is used for the record to be cleared to the preset folder information about junk files. If there is a record of the file to be accessed in the database, confirm that the file to be accessed exists under the preset folder through the confirmation module 3012, and then restore the file to be accessed from the preset folder to the original storage through the recovery module 302 location, and delete the record of the file to be accessed in the database through the record deletion module 401, and run the file to be accessed from the original storage location through the access module 303. If there is no record of the file to be accessed in the database, confirm that the file to be accessed does not exist under the preset folder through the confirmation module 3012, and then run the file to be accessed by the access module 303 according to the storage path pointed to by the file access operation. Access files.

Further, the terminal equipment also includes:

The scanning module 402 is used to regularly or periodically scan the files stored locally to obtain target files that meet preset file size conditions and time conditions;

A compression module 403, configured to compress the target file;

A cleaning module 404, configured to use the compressed target file as the junk file, clean it up to the preset folder, and delete the source file of the junk file;

The recording module 405 is configured to record the information of the junk file in the database.

Specifically, the scanning module 402 regularly or regularly scans files stored locally to obtain target files that meet preset file size conditions and time conditions. Then, the target file is compressed by the compression module 403, and the compressed target file is used as the junk file by the cleaning module 404, cleaned up to the preset folder, and the source file of the junk file is deleted. At the same time, the recording module 405 records the information of the junk file in the database.

Optionally, the scanning module 402 acquires the file size threshold and time threshold input by the user through the preset UI, and sets the parameter values of the file size condition and time condition according to the file size threshold and time threshold input by the user. And according to user-defined operations, set the storage directory to be scanned.

Further, the terminal equipment also includes:

The renaming module 406 is used to rename the compressed target file before the cleaning module 404 uses the compressed target file as the garbage file and cleans it under the preset folder;

Wherein, the junk file information recorded in the database includes: the original full path of the target file and the file name renamed after compression;

Then, the database query module 3011 is specifically used to query whether there is a target full path consistent with the full path of the file to be accessed in the database;

Confirmation module 3012, specifically for confirming that the file to be accessed exists under the preset folder if the full path of the target exists in the database, and confirming the preset folder if the full path of the target does not exist in the database The file to be accessed does not exist under

The recovery module 302 is specifically configured to obtain the compressed file corresponding to the associated file name from the preset folder according to the file name associated with the target full path in the database, and to obtain the compressed file corresponding to the target full path according to the target full path. After the file is decompressed, put it into the original storage location corresponding to the full path of the target, and delete the compressed file from the preset folder.

Specifically, the renaming module 406 renames the compressed target file before the cleaning module 404 cleans the compressed target file into the preset folder as the junk file. The garbage file information recorded in the database includes: the original full path of the target file and the file name renamed after compression. When performing a database query operation, the database query module 3011 is used to query whether there is a target full path consistent with the full path of the file to be accessed. If the target full path exists in the database, confirm that the file to be accessed exists under the preset folder through the confirmation module 3012, and then restore the file name associated with the target full path in the database through the recovery module 302, from the preset Obtain the compressed file corresponding to the associated file name under the folder, and according to the full path of the target, decompress the obtained compressed file and put it into the original storage location corresponding to the full path of the target, and from the preset folder Delete the compressed file, and at the same time, update the access time of the restored file to the current system time. If the target full path does not exist in the database, the confirmation module 3012 confirms that the file to be accessed does not exist in the preset folder.

Further, the scanning module 402 is specifically configured to regularly or periodically scan files stored in the storage space to obtain target files whose file size is larger than a preset file size and whose time difference between the last access time and the current system time is larger than the preset time difference.

Further, the terminal equipment also includes:

The cleaning module 404 is further configured to periodically delete files under the preset folder whose storage duration is longer than the preset duration, and clear the records of the regularly deleted files in the database.

Optionally, the cleaning module 404 determines how often the compressed files that have not been used in the preset folder are cleaned up according to user-defined operations on the UI interface. According to the determined result, the cleaning module 404 periodically deletes the files under the preset folder and the storage duration in the preset folder is longer than the preset duration, and clears the records of the regularly deleted files in the database.

Further, the attribute of the preset folder is a hidden file, and is set under the root directory.

For details not covered in this embodiment, please refer to the description of the embodiment shown in FIG. 1 and FIG. 2 above, and details will not be repeated here.

In the embodiment of the present invention, on the one hand, the purpose of saving space can be achieved by periodically compressing the files stored in the storage space that meet the preset file size conditions and time conditions and putting them into the preset folder; on the other hand, when When a file access operation is detected, in response to the file access operation, first query the database to see if there is a corresponding file in the preset folder specially used to store junk files, and if so, restore the file to the original storage location , simplifies the steps of file management, so that users no longer need to manually search for files to be accessed as garbage, and also improves the flexibility of file management, making file management more intelligent.

Please refer to FIG. 5 . FIG. 5 is a schematic structural diagram of a terminal device for performing the above-mentioned file management method provided by an embodiment of the present invention.

The terminal equipment described in this embodiment includes:

at least one input device 51 ; at least one output device 52 ; at least one processor 53 , such as a central processing unit; and, a memory 54 .

The aforementioned input device 51 , output device 52 , processor 53 and memory 54 are connected through a bus 55 .

Wherein, the input device 51 may specifically be a camera, a touch panel, a physical button or a mouse, and the like. The output device 52 may specifically be a display screen.

The memory 54 can be a high-speed random access memory (RAM, Random Access Memory) memory, or a non-volatile memory (non-volatile memory), such as a disk memory. The memory 54 is used to store a set of executable program codes, and the processor 53 is coupled to the memory 54. The above-mentioned input device 51, output device 52 and processor 53 are used to call the executable program codes stored in the memory 54, and perform the following operations:

The code is executed by the processor 53 to execute the file management method described in the embodiment shown in FIG. 1 and FIG. 2 .

Specifically, in response to the file access operation, query whether there is a file to be accessed pointed to by the file access operation under the preset folder, the preset folder is used to store the cleaned up junk files; if the preset folder is If the file to be accessed exists, restore the file to be accessed from the preset folder to the original storage location, and run the file to be accessed from the original storage location; if the file to be accessed does not exist under the preset folder, Then run the file to be accessed according to the storage path pointed to by the file access operation.

Further, the processor 53 also executes in response to the file access operation, in the preset database, inquires whether there is a record of the file to be accessed, and the database is used to record the garbage files cleaned up under the preset folder. information; if there is a record of the file to be accessed in the database, then confirm that the file to be accessed exists under the preset folder; if there is no record of the file to be accessed in the database, then confirm that there is no file under the preset folder There is the file to be accessed; and after restoring the file to be accessed from the preset folder to the original storage location, further comprising: deleting the record of the file to be accessed in the database.

Further, the processor 53 also executes regular or regular scans of locally stored files, obtains and compresses target files that meet preset file size conditions and time conditions; uses the compressed target files as the junk files, and cleans them up to the preset target files. Under the setting folder; delete the source file of the garbage file, and record the information of the garbage file in the database.

Further, before the processor 53 cleans the compressed target file under the preset folder as the junk file, it also performs renaming for the compressed target file; in response to the file access operation, in the database Query whether there is a target full path consistent with the full path of the file to be accessed; if the full path of the target exists in the database, then confirm that the file to be accessed exists under the preset folder, and according to the The file name associated with the path, obtain the compressed file corresponding to the associated file name from the preset folder; according to the full path of the target, decompress the obtained compressed file and put it into the original storage location corresponding to the full path of the target , and delete the compressed file from the preset folder; if the target full path does not exist in the database, then confirm that the file to be accessed does not exist in the preset folder.

Further, the processor 53 also executes periodic or regular scanning of the files stored in the storage space to obtain target files whose file size is larger than the preset file size and whose time difference between the last access time and the current system time is larger than the preset time difference.

Further, the processor 53 also executes to periodically delete the files under the preset folder whose storage duration is longer than the preset duration, and clears the records of the regularly deleted files in the database.

In the multiple embodiments provided in this application, it should be understood that the disclosed terminal device and method may be implemented in other ways. For example, the above-described embodiments are only illustrative. For example, the division of the modules is only a logical function division. In actual implementation, there may be other division methods. For example, multiple modules or components can be combined or can be Integrate into another system, or some features may be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication link shown or discussed may be through some interfaces, and the indirect coupling or communication link between modules may be in electrical, mechanical or other forms.

The modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or may be distributed to multiple network modules. Part or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional module in each embodiment of the present invention may be integrated into one processing module, each module may exist separately physically, or two or more modules may be integrated into one module. The above-mentioned integrated modules can be implemented in the form of hardware or in the form of software function modules.

If the integrated modules are realized in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the essence of the technical solution of the present invention or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-OnlyMemory), random access memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program codes.

It should be noted that, for the sake of simplicity of description, the aforementioned method embodiments are expressed as a series of action combinations, but those skilled in the art should know that the present invention is not limited by the described action sequence. Because of the present invention, certain steps may be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification belong to preferred embodiments, and the actions and modules involved are not necessarily required by the present invention.

In the foregoing embodiments, the descriptions of each embodiment have their own emphases, and for parts not described in detail in a certain embodiment, reference may be made to relevant descriptions of other embodiments.

The above is the description of the file management method and terminal equipment provided by the present invention. For those of ordinary skill in the art, according to the idea of the embodiment of the present invention, there will be changes in the specific implementation and application range. In summary, The contents of this description should not be construed as limiting the present invention.

Claims (10)

1. a kind of file management method, it is characterised in that methods described includes：

In response to file access operation, the lower text to be visited pointed to the presence or absence of the file access operation of inquiry default file folder Part, the default file is pressed from both sides for storing the garbage files being cleaned；

If there is the file to be visited under the default file folder, the file to be visited is pressed from both sides extensive from the default file It is multiple to run the file to be visited to original storage position, and from the original storage position；

If the default file folder is lower to be not present the file to be visited, the storage road pointed to according to the file access operation Footpath, runs the file to be visited.

2. file management method as claimed in claim 1, it is characterised in that described in response to file access operation, inquiry is pre- If the file to be visited pointed under file with the presence or absence of the file access operation, including：

In response to the file access operation, in default database, inquiry whether there is the record of the file to be visited, The database is used for the information for recording the garbage files being cleaned to the default file under pressing from both sides；

If there is the record of the file to be visited in the database, confirm that the default file folder is lower and wait to visit in the presence of described in Ask file；

If the record of the file to be visited is not present in the database, confirm that the default file folder is lower in the absence of described File to be visited；

Then, it is described to recover the file to be visited to original storage position from default file folder, in addition to：Institute State the record that the file to be visited is deleted in database.

3. file management method as claimed in claim 2, it is characterised in that methods described also includes：

The file that regular or timing scan is locally stored, obtains the target text for meeting default file size condition and time conditions Part is simultaneously compressed；

Using the file destination after compression as the garbage files, under cleaning to default file folder；

The source file of the garbage files is deleted, and records the information of the garbage files in the database.

4. file management method as claimed in claim 3, it is characterised in that

The file destination using after compression is as the garbage files, before clearing up to default file folder, including：For File destination after the compression is renamed；

The information of the garbage files recorded in the database includes：After the original complete trails of the file destination and compression again The filename of name；

Then, described in default database, inquiry whether there is the record of the file to be visited, including：

In the database, inquiry whether there is the target complete trails consistent with the complete trails of the file to be visited；

If there is the record of the file to be visited in the database, confirm that the default file folder is lower in the presence of described File to be visited, the file to be visited is recovered to original storage position from default file folder, including：

If there is the target complete trails in the database, confirm there is the text to be visited under the default file folder Part, the filename that the target complete trails according to the database is associated is closed from lower obtain of default file folder with described The corresponding compressed file of filename of connection；

It is corresponding described original by the target complete trails is put into after the compressed file decompression of acquisition according to the target complete trails Storage location, and delete the compressed file from default file folder；

If the record of the file to be visited is not present in the database, confirm to be not present under the default file folder The file to be visited, including：

If the target complete trails is not present in the database, confirm that the default file folder is lower in the absence of described to be visited File.

5. file management method as claimed in claim 3, it is characterised in that described periodically or in timing scan memory space to deposit The file of storage, obtains the file destination for meeting default file size condition and time conditions, including：

The file periodically or in timing scan memory space stored, obtains file size and is more than default file size and last access Time and the time difference of present system time are more than the file destination of preset time difference.

6. the file management method as described in any one of claim 1 to 5, it is characterised in that methods described also includes：

Periodically delete under the default file folder, the storage duration in default file folder is more than the file of preset duration, And the record for the file being periodically deleted is removed in the database.

7. the file management method as described in any one of claim 1 to 5, it is characterised in that the default file folder Attribute is hidden file, and is set under the root directory.

8. a kind of terminal device, it is characterised in that the terminal device includes:

Enquiry module, in response to file access operation, inquiry default file folder is lower to whether there is the file access operation The file to be visited pointed to, the default file is pressed from both sides for storing the garbage files being cleaned；

Recovery module, if for there is the file to be visited under default file folder, by the file to be visited from institute Default file folder is stated to recover to original storage position；

Access modules, for running the file to be visited from the original storage position；

The access modules, if being additionally operable to, the default file folder is lower to be not present the file to be visited, according to the file The store path that operation is pointed to is accessed, the file to be visited is run.

9. terminal device as claimed in claim 8, it is characterised in that

The enquiry module includes：

Database query module, in response to the file access operation, in default database, inquiry whether there is institute The record of file to be visited is stated, the database is used for the letter for recording the garbage files being cleaned to the default file under pressing from both sides Breath；

Module is confirmed, if for there is the record of the file to be visited in the database, confirming the default file folder Under there is the file to be visited, and if the record of the file to be visited is not present in the database, confirm described Default file folder is lower to be not present the file to be visited；

The terminal device also includes：

Record deletion module, the record for deleting the file to be visited in the database；

Scan module, the file being locally stored for regular or timing scan, it is timely that acquisition meets default file size condition Between condition file destination；

Compression module, for being compressed to the file destination；

Cleaning modul, for the file destination after compression as the garbage files, to be cleared up to default file folder, with And delete the source file of the garbage files；

Logging modle, the information for recording the garbage files in the database；

Renamer module, for regarding the file destination after compression as the garbage files, cleaning to institute in the cleaning modul It is that the file destination after the compression is renamed before stating under default file folder；

Wherein, the information of the garbage files recorded in the database includes：The original complete trails of the file destination and compression The filename renamed afterwards；

Then, the database query module, specifically in the database, inquiry whether there is and the file to be visited The consistent target complete trails of complete trails；

The confirmation module, if specifically for there is the target complete trails in the database, confirming the default file There is the file to be visited under folder, and if the target complete trails is not present in the database, confirm described default The file to be visited is not present under file；

The recovery module, the filename associated specifically for the target complete trails according to the database, from described pre- If obtaining compressed file corresponding with the filename of the association under file, and according to the target complete trails, it will obtain Compressed file decompression after be put into the corresponding original storage position of the target complete trails, and from default file folder Delete the compressed file；

Wherein, the scan module, specifically for the file stored in regular or timing scan memory space, obtains file size Time difference more than default file size and last access time and present system time is more than the poor file destination of preset time.

10. the terminal device as described in any one of claim 9, it is characterised in that the terminal device also includes：

The cleaning modul, is additionally operable to periodically delete under the default file folder, the storage duration in default file folder More than the file of preset duration, and the record for the file being periodically deleted is removed in the database；

The attribute of the default file folder is hidden file, and is set under the root directory.