Process management and control method, process management and control apparatus, electronic device, and storage medium

Abstract

The embodiments of the present application disclose a process management and control method, a process management and control apparatus, an electronic device, and a storage medium. The process management and control method comprises: determining a usage scenario on the basis of interaction data between a process and a system core service; and performing management and control processing on the process on the basis of the usage scenario and a management and control policy. The process management and control method provided in certain embodiments of the present application can perform more flexible process management and control on the basis of a usage scenario.

Description

Process management methods, process management devices, electronic devices and storage media

[0001] This application claims priority to Chinese Patent Application No. 202510205911.6, filed on February 24, 2025, entitled “Process Control Method, Process Control Device, Electronic Device and Storage Medium”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This specification relates to the field of computer technology, specifically to a process management method, a process management device, an electronic device, and a storage medium. Background Technology

[0003] Currently, terminal devices typically run multiple applications to meet users' diverse functional needs. However, running multiple applications simultaneously consumes CPU resources and increases power consumption. Therefore, terminal devices usually need to manage background processes. In related technologies, the background process management strategies of various systems are not yet perfect. They often simply freeze background processes to improve system performance and reduce power consumption. However, this method is prone to errors during freezing, affecting user experience, and the reliability of process freezing management is low. Technical solutions

[0004] This application provides a process management method, process management device, electronic device, and storage medium, which can perform more flexible process management based on the usage scenario.

[0005] In a first aspect, embodiments of this application provide a process management method, including: determining a usage scenario based on interaction data between a process and a core system service; and managing the process based on the usage scenario and management strategy.

[0006] In some implementations, processes are managed based on usage scenarios and management strategies, including: determining the management strategy corresponding to the usage scenario; and freezing or unfreezing the process based on the management strategy corresponding to the usage scenario.

[0007] In some implementations, the control strategy includes determining the freeze duration based on the interaction frequency in the usage scenario, where the higher the interaction frequency, the shorter the freeze duration.

[0008] In some implementations, the control strategy includes determining the priority of freezing or unfreezing based on at least one of the application type, system resource status, or system usage status in the usage scenario.

[0009] In some implementations, processes are managed based on usage scenarios and management strategies, including: monitoring changes in usage scenarios; and managing changes in usage scenarios.

[0010] In some implementations, the use case is determined based on the interaction data between the process and the core system services, including: determining the process label of the process based on the interaction data; and determining the use case based on the process label.

[0011] In some implementations, the use case is determined based on the process tag, including: if the process tag matches the process tag corresponding to the preset scenario, the use case is determined to be the preset scenario.

[0012] Secondly, embodiments of this application provide a process management device, including: a scenario determination module, used to determine the usage scenario based on the interaction data between the process and the core services of the system; and a process management module, used to manage and control the process based on the usage scenario and management strategy.

[0013] Thirdly, embodiments of this application provide an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to perform the operations described in the first aspect.

[0014] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, performs the operations described in the first aspect.

[0015] In summary, embodiments of this application disclose a process management method, a process management device, an electronic device, and a storage medium. The process management method includes: determining the usage scenario based on interaction data between the process and core system services; and managing the process based on the usage scenario and management strategies. Some embodiments of this application provide process management methods that enable more flexible process management based on usage scenarios. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in the embodiments of this specification, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0017] Figure 1 shows a flowchart of a process control method provided in some embodiments of this application;

[0018] Figure 2 shows a flowchart of a process control method provided in some other embodiments of this application;

[0019] Figure 3 shows an example diagram of the module architecture for process management provided in some embodiments of this application;

[0020] Figure 4 illustrates a flowchart of determining a use case according to some embodiments of this application;

[0021] Figure 5 illustrates an example of process management in a desktop application startup scenario provided by some embodiments of this application;

[0022] Figure 6 shows a schematic diagram of the structure of a process management device provided in some embodiments of this application;

[0023] Figure 7 shows a schematic diagram of the structure of an electronic device provided in some embodiments of this application.

[0024] Implementation methods of this application

[0025] The technical solutions of this application will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0026] Figure 1 shows a flowchart of a process control method provided in some embodiments of this application. Although a logical order is shown in the flowchart, in some cases, the operations shown or described may be performed in a different order than that shown in the figures. The specific flow of the process control method can be as follows:

