WO2017032313A1 - 一种待清理数据识别方法、装置及电子设备 - Google Patents

一种待清理数据识别方法、装置及电子设备 Download PDF

Info

Publication number
WO2017032313A1
WO2017032313A1 PCT/CN2016/096557 CN2016096557W WO2017032313A1 WO 2017032313 A1 WO2017032313 A1 WO 2017032313A1 CN 2016096557 W CN2016096557 W CN 2016096557W WO 2017032313 A1 WO2017032313 A1 WO 2017032313A1
Authority
WO
WIPO (PCT)
Prior art keywords
folder
file
cleaned
feature information
data amount
Prior art date
Application number
PCT/CN2016/096557
Other languages
English (en)
French (fr)
Inventor
于情情
阮昕
Original Assignee
北京金山安全软件有限公司
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 北京金山安全软件有限公司 filed Critical 北京金山安全软件有限公司
Priority to US15/752,162 priority Critical patent/US20180239839A1/en
Publication of WO2017032313A1 publication Critical patent/WO2017032313A1/zh

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/907Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/16File or folder operations, e.g. details of user interfaces specifically adapted to file systems
    • G06F16/162Delete operations
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/17Details of further file system functions
    • G06F16/1727Details of free space management performed by the file system
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/14Details of searching files based on file metadata
    • G06F16/148File search processing
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/16File or folder operations, e.g. details of user interfaces specifically adapted to file systems

