WO2015090173A1

WO2015090173A1 - Software cleaning method and system

Info

Publication number: WO2015090173A1
Application number: PCT/CN2014/093861
Authority: WO
Inventors: 牛强; 张庭; 王务志; 陈耀攀
Original assignee: 北京奇虎科技有限公司; 奇智软件（北京）有限公司
Priority date: 2013-12-16
Filing date: 2014-12-15
Publication date: 2015-06-25

Abstract

The present invention provides a software cleaning method and system. The method comprises: providing a software cleaning method according to one aspect of the present invention, the method comprising: identifying an installed software according to prerecorded software installation information; acquiring a cleaning request for the installed software, the cleaning request comprising descriptive information of the installed software; searching for descriptive information of related files of the installed software in a preset software information base according to the descriptive information of the installed software; and deleting the related files according to the descriptive information of the related files. The advantage of the present invention lies in that which software has been installed can be accurately checked by reverse checking and the user is informed, so as to make the user know which software has been installed and determine whether to clean the software.

Description

Software cleaning method and system

Technical field

The present invention relates to the field of computer technologies, and in particular, to a software cleaning method and system.

Background technique

With the development of computer and Internet technologies, various application software has emerged in an endless stream. Most of the software is very easy and friendly to install. Basically, it will provide a self-installation program. At the same time, an uninstall item will be written in the registry during the installation process. The current software management program can detect this item. Which software has been installed on the computer and can notify the user of the installed software. If the user needs to uninstall a certain software, the software management program can call the corresponding uninstaller to uninstall the software. Also, most software is usually installed when the user actively executes the software installation program.

However, some software does not provide an uninstaller for some purpose or its own irregularity, nor does it write an uninstall item to the registry, or the existing software management is caused by the uninstall item in the registry being deleted. If the program does not detect the uninstall item, it will not check the software that has actually been installed. This causes the user to have no knowledge of some software that actually exists, and the software occupies a large amount of installation space when the user does not understand its existence, or runs its own functions, occupies computing resources and Features may adversely affect user equipment.

It can be seen that the installed software is checked only based on the uninstallation item in the registry, and it is easy to miss some software that lacks the uninstall item in the registry but is actually installed, which causes the user to not understand these. The existence of the software and the inability to uninstall these software in a timely manner.

In addition, because some software is for some purpose or its own non-standard, its installation process is usually bundled installation - that is, the installation program of these software will trigger and execute the installation during the execution of other software installation programs, which is easy This type of software causes the installation of these software without the user's attention or complete ignorance. Many current rogue softwares are installed on the user's device through bundled installation. They usually run without the user's permission, occupy a lot of space and resources, and their functions often have adverse effects on the user equipment.

However, the current software management program can not distinguish the software in the user equipment, and can not identify which software is bundled, so it is difficult for the user to choose to uninstall the bundled software, but it will be interfered by these software.

Summary of the invention

In view of the above problems, the present invention has been made in order to provide a software cleaning method and software cleaning system that overcomes the above problems or at least partially solves or alleviates the above problems.

According to an aspect of the present invention, a software cleaning method is provided, comprising: identifying installed software according to pre-recorded software installation information; obtaining a cleaning request for installed software, the cleaning request including description information of the installed software According to the description information of the installed software, the description information of the related file of the installed software is searched in the preset software information base; and the related file is deleted according to the description information of the related file.

The present invention also provides a software cleaning system, comprising: an installed software identification module, configured to identify installed software according to pre-recorded software installation information; and a cleanup request acquisition module for obtaining cleanup of installed software The request, the cleanup request includes description information of the installed software, and the related file search module is configured to search for a description information of the related file of the installed software in the preset software information base according to the description information of the installed software; , used to delete related files according to the description information of related files.

According to another aspect of the present invention, a software cleaning method is further provided, comprising: identifying a bundled software bundled according to pre-recorded software behavior information, wherein the software behavior information is used to record behaviors of multiple software; The cleaning request of the bundled software includes the description information of the bundled software; according to the description information of the bundled software, the description information of the related file of the bundled software is searched in the preset software information base; and the related information is deleted according to the description information of the related file. file.

The present invention further provides a software cleaning system, comprising: a bundled software identification module, configured to identify bundled software bundled software according to pre-recorded software behavior information, wherein the software behavior information is used to record behaviors of multiple softwares; The cleanup request acquisition module is configured to obtain a cleanup request for the bundled software, where the cleanup request includes description information of the bundled software, and the related file search module is configured to search for the bundled software in the preset software information base according to the description information of the bundled software. The description information of the related file; the related file deletion module deletes the related file according to the description information of the related file.

According to still another aspect of the present invention, a computer program is provided comprising computer readable code that, when executed on a computing device, causes the computing device to perform a software cleanup method according to the above.

According to still another aspect of the present invention, a computer readable medium storing a computer program as described above is provided.

The beneficial effects of the invention are:

According to the software cleaning method and system of the present invention, based on the reverse checking of the software installation information, it is possible to distinguish which software has been installed on the user equipment, and notify the user of the installed software, and the user selects whether or not the user has Install the software to clean up, after the user confirms that the installed software needs to be cleaned up, The software is cleaned based on pre-recorded software file information in the software information base.

According to the software cleaning method and system of the present invention, based on the reverse checking of the behavior information of the software, it is possible to distinguish which bundled software, and the bundled software can be notified to the user, and the user selects whether to clean the bundled software according to his or her will. After the user confirms that the bundled software needs to be cleaned, the software can be cleaned based on the pre-recorded software file information in the software repository.

The above description is only an overview of the technical solutions of the present invention, and the above-described and other objects, features and advantages of the present invention can be more clearly understood. Specific embodiments of the invention are set forth below.

DRAWINGS

Various other advantages and benefits will become apparent to those skilled in the art from a The drawings are only for the purpose of illustrating the preferred embodiments and are not to be construed as limiting. Throughout the drawings, the same reference numerals are used to refer to the same parts. In the drawing:

1 shows a flow chart of a software cleanup method in accordance with one embodiment of the present invention;

2 shows a flow chart of a software cleanup method in accordance with one embodiment of the present invention;

3 shows a flow chart of a software cleanup method in accordance with one embodiment of the present invention;

4 shows a flow chart of a software cleanup method in accordance with one embodiment of the present invention;

FIG. 5 shows a flow chart of a software cleaning method according to an embodiment of the present invention;

6 shows a flow chart of a software cleanup method in accordance with one embodiment of the present invention;

Figure 7 shows a block diagram of a software cleaning system in accordance with one embodiment of the present invention;

Figure 8 shows a block diagram of a software cleaning system in accordance with one embodiment of the present invention;

Figure 9 shows a block diagram of a software cleaning system in accordance with one embodiment of the present invention;

Figure 10 shows a block diagram of a software cleaning system in accordance with one embodiment of the present invention;

Figure 11 shows a block diagram of a software cleaning system in accordance with one embodiment of the present invention;

Figure 12 shows a block diagram of a software cleaning system in accordance with one embodiment of the present invention;

Figure 13 shows a block diagram of a software cleaning system in accordance with one embodiment of the present invention;

Figure 14 shows a block diagram of a software cleaning system in accordance with one embodiment of the present invention;

