[go: up one dir, main page]

WO2016197814A1 - Procédé d'identification et de gestion de fichiers inutiles, dispositif d'identification, dispositif de gestion et terminal - Google Patents

Procédé d'identification et de gestion de fichiers inutiles, dispositif d'identification, dispositif de gestion et terminal Download PDF

Info

Publication number
WO2016197814A1
WO2016197814A1 PCT/CN2016/083174 CN2016083174W WO2016197814A1 WO 2016197814 A1 WO2016197814 A1 WO 2016197814A1 CN 2016083174 W CN2016083174 W CN 2016083174W WO 2016197814 A1 WO2016197814 A1 WO 2016197814A1
Authority
WO
WIPO (PCT)
Prior art keywords
file
junk file
junk
attribute data
policy
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2016/083174
Other languages
English (en)
Chinese (zh)
Inventor
黄勤波
古幼鹏
杨鹏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Publication of WO2016197814A1 publication Critical patent/WO2016197814A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/17—Details of further file system functions
    • G06F16/1727—Details of free space management performed by the file system
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/17—Details of further file system functions
    • G06F16/1724—Details of de-fragmentation performed by the file system

Definitions

  • 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.
  • 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.
  • 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.
  • 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.
  • a method for identifying junk files comprising:
  • 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 method 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:
  • the storage object comprises: a file and/or a folder.
  • 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.
  • the threshold matching case includes: whether an actual value of the operation attribute element matches a threshold of the operation 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 target attribute data further includes display status attribute data
  • the element further includes a status display element set according to the display status attribute data
  • the threshold matching situation includes: whether an actual value of the status display element matches a threshold of the status display element.
  • the operation attribute data includes at least one of an operation type, an operation time, and an operation time interval
  • the operation attribute element includes an operation type element, an operation time element, and At least one of the operational time interval elements
  • 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.
  • 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.
  • 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;
  • 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:
  • the managing the junk file includes:
  • 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.
  • 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.
  • 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.
  • the target attribute data further includes display status attribute data
  • the element further includes a status display element set according to the display status attribute data
  • the garbage file identification device further includes:
  • a receiving module configured to receive a policy modification instruction sent by a user
  • 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;
  • 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.
  • the management module includes a management submodule:
  • 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.
  • 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.
  • 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.
  • the requirements of the junk file judging policy may be different for different users.
  • 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.
  • FIG. 1 is a schematic flowchart of a garbage file identification method according to Embodiment 1 of the present invention.
  • FIG. 2 is a schematic flowchart of a garbage file identification method according to an alternative embodiment of the present invention.
  • FIG. 3 is a schematic flowchart of a garbage file management method according to Embodiment 2 of the present invention.
  • FIG. 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.
  • FIG. 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.
  • the system or application will generate corresponding files or folders, and these files or folders have their own corresponding attribute data.
  • 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 is a diagrammatic representation of 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.
  • steps S102-S103 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.
  • 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.
  • 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.
  • 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.
  • 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
  • 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.
  • 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 Vietnamese and so on.
  • 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.
  • an operation attribute element set according to the operation attribute data a size attribute element set according to the size attribute data
  • a status display according to the display status attribute data a status display according to the display status attribute data.
  • none of the above three elements can be separately selected for use in formulating a junk file judgment strategy to determine junk files.
  • 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;
  • the match case includes whether the actual value of the size attribute element matches the threshold of the size attribute element.
  • the operation attribute element of the embodiment includes an operation type element, an operation time element, and an operation time interval element
  • 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.
  • 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:
  • 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.
  • 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.
  • 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.
  • 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.
  • 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:
  • junk file judgment strategy can be: a single file cumulative write size exceeds 1G, or the overall size of the folder exceeds 800M.
  • 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.
  • the file is judged to be a junk file
  • 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;
  • 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.
  • the matching situation includes: whether the actual value of the status display element matches the threshold of the status display element.
  • 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.
  • the garbage policy includes the following methods:
  • the junk file judgment strategy can be set to, the storage object is a file, or the storage object is a folder.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the elements of this embodiment can also be set according to other data available for data mining.
  • other junk file judgment strategies can also be developed.
  • 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.
  • 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.
  • 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
  • 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 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.
  • 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.
  • 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 is not obtained.
  • the policy modification instruction is a threshold adjustment instruction for adjusting a threshold of an element of the junk file judgment policy
  • 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”.
  • the original attribute data on the terminal is fully utilized.
  • 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.
  • 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 is a diagrammatic representation of Embodiment 1:
  • This embodiment provides a garbage management method for managing the identified junk file.
  • the method includes steps S201 to S202:
  • the step S202 includes:
  • the first type directly delete the junk file
  • 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.
  • 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.
  • 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.
  • 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 is a diagrammatic representation of Embodiment 3
  • 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 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.
  • 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.
  • the target attribute data includes operation attribute data and/or size attribute data
  • 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.
  • the target attribute data further includes display status attribute data
  • the element further includes a status display element set according to the display status attribute data
  • 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.
  • 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.
  • 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.
  • 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 is not obtained.
  • 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.
  • 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 includes:
  • the junk file identification device 31 is configured to identify the junk file in the terminal file system
  • the management module 321 is configured to manage the junk files.
  • the management module 321 of the embodiment further includes a management submodule 3211:
  • the junk file is 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.
  • FIG. 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.
  • 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.
  • Embodiment 4 is a diagrammatic representation of Embodiment 4:
  • 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.
  • the junk file judging policy is preset on the terminal, as shown in FIG. The process includes the following steps S401 to S409:
  • 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;
  • 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;
  • 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;
  • S410 The junk file is changed to a non-spam file.
  • Embodiment 5 is a diagrammatic representation of Embodiment 5:
  • a computer readable storage medium storing computer executable instructions for performing the method of Embodiment 1 or Embodiment 2 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