Definitions

  • the present application relates to the field of data processing, and in particular, to a data identification method, apparatus, and electronic device to be cleaned.
  • the application running/system running in the electronic device usually buffers data (files or folders) or generates data, and the data is automatically saved to the corresponding storage space.
  • the capacity of the storage space of the electronic device is limited. Therefore, in order to release the storage space to ensure the subsequent normal operation of the system or the application, the storage space needs to be cleaned up.
  • the prior art garbage cleaning software usually determines the conventional garbage data (conventional junk files and regular junk folders) based on the pre-statistical analysis, and directly deletes the determined conventional junk data. To a certain cleaning effect.
  • a large file can be a movie cached by a user through a video playing software. If the user has watched it, the movie is highly likely to be useless to the user, so the movie can be identified as data to be cleaned; and the large folder can be an application.
  • Folder In the parent folder, a folder for storing various photos of the user. If the user has already saved the image in the folder, the folder is highly likely to be useless to the user, and therefore, the various photos of the user are stored. Folder can be It is identified as data to be cleaned up.
  • the embodiment of the present application provides a data identification solution for large files and large folders to effectively identify large files and large folders to be cleaned in the storage space.
  • the embodiment of the present application discloses a data identification method, device, and electronic device to be cleaned to identify large files and large folders to be cleaned in a storage space.
  • the technical solutions are as follows:
  • the embodiment of the present application provides a data identification method to be cleaned, which is applied to an electronic device, and the method includes:
  • the determined file to be cleaned and the determined folder to be cleaned are determined as data to be cleaned.
  • the preset folder feature information includes:
  • the feature information of the parent folder of the application in the operating system or the feature information of the specific folder of the operating system itself.
  • the preset conventional garbage judgment condition includes:
  • the second type of feature information of the folder conforms to the feature information of the preset conventional garbage folder
  • the first type of feature information of the file in the folder conforms to the feature information of the preset conventional junk file
  • the second type of feature information of the folder conforms to the feature information of the preset conventional junk folder
  • the first type of feature information of the file in the folder conforms to the feature information of the preset conventional junk file.
  • the first type of feature information includes: at least one of a file type, a file path, and a file name;
  • the second type of feature information includes at least one of a folder name, a folder path, and a file type in the folder.
  • the determining, according to the data volume of the included file, whether each intermediate folder is a folder to be cleaned includes:
  • the intermediate folder of the file in which the amount of data exceeds the second predetermined amount of data threshold is not determined to be a folder to be cleaned.
  • the determining, according to the data volume of the included file, whether each intermediate folder is a folder to be cleaned includes:
  • An intermediate folder in which the total data amount of the included files does not exceed the third predetermined data amount threshold is determined as a non-cleaning folder.
  • the determining whether each intermediate folder is based on the amount of data of the included file For the folder to be cleaned including:
  • An intermediate folder in which the total data amount of the included files does not exceed the third predetermined data amount threshold is determined as a non-cleaning folder.
  • the method for identifying data to be cleaned provided by the embodiment of the present application further includes:
  • the determined data to be cleaned is displayed, wherein the to-be-cleaned folder is displayed in the form of a folder icon, and the to-be-cleaned file is displayed in the form of a file icon.
  • the embodiment of the present application provides a data identification device to be cleaned, which is applied to an electronic device, and the device includes:
  • a scanning module configured to scan files and folders located in a storage space of the electronic device
  • a feature information obtaining module configured to obtain a data size and a first type of feature information of the scanned file, and a second type of feature information of the scanned folder;
  • An operation folder determining module configured to determine, as an operation folder, a folder in which the second type of feature information in the scanned folder meets the preset folder feature information
  • the intermediate folder determining module is configured to determine, as the intermediate folder, a folder in the determined operation folder that does not satisfy the preset regular garbage determination condition;
  • An intermediate folder processing module configured to determine, according to a data size of the included file, whether each intermediate folder is a folder to be cleaned;
  • the file determination module to be cleaned is used to increase the amount of data outside the operation folder by more than the first pre- Determining the data volume threshold and the first type of feature information does not meet the preset file feature information is determined as the file to be cleaned;
  • the to-be-cleaned data determining module is configured to determine the determined file to be cleaned and the determined to-be-cleaned folder as data to be cleaned.
  • the preset folder feature information includes:
  • the feature information of the parent folder of the application in the operating system or the feature information of the specific folder of the operating system itself.
  • the preset conventional garbage judgment condition includes:
  • the second type of feature information of the folder conforms to the feature information of the preset conventional garbage folder
  • the first type of feature information of the file in the folder conforms to the feature information of the preset conventional junk file
  • the second type of feature information of the folder conforms to the feature information of the preset conventional junk folder
  • the first type of feature information of the file in the folder conforms to the feature information of the preset conventional junk file.
  • the first type of feature information includes: at least one of a file type, a file path, and a file name;
  • the second type of feature information includes at least one of a folder name, a folder path, and a file type in the folder.
  • the intermediate folder processing module includes:
  • a first determining unit configured to separately determine, in the file in each intermediate file, whether the file size exceeds a second predetermined data amount threshold
  • a first processing unit configured to determine an intermediate folder of a file whose data size exceeds a second predetermined data amount threshold as a folder to be cleaned
  • a second processing unit configured to determine an intermediate folder of the file that does not have a data size exceeding the second predetermined data amount threshold as a non-cleaning folder.
  • the intermediate folder processing module includes:
  • a second determining unit configured to respectively determine whether a total data amount of the file in each intermediate folder exceeds a third predetermined data amount threshold
  • a third processing unit configured to determine an intermediate folder whose total data amount of the included file exceeds a third predetermined data amount threshold as a folder to be cleaned;
  • a fourth processing unit configured to determine an intermediate folder whose total data amount of the included file does not exceed a third predetermined data amount threshold as a non-cleaning folder.
  • the intermediate folder processing module includes:
  • a third determining unit configured to separately determine, in the file in each intermediate file, whether the file size exceeds a second predetermined data amount threshold
  • a fifth processing unit configured to determine an intermediate folder of the file whose data size exceeds the second predetermined data amount threshold as a folder to be cleaned
  • a fourth determining unit configured to continue to determine, respectively, whether a total data amount of a file in an intermediate folder of a file having no data amount exceeding a second predetermined data amount threshold exceeds a third predetermined data amount threshold;
  • a sixth processing unit configured to determine an intermediate folder whose total data amount of the included file exceeds a third predetermined data amount threshold as a folder to be cleaned;
  • a seventh processing unit configured to determine an intermediate folder whose total data amount of the included file does not exceed a third predetermined data amount threshold as a non-cleaning folder.
  • the data identification device to be cleaned provided by the embodiment of the present application further includes:
  • the display module is configured to display the determined data to be cleaned, wherein the to-be-cleaned folder is displayed in the form of a folder icon, and the to-be-cleaned file is displayed in the form of a file icon.
  • an embodiment of the present application further provides an electronic device, including: a housing, a processor, a memory, a circuit board, and a power supply circuit, wherein the circuit board is disposed inside a space enclosed by the housing, the processor and the memory Provided on a circuit board; a power supply circuit for supplying power to various circuits or devices of the electronic device; a memory for storing executable program code; and a processor for reading the stored in the memory Executable program code to execute a program corresponding to the executable program code for performing the following steps:
  • the determined file to be cleaned and the determined folder to be cleaned are determined as data to be cleaned.
  • an embodiment of the present application provides an application program for performing a data identification method to be cleaned provided by an embodiment of the present application at runtime.
  • the data identification method to be cleaned includes:
  • the amount of data outside the operational folder exceeds the first predetermined data amount threshold and the first type of feature
  • the file whose information does not meet the preset file characteristic information is determined as the file to be cleaned;
  • the determined file to be cleaned and the determined folder to be cleaned are determined as data to be cleaned.
  • the embodiment of the present application provides a storage medium for storing executable program code, where the executable program code is executed to execute the data identification method to be cleaned provided by the embodiment of the present application.
  • the data identification method to be cleaned includes:
  • the determined file to be cleaned and the determined folder to be cleaned are determined as data to be cleaned.
  • the files and folders located in the storage space of the electronic device are scanned; the data size and the first type of feature information of the scanned file are obtained, and the second type of feature information of the scanned folder is obtained.
  • the folder is determined as an intermediate folder; based on the data size of the included file, determining whether each intermediate folder is a folder to be cleaned; the amount of data outside the operating folder exceeds a first predetermined data amount threshold and the first type of feature
  • the file whose information does not meet the preset file feature information is determined as the file to be cleaned; the determined file to be cleaned and the determined folder to be cleaned are determined as data to be cleaned.
  • FIG. 1 is a flowchart of a method for identifying data to be cleaned according to an embodiment of the present application
  • FIG. 2 is another flowchart of a method for identifying data to be cleaned according to an embodiment of the present application
  • FIG. 3 is another flowchart of a method for identifying data to be cleaned according to an embodiment of the present application
  • FIG. 4 is another flowchart of a method for identifying data to be cleaned according to an embodiment of the present application
  • FIG. 5 is a schematic structural diagram of a data identification device to be cleaned according to an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of an intermediate folder processing module included in a data identification device to be cleaned according to an embodiment of the present disclosure
  • FIG. 7 is another schematic structural diagram of an intermediate folder processing module included in a data identification device to be cleaned according to an embodiment of the present disclosure
  • FIG. 8 is another schematic structural diagram of an intermediate folder processing module included in a data identification device to be cleaned according to an embodiment of the present disclosure
  • FIG. 9 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
  • a method, device and electronic device for identifying data to be cleaned are provided.
  • a method for identifying data to be cleaned provided by the embodiment of the present application is first introduced.
  • the data identification method to be cleaned provided by this embodiment is applied to an electronic device.
  • the electronic device can be: a smart phone, a tablet computer or a laptop computer, etc., which are all reasonable.
  • the function software for implementing the data identification method to be cleaned provided by the embodiment may be a special client software, or may be an existing plug-in for cleaning software for cleaning conventional garbage data. This is all reasonable.
  • a method for identifying data to be cleaned may include:
  • S101 Scan files and folders located in a storage space of the electronic device.
  • the storage space may be a storage space provided by the electronic device, or may be a peripheral storage space added by the user to the electronic device, such as an SD card (Secure Digital Memory Card), where The SD card is a memory card based on the semiconductor flash memory process, which is reasonable.
  • SD card Secure Digital Memory Card
  • the first type of feature information may include at least one of a file type, a file path, and a file name, and is of course not limited thereto.
  • the second type of feature information may include at least one of a folder name, a folder path, and a file type in the folder, and is of course not limited thereto.
  • the preset folder feature information can be set based on the folder associated with the application and the folder associated with the operating system, and then after obtaining the second type of feature information of the scanned folder
  • the folder in which the second type of feature information in the scanned folder satisfies the preset folder feature information may be determined as an operation folder.
  • the preset folder feature information may include: feature information of a parent folder of the application in the operating system, or feature information of a specific folder of the operating system itself.
  • the feature information of the parent folder of the common application in the operating system and the feature information of the specific folder of the operating system itself can be statistically analyzed in advance, and the feature information of the statistical analysis can be the folder name. At least one of a folder path, a file type within a folder; and, it can be understood that the second feature information is determined based on the feature information of the pre-statistical analysis due to the need to match the comparison.
  • the remaining folder in the operation folder may be determined as the intermediate folder, and then the determined intermediate The folder performs identification processing of the folder to be cleaned up.
  • the preset conventional garbage judgment condition may include:
  • the second type of feature information of the folder conforms to the feature information of the preset conventional garbage folder
  • the first type of feature information of the file in the folder conforms to the feature information of the preset conventional junk file
  • the second type of feature information of the folder conforms to the feature information of the preset conventional junk folder
  • the first type of feature information of the file in the folder conforms to the feature information of the preset conventional junk file.
  • the regular garbage folder to set the regular garbage judgment condition, wherein the regular garbage judgment condition can be separately based on the characteristics of the conventional garbage folder
  • the information is set, and may also be set according to the characteristic information of the conventional junk file in the conventional junk folder, or may be set in combination with the feature information of the conventional junk folder and the feature information of the conventional junk file, which are all reasonable.
  • the preset conventional junk file and the preset regular junk folder can be determined by the prior art, for example, by file type, file name or file path to determine whether the file is a regular junk file, by folder name or folder path To determine whether the folder is a regular folder, etc., do not repeat them here.
  • each intermediate folder is a folder to be cleaned based on the data size of the included file.
  • S106 determining, as the file to be cleaned, a file whose size of the data volume other than the operation folder exceeds the first predetermined data amount threshold and the first type of feature information does not meet the preset file feature information;
  • the large file to be cleaned is a file with a large amount of data other than the conventional junk file. Therefore, the preset file feature information can be set based on the feature information of the conventional junk file, and the operation file can be operated after determining the operation folder. A file whose size other than the folder exceeds the first predetermined data amount threshold and the first type of feature information does not conform to the preset file feature information is determined as the file to be cleaned.
  • the preset file feature information may be set according to the feature information of the conventional junk file.
  • the first predetermined data amount threshold may be set according to actual conditions, and is not limited herein.
  • the determined to-be-cleaned folder and the determined to-be-cleaned file may be determined as data to be cleaned, and the data to be cleaned is required by the user. Determine whether to delete the processed data.
  • the data identification method to be cleaned provided by the embodiment of the present application may further include:
  • the determined data to be cleaned is displayed, wherein the to-be-cleaned folder is displayed in the form of a folder icon, and the to-be-cleaned file is displayed in the form of a file icon.
  • the files and folders located in the storage space of the electronic device are scanned; the data size of the scanned file and the first type of feature information, and the second type of feature information of the scanned folder are obtained; Determining, as the operation folder, a folder in which the second type of feature information in the scanned folder satisfies the preset folder feature information; and the folder in the determined operation folder that does not satisfy the preset regular garbage determination condition Determining as an intermediate folder; determining, according to the data size of the included file, whether each intermediate folder is a folder to be cleaned; and the amount of data outside the operational folder exceeds a first predetermined data amount threshold and the first type of characteristic information
  • the file that does not meet the preset file feature information is determined as the file to be cleaned; the determined file to be cleaned and the determined folder to be cleaned are determined as data to be cleaned. It can be seen that the purpose of effectively identifying large files and large folders to be cleaned in the storage space can be realized by the solution.
  • the data identification method to be cleaned provided by this embodiment is applied to an electronic device.
  • the electronic device can be: a smart phone, a tablet computer or a laptop computer, etc., which are all reasonable.
  • the function software for implementing the data identification method to be cleaned provided by the embodiment may be a special client software, or may be an existing plug-in for cleaning software for cleaning conventional garbage data. This is all reasonable.
  • the method for identifying data to be cleaned may include the following steps:
  • S201 Scan files and folders located in a storage space of the electronic device
  • S203 Determine, as the operation folder, a folder in which the second type of feature information in the scanned folder meets the preset folder feature information.
  • the S201-S204 is similar to the S101-S104 in the foregoing embodiment, and details are not described herein.
  • S205 Determine, respectively, whether a file having a data size exceeding a second predetermined data amount threshold exists in a file in each intermediate file;
  • S206 Determine an intermediate folder of a file whose data size exceeds a second predetermined data amount threshold as a folder to be cleaned, and determine an intermediate folder of a file whose data size exceeds a second predetermined data amount threshold as non-waiting Clean up the folder;
  • the intermediate folder After determining the intermediate folder, it may be determined whether there is a file in the file in each intermediate file that exceeds the threshold of the second predetermined data amount, and performs different operations according to different judgment results. Specifically, Determining, as a folder to be cleaned, an intermediate folder of a file whose data size exceeds a second predetermined data amount threshold, and determining an intermediate folder of a file having a data size exceeding a second predetermined data amount threshold as a non-cleaned file folder.
  • the second predetermined data amount threshold may be set according to actual conditions, and is not limited herein.
  • S207-S208 is similar to S106-S107 of the foregoing embodiment, and details are not described herein.
  • the data identification method to be cleaned provided by the embodiment of the present application may further include:
  • the data identification method to be cleaned provided by this embodiment is applied to an electronic device.
  • the electronic device can be: a smart phone, a tablet computer or a laptop computer, etc., which are all reasonable.
  • the function software for implementing the data identification method to be cleaned provided by the embodiment may be a special client software, or may be an existing plug-in for cleaning software for cleaning conventional garbage data. This is all reasonable.
  • the method for identifying data to be cleaned may include the following steps:
  • S301 Scan files and folders located in a storage space of the electronic device.
  • the S301-S304 is similar to the S101-S104 in the foregoing embodiment, and is not described here.
  • An intermediate folder that exceeds a total data amount of the included file by a third predetermined data amount threshold Determining as a folder to be cleaned, determining an intermediate folder whose total data amount of the included file does not exceed a third predetermined data amount threshold is determined as a non-cleaning folder;
  • the intermediate folder After determining the intermediate folder, it may be separately determined whether the total data amount of the files in each intermediate folder exceeds a third predetermined data amount threshold, and performs different operations according to different judgment results. Specifically, the The intermediate folder containing the total data amount of the file exceeding the third predetermined data amount threshold is determined as the folder to be cleaned, and the intermediate folder whose total data amount of the included file does not exceed the third predetermined data amount threshold is determined as the non-cleaned file. folder.
  • the third predetermined data amount threshold may be set according to actual conditions, and is not limited herein.
  • S307-S308 is similar to S106-S107 of the foregoing embodiment, and details are not described herein.
  • the data identification method to be cleaned provided by the embodiment of the present application may further include:
  • the determined data to be cleaned is displayed, wherein the to-be-cleaned folder is displayed in the form of a folder icon, and the to-be-cleaned file is displayed in the form of a file icon.
  • the data identification method to be cleaned provided by this embodiment is applied to an electronic device.
  • the electronic device can be: a smart phone, a tablet computer or a laptop computer, etc., which are all reasonable.
  • the functional software can be either dedicated client software or a plug-in for existing clean-up software for cleaning up regular junk data, which is reasonable.
  • a method for identifying data to be cleaned may include the following steps:
  • S401 Scan files and folders located in a storage space of the electronic device.
  • the S401-S404 is similar to the S101-S104 in the foregoing embodiment, and details are not described herein.
  • S405 Determine whether there is a file in the file in each intermediate file that has a data size exceeding a second predetermined data amount threshold
  • S407. Determine, respectively, whether a total data amount of a file in an intermediate folder of a file having no data amount exceeding a second predetermined data amount threshold exceeds a third predetermined data amount threshold;
  • S408 Determine an intermediate folder whose total data amount of the included file exceeds a third predetermined data amount threshold as a folder to be cleaned, and determine an intermediate folder whose total data amount of the included file does not exceed a third predetermined data amount threshold as Non-cleaning folder;
  • the intermediate folder After determining the intermediate folder, it may be separately determined whether there is a file in the file in each intermediate file that has a data size exceeding a threshold value of the second predetermined data amount, and there is a file whose data size exceeds the threshold of the second predetermined data amount.
  • the intermediate folder is determined as the folder to be cleaned, and continues to determine whether the total data amount of the file in the intermediate folder of the file having no data amount exceeding the second predetermined data amount threshold exceeds the third predetermined data amount threshold. Further, the included text The intermediate folder whose total data amount exceeds the third predetermined data amount threshold is determined as the folder to be cleaned, and the intermediate folder whose total data amount of the included file does not exceed the third predetermined data amount threshold is determined as the non-cleaned folder. .
  • the second predetermined data amount threshold and the third predetermined data amount threshold may be set according to actual conditions, and are not limited herein.
  • the S409-S410 is similar to the S106-S107 in the foregoing embodiment, and details are not described herein.
  • the data identification method to be cleaned provided by the embodiment of the present application may further include:
  • the determined data to be cleaned is displayed, wherein the to-be-cleaned folder is displayed in the form of a folder icon, and the to-be-cleaned file is displayed in the form of a file icon.
  • first predetermined data amount threshold the second predetermined data amount threshold, and the third predetermined number of thresholds are only for distinguishing different predetermined data amount thresholds, and do not have any limiting meaning; similarly, the first The class feature information and the second class feature information are only for distinguishing different feature information, and do not have any limited meaning.
  • the embodiment of the present application further provides a data identification device to be cleaned, which is applied to an electronic device.
  • the device may include:
  • the scanning module 510 is configured to scan files and folders located in a storage space of the electronic device
  • the feature information obtaining module 520 is configured to obtain a data size and a first type of feature information of the scanned file, and a second type of feature information of the scanned folder;
  • the operation folder determining module 530 is configured to determine, as an operation folder, a folder in which the second type of feature information in the scanned folder meets the preset folder feature information;
  • the intermediate folder determining module 540 is configured to determine, as the intermediate folder, a folder in the determined operation folder that does not satisfy the preset regular garbage determination condition;
  • the intermediate folder processing module 550 is configured to determine, according to the data size of the included file, whether each intermediate folder is a folder to be cleaned;
  • the to-be-cleaned file determining module 560 is configured to determine, as the file to be cleaned, a file whose size of the data volume other than the operation folder exceeds the first predetermined data amount threshold and the first type of feature information does not meet the preset file feature information;
  • the data to be cleaned determining module 570 is configured to determine the determined file to be cleaned and the determined folder to be cleaned as data to be cleaned.
  • the files and folders located in the storage space of the electronic device are scanned; the data size and the first type of feature information of the scanned file are obtained, and the second type of feature information of the scanned folder is obtained.
  • the folder is determined as an intermediate folder; based on the data size of the included file, determining whether each intermediate folder is a folder to be cleaned; the amount of data outside the operating folder exceeds a first predetermined data amount threshold and the first type of feature
  • the file whose information does not meet the preset file feature information is determined as the file to be cleaned; the determined file to be cleaned and the determined folder to be cleaned are determined as data to be cleaned.
  • the preset folder feature information may include:
  • the feature information of the parent folder of the application in the operating system or the feature information of the specific folder of the operating system itself.
  • the preset conventional garbage judgment condition may include:
  • the second type of feature information of the folder conforms to the feature information of the preset conventional garbage folder
  • the first type of feature information of the file in the folder conforms to the feature information of the preset conventional junk file
  • the second type of feature information of the folder conforms to the feature information of the preset conventional junk folder
  • the first type of feature information of the file in the folder conforms to the feature information of the preset conventional junk file.
  • the first type of feature information may include: at least one of a file type, a file path, and a file name;
  • the second type of feature information may include at least one of a folder name, a folder path, and a file type within the folder.
  • the intermediate folder processing module 550 may include:
  • the first determining unit 551 is configured to determine, respectively, whether a file having a data size exceeding a second predetermined data amount threshold exists in a file in each intermediate file;
  • the first processing unit 552 is configured to determine an intermediate folder of the file whose data size exceeds the second predetermined data amount threshold as a folder to be cleaned;
  • the second processing unit 553 is configured to determine an intermediate folder of the file that does not have a data size exceeding the second predetermined data amount threshold as a non-cleaning folder.
  • the intermediate folder processing module 550 may include:
  • a second determining unit 554 configured to respectively determine whether a total data amount of the file in each intermediate folder exceeds a third predetermined data amount threshold
  • a third processing unit 555 configured to determine an intermediate folder whose total data amount of the included file exceeds a third predetermined data amount threshold as a folder to be cleaned;
  • the fourth processing unit 556 is configured to determine an intermediate folder whose total data amount of the included file does not exceed the third predetermined data amount threshold as a non-cleaning folder.
  • the intermediate folder processing module 550 may include:
  • the third determining unit 557 is configured to determine, respectively, whether a file having a data size exceeding a second predetermined data amount threshold exists in the file in each intermediate file;
  • a fifth processing unit 558 configured to determine an intermediate folder of the file whose data size exceeds the second predetermined data amount threshold as a folder to be cleaned
  • the fourth determining unit 559 is configured to continue to determine, respectively, whether the total data amount of the file in the intermediate folder of the file having no data amount exceeding the second predetermined data amount threshold exceeds a third predetermined data amount threshold;
  • a sixth processing unit 5510 configured to determine an intermediate folder whose total data amount of the included file exceeds a third predetermined data amount threshold as a folder to be cleaned;
  • the seventh processing unit 5511 is configured to determine an intermediate folder whose total data amount of the included file does not exceed the third predetermined data amount threshold as a non-cleaning folder.
  • the data identification device to be cleaned provided by the embodiment of the present application may further include:
  • the display module is configured to display the determined data to be cleaned, wherein the to-be-cleaned folder is displayed in the form of a folder icon, and the to-be-cleaned file is displayed in the form of a file icon.
  • the embodiment of the present application further provides an electronic device.
  • the electronic device may include: a housing 910, a processor 920, a memory 930, a circuit board 940, and a power circuit 950, wherein the circuit board
  • the 940 is disposed inside the space enclosed by the housing 910, and the processor 920 and the memory 930 are disposed on the circuit board 940;
  • the power supply circuit 950 is configured to supply power to various circuits or devices of the electronic device;
  • the memory 930 is configured to store executable program code.
  • the processor 920 runs a program corresponding to the executable program code by reading the executable program code stored in the memory 930 for performing the following steps:
  • the determined file to be cleaned and the determined folder to be cleaned are determined as data to be cleaned.
  • the electronic device provided by the embodiment of the present application scans files and folders located in the storage space of the electronic device; obtains the data size and the first type of feature information of the scanned file, and the second type of the scanned folder.
  • the class characteristic information; the folder in which the second type of feature information in the scanned folder satisfies the preset folder feature information is determined as an operation folder; and the determined operation folder does not satisfy the preset conventional garbage judgment
  • the conditional folder is determined as an intermediate folder; based on the amount of data of the included file, it is determined whether each intermediate folder is a folder to be cleaned; the amount of data outside the operated folder exceeds a first predetermined data amount threshold and A file whose feature information does not meet the preset file feature information is determined as a file to be cleaned; the determined file to be cleaned and the determined folder to be cleaned are determined as data to be cleaned. It can be seen that the purpose of effectively identifying large files and large folders to be cleaned in the storage space can be realized by the solution.
  • the electronic device exists in a variety of forms including, but not limited to:
  • Mobile communication devices These devices are characterized by mobile communication functions and are mainly aimed at providing voice and data communication.
  • Such terminals include: smart phones (such as iPhone), multimedia phones, functional phones, and low-end phones.
  • Ultra-mobile personal computer equipment This type of equipment belongs to the category of personal computers, has computing and processing functions, and generally has mobile Internet access.
  • Such terminals include: PDAs, MIDs, and UMPC devices, such as the iPad.
  • Portable entertainment devices These devices can display and play multimedia content. Such devices include: audio, video players (such as iPod), handheld game consoles, e-books, and smart toys and portable car navigation devices.
  • the server consists of a processor, a hard disk, a memory, a system bus, etc.
  • the server is similar to a general-purpose computer architecture, but because of the need to provide highly reliable services, processing power and stability High reliability in terms of reliability, security, scalability, and manageability.
  • the embodiment of the present application further provides an application program for performing the data identification method to be cleaned provided by the embodiment of the present application at runtime.
  • the data identification method to be cleaned includes:
  • the determined file to be cleaned and the determined folder to be cleaned are determined as data to be cleaned.
  • the files and folders located in the storage space of the electronic device are scanned; the data size and the first type of feature information of the scanned file are obtained, and the second type of feature information of the scanned folder is obtained.
  • Determining, as the operation folder, the folder in which the second type of feature information in the scanned folder satisfies the preset folder feature information; the unsatisfied in the determined operation folder The folder that presets the normal garbage judgment condition is determined as an intermediate folder; based on the data size of the included file, it is determined whether each intermediate folder is a folder to be cleaned; the amount of data outside the operation folder exceeds the first predetermined size
  • the data volume threshold and the file whose first type of feature information does not meet the preset file feature information are determined as the file to be cleaned; the determined file to be cleaned and the determined folder to be cleaned are determined as data to be cleaned. It can be seen that the purpose of effectively identifying large files and large folders to be cleaned in the storage space can be realized by the solution.
  • the embodiment of the present application further provides a storage medium for storing executable program code, and the executable program code is executed to execute the data identification method to be cleaned provided by the embodiment of the present application.
  • the data identification method to be cleaned includes:
  • the determined file to be cleaned and the determined folder to be cleaned are determined as data to be cleaned.
  • the files and folders located in the storage space of the electronic device are scanned; the data size and the first type of feature information of the scanned file are obtained, and the second type of feature information of the scanned folder is obtained.
  • the folder is determined as an intermediate folder; based on the data size of the included file, determining whether each intermediate folder is a folder to be cleaned; the amount of data outside the operating folder exceeds a first predetermined data amount threshold and the first type of feature Information does not match the default file feature letter
  • the file of the information is determined as the file to be cleaned; the determined file to be cleaned and the determined folder to be cleaned are determined as data to be cleaned. It can be seen that the purpose of effectively identifying large files and large folders to be cleaned in the storage space can be realized by the solution.

