WO2016197814A1

WO2016197814A1 - Junk file identification and management method, identification device, management device and terminal

Info

Publication number: WO2016197814A1
Application number: PCT/CN2016/083174
Authority: WO
Inventors: 黄勤波; 古幼鹏; 杨鹏
Original assignee: 中兴通讯股份有限公司
Priority date: 2015-11-18
Filing date: 2016-05-24
Publication date: 2016-12-15
Also published as: CN106708912A; CN106708912B

Abstract

Disclosed are a junk file identification and management method, an identification device, a management device and a terminal. The junk file identification method comprises: obtaining an actual value of each element in an element set of a stored object in a file system according to current actual target attribute data of the stored object; the elements being set according to the target attribute data of the stored object in the file system; and judging whether the stored object is a junk file according to the matching condition between the actual value of each element in the element set of the stored object and a threshold of a corresponding element in a pre-set junk file judgement policy.

Description

Garbage file identification and management method, identification device, management device and terminal

Technical field

This document relates to, but is not limited to, the field of computer technology, and in particular, to a garbage file identification and management method, an identification device, a management device and a terminal.

Background technique

With the development of science and technology, people are increasingly dependent on computers, mobile phones and other terminals, and their speed requirements are getting higher and higher. After a period of use, more and more junk files are generated, which causes the terminal to have such problems as stuck, memory, and insufficient internal and external storage space, which greatly affects the use of the terminal. In order to restore the running speed of the terminal, it is necessary to clean the junk files of the terminal and release more storage space.

In the related art, the commonly used junk file identification method is: the user selects a file to be judged, and then adds the file to a certain detection application, and the detection application uses the preset garbage judgment model to identify the file added by the user. Not a junk file. If it is identified that a file is a junk file, the detection application suggests to the user to clean up the junk file. In the cleaning method of the related art, the preset garbage judgment model is agnostic to the user, and the model is unchanged during use, but many files in the terminal are different according to the usage mode and the use time. The degree of garbage will change. The method based on the preset model to identify the junk file is less adaptable, which will produce errors and reduce the accuracy of the judgment.

Summary of the invention

The following is an overview of the topics detailed in this document. This Summary is not intended to limit the scope of the claims.

The embodiment of the invention provides a garbage file identification and management method, a recognition device, a management device and a terminal, and solves the problem that the method for identifying a junk file in the related art has poor adaptability and low accuracy.

The embodiments of the present invention adopt the following technical solutions.

A method for identifying junk files, comprising:

Obtaining an actual value of each element in the storage object feature set according to the current target attribute data of the storage object in the file system; the element is set according to target attribute data of the storage object in the file system;

The storage object is determined to be a junk file according to the actual value of each element in the storage target element set and the threshold matching condition of the corresponding element in the preset junk file determination policy.

Optionally, before the obtaining the actual value of each element in the storage object feature set according to the current target attribute data of the storage object in the file system, the method further includes:

Obtaining a feature set including at least one element, and setting the junk file judgment policy according to a threshold of at least one of the elements.

Optionally, the storage object comprises: a file and/or a folder.

Optionally, the target attribute data includes operation attribute data and/or size attribute data, the element including an operation attribute element set according to the operation attribute data and/or a size attribute element set according to the size attribute data.

Optionally, when the set of stored object elements includes an operation attribute element, the threshold matching case includes: whether an actual value of the operation attribute element matches a threshold of the operation attribute element;

When the storage object element set includes a size attribute element, the threshold matching case includes whether an actual value of the size attribute element matches a threshold of the size attribute element.

Optionally, the target attribute data further includes display status attribute data, and the element further includes a status display element set according to the display status attribute data.

Optionally, when the storage object feature set includes a status display element, the threshold matching situation includes: whether an actual value of the status display element matches a threshold of the status display element.

Optionally, when the target attribute data includes operation attribute data, the operation attribute data includes at least one of an operation type, an operation time, and an operation time interval, and the operation attribute element includes an operation type element, an operation time element, and At least one of the operational time interval elements;

When the target attribute data includes the size attribute data, the size attribute data includes at least one of a current size of the storage object, a size change amount of the storage object within the preset time period, and a space size of the storage area where the storage object is located; The size attribute element includes a current size element of the storage object, The storage object size change amount element and at least one of the space size elements of the storage area in which the storage object is located.

Optionally, the method for identifying the junk file further includes: receiving a policy modification instruction sent by the user, and modifying the junk file judgment policy according to the policy modification instruction.

Optionally, the policy modification instruction includes an element adjustment instruction for adjusting an element of the junk file judgment policy; and the modifying the junk file judgment policy includes: concentrating the element according to the element adjustment instruction The elements are updated, and the junk file judgment strategy is updated according to the updated feature set;

