WO2021017899A1

WO2021017899A1 - Method for efficiently cleaning equipment files and device

Info

Publication number: WO2021017899A1
Application number: PCT/CN2020/102780
Authority: WO
Inventors: 谢琪; 钱凯
Original assignee: 华为技术有限公司
Priority date: 2019-07-30
Filing date: 2020-07-17
Publication date: 2021-02-04
Also published as: CN110543451A

Abstract

Provided is a method for efficiently cleaning equipment files, the method is applied to terminal equipment, the method comprises: the terminal equipment identifies file types of files generated in the application use process (S201); recording the cleaning frequency of the file of the file type (S202); when the file cleaning frequency of the file type is greater than or equal to a first threshold, the file type is used as a first recommended cleaning file type, and the first recommended cleaning file type is added into a recommended cleaning list (S203). By recognizing the file type of the file, and recording the cleaning frequency of each file type, when the cleaning frequency is high, the file type is recommended. The user of the terminal equipment can be effectively helped to clean junk files in the terminal equipment more simply and quickly, and files to be cleaned do not need to be selected manually, the cleaning operation is more convenient and faster, file cleaning time is shortened, and cleaning efficiency and usability are improved.

Description

Method and device for efficiently cleaning equipment files

This application claims the priority of a Chinese patent application filed with the National Patent Office on July 30, 2019, the application number is 201910693918. 1, the invention title is "a method and device for efficiently cleaning equipment files", the entire content of which is incorporated by reference In this application.

Technical field

This application relates to the field of intelligent identification, and in particular to a method and device for efficiently cleaning equipment files.

Background technique

In today's society, electronic equipment has become an indispensable tool in people's life and work. However, in daily life, with the needs of people's life and work, electronic devices, such as mobile phones, tablet computers and other devices, will generate a large number of files during use. For example, in daily use, an application in an electronic device will generate files such as pictures, videos, audios, and installation packages, and occupy a large amount of storage space of the electronic device. Finally, the electronic equipment becomes very lagging when running, which seriously affects normal use.

Summary of the invention

The embodiment of the application provides a method and device for efficiently cleaning device files. By identifying the file type of the file generated during the use of the application in the terminal device, and according to the frequency with which the file type is cleaned, the frequently cleaned file type is recommended for cleaning File types are recommended, so that you do not need to manually select files when cleaning up files, and you can clean up frequently cleaned files with one click, making the cleaning operation more convenient.

In a first aspect, a method for efficiently cleaning device files is provided. The method is applied to a terminal device. The method includes: the terminal device recognizes the file type of the file generated during the use of the application; and records the frequency of the file cleaning of the first file type; When the frequency of files of the first file type being cleaned is greater than or equal to the first threshold, the first file type is added to the list of recommended cleaning.

In a possible implementation, the method further includes: recording the number of times the file of the second file type is used; when the number of times the file of the second file type is used is less than or equal to the second threshold, adding the second file type to It is recommended to clean up the list.

In a possible implementation manner, the method further includes: sending the first file type and/or the second file type to the server, so that the server determines the file type recommended by the server for cleaning according to the first file type and/or the second file type.

In a possible implementation manner, the method further includes: receiving a file type recommended by the server for cleaning from the server, and adding the file type recommended for cleaning by the server to a list of recommended cleaning.

In a possible implementation manner, the method further includes: performing one-click cleaning of the file types selected in the recommended cleaning list; or selecting the file types in the recommended cleaning list, filtering the contents of the file types individually, and Clean up.

In a possible implementation manner, the recommended cleaning list includes one or more file types; each file type in the recommended cleaning list has a selection box so that the terminal device can clean the selected file types.

In a possible implementation manner, the file type includes at least one of pictures, videos, audios, and application installation packages.

In a possible implementation manner, the file type includes: at least one of fuzzy pictures, similar pictures, two-dimensional codes, advertisements, screenshots, and emoticons.

In a second aspect, a method for efficiently cleaning device files is provided, which is characterized in that the method is applied to a server, and the method includes: receiving a first file type and/or a second file type sent by multiple terminal devices; When the number of terminal devices of the file type is greater than or equal to the third threshold, the first file type is used as the server to recommend cleaning file types; and when the number of terminal devices that recommend the second file type is greater than or equal to the third threshold, the second file type is used as the server Recommended file types to be cleaned up; the server-recommended file types to be cleaned up are sent to terminal devices other than multiple terminal devices.

In a third aspect, an apparatus for efficiently cleaning device files is provided. The apparatus includes: an identification module for identifying file types of files generated during application use; and a counting module for recording the cleanup of files of the first file type. Frequency: The processing module is used to add the first file type to the recommended cleaning list when the frequency with which the files of the first file type are cleaned is greater than or equal to the first threshold.