[0027] S101. Determine the usage scenario based on the interaction data between processes and core system services.

[0028] The core system services are components within the operating system that provide basic functions and services, and are crucial for the system's operation. Taking Android as an example, core system services may include, but are not limited to, activity management, installation package management, notification management, communication management, location management, sensor management, window management, input management, audio and video management, battery management, and network connection management.

[0029] Here, a process can be a system process or a process within an application, and a process can include one or more processes. For example, a process can be a media service process, providing basic services for audio and video playback. For example, a process can be a Bluetooth service process, managing Bluetooth connections and communication. For example, a process can be a browser application process; during browser usage, one or more processes are launched to handle page loading, multimedia playback, and other functions. As another example, a process can be a music player process; during music player usage, one or more processes can be launched to handle audio playback, Bluetooth connection, and other functions.

[0030] Interaction data is generated during the interaction between a process and the system's core services. This interaction can include, but is not limited to, communicating with the system's core services, calling a system service, or exchanging data or instructions with a system service. In some embodiments, the interaction data between a process and the system's core services can be obtained through source code instrumentation.

[0031] The usage scenario can reflect a user's operational behavior or purpose. For example, a usage scenario could be downloading an application, browsing within an application, playing audio or video, or playing a game. User operations are achieved through interactions between processes and core system services; therefore, by collecting and analyzing interaction data, user operations can be determined, and thus the usage scenario can be identified.

[0032] How to determine use cases based on interaction data will be described in detail later.

[0033] S102. Based on the usage scenario and management strategy, manage and control the process.

[0034] The control strategy can be used to manage processes for different usage scenarios. In some embodiments, the control strategy can be based on manually preset rules. Manually designed rules are more interpretable and suitable for usage scenarios with stable patterns and predictability. For example, for specific types of usage scenarios, the resource consumption of background processes can be limited. In other embodiments, the control strategy can also be based on the parameter design of machine learning or deep learning models. Compared with manually designed rules, machine learning or deep learning-driven strategies can better handle complex patterns and personalized usage scenarios. For example, the control strategy can be continuously optimized based on user feedback to make it more in line with users' personalized usage habits.

[0035] Figure 2 illustrates a flowchart of a process control method provided in some other embodiments of this application. Although a logical order is shown in the flowchart, in some cases, the operations shown or described may be performed in a different order than that shown in the figures. In some embodiments, operation S102 may include:

[0036] S201. Based on the usage scenario, determine the corresponding control strategy.

[0037] Different management strategies can be used for different use cases. By implementing targeted process management for different use cases, process management can be made more targeted and flexible.

[0038] S202. Based on the control strategy corresponding to the usage scenario, freeze or unfreeze the process.

[0039] For example, while music is playing, a user launches another application on the desktop, such as application A. This use case is that the user is using application A in the foreground while music is playing in the background. Based on this use case, the corresponding control strategy is to not freeze or restrict the background music playback process to avoid music playback interruptions. However, if the user manually pauses the music or the music has finished playing and playback has stopped, and the user launches another application on the desktop, such as application A, then the use case is that the user is using application A in the foreground. Based on this use case, the corresponding control strategy is to freeze or restrict the background music playback process.

[0040] For example, after the phone screen remains off for a period of time, it can be considered that the usage scenario is inactive. At this time, the control strategy can be: freeze the process of instant messaging applications, and when a network message notification arrives, temporarily unfreeze the process and notify the user in a timely manner; if the user does not check the phone, freeze the instant messaging application again after a few seconds until the next network message arrives, triggering the temporary unfreezing of the process.

[0041] The process management method provided in this application includes: determining the usage scenario based on the interaction data between the process and the core system services; and managing the process based on the usage scenario and management strategy. Some embodiments of this application provide a process management method that enables more flexible process management based on the usage scenario.

[0042] Figure 3 illustrates an example of a module architecture for process management provided in some embodiments of this application. As shown in Figure 3, the module architecture may include an application layer, a system framework layer, a system runtime library layer, and a kernel layer.

[0043] The application layer can intuitively showcase usage scenarios through user interactions with the application. Examples include application launch, application exit, download, audio / video playback, application installation, application switching, and application swiping.