Landscapes

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

Abstract

一种待清理数据识别方法、装置及电子设备。该方法包括:扫描位于存储空间内的文件和文件夹(S101);获得所扫描到的文件的数据量大小和第一类特征信息,文件夹的第二类特征信息(S102);将文件夹中第二类特征信息满足预设文件夹特征信息的文件夹确定为运营文件夹(S103);将运营文件夹中的不满足预设常规垃圾判断条件的文件夹确定为中间文件夹(S104);基于所包含文件的数据量大小,确定每一中间文件夹是否为待清理文件夹(S105);将运营文件夹以外的数据量大小超过第一预定数据量阈值且第一类特征信息不符合预设文件特征信息的文件确定为待清理文件(S106);将待清理文件和待清理文件夹确定为待清理数据(S107)。可以有效识别存储空间内的待清理的大文件和大文件夹。

Description

一种待清理数据识别方法、装置及电子设备
本申请要求于2015年8月27日提交中国专利局、申请号为201510536577.9发明名称为“一种待清理数据识别方法、装置及电子设备”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本申请涉及数据处理领域,特别涉及一种待清理数据识别方法、装置及电子设备。
背景技术
随着科学技术飞速的发展,各种电子设备不断的丰富并方便了大众生活。由于利用电子设备处理信息具有方便快捷、节省资源等优势,使得电子设备成为人们的生活或工作中不可或缺的一部分。
其中,电子设备中的应用程序运行/系统运行通常会缓冲数据(文件或文件夹)或生成数据,并且,数据会自动保存到相应的存储空间中。但是,电子设备的存储空间的容量具有一定的限制性,因此,为了释放存储空间以保证系统或应用程序的后续正常运行,需要对存储空间进行清理。为了对存储空间进行清理,现有技术的垃圾清理软件通常基于预先的统计分析确定出常规垃圾数据(常规垃圾文件和常规垃圾文件夹),进而直接将所确定出的常规垃圾数据删除,以起到一定的清理效果。
而申请人发现,对于除去常规垃圾数据以外的大文件(文件的数据量大于某一预定值,例如:50M)和大文件夹(文件夹的数据量大于某一预定值,例如:100M)而言,由于数据量较大,一旦对用户无用,存储空间浪费量极大,因此,可以将这些大文件和大文件夹认定为待清理数据,并在识别出后由用户决定是否删除。例如:大文件可以为用户通过视频播放软件缓存的电影,如果用户已经观看过,该电影极有可能对用户无用,因此,该电影可以被认定为待清理数据;而大文件夹可以为应用程序的父文件夹下的存储用户的各种照片的文件夹,如果用户已经对文件夹内的图片进行保存处理了,该文件夹极有可能对用户无用,因此,该存储用户的各种照片的文件夹可以被 认定为待清理数据。
基于上述需求,本申请实施例提供了一种针对于大文件和大文件夹的待清理数据识别方案,以有效识别存储空间内的待清理的大文件和大文件夹。
发明内容
基于上述问题,本申请实施例公开了一种待清理数据识别方法、装置及电子设备,以识别存储空间内的待清理的大文件和大文件夹。技术方案如下:
第一方面,本申请实施例提供了一种待清理数据识别方法,应用于电子设备,所述方法包括:
扫描位于所述电子设备的存储空间内的文件和文件夹;
获得所扫描到的文件的数据量大小和第一类特征信息,以及所扫描到的文件夹的第二类特征信息;
将所扫描到的文件夹中第二类特征信息满足预设文件夹特征信息的文件夹确定为运营文件夹;
将所确定出的运营文件夹中的不满足预设常规垃圾判断条件的文件夹确定为中间文件夹;
基于所包含文件的数据量大小,确定每一中间文件夹是否为待清理文件夹;
将运营文件夹以外的数据量大小超过第一预定数据量阈值且第一类特征信息不符合预设文件特征信息的文件确定为待清理文件;
将所确定出的待清理文件和所确定出的待清理文件夹确定为待清理数据。
可选的,所述预设文件夹特征信息,包括:
应用程序在操作系统中的父文件夹的特征信息,或,操作系统自身的特定文件夹的特征信息。
可选的,所述预设常规垃圾判断条件,包括:
文件夹的第二类特征信息符合预设常规垃圾文件夹的特征信息;
或者,
文件夹内的文件的第一类特征信息符合预设常规垃圾文件的特征信息;
或者,
文件夹的第二类特征信息符合预设常规垃圾文件夹的特征信息且文件夹内的文件的第一类特征信息符合预设常规垃圾文件的特征信息。
可选的,所述第一类特征信息,包括:文件类型、文件路径、文件名称中的至少一种;
所述第二类特征信息,包括:文件夹名称、文件夹路径、文件夹内文件类型中的至少一种。
可选的,所述基于所包含文件的数据量大小,确定每一中间文件夹是否为待清理文件夹,包括:
分别判断每一中间文件内的文件中是否存在数据量大小超过第二预定数据量阈值的文件;
将存在数据量大小超过第二预定数据量阈值的文件的中间文件夹确定为待清理文件夹;
将不存在数据量大小超过第二预定数据量阈值的文件的中间文件夹确定为非待清理文件夹。
可选的,所述基于所包含文件的数据量大小,确定每一中间文件夹是否为待清理文件夹,包括:
分别判断每一中间文件夹内的文件的总数据量是否超过第三预定数据量阈值;
将所包含文件的总数据量超过第三预定数据量阈值的中间文件夹确定为待清理文件夹;
将所包含文件的总数据量不超过第三预定数据量阈值的中间文件夹确定为非待清理文件夹。
可选的,所述基于所包含文件的数据量大小,确定每一中间文件夹是否 为待清理文件夹,包括:
分别判断每一中间文件内的文件中是否存在数据量大小超过第二预定数据量阈值的文件;
将存在数据量大小超过第二预定数据量阈值的文件的中间文件夹确定为待清理文件夹;
继续分别判断每一不存在数据量大小超过第二预定数据量阈值的文件的中间文件夹内的文件的总数据量是否超过第三预定数据量阈值;
将所包含文件的总数据量超过第三预定数据量阈值的中间文件夹确定为待清理文件夹;
将所包含文件的总数据量不超过第三预定数据量阈值的中间文件夹确定为非待清理文件夹。
可选的,本申请实施例所提供的一种待清理数据识别方法还包括:
展示所确定出的待清理数据,其中,所述待清理文件夹以文件夹图标形式展示,所述待清理文件以文件图标形式展示。
第二方面,本申请实施例提供了一种待清理数据识别装置,应用于电子设备,所述装置包括:
扫描模块,用于扫描位于所述电子设备的存储空间内的文件和文件夹;
特征信息获得模块,用于获得所扫描到的文件的数据量大小和第一类特征信息,以及所扫描到的文件夹的第二类特征信息;
运营文件夹确定模块,用于将所扫描到的文件夹中第二类特征信息满足预设文件夹特征信息的文件夹确定为运营文件夹;
中间文件夹确定模块,用于将所确定出的运营文件夹中的不满足预设常规垃圾判断条件的文件夹确定为中间文件夹;
中间文件夹处理模块,用于基于所包含文件的数据量大小,确定每一中间文件夹是否为待清理文件夹;
待清理文件确定模块,用于将运营文件夹以外的数据量大小超过第一预 定数据量阈值且第一类特征信息不符合预设文件特征信息的文件确定为待清理文件;
待清理数据确定模块,用于将所确定出的待清理文件和所确定出的待清理文件夹确定为待清理数据。
可选的,所述预设文件夹特征信息,包括:
应用程序在操作系统中的父文件夹的特征信息,或,操作系统自身的特定文件夹的特征信息。
可选的,所述预设常规垃圾判断条件,包括:
文件夹的第二类特征信息符合预设常规垃圾文件夹的特征信息;
或者,
文件夹内的文件的第一类特征信息符合预设常规垃圾文件的特征信息;
或者,
文件夹的第二类特征信息符合预设常规垃圾文件夹的特征信息且文件夹内的文件的第一类特征信息符合预设常规垃圾文件的特征信息。
可选的,所述第一类特征信息,包括:文件类型、文件路径、文件名称中的至少一种;
所述第二类特征信息,包括:文件夹名称、文件夹路径、文件夹内文件类型中的至少一种。
可选的,所述中间文件夹处理模块,包括:
第一判断单元,用于分别判断每一中间文件内的文件中是否存在数据量大小超过第二预定数据量阈值的文件;
第一处理单元,用于将存在数据量大小超过第二预定数据量阈值的文件的中间文件夹确定为待清理文件夹;
第二处理单元,用于将不存在数据量大小超过第二预定数据量阈值的文件的中间文件夹确定为非待清理文件夹。
可选的,所述中间文件夹处理模块,包括:
第二判断单元,用于分别判断每一中间文件夹内的文件的总数据量是否超过第三预定数据量阈值;
第三处理单元,用于将所包含文件的总数据量超过第三预定数据量阈值的中间文件夹确定为待清理文件夹;
第四处理单元,用于将所包含文件的总数据量不超过第三预定数据量阈值的中间文件夹确定为非待清理文件夹。
可选的,所述中间文件夹处理模块,包括:
第三判断单元,用于分别判断每一中间文件内的文件中是否存在数据量大小超过第二预定数据量阈值的文件;
第五处理单元,用于将存在数据量大小超过第二预定数据量阈值的文件的中间文件夹确定为待清理文件夹;
第四判断单元,用于继续分别判断每一不存在数据量大小超过第二预定数据量阈值的文件的中间文件夹内的文件的总数据量是否超过第三预定数据量阈值;
第六处理单元,用于将所包含文件的总数据量超过第三预定数据量阈值的中间文件夹确定为待清理文件夹;
第七处理单元,用于将所包含文件的总数据量不超过第三预定数据量阈值的中间文件夹确定为非待清理文件夹。
可选的,本申请实施例所提供的一种待清理数据识别装置还包括:
展示模块,用于展示所确定出的待清理数据,其中,所述待清理文件夹以文件夹图标形式展示,所述待清理文件以文件图标形式展示。
第三方面,本申请实施例还提供了一种电子设备,包括:壳体、处理器、存储器、电路板和电源电路,其中,电路板安置在壳体围成的空间内部,处理器和存储器设置在电路板上;电源电路,用于为电子设备的各个电路或器件供电;存储器用于存储可执行程序代码;处理器通过读取存储器中存储的 可执行程序代码来运行与可执行程序代码对应的程序,以用于执行以下步骤:
扫描位于所述电子设备的存储空间内的文件和文件夹;
获得所扫描到的文件的数据量大小和第一类特征信息,以及所扫描到的文件夹的第二类特征信息;
将所扫描到的文件夹中第二类特征信息满足预设文件夹特征信息的文件夹确定为运营文件夹;
将所确定出的运营文件夹中的不满足预设常规垃圾判断条件的文件夹确定为中间文件夹;
基于所包含文件的数据量大小,确定每一中间文件夹是否为待清理文件夹;
将运营文件夹以外的数据量大小超过第一预定数据量阈值且第一类特征信息不符合预设文件特征信息的文件确定为待清理文件;
将所确定出的待清理文件和所确定出的待清理文件夹确定为待清理数据。
第四方面,本申请实施例提供了一种应用程序,该应用程序用于在运行时执行本申请实施例提供的待清理数据识别方法。其中,待清理数据识别方法,包括:
扫描位于所述电子设备的存储空间内的文件和文件夹;
获得所扫描到的文件的数据量大小和第一类特征信息,以及所扫描到的文件夹的第二类特征信息;
将所扫描到的文件夹中第二类特征信息满足预设文件夹特征信息的文件夹确定为运营文件夹;
将所确定出的运营文件夹中的不满足预设常规垃圾判断条件的文件夹确定为中间文件夹;
基于所包含文件的数据量大小,确定每一中间文件夹是否为待清理文件夹;
将运营文件夹以外的数据量大小超过第一预定数据量阈值且第一类特征 信息不符合预设文件特征信息的文件确定为待清理文件;
将所确定出的待清理文件和所确定出的待清理文件夹确定为待清理数据。
第五方面,本申请实施例提供了一种存储介质,用于存储可执行程序代码,该可执行程序代码被运行以执行本申请实施例提供的待清理数据识别方法。其中,待清理数据识别方法,包括:
扫描位于所述电子设备的存储空间内的文件和文件夹;
获得所扫描到的文件的数据量大小和第一类特征信息,以及所扫描到的文件夹的第二类特征信息;
将所扫描到的文件夹中第二类特征信息满足预设文件夹特征信息的文件夹确定为运营文件夹;
将所确定出的运营文件夹中的不满足预设常规垃圾判断条件的文件夹确定为中间文件夹;
基于所包含文件的数据量大小,确定每一中间文件夹是否为待清理文件夹;
将运营文件夹以外的数据量大小超过第一预定数据量阈值且第一类特征信息不符合预设文件特征信息的文件确定为待清理文件;
将所确定出的待清理文件和所确定出的待清理文件夹确定为待清理数据。
本申请实施例中,扫描位于电子设备的存储空间内的文件和文件夹;获得所扫描到的文件的数据量大小和第一类特征信息,以及所扫描到的文件夹的第二类特征信息;将所扫描到的文件夹中第二类特征信息满足预设文件夹特征信息的文件夹确定为运营文件夹;将所确定出的运营文件夹中的不满足预设常规垃圾判断条件的文件夹确定为中间文件夹;基于所包含文件的数据量大小,确定每一中间文件夹是否为待清理文件夹;将运营文件夹以外的数据量大小超过第一预定数据量阈值且第一类特征信息不符合预设文件特征信息的文件确定为待清理文件;将所确定出的待清理文件和所确定出的待清理文件夹确定为待清理数据。可见,通过本方案可以实现有效识别存储空间内的待清理的大文件和大文件夹的目的。
附图说明
为了更清楚地说明本申请实施例和现有技术的技术方案,下面对实施例和现有技术中所需要使用的附图作简单地介绍,显而易见地,下面描述中的附图仅仅是本申请的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动的前提下,还可以根据这些附图获得其他的附图。
图1为本申请实施例所提供的一种待清理数据识别方法的流程图;
图2为本申请实施例所提供的一种待清理数据识别方法的另一流程图;
图3为本申请实施例所提供的一种待清理数据识别方法的另一流程图;
图4为本申请实施例所提供的一种待清理数据识别方法的另一流程图;
图5为本申请实施例所提供的一种待清理数据识别装置的结构示意图;
图6为本申请实施例所提供的一种待清理数据识别装置所包括的中间文件夹处理模块的具体结构示意图;
图7为本申请实施例所提供的一种待清理数据识别装置所包括的中间文件夹处理模块的另一具体结构示意图;
图8为本申请实施例所提供的一种待清理数据识别装置所包括的中间文件夹处理模块的另一具体结构示意图;
图9为本申请实施例所提供的一种电子设备的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行清楚、完整地描述,显然,所描述的实施例仅仅是本申请一部分实施例,而不是全部的实施例。基于本申请中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本申请保护的范围。
为了有效识别存储空间内的待清理的大文件和大文件夹,本申请实施例 提供了一种待清理数据识别方法、装置及电子设备。
下面首先对本申请实施例所提供的一种待清理数据识别方法进行介绍。
需要说明的是,本实施例所提供的一种待清理数据识别方法应用于电子设备。其中,在实际应用中,该电子设备可以为:智能手机、平板电脑或笔记本电脑等,这都是合理的。
并且,需要强调的是,实现本实施例所提供的一种待清理数据识别方法的功能软件可以为专门的客户端软件,也可以为现有的用于清理常规垃圾数据的清理软件的插件,这都是合理的。
如图1所示,一种待清理数据识别方法,可以包括:
S101,扫描位于电子设备的存储空间内的文件和文件夹;
S102,获得所扫描到的文件的数据量大小和第一类特征信息,以及所扫描到的文件夹的第二类特征信息;
在待清理数据的识别过程中,首先扫描位于电子设备的存储空间内的文件和文件夹,进而获得所扫描到的文件的数据量大小和第一类特征信息,以及所扫描到的文件夹的第二类特征信息。
其中,所述存储空间可以为电子设备自带的存储空间,也可以为用户自行为电子设备增加的外设存储空间,例如:SD卡(Secure Digital Memory Card,安全数码记忆卡),其中,该SD卡为基于半导体闪存工艺的存储卡,这都是合理的。
其中,该第一类特征信息,可以包括:文件类型、文件路径、文件名称中的至少一种,当然并不局限于此。
该第二类特征信息,可以包括:文件夹名称、文件夹路径、文件夹内文件类型中的至少一种,当然并不局限于此。
S103,将所扫描到的文件夹中第二类特征信息满足预设文件夹特征信息的文件夹确定为运营文件夹;
由于待清理大文件夹通常为:应用程序相关联的文件夹和操作系统相关 联的文件夹,因此,可以基于应用程序相关联的文件夹和操作系统相关联的文件夹来设定预设文件夹特征信息,进而在获得所扫描到的文件夹的第二类特征信息后,可以将所扫描到的文件夹中第二类特征信息满足预设文件夹特征信息的文件夹确定为运营文件夹。具体的,所述预设文件夹特征信息,可以包括:应用程序在操作系统中的父文件夹的特征信息,或,操作系统自身的特定文件夹的特征信息。
需要强调的是,可以预先统计分析各常用应用程序在操作系统中的父文件夹的特征信息,以及操作系统自身的特定文件夹的特征信息,并且,所统计分析的特征信息可以为文件夹名称、文件夹路径、文件夹内文件类型中的至少一种;并且,可以理解的是,由于需要匹配对比,第二特征信息基于预先统计分析的特征信息所确定。
S104,将所确定出的运营文件夹中的不满足预设常规垃圾判断条件的文件夹确定为中间文件夹;
其中,在排除运营文件夹中满足预设常规垃圾判断条件的文件夹(即常规垃圾文件夹)后,可以将运营文件夹内的剩余文件夹确定为中间文件夹,进而对所确定出的中间文件夹进行待清理文件夹的识别处理。
其中,该预设常规垃圾判断条件,可以包括:
文件夹的第二类特征信息符合预设常规垃圾文件夹的特征信息;
或者,
文件夹内的文件的第一类特征信息符合预设常规垃圾文件的特征信息;
或者,
文件夹的第二类特征信息符合预设常规垃圾文件夹的特征信息且文件夹内的文件的第一类特征信息符合预设常规垃圾文件的特征信息。
需要强调的是,可以预先统计分析运营文件夹中哪些文件夹是包含常规垃圾文件的常规垃圾文件夹,其中,该常规垃圾文件夹可以直接被删除,无需用户决定是否删除;进而依据所确定出的常规垃圾文件夹来设置常规垃圾判断条件,其中,该常规垃圾判断条件可以单独依据常规垃圾文件夹的特征 信息来设定,也可以单独依据该常规垃圾文件夹内的常规垃圾文件的特征信息来设定,也可以结合常规垃圾文件夹的特征信息和常规垃圾文件的特征信息来设定,这都是合理的。
并且,预设常规垃圾文件和预设常规垃圾文件夹可以通过现有技术来确定,例如:通过文件类型、文件名称或文件路径来确定文件是否为常规垃圾文件,通过文件夹名称或文件夹路径来确定文件夹是否为常规文件夹等,在此不做赘述。
S105,基于所包含文件的数据量大小,确定每一中间文件夹是否为待清理文件夹;
在确定出运营文件夹内的中间文件夹后,由于待清理大文件夹基于文件夹的数据量来确定,可以基于所包含文件的数据量大小,确定每一中间文件夹是否为待清理文件夹。
需要说明的是,关于基于所包含文件的数据量大小,确定每一中间文件夹是否为待清理文件夹的具体实现方式存在多种,为了布局清楚,后续将结合具体的实施例的方式来进行举例介绍。
S106,将运营文件夹以外的数据量大小超过第一预定数据量阈值且第一类特征信息不符合预设文件特征信息的文件确定为待清理文件;
其中,由于待清理大文件为常规垃圾文件以外的数据量较大的文件,因此,可以基于常规垃圾文件的特征信息设定预设文件特征信息,并在确定出运营文件夹后,可以将运营文件夹以外的数据量大小超过第一预定数据量阈值且第一类特征信息不符合预设文件特征信息的文件确定为待清理文件。其中,预设文件特征信息可以依据常规垃圾文件的特征信息设定。
其中,第一预定数据量阈值可以根据实际情况进行设定,在此不做限定。
S107,将所确定出的待清理文件和所确定出的待清理文件夹确定为待清理数据。
在确定出待清理文件夹和待清理文件后,可以将所确定出的待清理文件夹和所确定出的待清理文件确定为待清理数据,该待清理数据为需要用户确 定是否进行删除处理的数据。
更进一步的,本申请实施例所提供的待清理数据识别方法,还可以包括:
展示所确定出的待清理数据,其中,所述待清理文件夹以文件夹图标形式展示,所述待清理文件以文件图标形式展示。
本实施例中,扫描位于电子设备的存储空间内的文件和文件夹;获得所扫描到的文件的数据量大小和第一类特征信息,以及所扫描到的文件夹的第二类特征信息;将所扫描到的文件夹中第二类特征信息满足预设文件夹特征信息的文件夹确定为运营文件夹;将所确定出的运营文件夹中的不满足预设常规垃圾判断条件的文件夹确定为中间文件夹;基于所包含文件的数据量大小,确定每一中间文件夹是否为待清理文件夹;将运营文件夹以外的数据量大小超过第一预定数据量阈值且第一类特征信息不符合预设文件特征信息的文件确定为待清理文件;将所确定出的待清理文件和所确定出的待清理文件夹确定为待清理数据。可见,通过本方案可以实现有效识别存储空间内的待清理的大文件和大文件夹的目的。
下面结合具体的实施例,对本申请实施例所提供的一种待清理数据识别方法进行介绍。
需要说明的是,本实施例所提供的一种待清理数据识别方法应用于电子设备。其中,在实际应用中,该电子设备可以为:智能手机、平板电脑或笔记本电脑等,这都是合理的。
并且,需要强调的是,实现本实施例所提供的一种待清理数据识别方法的功能软件可以为专门的客户端软件,也可以为现有的用于清理常规垃圾数据的清理软件的插件,这都是合理的。
如图2所示,本实施例所提供的一种待清理数据识别方法,可以包括如下步骤:
S201,扫描位于电子设备的存储空间内的文件和文件夹;
S202,获得所扫描到的文件的数据量大小和第一类特征信息,以及所扫 描到的文件夹的第二类特征信息;
S203,将所扫描到的文件夹中第二类特征信息满足预设文件夹特征信息的文件夹确定为运营文件夹;
S204,将所确定出的运营文件夹中的不满足预设常规垃圾判断条件的文件夹确定为中间文件夹;
其中,本实施例中,S201-S204与上述实施例的S101-S104相似,在此不做赘述。
S205,分别判断每一中间文件内的文件中是否存在数据量大小超过第二预定数据量阈值的文件;
S206,将存在数据量大小超过第二预定数据量阈值的文件的中间文件夹确定为待清理文件夹,将不存在数据量大小超过第二预定数据量阈值的文件的中间文件夹确定为非待清理文件夹;
其中,在确定出中间文件夹后,可以分别判断每一中间文件内的文件中是否存在数据量大小超过第二预定数据量阈值的文件,并根据不同的判断结果执行不同的操作,具体的,将存在数据量大小超过第二预定数据量阈值的文件的中间文件夹确定为待清理文件夹,将不存在数据量大小超过第二预定数据量阈值的文件的中间文件夹确定为非待清理文件夹。
其中,第二预定数据量阈值可以根据实际情况进行设定,在此不做限定。
S207,将运营文件夹以外的数据量大小超过第一预定数据量阈值且第一类特征信息不符合预设文件特征信息的文件确定为待清理文件;
S208,将所确定出的待清理文件和所确定出的待清理文件夹确定为待清理数据。
其中,本实施例中,S207-S208与上述实施例的S106-S107相似,在此不做赘述。
更进一步的,本申请实施例所提供的待清理数据识别方法,还可以包括:
展示所确定出的待清理数据,其中,所述待清理文件夹以文件夹图标形 式展示,所述待清理文件以文件图标形式展示。
可见,通过本方案可以实现有效识别存储空间内的待清理的大文件和大文件夹的目的。
下面结合另一具体的实施例,对本申请实施例所提供的一种待清理数据识别方法进行介绍。
需要说明的是,本实施例所提供的一种待清理数据识别方法应用于电子设备。其中,在实际应用中,该电子设备可以为:智能手机、平板电脑或笔记本电脑等,这都是合理的。
并且,需要强调的是,实现本实施例所提供的一种待清理数据识别方法的功能软件可以为专门的客户端软件,也可以为现有的用于清理常规垃圾数据的清理软件的插件,这都是合理的。
如图3所示,本实施例所提供的一种待清理数据识别方法,可以包括如下步骤:
S301,扫描位于电子设备的存储空间内的文件和文件夹;
S302,获得所扫描到的文件的数据量大小和第一类特征信息,以及所扫描到的文件夹的第二类特征信息;
S303,将所扫描到的文件夹中第二类特征信息满足预设文件夹特征信息的文件夹确定为运营文件夹;
S304,将所确定出的运营文件夹中的不满足预设常规垃圾判断条件的文件夹确定为中间文件夹;
其中,本实施例中,S301-S304与上述实施例的S101-S104相似,在此不做赘述。
S305,分别判断每一中间文件夹内的文件的总数据量是否超过第三预定数据量阈值;
S306,将所包含文件的总数据量超过第三预定数据量阈值的中间文件夹 确定为待清理文件夹,将所包含文件的总数据量不超过第三预定数据量阈值的中间文件夹确定为非待清理文件夹;
其中,在确定出中间文件夹后,可以分别判断每一中间文件夹内的文件的总数据量是否超过第三预定数据量阈值,并根据不同的判断结果执行不同的操作,具体的,将所包含文件的总数据量超过第三预定数据量阈值的中间文件夹确定为待清理文件夹,将所包含文件的总数据量不超过第三预定数据量阈值的中间文件夹确定为非待清理文件夹。
其中,第三预定数据量阈值可以根据实际情况进行设定,在此不做限定。
S307,将运营文件夹以外的数据量大小超过第一预定数据量阈值且第一类特征信息不符合预设文件特征信息的文件确定为待清理文件;
S308,将所确定出的待清理文件和所确定出的待清理文件夹确定为待清理数据。
其中,本实施例中,S307-S308与上述实施例的S106-S107相似,在此不做赘述。
更进一步的,本申请实施例所提供的待清理数据识别方法,还可以包括:
展示所确定出的待清理数据,其中,所述待清理文件夹以文件夹图标形式展示,所述待清理文件以文件图标形式展示。
可见,通过本方案可以实现有效识别存储空间内的待清理的大文件和大文件夹的目的。
下面结合另一具体的实施例,对本申请实施例所提供的一种待清理数据识别方法进行介绍。
需要说明的是,本实施例所提供的一种待清理数据识别方法应用于电子设备。其中,在实际应用中,该电子设备可以为:智能手机、平板电脑或笔记本电脑等,这都是合理的。
并且,需要强调的是,实现本实施例所提供的一种待清理数据识别方法 的功能软件可以为专门的客户端软件,也可以为现有的用于清理常规垃圾数据的清理软件的插件,这都是合理的。
如图4所示,本实施例所提供的一种待清理数据识别方法,可以包括如下步骤:
S401,扫描位于电子设备的存储空间内的文件和文件夹;
S402,获得所扫描到的文件的数据量大小和第一类特征信息,以及所扫描到的文件夹的第二类特征信息;
S403,将所扫描到的文件夹中第二类特征信息满足预设文件夹特征信息的文件夹确定为运营文件夹;
S404,将所确定出的运营文件夹中的不满足预设常规垃圾判断条件的文件夹确定为中间文件夹;
其中,本实施例中,S401-S404与上述实施例的S101-S104相似,在此不做赘述。
S405,分别判断每一中间文件内的文件中是否存在数据量大小超过第二预定数据量阈值的文件;
S406,将存在数据量大小超过第二预定数据量阈值的文件的中间文件夹确定为待清理文件夹;
S407,分别判断每一不存在数据量大小超过第二预定数据量阈值的文件的中间文件夹内的文件的总数据量是否超过第三预定数据量阈值;
S408,将所包含文件的总数据量超过第三预定数据量阈值的中间文件夹确定为待清理文件夹,将所包含文件的总数据量不超过第三预定数据量阈值的中间文件夹确定为非待清理文件夹;
其中,在确定出中间文件夹后,可以分别判断每一中间文件内的文件中是否存在数据量大小超过第二预定数据量阈值的文件,将存在数据量大小超过第二预定数据量阈值的文件的中间文件夹确定为待清理文件夹,并继续分别判断每一不存在数据量大小超过第二预定数据量阈值的文件的中间文件夹内的文件的总数据量是否超过第三预定数据量阈值,进一步的,将所包含文 件的总数据量超过第三预定数据量阈值的中间文件夹确定为待清理文件夹,将所包含文件的总数据量不超过第三预定数据量阈值的中间文件夹确定为非待清理文件夹。
其中,本实施例中,第二预定数据量阈值和第三预定数据量阈值可以根据实际情况进行设定,在此不做限定。
S409,将运营文件夹以外的数据量大小超过第一预定数据量阈值且第一类特征信息不符合预设文件特征信息的文件确定为待清理文件;
S410,将所确定出的待清理文件和所确定出的待清理文件夹确定为待清理数据。
其中,本实施例中,S409-S410与上述实施例的S106-S107相似,在此不做赘述。
更进一步的,本申请实施例所提供的待清理数据识别方法,还可以包括:
展示所确定出的待清理数据,其中,所述待清理文件夹以文件夹图标形式展示,所述待清理文件以文件图标形式展示。
可见,通过本方案可以实现有效识别存储空间内的待清理的大文件和大文件夹的目的。
需要强调的是,上述的第一预定数据量阈值、第二预定数据量阈值、第三预定数量阈值仅仅为了区分不同的预定数据量阈值,并不具有任何限定意义;类似的,上述的第一类特征信息、第二类特征信息仅仅为了区分不同的特征信息,并不具有任何限定意义。
相应于上述方法实施例,本申请实施例还提供了一种待清理数据识别装置,应用于电子设备,如图5所示,所述装置可以包括:
扫描模块510,用于扫描位于所述电子设备的存储空间内的文件和文件夹;
特征信息获得模块520,用于获得所扫描到的文件的数据量大小和第一类特征信息,以及所扫描到的文件夹的第二类特征信息;
运营文件夹确定模块530,用于将所扫描到的文件夹中第二类特征信息满足预设文件夹特征信息的文件夹确定为运营文件夹;
中间文件夹确定模块540,用于将所确定出的运营文件夹中的不满足预设常规垃圾判断条件的文件夹确定为中间文件夹;
中间文件夹处理模块550,用于基于所包含文件的数据量大小,确定每一中间文件夹是否为待清理文件夹;
待清理文件确定模块560,用于将运营文件夹以外的数据量大小超过第一预定数据量阈值且第一类特征信息不符合预设文件特征信息的文件确定为待清理文件;
待清理数据确定模块570,用于将所确定出的待清理文件和所确定出的待清理文件夹确定为待清理数据。
本申请实施例中,扫描位于电子设备的存储空间内的文件和文件夹;获得所扫描到的文件的数据量大小和第一类特征信息,以及所扫描到的文件夹的第二类特征信息;将所扫描到的文件夹中第二类特征信息满足预设文件夹特征信息的文件夹确定为运营文件夹;将所确定出的运营文件夹中的不满足预设常规垃圾判断条件的文件夹确定为中间文件夹;基于所包含文件的数据量大小,确定每一中间文件夹是否为待清理文件夹;将运营文件夹以外的数据量大小超过第一预定数据量阈值且第一类特征信息不符合预设文件特征信息的文件确定为待清理文件;将所确定出的待清理文件和所确定出的待清理文件夹确定为待清理数据。可见,通过本方案可以实现有效识别存储空间内的待清理的大文件和大文件夹的目的。
具体的,所述预设文件夹特征信息,可以包括:
应用程序在操作系统中的父文件夹的特征信息,或,操作系统自身的特定文件夹的特征信息。
具体的,所述预设常规垃圾判断条件,可以包括:
文件夹的第二类特征信息符合预设常规垃圾文件夹的特征信息;
或者,
文件夹内的文件的第一类特征信息符合预设常规垃圾文件的特征信息;
或者,
文件夹的第二类特征信息符合预设常规垃圾文件夹的特征信息且文件夹内的文件的第一类特征信息符合预设常规垃圾文件的特征信息。
具体的,所述第一类特征信息可以包括:文件类型、文件路径、文件名称中的至少一种;
所述第二类特征信息可以包括:文件夹名称、文件夹路径、文件夹内文件类型中的至少一种。
具体的,在第一种实现方式中,如图6所示,所述中间文件夹处理模块550,可以包括:
第一判断单元551,用于分别判断每一中间文件内的文件中是否存在数据量大小超过第二预定数据量阈值的文件;
第一处理单元552,用于将存在数据量大小超过第二预定数据量阈值的文件的中间文件夹确定为待清理文件夹;
第二处理单元553,用于将不存在数据量大小超过第二预定数据量阈值的文件的中间文件夹确定为非待清理文件夹。
具体的,在第二种实现方式中,如图7所示,所述中间文件夹处理模块550,可以包括:
第二判断单元554,用于分别判断每一中间文件夹内的文件的总数据量是否超过第三预定数据量阈值;
第三处理单元555,用于将所包含文件的总数据量超过第三预定数据量阈值的中间文件夹确定为待清理文件夹;
第四处理单元556,用于将所包含文件的总数据量不超过第三预定数据量阈值的中间文件夹确定为非待清理文件夹。
具体的,在第三种实现方式中,如图8所示,所述中间文件夹处理模块550,可以包括:
第三判断单元557,用于分别判断每一中间文件内的文件中是否存在数据量大小超过第二预定数据量阈值的文件;
第五处理单元558,用于将存在数据量大小超过第二预定数据量阈值的文件的中间文件夹确定为待清理文件夹;
第四判断单元559,用于继续分别判断每一不存在数据量大小超过第二预定数据量阈值的文件的中间文件夹内的文件的总数据量是否超过第三预定数据量阈值;
第六处理单元5510,用于将所包含文件的总数据量超过第三预定数据量阈值的中间文件夹确定为待清理文件夹;
第七处理单元5511,用于将所包含文件的总数据量不超过第三预定数据量阈值的中间文件夹确定为非待清理文件夹。
更进一步的,本申请实施例所提供的待清理数据识别装置,还可以包括:
展示模块,用于展示所确定出的待清理数据,其中,所述待清理文件夹以文件夹图标形式展示,所述待清理文件以文件图标形式展示。
另外,本申请实施例还提供了一种电子设备,如图9所示,所述电子设备可以包括:壳体910、处理器920、存储器930、电路板940和电源电路950,其中,电路板940安置在壳体910围成的空间内部,处理器920和存储器930设置在电路板940上;电源电路950,用于为电子设备的各个电路或器件供电;存储器930用于存储可执行程序代码;处理器920通过读取存储器930中存储的可执行程序代码来运行与可执行程序代码对应的程序,以用于执行以下步骤:
扫描位于所述电子设备的存储空间内的文件和文件夹;
获得所扫描到的文件的数据量大小和第一类特征信息,以及所扫描到的文件夹的第二类特征信息;
将所扫描到的文件夹中第二类特征信息满足预设文件夹特征信息的文件夹确定为运营文件夹;
将所确定出的运营文件夹中的不满足预设常规垃圾判断条件的文件夹确定为中间文件夹;
基于所包含文件的数据量大小,确定每一中间文件夹是否为待清理文件夹;
将运营文件夹以外的数据量大小超过第一预定数据量阈值且第一类特征信息不符合预设文件特征信息的文件确定为待清理文件;
将所确定出的待清理文件和所确定出的待清理文件夹确定为待清理数据。
其中,处理器920对上述步骤的具体执行过程以及处理器920通过运行可执行程序代码来进一步执行的步骤,可以参见本申请图1-8所示实施例的描述,在此不再赘述。
本申请实施例所提供的电子设备扫描位于电子设备的存储空间内的文件和文件夹;获得所扫描到的文件的数据量大小和第一类特征信息,以及所扫描到的文件夹的第二类特征信息;将所扫描到的文件夹中第二类特征信息满足预设文件夹特征信息的文件夹确定为运营文件夹;将所确定出的运营文件夹中的不满足预设常规垃圾判断条件的文件夹确定为中间文件夹;基于所包含文件的数据量大小,确定每一中间文件夹是否为待清理文件夹;将运营文件夹以外的数据量大小超过第一预定数据量阈值且第一类特征信息不符合预设文件特征信息的文件确定为待清理文件;将所确定出的待清理文件和所确定出的待清理文件夹确定为待清理数据。可见,通过本方案可以实现有效识别存储空间内的待清理的大文件和大文件夹的目的。
该电子设备以多种形式存在,包括但不限于:
(1)移动通信设备:这类设备的特点是具备移动通信功能,并且以提供话音、数据通信为主要目标。这类终端包括:智能手机(例如iPhone)、多媒体手机、功能性手机,以及低端手机等。
(2)超移动个人计算机设备:这类设备属于个人计算机的范畴,有计算和处理功能,一般也具备移动上网特性。这类终端包括:PDA、MID和UMPC设备等,例如iPad。
(3)便携式娱乐设备:这类设备可以显示和播放多媒体内容。该类设备包括:音频、视频播放器(例如iPod),掌上游戏机,电子书,以及智能玩具和便携式车载导航设备。
(4)服务器:提供计算服务的设备,服务器的构成包括处理器、硬盘、内存、系统总线等,服务器和通用的计算机架构类似,但是由于需要提供高可靠的服务,因此在处理能力、稳定性、可靠性、安全性、可扩展性、可管理性等方面要求较高。
(5)其他具有数据交互功能的电子装置。
进一步的,本申请实施例还提供了一种应用程序,该应用程序用于在运行时执行本申请实施例提供的待清理数据识别方法。其中,待清理数据识别方法,包括:
扫描位于所述电子设备的存储空间内的文件和文件夹;
获得所扫描到的文件的数据量大小和第一类特征信息,以及所扫描到的文件夹的第二类特征信息;
将所扫描到的文件夹中第二类特征信息满足预设文件夹特征信息的文件夹确定为运营文件夹;
将所确定出的运营文件夹中的不满足预设常规垃圾判断条件的文件夹确定为中间文件夹;
基于所包含文件的数据量大小,确定每一中间文件夹是否为待清理文件夹;
将运营文件夹以外的数据量大小超过第一预定数据量阈值且第一类特征信息不符合预设文件特征信息的文件确定为待清理文件;
将所确定出的待清理文件和所确定出的待清理文件夹确定为待清理数据。
本申请实施例中,扫描位于电子设备的存储空间内的文件和文件夹;获得所扫描到的文件的数据量大小和第一类特征信息,以及所扫描到的文件夹的第二类特征信息;将所扫描到的文件夹中第二类特征信息满足预设文件夹特征信息的文件夹确定为运营文件夹;将所确定出的运营文件夹中的不满足 预设常规垃圾判断条件的文件夹确定为中间文件夹;基于所包含文件的数据量大小,确定每一中间文件夹是否为待清理文件夹;将运营文件夹以外的数据量大小超过第一预定数据量阈值且第一类特征信息不符合预设文件特征信息的文件确定为待清理文件;将所确定出的待清理文件和所确定出的待清理文件夹确定为待清理数据。可见,通过本方案可以实现有效识别存储空间内的待清理的大文件和大文件夹的目的。
更一进步的,本申请实施例还提供了一种存储介质,用于存储可执行程序代码,该可执行程序代码被运行以执行本申请实施例提供的待清理数据识别方法。其中,待清理数据识别方法,包括:
扫描位于所述电子设备的存储空间内的文件和文件夹;
获得所扫描到的文件的数据量大小和第一类特征信息,以及所扫描到的文件夹的第二类特征信息;
将所扫描到的文件夹中第二类特征信息满足预设文件夹特征信息的文件夹确定为运营文件夹;
将所确定出的运营文件夹中的不满足预设常规垃圾判断条件的文件夹确定为中间文件夹;
基于所包含文件的数据量大小,确定每一中间文件夹是否为待清理文件夹;
将运营文件夹以外的数据量大小超过第一预定数据量阈值且第一类特征信息不符合预设文件特征信息的文件确定为待清理文件;
将所确定出的待清理文件和所确定出的待清理文件夹确定为待清理数据。
本申请实施例中,扫描位于电子设备的存储空间内的文件和文件夹;获得所扫描到的文件的数据量大小和第一类特征信息,以及所扫描到的文件夹的第二类特征信息;将所扫描到的文件夹中第二类特征信息满足预设文件夹特征信息的文件夹确定为运营文件夹;将所确定出的运营文件夹中的不满足预设常规垃圾判断条件的文件夹确定为中间文件夹;基于所包含文件的数据量大小,确定每一中间文件夹是否为待清理文件夹;将运营文件夹以外的数据量大小超过第一预定数据量阈值且第一类特征信息不符合预设文件特征信 息的文件确定为待清理文件;将所确定出的待清理文件和所确定出的待清理文件夹确定为待清理数据。可见,通过本方案可以实现有效识别存储空间内的待清理的大文件和大文件夹的目的。
本说明书中的各个实施例均采用相关的方式描述,各个实施例之间相同相似的部分互相参见即可,每个实施例重点说明的都是与其他实施例的不同之处。尤其,对于装置、电子设备、应用程序和存储介质实施例而言,由于其基本相似于方法实施例,所以描述的比较简单,相关之处参见方法实施例的部分说明即可。
需要说明的是,在本文中,诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来,而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且,术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含,从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素,而且还包括没有明确列出的其他要素,或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下,由语句“包括一个……”限定的要素,并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
本领域普通技术人员可以理解实现上述方法实施方式中的全部或部分步骤是可以通过程序来指令相关的硬件来完成,所述的程序可以存储于计算机可读取存储介质中,这里所称得的存储介质,如:ROM/RAM、磁碟、光盘等。
以上所述仅为本申请的较佳实施例而已,并非用于限定本申请的保护范围。凡在本申请的精神和原则之内所作的任何修改、等同替换、改进等,均包含在本申请的保护范围内。