Figure 15 shows a flow chart of a software cleanup method in accordance with one embodiment of the present invention;

16 shows a flow chart of a software cleanup method in accordance with one embodiment of the present invention;

Figure 17 shows a flow chart of a software cleanup method in accordance with one embodiment of the present invention;

Figure 18 is a flow chart showing a software cleaning method in accordance with one embodiment of the present invention;

19 shows a flow chart of a software cleanup method in accordance with one embodiment of the present invention;

20 shows a flow chart of a software cleanup method in accordance with one embodiment of the present invention;

21 shows a flow chart of a software cleanup method in accordance with one embodiment of the present invention;

Figure 22 shows a block diagram of a software cleaning system in accordance with one embodiment of the present invention;

23 shows a block diagram of a software cleaning system in accordance with one embodiment of the present invention;

Figure 24 shows a block diagram of a software cleaning system in accordance with one embodiment of the present invention;

Figure 25 is a block diagram of a software cleaning system in accordance with one embodiment of the present invention;

Figure 26 shows a block diagram of a software cleaning system in accordance with one embodiment of the present invention;

Figure 27 shows a block diagram of a software cleaning system in accordance with one embodiment of the present invention;

28 shows a block diagram of a software cleaning system in accordance with one embodiment of the present invention;

29 shows a block diagram of a software cleaning system in accordance with one embodiment of the present invention;

Figure 30 shows a block diagram of a software cleanup system in accordance with one embodiment of the present invention.

Figure 31 is a schematic block diagram showing a computing device for performing a software cleaning method in accordance with the present invention;

Fig. 32 schematically shows a storage unit for holding or carrying program code implementing the software cleaning method according to the present invention.

detailed description

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While the embodiments of the present invention have been shown in the drawings, the embodiments Rather, these embodiments are provided so that this disclosure will be more fully understood and the scope of the disclosure will be fully disclosed.

The computer system/server can be described in the general context of computer system executable instructions (such as program modules) being executed by a computer system. Generally, program modules may include routines, programs, target programs, components, logic, data structures, and the like that perform particular tasks or implement particular abstract data types. The computer system/server can be implemented in a distributed cloud computing environment where tasks are performed by remote processing devices that are linked through a communication network. In a distributed cloud computing environment, program modules may be located on a local or remote computing system storage medium including storage devices.

As shown in FIG. 1 , an embodiment of the present invention provides a software cleaning method, including: Step 110: Identifying installed software according to pre-recorded software installation information, since installed software often remains after installation The following unique features can be judged whether the installed software is correct by verifying whether the features are correct; in step 120, a cleanup request for the installed software is obtained, and the cleanup request includes a description of the installed software. Information, in this embodiment, the installed software can be prompted to the user through an interface, and the user can select the software to be deleted according to his or her own desire; in step 130, according to the description information of the installed software, in the preset software information base. Search for the description of the related files of the installed software. The related files in this embodiment include the installation files, registry files, shortcuts, service files, generated files, etc. of the installed software. The related files may be installed software. And all the files generated in the working process; in step 140, the related files are deleted according to the description information of the related files. In this embodiment, the user is allowed to select which software in the installed software to be deleted, for example, the installed software may be All the files except the generated file are deleted. Based on the technical solution of the embodiment, the installed software is identified and notified to the user by means of a reverse check, and the software can be cleaned based on the user's will.

As shown in FIG. 2, another embodiment of the present invention provides a software cleaning method. Compared with the foregoing embodiment, the software cleaning method of the embodiment includes software description information, and the step 110 includes: 111. Search for a shortcut according to the description information of the shortcut. Step 112: Extract the path information from the target field in the attribute information of the shortcut. For example, the path information may be specifically “C:\Program Files\A\a. In the form of exe"; in step 113, it is checked whether the file or directory corresponding to the path information exists, for example, according to "C:\Program Files\A\a.exe", check whether a.exe exists; step 114, if the path information corresponds If the file or directory exists, the software corresponding to the shortcut is recognized as the installed software. Since the executable file or the key directory of the software is often recorded in the shortcut, if the executable file or the key directory exists in the user device, The software has been installed, and the technical solution of the embodiment can accurately identify the installed software. Further, if the path information in the shortcut corresponds to the directory, it is also checked whether the directory is not empty. If the non-empty judgment is that the corresponding software is installed, it is possible that the software has been uninstalled, but an empty folder is left. The program can avoid misjudgment.

As shown in FIG. 3, another embodiment of the present invention provides a software cleaning method. Compared with the foregoing embodiment, the software cleaning method of the embodiment includes software description information of a key value item in a registry. The path information is recorded in the key value item. For example, the path information may be in the form of “C:\Program Files\A”, and the step 110 includes: Step 115: searching for the key value item according to the description information of the key value item; Step 116 Extracting the path information from the value of the key value item; step 117, checking whether the file or directory corresponding to the path information exists, for example, checking whether the directory A exists according to "C:\Program Files\A"; step 118, such as path information If the corresponding file or directory exists, the software corresponding to the key value item is recognized as the installed software. Since the important files or important directories of the software are often recorded in the registry, the path information based on the registry key item is checked. If the important file or the important directory of the software is located in the user equipment, the software is installed, and the technical solution of the embodiment can accurately identify the installed software. Further, if the path information in the key value item corresponds to the directory, it is also checked whether the directory is not empty, and if the non-empty judgment corresponding software is installed, this is because it is possible The software has been uninstalled, but an empty folder has been left, which avoids misjudgment.

As shown in FIG. 4, another embodiment of the present invention provides a software cleaning method. Compared with the foregoing embodiment, the software cleaning method of the embodiment has multiple software installation information, and multiple software installation information has different information. The high and low priority, step 110 includes: Step 119, selecting a plurality of software installation information according to the priority level selection, for example, the description information of the shortcut mentioned in the foregoing embodiment, and the registry key value item may be included at the same time. Installation information; Step 1110: Perform identification of the installed software according to the selected software installation information, and comprehensively utilize various installation information by using the technical solution of the embodiment to comprehensively identify the installed software, and the priority exists. It ensures that different installation information can be searched regularly.

As shown in FIG. 5, another embodiment of the present invention provides a software cleaning method. Compared with the foregoing embodiment, the software cleaning method of the embodiment further includes: step 150, obtaining the installed software. The frequency of use, for example, may be the usage of the user in the past week or the month; in step 160, the cleaning recommendation is generated according to the frequency of use. For example, if the user frequently uses it, indicating that the user has a demand for the software, it is not recommended to clean up if If the user does not need to install the software, it means that the software has no value, so it is recommended to clean up.

Another embodiment of the present invention provides a software cleaning method. Compared with the foregoing embodiment, the software cleaning method of the embodiment, if the usage frequency is greater than a predetermined first threshold, the cleaning recommendation is recommended reservation, such as the frequency of use. If the usage is less than the predetermined second threshold, the cleaning recommendation is recommended cleaning. If the usage frequency is between the first threshold and the second threshold, the cleaning recommendation is that the cleaning is performed, and the first threshold is higher than the second threshold. In the technical solution, the installed software is divided into several major categories based on the frequency of use, and corresponding cleaning suggestions are given for each category for reference by the user. For example, the first threshold may be used once a week, and the second threshold is It can be used once a month. Specifically, you can provide a check box for software for different cleaning suggestions on a software interface, for users to check which software needs to be cleaned, and the check box corresponding to the recommended software is checked by default.