[0044] The system framework layer includes a core system service module, a scene recognition module, and a process freezing module. In the use cases described above, processes all need to interact with the core system services. For example, application startup involves interaction with services such as activity management, window management, and the display system. Application installation involves interaction with the installation package management service. Application swiping involves interaction with the view system and display system. Watching short videos involves interaction with the audio and video system.

[0045] The scene recognition module can collect interaction data during the interaction between processes and core system services through source code instrumentation. This data is then aggregated and integrated to complete scene recognition based on fragmented behaviors during the interaction. In some embodiments, the process / application tag recognition module can determine the process tag of a process or the application tag of an application based on the interaction data, and determine the usage scenario based on the process / application tag. The scene registration module determines whether the identified scenario is a preset scenario. The scene distribution module notifies the scene listening module in the system framework layer of the identified usage scenario.

[0046] The process freezing module can monitor scene identification information through the scene monitoring module, and the freeze / unfreeze decision module can determine whether to freeze or unfreeze a process based on the control strategy, thereby achieving the desired process control effect under a specified scene. In some embodiments, the process freezing module can monitor changes in the usage scene and perform control processing when the usage scene changes. For example, when the process label is "created," it can be determined that the current usage scene is a process startup scene. When the process label is "visible," it can be determined that the current usage scene is a process startup completion scene. In the process startup scene, background processes can be frozen for a short time. In the process startup completion scene, background processes that have been frozen for a short time can be unfrozen.

[0047] The system runtime library layer may include dependency libraries for the Android system runtime. This layer may include a freeze execution module to perform freeze or unfreeze operations based on information from the process freeze function module. The kernel layer may be used for kernel scheduling, including kernel freeze capabilities. In some embodiments, the freeze execution module may add freeze or unfreeze flags to a process based on the decision result of the freeze / unfreeze decision module, causing the process to enter kernel mode via a terminal, and adding a pending signal state. For a frozen process, when the above interrupt execution is completed and the process returns from kernel mode to user mode, the CPU resources of the process are yielded in the scheduler based on the pending signal. For a unfrozen process, the freeze flag is cleared, the frozen process is woken up, and a suitable CPU core is selected for execution.

[0048] It should be noted that the module architecture example shown in Figure 3 is only an example illustration, and other module architectures that use the process control method in this application are also within the protection scope of this application.

[0049] Next, we will introduce how to determine the use cases based on interaction data.

[0050] Figure 4 illustrates a flowchart of determining a use case according to some embodiments of this application. Although a logical order is shown in the flowchart, in some cases, the operations shown or described may be performed in a different order than those shown in the figures. In some embodiments, the specific process for determining a use case based on interaction data may be as follows:

[0051] S401. Determine the process label of the process based on the interaction data.

[0052] Process tags can be used to indicate the state of a process or the user action corresponding to that process. A process can have one or more tags. Process tags can include one or more dimensions. Process tags can be pre-set tags. For example, if the interaction data is the data that started the process, then a "created" tag can be added to the process. For example, based on whether the process is visible, a "visible / invisible" tag can be added to the process. For example, based on whether the process uses mobile data, a "using mobile data / not using mobile data" tag can be added to the process. Another example is based on the application installation status of the process, a "background application installation / application installation complete" tag can be added to the process. Process tags can also include other setting methods; this application does not limit the setting method of process tags.

[0053] S402. Determine whether the process label matches the process label corresponding to the preset scenario.

[0054] As mentioned above, in some embodiments, the scenario registration module can pre-define some usage scenarios and their corresponding process tags. For example, for a usage scenario of listening to music using a Bluetooth connection, the corresponding process tags could be "Bluetooth connection" and "music playback". For example, for a usage scenario of navigating using a map, the corresponding process tags could be "GPS positioning" and "voice broadcast". For yet another example, for a usage scenario of browsing information using social media software, the corresponding process tags could be "social media application", "visible", and "swipe application".

[0055] If the process label matches the process label corresponding to the preset scenario, execute operation S403.

[0056] S403. Determine the usage scenario as the preset scenario.

[0057] In some embodiments, when the scene monitoring module detects a process tag that matches a process tag corresponding to a preset scene, it determines the specific scene corresponding to the current usage scene based on the scene registration information. For example, after detecting the tags "visible" and "swipe application", the scene registration module determines that the current usage scene is browsing information using social media software based on the preset scene.