In a possible implementation, the counting module is also used to record the number of times the file of the second file type is used; the processing module is also used to: when the number of times the file of the second file type is used is less than or equal to the second threshold , Add the second file type to the recommended cleaning list.

In a possible implementation manner, the apparatus further includes: a sending module, configured to send the first file type and/or the second file type to the server, so that the server can determine the server recommendation according to the first file type and/or the second file type Clean up file types.

In a possible implementation manner, the device further includes: a receiving module, configured to receive the server recommended cleaning file type sent by the server, and add the server recommended cleaning file type to the recommended cleaning list.

In a possible implementation, the processing module is also used to: perform one-click cleaning of the file types ticked in the recommended cleaning list; or select the file types in the recommended cleaning list to individually filter the contents of the file types , And clean up.

In a fourth aspect, an apparatus for efficiently cleaning device files is provided, characterized in that the apparatus includes: a receiving module for receiving a first file type and/or a second file type sent by multiple terminal devices; a processing module for When the number of terminal devices recommending the first file type is greater than or equal to the third threshold, the first file type is used as the recommended cleaning file type; and when the number of terminal devices recommending the second file type is greater than or equal to the third threshold, the second The file type is used as the recommended cleaning file type of the server; the sending module is used to send the recommended cleaning file type of the server to other terminal devices except multiple terminal devices.

In a fifth aspect, a terminal is provided. The terminal includes a processor, the processor is coupled with a memory, and the processor reads and executes instructions in the memory, so that the terminal executes the method of the first aspect.

In a sixth aspect, a terminal is provided, the terminal includes a processor, the processor is coupled with a memory, and the processor reads and executes instructions in the memory, so that the server executes the method of the second aspect.

In a seventh aspect, a computer-readable storage medium storing a program is provided. The program includes instructions. When the instructions are executed by a computer, the computer executes the method of the first aspect.

In an eighth aspect, a computer-readable storage medium storing a program is provided. The program includes instructions. When the instructions are executed by a computer, the computer executes the method of the second aspect.

In a ninth aspect, a computer program product containing instructions is provided, which when run on a terminal, causes the method of the first aspect to be executed.

In a tenth aspect, a computer program product containing instructions is provided, which when run on an electronic device, causes the method of the second aspect to be executed.

This application discloses a method and device for efficiently cleaning equipment files. By identifying the file type of the file, and recording the frequency of each file type being cleaned, when the frequency of cleaning is high, the file type is recommended. It can effectively help terminal device users to clean up junk files in the terminal device more simply and quickly, and there is no need to manually select the files that need to be cleaned, making the cleaning operation more convenient, shortening the time to clean files, and improving the efficiency and ease of cleaning. Usability.

Description of the drawings

Figure 1 is a schematic diagram of file cleaning provided by an embodiment of the application;

FIG. 2 is a flowchart of a method for efficiently cleaning device files according to an embodiment of the application;

FIG. 3 is a flowchart of another method for efficiently cleaning device files according to an embodiment of the application;

FIG. 4 is a flowchart of another method for efficiently cleaning device files according to an embodiment of the application;

FIG. 5 is a flowchart of another method for efficiently cleaning device files according to an embodiment of the application;

Figure 6 is a schematic diagram of an efficient file cleaning provided by an embodiment of the application;

FIG. 7 is a schematic diagram of another efficient file cleaning provided by an embodiment of the application;

FIG. 8 is a schematic diagram of yet another efficient file cleaning provided by an embodiment of the application;

FIG. 9 is a schematic diagram of an apparatus for efficiently cleaning device files according to an embodiment of the application;

FIG. 10 is a schematic diagram of another device for efficiently cleaning device files according to an embodiment of the application;

FIG. 11 is a schematic structural diagram of a terminal provided by an embodiment of this application;

FIG. 12 is a schematic structural diagram of a server provided by an embodiment of this application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

This application can be applied to scenarios where users clean up junk files on terminal devices. In this scenario, the user will generate a large number of files when using some applications of the terminal device. For these files, some are files that users will frequently use, and the other may be files that users will use temporarily, which will no longer be used later and become junk files stored on terminal devices. But for the cleanup of these junk files, in some solutions, different files are presented one by one according to different file types. For users, when preparing to clean up some files of the terminal device, they need to filter the types that need to be cleaned, and the files that need to be cleaned under this type. As shown in FIG. 1, FIG. 1 is a schematic diagram of file cleaning provided by an embodiment of this application. The terminal device in Figure 1 takes a mobile phone as an example, showing that in this interface, only files are displayed one by one according to different file types. However, for a certain type of file, it is not recognized which file type is the file type that the user frequently cleans. For users, they need to be individually selected for cleaning.

