CN116028207A - Scheduling policy determination method, device, equipment and storage medium - Google Patents

Abstract

The present application discloses a scheduling policy determination method, device, equipment and storage medium, belonging to the technical field of computers. The method includes: determining the current user scene, power state, and system load of the electronic device, obtaining a first key value corresponding to the user scene, a second key value corresponding to the power state, and a third key value corresponding to the system load, according to the first key value The first key value, the second key value and the third key value determine the target key value. The scheduling strategy corresponding to the target key value is obtained from the corresponding relationship between the key value and the scheduling strategy. The reference factors for determining the scheduling strategy in this application are relatively comprehensive, so the subsequent resource scheduling based on the scheduling strategy can accurately realize the reasonable allocation of resources for electronic devices, so as to not only meet the needs of users, but also take into account the needs of the electronic devices themselves. The system requirements can further ensure the stable operation of the electronic equipment while reducing the energy consumption of the electronic equipment and improving the battery life of the electronic equipment.

Description

Scheduling strategy determination method, device, equipment and storage medium

This application claims the priority of the Chinese patent application with the application number 202210529304.1 and the application name "Scheduling Strategy Determination Method" filed on May 16, 2022, the entire contents of which are incorporated in this application by reference.

technical field

The present application relates to the field of computer technology, and in particular to a method, device, device and storage medium for determining a scheduling policy.

Background technique

With the improvement of the performance of electronic equipment, the power consumption of electronic equipment is also getting higher and higher, but the battery capacity is increased very slowly, resulting in the battery life of electronic equipment cannot meet the needs of users, reducing the user experience. For this reason, it is necessary to perform precise resource scheduling on the electronic device, so as to satisfy the user's long battery life experience while ensuring the performance of the electronic device.

At present, when performing resource scheduling on electronic devices, the corresponding scheduling strategy is determined according to the application program that the electronic device is running, and resource scheduling is performed according to the scheduling strategy, in order to reduce the resource requirements while the performance of the electronic device meets the resource requirements of the application program. Reduce the energy consumption of electronic equipment and improve the battery life of electronic equipment.

However, the above method only considers the running application program of the electronic device when performing resource scheduling, which is relatively limited, and cannot accurately realize a reasonable allocation of resources of the electronic device.

Contents of the invention

The present application provides a method, device, device and storage medium for determining a scheduling strategy, which can realize accurate and reasonable allocation of resources of electronic devices. The scheme is as follows:

In a first aspect, a method for determining a scheduling strategy is provided, in which method, the current user scenario of the electronic device is determined, and the power state and system load of the electronic device are determined. Afterwards, obtain the first key value corresponding to the user scenario, obtain the second key value corresponding to the power state, obtain the third key value corresponding to the system load, and determine the target according to the first key value, the second key value and the third key value key value. In the corresponding relationship between the key value and the scheduling policy, the scheduling policy corresponding to the target key value is obtained. The scheduling strategy is used for resource scheduling of the electronic device.

In this application, the reference factors for determining the scheduling strategy are relatively comprehensive, so the subsequent resource scheduling for electronic devices based on the scheduling strategy can accurately achieve a reasonable allocation of resources for electronic devices, so that not only can meet user needs, but also can take into account The system requirements of the electronic equipment itself can further ensure the stable operation of the electronic equipment while reducing the energy consumption of the electronic equipment and improving the battery life of the electronic equipment. Moreover, in this application, various reference factors are converted into corresponding key values, and then the corresponding scheduling strategy is directly obtained according to the key values. The operation process is simple, which can reduce system processing pressure and further ensure the stable operation of electronic equipment.

Optionally, the operation of determining the current user scenario of the electronic device may be: acquiring application running information of the electronic device, and determining the user scenario according to the application running information.

The application running information may include focus application information, and may further include application information such as non-focus application information and background application information. In this application, the application information of an application may include the application name, application type, application running status, etc. of the application.

The user scenario refers to the usage scenario of the user, that is, what the user is doing with the electronic device. This user scenario can reflect user needs. Since the user often uses various applications installed in the electronic device when using the electronic device, the user scenario can be determined according to the application running information in this application, and the determined user scenario is relatively accurate.

As an example, the operation of determining the user scenario according to the application running information may be: determining the main scenario according to the application type in the focused application information; Information and the background application information, determine at least one sub-scene; select a sub-scene with the highest priority from the at least one sub-scene, and the main scene and the selected sub-scene are user scenes.

The priority of each sub-scene can be set in advance in the electronic device, and the priority of each sub-scene can be set in advance by the technician according to the usage requirements. For example, the technician can set each The priority of the sub-scenes, the greater the impact on the battery life of the electronic device, the higher the priority, and the smaller the impact on the battery life of the electronic device, the lower the priority.

In this way, after at least one sub-scene is determined according to the main scene, the application running state in the focused application information, the non-focused application information, and the background application information, a sub-scene with the highest priority can be selected, so that the following can be based on This sub-scenario determines the most reasonable scheduling strategy to maximize the battery life of electronic devices.

As another example, system operating status may also be detected. In this case, the operation of determining the user scenario according to the application running information may be as follows: if the system working state is changed to an idle state, when the application running information indicates that the applications are not in use by the user, determine that the user scenario is idle Scenes.

The system working state refers to the current working state of the system, which can be divided into idle state and other states. The idle state refers to a state in which the system has not been operated by a user for a long time.

The user scene is an idle scene, which means that the user is not currently using the electronic device (that is, not operating and not using the application), and accordingly a scheduling strategy applicable to this situation can be subsequently determined.

As yet another example, the operation of determining the user scenario according to the application running information may be: acquiring IO load information, and determining the user scenario according to the application running information and the IO load information.

The IO load information is used to reflect the IO load status. Exemplarily, the IO load information may include an IO time ratio, and the IO time ratio refers to a time ratio used for IO operations in a period, that is, indicates what percentage of a second is used for IO operations. The IO time ratio can reflect the level of IO load. That is, the higher the IO time ratio, the higher the IO load; the lower the IO time ratio, the lower the IO load.

In this application, user behavior can be inferred based on IO load information, which in turn helps to determine user scenarios. For example, if the persistence of the IO load information is above 30%, it can be considered that the user is copying files; or, if the persistence of the IO load information is between 10% and 30%, it can be considered that the user is decompressing files.

Optionally, the power state includes a power mode and a power plan, and the operation of determining the power state of the electronic device may be: if a power mode change event and a power plan change event are detected, then according to the power mode change event and the power plan Change events determine the state of the power supply.

During the operation of the electronic device, if the power mode changes, a power mode change event will be triggered, and the power mode change event is used to indicate the latest power mode after the change. During the operation of the electronic device, if the power plan changes, a power plan change event will be triggered, and the power plan change event is used to indicate the latest power plan after the change. In this way, the power state can be quickly and accurately determined according to the power mode change event and the power plan change event.

Optionally, according to the first key value, the second key value and the third key value, the operation of determining the target key value may be: concatenating the first key value, the second key value and the third key value to obtain the target key value value. For example, the first key value, the second key value and the third key value can be spliced according to the preset splicing method, for example, the second key value can be spliced at the end of the first key value, and then the third key value value is concatenated at the end of the second key value to obtain the target key value.

Optionally, if any one or more of the user scenario, the power state, and the system load changes, re-execute the acquisition of the first key value corresponding to the user scenario, and the acquisition of the second key value corresponding to the power state. value, and the step of obtaining the third key value corresponding to the system load and subsequent steps. That is, re-determine the key values corresponding to the three, and splicing the key values corresponding to the three to obtain the target key value, and re-determine the scheduling strategy accordingly. In this way, it can be ensured that the determined scheduling strategy can adapt to the latest state of the electronic device, so that the resource allocation of the electronic device can be accurately and reasonably allocated according to the scheduling strategy.

In this application, the current user scene, power state and system load of the electronic device can be continuously determined during the operation of the electronic device, that is, the user scene, power state and system load can be dynamically identified, and based on the Changes in the user scenario, the power supply status and the system load dynamically determine the scheduling strategy, and dynamically optimize resources accordingly.

In a second aspect, a scheduling strategy determining device is provided, and the scheduling strategy determining device has a function of realizing the behavior of the scheduling strategy determining method in the above first aspect. The device for determining a scheduling policy includes at least one module, and the at least one module is configured to implement the method for determining a scheduling policy provided in the first aspect above.

The third aspect provides a dispatching policy determination device, the structure of the dispatching policy determination device includes a processor and a memory, and the memory is used to store and support the dispatching policy determination device to perform the dispatching policy determination provided in the first aspect above The program of the method, and stores the data involved in implementing the method for determining the scheduling strategy described in the first aspect above. The processor is configured to execute programs stored in the memory. The scheduling policy determination device may further include a communication bus for establishing a connection between the processor and the memory.

In a fourth aspect, a computer-readable storage medium is provided, where instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium is run on a computer, it causes the computer to execute the scheduling policy determination method described in the above-mentioned first aspect.

According to a fifth aspect, a computer program product containing instructions is provided, which, when run on a computer, causes the computer to execute the scheduling policy determination method described in the first aspect above.

The technical effects obtained by the above-mentioned second aspect, third aspect, fourth aspect and fifth aspect are similar to those obtained by the corresponding technical means in the above-mentioned first aspect, and will not be repeated here.

Description of drawings

FIG. 1 is a schematic structural diagram of an electronic device provided in an embodiment of the present application;

FIG. 2 is a schematic diagram of a software module architecture provided by an embodiment of the present application;

FIG. 3 is a schematic diagram of interaction between software modules provided by an embodiment of the present application;

FIG. 4 is a schematic diagram of another software module architecture provided by the embodiment of the present application;

FIG. 5 is a schematic diagram of interaction between another software module provided by the embodiment of the present application;

FIG. 6 is a flow chart of a method for determining a scheduling policy provided in an embodiment of the present application;

FIG. 7 is a schematic diagram of determining a user scenario provided by an embodiment of the present application;

FIG. 8 is a schematic diagram of determining a power state provided by an embodiment of the present application;

FIG. 9 is a schematic diagram of determining a scheduling strategy provided by an embodiment of the present application;

Fig. 10 is a schematic structural diagram of an apparatus for determining a scheduling policy provided by an embodiment of the present application.

