CN102163161B - A kind of process management method and device - Google Patents

Abstract

The invention discloses a process management method and device. The method includes: when the application program is running, collecting the relevant processes of the application program; merging the relevant processes of the application program into a set for management. The present invention provides another way for the user to more easily manage the process of the current system, provides the process of the whole system to the user more friendly, and makes the management more controllable through this display mode.

Description

Process management method and device

technical field

The invention belongs to the field of computers, and in particular relates to a process management method and device.

Background technique

A process is a running activity of a program with certain independent functions on a certain data set. It can apply for and own system resources, and is the basic unit of dynamic execution of the operating system. In a traditional operating system, a process is not only a basic allocation unit, but also a basic execution unit.

To an application, a process is like a big container. After the application program is run, it is equivalent to loading the application program into the container, and you can add other data and files to the container, such as: variable data required by the application program at runtime, DLL files that need to be referenced, etc. When the application is run twice, the contents of the container will not be dumped, and the system will find a new process container to accommodate it.

Processes can be divided into system processes and user processes. The system process refers to the process used to complete various functions of the operating system, which represents the operating system itself in the running state and is the basic condition for the system to run; the programs carried by the system process include: the system manages individual computers and completes various programs necessary for operation. User processes refer to all processes initiated by users, and programs carried by user processes, including: additional programs opened and executed by users, and these additional programs of course also include illegal programs that are automatically run without the user's knowledge.

When the application program is closed, the general application program closes the process of the application program. However, some existing applications, such as: PPS, pplive, uus, etc., after the user finishes running these applications and closes them, often the processes of these applications are still running in the task manager, which leads to the appearance of application programs. The case where the process is closed but the process does not exit. However, these processes still occupy system resources. When there are many similar application programs installed by the user, once these application programs are started, they will cause a great consumption of system resources. As mentioned earlier, this type of application cannot be truly exited from the traditional application interface. If you want to close these processes to release system resources, you can only close these processes manually. It is more difficult for ordinary users of knowledge.

The same application is likely to run on several data sets at the same time, that is to say, the same program can correspond to multiple processes, so when there are many related processes of this type of application that the above program is closed but the process does not exit, manually close these processes work becomes very complicated. First of all, it is necessary to identify which processes belong to this application program, which requires the user to have considerable computer skills and be very familiar with this application program, which is extremely difficult for ordinary users and even many technical personnel in the industry. And even if all the processes of the application program can be found out, these processes need to be manually closed one by one, which makes the operation more cumbersome. If many application programs need to be closed at this time, and each application program corresponds to multiple processes, this work is almost impossible to complete.

In addition, some applications will generate a process every time they are expanded, so that these applications will open multiple processes when they are repeatedly launched. If users want to manage these processes, especially when they want to close these applications, they need to pass Turning them off one by one manually makes the operation very cumbersome.

Contents of the invention

In view of this, the technical problem to be solved by the present invention is to provide a process management method and device, so that ordinary users can manage processes without hindrance.

In order to solve the above technical problem, the present invention discloses a process management method, including: when the application program is running, collecting the relevant processes of the application program; combining the relevant processes of the application program into a set for management.

Further, the step of merging the related processes of the application programs into a set for management includes: merging the related processes of the application programs into a set for display.

Further, the name of the collection is displayed as an application program name or document name, and the display icon of the collection is displayed as an application program icon.

Further, the step of merging the related processes of the application programs into a set for management includes: merging the related processes of the application programs into a set, and closing the related processes by closing the set.

Further, the method includes: receiving a closing instruction for the set, closing the identified independent processes in the set, and dissolving the set.

Further, the step of merging the related processes of the application programs into a set for management includes: merging the related processes of the application programs into a set, and suspending/continuing the related processes by suspending/continuing the set .

Further, the method includes: receiving a pause/continue instruction for the set, and suspending/continuing the identified independent process in the set, associating the identified shared process in the set with the application program The thread suspends/continues.

Further, the related process of the application program includes: the main process of the application program and the same kind of process as the main process opened by the application program.