In response to the above-mentioned problems, this application records the cleaning frequency of these cleaned files, and recommends this type of file when a certain frequency is reached. When the user cleans up the file again, it will be shown to the user as a priority recommendation, so that the user does not need to select the file to be cleaned when cleaning the file, which makes the cleaning operation more convenient, shortens the time to clean the file, and improves the cleaning efficiency and ease of use Sex.

The technical solutions in the embodiments of the present application will be described in detail below in conjunction with the drawings in the embodiments of the present application.

As shown in FIG. 2, FIG. 2 is a flowchart of a method for efficiently cleaning device files according to an embodiment of the application.

Figure 2 provides a method for efficiently cleaning device files. This method can be applied to terminal equipment. Those skilled in the art should note that the terminal devices involved in this application can be any terminal devices such as mobile phones, computers, tablets, and wearable devices. This application is not limited here.

The method can include the following steps:

S201: The terminal device recognizes the file type of the file generated during the use of the application.

In one embodiment, the terminal device recognizes the file type of the file generated when its own device uses different applications. In an example, for example, the terminal device may be a mobile phone, and the mobile phone can recognize that it is using different applications. For example, when the mobile phone uses different applications such as WeChat, Weibo, camera, and browser, the file type of the file generated during the use process. For example, when using WeChat, Weibo, camera, browser and other applications, some pictures are generated through screenshots, screenshots or saved, and the file type is recognized as pictures or videos; or when using a music player or browser , Weibo or WeChat and other applications, the generated file type is music file; or when using WeChat, QQ and other chat tools, some file types are generated, such as word, excel, ppt, pdf, etc.; Or, when downloading the application using the application store, a file of the application installation package is generated.

In one example, the terminal can identify the file type of the file when scanning the file. In another example, the terminal can immediately recognize the file type of the file when the file is generated. In another example, when the user selects file deletion, the terminal identifies the file type of the file to be deleted.

Those skilled in the art should note that the file types involved in this application are not limited to the above examples, and can also include any file type. Any easily conceivable changes or substitutions should be covered by the protection scope of this application.

In one embodiment, the file type may include at least one of pictures, videos, audios, application installation packages, and so on.

In an example, the file types can be classified according to file formats, such as pictures, audios, videos, installation packages, word, ppt, etc. In another example, file types can also be classified according to the source of the file, such as WeChat, camera, and files generated in a browser.

In one embodiment, for files of file types such as pictures, more detailed classifications can also be identified. In an example, the picture can also be divided according to the picture quality, such as a blurred picture and a clear picture. In another example, file types can also be classified according to usage, such as at least one of two-dimensional codes, advertisements, screenshots, and emoticons. In another example, the file types can also be classified according to the content of the pictures, for example, there are different file types such as two-dimensional code, people, scenery, architecture, food, flowers, sky, etc. In another example, the file type may also include similar pictures. Those in the art should note that the above-mentioned file classifications are not unique, and can be classified according to other conditions, and this application is not limited here.

In another example, the file size can also be identified, for example, the data size of the storage space of the terminal device occupied by different pictures.

S202: Record the frequency at which files of the first file type are cleaned up.

In one example, the mobile phone records how often files of various file types are cleaned up. Wherein, the frequency of being cleaned may be the number of times that files of the file type are cleaned in a period of time. For example, the period of time can be set to one month, three months, half a year, one year, etc. In another example, each time a file of this file type is deleted, the number of times it has been cleaned up can be increased by one. In another example, each time a file of the file type is deleted, the number of times that it is cleaned up can be increased by one, and deleting a file of the file type once may be deleting multiple files of the file type at one time. Those skilled in the art should note that the period of cleaning frequency involved in this application can be any fixed period of time, which is not limited in this application.

In one example, the frequency with which files of the first file type are cleaned can be recorded.

S203: When the frequency of cleaning files of the first file type is greater than or equal to the first threshold, the first file type is used as the first recommended cleaning file type and added to the list of recommended cleaning.