Another embodiment of the present invention provides a software cleaning method. Compared with the foregoing embodiment, the software cleaning method, the software installation information, and/or the software information database of the embodiment are located in a cloud server, and the method further includes: obtaining from a cloud server. The software installation information and/or the software information base, the software installation information does not need to occupy the space of the user equipment. In addition, the cloud server side can provide the collected white list of the installed software through installation presets or regular or irregular upgrade methods. Each user equipment, so that the user equipment can query whether the software is installed software according to the white list.

Another embodiment of the present invention provides a software cleaning method. Compared with the foregoing embodiment, the software cleaning method of the embodiment records the description information of the plurality of related files of the installed software in the software information database, and the step 140 further includes: And generating the cleaning progress information according to the number of the plurality of related files and the number of the deleted files of the plurality of related files, to prompt the cleaning progress of the installed software, in the technical solution of the embodiment, the user may be notified The progress of the software cleanup, the specific form of the cleanup progress can be passed through the progress bar, or the percentage The form of the presentation is for the user.

Another embodiment of the present invention provides a software cleaning method. Compared with the foregoing embodiment, the software cleaning method of the embodiment further includes: according to the file currently being deleted, indicating that the current progress is being performed by clearing the progress information. In the technical solution of the embodiment, the currently deleted file is also prompted, and the name, path, and the like of the file may be presented to the user.

As shown in FIG. 6 , another embodiment of the present invention provides a software cleaning method. Compared with the foregoing embodiment, the software cleaning method of the embodiment further includes: Step 170: Obtain a recovery request for the installed software. In the technical solution of the embodiment, the cleaned software is recorded, and the information of the deleted software is displayed to the user through a software interface; in step 180, the action of deleting the installed file is performed in reverse to cancel the In the technical solution of the embodiment, the user is allowed to recover the deleted software in time.

As shown in FIG. 7, an embodiment of the present invention provides a software cleaning system, including: an installed software identification module 210, configured to identify installed software according to pre-recorded software installation information, since installed The software often leaves some unique features after installation, and can be judged whether the installed software is correct by verifying whether the features are correct; the cleanup request obtaining module 220 is configured to obtain a cleanup request for the installed software, and the cleanup request includes The description information of the installed software, the embodiment may prompt the user to install the software through an interface, the user may choose to select the software to be deleted according to his or her own desire; the related file searching module 230 is configured according to the description of the installed software. The information is used to search for the description information of the related files of the installed software in the preset software information database. The related files in this embodiment include installation files, registry files, shortcut files, service files, generated files, etc. of the installed software. Etc., related files can be all the files generated during the installation and work of the installed software. The related file deletion module 240 is configured to delete related files according to the description information of the related file. In this embodiment, the user is allowed to select which software in the installed software to delete, for example, the generated software may be generated. All the files outside the file are deleted. Based on the technical solution of the embodiment, the installed software is identified and notified to the user by means of a reverse check, and the software can be cleaned based on the user's will.

As shown in FIG. 8 , another embodiment of the present invention provides a software cleaning system. Compared with the foregoing embodiment, the software cleaning system of the embodiment includes software description information, and the system includes: The mode finding module 250 is configured to search for a shortcut according to the description information of the shortcut. The first path extraction module 260 is configured to extract the path information from the target field in the attribute information of the shortcut. For example, the path information may be specifically The form of "C:\Program Files\A\a.exe"; the first path checking module 270 is configured to check whether a file or a directory corresponding to the path information exists, for example, according to "C:\Program Files\A\a. Exe", check whether a.exe exists; if the file or directory corresponding to the path information exists, the installed software identification module 210 identifies the software corresponding to the shortcut as the installed software, due to the shortcut The executable file or the key directory of the software is often recorded. If the executable file or the key directory exists in the user equipment, the software is installed, and the technical solution of the embodiment can accurately identify the installed software. Further, if the path information in the shortcut corresponds to the directory, it is also checked whether the directory is not empty. If the non-empty judgment is that the corresponding software is installed, it is possible that the software has been uninstalled, but an empty folder is left. The program can avoid misjudgment.

As shown in FIG. 9 , another embodiment of the present invention provides a software cleaning system. Compared with the foregoing embodiment, the software cleaning system of the embodiment includes software description information of a key value item in the registry. The path information is recorded in the key value item. For example, the path information may be in the form of “C:\Program Files\A”, and the system further includes: a key value item searching module 280, configured to search according to the description information of the key value item. a key value item; a second path extraction module 290, configured to extract path information from the value of the key value item; the second path checking module 2100 is configured to check whether a file or a directory corresponding to the path information exists, for example, according to "C: \Program Files\A" checks whether the directory A exists; if the file or directory corresponding to the path information exists, the installed software identification module 210 identifies the software corresponding to the key value item as the installed software, because the important file or important directory of the software It is often recorded in the registry, so it is checked based on the path information of the registry key item. If the important file or important directory of the software is located in the user device, then Software has been installed, the technical solutions of the present embodiment can accurately identify the installed software. Further, if the path information in the key value item corresponds to the directory, it is also checked whether the directory is not empty. If the non-empty judgment is that the corresponding software is installed, it is possible that the software has been uninstalled, but an empty folder is left. This program can avoid misjudgment. .

As shown in FIG. 10, another embodiment of the present invention provides a software cleaning system. Compared with the foregoing embodiment, the software cleaning system of the embodiment has multiple software installation information, and various software installation information have different information. The system further includes: an installation information selection module 2110, configured to sequentially select a plurality of software installation information according to the priority level selection, for example, the description information and the registration of the shortcut mentioned in the foregoing embodiment may be included at the same time. The installation information of the table key value item; the installed software identification module 210 performs the identification of the installed software according to the selected software installation information, and comprehensively utilizes various installation information through the technical solution of the embodiment to comprehensively identify The installed software, the existence of priority, ensures that different installation information can be searched regularly.

As shown in FIG. 11, another embodiment of the present invention provides a software cleaning system. Compared with the foregoing embodiment, the software cleaning system of the embodiment further includes: a usage frequency obtaining module 2120, configured to acquire installed software. The frequency of use, for example, may be the usage of the user in the past week or the month; the cleaning suggestion generating module 2130 is configured to generate a cleaning suggestion according to the frequency of use, for example, if the user frequently uses the user to have the demand for the software, It is not recommended to clean up. If the user basically does not need to install the software, it means that the software has no value, so it is recommended to clean up.

Another embodiment of the present invention provides a software cleaning system. Compared with the foregoing embodiment, the software cleaning system of the embodiment, if the usage frequency is greater than a predetermined first threshold, the cleaning recommendation is recommended, such as the frequency of use. If the usage is less than the predetermined second threshold, the cleaning recommendation is recommended cleaning. If the usage frequency is between the first threshold and the second threshold, the cleaning recommendation is that the cleaning is performed, and the first threshold is higher than the second threshold. In the technical solution, the installed software is divided into several major categories based on the frequency of use, and corresponding cleaning suggestions are given for each category for reference by the user. For example, the first threshold may be used once a week, and the second threshold is It can be used once a month. Specifically, you can provide a check box for software for different cleaning suggestions on a software interface, for users to check which software needs to be cleaned, and the check box corresponding to the recommended software is checked by default.