Or the policy modification instruction includes an element threshold adjustment instruction for adjusting a threshold of an element of the junk file judgment policy; and the modifying the junk file judgment policy includes: corresponding to the element tune threshold The threshold of the element is updated, and the junk file judgment policy is updated according to the updated threshold.

A garbage file management method, comprising:

Identifying the junk file by the above method of identifying the junk file;

Manage the junk files.

Optionally, the managing the junk file includes:

Delete the junk file;

Or presenting the junk file to the user for confirmation, and managing the junk file according to the first confirmation instruction of the user;

Or presenting the junk file and the junk file judging policy to the user for confirmation, and managing the junk file according to the second confirmation instruction of the user.

A junk file identification device comprising:

An analysis module configured to obtain an actual value of each element in the storage object feature set according to a current target attribute data of the storage object in the file system; the element is stored according to a file system The object's target attribute data is set;

The judging module is configured to determine whether the storage object is a junk file according to an actual value of each element in the storage target element set and a threshold matching condition of a corresponding element in a junk file judging policy set in advance.

Optionally, the garbage file identification device further includes:

The policy setting module is configured to acquire a feature set including at least one element, and set the junk file judgment policy according to a threshold of at least one of the elements.

Optionally, the garbage file identification device further includes:

a receiving module, configured to receive a policy modification instruction sent by a user;

And modifying the module, configured to modify the junk file judgment policy according to the policy modification instruction.

Optionally, the receiving module includes a first receiving submodule configured to receive an element adjustment instruction, where the element adjustment instruction includes a policy modification instruction for adjusting an element of the junk file determining policy; the modifying module The first modification submodule is configured to update the elements in the feature set according to the element adjustment instruction, and update the junk file determination policy according to the updated feature set;

Or the receiving module includes a second receiving submodule configured to receive an element threshold adjustment instruction, where the element threshold adjustment instruction includes a policy modification instruction for adjusting a threshold of an element of the junk file determination policy; The modification module includes a second modification submodule, configured to update the threshold of the corresponding element according to the element adjustment threshold instruction, and update the junk file determination policy according to the updated threshold.

A junk file management device, comprising:

The garbage file identification device described above is configured to identify the junk file in the terminal file system;

A management module configured to manage the junk file.

Optionally, the management module includes a management submodule:

Set to delete the junk file;

Or setting to present the junk file to the user for confirmation, and managing the junk file according to the first confirmation instruction of the user;

Or setting to present the junk file and the junk file judging policy to the user for confirmation, and managing the junk file according to the second confirmation instruction of the user.

A terminal comprising the above-described junk file identification device and the above-described junk file management device; the junk file identification device being included in the junk file management device; the junk file identification device being set to be garbage in a terminal file system The file is identified; the junk file management device is configured to manage the junk file identified by the junk file identification device.

A computer readable storage medium storing computer executable instructions for performing the above method. Beneficial effects:

The solution provided by the embodiment of the present invention can utilize the target attribute data of the storage object in the file system, set a feature set including at least one element according to the target attribute data, and set a garbage that can determine the junk file according to the threshold value of the element. The file judgment strategy, and then according to the actual target attribute data of the storage object in the file system, obtain the actual value of the element, and determine whether the storage object is a junk file according to the actual value of each element in the storage object element set and the junk file judgment policy. The solution provided by the embodiment of the present invention has higher judgment accuracy, and the garbage file judgment strategy adopted by the embodiment of the present invention is set according to the element set by the target attribute data of the actual storage object, and may be different according to the selected element. The solution provided by the embodiment of the present invention has good adaptability.

In order to improve the accuracy of the judgment and make better use of the existing resources, the optional solution of the embodiment of the present invention selects the operation attribute data and/or the size attribute data in the target attribute data of the storage object. As an important data source for setting elements, and setting the operation attribute elements and size attribute elements separately based on these two data.

In addition, the requirements of the junk file judging policy may be different for different users. In order to adapt to the actual needs and improve the judging accuracy, the optional solution of the embodiment of the present invention may further modify the junk file judging policy according to the policy modification command sent by the user.

Other aspects will be apparent upon reading and understanding the drawings and detailed description.

BRIEF abstract

1 is a schematic flowchart of a garbage file identification method according to Embodiment 1 of the present invention;

2 is a schematic flowchart of a garbage file identification method according to an alternative embodiment of the present invention;

3 is a schematic flowchart of a garbage file management method according to Embodiment 2 of the present invention;

4 is a schematic diagram of a terminal according to Embodiment 3 of the present invention;

FIG. 5 is a schematic diagram of a junk file identification apparatus according to a third embodiment of the present invention; FIG.

6 is a schematic diagram of a junk file management apparatus according to a third embodiment of the present invention;

7 is a schematic diagram of a terminal according to an example of Embodiment 3 of the present invention;

FIG. 8 is a schematic flowchart of a method for cleaning a junk file according to Embodiment 4 of the present invention.

Embodiments of the invention