In one embodiment, when the frequency of cleaning files of the first file type is greater than or equal to the first threshold, the file type is regarded as the first recommended cleaning file type and added to the recommended cleaning list. In an example, for example, the file type of a QR code file is cleaned 5 times in a month, and the preset first threshold can be cleaned 3 times in a month, the mobile phone determines the QR code type If the frequency of the file being cleaned is greater than the preset first threshold, the QR code type is used as the first recommended file type to be cleaned and added to the list of recommended cleansing. When the user cleans up the file, the QR code type will be displayed in the recommendation list as a priority recommendation for cleaning. In another example, for example, the frequency that a file with a QR code file type is cleaned 5 times in the first month, and the preset first threshold can be cleaned 3 times a month, the mobile phone determines The QR code type files are cleaned more frequently than the preset first threshold. First, the QR code type is not used as the first recommended file type to be cleaned, and it is added to the list of recommended cleansing. When 4 is cleaned in the second month 2 times, 6 times in the third month, the mobile phone detects that the frequency of 3 consecutive times that the QR code file has been cleaned is more than 3 times, then the QR code type is the first recommended file type to be cleaned up and added It is recommended to clean up the list. When the user cleans up the file, the QR code type will be displayed in the recommendation list as a priority recommendation for cleaning. In another example, for example, the frequency that a file with a QR code file type is cleaned 5 times in the first month, and the preset first threshold can be cleaned 3 times a month, the mobile phone determines The frequency with which files of the QR code type are cleaned up is greater than the preset first threshold. First, the QR code type is not used as the first recommended file type to be cleaned, and it is added to the list of recommended cleanups. When it is cleaned in the second month 2 2 times, 6 times in the third month, the mobile phone detects more than 2 times of the two-dimensional code type files are cleaned up more than 3 times, the two-dimensional code type as the first recommended file type to clean up, add It is recommended to clean up the list. When the user cleans up the file, the QR code type will be displayed in the recommendation list as a priority recommendation for cleaning. S204: Perform one-click cleaning of the file types selected in the recommended cleaning list; or select the file types in the recommended cleaning list, individually filter the files in the file type, and perform cleaning.

In one embodiment, the recommended cleaning list includes one or more file types. Each file type in the recommended cleaning list can have a selection box so that the user can select one or more file types, and the terminal device will check the selected file types for cleaning.

In one embodiment, the user can perform one-click cleaning of the selected file types in the recommended cleaning list, so as to achieve rapid cleaning without the user having to filter separately. In another embodiment, if some files of the file types currently recommended for cleaning still need to be kept. The user can also select the file type in the recommended cleaning list, and filter the specific files in the file type one by one, and then clean the files that have been individually filtered.

In one example, the first recommended cleaning file type is in the recommended cleaning list, and it is checked by default. So that users do not need to manually check again when cleaning up, simplifying the cleaning operation and improving the efficiency of cleaning.

As shown in FIG. 3, FIG. 3 is a flowchart of another method for efficiently cleaning device files according to an embodiment of the application.

After S201 shown in FIG. 2, the following steps may be further included:

S205: Record the number of times the file of the second file type is used.

In one example, the mobile phone records the number of times a file of each file type is used. The number of times used may be the number of times a file of the file type is used within a period of time. For example, the period of time can be set to the last month, the last three months, the last six months, the last year, etc. For example, application installation package 1 has been called only once in the last month, and application installation package 2 has been called only once in the last month. The terminal device can use the file type of application installation package as the recommended file type. Recommended; or some screenshots have only been used once in the last month, and some screenshots are useless even once. You can recommend the screenshot file type as the recommended file type.

S206: When the number of times the file of the file type is used is less than or equal to the second threshold, the second file type is taken as the second recommended cleaning file type and added to the recommended cleaning list.

In an embodiment, for a terminal device such as a mobile phone, the number of times the file type is used can also be identified. For example, when a file of a certain file type is used too few times, it can be determined that the file of this file type is not frequently used by the user. For files that are not frequently used, but occupy the storage space of the mobile phone for a long time, the mobile phone can determine that the files of this file type are junk files and can be recommended for cleaning. In one example, for example, the mobile phone recognizes that certain screenshots have only been used once, or even not used once. The second threshold can be preset to 1 time. The mobile phone determines that the file type is a screenshot file. When the mobile phone determines that the number of times a file of this screenshot type has been used is less than the second threshold, it determines that the screenshot type is the second recommended cleaning file type and adds it to the recommended cleaning list for users When cleaning up junk files, it is more convenient and quick to clean up junk files.

After S206, S204 as shown in FIG. 2 can be continued.

In one example, the second recommended cleaning file type is in the recommended cleaning list, and it is checked by default. So that users do not need to manually check again when cleaning up, simplifying the cleaning operation and improving the efficiency of cleaning.

It is understandable that the above embodiments shown in FIG. 2 and FIG. 3 can be implemented in combination, and the terminal device recognizes the file types that are frequently cleaned up and the file types that are used less frequently, and both are displayed in the recommended cleanup list.

As shown in FIG. 4, FIG. 4 is a flowchart of yet another method for efficiently cleaning device files according to an embodiment of the application.

After S203 shown in FIG. 2 or S206 shown in FIG. 3, the following steps may be further included:

S207: Send the first recommended cleaning file type and/or the second recommended cleaning file type to the server, so that the server determines the third recommended cleaning file type according to the first recommended cleaning file type and/or the second recommended cleaning file type.