As shown in FIG. 12, another embodiment of the present invention provides a software cleaning system. Compared with the foregoing embodiment, the software cleaning system, the software installation information, and/or the software information database of the embodiment are located in a cloud server, and the system further The cloud data obtaining module 2140 is configured to obtain software installation information and/or a software information library from the cloud server, where the software installation information does not need to occupy the space of the user equipment, and the cloud server may collect the installed software white. The list is provided to each user device by installing presets or periodically or irregularly, so that the user device can query whether the software is installed software according to the white list.

As shown in FIG. 13 , another embodiment of the present invention provides a software cleaning system. Compared with the foregoing embodiment, the software cleaning system of the embodiment records a description of multiple related files of the installed software in the software information database. The information system further includes: a cleaning progress prompting module 2150, configured to generate cleaning progress information according to the number of the plurality of related files and the number of deleted files of the plurality of related files, to prompt the cleaning progress of the installed software, In the technical solution of the embodiment, the cleaning progress of the software of the user may be notified, and the specific form of the cleaning progress may be presented to the user by a progress bar or a percentage.

Another embodiment of the present invention provides a software cleaning system. Compared with the foregoing embodiment, the software cleaning system of the embodiment, the cleaning progress prompting module 2150, according to the file currently being deleted, shows that the progress is currently being performed by the cleaning progress information. In the technical solution of the embodiment, the currently deleted file is also prompted, and the name, path, and the like of the file may be presented to the user.

As shown in FIG. 14, another embodiment of the present invention provides a software cleaning system. Compared with the foregoing embodiment, the software cleaning system of the embodiment further includes: a recovery request obtaining module 2160, configured to acquire the installed The recovery request of the software; the related file recovery module 2170 is configured to perform the action of deleting the installed file in reverse to cancel the cleaning of the installed software. In the technical solution of the embodiment, the currently deleted file is also prompted. Specifically, the name, path, and the like of the file may be presented to the user.

The embodiment of the present invention further provides another software cleaning method and system. Another software cleaning method and system provided by the embodiments of the present invention are introduced.

As shown in FIG. 15, an embodiment of the present invention provides a software cleaning method, including: a step 310. Identify the bundled software bundled software according to the pre-recorded software behavior information. The software behavior information is used to record the behavior of multiple softwares. Since the behavior of the bundled software often has some unique features, based on whether the bundled software can be used for binding The determination of the software is as follows: Step 320: Obtain a cleanup request for the bundled software, and the cleanup request includes the description information of the bundled software. In this embodiment, the bundled software may be prompted to the user through an interface, and the user may choose to delete according to his own wishes. Software: Step 330: Searching, according to the description information of the bundle software, the description information of the related file of the bundle software in the preset software information database, where the related files in the embodiment include the installation file of the bundle software, the registry file, and the shortcut manner. The service file, the generated file, and the like, the related file may be all the files generated during the installation and working process of the bundle software; in step 340, the related file is deleted according to the description information of the related file, and the user is allowed to select the bundle in this embodiment. Which software of the software is deleted, for example, Bundle all files except the file is deleted to generate, based on the technical solution of the present embodiment, and notifies the user by way of pegging bundle identified, and based on the user's wishes to clean software.

As shown in FIG. 16, another embodiment of the present invention provides a software cleaning method. Compared with the foregoing embodiment, the software cleaning method of the embodiment includes software logs, process logs, and process logs for recording multiple software processes. The parent-child relationship data includes the description information of the child process and the description information of the parent process, and the step 310 includes: Step 311: acquiring description information of the child process from the process log; Step 312, according to the description of the child process The information identifies the software corresponding to the child process as bundled software. This is because the bundle software is rarely started by the user, and more is started when the bundled software starts. This feature is reflected in the software process is two software. There is a parent-child relationship between the processes, and the process of the bundled software is a child process, and the process of the bundled software is a parent process. In this embodiment, the parent-child relationship between processes can be used to effectively identify which processes correspond to the software. software.

As shown in FIG. 17, another embodiment of the present invention provides a software cleaning method. Compared with the foregoing embodiment, in the software cleaning method of the embodiment, the parent-child relationship data includes a child process flag indicating the description information of the child process. And the parent process flag indicating the description information of the parent process, step 311 includes: Step 3111, searching for the child process tag from the process log, the child process tag may be a field, such as abc; Step 3112, searching for the child according to the child process tag The description information of the process, for example, the description information of the child process pointed to by the aforementioned field abc.

Another embodiment of the present invention provides a software cleaning method. Compared with the foregoing embodiment, the software cleaning method of the embodiment includes software monitoring information, and the monitoring log is based on monitoring the installation process of multiple softwares. The monitoring log includes the description information of the bundled software and the binding label indicating the description information of the bundled software. That is to say, the known bundled software is directly recorded in the monitoring log, and it is very simple to check the bundled software according to the record of the monitoring log.

As shown in FIG. 18, another embodiment of the present invention provides a software cleaning method. Compared with the foregoing embodiment, the software cleaning method of the embodiment includes software information including a bundled feature library, and the bundled feature library is used for record binding. Features, bundled software currently has a variety of, the more common one is direct bundling, the second is possible by applying an address on the Internet, the address describes which software will be bundled, download the description link, you can automatically run the installation, this embodiment The technical solution is directed to the first type, and can directly capture the feature information of the bundle and record the bundled feature database. For the second type, the bundled logic can be analyzed by the packet capture tool, for example, which addresses are accessed, and which packages are bundled. Then collect these addresses and record them, and download the latest link from the address to get the latest bundle content, and then analyze the characteristics of the bundle and record it. The specific features can be the resource information and signature of the bundle. Information, executable file attributes, and command line information, etc., step 310 includes: step 313, capture Creating an event of a new process, and acquiring related information of the new process; step 314, comparing related information of the new process with the binding feature in the bundled feature database; and step 315, if the related information of the new process is consistent with the bundled feature, The software corresponding to the new process is identified as a bundled software.

As shown in FIG. 19, another embodiment of the present invention provides a software cleaning method. Compared with the foregoing embodiment, the software cleaning method of the embodiment further includes, after step 320, step 316, according to the pre-recorded The software behavior information identifies the bundled software corresponding to the bundle software. For example, in combination with the foregoing embodiments, the software corresponding to the parent process may be identified as bundled software according to the parent-child process relationship, for example, the bundled software is recorded in the monitoring log, The reverse check may be performed based on the content of the monitoring log; in step 317, the prompt information is generated to prompt the binding relationship between the bundled software and the bundled software, and the bundled software and the corresponding bundled software information may be simultaneously displayed through a software interface. For reference. The order of step 316 and step 317 can be reversed.

As shown in FIG. 20, another embodiment of the present invention provides a software cleaning method. Compared with the foregoing embodiment, the software cleaning method of the embodiment further includes: step 318, obtaining the use of the bundle software. The frequency, for example, may be the usage of the user in the past week or the month; in step 319, the cleaning recommendation is generated according to the frequency of use. For example, if the user frequently uses the user, the user is in need of the software, and the cleaning is not recommended. If you do not need to bundle the software, it means that the software has no value, so it is recommended to clean it up.