During the use of the terminal, the system or application will generate corresponding files or folders, and these files or folders have their own corresponding attribute data. Run the system or application, the attribute data of the corresponding file or folder will also be updated, such as reading, writing, modifying, etc., and other attribute data corresponding to the data and files related to these operations will be recorded by the terminal. The embodiment is based on the in-depth mining of these raw data to identify junk files.

Embodiment 1:

This embodiment provides a method for cleaning a junk file that can more accurately determine and clean the junk file, improve the judging efficiency, and reduce the judging time. For the method, refer to FIG. 1, including steps S102-S103:

S102: Obtain an actual value of each element in the storage object feature set according to the current actual target attribute data of the storage object in the file system; the element is set according to target attribute data of the storage object in the file system;

S103: Determine whether the storage object is a junk file according to the actual value of each element in the storage object element set and the threshold matching condition of the corresponding element in the preset junk file judgment policy.

Optionally, the method is as shown in FIG. 2, and before step S102, the method may further include:

S101: Acquire a feature set including at least one element, and set the junk file judgment policy according to a threshold of at least one element.

Optionally, the storage object in the file system includes files and/or folders, and may also include data stored in the terminal in other forms, which is gradually generated by the system or different applications during use, and the time is longer. Long, the number and size of files will increase, which will affect the speed of the terminal. In order to restore the operation speed of the terminal and improve the user experience, files and/or folders need to be cleaned up.

In order to improve the judgment accuracy of the garbage object and to make full use of the existing data, the present embodiment analyzes the garbage level of the storage object based on the data index of each aspect of each storage object in the file system, and of course stores the data of the object. There are various indicators, and not all data is helpful for judgment. Therefore, the present embodiment selects the target attribute data of the storage object as a basis.

Optionally, the target attribute data selected in this embodiment includes but is not limited to one or more of the following: operation attribute data, size attribute data, and display state attribute data, and the operation attribute data includes one or more related to the storage object operation. Data, for example, data related to the storage object operation type, data related to the operation time of the storage object, and data related to the operation time interval of the storage object; the size attribute data includes data related to the size of the storage object, For example, the current size of the storage object in the storage area, the size of the storage area where the storage object is located, and the size of the storage object in a certain period of time. If the storage object is a folder, the size attribute data herein may also include a folder. The number of child files; the display state attribute data is data related to one or more display states of the storage object, such as the originator of the storage object, the format of the storage object (is a file/folder), whether the storage object is readable, Whether the storage object is writable, the storage object is displayed/hidden Tibetan and so on.

Correspondingly, the elements set according to the target attribute data in S101 respectively include one or more of the following: an operation attribute element set according to the operation attribute data, a size attribute element set according to the size attribute data, and a status display according to the display status attribute data. Element; Optionally, none of the above three elements can be separately selected for use in formulating a junk file judgment strategy to determine junk files.

Optionally, the operation attribute element and/or the size attribute element are selected as the basic element to formulate a junk file judgment strategy, and when the storage object element set includes the operation attribute element, the threshold matching situation includes: whether the actual value of the operation attribute element is The threshold of the operational attribute element matches;

When a storage object feature set includes a size attribute element, the match case includes whether the actual value of the size attribute element matches the threshold of the size attribute element.

Optionally, the operation attribute element of the embodiment includes an operation type element, an operation time element, and an operation time interval element, and the operation type element includes all operation actions of the monitored file, such as deleting, creating, moving, copying, and opening. , modification, read and write permission modification, etc.; operation time elements include the time corresponding to each of the above operations, such as the time of creating the file, the time to modify the file, etc.; the operation time interval element can be regarded as derived from the operation time For the time period, the time interval between the current modification time and the current time interval, the time interval between the last time the file was opened, and the current time interval, etc., when setting the junk file judgment policy according to the above elements, it is necessary to set a threshold for the corresponding element, and the threshold value of the element refers to It is the condition that the selected element is satisfied. The threshold here can be not only a specific value, but also a message indicating a certain state.

After selecting the good elements, the junk file judgment strategy can be set according to the threshold of the element. The selected element is the above operation time element, then the threshold is the time-related value, the selected element is the operation type element, and the threshold is an operation type. The garbage policy based on the above operational attribute elements includes the following methods:

First, the operation type element is selected, and the junk file judgment policy can be set to determine the file as a junk file when it is detected that the type of operation performed on a file is deleted.

Second, select the operation time element, the junk file judgment strategy can be set to a certain operation time of a file before a certain time point, determine the file as a junk file, for example, the setting can be, the file modification time is all in August 2015 Before the 8th, the file was determined to be a junk file. Match above It means that if the actual modification time of the file is August 6, 2015, the actual value of the modification time of the file matches the threshold of the modification time in the junk file judgment policy.