Further, the step of collecting the relevant processes of the application program includes: monitoring each process in real time or periodically, and collecting the relevant processes of the application program according to the process name and/or path name of the main process of the application program.

Further, the related processes of the application program include: the main process of the application program and one or more processes having a family relationship with the main process.

Further, the step of collecting related processes of the application program includes: presetting a process list, in which identifiers of all potential related processes of the application program are saved; combining the process list, collecting the application program in real time or periodically related processes of the program.

Further, the method includes: combining with the process list, performing security checks on processes not matched by the process list in real time or periodically.

Further, the step of collecting the relevant processes of the application program includes: monitoring each process in real time or periodically, and collecting the relevant processes of the application program according to the main process of the application program and the process family relationship.

Further, it includes: finding the upper-level process/lower-level process of an unknown process according to the parent process ID/child process ID, and when it is determined that the upper-level process/lower-level process has a family relationship with the main process, determine that the process is the related processes of the above-mentioned application programs and collect and record the processes.

Further, it includes: finding an unrecorded lower-level process/upper-level process according to the child process ID/parent process ID of a known process in the related process, and determining the lower-level process/upper-level process as the related process of the application program and collect records.

In order to solve the above technical problems, the present invention also discloses a process management device, which is applied to the situation where one or more related processes carry an application program, including: a collection module, used to collect the application program when the application program is running The related processes of the program; the management module is used to combine the related processes of the application program into a set for management.

Further, the management module is configured to combine the related processes of the application programs into a collection for display; the collection name is displayed as an application program name or document name, and the display icon of the collection is displayed as an application program icon. show;

Further, the management module is configured to combine related processes of the application programs into a set, and close/pause/continue the related processes by closing/pausing/continuing the set.

Further, the management module is configured to receive a shutdown instruction for the collection, close the identified independent processes in the collection, and disband the collection; and is further used for receiving a suspension of the collection /continue indication, and suspend/continue the identified independent process in the set, and suspend/continue the thread related to the application program in the identified shared process in the set.

Further, the collection module is configured to monitor each process in real time or periodically, and collect related processes of the application program according to the process name and/or path name of the main process of the application program; the related processes of the application program, Including: the main process of the application program and the same process as the main process opened by the application program.

Further, the collection module is configured to monitor each process in real time or periodically and collect related processes of the application program according to the main process of the application program and the process family relationship; it is also used to preset a process list, in which the The identification of all potential related processes of the application program, combined with the process list, collects the related processes of the application program in real time or periodically; the related processes of the application program include: the main process of the application program and the One or more processes with a family relationship to the main process.

Further, the collection module is configured to find the upper-level process/lower-level process of an unknown process according to its parent process ID/child process ID, and when it is determined that the upper-level process/lower-level process has a family relationship with the main process, determine The process is a related process of the application and collects records; it is further used to find an unrecorded lower layer process/upper layer process according to the child process ID/parent process ID of a known process in the related process, and determine the The lower-level process/upper-level process is a related process of the application program and collects records; it is further used in combination with the process list to perform security detection on processes not matched by the process list in real time or periodically.

Compared with existing solutions, the technical effects obtained by the present invention are:

1) For the whole system, it provides another way for the user to manage the current system process more easily, provides the process of the whole system to the user more friendly, and makes the management controllable through this display method stronger;

2) For individual processes, users do not need professional knowledge to manage individual application programs without barriers, and do not need to understand the relationship between individual application programs and their related processes;

3) By managing the processes according to the relationship of the same source and the same type, the processes can be purposefully distinguished and sorted according to user needs, and the redundant operation is greatly simplified through the management of the collection;

4) Realize the real shutdown of the application without affecting the use of other processes and applications, and reasonably release system resources while maintaining the stable operation of the system;

5) Use an independent UI management interface, and use the application name or document name to name the process to make the process readable and easier for users to understand and manage;

6) In the process of process management, suspicious processes can also be found and safety testing can be carried out to further ensure the stability of the system;