Another embodiment of the present invention provides a software cleaning method. Compared with the foregoing embodiment, the software cleaning method of the embodiment, if the usage frequency is greater than a predetermined first threshold, the cleaning recommendation is recommended reservation, such as the frequency of use. If the usage is less than the predetermined second threshold, the cleaning recommendation is recommended cleaning. If the usage frequency is between the first threshold and the second threshold, the cleaning recommendation is that the cleaning is performed, and the first threshold is higher than the second threshold. In the technical solution, the bundled software is divided into several major categories based on the frequency of use, and corresponding cleaning suggestions are given for each category for reference by the user. For example, the first threshold may be used once a week, and the second threshold is each Used once a month, specifically, a check box can be provided for software for different cleaning suggestions on a software interface for use. The software selected by the user needs to be cleaned up, and the check box corresponding to the recommended software is checked by default.

Another embodiment of the present invention provides a software cleaning method. Compared with the foregoing embodiment, the software cleaning method, the software behavior information, and/or the software information database of the embodiment are located in a cloud server, and the method further includes: obtaining from a cloud server. The software behavior information and/or the software information base, the software behavior information and/or the software information base does not need to occupy the space of the user equipment. In addition, the cloud server side may whitelist the collected bundle software by installing presets or periodically, not The periodic upgrade mode is provided to each user device, so that the user device can query whether the software is a bundled software according to the bundle whitelist.

Another embodiment of the present invention provides a software cleaning method. Compared with the foregoing embodiment, the software cleaning method of the embodiment, the software information database records the description information of the plurality of related files of the bundle software, and the step 340 further includes: According to the number of the plurality of related files, and the number of the deleted files of the plurality of related files, the cleaning progress information is generated to prompt the cleaning progress of the bundled software. In the technical solution of the embodiment, the software of the user may be notified. The progress of the cleanup process, the specific form of the cleanup progress can be presented to the user through a progress bar or a percentage.

Another embodiment of the present invention provides a software cleaning method. Compared with the foregoing embodiment, the software cleaning method of the embodiment further includes: according to the file currently being deleted, the current progress is indicated by the cleaning progress information. In the technical solution of the embodiment, the currently deleted file is also prompted, and the name, path, and the like of the file may be presented to the user.

As shown in FIG. 21, another embodiment of the present invention provides a software cleaning method. Compared with the foregoing embodiment, the software cleaning method of the embodiment further includes: Step 350: Acquire a recovery request for the bundle software, In the technical solution of the embodiment, the cleaned software is recorded, and the information of the deleted software is displayed to the user through a software interface; in step 360, the action of deleting the related file is performed in reverse to cancel the binding of the software. In the technical solution of the embodiment, the user is allowed to recover the deleted software in time.

As shown in FIG. 22, another embodiment of the present invention further provides a software cleaning system, including: a bundle software identification module 410, configured to identify bundled software bundled software according to pre-recorded software behavior information, and software behavior. The information is used to record the behavior of multiple softwares. Since the behavior of the bundled software often has some unique features, based on this, it can be judged whether it is a bundled software; the cleanup request acquisition module 420 is configured to obtain a cleanup request for the bundled software. The cleaning request includes the description information of the bundled software. In this embodiment, the bundled software can be prompted to the user through an interface, and the user can select the software to be deleted according to the will of the user; the related file searching module 430 is configured to be used according to the bundled software. The description information is used to search for the description information of the related files of the bundle software in the preset software information database. The related files in this embodiment include the installation files of the bundled software, the registry file, the shortcut file, the service file, the generated file, and the like. The related file can be the installation of the bundled software and the work process. Documents; documents deleting module 440, according to the description information file, The related files are deleted in the embodiment, and the user is allowed to select which software of the bundle software to delete. For example, all the files except the generated file of the bundled software can be deleted, and the technical solution according to the embodiment is used for the reverse check. The way to identify the bundled software and notify the user, and can clean the software based on the user's wishes.

As shown in FIG. 23, another embodiment of the present invention provides a software cleaning system. Compared with the foregoing embodiment, the software cleaning system of the embodiment includes software logs, process logs, and process logs for recording multiple software processes. The parent-child relationship data includes the description information of the child process and the description information of the parent process, and the system further includes: a child process identification module 450, configured to obtain the description information of the child process from the process log; The module 410 identifies the software corresponding to the child process as bundled software according to the description information of the child process, because the bundled software is rarely initiated by the user, and more is started when the bundled software starts. This feature is reflected in In the software process, there is a parent-child relationship between the processes of the two softwares, and the process of the bundled software is a child process, and the process of the bundled software is a parent process. In this embodiment, the parent-child relationship between processes can be effectively recognized. Which software corresponds to which software is bundled.

As shown in FIG. 24, another embodiment of the present invention provides a software cleaning system. Compared with the foregoing embodiment, in the software cleaning system of this embodiment, the parent-child relationship data includes a child process flag indicating the description information of the child process. And a parent process tag that points to the description information of the parent process, the system further includes: a child process tag lookup module 460, configured to find the child process tag from the process log, the child process tag can be a field, such as abc; the child process identification module 450 searches for the description information of the sub-process according to the sub-process tag, for example, searches for the description information of the sub-process pointed to by the aforementioned field abc.

Another embodiment of the present invention provides a software cleaning system. Compared with the foregoing embodiment, the software cleaning system of the embodiment includes software monitoring information, and the monitoring log is based on monitoring the installation process of multiple softwares. The monitoring log includes the description information of the bundled software and the binding label indicating the description information of the bundled software. That is to say, the known bundled software is directly recorded in the monitoring log, and it is very simple to check the bundled software according to the record of the monitoring log.

As shown in FIG. 25, another embodiment of the present invention provides a software cleaning system. Compared with the foregoing embodiment, the software cleaning information of the embodiment includes a bundled feature library, and the bundled feature library is used for record binding. Features, bundled software currently has a variety of, the more common one is direct bundling, the second is possible by applying an address on the Internet, the address describes which software will be bundled, download the description link, you can automatically run the installation, this embodiment The technical solution is directed to the first type, and can directly capture the feature information of the bundle and record the bundled feature database. For the second type, the bundled logic can be analyzed by the packet capture tool, for example, which addresses are accessed, and which packages are bundled. Then collect these addresses and record them, and download the latest link from the address to get the latest bundle content, and then analyze the characteristics of the bundle and record it. The specific features can be the resource information and signature of the bundle. Information, executable file attributes, and command line information, etc., system The method further includes: a process capture module 470, configured to capture an event of creating a new process, and acquire related information of the new process; and a feature comparison module 480, configured to compare related information of the new process with the bundled feature in the bundled feature library; The related information of the new process is consistent with the bundling feature, and the bundle identification module 410 identifies the software corresponding to the new process as the bundled software.

As shown in FIG. 26, another embodiment of the present invention provides a software cleaning system. Compared with the foregoing embodiment, the software cleaning system of the embodiment further includes: a bundled software identification module 490, configured to perform pre-recording according to the pre-recording. The software behavior information identifies the bundled software corresponding to the bundle software. For example, in combination with the foregoing embodiments, the software corresponding to the parent process can be identified as bundled software according to the parent-child process relationship, for example, the bundled software is recorded in the monitoring log. The back-up relationship prompting module 4100 is configured to generate the prompt information, and prompt the binding relationship between the bundled software and the bundled software. Specifically, the bundled software and the corresponding bundle can be simultaneously displayed through a software interface. Information about the bundled software for reference.