Third, select the operation time interval element, the junk file judgment strategy can be limited to a certain operation distance of a file from the current maximum time interval, beyond the interval, the file is determined to be a junk file, for example, the setting may be, the file last accessed time If the current duration is more than 10 days, the file is determined to be a junk file. It can also be set within one week of the current time. The effective activity time of the owner of the file is less than 30s, and the file is determined to be a junk file.

4. Select at least two elements of the operation type element, the operation time element, and the operation time interval element to set the garbage judgment processing, such as the modification time of the file before August 8th, 2015 and the time when the file was last accessed from the current time The duration is more than 10 days, and the file is judged to be a junk file. Of course, it is also possible to determine that the file is a junk file when any of the elements match the threshold.

Optionally, the size attribute element of the embodiment includes a storage object current size element, a storage object size change quantity element, and a size element of the storage area where the storage object is located, and the storage element current size element includes a storage object size, if The storage object is a folder, the element refers to the overall size of the folder; the storage object size change amount element includes the amount of change of the size of the storage object in a certain period of time, and may be incremented or deviated; the storage area where the storage object is located The size element includes the total size of the storage area where the storage object is located, and the threshold corresponding to the size element is a numerical condition that the amount of change of a certain size or size satisfies.

Among the above-mentioned several size attribute elements, the garbage determination condition set only according to the size element of the storage area in which the storage object is located may be combined with the garbage determination condition determined according to other elements to determine the junk file, and the garbage is determined according to the above-mentioned size attribute element. The strategy includes the following ways:

First, select the current size of the storage object, junk file judgment strategy can be: a single file cumulative write size exceeds 1G, or the overall size of the folder exceeds 800M.

Second, the storage object size change amount element, the junk file judgment strategy can be set as: the storage object size change amount exceeds a certain value within a certain period of time, and is determined to be a junk file, for example, may be, within 7 days according to the current time, a file The increment is over 300M and it is determined that the file may be a junk file. The above matching means that if the file has an actual size increment of 200M within 7 days from the current time, the actual value of the storage object size change amount element of the file and the storage object size change amount element in the junk file judgment policy. The thresholds are not matched.

3. Select any one or all of the storage object current size element and the storage object size change quantity element, and combine with the size element of the storage area where the storage object is located to set the junk file judgment strategy.

If the accumulated write size of a single file exceeds 1G, and the remaining space of the partition where the file is located is less than 10%, and the file size is in the top 10 (top ten) of the partition, the file is judged to be a junk file;

Or within 7 weeks from the current, the increment of a file exceeds 300M, and the remaining space of the file is less than 10%, and the file size accounts for top 10 in the partition, and the file is judged to be a junk file;

Or within 7 weeks from the current, the increment of a file exceeds 300M, and the cumulative write size of the file exceeds 1G, and the remaining space of the file is less than 10%, and the file size accounts for top10 in the partition, and the judgment is made. The file is a junk file.

Optionally, when the storage object element set of the embodiment includes the status display element, the matching situation includes: whether the actual value of the status display element matches the threshold of the status display element.

Optionally, the status display element of the embodiment includes a format element, indicating whether the storage object is a file or a folder; a readable attribute element indicating whether the file is readable; a writable attribute element indicating whether the file is writable; a founder element, Represents the originator of the storage object; shows/hides the feature, indicating whether the storage object is hidden or displayed.

According to the above state display element system, the garbage policy includes the following methods:

First, only select the format elements, the junk file judgment strategy can be set to, the storage object is a file, or the storage object is a folder.

Second, only select the readable attribute element or the writable attribute element, the junk file judgment strategy can be set to, the storage object can be read or the storage object can be written, and the file may be a junk file.

Third, only the founder element, the junk file judgment strategy can be set to, the founder of the storage object is an application or system that is prone to garbage, such as the file founder is QQ, WeChat, Weibo and other applications that are prone to garbage. The above matching means that if the originator of the file is QQ, the actual value of the founder element of the file matches the threshold of the founder element in the junk file judgment policy.

4. Only select/hide elements, the junk file judgment policy can be set to, if the file or folder is a hidden file, the file or folder is not determined as a junk file.

In addition, the garbage file judgment policy set according to the above four state display element settings may be selected to obtain a new junk file judgment strategy.

According to one or more of the three categories of elements: the operation attribute element, the size attribute element, and the status display element, the prepared junk file judgment strategy can be freely combined into a new junk file judgment strategy; optionally, according to the status display The junk file judgment strategy for element development is used together with the junk file judgment strategy based on other factors.

The junk file judging policy based on the operation attribute element and the size attribute element may be a set of junk judgment conditions set according to the respective sub-elements, for example, the read/write time of a file has been more than 7 days, and the file is accumulated. If the size of the file reaches or exceeds 1 GB, and the owner (application or system) of the file is active for less than or equal to 30 s in a week, the file is determined to be a junk file.