7) Cooperate with the same collection management method for the process to make the process-based suspension/continuation management more efficient; cooperate with the collection management method of the same source (collected according to the application program) for the process, you can suspend/continue the management of a single process Resume, implements pause/resume to the overall application.

Description of drawings

Fig. 1 is the method flowchart of the first and second embodiments of the present invention;

Fig. 2 is the first schematic diagram of the application example of step S14 of the present invention;

FIG. 3 is a second schematic diagram of an application example of step S14 of the present invention;

4 is a schematic diagram of an application example of the first embodiment of the present invention;

5 is a schematic diagram of an application example of the second embodiment of the present invention;

Fig. 6 is a device structure diagram of the third embodiment of the present invention.

Detailed ways

The implementation of the present invention will be described in detail below in conjunction with the drawings and examples, so that the realization process of how to use technical means to solve technical problems and achieve technical effects in the present invention can be fully understood and implemented accordingly.

The core idea of the present invention is: when the application program is running, collect the relevant processes of the application program; combine the relevant processes of the application program into one set for management. It is applied to the situation where one or more related processes host an application, or to the architecture of multiple sets of processes, that is, each time an application is extended, a new set of processes is correspondingly maintained.

The management of merging the related processes of the application program into a set includes the following two parts: 1) merging and displaying, merging the related processes of the application program into a set for display; the name of the set is named after the application name or the document name, and the display icon of the set is displayed as an application icon; 2) One-click close/pause/continue, that is, to merge the related processes of the application into one set, and close/pause/continue the Set to close/pause/continue the related process.

The document name refers to the name of the task currently executed by the application program or the name of the currently running file or the name of the currently playing media.

The name of the application program refers to the name of the application program, which can be the name of the program in Chinese or English, or the name of the executable file of the application program.

For example, when a video player is running, it is associated with multiple processes. After merging these processes into a collection, you can use the name of the video file (document name) being played as the collection name. Of course, you can also use this video player The name of the device (application name) is used as the collection name.

Related processes can include two levels, namely homologous processes and similar processes;

1) Homologous process

Related processes include: the main process of the application program and supporting processes that have a family relationship with the main process; wherein, these supporting processes include: one or more processes that are directly or indirectly opened and called by the main process, and directly Or indirectly open and call one or more processes of the main process; it should be noted that the supporting process includes an independent process and/or a shared process; the shared process is a process called by multiple upper-level processes at the same time, so The above-mentioned independent process is a process called by only one upper-level process;

2) Similar processes

Related processes include: the main process of the application, the process opened by the application of the same type as the main process, and of course, the process of the same type as the main process opened by the application of the same type ; It should be noted that processes of the same type as the main process may also include independent processes and/or shared processes. For example, each time an application is run, it corresponds to a process. This application is run continuously for 3 times. At this time There are 3 processes, and these three processes are the same kind of process.

The management of homologous processes in the method of the present invention will be described below with the first embodiment. Applied to the situation where one or more related processes carry an application program, the above-mentioned application program mainly refers to a program carried by a user process. As shown in Figure 1, perform the following operations:

Step S11, when the application program is running, collect the relevant process of the application program;

Related processes include: the main process of the application program and supporting processes that have a family relationship with the main process; wherein, these supporting processes include: one or more processes that are directly or indirectly opened and called by the main process, and directly Or indirectly start and call one or more processes of the main process; it should be noted that the supporting processes include independent processes and/or shared processes.

The collection of the relevant processes of the application program can be realized in the following ways alone or in combination, and the present invention is not limited thereto:

1) Presetting a process list, wherein the identifiers of all potential related processes of the application are stored; combining the list to collect the related processes of the application in real time or periodically;

Specifically, the identifier of the related process is PID (process identification); all potential related processes refer to all possible processes related to the application program, no matter whether they are currently started with the application program, this potential related process Processes can be exhaustively enumerated by technicians based on experience and statistical data and need to be constantly updated and maintained;

The processes appearing in the system are monitored in real time or periodically, the PIDs of these processes are obtained, and which of the processes appearing in the system are related to the application program is identified through process list matching and collected and recorded. In addition, for the processes that appear in the system that are not matched by the process list, security checks are performed in real time or periodically to further ensure the security of the system.

