Process management method and device, computing equipment and computer readable storage medium

Abstract

The invention relates to the technical field of computers, and discloses a method for process management, which comprises the following steps: under the condition of meeting a low power consumption condition, sending a low power consumption control message to an event management process so as to enable the event management process to send a stop signal; and under the condition that the stop signal is received, the application process enters a low-power-consumption state. By receiving the stop signal sent by the event management process, the running state of the application process is switched, so that the application process enters the low-power-consumption state, power consumption management on the application process can be realized, and the power consumption of the system is reduced. The invention furthermore discloses a process management apparatus, a computing device and a computer readable storage medium.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a method, apparatus, computing device, and computer-readable storage medium for process management. Background Art

[0002] Currently, in multi-threaded applications, when the main thread enters the idle state, other threads do not enter the idle state at the same time, but continue to run in the background, thereby continuing to occupy the processor's computing resources and preventing the entire application or even the system from entering a low-power state.

[0003] In order to manage the power consumption of the application process and reduce the power consumption of the entire application or even the system, the related technology discloses a process management method, including: maintaining a first thread for the application process, the application process includes one or more application threads, the one or more application threads are used to implement predetermined functions, each application thread receives messages from outside the application process and / or sends messages to the outside of the application process through the first thread; according to the type of the message received by the first thread, the running state of the application process is switched.

[0004] In the process of implementing the embodiments of the present disclosure, it is found that there are at least the following problems in the related art:

[0005] Although the related technology can realize power consumption management for application processes, it needs to maintain a separate thread for receiving messages sent from the outside and switching the process state through communication between threads. In addition, maintaining this separate thread will occupy thread resources.

[0006] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present application, and therefore may include information that does not constitute the prior art known to ordinary technicians in the field. Summary of the invention

[0007] In order to provide a basic understanding of some aspects of the disclosed embodiments, a brief summary is given below. The summary is not an extensive review, nor is it intended to identify key / critical components or delineate the scope of protection of these embodiments, but rather serves as a prelude to the detailed description that follows.

[0008] The embodiments of the present disclosure provide a method, apparatus, computing device, and computer-readable storage medium for process management, which can reduce the power consumption of the system and reduce the occupation of thread resources in the application process.

[0009] In some embodiments, the method includes: when a low power consumption condition is met, sending a low power consumption control message to an event management process so that the event management process sends a stop signal; when the stop signal is received, the application process enters a low power consumption state.

[0010] Optionally, sending a low power consumption control message to an event management process includes: an application process sending a low power consumption control message to an event management process; or, an application process sending a low power consumption control message to a monitoring process, and the monitoring process forwarding the low power consumption control message to the event management process.

[0011] Optionally, satisfying the low power consumption condition includes: a main thread of the application thread enters an idle state.

[0012] Optionally, receiving the stop signal includes: the event management process sending the stop signal to the application process; or, the event management process sending the stop signal to the monitoring process, and the monitoring process forwarding the stop signal to the application process.

[0013] Optionally, the application process enters a low power consumption state, including: pausing all threads of the application process.

[0014] Optionally, the method further includes: when an external event occurs, the application process exits the low power consumption state.

[0015] Optionally, the application process exits the low power consumption state, including: the application process resumes running all threads when receiving a start signal sent by the event management process.

[0016] In some embodiments, the device includes: a processor and a memory storing program instructions, and the processor is configured to execute the method for process management when running the program instructions.

[0017] In some embodiments, the computing device includes: a computing device body; and a device for process management, installed on the computing device body.

[0018] In some embodiments, the computer-readable storage medium includes: program instructions stored therein, and when the program instructions are executed, the computer is used to execute the method for process management.

[0019] The method, apparatus, computing device, and computer-readable storage medium for process management provided by the embodiments of the present disclosure can achieve the following technical effects:

[0020] Through the signal in the process communication mechanism, the communication between the event management process and the application process can be realized. When the application process meets the low power consumption condition, the running state of the application process can be switched by receiving the stop signal sent by the event management process, so that the application process enters the low power consumption state, thereby realizing the power consumption management of the application process and reducing the power consumption of the system. In addition, in the related art, the application process needs to maintain a separate thread for receiving external messages. The embodiment of the present disclosure does not need to modify the application process, does not occupy the thread resources of the application process, and improves the thread utilization rate of the application process. In addition, in the related art, the low power consumption scenario must be considered during the design process, and an independent thread needs to be written to control the running state of the process to achieve power consumption management, and the application process is sensitive to the power consumption management mechanism. The embodiment of the present disclosure directly switches the running state of the application process by receiving the stop signal sent by the event management process, so that the application process enters the low power consumption state. There is no need to consider the low power consumption scenario during the design process, and there is no need for communication between the threads of the application process during the power consumption management process. The application process can run normally before entering the low power consumption state, so that the application process is not sensitive to the power consumption management mechanism.

[0021] The above general description and the following description are exemplary and explanatory only and are not intended to limit the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] One or more embodiments are exemplarily described by corresponding drawings, which do not limit the embodiments. Elements with the same reference numerals in the drawings are shown as similar elements, and the drawings do not constitute a scale limitation, and wherein:

[0023] Figure 1 It is a schematic diagram of the hardware environment used for process management;

[0024] Figure 2 It is a schematic diagram of the software environment used for process management;

[0025] Figure 3 is a schematic diagram of a method for process management provided by an embodiment of the present disclosure;

[0026] Figure 4 is a schematic diagram of another method for process management provided by an embodiment of the present disclosure;

[0027] Figure 5 is an application schematic diagram of an embodiment of the present disclosure;

[0028] Figure 6 is a schematic diagram of another method for process management provided by an embodiment of the present disclosure;

[0029] Figure 7It is a schematic diagram of a device for process management provided by an embodiment of the present disclosure. DETAILED DESCRIPTION

[0030] In order to be able to understand the features and technical contents of the embodiments of the present disclosure in more detail, the implementation of the embodiments of the present disclosure is described in detail below in conjunction with the accompanying drawings. The attached drawings are for reference only and are not used to limit the embodiments of the present disclosure. In the following technical description, for the convenience of explanation, a full understanding of the disclosed embodiments is provided through multiple details. However, one or more embodiments can still be implemented without these details. In other cases, to simplify the drawings, well-known structures and devices can be simplified for display.

[0031] The terms "first", "second", etc. in the specification and claims of the embodiments of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchanged where appropriate, so that the embodiments of the embodiments of the present disclosure described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

[0032] Unless otherwise stated, the term "plurality" means two or more.

[0033] In the embodiment of the present disclosure, the character " / " indicates that the preceding and following objects are in an "or" relationship. For example, A / B indicates: A or B.

[0034] The term "and / or" is a description of the association relationship between objects, indicating that three relationships can exist. For example, A and / or B means: A or B, or, A and B.

[0035] The term "correspondence" may refer to an association relationship or a binding relationship. The correspondence between A and B means that there is an association relationship or a binding relationship between A and B.

[0036] Terminology explanation:

[0037] Power management refers to the mechanisms and methods for managing system power consumption.

[0038] A thread is the smallest unit that an operating system can schedule and execute.

[0039] A process is an instance of a running program and is the management and control unit of the operating system for the executing program.

[0040] Signal refers to a mechanism for delivering asynchronous notifications and handling software interrupts between processes.

[0041] Combination Figure 1 As shown, the system for process management includes: a terminal device 102 and a server 104 .

[0042] The method for process management provided by the embodiments of the present disclosure can be widely used in smart home (SmartHome), smart home, smart home equipment ecology, smart residential (Intelligence House) ecology and other whole-house intelligent digital control application scenarios. Figure 1 As shown, the server 104 is connected to the terminal device 102 via a network, and can be used to provide services (such as application services, etc.) for the terminal or a client installed on the terminal. A database can be set on the server or independently of the server to provide data storage services for the server 104. Cloud computing and / or edge computing services can be configured on the server or independently of the server to provide data computing services for the server 104.