According to the operation attribute element and the status display element, the junk file judgment strategy may be that the last operation time of a file is before October 30, the file read/write time interval has been more than 7 days, and the file is a non-hidden file. The file is determined to be a junk file.

The garbage file judgment strategy based on the three elements can be: the last operation time of a file is before October 30; and the file size exceeds 1G; and the remaining space of the file partition is less than 10%; and the file is within one week. The increment is more than 800M, and the file is determined to be a junk file.

Of course, in addition to the above attribute data, the elements of this embodiment can also be set according to other data available for data mining. In addition to the above examples, other junk file judgment strategies can also be developed.

Optionally, if the junk file judging policy is set by the above manner, more than one selected element is selected, and the set junk file judging strategy is more than one. For a certain storage object, not all the actual values of the elements match. The junk file judges the threshold of the elements in the strategy, but only matches a part. Then, a judgment rule can be set at this time, and the junk file is judged according to the actual matching condition. The judging rule may be that the storage object element has elements in the set. The actual value is matched with the threshold of the corresponding element in the junk file judgment strategy. Of course, these elements must include at least one of the above-mentioned operation attribute element and size attribute element, and the number of matching elements is greater than the preset. A value is determined to determine that the storage object is a junk file. For example, the selected elements are the operation time interval element, the operation time element, the storage object current size element, and the status display element. The junk file judgment strategy set according to these elements is: 1. The file last accessed time is longer than 10 days from the current time. 2, the size of the file exceeds 1G, 3, the founder of the storage object is an application or system that is prone to garbage, such as the file founder is QQ, WeChat, Weibo, etc. The application, 4, file modification time is all before August 8, 2015. The junk file judging policy may be set such that the actual value of the element in the storage object feature set matches at least the threshold of the element in the strategy 1, or the actual value of the element in the storage object element set matches at least the threshold of the element in the strategy 2; In addition, the number of matching elements in the storage target element set exceeds two, and it is determined that the storage object is a junk file.

The junk file judging policy set in the embodiment S101 may be preset on the terminal, so the S101 may also directly obtain the preset junk file judging policy.

The attribute data of storage objects on different terminals are different, so different users may have different requirements for junk file judgment policies. In order to meet the requirements of the user and improve the adaptability of the present invention to different terminals, optionally, in this embodiment, the method further includes:

The policy modification instruction sent by the user is received, and the junk file judgment policy is modified according to the modification instruction of the policy.

Optionally, the policy modification instruction may include a component adjustment instruction or a threshold adjustment instruction for adjusting an element of the junk file judgment policy; and the policy modification instruction is a component adjustment instruction, the junk file judgment strategy The modifying includes: updating the elements in the feature set according to the element adjustment instruction, updating the junk file judgment strategy according to the updated feature set; updating the element in the feature set includes deleting or adding the element in the feature set, In the junk file judgment strategy, the corresponding junk file judgment strategy is deleted or added accordingly, and when the current target attribute data of the storage object is obtained, the acquired target attribute data also has corresponding correspondingly as the element is added or deleted. Delete or increase. For example, when the feature element deletes the size element of the storage area where the storage object is located, the junk file judgment policy set according to the element in the junk file judgment policy is also deleted, and when the target attribute data of the storage object is obtained, the storage object is not obtained. The size data of the storage area.

The policy modification instruction is a threshold adjustment instruction for adjusting a threshold of an element of the junk file judgment policy, and the modifying the junk file judgment policy includes: updating a threshold of the corresponding element according to the threshold adjustment instruction, according to the updated The threshold update policy of the junk file, for example, the threshold adjustment instruction indicates that the threshold of the policy of “the size of the file exceeds 1G” is modified to 900M, and the updated junk file determination policy is “the size of the file exceeds 900M”.

By adopting the junk file identification method of the embodiment, the original attribute data on the terminal is fully utilized. According to the attribute data, a feature set containing at least one feature is set, and a junk file judgment strategy is set according to the elements, and then the actual value of the element is obtained, and the actual value of the element is obtained, and then according to the actual value. And the threshold matching of the corresponding elements in the junk file judgment strategy, and determining whether the storage object is a junk file, such a judging method has good adaptability and high judgment accuracy.

Embodiment 2:

This embodiment provides a garbage management method for managing the identified junk file. Referring to FIG. 3, the method includes steps S201 to S202:

S201: Identify the junk file by using the junk file identification method described in the first embodiment;

S202: Manage garbage files.

After the junk file is identified, the junk file needs to be processed, but the junk file may have files that the user needs, such as videos or photos that have not been read for a long time. Although it is judged as junk files, it may actually be If the user needs to keep it, if it is cleaned up, the user data will be lost. In order to avoid this situation, the embodiment provides the user with different management modes of the junk file for the user to select. The step S202 includes:

The first type, directly delete the junk file;