2) monitoring each process in real time or periodically, and collecting related processes of the application program according to the main process of the application program and the process family relationship;

Specifically, when a new process is discovered through real-time or periodic monitoring, the upper-level process/lower-level process is found according to the parent process ID/child process ID of the process, and then the upper-level/lower-level process is searched step by step according to the upper-level process/lower-level process , and finally find the main process, so that it can be judged whether the upper process/lower process has a family relationship with the main process, and if there is a family relationship, determine that the new process is a related process of the application program and collect the records process;

Or, when a new process is found through real-time or periodic monitoring, the upper-level process/lower-level process can be found according to the parent process ID/child process ID of the process, and the relationship between the upper-level process/lower-level process and the above-mentioned process can be directly known according to a family relationship list. Whether the main process has a family relationship, if there is a family relationship, directly determine that the new process is a related process of the application program and collect and record the process.

Or, when a new process is found to appear through real-time or periodic monitoring, it triggers the detection of all related processes of the application program that have collected records, and detects whether there is an unrecorded lower-level process according to the sub-process identifier of each related process , if it exists, it can be determined that this lower-level process is a related process of the application program, and the lower-level process is collected and recorded.

Or, by detecting all relevant processes of the application program that have been collected and recorded in real time or periodically, find the unrecorded upper-level process according to the parent process identification of the main process and its upper-level process, and determine that the upper-level process is all process related to the application described above and collect records.

It should be noted that, in 1), when the process list is not updated but a new process appears, 2) can be combined to identify and collect the new process to ensure the accuracy of the merged display; in 2), it can also be Use the process list of 1) as the family relationship list, as the basis for judging whether there is a family relationship and whether it is recorded, so as to ensure the accuracy of the merged display;

Step S12, merging and displaying the related processes of the application programs as a set on the UI management interface;

The related processes of this application generally have the same attribute or the name that best represents these related processes, such as the same or similar process name, or the same or similar part in the process name, or the application name, Document name, these names can be used as the name of the collection to display these related processes together, and the icon of the collection is displayed as an application program icon. Of course, the present invention is not limited to this; Some resources are run on the UI management interface and are only merged and displayed as a name, so that they can be managed as a unified process (collection), so that ordinary users can understand and manage the process without barriers, and understand the application The correspondence between the program and its related processes;

Step S13, receiving a close/pause/continue instruction for the application or a close/pause/continue instruction for the merged display set;

For some applications, it will correspond to multiple processes, so it is extremely difficult for ordinary users to close the application through the process;

For some applications, there is a situation that the program is exited but the process is still open, so that the user cannot really exit through the exit of the program interface; the user thinks that the program has been closed, but in fact the process of these programs is still running and takes up a lot of system resources; and even Users know that the processes of these programs are still running, but if the above-mentioned one-to-many relationship exists between these programs and processes, due to technical reasons, ordinary users cannot know which processes;

Through the operation of steps S11-S12, if the user wants to close the application program, he can enter the UI management interface that combines and displays the relevant processes of each application program, and directly clicks to close the process of the application program combined display, and the application program can be directly closed. The relevant processes of the program are closed together, so that the user can easily close the relevant processes of the application without professional knowledge, which solves the difficulty that the user cannot find the relevant processes of the application and closes these processes one by one trouble;

Step S14, closing/suspending/continuing the independent process among the identified related processes of the application program;

1) receiving a closing instruction for the collection and closing the identified independent process in the collection, and disbanding the collection on the UI management interface;

2) receiving a suspend/continue instruction for the set, and suspending/continuing the identified independent processes in the set, and suspending threads related to the application program in the identified shared processes in the set /Continue, and display the collection as a pause/running state on the UI management interface; the currently processed data of the paused process or thread can be saved, and the read data will continue to run from the pause point when the process or thread is continued; It is also possible to discard the currently processed data of the suspended process or thread, and start rerunning from the initial state when continuing the process or thread. For example, when a web page is opened through a 360 browser, the opening of the page can be suspended in this way /continue.