[0043] It should be understood that the terminal device 102 in the embodiment of the present disclosure may be referred to as a user equipment (UserEquipment), a terminal device, a mobile device or a mobile terminal, etc. For example, the terminal device 102 may not be limited to a PC, a mobile phone, a mobile phone, a tablet computer, a computer with a mobile terminal, etc. For another example, the terminal device 102 may also be a smart air conditioner, a smart range hood, a smart refrigerator, a smart oven, a smart stove, a smart washing machine, a smart water heater, a smart washing device, a smart dishwasher, a smart projection device, a smart TV, a smart clothes drying rack, a smart curtain, a smart audio and video, a smart socket, a smart speaker, a smart speaker, a smart fresh air device, a smart kitchen and bathroom device, a smart bathroom device, a smart sweeping robot, a smart window cleaning robot, a smart mopping robot, a smart air purification device, a smart steamer, a smart microwave oven, a smart kitchen treasure, a smart purifier, a smart water dispenser, a smart door lock, etc.

[0044] Currently, there are multi-threaded applications in the above-mentioned terminal device 102. When the main thread enters the idle state, other threads do not enter the idle state at the same time, but continue to run in the background, thereby continuing to occupy the processor's computing resources, and unable to make the entire application or even the system enter a low-power state.

[0045] In order to manage the power consumption of the application process and reduce the power consumption of the entire application or even the system, the related technology discloses a process management method, including: maintaining a first thread for the application process, the application process includes one or more application threads, the one or more application threads are used to implement predetermined functions, each application thread receives messages from outside the application process and / or sends messages to the outside of the application process through the first thread; according to the type of the message received by the first thread, the running state of the application process is switched.

[0046] Although the related technology can realize power consumption management for application processes, it needs to maintain a separate thread for receiving messages sent from the outside and switching the process state through communication between threads. In addition, maintaining this separate thread will occupy thread resources.

[0047] The present disclosure provides a method for process management. Figure 2 As shown, the communication between the event management process and the application process can be realized through the signal in the process communication mechanism, thereby reducing the power consumption of the system and reducing the occupation of thread resources in the application process.

[0048] Among them, after the event management process starts running, it waits for the low power control message or external event to be sent. When the low power control message is received, a stop signal is sent to the application process to make the application process enter the low power state. When the external event is sent, a start signal is sent to the application process to make the application process exit the low power state. The power consumption management of the application process is realized, and the power consumption of the system is reduced.

[0049] Combination Figure 3 As shown, the method for process management provided by the embodiment of the present disclosure includes:

[0050] S01, when the application process meets the low power consumption condition, the application process sends a low power consumption control message to the event management process, so that the event management process sends a stop signal.

[0051] S02, when receiving a stop signal, the application process enters a low power consumption state.

[0052] By adopting the method for process management provided by the embodiment of the present disclosure, the communication between the event management process and the application process can be realized through the signal in the process communication mechanism. When the application process meets the low power consumption condition, the running state of the application process can be switched by receiving the stop signal sent by the event management process, so that the application process enters the low power consumption state, thereby realizing the power consumption management of the application process and reducing the power consumption of the system. In addition, in the related art, the application process needs to maintain a separate thread for receiving external messages. The embodiment of the present disclosure does not need to modify the application process, does not occupy the thread resources of the application process, and improves the thread utilization rate of the application process. In addition, in the related art, the low power consumption scenario must be considered during the design process, and an independent thread needs to be written to control the running state of the process to realize power consumption management, and the application process is sensitive to the power consumption management mechanism. . The embodiment of the present disclosure directly switches the running state of the application process by receiving the stop signal sent by the event management process, so that the application process enters the low power consumption state. There is no need to consider the low power consumption scenario during the design process, and there is no need for communication between the threads of the application process during the power consumption management process. The application process can run normally before entering the low power consumption state, so that the application process is not sensitive to the power consumption management mechanism.

[0053] Optionally, sending the low power consumption control message to the event management process includes the application process sending the low power consumption control message to the event management process; or, the application process sending the low power consumption control message to the monitoring process, and the monitoring process forwarding the low power consumption control message to the event management process.