L'invention concerne un procédé d'identification et de gestion de fichiers inutiles, un dispositif d'identification, un dispositif de gestion et un terminal. Le procédé d'identification de fichiers inutiles comprend les étapes consistant à : obtenir une valeur réelle de chaque élément dans un ensemble d'éléments d'un objet stocké dans un système de fichiers en fonction des données d'attribut cible réelles actuelles de l'objet stocké ; les éléments étant paramétrés en fonction des données d'attribut cible de l'objet stocké dans le système de fichiers ; et évaluer si l'objet stocké est un fichier inutile selon la condition de concordance entre la valeur réelle de chaque élément dans l'ensemble d'éléments de l'objet stocké et un seuil d'un élément correspondant dans une politique d'évaluation de fichiers inutiles prédéfinie.
PCT/CN2016/083174 2015-11-18 2016-05-24 Procédé d'identification et de gestion de fichiers inutiles, dispositif d'identification, dispositif de gestion et terminal Ceased WO2016197814A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510807437.0A CN106708912B (zh) 2015-11-18 2015-11-18 垃圾文件识别及管理方法、识别装置、管理装置和终端
CN201510807437.0 2015-11-18

Publications (1)

Publication Number Publication Date
WO2016197814A1 true WO2016197814A1 (fr) 2016-12-15

Family

ID=57502878

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/083174 Ceased WO2016197814A1 (fr) 2015-11-18 2016-05-24 Procédé d'identification et de gestion de fichiers inutiles, dispositif d'identification, dispositif de gestion et terminal

Country Status (2)