Claims (19)

  1. 一种待清理数据识别方法,应用于电子设备,其特征在于,所述方法包括:
    扫描位于所述电子设备的存储空间内的文件和文件夹;
    获得所扫描到的文件的数据量大小和第一类特征信息,以及所扫描到的文件夹的第二类特征信息;
    将所扫描到的文件夹中第二类特征信息满足预设文件夹特征信息的文件夹确定为运营文件夹;
    将所确定出的运营文件夹中的不满足预设常规垃圾判断条件的文件夹确定为中间文件夹;
    基于所包含文件的数据量大小,确定每一中间文件夹是否为待清理文件夹;
    将运营文件夹以外的数据量大小超过第一预定数据量阈值且第一类特征信息不符合预设文件特征信息的文件确定为待清理文件;
    将所确定出的待清理文件和所确定出的待清理文件夹确定为待清理数据。
  2. 根据权利要求1所述的方法,其特征在于,所述预设文件夹特征信息,包括:
    应用程序在操作系统中的父文件夹的特征信息,或,操作系统自身的特定文件夹的特征信息。
  3. 根据权利要求1所述的方法,其特征在于,所述预设常规垃圾判断条件,包括:
    文件夹的第二类特征信息符合预设常规垃圾文件夹的特征信息;
    或者,
    文件夹内的文件的第一类特征信息符合预设常规垃圾文件的特征信息;
    或者,
    文件夹的第二类特征信息符合预设常规垃圾文件夹的特征信息且文件夹内的文件的第一类特征信息符合预设常规垃圾文件的特征信息。
  4. 根据权利要求1所述的方法,其特征在于,所述第一类特征信息,包括:文件类型、文件路径、文件名称中的至少一种;
    所述第二类特征信息,包括:文件夹名称、文件夹路径、文件夹内文件类型中的至少一种。
  5. 根据权利要求1所述的方法,其特征在于,所述基于所包含文件的数据量大小,确定每一中间文件夹是否为待清理文件夹,包括:
    分别判断每一中间文件内的文件中是否存在数据量大小超过第二预定数据量阈值的文件;
    将存在数据量大小超过第二预定数据量阈值的文件的中间文件夹确定为待清理文件夹;
    将不存在数据量大小超过第二预定数据量阈值的文件的中间文件夹确定为非待清理文件夹。
  6. 根据权利要求1所述的方法,其特征在于,所述基于所包含文件的数据量大小,确定每一中间文件夹是否为待清理文件夹,包括:
    分别判断每一中间文件夹内的文件的总数据量是否超过第三预定数据量阈值;
    将所包含文件的总数据量超过第三预定数据量阈值的中间文件夹确定为待清理文件夹;
    将所包含文件的总数据量不超过第三预定数据量阈值的中间文件夹确定为非待清理文件夹。
  7. 根据权利要求1所述的方法,其特征在于,所述基于所包含文件的数据量大小,确定每一中间文件夹是否为待清理文件夹,包括:
    分别判断每一中间文件内的文件中是否存在数据量大小超过第二预定数据量阈值的文件;
    将存在数据量大小超过第二预定数据量阈值的文件的中间文件夹确定为待清理文件夹;
    继续分别判断每一不存在数据量大小超过第二预定数据量阈值的文件的中间文件夹内的文件的总数据量是否超过第三预定数据量阈值;
    将所包含文件的总数据量超过第三预定数据量阈值的中间文件夹确定为待清理文件夹;
    将所包含文件的总数据量不超过第三预定数据量阈值的中间文件夹确定为非待清理文件夹。
  8. 根据权利要求1-7任意一项所述的方法,其特征在于,还包括:
    展示所确定出的待清理数据,其中,所述待清理文件夹以文件夹图标形式展示,所述待清理文件以文件图标形式展示。
  9. 一种待清理数据识别装置,应用于电子设备,其特征在于,所述装置包括:
    扫描模块,用于扫描位于所述电子设备的存储空间内的文件和文件夹;
    特征信息获得模块,用于获得所扫描到的文件的数据量大小和第一类特征信息,以及所扫描到的文件夹的第二类特征信息;
    运营文件夹确定模块,用于将所扫描到的文件夹中第二类特征信息满足预设文件夹特征信息的文件夹确定为运营文件夹;
    中间文件夹确定模块,用于将所确定出的运营文件夹中的不满足预设常规垃圾判断条件的文件夹确定为中间文件夹;
    中间文件夹处理模块,用于基于所包含文件的数据量大小,确定每一中间文件夹是否为待清理文件夹;
    待清理文件确定模块,用于将运营文件夹以外的数据量大小超过第一预定数据量阈值且第一类特征信息不符合预设文件特征信息的文件确定为待清理文件;
    待清理数据确定模块,用于将所确定出的待清理文件和所确定出的待清 理文件夹确定为待清理数据。
  10. 根据权利要求9所述的装置,其特征在于,所述预设文件夹特征信息,包括:
    应用程序在操作系统中的父文件夹的特征信息,或,操作系统自身的特定文件夹的特征信息。
  11. 根据权利要求9所述的装置,其特征在于,所述预设常规垃圾判断条件,包括:
    文件夹的第二类特征信息符合预设常规垃圾文件夹的特征信息;
    或者,
    文件夹内的文件的第一类特征信息符合预设常规垃圾文件的特征信息;
    或者,
    文件夹的第二类特征信息符合预设常规垃圾文件夹的特征信息且文件夹内的文件的第一类特征信息符合预设常规垃圾文件的特征信息。
  12. 根据权利要求9所述的装置,其特征在于,所述第一类特征信息,包括:文件类型、文件路径、文件名称中的至少一种;
    所述第二类特征信息,包括:文件夹名称、文件夹路径、文件夹内文件类型中的至少一种。
  13. 根据权利要求9所述的装置,其特征在于,所述中间文件夹处理模块,包括:
    第一判断单元,用于分别判断每一中间文件内的文件中是否存在数据量大小超过第二预定数据量阈值的文件;
    第一处理单元,用于将存在数据量大小超过第二预定数据量阈值的文件的中间文件夹确定为待清理文件夹;
    第二处理单元,用于将不存在数据量大小超过第二预定数据量阈值的文件的中间文件夹确定为非待清理文件夹。
  14. 根据权利要求9所述的装置,其特征在于,所述中间文件夹处理模块,包括:
    第二判断单元,用于分别判断每一中间文件夹内的文件的总数据量是否超过第三预定数据量阈值;
    第三处理单元,用于将所包含文件的总数据量超过第三预定数据量阈值的中间文件夹确定为待清理文件夹;
    第四处理单元,用于将所包含文件的总数据量不超过第三预定数据量阈值的中间文件夹确定为非待清理文件夹。
  15. 根据权利要求9所述的装置,其特征在于,所述中间文件夹处理模块,包括:
    第三判断单元,用于分别判断每一中间文件内的文件中是否存在数据量大小超过第二预定数据量阈值的文件;
    第五处理单元,用于将存在数据量大小超过第二预定数据量阈值的文件的中间文件夹确定为待清理文件夹;
    第四判断单元,用于继续分别判断每一不存在数据量大小超过第二预定数据量阈值的文件的中间文件夹内的文件的总数据量是否超过第三预定数据量阈值;
    第六处理单元,用于将所包含文件的总数据量超过第三预定数据量阈值的中间文件夹确定为待清理文件夹;
    第七处理单元,用于将所包含文件的总数据量不超过第三预定数据量阈值的中间文件夹确定为非待清理文件夹。
  16. 根据权利要求9-15任意一项所述的装置,其特征在于,还包括:
    展示模块,用于展示所确定出的待清理数据,其中,所述待清理文件夹以文件夹图标形式展示,所述待清理文件以文件图标形式展示。
  17. 一种电子设备,其特征在于,包括:壳体、处理器、存储器、电路板和电源电路,其中,电路板安置在壳体围成的空间内部,处理器和存储器 设置在电路板上;电源电路,用于为电子设备的各个电路或器件供电;存储器用于存储可执行程序代码;处理器通过读取存储器中存储的可执行程序代码来运行与可执行程序代码对应的程序,以用于执行以下步骤:
    扫描位于所述电子设备的存储空间内的文件和文件夹;
    获得所扫描到的文件的数据量大小和第一类特征信息,以及所扫描到的文件夹的第二类特征信息;
    将所扫描到的文件夹中第二类特征信息满足预设文件夹特征信息的文件夹确定为运营文件夹;
    将所确定出的运营文件夹中的不满足预设常规垃圾判断条件的文件夹确定为中间文件夹;
    基于所包含文件的数据量大小,确定每一中间文件夹是否为待清理文件夹;
    将运营文件夹以外的数据量大小超过第一预定数据量阈值且第一类特征信息不符合预设文件特征信息的文件确定为待清理文件;
    将所确定出的待清理文件和所确定出的待清理文件夹确定为待清理数据。
  18. 一种应用程序,其特征在于,所述应用程序用于在运行时执行权利要求1-8任意一项所述的待清理数据识别方法。
  19. 一种存储介质,其特征在于,所述存储介质用于存储可执行程序代码,所述可执行程序代码被运行以执行权利要求1-8任意一项所述的待清理数据识别方法。