[0054] In this way, the low-power control message can be sent directly from the application process to the event management process, which simplifies the transmission path of the low-power control message, so that the low-power control message can be transmitted to the event management process more quickly, so that when the application process meets the low-power condition, the event management process can send a stop signal more quickly, thereby allowing the application process to enter a low-power state more quickly, further reducing the power consumption of the system. In addition, the low-power control message can also be first sent from the application process to the monitoring process, and then the monitoring process forwards the low-power control message to the event management process, and the message is forwarded through the monitoring process, which increases the transmission path of the low-power control message, so that when the low-power control message cannot be sent directly from the application process to the event management process, the low-power control message can still be transmitted to the event management process, so that the event management process can send a stop signal, thereby allowing the application process to enter a low-power state, realizing power consumption management of processes under different circumstances and reducing the power consumption of the system.

[0055] Optionally, satisfying the low power consumption condition includes the main thread of the application thread entering an idle state.

[0056] When the main thread enters the idle state, the application process does not need to continue to provide services to the user, but the remaining threads of the application process will continue to run in the background, occupying system resources and increasing the power consumption of the system. When the main thread enters the idle state, the application process needs to enter a low-power state to reduce the power consumption of the system. Therefore, when the main thread of the application process enters the idle state, the application process meets the low-power condition.

[0057] Optionally, receiving the stop signal includes: the event management process sending the stop signal to the application process; or, the event management process sending the stop signal to the monitoring process, and the monitoring process forwarding the stop signal to the application process.

[0058] In this way, the stop signal can be sent directly from the event management process to the application process, which simplifies the transmission path of the stop signal, so that the stop signal can be transmitted to the application process more quickly, so that the application process enters a low-power state more quickly, further reducing the power consumption of the system. In addition, the stop signal can also be first sent from the event management process to the monitoring process, and then the monitoring process forwards the stop signal to the application process, and the signal is transferred through the monitoring process, which increases the transmission path of the stop signal, so that when the stop signal cannot be sent directly from the event management process to the application process, the stop signal can still be transmitted to the application process, so that the application process enters a low-power state, realizing power consumption management of processes under different situations and reducing the power consumption of the system.

[0059] For example, in Linux systems, the stop signal is the SIGSTOP signal.

[0060] In the process communication mechanism, the SIGSTOP signal can suspend the running process. By sending the SIGSTOP signal to the application process through the event management process, the running application process can be suspended, so that the application process enters a low-power state, thereby realizing power consumption management of the application process and reducing the power consumption of the system. Furthermore, the SIGSTOP signal is sent by the event management process. After the application process receives the SIGSTOP signal, all threads of the application process suspend operation and enter a low-power state, and there is no need for threads to communicate with each other. After the application process receives the SIGSTOP signal, all threads are in normal operation. Therefore, the application process is unaware of power consumption management.

[0061] Optionally, the application process entering the low power consumption state includes pausing all threads of the application process.

[0062] The running of application process threads will occupy system resources and increase system power consumption. When the main thread of the application process enters the idle state, the application process needs to be managed so that the application process enters a low power consumption state. By pausing all threads of the application process, the running threads in the application process enter the paused state, so that the application process enters a low power consumption state, thereby reducing the system resource occupation and the system power consumption.

[0063] Optionally, the method for process management also includes the application process exiting the low power consumption state when an external event occurs.

[0064] Combination Figure 4 As shown, another method for process management provided by an embodiment of the present disclosure includes:

[0065] S11, when the low power consumption condition is met, the application process sends a low power consumption control message to the event management process, so that the event management process sends a stop signal.

[0066] S12, when the application process receives the stop signal, it enters a low power consumption state.

[0067] S13, when an external event occurs, the application process exits the low power consumption state.

[0068] In this embodiment, when the application process meets the low power consumption condition, it enters the low power consumption state through the stop signal sent by the event management process, which can realize the power consumption management of the application process and thus reduce the power consumption of the system. When the user needs to run the application process, the application process needs to exit the low power consumption state. After the external event occurs, the application process will exit the low power consumption state and continue to provide services to the user.

[0069] Optionally, the application process exiting the low power consumption state includes the application process resuming running all threads when receiving a start signal sent by the event management process.