Detailed ways

In order to make the purpose, technical solution and advantages of the present application clearer, the implementation manner of the present application will be further described in detail below in conjunction with the accompanying drawings.

It should be understood that the "plurality" mentioned in this application means two or more. In the description of this application, unless otherwise specified, "/" means or means, for example, A/B can mean A or B; "and/or" in this article is just a description of the relationship between associated objects, It means that there can be three kinds of relationships, for example, A and/or B, which can mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in order to clearly describe the technical solution of the present application, words such as "first" and "second" are used to distinguish the same or similar items with basically the same function and effect. Those skilled in the art can understand that words such as "first" and "second" do not limit the number and execution order, and words such as "first" and "second" do not necessarily limit the difference.

Phrases such as "one embodiment" or "some embodiments" described in this application mean that a particular feature, structure, or characteristic described by the embodiment is included in one or more embodiments of the present application. Thus, appearances of "in one embodiment," "in some embodiments," "in other embodiments," "in other embodiments," etc. in various places in this application are not necessarily All refer to the same embodiment, but mean "one or more but not all embodiments" unless specifically stated otherwise. In addition, the terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless specifically stated otherwise.

In order to make the description of each embodiment clear and concise, a brief introduction of related concepts or technologies is given below:

1. Focus window refers to the window with focus. The focused window is the only window that can receive keyboard input. The way to determine the focus window is associated with the focus mode of the system. The top-level window of the focused window is called the active window. Only one window can be active at a time. The focus window is probably the window that the user needs to use currently.

2. The focus application refers to the application to which the focus window belongs, and the focus application is an application that is currently running in the foreground and can receive operations such as keyboard input and mouse operations.

3. A non-focus application refers to an application that runs in the foreground but cannot currently receive keyboard input and mouse operations, that is, generally refers to an application that runs in the foreground but is not operated by the user.

4. Background applications refer to applications that have been minimized to run in the background.

5. Focus mode, which can be used to determine how the mouse makes a window focus. Generally, there are three types of focus modes, namely:

(1) Click-to-focus, in this mode, the window clicked by the mouse can get the focus. That is, when the mouse clicks on any position of a window that can get the focus, this window can be activated, and this window is placed at the front of all windows and receives keyboard input. When the mouse clicks on other windows, this window loses focus.

(2) Focus follows the mouse (focus-follow-mouse), in this mode, the window under the mouse can get the focus. That is, when the mouse moves within the scope of a window that can get the focus, the user does not need to click somewhere in the window to activate this window and receive keyboard input, but this window is not necessarily placed at the front of all windows. When the mouse moves out of the scope of this window, this window will also lose focus.

(3) Sloppy focus, this focus mode is similar to focus-follow-mouse, when the mouse moves to a window that can get the focus, the user does not need to click somewhere in the window to activate this A window that receives keyboard input, but this window is not necessarily placed on top of all windows. Different from focus-follow-mouse, when the mouse moves out of the scope of this window, the focus will not change accordingly, only when the mouse moves to another window that can receive the focus, the focus will change.

6. Processes, including multiple threads, threads can create windows. The focus process is the process to which the thread that created the focus window belongs.

7. Long-term turbo frequency power consumption (power limit1, PL1) refers to the power consumption of the central processing unit (CPU) under normal load, which is equivalent to the thermal design power consumption. The operating power consumption of the CPU most of the time is not Exceed PL1.

8. Short-term turbo frequency power consumption (power limit2, PL2) refers to the highest power consumption that the CPU can achieve in a short period of time, and it has a duration limit. Generally, PL2 is greater than PL1.

平台的名称。在超威半导体公司(Advanced Micro Devices，AMD)

平台，PL1称为SPL(sustained power limit)，PL2的一阶段称为FPPT(fast ppt limit)，PL2的二阶段称为SPPT(slow ppt limit)。It is worth noting that PL1 and PL2 are Intel

The name of the platform. At Advanced Micro Devices (AMD)

Platform, PL1 is called SPL (sustained power limit), the first stage of PL2 is called FPPT (fast ppt limit), and the second stage of PL2 is called SPPT (slow ppt limit).

9. CPU energy performance preference (EPP), which is used to reflect the scheduling tendency of the CPU, and its value ranges from 0 to 255. The smaller the CPU energy efficiency ratio, the CPU tends to be high-performance; the higher the CPU energy efficiency ratio, the CPU tends to low power consumption.

10. Energy efficiency-performance optimization gear (energy performance optimize gear, EPO Gear), used to represent the intensity of EPP adjustment, the value range can be 1 to 5; the larger the value, the more energy-efficient when adjusting EPP; the smaller the value, The more inclined to performance when adjusting EPP.

The electronic equipment involved in the embodiments of the present application will be described below.

The electronic device may be a tablet computer, a notebook computer, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a desktop computer, a personal digital assistant (personal digital assistant, PDA) and other devices.

FIG. 1 is a schematic structural diagram of an electronic device 100 provided by an embodiment of the present application. As shown in Figure 1, the electronic device 100 may include: a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, a charging management module 140, a power management module 141, and a battery 142 , a wireless communication module 150, a display screen 160, and the like.