Secondly, the junk file is presented to the user for confirmation, and the junk file is managed according to the first confirmation instruction of the user, including: if the first confirmation instruction is to delete the file, the junk file is directly deleted, if the first confirmation command is If the file is not deleted, the file is renamed to a non-spam file.

Thirdly, the junk file and the junk file judging policy corresponding to the junk file are presented to the user for confirmation, and the junk file is managed according to the second confirmation instruction of the user, including: if the second confirming instruction is to delete the file, directly The junk file is deleted, and if the second confirmation command is not deleting the file, the file is reclassified as a non-spam file.

If the user selects the second or third management method for the junk file mentioned above, after the junk file identification is completed, the junk file may be marked as the file to be cleaned, and the identified junk file may be processed after the certain rules are met. Processing, in addition to receiving the confirmation command sent by the user, the rule may also be other conditions, such as a preset deletion period, and the terminal is configured to delete according to a preset. Periodically delete files scanned during the deletion period, or set the rule to delete junk files in the area when the remaining space of the storage object is less than a certain threshold.

This embodiment provides users with different management methods to manage the identified junk files, which can meet the different needs of users and enhance the user's sense of use, especially for presenting junk files and junk file judgment strategies for users, so that users can intuitively understand The junk file and its decision strategy help the user finally determine which files need to be deleted.

Embodiment 3:

This embodiment provides a terminal 3. Referring to FIG. 4, the terminal includes:

The junk file identification device 31 is configured to identify the junk file in the terminal file system;

The junk file management device 32 is configured to manage the junk files identified by the junk file identification device;

The junk file identification device 31 is included in the junk file management device 32.

The junk file discriminating device 31 and the junk file managing device 32 will be described in detail below with reference to Figs.

The junk file identification device 31, see Fig. 7, includes:

The analyzing module 312 is configured to obtain an actual value of each element in the storage object element set according to the current target attribute data of the storage object in the file system; the element is set according to the target attribute data of the storage object in the file system;

The determining module 313 is configured to determine whether the storage object is a junk file according to the actual value of each element in the storage target element set and the threshold matching condition of the corresponding element in the preset junk file judgment policy;

The junk file identification device 31 may further include:

The policy setting module 311 is configured to acquire a feature set including at least one element, and set the junk file determination policy according to a threshold of the at least one element.

Optionally, the storage objects in this embodiment include files and/or folders.

This embodiment utilizes data pointers of one or more aspects of a storage object in a file system. The data may be recorded when the storage object is created, or may be related information recorded during use. This information is very complicated. In order to make better use of the information, the storage object is selected in this embodiment. The target attribute data is used.

Optionally, the target attribute data includes operation attribute data and/or size attribute data, and the element includes an operation attribute element set according to the operation attribute data and/or a size attribute element set according to the size attribute data.

Optionally, the target attribute data further includes display status attribute data, and correspondingly, the element further includes a status display element set according to the display status attribute data.

The content of the above elements and the method of setting the junk file judging policy according to the elements are referred to the first embodiment of the present invention.

The attribute data of storage objects on different terminals are different, so different users may have different requirements for junk file judgment policies. In order to meet the needs of the user and improve the adaptability of the present invention to different terminals, the garbage file identifying apparatus 31 of the present embodiment further includes:

The receiving module 314 is configured to receive a policy modification instruction sent by the user, and the modifying module 315 is configured to modify the junk file judgment policy according to the policy modification instruction.

Optionally, the policy modification instruction may include a component adjustment instruction or a threshold adjustment instruction; the receiving module 314 includes a first receiving submodule 3141 configured to receive an element adjustment instruction, where the element adjustment instruction is an element for determining a junk file policy The policy modification instruction to make adjustments. Correspondingly, the modification module 315 includes a first modification sub-module 3151: configured to update elements in the feature set according to the element adjustment instruction, and update the policy according to the updated feature set; the first modification sub-module 3151 updates the elements in the feature set Including, deleting or adding the elements in the feature set, correspondingly deleting or adding the corresponding junk file judgment strategy in the junk file judgment strategy, and correspondingly, the analysis module 312 acquires the target when acquiring the current target attribute data of the storage object. Attribute data will also be deleted or added as the feature is added or deleted. For example, when the feature element deletes the size element of the storage area where the storage object is located, the junk file judgment policy set according to the element in the junk file judgment policy is also deleted, and when the target attribute data of the storage object is obtained, the storage object is not obtained. The size data of the storage area.

Or the receiving module 314 includes a second receiving submodule 3142, configured to receive a component adjustment instruction, The element threshold adjustment instruction is a policy modification instruction for adjusting a threshold of an element of the junk file determination policy. Correspondingly, the modification module 315 includes a second modification sub-module 3152: configured to update elements in the feature set according to the element adjustment instruction, and update the policy according to the updated feature set; for example, the second modification sub-module 3152 according to the size of the file The threshold of the policy exceeding 1G is modified to a threshold modification command of 900M, and the original junk file judgment policy is updated to "the file size exceeds 900M."