[0070] After an external event occurs, the event management process sends a start signal. After receiving the start signal sent by the event management process, the application process resumes the operation of all threads, then exits the low power state and continues to provide services to users.

[0071] For example, when applied to Linux system, the start signal is SIGCONT signal.

[0072] In the process communication mechanism, the SIGCONT signal can resume the suspended process. When an external event occurs, the event management process sends a SIGCONT signal to the application process, which can resume the suspended application process and make the application process exit the low power state, thereby realizing power consumption management of the application process.

[0073] Optionally, the external event includes an external input event and a timing event.

[0074] For example, combining Figure 6 As shown, when the user needs the application process to resume operation, he can input a command through the keyboard to cause an external input event to occur, thereby causing the application process to exit the low power state and continue to provide services to the user. In addition, a timer can be set in the application process in advance as a timed event. When the application process enters the low power state for the set time, the timed event occurs, and the application process exits the low power state and continues to provide services to the user.

[0075] Optionally, the method for process management further includes determining, by the application process, whether a low power consumption condition is satisfied.

[0076] Combination Figure 5 As shown, another method for process management provided by an embodiment of the present disclosure includes:

[0077] S21, the application process detects the current running status.

[0078] S22, the application process determines whether the low power consumption condition is met.

[0079] S23, when the low power consumption condition is met, the application process sends a low power consumption control message to the event management process, so that the event management process sends a stop signal.

[0080] S24, when the application process receives the stop signal, it enters a low power consumption state.

[0081] S25, when an external event occurs, the application process exits the low power consumption state.

[0082] In this embodiment, the application process determines whether the low power consumption condition is met, so that the application process can timely determine the current running state. When the low power consumption condition is met, a low power consumption control message is sent to the event management process, so that the event management process sends a stop signal, and then the application process enters a low power consumption state when receiving the stop signal, thereby realizing power consumption management of the application process. Moreover, when the user needs to run the application process, the application process needs to exit the low power consumption state. After the external event occurs, the application process will exit the low power consumption state and continue to provide services to the user.

[0083] Combination Figure 7 As shown, the embodiment of the present disclosure provides a device 10 for process management, including a processor 100 and a memory 101. Optionally, the device 10 may also include a communication interface 102 and a bus 103. The processor 100, the communication interface 102, and the memory 101 may communicate with each other through the bus 103. The communication interface 102 may be used for information transmission. The processor 100 may call the logic instructions in the memory 101 to execute the method for process management of the above embodiment.

[0084] In addition, the logic instructions in the memory 101 described above may be implemented in the form of software functional units and when sold or used as independent products, may be stored in a computer-readable storage medium.

[0085] The memory 101 is a computer-readable storage medium that can be used to store software programs and computer executable programs, such as program instructions / modules corresponding to the methods in the embodiments of the present disclosure. The processor 100 executes functional applications and data processing by running the program instructions / modules stored in the memory 101, that is, implementing the method for process management in the above-mentioned embodiments.

[0086] The memory 101 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application required for at least one function; the data storage area may store data created according to the use of the terminal device, etc. In addition, the memory 101 may include a high-speed random access memory and may also include a non-volatile memory.

[0087] The embodiments of the present disclosure provide a computing device, including: a computing device body, and the above-mentioned device 10 for process management. The device 10 for process management is installed in the computing device body. The installation relationship described here is not limited to placement inside the computing device body, but also includes installation connections with other components of the computing device, including but not limited to physical connections, electrical connections, or signal transmission connections. It can be understood by those skilled in the art that the device 10 for process management can be adapted to a feasible computing device body, thereby realizing other feasible embodiments.

[0088] An embodiment of the present disclosure provides a computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions are configured to execute the above-mentioned method for process management.

[0089] The technical solution of the embodiment of the present disclosure can be embodied in the form of a software product, which is stored in a storage medium and includes one or more instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in the embodiment of the present disclosure. The aforementioned storage medium may be a non-transient storage medium, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, and other media that can store program codes.