It can be understood that, the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the electronic device 100 . In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown in the figure, or combine certain components, or separate certain components, or arrange different components. The illustrated components may be realized in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units, for example: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processing unit (graphics processing unit, GPU), an image signal processor ( image signal processor (ISP), controller, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural network processor (neural-network processing unit, NPU), etc. Wherein, different processing units may be independent devices, or may be integrated in one or more processors.

The controller may be the nerve center and command center of the electronic device 100 . The controller can generate an operation control signal according to the instruction opcode and timing signal, and complete the control of fetching and executing the instruction.

In some embodiments, a memory may also be provided in the processor 110 for storing instructions and data. Exemplarily, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to use the instruction or data again, it can be directly recalled from the memory. Repeated access is avoided, and the waiting time of the processor 110 is reduced, thereby improving the efficiency of the system.

In some embodiments, the processor 110 may include one or more interfaces, such as an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuitsound, I2S) interface, pulse code modulation ( pulse code modulation (PCM) interface, universal asynchronous receiver/transmitter (UART) interface, mobile industry processor interface (mobile industry processor interface, MIPI), general-purpose input/output (general-purpose input/output, GPIO) An interface, a subscriber identity module (subscriber identity module, SIM) interface, and/or a USB interface, etc.

It can be understood that the interface connection relationship between the modules shown in the embodiment of the present application is only a schematic illustration, and does not constitute a structural limitation of the electronic device 100 . In other embodiments, the electronic device 100 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

The charging management module 140 is configured to receive a charging input from a charger. Wherein, the charger may be a wireless charger or a wired charger. While the charging management module 140 is charging the battery 142 , it can also supply power to the electronic device 100 through the power management module 141 .

The power management module 141 is used for connecting the battery 142 , the charging management module 140 and the processor 110 . The power management module 141 receives the input from the battery 142 and/or the charging management module 140 to provide power for the processor 110 , the internal memory 121 , the external memory, the display screen 160 , and the wireless communication module 150 . In some embodiments, the power management module 141 and the charging management module 140 can also be set in the same device.

The wireless communication module 150 can provide wireless local area networks (wireless local area networks, WLAN) (such as wireless fidelity (Wireless Fidelity, Wi-Fi) network), bluetooth (bluetooth, BT), global navigation satellite system, etc. (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field communication technology (near field communication, NFC), infrared technology (infrared, IR) and other wireless communication solutions. For example, in the embodiment of the present application, the electronic device 100 can establish a Bluetooth connection with a device such as a wireless earphone through the wireless communication module 150 . The wireless communication module 150 may be one or more devices integrating at least one communication processing module. The wireless communication module 150 receives electromagnetic waves through the antenna, frequency-modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110 . The wireless communication module 150 can also receive the signal to be transmitted from the processor 110, perform frequency modulation on it, amplify it, and convert it into electromagnetic wave and radiate it through the antenna.

The electronic device 100 realizes the display function through the GPU, the display screen 160 , and the application processor. The GPU is a microprocessor for image processing, and is connected to the display screen 160 and the application processor. GPUs are used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

The display screen 160 is used for displaying images, videos and the like. The display screen 160 includes a display panel.

The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, so as to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function, such as saving music, video and other files in the external memory card.

The internal memory 121 may be used to store computer-executable program codes including instructions. The processor 110 executes various functional applications and data processing of the electronic device 100 by executing instructions stored in the internal memory 121 . The internal memory 121 may include an area for storing programs and an area for storing data. Wherein, the stored program area can store an operating system, at least one application program required by a function (such as a sound playing function, an image playing function, etc.) and the like. The storage data area can store data created during the use of the electronic device 100 (such as audio data, phonebook, etc.) and the like. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, flash memory device, universal flash storage (universal flash storage, UFS) and the like.

Next, a possible software system of the electronic device 100 will be described.

The software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a micro-service architecture, or a cloud architecture. In the embodiment of the present application, the software system of the electronic device 100 is exemplarily described by taking a Windows system with a layered architecture as an example.

FIG. 2 is a block diagram of a software system of an electronic device 100 provided by an embodiment of the present application. Referring to Figure 2, the layered architecture divides the software into several layers, and each layer has a clear role and division of labor. Layers communicate through software interfaces. In some embodiments, the Windows system is divided into user mode and kernel mode. Wherein, the user state includes the application layer and the subsystem dynamic link library. The kernel state is divided into firmware layer, hardware abstraction layer (hardware abstraction layer, HAL), kernel (kernel), driver layer and executive body from bottom to top.

As shown in Figure 2, the application layer includes applications such as music, video, games, office, and social networking. The application layer also includes an environment subsystem, a system probe module, a first scene recognition engine, a first scheduling engine, and the like. Wherein, only some application programs are shown in the figure, and the application layer may also include other application programs, such as shopping applications, browsers, etc., which are not limited in this embodiment of the present application.

The environment subsystem can present certain subsets of basic executive system services to applications in a specific form, providing an execution environment for applications.

The system probe module is used to report the status to the first scene recognition engine. The first scene recognition engine is used to complete the recognition of the user scene according to the status reported by the system probe module, and determine the scheduling strategy according to the recognized user scene. The first scheduling engine is used to schedule the firmware layer according to the scheduling policy.

In some embodiments, the first scene identification engine can identify the user scene in which the electronic device 100 is located, and determine a basic scheduling policy matching the user scene. The first dispatching engine may acquire the load condition of the electronic device 100, and determine an actual dispatching strategy that conforms to the actual operating condition of the electronic device 100 in combination with the load condition of the electronic device 100 and the above-mentioned basic scheduling strategy. Among them, the specific content of the first scene recognition engine and the first scheduling engine will be described later, and will not be described here.

The subsystem dynamic link library includes an application programming interface (application programming interface, API) module, and the API module includes a Windows (window) API, a Windows native API, and the like. Among them, Windows API and Windows native API can provide system call entry and internal function support for applications, the difference is that Windows native API is the native API of Windows system. For example, Windows API may include user.dll, kernel.dll, and Windows native API may include ntdll.dll. Among them, user.dll is a Windows user interface interface, which can be used to perform operations such as creating a window and sending a message. kernel.dll is used to provide applications with an interface to access the kernel. ntdll.dll is an important Windows NT kernel-level file that describes the Windows native NTAPI interface. When Windows starts, ntdll.dll resides in a specific write-protected area of memory, preventing other programs from occupying this memory area.

Execution body includes process manager, virtual memory manager, security reference monitor, input/output (Input/Output, I/O) manager, Windows management instrumentation (Windows management instrumentation, WMI) plug-in, power manager, system event Driver (operating system event driver, OsEventDriver) node (also called event driver (Event driver, Event driver) node), system and chip driver (operating system to System on Chip, OS2SOC) node, etc.

The process manager is used to create and terminate processes and threads. The virtual memory manager implements "virtual memory". The virtual memory manager also provides basic support for the cache manager. The Security Reference Monitor enforces security policies on the local computer, it protects operating system resources, and performs runtime object protection and monitoring. The I/O Manager performs device-independent I/O and further processing calls appropriate device drivers. Power Manager manages power state changes for all devices that support power state changes. The OsEventDriver node can interact with the kernel and the driver layer, such as interacting with the graphics card driver. After determining that there is a GPU video decoding event, it reports the GPU video decoding event to the system probe module. The OS2SOC node can be used by the first scheduling engine to send adjustment information to the hardware device, for example, send adjustment information on PL1 and PL2 to the CPU.

动态调谐技术(dynamictuning technology，DTT)驱动、鼠标驱动、音视频驱动、摄像头驱动、键盘驱动等。例如，显卡驱动可以驱动GPU运行，Intel DTT驱动可以驱动CPU运行。The kernel and driver layer includes the kernel and device drivers. The kernel is an abstraction of the processor architecture, which isolates the difference between the execution body and the processor architecture, and ensures the portability of the system. The kernel can perform thread arrangement and scheduling, trap handling and exception scheduling, interrupt handling and scheduling, etc. Device drivers run in kernel mode and serve as the interface between the I/O system and related hardware. Device drivers can include graphics drivers,

Dynamic tuning technology (dynamictuning technology, DTT) driver, mouse driver, audio and video driver, camera driver, keyboard driver, etc. For example, the graphics card driver can drive the GPU to run, and the Intel DTT driver can drive the CPU to run.

HAL is a core mode module that can hide various hardware-related details, such as I/O interfaces, interrupt controllers, and multi-processor communication mechanisms, etc. It provides a unified service interface for different hardware platforms running Windows, and realizes various Portability across hardware platforms. It should be noted that, in order to maintain the portability of Windows, Windows internal components and user-written device drivers do not directly access the hardware, but call routines in the HAL.

The firmware layer can include basic input output system (basic input output system, BIOS), BIOS is a set of programs solidified into a read only memory (ROM) chip on the computer motherboard, which stores the most important basic information of the computer. The input and output program, the self-test program after booting and the system self-starting program, it can read and write the specific information of the system setting from the complementary metal oxide semiconductor (CMOS). Its main function is to provide the computer with the lowest and most direct hardware setting and control. The Intel DTT driver can send instructions to the CPU through the BIOS.

It should be noted that the embodiment of the present application only uses the Windows system as an example. In other operating systems (such as Android (Android) system, IOS system, etc.), as long as the functions realized by each functional module are similar to the embodiment of the present application, The scheme of the present application can be realized.

Next, the workflow of software and hardware for scheduling resources by the electronic device 100 described in the embodiment of FIG. 2 above will be described.

FIG. 3 is a schematic diagram of a workflow of software and hardware for scheduling resources by an electronic device 100 provided in an embodiment of the present application.

As shown in FIG. 3 , the application layer includes a system probe module and a first scene recognition engine, and the first scene recognition engine includes a scene recognition module and a basic policy matching manager. The scene recognition module can interact with the system probe module and the basic policy matching manager respectively. The scene recognition module can send a request to the system probe module to obtain the status of the probe. The system probe module can acquire the running status of the electronic device 100 . For example, the system probe module may include power supply status probes, peripheral device status probes, process load probes, audio and video status probes, system load probes, and system event probes.

Among them, the power state probe can subscribe power state events to the kernel state, and determine the power state according to the callback function fed back by the kernel state. The power state includes battery (remaining) power, power mode, etc., and the power mode can include alternating current (AC ) status and DC power supply (direct current, DC) status. For example, the power state probe may send a request for subscribing to power state events to the OsEventDriver node of the executive layer, and the OsEventDriver node forwards the request to the power manager of the executive layer. The power manager can feed back the callback function to the power status probe through the OsEventDriver node.

The peripheral state probe can subscribe peripheral events to the kernel state, and determine the peripheral events according to the callback function fed back from the kernel state. Peripheral events include mouse wheel sliding events, mouse click events, keyboard input events, microphone input events, camera input events, etc.

The process load probe can subscribe the process load to the kernel state, and determine the load of the process (for example, the focus process) according to the callback function fed back by the kernel state.

The system load probe can subscribe to the system load from the kernel state, and determine the system load according to the callback function fed back from the kernel state.

The audio and video state probe can subscribe to the audio and video events in the kernel state, and determine the audio and video events currently existing in the electronic device 100 according to the callback function fed back from the kernel state. Audio and video events may include GPU decoding events, etc. For example, the audio and video state probe can send a request to subscribe to GPU decoding events to the OsEventDriver node of the executive layer, and the OsEventDriver node forwards the request to the graphics card driver of the kernel and driver layer. The graphics card driver can monitor the status of the GPU. After monitoring that the GPU is performing decoding operations, it will feed back the callback function to the audio and video status probe through the OsEventDriver node.

System event probes can subscribe to system events from the kernel state, and determine system events according to the callback function fed back from the kernel state. System events may include window change events, process creation events, thread creation events, and the like. For example, the system event probe may send a request for subscribing to the process creation event to the OsEventDriver node of the executive layer, and the OsEventDriver node forwards the request to the process manager. After the process is created, the process manager can feed back the callback function to the system event probe through the OsEventDriver node. For another example, the system event probe can also send a request to subscribe to the focus window change event to the API module, and the API module can monitor whether the focus window of the electronic device 100 changes, and when the focus window is monitored to Feedback callback function.

It can be seen that the system probe module subscribes various events of the electronic device 100 to the kernel state, and then determines the running state of the electronic device 100 according to the callback function fed back from the kernel state, that is, obtains the probe state. After the system probe module obtains the probe status, it can feed back the probe status to the scene recognition module. After the scene recognition module receives the probe state, it can determine the user scene where the electronic device 100 is located according to the probe state. The user scene may include a video scene, a game scene, an office scene, a social scene, and the like. The user scenario can reflect the current usage needs of the user. For example, when the scene recognition module recognizes that the focused window is a window of a video application, it determines that the electronic device 100 is in a video scene, which indicates that the user needs to use the video application to watch and browse videos. For another example, when the scene recognition module recognizes that the focus window is a chat window of an instant messaging application, it determines that the electronic device 100 is in a social scene. The context recognition module may also send the user context to the base policy matching manager. The basic policy matching manager can determine the basic scheduling policy according to the user scenario. The basic policy matching manager can feed back the basic scheduling policy to the scene identification module. The scenario recognition module can send the basic scheduling policy and the user scenario to the first scheduling engine of the application layer.

As shown in FIG. 3 , the first scheduling engine includes a load controller, a chip policy fuser, and a scheduling executor. Wherein, the load controller can receive the basic scheduling policy and the user scenario sent by the scenario identification module. The load controller can also obtain the system load from the system probe module, and adjust the basic scheduling policy according to the system load and the user scenario to obtain the actual scheduling policy. The actual scheduling policy includes an operating system (Operating System, OS) scheduling policy and a first CPU power consumption scheduling policy.

Wherein, the load controller may send the OS scheduling policy to the scheduling executor, and the scheduling executor performs scheduling based on the OS scheduling policy. The OS scheduling policy is used to adjust the process priority and I/O priority of the focus process. Exemplarily, the scheduling executor may send an instruction to adjust the process priority of the focus process to the process manager, and in response to the instruction, the process manager adjusts the process priority of the focus process. For another example, the scheduling executor may send an instruction to adjust the I/O priority of the focus process to the I/O manager, and in response to the instruction, the I/O manager adjusts the I/O priority of the focus process.

的CPU和

的CPU，这两类CPU对于CPU功耗的调整方式并不相同，因此需要进行区分。The load controller can also send the first CPU power consumption scheduling policy to the chip policy fuser, and the chip policy fuser can obtain the second CPU power consumption scheduling policy based on the chip platform type of the CPU and the first CPU power consumption scheduling policy. For example, CPU chip platform types are mainly divided into two types, namely

CPU and

The two types of CPUs have different adjustment methods for CPU power consumption, so they need to be distinguished.

调度执行器可以向电源管理器发送调整EPP的指令，以调整CPU的EPP。另外，调度执行器还可以向OS2SOC驱动节点发送调整PL1、PL2的指令，以调整CPU的PL1和PL2。If the chip platform type of the CPU is

The scheduling executor can send an instruction to adjust the EPP to the power manager to adjust the EPP of the CPU. In addition, the scheduling executor can also send an instruction to adjust PL1 and PL2 to the OS2SOC driver node, so as to adjust PL1 and PL2 of the CPU.

调度执行器可以通过WMI插件向Intel DTT驱动发送第二CPU功耗调度策略，第二CPU功耗调度策略可包括PL1的最小值(PL1_mini)、PL1的最大值(PL1_max)、PL2、PL2的持续时间(PL2_time)及EPO Gear，由Intel DTT驱动指示CPU基于第二CPU功耗调度策略运行。If the chip platform type of the CPU is

The scheduling executor can send the second CPU power consumption scheduling policy to the Intel DTT driver through the WMI plug-in, and the second CPU power consumption scheduling policy can include the minimum value of PL1 (PL1_mini), the maximum value of PL1 (PL1_max), PL2, and the continuation of PL2 Time (PL2_time) and EPO Gear are driven by Intel DTT to instruct the CPU to run based on the second CPU power consumption scheduling policy.

Next, another possible software system of the electronic device 100 will be described.

The software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a micro-service architecture, or a cloud architecture. In the embodiment of the present application, the software system of the electronic device 100 is exemplarily described by taking a Windows system with a layered architecture as an example.

FIG. 4 is a block diagram of a software system of an electronic device 100 provided by an embodiment of the present application. Referring to Figure 4, the layered architecture divides the software into several layers, and each layer has a clear role and division of labor. Layers communicate through software interfaces. In some embodiments, the Windows system includes an application layer, a subsystem dynamic link library, a driver layer and a firmware layer.

As shown in Figure 4, the application layer includes applications such as music, video, games, office, and social networking. The application layer also includes a system probe module, a second scene recognition engine, a second scheduling engine, a policy configuration module, a housekeeper interface module, and the like. Wherein, only some application programs are shown in the figure, and the application layer may also include other application programs, such as shopping applications, browsers, etc., which are not limited in this embodiment of the present application.

The system probe module is used to report the status to the second scene recognition engine. The second scenario identification engine is used to complete the identification of user scenarios according to the status reported by the system probe module, and determine the scheduling strategy according to the identified user scenarios. The second scheduling engine is used to schedule the firmware layer according to the scheduling policy.

The policy configuration module is used to send multiple pre-configured scheduling policies to the second scene recognition engine. After the second scene recognition engine recognizes the user scene, it searches for a scheduling policy that matches the recognized user scene from the various scheduling policies. The housekeeper interface module is used to provide the currently used power mode to the second scene recognition module, and the second scene recognition engine can select a scheduling strategy that matches the currently used power mode and the current user scene.

The subsystem dynamic link library includes an API module, and the API module includes a Windows API, a Windows native API, and the like. Among them, Windows API and Windows native API can provide system call entry and internal function support for applications, the difference is that Windows native API is the native API of Windows system. For example, Windows API may include user.dll, kernel.dll, and Windows native API may include ntdll.dll. Among them, user.dll is a Windows user interface interface, which can be used to perform operations such as creating a window and sending a message. kernel.dll is used to provide applications with an interface to access the kernel. ntdll.dll is an important Windows NT kernel-level file that describes the Windows native NTAPI interface. When Windows starts, ntdll.dll resides in a specific write-protected area of memory, preventing other programs from occupying this memory area.

The driver layer may include a process manager, a virtual memory manager, a security reference monitor, an I/O manager, a power manager, a WMI plug-in, an Event driver node, and an OS2SOC driver node.

The process manager is used to create and terminate processes and threads. The virtual memory manager implements "virtual memory". The virtual memory manager also provides basic support for the cache manager. The Security Reference Monitor enforces security policies on the local computer, it protects operating system resources, and performs runtime object protection and monitoring. The I/O Manager performs device-independent I/O and further processing calls appropriate device drivers. Power Manager manages power state changes for all devices that support power state changes. The WMI plug-in can be used for the second scheduling engine to send scheduling policies to the firmware layer; the Event driver node can interact with graphics card drivers, audio and video drivers, camera drivers and keyboard drivers, so that the system probe module can detect various events (also It can be referred to as data or information), such as interacting with the graphics card driver, so that the system probe module can monitor GPU video decoding events. The OS2SOC driver node can be used by the second scheduling engine to send scheduling policies to the firmware layer.

和

等，这三个硬件平台的调度策略可以不同，因此第二调度引擎在确定调度策略时可以区分硬件平台类型。这种情况下，固件层还可以包括Intel DTT、AMD电源管理框架(power management framework，PMF)、NVIDIA数据库(database，DB)等。The firmware layer includes various hardware and hardware drivers configured for the electronic device 100. For example, the firmware layer may include a CPU, a mouse, etc., and the firmware layer also includes a mouse driver. The hardware platform of the hardware configured by the electronic device 100 may be different. For example, the hardware platform includes:

and

etc., the scheduling policies of the three hardware platforms may be different, so the second scheduling engine may distinguish the types of hardware platforms when determining the scheduling policy. In this case, the firmware layer may also include Intel DTT, AMD power management framework (power management framework, PMF), NVIDIA database (database, DB) and so on.

It should be noted that the embodiment of the present application only uses the Windows system as an example to illustrate, in other operating systems (such as Android system, IOS system, etc.), as long as the functions realized by each functional module are similar to the embodiment of the present application, the present application can also be realized. application program.

Next, the workflow of software and hardware for scheduling resources by the electronic device 100 described in the embodiment of FIG. 4 above will be described.

FIG. 5 is a schematic diagram of a workflow of software and hardware for scheduling resources by an electronic device 100 provided in an embodiment of the present application.

As shown in FIG. 5 , the operating system of the electronic device 100 includes a system probe module, a second scene recognition engine, a second scheduling engine, and a chip scheduling engine. The system probe module, the second scene recognition engine and the second scheduling engine are located at the application layer, the second scene recognition engine can run as a plug-in, and the second scheduling engine can run as a service. The chip scheduling engine is located in the driver layer, and the chip scheduling engine can run as a service.

The second scene identification engine can interact with the system probe module to identify the user scene according to the operating status of the electronic device 100 fed back by the system probe module. The second scene recognition engine can interact with the second scheduling engine. After the second scene recognition engine recognizes the user scene, it determines a scheduling policy according to the user scene, and sends the scheduling policy to the second scheduling engine. After receiving the scheduling policy, the second scheduling engine returns a receiving result to the second scene recognition engine, so as to notify the second scene recognition engine that it has successfully received the scheduling policy. Then, the second scheduling engine sends a scheduling policy to the chip scheduling engine, and the chip scheduling engine executes the scheduling policy.

The second scene recognition engine includes a scene recognition module, a scene library, a strategy scheduling module and a strategy library. The second scheduling engine includes a scene interaction module, a scheduling policy fusion module and a scheduling executor. The chip scheduling engine includes WMI plug-in, Event driver node and OS2SOC driver node. The firmware layer includes Intel DTT, AMD PMF, NVIDIA DB, etc.

As shown in FIG. 5 , the second scene recognition engine can interact with the system probe module, the policy configuration module, the housekeeper interface module, and the second scheduling engine respectively.

The housekeeper interface module can send the power mode currently used by the electronic device to the second scene recognition engine, and the power mode can assist the second scene recognition engine to determine a scheduling strategy; the policy configuration module is used to send a variety of pre-configured scheduling strategies to the second scene recognition engine Strategy.

The system probe module can acquire the running status of the electronic device 100 . For example, the system probe module may include power supply status probes, peripheral device status probes, audio and video status probes, application switching probes, system load probes, system working status probes, and the like.

Among them, the power state probe is used to detect the power state. The power state includes battery (remaining) power, power mode, power plan, etc. The power mode can include AC state and DC state, and the power plan can include energy efficiency plan, balance plan, and performance plan. wait. Peripheral status probes are used to detect peripheral events, including mouse wheel sliding events, mouse click events, keyboard input events, microphone input events, camera input events, etc. The audio and video status probe is used to detect audio events and video events that currently exist in the electronic device 100 . The application switching probe is used to detect the applications currently running on the electronic device 100, that is, to detect focus applications, non-focus applications, background applications, etc., wherein the focus application is the application to which the focus window belongs, and the non-focus application is the currently opened window that is not the focus The window is the application to which the window is not minimized, and the background application is the application running in the background. The system load probe is used to detect the current load level of the system. The system working state probe is used to detect the current working state of the system, that is, to detect whether the system is currently in an idle state.

The system probe module detects the running status of the electronic device 100 through various probes, that is, obtains the status of the probes. The second scene recognition engine may subscribe to the probe status to the system probe module. In this case, after obtaining the probe status, the system probe module may report the probe status to the second scene recognition engine.

第12代平台的架构提供的大小核调度能力，指示优先使用大核(偏性能)还是小核(偏能效)进行的策略配置。The scene library in the second scene recognition engine is used to store multiple user scenes. For example, user scenes include multiple main scenes such as social scenes, office scenes, and browser scenes. Each main scene can be divided into multiple sub-scenes, such as browser Scenarios include browser surfing the web, browser audio playback, and browser video playback. The policy library in the second scene recognition engine is used to store various scheduling policies sent by the policy configuration module. For example, scheduling policies include big and small core scheduling and office policy library, etc. The office policy library records scheduling policies related to office applications. Big and small core scheduling is

The large and small core scheduling capabilities provided by the architecture of the 12th generation platform indicate the policy configuration of using large cores (biased performance) or small cores (biased energy efficiency).

The policy scheduling module can send a scene query and subscription request to the scene recognition module. The query and subscription scene request is used to trigger the scene recognition module to perform scene recognition. The query and subscription scene request can be sent immediately after the electronic device 100 is turned on, or can be sent periodically. This application implements Examples are not limited to this.

After receiving the query subscription scene request, the scene recognition module sends a query subscription status request to the system probe module. The query subscription status request is used to instruct each probe in the system probe module to perform status detection/status determination, etc. The needle module can report the state of the electronic device 100 to the scene recognition module. The scene recognition module determines the current user scene of the electronic device 100 from the scene library according to the state of the electronic device, and reports the user scene to the policy scheduling module. The policy scheduling module can determine the scheduling policy from the policy library according to the current user scenario of the electronic device 100 .

In addition, the policy scheduling module can also receive the power mode delivered by the housekeeper interface module, and the power supply mode can be determined according to the user switch identification sent by the housekeeper interface module. The policy scheduling module may refer to the power mode when determining the scheduling policy, for example, determining a scheduling policy that matches the currently used power mode and the current user scenario. Alternatively, the power mode is used as a condition for whether the policy scheduling module determines the scheduling policy. When the power mode is a preset mode, the policy scheduling module determines the scheduling policy according to the user scenario.

The policy scheduling module sends the scheduling policy to the scene interaction module. After receiving the scheduling policy, the scene interaction module returns the receiving result to the policy scheduling module. The receiving result is used to notify the policy scheduling module that it has successfully received the scheduling policy. The scene interaction module sends the scheduling policy to the scheduling policy fusion module, and the scheduling policy fusion module analyzes and escapes the scheduling policy, so as to parse and escape the policy parameters in the scheduling policy into parameters recognized by the hardware platform. The dispatch policy fusion module sends the parsed and escaped dispatch policy to the dispatch executor. The scheduling executor sends the scheduling policy after parsing and escaping according to the hardware platform type.

调度执行器可以向OS2SOC驱动节点发送解析转义后的调度策略；如果硬件平台类型为

调度执行器可以通过WMI插件向IntelDTT驱动发送解析转义后的调度策略。在本申请实施例中，调度策略可以是芯片调度策略，通过调整芯片的能效比，实现功耗的最佳平衡。例如，调度策略可以是CPU的功耗调度策略。For example, if the hardware platform type is

The scheduling executor can send the scheduling policy after parsing and escaping to the OS2SOC driver node; if the hardware platform type is

The scheduling executor can send the parsed and escaped scheduling policy to the IntelDTT driver through the WMI plug-in. In the embodiment of the present application, the scheduling policy may be a chip scheduling policy, and an optimal balance of power consumption is achieved by adjusting the energy efficiency ratio of the chip. For example, the scheduling policy may be a power consumption scheduling policy of the CPU.

调度执行器可以向电源管理器发送调度策略中的用于调整CPU的EPP的指令。另外，调度执行器还可以向OS2SOC驱动节点发送调度策略中的用于调整CPU的PL1、PL2的指令。若硬件平台类型为

调度执行器可以通过WMI插件向Intel DTT驱动发送调度策略，其中可包括PL1的最小值、PL1的最大值、PL2、PL2的持续时间及EPO Gear，由Intel DTT驱动指示CPU基于该调度策略运行。WMI插件、Intel DTT和OS2SOC驱动节点在接收到调度策略后，可以返回接收结果，接收结果用于指示自身已成功接收到调度策略。If the hardware platform type is

The scheduling executor may send an instruction for adjusting the EPP of the CPU in the scheduling policy to the power manager. In addition, the scheduling executor may also send instructions for adjusting PL1 and PL2 of the CPU in the scheduling policy to the OS2SOC driver node. If the hardware platform type is

The scheduling executor can send the scheduling policy to the Intel DTT driver through the WMI plug-in, which can include the minimum value of PL1, the maximum value of PL1, PL2, the duration of PL2, and EPO Gear, and the Intel DTT driver instructs the CPU to run based on the scheduling policy. After receiving the scheduling policy, the WMI plug-in, Intel DTT and OS2SOC driver nodes can return the receiving result, which is used to indicate that they have successfully received the scheduling policy.

It should be noted that, in the above embodiments of FIG. 2-FIG. 3, the first scene recognition engine may determine the scheduling policy according to the user scene. Similarly, in the above embodiments of FIG. 4-FIG. 5, the second scene recognition engine may determine the scheduling policy according to the user scene. However, if only user scenarios are considered to determine the scheduling strategy, the determined scheduling strategy is relatively limited, and cannot accurately and reasonably allocate resources of electronic devices.

For this reason, the embodiment of the present application provides a scheduling policy determination method, which can determine the scheduling policy in combination with the current user scenario of the electronic device, the power state of the electronic device, and the system load. The reference factors for determining the scheduling policy in this way are more comprehensive , so the subsequent resource scheduling based on this scheduling strategy can accurately realize the reasonable allocation of resources of electronic equipment, so as to not only meet the needs of users, but also take into account the system requirements of the electronic equipment itself, thereby reducing the energy consumption of electronic equipment. To ensure the stable operation of the electronic equipment while improving the battery life of the electronic equipment.

The method for determining the scheduling policy provided by the embodiment of the present application is explained in detail below.

Fig. 6 is a flow chart of a method for determining a scheduling policy provided by an embodiment of the present application. Referring to Figure 6, the method comprises the following steps:

Step 601: The electronic device determines the current user scene where the electronic device is located.

The user scenario refers to the usage scenario of the user, that is, what the user is doing with the electronic device. This user scenario can reflect user needs.

Specifically, the operation of step 601 may be: the electronic device obtains application running information of the electronic device, and determines the user scenario where the electronic device is located according to the application running information.

Since the user often uses various applications installed in the electronic device when using the electronic device, the user scenario can be determined according to the application running information in the embodiment of the present application, and the determined user scenario is relatively accurate.

The application running information may include focus application information, and may further include application information such as non-focus application information and background application information. In this embodiment of the present application, the application information of an application may include the application name, application type, application running status, etc. of the application.

In some embodiments, the application running information can be obtained through the system probe module in the embodiments of FIGS. 2-5 above. The system probe module can report the obtained application operation information to the scene identification module, and the scene identification module can identify the user scene according to the application operation information.

For example, in the embodiments shown in FIGS. 2-3 above, the system probe module may include a system event probe, and the system event probe may include a focus window probe. The focus window probe is used to determine the latest focus window when the focus window changes. The focus window probe can report the focus window change event to the system event probe. The system event probe can determine the application information of the current focus application, non-focus application, background application and other applications according to the focus window change event reported by the focus window probe, so as to obtain application running information. Then the system event probe can report the application running information to the scene identification module, so that the scene identification module can identify the user scene accordingly.

For another example, in the embodiments of FIGS. 4-5 above, the system probe module may include an application switching probe, and the application switching probe may include a focus window probe. The focus window probe is used to determine the latest focus window when the focus window changes, and the focus window probe can report the focus window change event to the application switching probe. The application switching probe can determine the application information of the current focus application, non-focus application, background application and other applications according to the focus window change event reported by the focus window probe, so as to obtain application running information. Then the application switching probe can report the application running information to the scene identification module, so that the scene identification module can identify the user scene accordingly.

When the above-mentioned system event probe or application switching probe determines the application information of the current focus application, non-focus application, background application and other applications according to the focus window change event reported by the focus window probe, it can receive the information reported by the focus window probe. After the focus window change event, determine the current focus application, non-focus application, background application and other applications according to the process creation event, process exit event, window event, etc. detected by other probes in the system probe module, that is, determine each application The application name and application type, and then combine the peripheral status, audio status, video status, process load, etc. detected by other probes in the system probe module to determine the application running status of each application, so that the current focus application, The application information of applications such as non-focus applications and background applications is to obtain application running information.

Wherein, the window event may include a window full screen event, a window minimize event, a focus gain event, a focus loss event, and the like. The window fullscreen event is used to indicate that a window is fullscreened. The window minimize event is used to indicate that a window has been minimized. The focus event is used to indicate that a window has focus. The focus lost event is used to indicate that a window has lost focus. The window that gets the focus is the focused window. The window that loses focus is the window that gained focus last time, that is, the last historical focus window.

Optionally, the operation of the electronic device (such as the above-mentioned scene recognition module) determining the user scene where the electronic device is located according to the application running information may be implemented through the following method 1, method 2, or method 3.

Method 1: The electronic device determines the main scene according to the application type in the focus application information (that is, the application type of the focus application), and then determines the sub-scene according to the main scene and the application running state in the focus application information (that is, the application running state of the focus application). scene, the main scene and the sub-scene are user scenes.

Optionally, the correspondence between the focus application type and the main scene may be preset in the electronic device. In this case, the electronic device may obtain the corresponding main scene from the correspondence between the focused application type and the main scene according to the application type in the focused application information.

For example, the corresponding relationship between the focus application type and the main scene may be shown in Table 1 below. In this case, if the application type in the focus application information is video, it can be determined according to Table 1 that the main scene is a video scene; if the application type in the focus application information is office, then according to Table 1 it can be determined that the main scene is Office scene; if the application type in the focus application information is a game, then it can be determined that the main scene is a game scene according to Table 1; if the application type in the focus application information is a social type, then according to Table 1, it can be determined that the main scene is a social scene ; If the application type in the focus application information is a browser class, then according to Table 1, it can be determined that the main scene is a browser scene.

Table 1

Focus application type main scene video class video scene Office Office scene games game scene social class social scene browser class browser scene ... ...

In the embodiment of the present application, only the above Table 1 is taken as an example to illustrate the corresponding relationship between the focus application type and the main scene, and the above Table 1 does not limit the embodiment of the present application.

As an example, the electronic device may directly determine the sub-scene according to the main scene and the running state of the application in the focus application information.

Optionally, the correspondence between the main scene, the running state of the focus application and the sub-scenes may be preset in the electronic device. In this case, the electronic device may obtain the corresponding sub-scene from the correspondence between the main scene, the running state of the focused application, and the sub-scene according to the main scene and the application running state in the focus application information.

For example, the correspondence between the main scene, the running state of the focus application and the sub-scenes may be shown in Table 2 below. In this case, if the main scene is an office scene, and the application running state in the focus application information is receiving mouse input, then according to Table 2, it can be determined that the sub-scene is a document browsing scene in the office scene. If the main scene is an office scene, and the application running state in the focus application information is receiving keyboard input, then according to Table 2, it can be determined that the sub-scene is a document editing scene in the office scene. If the main scene is an office scene, and the application running state in the focus application information is using a camera, then according to Table 2, it can be determined that the sub-scene is a video conference scene in the office scene. If the main scene is a social scene, and the application running state in the focus application information is receiving keyboard input, then according to Table 2, it can be determined that the sub-scene is a text chat scene in a social scene. If the main scene is a social scene, and the application running state in the focus application information is using a microphone and not using a camera, then according to Table 2, it can be determined that the sub-scene is a voice chat scene in a social scene. If the main scene is a social scene, and the application running state in the focus application information is using a microphone and a camera, then according to Table 2, it can be determined that the sub-scene is a video chat scene in a social scene.

Table 2

In the embodiment of the present application, only the above Table 2 is used as an example to illustrate the corresponding relationship between the main scene, the running state of the focus application and the sub-scene, and the above Table 2 does not limit the embodiment of the present application.

As another example, the electronic device may determine at least one sub-scene according to the main scene, the application running state in the focused application information, the non-focused application information, and the background application information, and then select a priority from the at least one sub-scene The highest subscene.

The priority of each sub-scene can be set in advance in the electronic device, and the priority of each sub-scene can be set in advance by the technician according to the usage requirements. For example, the technician can set each The priority of the sub-scenes, the greater the impact on the battery life of the electronic device, the higher the priority, and the smaller the impact on the battery life of the electronic device, the lower the priority. In this way, after at least one sub-scene is determined according to the main scene, the application running state in the focused application information, the non-focused application information, and the background application information, a sub-scene with the highest priority can be selected, so that the following can be based on the sub-scene The most reasonable scheduling strategy is determined to maximize the battery life of the electronic equipment.

Optionally, the correspondence between the main scene, the running status of the focused application, the information of the non-focused application, the information of the background application and the sub-scenes may be preset in the electronic device. In this case, the electronic device can, according to the main scene, the application running state in the focus application information, the non-focus application information and the background application information, from the main scene, the focus application running state, the non-focus application information, the background application information and the sub- In the corresponding relationship between scenes, at least one corresponding sub-scene is acquired.

For example, the correspondence between the main scene, the running state of the focus application, the information of the non-focus application, the information of the background application and the sub-scenes may be shown in Table 3 below.

table 3

In the embodiment of this application, only the above Table 3 is taken as an example to illustrate the corresponding relationship between the main scene, the running state of the focus application, the information of the non-focus application, the information of the background application and the sub-scene, and the above Table 3 does not apply to the implementation of this application. Examples constitute limitations.

In this case, if the main scene is a browser scene, the application running status in the focus application information is None, the application name in the non-focus application information is word, the application type is office, and the application running status is None, and the background application information The application named xx music, the application type is music, and the application running status is output audio. According to Table 3, it can be determined that there are two sub-scenes, one is the office data query scene in the browser scene, and the other is the browser scene. The scene under the background listening to the music scene. Assuming that the priority of the office data query scene in the browser scene is higher than that of listening to music in the background in the browser scene, the office data query scene in the browser scene can be selected.

If the main scene is an office scene, the application running status in the focus application information is receiving keyboard input, the application name in the non-focus application information is xx making friends, the application type is social, and the application running status is using the microphone. The application name is xx browser, the application type is browser class, and the application running status is none. According to Table 3, it can be determined that there are two sub-scenarios, one is the voice chat scene in the office scene, and the other is the document in the office scene Edit the scene. Assuming that the voice chat scene in the office scene has a higher priority than the document editing scene in the office scene, the voice chat scene in the office scene can be selected.

Mode 2, the electronic device determines the user scenario according to the application running information and system working status.

Electronic devices can detect system operating status. The system working state refers to the current working state of the system, which can be divided into idle state and other states. The idle state refers to a state in which the system has not been operated by a user for a long time.

If the working state of the system is other than the idle state, the electronic device may determine the user scenario according to the above method 1, that is, determine the user scenario directly according to the application running information.

In some embodiments, in the embodiments of Fig. 2-Fig. 5 above, the system probe module may include a system working state probe, which is used to detect the current working state of the system (that is, the system working state) , that is, to detect whether the system is currently idle, and report the system working status to the scene recognition module when the system working status is idle. After receiving the working state of the system, the scene identification module can determine the user scene according to the working state of the system and the running information of the application.

In other words, when the system working state is other than the idle state, the system working state probe will not report the system working state to the scene recognition module, then the scene recognition module will determine according to the above method 1 The user scenario is to determine the user scenario directly according to the running information of the application. When the system working status changes to idle status, the system working status probe will report the system working status to the scene recognition module, and the scene recognition module can know the system working status after receiving the system working status reported by the system working status probe Changed to the idle state, at this time the scene recognition module can determine the user scene according to the system working state and the application running information.

Optionally, when the system working status probe acquires the system working status, it can determine the system working status according to the device cover status, device screen bright status, system lock status, mouse and keyboard peripheral status, etc. For example, if there is no mouse and keyboard input for a long time when the device is not closed, the screen is on and the device is not locked, it can be determined that the system working state is the idle state; otherwise, it can be determined that the system working state is other than the idle state other states.

Optionally, when the user scenario is determined according to the system working state and the application running information, if the system working state changes to an idle state, and the application running information indicates that there is an application in use by the user, the electronic device can follow the above method 1 Determining the user scenario means determining the user scenario directly based on the application running information. For example, if the working state of the system is idle, and the application running state in at least one of the application information such as the focused application information, the non-focused application information, and the background application information indicates that the microphone is being used, the camera is being used, the video is being output, Audio is being output, or other peripherals are being used, indicating that the user is using certain applications, and the electronic device can determine the user scenario according to the above method 1, that is, directly determine the user scenario based on the application running information.

Alternatively, if the system working state changes to an idle state, and the application running information indicates that the applications are not in use by the user, the electronic device can determine that the main scene is an idle scene. as a user scenario. For example, if the system working status is idle, and the application running status in the application information such as focused application information, non-focused application information, and background application information all indicate that the microphone is not used, the camera is not used, the video is not output, the audio is not output, and the Using other peripherals means that the user does not use the application, and the electronic device can determine that the main scene is an idle scene, that is, determine that the user scene is an idle scene. The user scene is an idle scene, which means that the user is not currently using the electronic device (that is, not operating and not using the application), and accordingly a scheduling strategy applicable to this situation can be subsequently determined.

Mode 3, the electronic device determines the user scenario where the electronic device is located according to the application running information and the IO load information.

Electronic devices can obtain IO load information. In some embodiments, in the above embodiments of Figure 2-Figure 5, the system probe module may include a system load probe, the system load probe can detect IO load information, and report the IO load information to the scene identification module , for the scene recognition module to determine the user scene accordingly.

The IO load information is used to reflect the IO load status. Exemplarily, the IO load information may include an IO time ratio, and the IO time ratio refers to a time ratio used for IO operations in a period, that is, indicates what percentage of a second is used for IO operations. The IO time ratio can reflect the level of IO load. That is, the higher the IO time ratio, the higher the IO load; the lower the IO time ratio, the lower the IO load. In some embodiments, the IO time ratio can be obtained through the IO throughput statistics service, and of course, the IO time ratio can also be obtained in other ways, which is not limited in this embodiment of the present application.

In the embodiment of the present application, the user behavior can be inferred according to the IO load information, which in turn helps to determine the user scenario. For example, if the persistence of the IO load information is above 30%, it can be considered that the user is copying files; or, if the persistence of the IO load information is between 10% and 30%, it can be considered that the user is decompressing files.

Optionally, the electronic device may determine the main scene according to the application type in the focus application information in the application running information, and then determine the sub-scene according to the main scene and the IO load information, and the main scene and the sub-scene are user Scenes.

For example, the correspondence between the main scene, IO load information and sub-scenes may be preset in the electronic device. In this case, the electronic device can obtain the corresponding sub-scene from the corresponding relationship according to the main scene and the IO load information.

It is worth noting that the electronic device can not only determine the sub-scene according to the main scene and the IO load information, but also combine other information, such as combining the application running status and non-focus application information in the application running information in the focus application information , background application information, etc. to determine the sub-scene, which can make the determined sub-scene more accurate.

The following takes FIG. 7 as an example to illustrate the process of determining the user scene in step 601 above.

FIG. 7 is a schematic diagram of determining a user scenario provided by an embodiment of the present application.

Referring to FIG. 7 , when the focused window changes, the current focused application information, non-focused application information and background application information can be obtained, and then the main scene can be determined according to the application type in the focused application information. Afterwards, scene jitter filtering can be performed, specifically: if the newly determined main scene is the same as the last determined main scene, and the application running status in the newly obtained focus application information is the same as the focus application information obtained last time If the running status of the applications in is the same, the user scenario is not re-determined, and the operation ends; otherwise, continue to determine the sub-scenario.

When the working state of the system changes, the current working state of the system can be obtained. If the working state of the system is not idle, the user scenario is not re-determined, and the operation ends. If the working state of the system is the idle state, then determine whether the main scene is an idle scene according to the application running state in the current focus application information, non-focus application information, and background application information. If the application running status in the focus application information, non-focus application information, and background application information indicates that the microphone is not used, the camera is not used, the video is not output, the audio is not output, and other peripherals are not used, it can be determined that the main scene is an idle scene , that is, it is determined that the user scene is an idle scene. However, if the application running status in the focused application information, non-focused application information, and background application information indicates that the microphone is being used, the camera is being used, video is being output, audio is being output, or other peripherals are being used, then the focus window does not currently occur When changing, do not redefine the user scene, end the operation, and continue to determine the sub-scene when the focus window changes and the main scene has been determined according to the application type in the focus application information.

When determining the sub-scene, at least one sub-scene can be determined according to the main scene, the application running state in the focus application information, the non-focus application information and the background application information. For example, in combination with the main scene, the focus application information, the non-focus application information and The application running state in the background application information is analyzed to obtain at least one sub-scenario. Then compare the priority of the at least one sub-scene, select the sub-scene with the highest priority, and determine the main scene and the selected sub-scene as the user scene.

Step 602: the electronic device determines a power state of the electronic device.

The power state may include a power mode, a power plan, etc., the power mode may include an AC state and a DC state, and the power plan may include an energy efficiency plan, a balance plan, a performance plan, and the like.

In some embodiments, in the embodiments shown in FIGS. 2-5 above, the system probe module may include a power state probe, which is used to detect the power state and report the power state to the scene recognition module.

Optionally, when determining the power state, the power state probe may determine the current power state according to the power mode change event and the power plan change event. During the operation of the electronic device, if the power mode changes, a power mode change event will be triggered, and the power mode change event is used to indicate the latest power mode after the change. During the operation of the electronic device, if the power plan changes, a power plan change event will be triggered, and the power plan change event is used to indicate the latest power plan after the change.

It is worth noting that in some cases, the power mode change event and the power plan change event will be directly triggered when the electronic device is turned on. At this time, the power status probe can directly detect the power mode change event and the power plan change event to determine the current the power state of . However, in some other cases, the power mode change event and the power plan change event are not triggered when the electronic device is started, and the power state probe cannot directly detect the power mode change event and the power plan change event at this time. In this case, in order to ensure normal determination of the power state when starting up, the electronic device may actively determine the power state when starting up.

The following uses FIG. 8 as an example to illustrate the process of determining the power state in step 602 above.

FIG. 8 is a schematic diagram of determining a power state provided by an embodiment of the present application.

Referring to Figure 8, the electronic device actively obtains the power mode information when it is turned on; if the power mode information is not obtained, that is, the acquisition fails, the power state is not determined, and the operation ends; if the power mode information is obtained, that is, the acquisition is successful, then Continue to Get Power Plan Information. Afterwards, if the power plan information is not obtained, that is, the acquisition fails, then the power plan is set as a balanced plan, and then the power plan filtering operation is performed; if the power plan information is obtained, that is, the acquisition is successful, the power plan filtering operation is performed.

During normal operation of the electronic device, the power state probe can determine the power mode through the power mode probe, and can determine the power plan through the power plan probe. The power mode probe can detect power mode change events. The power plan probe can detect power plan change events. In this way, when the power mode changes and/or the power plan changes, the power status probe can obtain the changed power mode and/or the changed power plan, and then perform the power plan filtering operation.

When performing the power plan filtering operation, if the newly determined power plan has not changed compared with the last determined power plan, the operation will end without re-determining the power state; Once the determined power plan changes, power state jitter filtering is performed, specifically: the newly determined power plan is the same as the power plan in the current power state, and the newly determined power mode is the same as the current power state In the case of the same power mode, end the operation without re-determining the power state; if the newly determined power plan is different from the power plan in the current power state, and/or, the newly determined power mode is different from the current power state If the power modes in the system are different, the power state is re-determined, that is, the newly determined power plan and power mode are determined as the power state.

Step 603: the electronic device determines the system load of the electronic device.

In some embodiments, in the embodiments shown in FIGS. 2-5 above, the system probe module may include a system load probe, which is used to detect the system load and report the system load to the scene recognition module.

Exemplarily, the system load of an electronic device may be represented by a load level. The load level is used to reflect the overall load condition of the system. For example, the load levels may be light, medium, and heavy. A load rating of light indicates that the system load is low; a load rating of medium indicates that the system load is moderate; a load rating of heavy indicates that the system load is relatively high.

Optionally, the electronic device (such as the system load module) may determine the current load level of the electronic device according to the current device performance index of the electronic device. For example, the load level may be determined according to CPU load information and IO load information.

The CPU load information is used to reflect the CPU load. Exemplarily, the CPU load information may include a system frame loss rate. The frame loss rate of the system can reflect the level of CPU load. That is, the higher the system frame loss rate, the higher the CPU load; the lower the system frame loss rate, the lower the CPU load. In some embodiments, the system frame loss rate can be obtained through the relevant interface used to obtain frame information in the SurfaceFlinger service. Of course, the system frame loss rate can also be obtained through other methods, which is not limited in this embodiment of the present application.

The IO load information is used to reflect the IO load status. Exemplarily, the IO load information may include an IO time ratio, and the IO time ratio refers to a time ratio used for IO operations in a period, that is, indicates what percentage of a second is used for IO operations. The IO time ratio can reflect the level of IO load. That is, the higher the IO time ratio, the higher the IO load; the lower the IO time ratio, the lower the IO load. In some embodiments, the IO time ratio can be obtained through the IO throughput statistics service, and of course, the IO time ratio can also be obtained in other ways, which is not limited in this embodiment of the present application.

Optionally, the operation of determining the load level according to the CPU load information and the IO load information may be: if the system frame loss rate is greater than or equal to the first frame loss rate threshold, or the IO time ratio is greater than or equal to the first time ratio threshold, then determine The load level is heavy; if the system frame loss rate is greater than the second frame loss rate threshold and less than the first frame loss rate threshold, and the IO time ratio is greater than the second time ratio threshold and less than the first time ratio threshold, the load level is determined to be medium ; If the system frame loss rate is less than or equal to the second frame loss rate threshold, or the IO time ratio is less than or equal to the second time ratio threshold, determine that the load level is light.

Both the first frame loss rate threshold and the second frame loss rate threshold can be set in advance. The first frame loss rate threshold and the second frame loss rate threshold are used to judge the high or low frame loss rate of the system. The first frame loss rate The threshold is greater than the second frame loss rate threshold. For example, the first frame loss rate threshold may be 1%, 2% and so on, and the second frame loss rate threshold may be 0%, 0.1% and so on. When the system frame loss rate is greater than or equal to the first frame loss rate threshold, it indicates that the system frame loss rate is high, that is, the CPU load is high. When the system frame loss rate is less than or equal to the second frame loss rate threshold, it indicates that the system frame loss rate is low, that is, the CPU load is low.

Both the first time ratio threshold and the second time ratio threshold can be set in advance. The first time ratio threshold and the second time ratio threshold are thresholds used to judge the IO time ratio. The first time ratio threshold is greater than the second time ratio threshold. For example, the first time ratio threshold may be 60%, 85% and so on, and the second time ratio threshold may be 40%, 35% and so on. When the IO time ratio is greater than or equal to the first time ratio threshold, it indicates that the IO time ratio is high, that is, the IO load is high. When the IO time ratio is less than or equal to the second time ratio threshold, it indicates that the IO time ratio is low, that is, the IO load is low.

In this case, if the system frame loss rate is greater than or equal to the first frame loss rate threshold, or the IO time ratio is greater than or equal to the first time ratio threshold, it means that the CPU load or IO load is high, that is, the system load is high , so it can be determined that the load level is heavy.

If the system frame loss rate is greater than the second frame loss rate threshold and less than the first frame loss rate threshold, and the IO time ratio is greater than the second time ratio threshold and less than the first time ratio threshold, it means that the CPU load is moderate and the IO load is moderate, that is, The system load is moderate, so it can be determined that the load level is medium.

If the system frame loss rate is less than or equal to the second frame loss rate threshold, or the IO time ratio is less than or equal to the second time ratio threshold, it means that the CPU load or IO load is low, which means that the system load is low, so the load can be determined The grade is light.

Step 604: The electronic device determines a scheduling policy according to the user scenario, the power state and the system load.

The scheduling policy is used to schedule resources of electronic devices, and is specifically used to schedule underlying hardware resources. The scheduling strategy contains tuning parameters that are reasonable for the current state of the electronic equipment. The scheduling policy can be delivered to the scheduling engine, so that the scheduling engine can schedule the underlying hardware resources based on the scheduling policy.

In the embodiment of the present application, the current user scene, power state and system load of the electronic device can be continuously determined during the operation of the electronic device, that is, the user scene, power state and system load can be dynamically identified, and According to the change of the user scenario, the power state and the system load, the scheduling strategy is dynamically determined, and resources are dynamically optimized accordingly. In this way, the resource allocation of electronic equipment can be accurately realized, so that the energy consumption of electronic equipment can be reduced, the battery life of electronic equipment can be improved, and the electronic equipment can be guaranteed stable operation of the equipment.

Specifically, the operation of step 604 may be as follows: the electronic device obtains the first key value corresponding to the user scenario, obtains the second key value corresponding to the power state, and obtains the third key value corresponding to the system load, and then according to the first key value The first key value, the second key value, and the third key value determine the target key value, and then obtain the policy corresponding to the target key value as a scheduling policy.

Optionally, the corresponding relationship between user scenarios and key values (also referred to as key values) may be preset in the electronic device, and the corresponding relationship may be preset by technicians according to usage requirements, including various user The key value corresponding to the scene. The electronic device may acquire the key value corresponding to the user scenario from the correspondence relationship as the first key value.

Optionally, the electronic device may be preset with a correspondence between power states and key values. The correspondence may be preset by technicians according to usage requirements, including key values corresponding to various power states. The electronic device may acquire the key value corresponding to the power state from the correspondence relationship as the second key value.

As an example, in the case that the power state includes a power mode and a power plan, the correspondence between the power state and the key value may include two correspondences, one of which is the correspondence between the power mode and the key value , another correspondence is the correspondence between a power plan and a key figure. In this case, the electronic device can obtain the key value corresponding to the power mode in the power state from the correspondence between the power mode and the key value, and then obtain the key value from the correspondence between the power plan and the key value. The key value corresponding to the power plan in the power state, and then splicing the key value corresponding to the power mode and the key value corresponding to the power plan to obtain a second key value.

Optionally, the corresponding relationship between system loads (such as load levels) and key values can be preset in the electronic equipment. The corresponding relationship can be preset by technicians according to usage requirements, including various system loads key value. The electronic device may acquire the key value corresponding to the system load from the correspondence relationship as the third key value.

Optionally, when the electronic device determines the target key value based on the first key value, the second key value, and the third key value, the first key value, the second key value, and the third key value can be spliced together to obtain the target key value value. For example, the first key value, the second key value and the third key value can be spliced according to the preset splicing method, for example, the second key value can be spliced at the end of the first key value, and then the third key value value is concatenated at the end of the second key value to obtain the target key value.

Optionally, the electronic device may be preset with a corresponding relationship between key values and scheduling policies. The corresponding relationship may be preset by technicians according to usage requirements, including scheduling policies corresponding to each key value. The electronic device can obtain the scheduling policy corresponding to the target key value from the corresponding relationship. Afterwards, the electronic device can use the obtained scheduling policy to perform resource scheduling on the electronic device.

It is worth noting that when any one or more of the user scenario, power state, and system load changes, the electronic device needs to re-determine the scheduling strategy based on these three. Specifically, step 604 needs to be re-executed to determine the scheduling strategy based on the latest user scenario, power supply status, and system load, that is, it is necessary to re-determine the key values corresponding to the three, and splicing the key values corresponding to the three Get the target key value, and re-determine the scheduling strategy accordingly. In this way, it can be ensured that the determined scheduling strategy can adapt to the latest state of the electronic device, so that the resource allocation of the electronic device can be accurately and reasonably allocated according to the scheduling strategy.

The following takes FIG. 9 as an example to illustrate the process of determining the scheduling policy in step 604 above.

FIG. 9 is a schematic diagram of determining a scheduling policy provided by an embodiment of the present application.

Referring to Figure 9, when any one or more of the user scenario, power state, and system load changes, the electronic device can re-determine the scheduling strategy based on these three, that is, reacquire the key values corresponding to the three, and The key values corresponding to the three are spliced to obtain the target key value, and the scheduling strategy is re-determined accordingly. In particular, since changes in the power state and system load may affect changes in the running state of the background program, if the power state or system load changes without changing the user scene, the sub-scene can be re-determined, if the sub-scene If the scene changes, the user scene can be re-determined, and then the key values corresponding to the user scene, power state, and system load can be obtained again, and the key values corresponding to the three can be spliced to obtain the target key value, and the scheduling can be re-determined based on this Strategy. Wherein, when the power state or system load changes when the user scene does not change, the sub-scene can be re-determined by using the code used to determine the sub-scene in the process of determining the user scene in step 601 above, so, Code reuse can be realized and processing pressure can be reduced.

In the embodiment of the present application, the current user scene of the electronic device is determined, and the power state and system load of the electronic device are determined. Afterwards, obtain the first key value corresponding to the user scenario, obtain the second key value corresponding to the power state, obtain the third key value corresponding to the system load, and determine the target according to the first key value, the second key value and the third key value key value. In the corresponding relationship between the key value and the scheduling policy, the scheduling policy corresponding to the target key value is obtained. In the embodiment of the present application, the reference factors when determining the scheduling strategy are relatively comprehensive, so the subsequent resource scheduling of electronic devices based on the scheduling strategy can accurately realize the reasonable allocation of resources for electronic devices, so as to not only meet user needs, but also Taking into account the system requirements of the electronic equipment itself, it is possible to ensure the stable operation of the electronic equipment while reducing the energy consumption of the electronic equipment and improving the battery life of the electronic equipment. Moreover, in the embodiment of the present application, various reference factors are converted into corresponding key values, and then the corresponding scheduling strategy is directly obtained according to the key values. The operation process is simple, which can reduce system processing pressure and further ensure the stable operation of electronic equipment.

Fig. 10 is a schematic structural diagram of an apparatus for determining a scheduling strategy provided by an embodiment of the present application. This apparatus can be implemented by software, hardware, or a combination of the two to become part or all of a computer device. The computer device can be implemented as shown in Fig. 1 above. The electronic device 100 described as an example. Referring to FIG. 10 , the device includes: a first determination module 1001 , a first acquisition module 1002 , a second determination module 1003 and a second acquisition module 1004 .

The first determining module 1001 is configured to determine the current user scene of the electronic device, and determine the power state and system load of the electronic device;

The first acquiring module 1002 is configured to acquire a first key value corresponding to a user scenario, acquire a second key value corresponding to a power state, and acquire a third key value corresponding to a system load;

The second determining module 1003 is configured to determine the target key value according to the first key value, the second key value and the third key value;

The second acquiring module 1004 is configured to acquire a scheduling policy corresponding to the target key value in the corresponding relationship between the key value and the scheduling policy, and the scheduling policy is used for resource scheduling of the electronic device.

Optionally, the first determination module 1001 is used for:

Obtain application running information of the electronic device, where the application running information includes focus application information, and the focus application information includes the application type and application running status of the focus application;

Determine user scenarios based on application running information.

Optionally, the first determination module 1001 is used for:

Determine the main scene according to the application type in the focus application information;

Determine at least one sub-scene according to the main scene, the application running state in the focus application information, the non-focus application information and the background application information;

A sub-scene with the highest priority is selected from at least one sub-scene, and the main scene and one sub-scene are user scenes.

Optionally, the device also includes:

The detection module is used to detect the working state of the system;

The first determining module 1001 is used for:

If the system working state is changed to the idle state, when the application running information indicates that the applications are not in use by the user, it is determined that the user scene is an idle scene.

Optionally, the first determining module 1001 is used for:

Obtain IO load information;

Determine the user scenario based on application running information and IO load information.

Optionally, the power state includes a power mode and a power plan, and the first determining module 1001 is used for:

If the power mode change event and the power plan change event are detected, the power state is determined according to the power mode change event and the power plan change event.

Optionally, the second determination module 1003 is used for:

The first key value, the second key value and the third key value are spliced together to obtain the target key value.

Optionally, the device also includes:

The trigger module is used to trigger the first acquisition module 1002 to acquire the first key value corresponding to the user scene and the second key value corresponding to the power state if any one or more of the user scene, power state, and system load changes. value, and obtain the third key value corresponding to the system load.

In the embodiment of the present application, the current user scene of the electronic device is determined, and the power state and system load of the electronic device are determined. Afterwards, obtain the first key value corresponding to the user scenario, obtain the second key value corresponding to the power state, obtain the third key value corresponding to the system load, and determine the target according to the first key value, the second key value and the third key value key value. In the corresponding relationship between the key value and the scheduling policy, the scheduling policy corresponding to the target key value is obtained. In the embodiment of the present application, the reference factors when determining the scheduling strategy are relatively comprehensive, so the subsequent resource scheduling of electronic devices based on the scheduling strategy can accurately realize the reasonable allocation of resources for electronic devices, so as to not only meet user needs, but also Taking into account the system requirements of the electronic equipment itself, it is possible to ensure the stable operation of the electronic equipment while reducing the energy consumption of the electronic equipment and improving the battery life of the electronic equipment. Moreover, in the embodiment of the present application, various reference factors are converted into corresponding key values, and then the corresponding scheduling strategy is directly obtained according to the key values. The operation process is simple, which can reduce system processing pressure and further ensure the stable operation of electronic equipment.

It should be noted that: when the scheduling policy determination device provided in the above embodiment determines the scheduling policy, it only uses the division of the above-mentioned functional modules as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional modules according to needs. , that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.

The functional units and modules in the above-mentioned embodiments can be integrated into one processing unit, or each unit can exist separately physically, or two or more units can be integrated into one unit, and the above-mentioned integrated units can use hardware It can also be implemented in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the protection scope of the embodiments of the present application.

The dispatching policy determination device provided by the above-mentioned embodiment and the embodiment of the dispatching policy determination method belong to the same concept. For the specific working process and technical effects of the units and modules in the above-mentioned embodiment, please refer to the method embodiment, and will not repeat them here. .

In the above embodiments, all or part may be implemented by software, hardware, firmware or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network or other programmable devices. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be accessed from a website, computer, server, or data center Transmission to another website site, computer, server or data center by wired (such as: coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (such as: infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer, or may be a data storage device such as a server or a data center integrated with one or more available media. The available medium may be a magnetic medium (such as a floppy disk, a hard disk, a magnetic tape), an optical medium (such as a digital versatile disc (Digital Versatile Disc, DVD)) or a semiconductor medium (such as a solid state disk (Solid State Disk, SSD)) wait.

The above-mentioned optional embodiments provided by the application are not intended to limit the application. Any modifications, equivalent replacements, improvements, etc. made within the technical scope of the disclosure of the application shall be included in the scope of the application. within the scope of protection.

Claims (11)

1. A scheduling strategy determination method, characterized in that the method comprises: Determine the current user scenario of the electronic device, and determine the power state and system load of the electronic device; Obtain a first key value corresponding to the user scenario, obtain a second key value corresponding to the power state, and obtain a third key value corresponding to the system load; determining a target key value according to the first key value, the second key value, and the third key value; In the corresponding relationship between the key value and the scheduling policy, the scheduling policy corresponding to the target key value is acquired, and the scheduling policy is used to perform resource scheduling on the electronic device. 2. The method according to claim 1, wherein the determining the current user scene of the electronic device comprises: Acquire application running information of the electronic device, where the application running information includes focus application information, and the focus application information includes an application type and an application running state of the focus application; The user scenario is determined according to the application running information. 3. The method according to claim 2, wherein the application running information further includes non-focus application information and background application information, and determining the user scenario according to the application running information comprises: determining the main scene according to the application type in the focus application information; Determine at least one sub-scene according to the main scene, the application running state in the focus application information, the non-focus application information, and the background application information; Selecting a sub-scene with the highest priority from the at least one sub-scene, the main scene and the one sub-scene being the user scene. 4. The method of claim 2, further comprising: Check the working status of the system; The determining the user scenario according to the application running information includes: If the system working state is changed to an idle state, when the application running information indicates that the applications are not in use by the user, the user scene is determined to be an idle scene. 5. The method according to claim 2, wherein the determining the user scenario according to the application running information comprises: Obtain input and output IO load information; Determine the user scenario according to the application running information and the IO load information. 6. The method according to any one of claims 1-5, wherein the power state includes a power mode and a power plan, and determining the power state of the electronic device includes: If a power mode change event and a power plan change event are detected, the power state is determined according to the power mode change event and the power plan change event. 7. The method according to any one of claims 1-6, wherein the determining the target key value according to the first key value, the second key value and the third key value comprises: Splicing the first key value, the second key value and the third key value to obtain the target key value. 8. The method according to any one of claims 1-7, further comprising: If any one or more of the user scenario, the power state, and the system load changes, re-execute the obtaining of the first key value corresponding to the user scenario, and obtain the key value corresponding to the power state. The second key value, and the step of obtaining the third key value corresponding to the system load and subsequent steps. 9. A scheduling policy determination device, characterized in that the device comprises: A first determining module, configured to determine the current user scene of the electronic device, and determine the power state and system load of the electronic device; A first acquiring module, configured to acquire a first key value corresponding to the user scenario, acquire a second key value corresponding to the power state, and acquire a third key value corresponding to the system load; A second determining module, configured to determine a target key value according to the first key value, the second key value, and the third key value; The second obtaining module is configured to obtain a scheduling strategy corresponding to the target key value in the corresponding relationship between the key value and the scheduling strategy, and the scheduling strategy is used to perform resource scheduling on the electronic device. 10. A computer device, characterized in that the computer device comprises a memory, a processor, and a computer program stored in the memory and operable on the processor, the computer program being executed by the processor When realizing the method as described in any one of claims 1-8. 11. A computer-readable storage medium, characterized in that instructions are stored in the computer-readable storage medium, and when it is run on a computer, the computer executes the method according to any one of claims 1-8 .

Images