The junk file management device 32, see Fig. 6, includes:

The management module 321 is configured to manage the junk files.

Optionally, in order to provide the user with a different method for managing the junk file, the management module 321 of the embodiment further includes a management submodule 3211:

Set to delete junk files directly;

Or set to present the junk file to the user for confirmation, and manage the junk file according to the first confirmation instruction of the user. If the first confirmation instruction is to delete the file, the junk file is directly deleted, if the first confirmation instruction is not deleting the file. , the file is changed to a non-spam file.

Or set to present the junk file and the junk file judging policy corresponding to the junk file to the user for confirmation, and manage the junk file according to the second confirmation instruction of the user, and if the second confirmation command is to delete the file, directly delete the junk. File, if the second confirmation command is to not delete the file, the file is changed to a non-spam file.

7 is a schematic diagram of an example of a terminal 3 including the modules, sub-modules involved in the alternative of the junk file identification device 31 described above, and modules involved in the alternative of the junk file management device 32. , sub-modules.

With the terminal of the embodiment, the elements set according to the attribute data of the storage object can be acquired, and then the junk file judging policy is set according to the threshold values of the elements, and the actual elements of the storage object are analyzed according to the obtained attribute data of the storage object. The value, according to the actual value and the threshold matching condition of the corresponding element in the junk file judgment strategy, determines whether the storage object is a junk file, and then selects the management method to manage the junk file, and the terminal of the embodiment can quickly and accurately identify the junk. File, and then manage the junk files according to the management mode selected by the user, so that the judgment is accurate Both the certainty and the sense of user use have improved.

Embodiment 4:

In this embodiment, a method for judging whether a file is a junk file is taken as an example to describe a method for cleaning a junk file. In this embodiment, the junk file judging policy is preset on the terminal, as shown in FIG. The process includes the following steps S401 to S409:

S401: When a file is accessed, record related data of the file;

These data include, but are not limited to, the read/write type of the file, the read/write time, the read/write size, and the size change of the file after reading and writing.

S402: Acquire a feature set, where the elements in the feature set are set according to related data of the recorded file;

S403: Acquire a junk file judgment strategy;

S404: Obtain current target attribute data of the file.

S405: Analyze an actual value of the element based on the current target attribute data of the file;

S406: judging whether the file is a junk file according to the junk file judgment strategy and the actual value of the element, if the judgment result is yes, proceed to S407, and if the judgment result is no, return to S401;

S407: Presenting the junk file and the corresponding junk file judgment strategy to the user;

S408: receiving the user's instruction, if the user's instruction is to delete the junk file, go to S409, if the user's instruction is not to delete the file, go to S410;

S409: Delete the junk file selected by the user;

S410: The junk file is changed to a non-spam file.

Embodiment 5:

A computer readable storage medium storing computer executable instructions for performing the method of Embodiment 1 or Embodiment 2 above.

Obviously, those skilled in the art should understand that the above modules or steps of the embodiments of the present invention can be implemented by a general computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in a storage medium (ROM/RAM, diskette, optical disk) by a computing device, and in some cases The steps shown or described may be performed in an order different than that herein, or they may be separately fabricated into an integrated circuit module, or a plurality of modules or steps thereof may be implemented as a single integrated circuit module. Therefore, embodiments of the invention are not limited to any particular combination of hardware and software.

Industrial applicability

The solution provided by the embodiment of the present invention has a high judgment accuracy, and the garbage file judgment strategy adopted by the embodiment of the present invention is set according to the element set by the target attribute data of the actual storage object, and may be based on the selected element. The solution provided by the embodiment of the present invention has good adaptability.

Claims

A method for identifying junk files, comprising:

Obtaining an actual value of each element in the storage object feature set according to the current target attribute data of the storage object in the file system; the element is set according to target attribute data of the storage object in the file system;

The storage object is determined to be a junk file according to the actual value of each element in the storage target element set and the threshold matching condition of the corresponding element in the preset junk file determination policy.
The junk file identification method according to claim 1, wherein the obtaining the actual value of each element in the storage object element set according to the current target attribute data of the storage object in the file system further comprises:

Obtaining a feature set including at least one element, and setting the junk file judgment policy according to a threshold of at least one of the elements.
The junk file identifying method according to claim 1, wherein said storage object comprises: a file and/or a folder.
The junk file identifying method according to claim 1, wherein said target attribute data includes operation attribute data and/or size attribute data, said element including an operation attribute element set according to said operation attribute data, and/or The size attribute element set by the size attribute data.
The junk file identifying method according to claim 4, wherein, when the set of storage object elements includes an operation attribute element, the threshold matching case includes: whether an actual value of the operation attribute element matches a threshold of the operation attribute element ;