[0090] The above description and the accompanying drawings fully illustrate the embodiments of the present disclosure so that those skilled in the art can practice them. Other embodiments may include structural, logical, electrical, process and other changes. The embodiments represent only possible changes. Unless explicitly required, separate components and functions are optional, and the order of operation may vary. The parts and features of some embodiments may be included in or replace the parts and features of other embodiments. Moreover, the words used in this application are only used to describe the embodiments and are not used to limit the claims. As used in the description of the embodiments and the claims, unless the context clearly indicates, the singular forms of "a", "an" and "the" are intended to include plural forms as well. Similarly, the term "and / or" as used in this application refers to any and all possible combinations of listings containing one or more associated ones. In addition, when used in the present application, the term "comprise" and its variants "comprises" and / or comprising refer to the presence of stated features, wholes, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or groups thereof. In the absence of further restrictions, the elements defined by the sentence "comprising a ..." do not exclude the presence of other identical elements in the process, method or device comprising the elements. In this article, each embodiment may focus on the differences from other embodiments, and the same and similar parts between the various embodiments may refer to each other. For the methods, products, etc. disclosed in the embodiments, if they correspond to the method part disclosed in the embodiments, then the relevant parts can refer to the description of the method part.

[0091] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software may depend on the specific application and design constraints of the technical solution. The technicians may use different methods for each specific application to implement the described functions, but such implementations should not be considered to exceed the scope of the embodiments of the present disclosure. The technicians may clearly understand that, for the convenience and simplicity of description, the specific working processes of the systems, devices and units described above may refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here.

[0092] In the embodiments disclosed herein, the disclosed methods and products (including but not limited to devices, equipment, etc.) can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units can be only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between each other shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms. The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to implement this embodiment. In addition, each functional unit in the embodiment of the present disclosure may be integrated in a processing unit, or each unit may exist physically alone, or two or more units may be integrated in one unit.

[0093] The flowchart and block diagram in the accompanying drawings show the possible architecture, function and operation of the system, method and computer program product according to the embodiment of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of the code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. In some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, which can depend on the functions involved. In the description corresponding to the flowchart and the block diagram in the accompanying drawings, the operations or steps corresponding to different boxes can also occur in a different order from the order disclosed in the description, and sometimes there is no specific order between different operations or steps. For example, two consecutive operations or steps can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, which can depend on the functions involved. Each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented by a dedicated hardware-based system that performs the specified functions or actions, or may be implemented by a combination of dedicated hardware and computer instructions.

Claims

1. A method for process management, characterized in that: include: When the low power consumption condition is met, a low power consumption control message is sent to the event management process so that the event management process sends a stop signal; Upon receiving a stop signal, the application process enters a low power state.

2. The method according to claim 1, characterized in that: Send low power control messages to the event management process, including: The application process sends a low power consumption control message to the event management process; or, The application process sends a low power consumption control message to the monitoring process, and the monitoring process forwards the low power consumption control message to the event management process.

3. The method according to claim 1, characterized in that: Meeting the low power consumption conditions includes: The main thread of the application thread enters the idle state.

4. The method according to claim 1, characterized in that: A stop signal is received, including: The event management process sends a stop signal to the application process; or, The event management process sends a stop signal to the monitoring process, and the monitoring process forwards the stop signal to the application process.

5. The method according to claim 1, characterized in that The application process enters a low power state, including: Pause all threads of the application process.

6. The method according to any one of claims 1 to 5, characterized in that: Also includes: When an external event occurs, the application process exits the low power state.

7. The method according to claim 6, characterized in that The application process exits the low power state, including: When the application process receives the start signal sent by the event management process, it resumes running all threads.

8. A device for process management, comprising a processor and a memory storing program instructions, characterized in that: The processor is configured to execute the method for process management according to any one of claims 1 to 7 when running the program instructions.

9. A computing device, characterized in that include: Computing device body; The apparatus for process management as claimed in claim 8 is installed in the computing device body.

10. A computer-readable storage medium storing program instructions, characterized in that: When the program instructions are executed, the computer is configured to execute the method for process management according to any one of claims 1 to 7.

Images