PCT/CN2016/096557 2015-08-27 2016-08-24 一种待清理数据识别方法、装置及电子设备 WO2017032313A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US15/752,162 US20180239839A1 (en) 2015-08-27 2016-08-24 Method and Apparatus for Identifying To-Be-Cleaned Data, and Electronic Device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510536577.9A CN105159975B (zh) 2015-08-27 2015-08-27 一种待清理数据识别方法、装置及电子设备
CN201510536577.9 2015-08-27

Publications (1)

Publication Number Publication Date
WO2017032313A1 true WO2017032313A1 (zh) 2017-03-02

Family

ID=54800831

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/096557 WO2017032313A1 (zh) 2015-08-27 2016-08-24 一种待清理数据识别方法、装置及电子设备

Country Status (3)

Country Link
US (1) US20180239839A1 (zh)
CN (1) CN105159975B (zh)
WO (1) WO2017032313A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105159975B (zh) * 2015-08-27 2018-09-11 北京金山安全软件有限公司 一种待清理数据识别方法、装置及电子设备
CN105787130B (zh) * 2016-03-30 2019-09-27 北京金山安全软件有限公司 图片清理方法、装置和移动终端
CN105893152A (zh) * 2016-03-31 2016-08-24 广东欧珀移动通信有限公司 一种内存管理方法、装置及移动终端
CN106708426B (zh) * 2016-11-11 2019-10-01 努比亚技术有限公司 垃圾文件识别装置和方法
US10917535B2 (en) * 2019-06-27 2021-02-09 Kyocera Document Solutions Inc. Scanning system with automatic file folder refiler
CN112698619A (zh) * 2021-01-25 2021-04-23 江苏米塔网络科技服务有限公司 一种设备运行状态判断方法
CN114224244B (zh) * 2021-11-09 2023-09-05 深圳市倍思科技有限公司 洗地机工作模式切换方法、装置、洗地机及存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102929980A (zh) * 2012-10-17 2013-02-13 广东欧珀移动通信有限公司 一种文件夹清理方法及装置
CN103559299A (zh) * 2013-11-14 2014-02-05 贝壳网际(北京)安全技术有限公司 清理文件的方法、装置及移动终端
CN103761306A (zh) * 2014-01-22 2014-04-30 深圳市欧珀通信软件有限公司 一种智能终端文件清理方法及装置
CN104317840A (zh) * 2014-10-10 2015-01-28 北京金山安全软件有限公司 一种文件清理方法、装置及终端
CN105045928A (zh) * 2015-08-27 2015-11-11 北京金山安全软件有限公司 一种待清理数据展示方法、装置及电子设备
CN105159975A (zh) * 2015-08-27 2015-12-16 北京金山安全软件有限公司 一种待清理数据识别方法、装置及电子设备

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100030814A1 (en) * 2008-08-01 2010-02-04 Yahoo! Inc. System, method, or apparatus relating to a data structure with a large number of entries
JP5512570B2 (ja) * 2011-02-24 2014-06-04 株式会社日立ソリューションズ 文書処理装置、及びファイルサーバ管理支援方法、並びにファイルサーバ管理支援プログラム
CN102333079A (zh) * 2011-02-25 2012-01-25 北京兴宇中科科技开发股份有限公司 一种磁盘空间清理方法
CN103365882A (zh) * 2012-03-30 2013-10-23 网秦无限(北京)科技有限公司 一种移动终端上垃圾文件清理的方法和系统
CN102880713B (zh) * 2012-09-29 2016-08-03 北京奇虎科技有限公司 文件清理方法及装置
CN104317741B (zh) * 2014-11-13 2017-05-03 北京奇虎科技有限公司 缓存目录的识别、清理方法和系统

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102929980A (zh) * 2012-10-17 2013-02-13 广东欧珀移动通信有限公司 一种文件夹清理方法及装置
CN103559299A (zh) * 2013-11-14 2014-02-05 贝壳网际(北京)安全技术有限公司 清理文件的方法、装置及移动终端
CN103761306A (zh) * 2014-01-22 2014-04-30 深圳市欧珀通信软件有限公司 一种智能终端文件清理方法及装置
CN104317840A (zh) * 2014-10-10 2015-01-28 北京金山安全软件有限公司 一种文件清理方法、装置及终端
CN105045928A (zh) * 2015-08-27 2015-11-11 北京金山安全软件有限公司 一种待清理数据展示方法、装置及电子设备
CN105159975A (zh) * 2015-08-27 2015-12-16 北京金山安全软件有限公司 一种待清理数据识别方法、装置及电子设备