Because the related processes of the application program may contain shared processes, if these shared processes are also closed, it will affect the operation of other applications, so it is only necessary to identify the independent processes in the related processes of the application program and close them; The shared process in the related process of the application program remains open, but the thread about the independent process in the shared process ends; at this time, it can be considered that the application program is completely closed, and the combined display set is closed. In this way, the application program can be truly closed without affecting the use of other processes and application programs, and the system resources can be reasonably released while maintaining the stable operation of the system. In addition, the operation of identifying an independent process may be performed after receiving the shutdown instruction in step S13, or may be performed before, and the present invention is not limited thereto.

Step S14 of the present invention is explained below in particular with an application example. As shown in FIG. 2 , application A corresponds to process A and process C, and is combined and displayed as set A; application B corresponds to process B and process C, and is combined and displayed as set B. If the user wants to close application program A, then enter the UI management interface and click to close collection A, as shown in Figure 3, at this time, process A is closed after identification, and process C is kept open, because process C still carries application program B, but process C The thread in the part about process A ends. Process C is only called by process B at this time, so it has become an independent process. At this time, if the user wants to close application B, then enter the UI management interface and click to close set B. At this time, both process B and process C are closed.

Hereinafter, an application example is used to explain the overall process of the first embodiment of the present invention, as shown in FIG. 4 .

The application scenarios of the present invention are as follows:

When 360 Security Guard is running, it will start the process of the main program of 360 Security Guard (360safe.exe), and this process will also start the process of the real-time monitoring program (360tray.exe), and the process of this real-time monitoring program will also open the active defense service process (ZhuDongFangYu.exe); but for ordinary users, the meaning and function of these three processes are basically unreadable, and when browsing these three processes through the existing windows task manager, ordinary users also The correlation between these three processes will not be known.

Below, carry out process management by the mode of the present invention:

First, according to the pre-configured list of all related processes of 360 Security Guard, it can be collected that 360 Security Guard has opened three processes: the main process 360safe.exe and supporting processes 360tray.exe and ZhuDongFangYu.exe.

Then, the three processes 360safe.exe, 360tray.exe and ZhuDongFangYu.exe are merged and displayed on the UI management interface as a collection "360 Security Guard", and the icon of the application "360 Security Guard" is used for display; General users can see the process of 360 Security Guard without barriers, and can also understand the corresponding relationship between 360 Security Guard and the process.

At this time, if the user wants to close 360 Security Guard, he only needs to click the icon of the collection "360 Security Guard" on the UI management interface to issue a shutdown instruction; identify the three processes 360safe.exe and 360tray among the related processes of 360 Security Guard. exe and ZhuDongFangYu.exe are independent processes, and closing them directly will not affect the operation of other applications, so close these three processes, and close the combined display "360 Security Guard" on the UI management interface.

It should be noted that the above closing operation is particularly meaningful for a class of applications that exit the program but still open the process. Because this type of application program cannot really exit from the traditional application program interface, the system resources occupied by the process can only be released by manually closing the process. However, this kind of process closing operation is relatively difficult for ordinary users who do not have professional knowledge, especially when there are many related processes of this type of application, it is difficult for ordinary users to identify all related processes and close them one by one. Identifying these processes and shutting them down individually is difficult, even for a skilled technician. However, the closing operation can be easily completed by using the solution of the present invention, which brings great convenience to ordinary users and even technicians to manage the process.

The management of similar processes in the method of the present invention will be described below with the second embodiment. The architecture applied to multiple sets of processes, that is, each time an application is extended, a new set of processes is correspondingly maintained. The above-mentioned application program mainly refers to a program carried by a user process. Refer to Figure 1 and perform the following operations:

Step S21, when the application program is running, collect the relevant process of the application program;

Related processes include: the main process of the application program, the process opened by the application program of the same type as the main process, and the process of the same type as the main process opened by the application program of the same type as the application program; explanation is required Notably, processes of the same type as the main process may also include independent processes and/or shared processes.

The collection of the relevant process of the application program can be realized in the following manner, and the present invention is not limited thereto:

Monitor each process in real time or periodically, and collect related processes of the application program according to the process name and/or path name of the main process of the application program; specifically, some applications will open multiple processes when they are started repeatedly, such as : When the application program is running, it corresponds to a main process; at this time, the user starts the application program again, and the application program will start another process, generally with the same name and/or path as the main process, and the two Those are similar processes; at this time, through real-time or periodic monitoring of each process in the system, according to the process name or path name of the main process of the application, collect other processes with the same name and/or the same path opened by the application, These processes are the relevant processes of the application program.

Step S22, merging and displaying the related processes of the application programs as a set on the UI management interface;

The related processes of this application generally have the same attribute or the name that best represents these related processes, such as the same or similar process name, or the same or similar part in the process name, or the application name, Document name, these names can be used as the name of the collection to display these related processes together, and the icon of the collection is displayed as an application program icon. Of course, the present invention is not limited to this; Running on some resources, it is only merged and displayed as a name on the UI management interface, so as to be managed as a unified process, so that general users can understand and manage the process without barriers, and understand the application related to it Process correspondence;

Step S23, receiving a close/pause/continue instruction for the application or a close/pause/continue instruction for the merged display set;

For some applications, there is a situation that a new process will be opened every time the application is expanded. If the application is opened multiple times, multiple sets of the same process will appear at the same time; Close/pause/continue, you must manually close/pause/continue these applications one by one;

Through the operations of steps S21-S22, if the user wants to close these applications that have been extended multiple times, he can enter the UI management interface that combines and displays the related processes of the applications, and directly clicks to close the collection of applications that are displayed in combination, and can Directly close the relevant processes of the application programs together, so that the user can easily close these application programs together, saving the user the trouble of closing them one by one;

Step S24, closing/suspending/continuing the independent process among the identified related processes of the application program;

1) receiving a closing instruction for the collection and closing the identified independent process in the collection, and disbanding the collection on the UI management interface;

2) receiving a suspend/continue instruction for the set, and suspending/continuing the identified independent processes in the set, and suspending threads related to the application program in the identified shared processes in the set /Continue, and display the collection as a pause/running state on the UI management interface; the currently processed data of the paused process or thread can be saved, and the read data will continue to run from the pause point when the process or thread is continued; It is also possible to discard the currently processed data of the suspended process or thread, and start rerunning from the initial state when continuing the process or thread.

Because the related processes of the application program may contain shared processes, if these shared processes are also closed, it will affect the operation of other applications, so it is only necessary to identify the independent processes in the related processes of the application program and close them; The shared process in the related process of the application program remains open, but the thread about the independent process in the shared process ends; at this time, it can be considered that the application program is completely closed, and the combined display set is closed. In this way, the application program can be truly closed without affecting the use of other processes and application programs, and the system resources can be reasonably released while maintaining the stable operation of the system. In addition, the operation of identifying an independent process may be performed after receiving the closing instruction in step S23, or may be performed before, and the present invention is not limited thereto. Refer to the application example of step S14.

Hereinafter, an application example is used to explain the overall process of the second embodiment of the present invention, as shown in FIG. 5 .

The application scenarios of the present invention are as follows:

When a user initially opens a web page through the 360 browser based on Webkit and IE dual-core, three 360 browser processes (360chrome.exe) with the same process name will be opened, corresponding to the extension program "Favorites", the plug-in "shockwave flash” and the opened current webpage; and the user opens three webpages in a row through the 360 browser through tabs, and three 360 browser processes (360chrome.exe) with the same process name appear, and each process corresponds to a newly opened webpage. At this time, if the user wishes to close the pages of the 360 browser, they also need to close these pages one by one.

Below, carry out process management by the mode of the present invention:

First, according to the process name 360chrome.exe of the 360 browser, the present invention can collect other processes that the 360 browser has opened multiple times: 360chrome.exe.

Then, these processes 360chrome.exe are merged and displayed on the UI management interface as a set "360 browser", and displayed using the icon of 360 browser; in this way, general users can see the whole of 360 browser without barriers process.