[0058] The process management method provided in some embodiments of this application can determine the process tag of a process based on the interaction data between the process and the core system services. Furthermore, it can determine the usage scenario based on the process tag. The method provided in this embodiment can more accurately identify usage scenarios and achieve precise limitation of CPU resources.

[0059] Next, we will provide a detailed introduction to the control strategy.

[0060] In some embodiments, the control strategy can be to determine the freeze duration based on the interaction frequency in the usage scenario. The higher the interaction frequency, the shorter the freeze duration.

[0061] For example, in scenarios involving high-frequency interactions or short-duration operations, the management strategy is short-term freezing. For instance, when a user launches an application by clicking a desktop icon or switches between applications, some background application processes can be briefly frozen to limit their resource usage. The application launch or switching operation is considered a short-duration action, and the restriction on background processes is lifted after the operation ends. Another example is in scenarios where users frequently swipe within an application, with each swipe being a short-duration action. When frame drops or stuttering occur during swiping, a short-term freezing operation can also be used to limit the CPU resource usage of processes affecting the foreground swipe frame rate, thus making the foreground swipe operation smoother.

[0062] For example, in scenarios with low-frequency interaction or background operation, the management strategy is to freeze the application for an extended period. For instance, in a scenario where a user switches the first application to the background and then switches the second application to the foreground, the first application's process is still active in the background. Without affecting the use of the second application in the foreground, the first application's process can be frozen for an extended period, releasing the CPU resources it occupies. When the user wants to use the first application again, i.e., switches it back to the foreground, it can be unfrozen to respond to the user's interaction.

[0063] In some embodiments, the control strategy may be to determine the priority of freezing or unfreezing based on one or more of the application type, system resource status, or system usage status in the usage scenario.

[0064] The application types can include, but are not limited to, instant messaging, music, video, navigation, news, and games. System resource status can include, but is not limited to, CPU resource usage and memory usage. System usage status can include, but is not limited to, screen on / off status, battery level, navigation status, audio / video playback status, and network connection status.

[0065] For example, in a scenario where a user uses a navigation app for navigation, and then switches the navigation app to the background while bringing other apps to the foreground, the navigation app's process remains active in the background. However, due to the app type (navigation) and the system's usage state (navigation state), even though the navigation app has been switched to the background, its freezing priority is still lower than other processes. Therefore, the navigation app's process is not frozen unless it affects the use of foreground apps.

[0066] For example, consider a scenario where a user is browsing a news app in the foreground and using a navigation app in the background, then turns off the phone screen. The system's current state (screen off) and the app type (news app, navigation app) determine that, although the news app is in the foreground and the navigation app is in the background, the news app's process will be frozen with higher priority than the navigation app's process. In cases of resource scarcity, the news app's process will be frozen or restricted first.

[0067] The process control methods provided in some embodiments of this application can employ targeted control strategies for different use scenarios, making process restrictions in different scenarios more flexible and targeted.

[0068] Figure 5 illustrates an example of process management in a desktop application launch scenario provided by some embodiments of this application. This example uses the scenario of launching an application by clicking an icon on the terminal device's desktop as an example to illustrate the process management process.

[0069] When a user clicks an icon on the terminal device's desktop, an input event is generated at the hardware layer. The input system at the system framework layer can then pass the input event to the corresponding application layer program for processing (the input event is passed to the terminal device's desktop application when the application is launched), executing the application's startup logic.

[0070] When a desktop application on a terminal device receives an input event, if the event type is "press and release," it considers the user's action to be a click. It then executes the control logic to launch the clicked application. The desktop application then passes the application launch information to the system's core services. At this point, the application process management service creates a task process, the activity management service creates application activity information, and the window management service performs window switching operations, etc.

[0071] Interactive data (data flow information) from these system services can be passed to the scene recognition function via source code instrumentation, adding tag information to applications and / or processes. For example, the data flow during the startup process can add a "created" tag to the application and / or process. Similarly, when the target application window is visible, a "visible" tag can be added to the application and / or process. In other embodiments, instead of setting separate application tags, process tags can be added only to the processes within the application.