In one embodiment, the mobile phone can send the file types that it cleans frequently, that is, the recommended first recommended clean file type, and the file types that it does not frequently use, that is, the second recommended clean file type, to the server. So that the server can determine the recommended cleaning file type for the server according to the recommended cleaning file types recommended by multiple different mobile phones, and recommend the corresponding cleaning file type for other mobile phones, that is, the third recommended cleaning file type.

In an example, when the third recommended cleaning file type is the first recommended cleaning file type, the server can identify which terminal devices have sent the first recommended cleaning file type, and avoid when sending the third recommended cleaning file type The terminal device that has sent the first recommended cleaning file type, and the third recommended cleaning file type is sent to other terminal devices. Of course, it is understandable that, in another example, the server may directly send the third recommended cleaning file type, regardless of whether the terminal device has sent the first recommended cleaning file type. In addition, the mobile phone can also receive the third recommended cleaning file type sent by the server, as follows: S208

S208: Receive the third recommended cleaning file type sent by the server, and add the third recommended cleaning file type sent by the server to the recommended cleaning list.

In another embodiment, the mobile phone receives the server recommended cleaning file type sent by the server, that is, the third recommended cleaning file type, and the mobile phone can determine whether it has the same recommended cleaning file type as the third recommended cleaning file type. For example, the third recommended cleaning file type sent by the server is the first recommended cleaning file type that has been determined by the mobile phone and already exists in the recommended cleaning list, so there is no need to add it again. If the third recommended cleaning file type sent by the server is one of the file types recognized by the mobile phone, but not the first recommended cleaning file type and the second recommended cleaning file type that the mobile phone has determined, but it does not appear in the recommended cleaning In the list, the mobile phone can add the third recommended cleaning file type to the recommended cleaning list, so that the user can recommend cleaning. If the third recommended cleaning file type sent by the server is not one of the file types recognized by the mobile phone, and it is not the first recommended cleaning file type and the second recommended cleaning file type that the mobile phone has determined, it does not appear in the recommended In the cleaning list, the mobile phone can add the recommended cleaning file type to the recommended cleaning list, so that the user can recommend cleaning. Those skilled in the art should note that when the third recommended cleaning file type sent by the server is not one of the file types identified by the mobile phone and does not appear in the recommended cleaning list, you can choose to add or not add it according to the actual situation. It is not limited here.

In an example, the third recommended cleaning file type sent by the server is in the recommended cleaning list, and the default is not checked. When the user cleans up, he can check it separately according to the actual situation.

In addition, the mobile phone can also receive the fourth recommended cleaning file type sent by the server, and the mobile phone can use the above processing method to process.

Those skilled in the art should note that there is no order in which steps S207 and S208 are executed sequentially.

After S208, S204 as shown in FIG. 2 can be continued.

Those skilled in the art should also note that steps 207 and 208 may also be performed after step 204.

This application discloses a method for efficiently cleaning device files. By identifying the file type of the file, and recording the frequency with which each file type is cleaned, when the frequency of cleaning is high, the file type is recommended. It can effectively help terminal device users to clean up junk files in the terminal device more simply and quickly, and there is no need to manually select the files that need to be cleaned, making the cleaning operation more convenient, shortening the time to clean files, and improving the efficiency and ease of cleaning. Usability.

As shown in FIG. 5, FIG. 5 is a flowchart of another method for efficiently cleaning device files according to an embodiment of the application;

Figure 5 provides an efficient way to clean up device files. This method can be applied to the server. The method can include the following steps:

S501: Receive a first recommended cleaning file type and/or a second recommended cleaning file type sent by multiple terminal devices.

In an embodiment, the server receives the first recommended cleaning file type and/or the second recommended cleaning file type sent by multiple terminal devices. Among them, the terminal device may also be one or more different terminal devices. In one example, the terminal device may send only the first recommended cleaning file type, or only the second recommended cleaning file type. In another example, the first recommended cleaning file type and the second recommended cleaning file type may also be sent at the same time. In another example, the first terminal device can send the first file type, and the second terminal device can send the second file type.

S502: When the number of terminal devices recommending the first recommended file type to be cleaned is greater than or equal to a third threshold, use the first recommended file type to be cleaned as the third recommended file type; and when the number of terminal devices recommending the second file type is greater than or equal to the first When the threshold is three, the second file type is used as the fourth recommended file type for cleaning. The server recommended file types for cleaning include the third recommended file type for cleaning and the fourth recommended file type for cleaning.

In an example, suppose that the server determines that there are 5000 terminal devices whose recommended cleaning file type is the screenshot type, and the preset third threshold may be 1000. When the server can determine that the number of terminal devices whose recommended cleaning type is a screenshot type is greater than the third threshold 1000, the screenshot type can be used as the server recommended cleaning file type, that is, the third recommended cleaning file type.