Country Link
CN (1) CN106708912B (fr)
WO (1) WO2016197814A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111263936A (zh) * 2017-08-22 2020-06-09 深圳传音通讯有限公司 电子终端的垃圾文件处理方法与电子终端

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108021630B (zh) * 2017-11-21 2021-03-30 深圳市雷鸟网络传媒有限公司 垃圾文件清理方法、智能终端及计算机可读存储介质
CN108255930B (zh) * 2017-11-30 2020-06-05 维沃移动通信有限公司 一种移动终端的数据清理方法及移动终端
CN109656875B (zh) * 2018-12-05 2023-05-16 广东小天才科技有限公司 存储空间的分类管理方法、装置、终端及存储介质
CN111026716A (zh) * 2019-11-20 2020-04-17 深圳传音控股股份有限公司 文件管理方法、装置及计算机存储介质
CN111177075B (zh) * 2019-12-26 2022-04-22 浪潮电子信息产业股份有限公司 一种垃圾数据的识别方法、系统、电子设备及存储介质
CN112131189A (zh) * 2020-09-29 2020-12-25 珠海海鸟科技有限公司 一种清理垃圾文件的方法、装置及电子设备
CN112486920A (zh) * 2020-11-23 2021-03-12 上海传兴科技有限公司 文件处理方法、移动终端及存储介质
CN114138721A (zh) * 2021-11-29 2022-03-04 惠州Tcl移动通信有限公司 垃圾文件的处理方法、装置、计算机设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101464904A (zh) * 2009-01-09 2009-06-24 华为技术有限公司 文件识别方法及装置
CN103530424A (zh) * 2013-10-31 2014-01-22 北京奇虎科技有限公司 一种垃圾文件的检测方法及装置
CN103631934A (zh) * 2013-12-06 2014-03-12 贝壳网际（北京）安全技术有限公司 垃圾文件检测方法及装置

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012167392A2 (fr) * 2011-06-06 2012-12-13 ETH Zürich Procédé et dispositifs de suppression sécurisée de données dans un système de fichiers journalisé

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101464904A (zh) * 2009-01-09 2009-06-24 华为技术有限公司 文件识别方法及装置
CN103530424A (zh) * 2013-10-31 2014-01-22 北京奇虎科技有限公司 一种垃圾文件的检测方法及装置
CN103631934A (zh) * 2013-12-06 2014-03-12 贝壳网际（北京）安全技术有限公司 垃圾文件检测方法及装置

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111263936A (zh) * 2017-08-22 2020-06-09 深圳传音通讯有限公司 电子终端的垃圾文件处理方法与电子终端

Also Published As

Publication number Publication date
CN106708912A (zh) 2017-05-24
CN106708912B (zh) 2021-06-25

Similar Documents

Publication Publication Date Title
WO2016197814A1 (fr) Procédé d'identification et de gestion de fichiers inutiles, dispositif d'identification, dispositif de gestion et terminal
US10275355B2 (en) Method and apparatus for cleaning files in a mobile terminal and associated mobile terminal
US9813450B1 (en) Metadata-based verification of artifact quality policy compliance
US9607278B2 (en) Systems and methods for supporting social productivity using relevancy scoring
US11640583B2 (en) Generation of user profile from source code
US9253130B2 (en) Systems and methods for supporting social productivity using a dashboard
CN109241358A (zh) 元数据管理方法、装置、计算机设备及存储介质
CN105700819B (zh) 用于网络数据存储的方法和系统
US20210374163A1 (en) Scanning for information according to scan objectives
CN112925783B (zh) 业务数据处理方法和装置、电子设备和存储介质
CN103577454A (zh) 一种文件合并方法和装置
CN110795400B (zh) 一种文件的管理方法、装置、设备及介质
CN108897859A (zh) 一种元数据检索方法、装置、设备及计算机可读存储介质
CN107657051A (zh) 一种图片标签的生成方法、终端设备及存储介质
CN108647935B (zh) 一种财务凭证生成规则更新方法及装置
CN114063879B (zh) 用于处理操作命令的方法、电子设备和存储介质
CN107193754B (zh) 进行数据存储用于搜索的方法及设备
CN104268231B (zh) 一种文件访问方法、装置及智能文件系统
CN114491195A (zh) 特征数据识别方法及装置、电子设备、存储介质
CN112685557B (zh) 可视化信息资源管理方法及装置
US9183388B2 (en) Injustice detecting system, injustice detecting device and injustice detecting method
CN113655958A (zh) 应用数据的存储方法
CN105224438A (zh) 基于网盘的用户消费提醒方法及装置
CN108073712B (zh) 信息系统中的主数据删除方法、装置和计算机设备
CN112632266B (zh) 数据写入方法、装置、计算机设备及可读存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16806712

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16806712

Country of ref document: EP

Kind code of ref document: A1