[0072] Once the application and / or process tags are identified, the scenario recognition module determines the current usage scenario. Specifically, the "Created" tag indicates the current scenario is a process / application startup scenario. When the process / application tag is "Visible," the current scenario indicates the process / application has completed startup. The scenario recognition module promptly sends the usage scenario information to registered modules that are monitoring these scenario changes.

[0073] Because the process freezing module registers and monitors changes in certain scenarios, the freeze and unfreeze decision module can execute freeze or unfreeze operations based on these changes. This is achieved by sending freeze or unfreeze signals through the freeze / unfreeze execution module in the system runtime library, ultimately resulting in the kernel-level scheduler restricting or lifting the restrictions. For example, in the scenario of starting a process / application, a background process can be frozen for a short period. Similarly, in the scenario of a process / application completing its startup, a background process that has been frozen for a short time can be unfrozen.

[0074] In summary, the process management methods provided in some embodiments of this application can dynamically add and remove tags for applications and / or processes by instrumenting the source code of various core system services at the system framework layer. The scenario recognition module can identify the current user scenario based on changes in the state of application tags and / or process tags, and simultaneously send the scenario to other modules registered to listen to that scenario (e.g., the process freezing function module). The process freezing function can decide whether to send a freeze or unfreeze signal according to the module's preset management strategy. Finally, the kernel scheduler restricts or removes restrictions on the process based on the signal type.

[0075] Figure 6 shows a schematic diagram of the structure of a process management device provided in some embodiments of this application. The process management device 600 may include:

[0076] The scenario determination module 601 is used to determine the usage scenario based on the interaction data between the process and the core system services.

[0077] The process management module 602 is used to manage and control processes based on usage scenarios and management strategies.

[0078] The process management device 600 provided in some embodiments of this application can determine the usage scenario based on the interaction data between the process and the core system services by the scenario determination module 601. Next, the process management device 600 can perform process management based on the usage scenario and management strategy by the process management module 602. The process management device 600 provided in some embodiments of this application can perform more flexible process management based on the usage scenario.

[0079] In some embodiments, the process management module 602 may include a first determining unit and a first managing unit. The first determining unit may be used to determine a management policy corresponding to a usage scenario. The first managing unit may be used to freeze or unfreeze a process based on the management policy corresponding to the usage scenario.

[0080] In some embodiments, the control strategy may include: determining the freeze duration based on the interaction frequency in the usage scenario, wherein the higher the interaction frequency, the shorter the freeze duration.

[0081] In some embodiments, the control policy may include determining the priority of freezing or unfreezing based on at least one of the application type, system resource status, or system usage status in the usage scenario.

[0082] In some embodiments, the process management module 602 may include a monitoring unit and a second management unit. The monitoring unit can be used to monitor changes in the usage scenario. The second management unit can be used to perform management and control processes when the usage scenario changes.

[0083] In some embodiments, the scenario determination module 601 may include a second determination unit and a third determination unit. The second determination unit may be used to determine a process tag of a process based on interaction data. The third determination unit may be used to determine a usage scenario based on the process tag.

[0084] In some embodiments, the third determining unit may be the first determining subunit. The first determining subunit may be used to determine that the usage scenario is a preset scenario when the process tag matches the process tag corresponding to the preset scenario.

[0085] In addition, this application also provides an electronic device. Figure 7 shows a schematic diagram of the structure of an electronic device provided in some embodiments of this application. Specifically:

[0086] The electronic device 700 may include components such as a processor 701 with one or more processing cores, and a memory 702 with one or more computer-readable storage media. Those skilled in the art will understand that the structure of the electronic device 700 shown in FIG. 7 does not constitute a limitation on the electronic device, and it may include more or fewer components than shown, or combine certain components, or have different component arrangements. Wherein:

[0087] The processor 701 is the control center of the electronic device 700. It connects various parts of the electronic device 700 via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 702, and by calling data stored in the memory 702, it performs various functions and processes data of the electronic device 700, thereby providing overall monitoring of the electronic device 700. Optionally, the processor 701 may include one or more processing cores; preferably, the processor 701 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the modem processor may also not be integrated into the processor 701.

[0088] The memory 702 can be used to store software programs and modules. The processor 701 executes various functional applications and data processing by running the software programs and modules stored in the memory 702. The memory 702 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function, etc.; the data storage area may store data created based on the use of the electronic device 700, etc. In addition, the memory 702 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the memory 702 may also include a memory controller to provide the processor 701 with access to the memory 702.