S503: Send the file type recommended by the server to be cleaned up to the terminal device.

In one embodiment, the server sends the determined file type recommended by the server to be cleaned up to each terminal device, so that after receiving the file type recommended by the server to clean up, each terminal device makes a corresponding recommendation according to its own device situation. In an example, the server may send the third recommended clean-up file type to other terminal devices other than the multiple terminal devices. For example, the file type sent by the server is file type A. When mobile phone A recommends file type A, The server can send other mobile phones that do not recommend A file type. In another example, it can also be sent to each terminal device indiscriminately. For example, the file type sent by the server is file type A, and the server does not need to know whether A mobile phone recommends file type A. The server only needs to send file type A to include file type A. All the phones in the phone are fine. For example, the third recommended cleaning file type may be a screenshot, and the server sends the screenshot type as recommended cleaning to each terminal device, and each terminal device recommends the screenshot type as recommended cleaning to the user according to the file cleaning status of its own device.

This application discloses a method for efficiently cleaning device files. The recommended file type is reported to a server, and the server makes a comprehensive judgment based on the information reported by different terminal devices. When the server determines that a certain file type has most of the terminal devices as a recommendation, the server can also recommend the type as a recommendation to other terminal devices, so that other terminal devices can use this type as an optional cleaning Items make the cleaning operation more convenient, shorten the time for cleaning files, and improve the efficiency and ease of cleaning.

As shown in FIG. 6, FIG. 6 is a schematic diagram of an efficient file cleaning provided by an embodiment of the application.

The terminal device in Fig. 6 takes a mobile phone as an example, showing a display interface for efficient file cleaning. In this interface, it can be seen that the file type is fuzzy picture as the recommended cleaning file type, which is displayed under the recommended cleaning list, and the file type is checked by default. The user can select the "one-click cleanup" button based on the recommendation to quickly clean up junk files. The user can click on the file type, such as "fuzzy picture" to enter the next level of the file type. As shown in the right interface in Figure 6, for the file type of the fuzzy picture, the user can selectively delete the files under the file type according to their actual needs by filtering the files under the file type one by one. For example, in the right side of Figure 6, each picture has a check box. When the check box of the picture is checked, click the "Clean up" button below to delete the checked pictures.

As shown in FIG. 7, FIG. 7 is a schematic diagram of another efficient file cleaning provided by an embodiment of the application.

The terminal device in Fig. 7 takes a mobile phone as an example, showing a display interface for efficient file cleaning. In this interface, it can be seen that the file type is similar to the picture as the recommended cleaning file type, which is displayed under the recommended cleaning list, and the file type is checked by default. The user can select the "one-click cleanup" button based on the recommendation to quickly clean up junk files. The user clicks on the file type, such as "similar pictures", to enter the next level of the file type. As shown in the right interface in Figure 7, for the file type of the similar picture, the user can selectively delete the files under the file type according to their actual needs. For example, in the right side of Figure 7, each picture has a check box. The system selects one of the similar pictures by default. At the same time, the user can also select both similar two pictures, or select a part of the pictures. When the check box of the picture is checked, click the "Clean up" button below to delete the checked picture.

As shown in FIG. 8, FIG. 8 is a schematic diagram of yet another efficient file cleaning provided by an embodiment of this application.

The terminal device in FIG. 8 takes a mobile phone as an example, showing a display interface for efficient file cleaning. In this interface, for a certain application, the recommended cleaning file type in the recommended cleaning list under the application can be displayed, and the file type is checked by default. For example, the application can be WeChat, and some file types generated in the WeChat application, such as junk files, Moments pictures, Moments videos, QR code pictures, advertisement pictures, screenshot pictures, etc., are displayed in the recommended cleaning list. The user can select the "one-click cleanup" button based on the recommendation to quickly clean up junk files. The user can also choose the recognized recommended file type for cleaning. For example, the user can select only the screenshot image and then select the "one-click cleaning" button to quickly clean up the screenshot image. For different file types, users can enter the next level of each file type according to their actual needs, and selectively delete the files under that file type by filtering them one by one. Of course, for this application, such as WeChat, you can also directly select special cleaning, that is, cleaning files of different file types. The special cleaning may include file types recommended for cleaning, or may not include file types recommended for cleaning. Those skilled in the art should understand that special cleaning is the cleaning method for different file types before the mobile phone recommends certain file types.

As shown in FIG. 9, FIG. 9 is a schematic diagram of an apparatus for efficiently cleaning device files according to an embodiment of the application.

FIG. 9 provides an apparatus 900 for efficiently cleaning device files. The device 900 may be a terminal device. The device 900 includes: an identification module 901, used to identify the file type of a file generated during the use of the application; a counting module 902, used to record how often files of the first file type are cleaned; a processing module 903: When the frequency of cleaning files of the first file type is greater than or equal to the first threshold, the first file type is used as the first recommended cleaning file type and added to the recommended cleaning list.