As shown in FIG. 27, another embodiment of the present invention provides a software cleaning system. Compared with the foregoing embodiment, the software cleaning system of the embodiment further includes: a frequency acquisition module 4110, configured to acquire bundle software. The frequency of use, for example, may be the usage of the user in the last week or the month; the cleaning suggestion generating module 4120 is configured to generate a cleaning suggestion according to the frequency of use, for example, if the user frequently uses the user to have the demand for the software, then It is recommended to clean up. If the user does not need to bundle the software, it means that the software has no value, so it is recommended to clean up.

Another embodiment of the present invention provides a software cleaning system. Compared with the foregoing embodiment, the software cleaning system of the embodiment, if the usage frequency is greater than a predetermined first threshold, the cleaning recommendation is recommended, such as the frequency of use. If the usage is less than the predetermined second threshold, the cleaning recommendation is recommended cleaning. If the usage frequency is between the first threshold and the second threshold, the cleaning recommendation is that the cleaning is performed, and the first threshold is higher than the second threshold. In the technical solution, the bundled software is divided into several major categories based on the frequency of use, and corresponding cleaning suggestions are given for each category for reference by the user. For example, the first threshold may be used once a week, and the second threshold is each Use once a month. Specifically, you can provide a check box for software for different cleaning suggestions on a software interface, for users to check which software needs to be cleaned, and the check box corresponding to the recommended software is checked by default.

As shown in FIG. 28, another embodiment of the present invention provides a software cleaning system. Compared with the foregoing embodiment, the software cleaning system, the software behavior information, and/or the software information library of the embodiment are located in a cloud server, and the system further The cloud data obtaining module 4130 is configured to obtain software behavior information and/or a software information library from the cloud server, where the software behavior information and/or the software information library does not need to occupy the space of the user equipment, and the cloud server side may collect The bundled software whitelist is provided to each user device by installing presets or periodically or irregularly upgraded, so that the user equipment can query whether the software is bundled according to the bundle whitelist.

As shown in FIG. 29, another embodiment of the present invention provides a software cleaning system, which is compared with the above embodiment. The software cleaning system of the embodiment, the software information database records the description information of the plurality of related files of the bundle software, and further includes: a cleaning progress prompting module 4140, configured to use the number of the plurality of related files, and the plurality of related files. The number of deleted files is generated, and the cleaning progress information is generated to prompt the cleaning process of the bundled software. In the technical solution of the embodiment, the cleaning progress of the software can be notified to the user, and the specific form of the cleaning progress can be passed through the progress bar, or The form of the percentage is presented to the user.

Another embodiment of the present invention provides a software cleaning system. Compared with the foregoing embodiment, the software cleaning system of the embodiment, the cleaning progress prompting module 4140, according to the file currently being deleted, shows that the current progress is being performed by clearing the progress information. In the technical solution of the embodiment, the currently deleted file is also prompted, and specifically, the name, path, and the like of the file are presented to the user.

As shown in FIG. 30, another embodiment of the present invention provides a software cleaning system. Compared with the foregoing embodiment, the software cleaning system of the embodiment further includes: a recovery request obtaining module 4150, configured to acquire the bundled software. The recovery request, in the technical solution of the embodiment, records the cleaned software, and displays the information of the deleted software to the user through a software interface; the related file recovery module 4160 is configured to perform the deletion related to the reverse The action of the file is to cancel the cleaning of the bundled software. In the technical solution of the embodiment, the user is allowed to recover the deleted software in time.

The algorithms and displays provided herein are not inherently related to any particular computer, virtual system, or other device. Various general purpose systems can also be used with the teaching based on the teachings herein. The structure required to construct such a system is apparent from the above description. Moreover, the invention is not directed to any particular programming language. It is to be understood that the invention may be embodied in a variety of programming language, and the description of the specific language has been described above in order to disclose the preferred embodiments of the invention.

In the description provided herein, numerous specific details are set forth. However, it is understood that the embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures, and techniques are not shown in detail so as not to obscure the understanding of the description.

Similarly, the various features of the invention are sometimes grouped together into a single embodiment, in the above description of the exemplary embodiments of the invention, Figure, or a description of it. However, the method disclosed is not to be interpreted as reflecting the intention that the claimed invention requires more features than those recited in the claims. Rather, as the following claims reflect, inventive aspects reside in less than all features of the single embodiments disclosed herein. Therefore, the claims following the specific embodiments are hereby explicitly incorporated into the embodiments, and each of the claims as a separate embodiment of the invention.

Those skilled in the art will appreciate that the modules in the devices of the embodiments can be adaptively changed and placed in one or more devices different from the embodiment. Can be put in the embodiment Modules or units or components are combined into one module or unit or component, and in addition they can be divided into multiple sub-modules or sub-units or sub-components. In addition to such features and/or at least some of the processes or units being mutually exclusive, any combination of the features disclosed in the specification, including the accompanying claims, the abstract and the drawings, and any methods so disclosed, or All processes or units of the device are combined. Each feature disclosed in this specification (including the accompanying claims, the abstract and the drawings) may be replaced by alternative features that provide the same, equivalent or similar purpose.

In addition, those skilled in the art will appreciate that, although some embodiments described herein include certain features that are included in other embodiments and not in other features, combinations of features of different embodiments are intended to be within the scope of the present invention. Different embodiments are formed and formed. For example, in the following claims, any one of the claimed embodiments can be used in any combination.

The various component embodiments of the present invention may be implemented in hardware, or in a software module running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that a microprocessor or digital signal processor (DSP) may be used in practice to implement some or all of the functionality of some or all of the components of the device in accordance with embodiments of the present invention. The invention can also be implemented as a device or device program (e.g., a computer program and a computer program product) for performing some or all of the methods described herein. Such a program implementing the invention may be stored on a computer readable medium or may be in the form of one or more signals. Such signals may be downloaded from an Internet website, provided on a carrier signal, or provided in any other form.

For example, Figure 31 illustrates a computing device that can implement a software cleanup method in accordance with the present invention. The computing device conventionally includes a processor 5110 and a computer program product or computer readable medium in the form of a memory 5120. The memory 5120 may be an electronic memory such as a flash memory, an EEPROM (Electrically Erasable Programmable Read Only Memory), an EPROM, a hard disk, or a ROM. Memory 5120 has a storage space 5130 for program code 5131 for performing any of the method steps described above. For example, storage space 5130 for program code may include various program code 5131 for implementing various steps in the above methods, respectively. The program code can be read from or written to one or more computer program products. These computer program products include program code carriers such as hard disks, compact disks (CDs), memory cards or floppy disks. Such a computer program product is typically a portable or fixed storage unit as described with reference to FIG. The storage unit may have a storage segment, a storage space, and the like that are similarly arranged to the storage 5120 in the computing device of FIG. The program code can be compressed, for example, in an appropriate form. Typically, the storage unit includes computer readable code 5131', ie, code readable by a processor, such as 5110, that when executed by a computing device causes the computing device to perform each of the methods described above step.