Also Published As

Publication number Publication date
US20180239839A1 (en) 2018-08-23
CN105159975A (zh) 2015-12-16
CN105159975B (zh) 2018-09-11

Similar Documents

Publication Publication Date Title
WO2017032313A1 (zh) 一种待清理数据识别方法、装置及电子设备
WO2017032312A1 (zh) 一种待清理数据展示方法、装置及电子设备
CN103632165B (zh) 一种图像处理的方法、装置及终端设备
WO2017045443A1 (zh) 一种图像检索方法及系统
KR101872564B1 (ko) 무경계 표 검출 엔진
US9413704B2 (en) Presenting messages associated with locations
US20170366967A1 (en) Method and browser for browsing web page, and storage medium
US8600970B2 (en) Server-side search of email attachments
CN103365882A (zh) 一种移动终端上垃圾文件清理的方法和系统
CN105447115A (zh) 一种清理垃圾文件的方法、装置及电子设备
Faheem et al. Smartphone forensic analysis: A case study for obtaining root access of an android samsung s3 device and analyse the image without an expensive commercial tool
WO2018233155A1 (zh) 即时通信方法及装置
US10838917B2 (en) Junk picture file identification method, apparatus, and electronic device
WO2015196981A1 (zh) 一种鉴别图片垃圾文件的方法及装置
CN106776908B (zh) 数据清理方法、装置及终端
US20180349580A1 (en) Information processing method and device, and electronic equipment
US20190042600A1 (en) Image presenting method and apparatus, and electronic device
WO2018200284A1 (en) Media sharing based on identified physical objects
CN104869144A (zh) 一种信息分享方法及电子设备
CN109871685B (zh) 一种rtf文件的解析方法及装置
CN105608216A (zh) 一种管理注册信息的方法、装置及电子设备
WO2017076025A1 (zh) 一种信息处理方法、装置及电子设备
US10050994B2 (en) Method and computing device for processing data
CN103699571A (zh) 一种文件同步方法、装置及电子设备
CN104182479B (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: 16838571

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 15752162

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 11/06/2018)

122 Ep: pct application non-entry in european phase

Ref document number: 16838571

Country of ref document: EP

Kind code of ref document: A1