At this time, if the user wants to close the 360 browser, he only needs to click the icon of the set "360 browser" on the UI management interface to issue a shutdown instruction; identify all six 360chrome.exe processes related to the 360 browser, and these processes They are all independent processes, and closing them directly will not affect the operation of other applications, then close these six 360chrome.exe processes, and close the combined display "360 browser" on the UI management interface.

The device of the present invention is described below with the third embodiment, which is applied to the situation where one or more related processes carry an application program, or to the architecture of multiple sets of processes, that is, each time an application is extended, a set of corresponding maintenance is maintained. new process. The above-mentioned application program mainly refers to a program carried by a user process.

As shown in FIG. 6 , it is a process management device, which runs in the same system as the application program. The process management device includes: a collection module 1 and a management module 2;

A collection module 1, configured to collect related processes of the application when the application is running;

The management module 2 is used to provide a UI (user interface) management interface to merge the relevant processes of the application programs into a set for management;

Specifically, the management module 2 can be used for "merging and displaying"—namely, merging the related processes of the application programs into a collection for display; the collection name is displayed with the application name or document name, and the The display icon of the collection is displayed as an application icon;

The management module 2 can also be used for "one-click closing/pausing/continuing"—that is, merging the related processes of the application program into a set, and closing/pausing/continuing the set to close/close the related processes Pausing/continuing; specifically, when receiving a closing instruction for the application program or a closing instruction for the merged and displayed process, identifying an independent process among the related processes of the application program, closing the independent process, and On the UI management interface, the combined display collection will be dissolved; after receiving the pause/continue instruction for the collection, and suspending/continuing the identified independent process in the collection, the identified shared process in the collection Suspend/continue the thread related to the application in the application program; the currently processed data of the suspended process or thread can be saved, and the read data can continue to run from the suspended point when the process or thread is continued; the suspended process or The currently processed data of the thread is discarded, and the process or thread is resumed from the initial state when continuing the process or thread.

Collection module 1 includes the following two levels of collection for two different application scenarios:

1) The architecture applied to multiple sets of processes, that is, each time an application is extended, a new set of processes is correspondingly maintained. The related process of the application program includes: the main process of the application program and the same process as the main process opened by the application program.

The collection module 1 monitors each process in real time or periodically, and collects related processes of the application program according to the process name and/or path name of the main process of the application program.

2) Applied to the situation where one or more related processes carry an application program. The related processes of the application program include: the main process of the application program and one or more lower-level processes having a family relationship with the main process.

The collection module 1 can be used to preset a process list, wherein the identifiers of all potential related processes of the application program are saved, and the related processes of the application program are collected in real time or periodically in combination with the list; The above process list is used to perform security detection on processes not matched by the process list in real time or periodically;

The collection module 1 can also be used to monitor each process in real time or periodically and collect the related processes of the application program according to the main process of the application program and the process family relationship; The process identification finds its upper-level process/lower-level process, and when it is determined that the upper-level process/lower-level process has a family relationship with the main process, determine that the process is a related process of the application program and collect and record the process; or, Find an unrecorded lower-layer process/upper-layer process according to the child process ID/parent process ID of a known process in the related process, determine that the lower-layer process/upper-layer process is a related process of the application program, and collect and record the Lower process/upper process.

The aforementioned process management device corresponds to the features of the aforementioned process management method, and for the shortcomings, please refer to the aforementioned process management method.

The above description shows and describes several preferred embodiments of the present invention, but as mentioned above, it should be understood that the present invention is not limited to the forms disclosed herein, and should not be regarded as excluding other embodiments, but can be used in various Various other combinations, modifications, and environments can be made within the scope of the inventive concept described herein, by the above teachings or by skill or knowledge in the relevant field. However, changes and changes made by those skilled in the art do not depart from the spirit and scope of the present invention, and should all be within the protection scope of the appended claims of the present invention.

Claims (19)