As used herein, "one embodiment", "an embodiment" or "one or more embodiments" means The specific features, structures, or characteristics described in connection with the embodiments are included in at least one embodiment of the invention. In addition, it is noted that the phrase "in one embodiment" is not necessarily referring to the same embodiment.

It is to be noted that the above-described embodiments are illustrative of the invention and are not intended to be limiting, and that the invention may be devised without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as a limitation. The word "comprising" does not exclude the presence of the elements or steps that are not recited in the claims. The word "a" or "an" The invention can be implemented by means of hardware comprising several distinct elements and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means can be embodied by the same hardware item. The use of the words first, second, and third does not indicate any order. These words can be interpreted as names.

In addition, it should be noted that the language used in the specification has been selected for the purpose of readability and teaching, and is not intended to be construed or limited. Therefore, many modifications and changes will be apparent to those skilled in the art without departing from the scope of the invention. The disclosure of the present invention is intended to be illustrative, and not restrictive, and the scope of the invention is defined by the appended claims.

Claims

A software cleaning method comprising:

Identify installed software based on pre-recorded software installation information;

Obtaining a cleanup request for the installed software, the cleanup request including description information of the installed software;

Defining, according to the description information of the installed software, the description information of the related file of the installed software in a preset software information base;

And deleting the related file according to the description information of the related file.
The software cleaning method according to claim 1, wherein the software installation information comprises description information of the shortcut, and the step of identifying the installed software according to the pre-recorded software installation information comprises:

Finding the shortcut according to the description information of the shortcut;

Extracting path information from a target field in the attribute information of the shortcut;

Checking whether a file or directory corresponding to the path information exists;

If the file or directory corresponding to the path information exists, the software corresponding to the shortcut is identified as the installed software.
The software cleaning method according to claim 1, wherein the software installation information includes description information of a key value item in a registry, and path information is recorded in the key value item, and the software installation information according to pre-recording The steps to identify the installed software include:

Finding the key value item according to the description information of the key value item;

Extracting path information from values of the key value items;

Checking whether a file or directory corresponding to the path information exists;

If the file or directory corresponding to the path information exists, the software corresponding to the key item is identified as the installed software.
The software cleaning method according to claim 1, wherein the software installation information is different, and the plurality of software installation information have different priorities, and the pre-recorded software installation information identifies that The steps to install the software include:

Select the plurality of software installation information in turn according to the priority level;

The identification of the installed software is performed based on the selected software installation information.
The software cleaning method according to claim 1, wherein before the step of obtaining the cleaning request for the installed software, the method further comprises:

Obtaining the frequency of use of the installed software;

A cleanup suggestion is generated based on the frequency of use.
The software cleaning method according to claim 5, wherein

If the usage frequency is greater than a predetermined first threshold, the cleaning suggestion is a suggestion reservation, and if the usage frequency is less than a predetermined second threshold, the cleaning suggestion is a suggestion cleanup, if the use frequency is located When the first threshold is between the second threshold and the second threshold, the cleaning suggestion may be cleaned, and the first threshold is higher than the second threshold.
The software cleaning method according to claim 1, wherein the software installation information and/or the software information base are located in a cloud server, the method further comprising:

Obtaining the software installation information and/or the software information library from the cloud server.
The software cleaning method according to claim 1, wherein the software information database records description information of a plurality of related files of the installed software, and the related file is deleted according to the description information of the related file. The steps also include:

According to the number of the plurality of related files and the number of deleted files of the plurality of related files, cleaning progress information is generated to prompt the cleaning progress of the installed software.
The software cleaning method according to claim 8, wherein the step of deleting the related file according to the description information of the related file further comprises:

The description information of the file currently being deleted is shown by the cleaning progress information according to the file currently being deleted.
The software cleaning method according to any one of claims 1 to 9, further comprising:

Obtaining a recovery request for the installed software;

The action of deleting the installed file is reversed to cancel the cleaning of the installed software.
A software cleaning system comprising:

A software identification module is installed for identifying the installed software according to the pre-recorded software installation information;

a cleanup request obtaining module, configured to obtain a cleanup request for the installed software, where the cleanup request includes description information of the installed software;

And a related file searching module, configured to search, in a preset software information base, the description information of the related file of the installed software according to the description information of the installed software;

And a related file deletion module, configured to delete the related file according to the description information of the related file.
The software cleaning system of claim 11, wherein the software installation information comprises description information of a shortcut, the system further comprising:

a shortcut search module, configured to search for the shortcut according to the description information of the shortcut;

a first path extraction module, configured to extract a path from a target field in the attribute information of the shortcut information;

a first path checking module, configured to check whether a file or a directory corresponding to the path information exists;

If the file or directory corresponding to the path information exists, the installed software identification module identifies the software corresponding to the shortcut as the installed software.
The software cleaning system of claim 11, wherein the software installation information comprises description information of a key value item in a registry, the key value item is recorded with path information, and the system further comprises:

a key item search module, configured to search for the key value item according to the description information of the key value item;

a second path extraction module, configured to extract path information from values of the key value items;

a second path checking module, configured to check whether a file or a directory corresponding to the path information exists;

If the file or directory corresponding to the path information exists, the installed software identification module identifies the software corresponding to the key item as the installed software.
The software cleaning system of claim 11, wherein the software installation information is different, and the plurality of software installation information has different levels of priority, the system further comprising:

An installation information selection module, configured to sequentially select the plurality of software installation information according to a priority level;

The installed software identification module performs identification of the installed software according to the selected software installation information.
The software cleaning system of claim 11 further comprising:

Using a frequency acquisition module, configured to acquire a frequency of use of the installed software;

A cleanup suggestion generation module is configured to generate a cleanup suggestion according to the frequency of use.
A software cleaning system according to claim 15, wherein

If the usage frequency is greater than a predetermined first threshold, the cleaning suggestion is a suggestion reservation, and if the usage frequency is less than a predetermined second threshold, the cleaning suggestion is a suggestion cleanup, if the use frequency is located When the first threshold is between the second threshold and the second threshold, the cleaning suggestion may be cleaned, and the first threshold is higher than the second threshold.
The software cleaning system of claim 11, wherein the software installation information and/or the software information base are located in a cloud server, the system further comprising:

The cloud data obtaining module is configured to obtain the software installation information and/or the software information library from the cloud server.
The software cleaning system of claim 11, wherein the software information base records description information of a plurality of related files of the installed software, the system further comprising:

a cleaning progress prompting module, configured to generate cleaning progress information according to the number of the plurality of related files and the number of deleted files of the plurality of related files, to prompt for cleaning up the installed software degree.
The software cleaning system according to claim 18, wherein the cleaning progress prompting module displays the description information of the file currently being deleted by the cleaning progress information according to the file currently being deleted.
The software cleaning system according to any one of claims 11 to 19, further comprising:

a recovery request obtaining module, configured to obtain a recovery request for the installed software;

And a related file recovery module, configured to perform an action of deleting the installed file in reverse to cancel the cleaning of the installed software.
A software cleaning method comprising:

Identifying bundled installed bundles based on pre-recorded software behavior information, the software behavior information being used to record behavior of multiple softwares;

Obtaining a cleanup request for the bundled software, where the cleanup request includes description information of the bundled software;