In a possible implementation, the counting module 902 is also used to record the number of times the file of the second file type is used; the processing module 903 is also used to: when the number of times the file of the second file type is used is less than or equal to the second When the threshold is set, the second file type is used as the second recommended file type for cleaning and added to the list of recommended cleaning.

In a possible implementation manner, the apparatus 900 further includes: a sending module 904, configured to send the first recommended cleaning file type and/or the second recommended cleaning file type to the server, so that the server can clean the file type and/or according to the first recommendation. Or the second recommended cleaning file type determines the third recommended cleaning file type.

In a possible implementation manner, the apparatus 900 further includes: a receiving module 905, configured to receive the third recommended cleaning file type sent by the server, and add the third recommended cleaning file type sent by the server to the recommended cleaning list.

In a possible implementation, the processing module 903 is also used to: perform one-click cleaning of the file types selected in the recommended cleaning list; or select the file types in the recommended cleaning list to separate the contents of the file types Screen and clean up.

In a possible implementation manner, the file type includes at least one of pictures, application files, videos, audios, and application installation packages.

The present application discloses a device for efficiently cleaning equipment files. By identifying the file type of the file, and recording the frequency of each file type being cleaned, when the frequency of cleaning is high, the file type is recommended. It can effectively help terminal device users to clean up junk files in the terminal device more simply and quickly, and there is no need to manually select the files that need to be cleaned, making the cleaning operation more convenient, shortening the time to clean files, and improving the efficiency and ease of cleaning. Usability.

As shown in FIG. 10, FIG. 10 is a schematic diagram of another device for efficiently cleaning device files according to an embodiment of the application.

FIG. 10 provides an apparatus 1000 for efficiently cleaning device files. The apparatus 1000 may be a server, and the apparatus 1000 includes: a receiving module 1001 for receiving the first recommended cleaning file type and/or the second recommended cleaning file type sent by the terminal device; a processing module 1002 for when the first recommended cleaning file type is recommended When the number of terminal devices of the file type and/or the second recommended cleaning file type is greater than or equal to the third threshold, the first recommended cleaning file type and/or the second recommended cleaning file type are used as the third recommended cleaning file type; the sending module 1003, Used to send the third recommended cleaning file type to the terminal device.

This application discloses a device for efficiently cleaning device files. By reporting the recommended file type to a server, the server then makes a comprehensive judgment based on the information reported by different terminal devices. When the server determines that a certain file type has most of the terminal devices as a recommendation, the server can also recommend the type as a recommendation to other terminal devices, so that other terminal devices can use this type as an optional cleaning Items make the cleaning operation more convenient, shorten the time for cleaning files, and improve the efficiency and ease of cleaning.

As shown in FIG. 11, FIG. 11 is a schematic structural diagram of a terminal according to an embodiment of the present invention.

FIG. 11 provides a terminal device 1100. The terminal device 1100 may include a processor 1101, a memory 1102, a communication interface 1103, and a bus 1104. The processor 1101, the memory 1102, and the communication interface 1103 in the terminal device may establish a communication connection through the bus 1104. The communication interface 1104 is used to send and receive external information.

The processor 1101 may be a central processing unit (CPU).

The memory 1102 may include volatile memory (volatile memory), such as random-access memory (RAM); the memory 1102 may also include non-volatile memory (English: non-volatile memory), such as read-only memory (read-only memory, ROM), flash memory, hard disk drive (HDD) or solid state drive (SSD); the memory 1102 may also include a combination of the foregoing types of memory.

The method for efficiently cleaning device files provided by the embodiments in FIG. 2 to FIG. 4 are all executed by the processor 1101. The file data and/or calculated data in this application will be stored in the memory 1102. In addition, the memory 1102 will also be used to store program instructions executed by the processor for implementing the method for efficiently cleaning device files described in the above-mentioned embodiments in FIG. 2 to FIG. 4 and so on.

As shown in FIG. 12, FIG. 12 is a schematic structural diagram of a server according to an embodiment of the present invention.

FIG. 12 provides a server 1200. The server 1200 may include a processor 1201, a memory 1202, a communication interface 1203, and a bus 1204. The processor 1201, the memory 1202, and the communication interface 1203 in the terminal device may establish a communication connection through the bus 1204. The communication interface 1204 is used to send and receive external information.

The processor 1201 may be a central processing unit (CPU).

The memory 1202 may include volatile memory (volatile memory), such as random-access memory (RAM); the memory 1202 may also include non-volatile memory (English: non-volatile memory), such as read-only memory (read-only memory, ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD); the memory 1202 may also include a combination of the foregoing types of memory.