1. A process management method, characterized in that, comprising: On the UI management interface, the collected related processes of an application are merged into a unified process for management, which is displayed as a single name or icon; The related processes keep running on their original resources. 2. The process management method according to claim 1, wherein: The name of the unified process is displayed as an application program name or document name, and the display icon of the unified process is displayed as an application program icon. 3. The process management method according to claim 2, wherein the step of merging the collected related processes of an application running into a unified process for management further comprises: The related processes run by the application program are closed by closing the unified process. 4. The process management method according to claim 3, further comprising: receiving a shutdown instruction for the unified process, closing the identified independent processes in the unified process, and disbanding the unified process. 5. The process management method according to claim 1, wherein the step of merging the collected related processes of an application running into a unified process for management further comprises: Pausing/continuing the associated process of the application running by pausing/continuing the unified process. 6. The process management method according to claim 5, further comprising: receiving a suspend/resume indication of the unified process, and suspending/resuming identified independent processes in the unified process, and suspending/resuming identified threads associated with the application in shared processes in the unified process Pause/Continue. 7. The process management method according to any one of claims 1 to 6, wherein the collected steps of the related process run by an application include: Each process is monitored in real time or periodically, and related processes of the application are collected according to the process name and/or path name of the main process of the application. 8. The process management method according to claim 7, wherein the collected steps of the related process run by a certain application program include: Presetting a process list, wherein identifiers of all potential related processes of the application are stored; Combined with the process list, the relevant processes of the application program are collected in real time or periodically. 9. The process management method according to claim 8, further comprising: Combined with the process list, security checks are performed on processes not matched by the process list in real time or periodically. 10. The process management method according to claim 8, wherein the collected steps of the related process run by a certain application program include: Each process is monitored in real time or periodically, and related processes of the application are collected according to the main process of the application and the process family relationship. 11. The process management method according to claim 10, further comprising: Find the upper-level process/lower-level process according to the parent process ID/child process ID of an unknown process, and determine that the process is related to the application program when it is determined that the upper-level process/lower-level process has a family relationship with the main process process and collect records of said process. 12. The process management method according to claim 10, further comprising: According to the child process ID/parent process ID of a known process in the related process, find the unrecorded lower layer process/upper layer process, determine the lower layer process/upper layer process as the related process of the application program and collect records. 13. A process management device, characterized in that it is applied to the situation where one or more related processes carry an application program, comprising: A collection module, used to collect related processes running by an application; The management module is used for merging the related processes of a certain application program collected by the collection module into a unified process for management on the UI management interface, which is displayed as a single name or icon, and keeps the related processes in their respective Run on the original resources. 14. The process management device according to claim 13, characterized in that, it is displayed as a single name or icon, further comprising: the name of the unified process is displayed as an application name or a document name, and the display of the unified process Icons are displayed as application icons. 15. The process management device according to claim 13, wherein: The management module is further configured to close/pause/continue the related process by closing/pausing/continuing the unified process. 16. The process management device according to claim 15, wherein: The management module is further configured to receive a shutdown instruction for the unified process, close the identified independent process in the unified process, and disband the unified process; and is further configured to receive a shutdown instruction for the unified process and suspend/continue the identified independent process in the unified process, and suspend/continue the identified thread related to the application in the shared process in the unified process. 17. The process management device according to claim 14, wherein: The collection module is configured to monitor each process in real time or periodically, and collect related processes of the application program according to the process name and/or path name of the main process of the application program. 18. The process management device according to claim 14, wherein: The collection module is configured to preset a process list, which saves the identifiers of all potential related processes of the application program, and collects the related processes of the application program in real time or periodically in combination with the process list. 19. The process management device according to claim 17, wherein: The collection module is further configured to find the upper-level process/lower-level process of an unknown process according to its parent process ID/child process ID, and when it is determined that the upper-level process/lower-level process has a family relationship with the main process, determine the The process is a related process of the application program and collects records; it is further used to find an unrecorded lower-level process/upper-level process according to the child process ID/parent process ID of a known process in the related process, and determine the lower-level process The process/upper-level process is a related process of the application program and collects records; it is further used in combination with the process list to perform security checks on processes not matched by the process list in real time or periodically.