Defining, according to the description information of the bundle software, description information of a related file of the bundle software in a preset software information base;

And deleting the related file according to the description information of the related file.
The software cleaning method according to claim 21, wherein the software behavior information comprises a process log, the process log records parent-child relationship data between processes of the plurality of software, and the parent-child relationship data includes a child process The description information and the description information of the parent process, and the step of identifying the bundled software bundle according to the pre-recorded software behavior information includes:

Obtaining description information of the sub-process from the process log;

The software corresponding to the sub-process is identified as the bundle-installed software according to the description information of the sub-process.
The software cleaning method according to claim 22, wherein said parent-child relationship data includes a child process flag indicating description information of said child process, and a parent process flag indicating description information of said parent process, said slave The step of obtaining the description information of the sub-process in the process log includes:

Finding the child process tag from the process log;

Finding description information of the child process according to the child process tag.
The software cleaning method according to claim 21, wherein the software behavior information comprises a monitoring log, and the monitoring log is obtained based on monitoring a installation process of the plurality of software, wherein the monitoring log includes the bundled software Descriptive information, and a binding tag pointing to the description information of the bundled software.
The software cleaning method according to claim 21, wherein the software behavior information comprises a bundled feature library, the bundled feature library is configured to record a bundle feature, and the pre-recorded software behavior information is The steps to bundle bundled software include:

Capture events that create new processes, and get information about the new processes;

Comparing related information of the new process with the binding feature in the bundled feature library;

If the related information of the new process matches the binding feature, the software corresponding to the new process is identified as the bundled software.
The software cleaning method according to claim 21, wherein before the step of obtaining the cleaning request for the bundled software, the method further comprises:

Identifying the bundled software corresponding to the bundled software according to the pre-recorded software behavior information;

A prompt message is generated to prompt a binding relationship between the bundled software and the bundled software.
The software cleaning method according to claim 21, wherein before the step of obtaining the cleaning request for the bundled software, the method further comprises:

Obtaining the frequency of use of the bundled software;

A cleanup suggestion is generated based on the frequency of use.
A software cleaning method according to claim 27, wherein

If the usage frequency is greater than a predetermined first threshold, the cleaning suggestion is a suggestion reservation, and if the usage frequency is less than a predetermined second threshold, the cleaning suggestion is a suggestion cleanup, if the use frequency is located When the first threshold is between the second threshold and the second threshold, the cleaning suggestion may be cleaned, and the first threshold is higher than the second threshold.
The software cleaning method according to claim 21, wherein the software behavior information and/or the software information base is located in a cloud server, the method further comprising:

Obtaining the software behavior information and/or software information library from the cloud server.
The software cleaning method according to claim 21, wherein the software information library records description information of a plurality of related files of the bundle software, and the deleting the related files according to the description information of the related files The steps also include:

According to the number of the plurality of related files and the number of deleted files of the plurality of related files, cleaning progress information is generated to prompt the cleaning progress of the bundled software.
The software cleaning method according to claim 30, wherein the step of deleting the related file according to the description information of the related file further comprises:

The description information of the file currently being deleted is shown by the cleaning progress information according to the file currently being deleted.
The software cleaning method according to any one of claims 21 to 31, further comprising:

Obtaining a recovery request for the bundled software;

The action of deleting the related file is reversed to cancel the cleaning of the bundle.
A software cleaning system comprising:

a bundle identification software module, configured to identify bundled software bundles according to pre-recorded software behavior information, where the software behavior information is used to record behaviors of multiple softwares;

a cleanup request obtaining module, configured to obtain a cleanup request for the bundled software, where the cleanup request includes description information of the bundled software;

The related file searching module is configured to search, in the preset software information database, the description information of the related file of the bundled software according to the description information of the bundled software;

The related file deletion module deletes the related file according to the description information of the related file.
The software cleaning system according to claim 33, wherein said software behavior information comprises a process log, said process log records parent-child relationship data between processes of said plurality of software, said parent-child relationship data including child process Descriptive information and description information of the parent process, the system further includes:

a sub-process identification module, configured to obtain, from the process log, description information of the sub-process;

The bundle identification software identifies the software corresponding to the sub-process as the bundle-installed software according to the description information of the sub-process.
The software cleaning system according to claim 34, wherein said parent-child relationship data includes a child process flag indicating description information of said child process, and a parent process flag indicating description information of said parent process, said system Also includes:

a sub-process tag search module, configured to search for the sub-process tag from the process log;

The sub-process identification module searches for description information of the sub-process according to the sub-process tag.
The software cleaning system according to claim 33, wherein the software behavior information comprises a monitoring log, and the monitoring log is obtained based on monitoring of an installation process of the plurality of software, wherein the monitoring log includes the bundled software Descriptive information, and a binding tag pointing to the description information of the bundled software.
The software cleaning method according to claim 33, wherein the software behavior information comprises a bundled feature library, the bundled feature library is used to record a bundled feature, and the system further comprises:

a process capture module, configured to capture an event of creating a new process, and obtain information about the new process;

a feature comparison module, configured to compare related information of the new process with a bundled feature in the bundled feature library;

If the related information of the new process matches the bundling feature, the bundle identification module identifies the software corresponding to the new process as the bundled software.
The software cleaning system of claim 33, further comprising:

a bundled software identification module for identifying the bundled software pair based on pre-recorded software behavior information Should be bundled with software;

The binding relationship prompting module is configured to generate prompt information, and prompt a binding relationship between the bundled software and the bundled software.
The software cleaning system of claim 33, further comprising:

Using a frequency acquisition module, configured to acquire a frequency of use of the bundle software;

A cleanup suggestion generation module is configured to generate a cleanup suggestion according to the frequency of use.
A software cleaning system according to claim 39, wherein

If the usage frequency is greater than a predetermined first threshold, the cleaning suggestion is a suggestion reservation, and if the usage frequency is less than a predetermined second threshold, the cleaning suggestion is a suggestion cleanup, if the use frequency is located When the first threshold is between the second threshold and the second threshold, the cleaning suggestion may be cleaned, and the first threshold is higher than the second threshold.
The software cleaning system of claim 33, wherein the software behavior information and/or the software information base is located in a cloud server, the system further comprising:

The cloud data obtaining module is configured to obtain the software behavior information and/or the software information library from the cloud server.
The software cleaning system according to claim 33, wherein the description information of the plurality of related files of the bundled software is recorded in the software information base, further comprising:

The cleaning progress prompting module is configured to generate cleaning progress information according to the number of the plurality of related files and the number of deleted files of the plurality of related files, to prompt the cleaning progress of the bundled software.
The software cleaning system according to claim 42, wherein the cleaning progress prompting module further displays description information of the file currently being deleted by the cleaning progress information according to the file currently being deleted.
The software cleaning system according to any one of claims 33 to 43, further comprising:

a recovery request acquisition module, configured to acquire a recovery request for the bundle software;

The related file recovery module is configured to perform an action of deleting the related file in reverse to cancel the cleaning of the bundled software.
A computer program comprising computer readable code, when said computer readable code is run on a computing device, causing said computing device to perform any of claims 1 to 10, and/or claims 21-32 The software cleaning method described.
A computer readable medium storing the computer program of claim 45.