When the storage object element set includes a size attribute element, the threshold matching case includes whether an actual value of the size attribute element matches a threshold of the size attribute element.
The junk file identifying method according to claim 4, wherein the target attribute data further includes display state attribute data, and the element further includes a status display element set according to the display state attribute data.
The junk file identifying method according to claim 6, wherein when the set of storage object elements includes a status display element, the threshold matching case includes: whether an actual value of the status display element matches a threshold of the status display element .
The junk file identifying method according to claim 4, wherein, when the target attribute data includes operation attribute data, the operation attribute data includes at least one of an operation type, an operation time, and an operation time interval, the operation attribute The feature includes at least one of an operation type element, an operation time element, and an operation time interval element;

When the target attribute data includes the size attribute data, the size attribute data includes at least one of a current size of the storage object, a size change amount of the storage object within the preset time period, and a space size of the storage area where the storage object is located; The size attribute element includes at least one of a storage object current size element, a storage object size change amount element, and a spatial size element of a storage area in which the storage object is located.
The junk file identification method according to any one of claims 1 to 8, further comprising: receiving a policy modification instruction sent by the user, and modifying the junk file judgment policy according to the policy modification instruction.
The junk file identification method according to claim 9, wherein the policy modification instruction includes an element adjustment instruction for adjusting an element of the junk file judgment policy; and the modifying the junk file judgment policy includes: The element adjustment instruction updates an element in the feature set, and updates the junk file determination policy according to the updated feature set;

Or the policy modification instruction includes an element threshold adjustment instruction for adjusting a threshold of an element of the junk file judgment policy; and the modifying the junk file judgment policy includes: corresponding to the element tune threshold The threshold of the element is updated, and the junk file judgment policy is updated according to the updated threshold.
A garbage file management method, comprising:

Identifying a junk file by the method for identifying a junk file according to any one of claims 1 to 10;

Manage the junk files.
The junk file management method according to claim 11, wherein said managing the junk file comprises:

Delete the junk file;

Or presenting the junk file to the user for confirmation, according to the user's first confirmation instruction The junk file is managed;

Or presenting the junk file and the junk file judging policy to the user for confirmation, and managing the junk file according to the second confirmation instruction of the user.
A junk file identification device comprising:

The analyzing module is configured to obtain an actual value of each element in the storage object element set according to the current target attribute data of the storage object in the file system; the element is set according to target attribute data of the storage object in the file system;

The judging module is configured to determine whether the storage object is a junk file according to an actual value of each element in the storage target element set and a threshold matching condition of a corresponding element in a junk file judging policy set in advance.
The junk file identification device of claim 13 further comprising:

The policy setting module is configured to acquire a feature set including at least one element, and set the junk file judgment policy according to a threshold of at least one of the elements.
The junk file identifying apparatus according to claim 13, wherein said target attribute data includes operation attribute data and/or size attribute data, said element including an operation attribute element set according to said operation attribute data, and/or The size attribute element set by the size attribute data.
The junk file discriminating device according to claim 15, wherein said target attribute data further includes display state attribute data, and said element further includes a status display element set in accordance with said display state attribute data.
The junk file identification device according to any one of claims 13 to 16, further comprising:

a receiving module, configured to receive a policy modification instruction sent by a user;

And modifying the module, configured to modify the junk file judgment policy according to the policy modification instruction.
The junk file identifying apparatus according to claim 17, wherein said receiving module comprises a first receiving submodule configured to receive an element adjustment instruction, said element adjustment instruction including an element for determining said junk file judging policy The modified policy modification instruction includes: the first modification submodule, configured to update the elements in the feature set according to the element adjustment instruction, and update the junk file determination policy according to the updated feature set;

Or the receiving module includes a second receiving submodule configured to receive an element threshold adjustment instruction, where the element threshold adjustment instruction includes a policy modification instruction for adjusting a threshold of an element of the junk file determination policy; The modification module includes a second modification submodule, configured to update the threshold of the corresponding element according to the element adjustment threshold instruction, and update the junk file determination policy according to the updated threshold.
A junk file management device, comprising:

The junk file identifying apparatus according to any one of claims 13 to 18, configured to identify a junk file in the terminal file system;

A management module configured to manage the junk file.
The junk file management apparatus according to claim 19, wherein said management module comprises a management sub-module:

Set to delete the junk file;

Or setting to present the junk file to the user for confirmation, and managing the junk file according to the first confirmation instruction of the user;

Or setting to present the junk file and the junk file judging policy to the user for confirmation, and managing the junk file according to the second confirmation instruction of the user.
A terminal comprising the junk file identification device according to any one of claims 13 to 18 and the junk file management device according to claim 19 or 20, wherein the junk file identification device is included in the junk file management device The garbage file identification device is configured to identify the junk file in the terminal file system; the junk file management device is configured to manage the junk file identified by the junk file identification device.