[0089] Specifically in this embodiment, the processor 701 in the electronic device 700 will load the executable files corresponding to the processes of one or more applications into the memory 702 according to the following instructions, and the processor 701 will run the applications stored in the memory 702, thereby realizing the operation in any of the process management methods provided in this application embodiment.

[0090] The specific process of the process control method executed by the electronic device 700 can be referred to the description in Figure 1, Figure 3 or Figure 4, and will not be repeated here.

[0091] Those skilled in the art will understand that all or part of the operations in the various methods of the above embodiments can be performed by instructions, or by instructions controlling related hardware. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0092] Therefore, this application provides a computer-readable storage medium storing a computer program that can be loaded by a processor to perform operations in any of the process control methods provided in this application.

[0093] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0094] The computer-readable storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0095] Since the instructions stored in the computer-readable storage medium can execute the operations in any of the process control methods provided in this application, the beneficial effects that any of the process control methods provided in this application can achieve can be realized, as detailed in the preceding embodiments, and will not be repeated here.

[0096] The above provides a detailed description of the process management method, process management device, electronic device, and storage medium provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A process management method, wherein, include: Based on the interaction data between processes and core system services, determine the use cases; as well as Based on the aforementioned usage scenarios and management strategies, the process is managed and controlled.

2. The method as described in claim 1, wherein, The process control and management based on the usage scenario and control strategy includes: Based on the aforementioned usage scenario, determine the corresponding control strategy for that usage scenario; and Based on the control strategy corresponding to the usage scenario, the process can be frozen or unfrozen.

3. The method as described in claim 2, wherein, The control strategy includes: The freeze duration is determined based on the interaction frequency in the usage scenario, wherein the higher the interaction frequency, the shorter the freeze duration.

4. The method of claim 2, wherein, The control strategy includes: The priority of freezing or unfreezing is determined based on at least one of the application type, system resource status, or system usage status in the described use case.

5. The method of claim 1, wherein, The process control and management based on the usage scenario and control strategy includes: Monitor changes in the aforementioned use cases; and The aforementioned control and management process will be implemented if the usage scenario changes.

6. The method of claim 1, wherein, The use cases are determined based on the interaction data between processes and core system services, including: The process label of the process is determined based on the interaction data; and The usage scenario is determined based on the process tag.

7. The method of claim 6, wherein, The process of determining the use case based on the process tag includes: If the process tag matches the process tag corresponding to the preset scenario, the usage scenario is determined to be the preset scenario.

8. A process control device, wherein, include: The scenario determination module is used to determine the usage scenario based on the interaction data between processes and core system services; as well as The process management module is used to manage and control the process based on the usage scenario and management strategy.

9. The process control device as described in claim 8, wherein, The process management module manages the process based on the usage scenario and management strategy, including: Based on the aforementioned usage scenario, determine the corresponding control strategy for that usage scenario; and Based on the control strategy corresponding to the usage scenario, the process can be frozen or unfrozen.

10. The process control device according to claim 9, wherein, The control policies in the process management module include: The freeze duration is determined based on the interaction frequency in the usage scenario, wherein the higher the interaction frequency, the shorter the freeze duration.

11. The process control device according to claim 9, wherein, The control policies in the process management module include: The priority of freezing or unfreezing is determined based on at least one of the application type, system resource status, or system usage status in the described use case.

12. The process control device according to claim 8, wherein, The process management module manages the process based on the usage scenario and management strategy, including: Monitor changes in the aforementioned use cases; and The aforementioned control and management process will be implemented if the usage scenario changes.

13. The process control device according to claim 8, wherein, The scenario determination module determines the usage scenario based on the interaction data between the process and the core system services, including: The process label of the process is determined based on the interaction data; and The usage scenario is determined based on the process tag.

14. The process control device according to claim 13, wherein, The scenario determination module determines the usage scenario based on the process tag, including: If the process tag matches the process tag corresponding to the preset scenario, the usage scenario is determined to be the preset scenario.

15. An electronic device, wherein, It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, performs the operations described in any one of claims 1-7.

16. A computer-readable storage medium, wherein, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the operations described in any one of claims 1-7.

Images