The method for efficiently cleaning device files provided by the embodiment in FIG. 5 is all executed by the processor 1201. The file data and/or calculated data in this application will be stored in the memory 1202. In addition, the memory 1202 will also be used to store program instructions and the like corresponding to the method for efficiently cleaning device files described in the embodiment in FIG. 5 and executed by the processor.

This application identifies the file type of the file and records how often each file type is cleaned. When the frequency of cleansing is high, the file type is recommended. It can effectively help terminal device users to clean up junk files in the terminal device more simply and quickly, and there is no need to manually select the files that need to be cleaned, making the cleaning operation more convenient, shortening the time to clean files, and improving the efficiency and ease of cleaning. Usability.

Those of ordinary skill in the art should be further aware that the units and algorithm steps of the examples described in the embodiments disclosed herein can be implemented by electronic hardware, computer software or a combination of both, in order to clearly illustrate the hardware For the interchangeability with software, the composition and steps of each example have been described generally in terms of function in the above description. Whether these functions are executed by hardware or software depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

Those of ordinary skill in the art can understand that all or part of the steps in the methods of the above embodiments can be implemented by a program instructing a processor to complete, and the program can be stored in a computer-readable storage medium, which is non-transitory ( English: non-transitory media, such as random access memory, read only memory, flash memory, hard disk, solid state drive, magnetic tape (English: magnetic tape), floppy disk (English: floppy disk), optical disc (English: optical disc) And any combination.

The above are only preferred specific implementations of this application, but the protection scope of this application is not limited to this. Any person skilled in the art can easily think of changes or changes within the technical scope disclosed in this application. Replacement shall be covered within the scope of protection of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

A method for efficiently cleaning device files, characterized in that the method is applied to a terminal device, and the method includes:

The terminal device recognizes the file type of the file generated during the use of the application;

Record the frequency with which files of the first file type are cleaned;

When the frequency of the files of the first file type being cleaned is greater than or equal to the first threshold, the first file type is added to the list of recommended cleaning.
The method of claim 1, wherein the method further comprises:

Record the number of times a file of the second file type is used;

When the number of times the file of the second file type is used is less than or equal to the second threshold, the second file type is added to the list of recommended cleaning.
The method according to claim 1 or 2, wherein the method further comprises:

The first file type and/or the second file type are sent to the server, so that the server determines the file type recommended by the server for cleaning according to the first file type and/or the second file type.
The method according to claim 1 or 2, wherein the method further comprises:

Receiving the server recommended cleaning file type sent by the server, and adding the server recommended cleaning file type to the recommended cleaning list.
The method according to any one of claims 1-4, wherein the recommended cleaning list includes one or more file types;

Each file type in the recommended cleaning list has a selection box, so that the terminal device cleans the selected file type.
The method according to claim 1, wherein the file type includes at least one of picture, video, audio, and application installation package.
The method according to claim 1, wherein the file type includes at least one of a fuzzy picture, a similar picture, a two-dimensional code, an advertisement, a screenshot, and an emoticon.
A device for efficiently cleaning equipment files, characterized in that the device includes:

The identification module is used to identify the file type of the file generated during the use of the application;

The counting module is used to record the frequency of files of the first file type being cleaned up;

The processing module is configured to add the first file type to the list of recommended cleaning when the frequency of cleaning the files of the first file type is greater than or equal to a first threshold.
9. The device according to claim 8, wherein the counting module is further configured to record the number of times a file of the second file type is used;

The processing module is further configured to add the second file type to the recommended cleaning list when the number of times the file of the second file type is used is less than or equal to a second threshold.
The device according to claim 8 or 9, wherein the device further comprises:

The sending module is configured to send the first file type and/or the second file type to the server, so that the server can determine the file type recommended by the server for cleaning according to the first file type and/or the second file type .
The device according to claim 8 or 9, wherein the device further comprises:

The receiving module is configured to receive the file type recommended by the server for cleaning and adding the file type recommended for cleaning by the server to the list of recommended cleaning.
11. The device according to any one of claims 8-11, wherein the recommended cleaning list includes one or more file types;

Each file type in the recommended cleaning list has a selection box, so that the terminal device cleans the selected file type.
The device according to claim 8, wherein the file type includes at least one of picture, video, audio, and application installation package.
8. The device of claim 8, wherein the file type includes at least one of a blurred picture, a similar picture, a two-dimensional code, an advertisement, a screenshot, and an expression.
A terminal, wherein the terminal includes a processor, the processor is coupled with a memory, and the processor reads and executes instructions in the memory, so that the terminal executes the claims 1-7 Any of the methods described.
A computer-readable storage medium storing a program, wherein the program includes instructions that, when executed, cause the method according to any one of claims 1-7 to be executed.