WO2023221720A1

WO2023221720A1 - Resource scheduling method and apparatus

Info

Publication number: WO2023221720A1
Application number: PCT/CN2023/089131
Authority: WO
Inventors: 尚明
Original assignee: 荣耀终端有限公司
Priority date: 2022-05-16
Filing date: 2023-04-19
Publication date: 2023-11-23
Also published as: WO2023221720A9; CN117112187A

Abstract

Embodiments of the present application provide a resource scheduling method and apparatus, which are applied to an electronic device. An operating system of the electronic device is a Windows system. The method comprises: on the basis of a system probe module of the electronic device, acquiring basic state information of the electronic device; processing the basic state information, and obtaining running state information of the electronic device, the running state information of the electronic device comprising at least one of an application running state, a system operating state, and system power supply mode information of the electronic device; on the basis of the running state information of the electronic device, determining an application scenario in which the electronic device is located; on the basis of the application scenario in which the electronic device is located, determining a target resource scheduling policy matching the application scenario in which the electronic device is located, the target resource scheduling policy comprising a central processing unit power consumption scheduling policy; and according to the target resource scheduling policy, performing resource scheduling on the electronic device.

Description

Resource scheduling method and device

This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on May 16, 2022, with the application number 202210530837.1 and the invention title "Resource Scheduling Method and Device", the entire content of which is incorporated into this application by reference. .

Technical field

The present application relates to the technical field of resource scheduling, and in particular, to a resource scheduling method and device.

Background technique

Currently, electronic devices can use Windows as the operating system. When the hardware configuration is the same, there is not much difference in performance and battery life between electronic devices equipped with Windows 10 system and electronic devices equipped with Windows 11 system. The reason why electronic devices equipped with different operating systems have little difference in performance and battery life is the resource scheduling of electronic devices. From this, it can be seen that the resource scheduling of electronic devices is an urgent problem that needs to be solved.

Contents of the invention

This application provides a resource scheduling method and device, aiming to solve the resource scheduling problem of electronic equipment. In order to achieve the above objectives, this application provides the following technical solutions:

In the first aspect, this application provides a resource scheduling method. The method is applied to electronic equipment. The operating system of the electronic equipment is a Windows system. The method includes: a system probe module based on the electronic equipment obtains basic status information of the electronic equipment; The information is processed to obtain the operating status information of the electronic device. The operating status information of the electronic device includes at least one of the application operating status of the electronic device, the system working status and the system power mode information; the electronic device is determined based on the operating status information of the electronic device. The application scenario in which the electronic device is located; based on the application scenario in which the electronic device is located, a target resource scheduling strategy that matches the application scenario in which the electronic device is located is determined. The target resource scheduling strategy includes a central processor power consumption scheduling strategy; according to the target resource scheduling strategy Resource scheduling for electronic equipment. The target resource scheduling strategy can be called the target scheduling strategy.

In this embodiment, the electronic device equipped with the Windows system can obtain the basic status information of the electronic device based on the system probe module; the basic status information is processed to obtain the operating status information of the electronic device. The operating status information of the electronic device includes the electronic device. At least one of the application running status of the device, the system working status and the system power mode information; determining the application scenario of the electronic device based on the running status information of the electronic device; determining the application scenario related to the electronic device based on the application scenario of the electronic device. The target resource scheduling strategy matches the application scenario. The target resource scheduling strategy includes the central processor power consumption scheduling strategy. Resource scheduling is performed on electronic devices according to the target resource scheduling strategy to ensure that resources are reasonably allocated under the application scenario as much as possible. Reduce the power consumption of electronic devices, improve the battery life of electronic devices, and reduce the impact on mobile application scenarios. Mobile application scenarios are an application scenario. Because the electronic device can reasonably allocate resources according to the application scenario in which the electronic device is currently located, so that the resources can meet the resource requirements of the application scenario, ensure the smooth operation of the application in the application scenario, and improve the user experience. Among them, the running status information of the electronic device includes at least one of the application running status of the electronic device, the system working status and the system power mode information. Therefore, the electronic device can comprehensively determine the application scenario based on various information and improve the accuracy.

In this example, the basic status information can be called first-level events, first-level information or first-level data, etc. The basic status information can be obtained through the first-level probe in the system probe module, and the running status information can be called second-level events. , second-level letter Information or secondary data, etc., can also be called a mixed state. Running status information can be obtained through the secondary probe in the system probe module. The primary probe and the secondary probe can be interfaces in the Windows system. After obtaining the basic status information, the basic status information is summarized and analyzed to obtain the running status. information.

Optionally, the basic status information includes: at least one of basic operation information related to the application, audio and video usage information, power mode usage information, external device usage information, and display usage information. The basic operation information related to the application is at least Including the application name and application type of the focus application, the electronic device can obtain running status information by integrating multiple basic information, so that the running status information can cover multiple aspects of information.

Optionally, the basic running information related to the application includes: the application name and application type of the focused application, the application name and application type of the non-focused application, the application name and application type of the background application; the audio and video usage information includes: whether to use graphics processing information about the device, whether to use the audio module, and whether to use the camera; power mode usage information includes: the usage mode of the operating system and the power supply mode of the electronic device; external device usage information includes: information about whether to use external devices; display screen Usage information includes: screen bright information of the display screen, lock screen unlock information of the display screen, and information of whether the electronic device is in a closed state.

The basic operation information related to the application can be obtained through the process probe, focus change (full screen) probe, and minimization probe in the system probe module. Audio and video usage information can be obtained through the GPU probe, audio probe, and Camera probe in the system probe module. For example, the GPU probe obtains information about whether the graphics processor is used, the audio probe obtains information about whether the audio module is used, and the Camera probe Need to get information about whether the camera is used. Power mode usage information can be obtained through the AC/DC power probe and system mode probe in the system probe module. For example, the AC/DC power probe obtains the power supply mode of the electronic device, such as DC power supply or AC power supply. AC power supply instructions Using the power adapter, the system mode probe can obtain the usage mode of the operating system, which includes optimal energy efficiency, balance, and optimal performance.

Optionally, processing the basic status information to obtain the running status information of the electronic device includes: obtaining the application name and application type of the focus application, the application name and application type of the non-focus application, and the application name of the background application from the basic status information and application type; if the audio and video usage information in the basic status information indicates that the application uses the graphics processor and/or camera, determine that the running state of the application is the video state, and the application includes at least one of a focused application, a non-focused application, and a background application; If the audio and video usage information in the basic status information indicates that the application uses the audio module, determine the running status of the application to be the audio status; if the audio and video usage information in the basic status information indicates that the application uses the graphics processor, camera and audio module, determine the running status of the application For audio and video status.

When determining the running state of the application, focus applications, non-focus applications and background applications can be used. If one of these applications uses a graphics processor and/or camera, the running state of the application is determined to be the video state, so that once the focus application is switched For applications using a graphics processor, the resource scheduling of the electronic device is matched to the video status so that the focused application can run smoothly after switching.

Optionally, processing the basic status information to obtain the operating status information of the electronic device includes: determining the current mode of the electronic device according to the power mode of the operating system; if the power supply mode of the electronic device is DC power supply, determining whether the electronic device has Use a power adapter; if the power supply method of the electronic device is regarded as AC power supply, determine whether the electronic device uses a power adapter to determine whether the electronic device uses a power adapter and is in a certain mode, so that application scenarios can be distinguished by whether a power adapter is used and the mode. . The mode the electronic device is currently in can be one of optimal energy efficiency, balance, and optimal performance. If the AC/DC power probe detects that it is in the AC state, it means that the power adapter is used; if the AC/DC power probe detects that it is in the AC state, it means that the power adapter is not used; the AC/DC power probe And the system mode probe summarizes the system power mode information, such as using the power adapter and being in the best energy efficiency mode.

Optionally, the basic status information includes external device usage information and display screen usage information. The basic status information is processed to obtain the operating status information of the electronic device, including: if the external device inputs an event to the electronic device and the display screen is in a bright screen and unlocked state , the electronic device is not in a closed state, confirm that the electronic device is in a state of use by the user; if the external device inputs an event to the electronic device, the display is in a bright screen unlocked state, and the electronic device is not in a closed state, determine that the electronic device is in a state that is not in use by the user. status; if the electronic device is in a closed state and/or the display screen is in a bright-screen unlocked state, determine that the electronic device is in a state that is not in use by the user, and determine whether the electronic device has input events from the external device and whether the display screen is being used. Whether it is in a user-used state to allocate different target resource scheduling policies when the user is using or not using it. Events input by external devices to electronic devices can be detected through the mouse and keyboard peripheral probes. Whether the display is on can be detected through the PC bright screen probe. Whether the screen is in a locked state can be detected through the Windows lock probe. When the cover is closed, the PC lid closing probe detection.

Optionally, determining the application scenario in which the electronic device is located based on the operating status information of the electronic device includes: determining the first application scenario in which the electronic device is located based on the first part of the information in the operating status information; and determining the first application scenario in which the electronic device is located based on the second part of the operating status information. For part of the information, the first application scenario is adjusted to determine the second application scenario where the electronic device is located. The second application scenario where the electronic device is located is the application scenario where the electronic device is located. The first application scenario can be called the original application scenario, and the second application scenario can be called the target application scenario. After the first application scenario is initially determined, it is adjusted so that the target application scenario can correspond to the first part of the information and the second part of the information. .

Optionally, determining the first application scenario in which the electronic device is located based on the first part of the information in the running status information includes: determining the first application scenario based on the application running status in the running status information and the system load of the electronic device; The second part of the information in the status information adjusts the first application scenario and determines the second application scenario in which the electronic device is located. If the system working status information in the running status information indicates that the electronic device is in a state used by the user, the second part of the information is adjusted. One application scenario is determined as the second application scenario; if the system working status information in the running status information indicates that the electronic device is in a state that is not used by the user, it is determined that the electronic device is in an idle scenario, and the idle scenario is the second application scenario. In addition, the system power mode information can supplement and improve the second application scenario, such as adding system power mode information to the second application scenario, such as adding that the power adapter is currently in the best energy efficiency mode, etc. System load is optional when determining the first application scenario.

Optionally, determining a target resource scheduling policy that matches the application scenario of the electronic device based on the application scenario in which the electronic device is located includes: if the electronic device does not use a power adapter, based on the application scenario and system power supply of the electronic device mode information to determine a target resource scheduling strategy that matches the application scenario of the electronic device; the method also includes: if the electronic device uses a power adapter, it is prohibited to determine based on the application scenario of the electronic device that matches the application scenario of the electronic device. Matching target resource scheduling policy. The electronic device can determine the target resource scheduling strategy based on the application scenario and system power mode information, so that the target resource scheduling strategy can match the application scenario and system power mode information. If there is no system power mode information, the target resource scheduling strategy can be determined based on the application scenario. System power mode information is optional when determining target resource scheduling policies.

Optionally, the CPU power consumption scheduling strategy includes a first sub-strategy and a second sub-strategy. The second sub-strategy is a dynamic tuning technology strategy determined according to the first sub-strategy; the electronic device is adjusted for resource scheduling according to the target resource scheduling strategy. The method includes: if the hardware platform type is the first type, resource scheduling is performed on the electronic device according to the first sub-policy; if the hardware platform type is the second type, resource scheduling is performed on the electronic device according to the second sub-policy.

Optionally, the method also includes: if the target resource scheduling strategy fails, obtain a preset self-built strategy; perform resource scheduling on the electronic device according to the self-built strategy to improve the target resource scheduling strategy. The self-built strategy can be in conjunction with the electronic device. A policy related to the scenario the device is currently in. For example, in the browser scenario, the self-built policy is a browser scenario performance control strategy. Resource scheduling is completed through the self-built policy, and the scheduling policy is supplemented and improved by the self-built policy.

In a second aspect, this application provides a resource scheduling device. The device is applied to electronic equipment. The operating system of the electronic device is a Windows system. The device includes: an acquisition unit for acquiring the basic status of the electronic device based on the system probe module of the electronic device. Information; process the basic status information to obtain the operating status information of the electronic device. The operating status information of the electronic device includes at least one of the application operating status of the electronic device, the system working status and the system power mode information; the determining unit is used to Determine the application scenario of the electronic device based on the operating status information of the electronic device; determine the target resource scheduling strategy that matches the application scenario of the electronic device based on the application scenario of the electronic device. The target resource scheduling strategy includes the central processor Power consumption scheduling strategy; scheduling unit, used to schedule resources for electronic devices according to the target resource scheduling strategy, to ensure that resources are reasonably allocated in application scenarios as much as possible, thereby reducing the power consumption of electronic devices, improving the battery life of electronic devices, and reducing the impact on mobile devices. The impact of application scenarios. Because the electronic device can reasonably allocate resources according to the application scenario in which the electronic device is currently located, so that the resources can meet the resource requirements of the application scenario, ensure the smooth operation of the application in the application scenario, and improve the user experience. Among them, the running status information of the electronic device includes at least one of the application running status of the electronic device, the system working status and the system power mode information. Therefore, the electronic device can comprehensively determine the application scenario based on various information and improve the accuracy.

In this example, the basic status information can be called first-level events, first-level information or first-level data, etc. The basic status information can be obtained through the first-level probe in the system probe module, and the running status information can be called second-level events. , secondary information or secondary data, etc. The running status information can be obtained through the secondary probe in the system probe module. The primary probe and secondary probe can be the interface in the Windows system. After obtaining the basic status information Summarize and analyze basic status information to obtain running status information.

Optionally, the basic running information related to the application includes: the application name and application type of the focused application, the application name and application type of the non-focused application, the application name and application type of the background application; the audio and video usage information includes: whether to use graphics processing information about the device, whether to use the audio module, and whether to use the camera; power mode usage information includes: the power mode of the operating system and the power supply mode of the electronic device; external device usage information includes: information about whether to use external devices; display screen Usage information includes: screen bright information of the display screen, lock screen unlock information of the display screen, and information of whether the electronic device is in a closed state. The basic operation information related to the application can be obtained through the process probe, focus change (full screen) probe, and minimization probe in the system probe module. Audio and video usage information can be obtained through the GPU probe, audio probe, and Camera probe in the system probe module. For example, the GPU probe obtains information about whether the graphics processor is used, the audio probe obtains information about whether the audio module is used, and the Camera probe Need to get information about whether the camera is used. Power mode usage information can be obtained through the AC/DC power probe and system mode probe in the system probe module. For example, the AC/DC power probe obtains the power supply mode of the electronic device, such as DC power supply or AC power supply. AC power supply instructions Using the power adapter, the system mode probe can obtain the usage mode of the operating system, the usage mode of the operating system, and the operating system Usage modes include optimal energy efficiency, balance, and optimal performance.

Optionally, the acquisition unit processes the basic status information to obtain the running status information of the electronic device, including: obtaining the application name and application type of the focus application, the application name and application type of the non-focus application, and the application type of the background application from the basic status information. Application name and application type; if the audio and video usage information in the basic status information indicates that the application uses a graphics processor and camera, determine that the running state of the application is the video state, and the application includes at least one of a focused application, a non-focused application, and a background application; If the audio and video usage information in the basic status information indicates that the application uses the audio module, determine the running status of the application to be the audio status; if the audio and video usage information in the basic status information indicates that the application uses the graphics processor, camera and audio module, determine the running status of the application For audio and video status.

Optionally, the acquisition unit processes the basic status information to obtain the running status information of the electronic device, including: determining the current mode of the power module according to the power mode of the operating system; if the power supply mode of the electronic device is DC power supply, determining the mode of the electronic device. The device does not use a power adapter; if the power supply method of the electronic device is regarded as AC power supply, make sure the electronic device uses a power adapter.

Optionally, the basic status information includes external device usage information and display screen usage information. The acquisition unit processes the basic status information to obtain the running status information of the electronic device including: if the external device inputs an event to the electronic device and the display screen is on In the unlocked state and the electronic device is not in a closed state, it is determined that the electronic device is in a state for use by the user; if the external device inputs an event to the electronic device, the display is in a bright-screen unlocked state, and the electronic device is not in a closed state, it is determined that the electronic device is in a user-friendly state. Not in use; if the electronic device is in a closed state and/or the display is in a bright-screen unlocked state, it is determined that the electronic device is in a state that is not in use by the user.

Optionally, the determining unit determines the application scenario in which the electronic device is located based on the operating status information of the electronic device, including: determining the first application scenario in which the electronic device is located based on the first part of the information in the operating status information; The second part of the information adjusts the first application scenario and determines the second application scenario where the electronic device is located. The second application scenario where the electronic device is located is the application scenario where the electronic device is located.

In a third aspect, the present application provides an electronic device. The electronic device includes: a memory and one or more processors; wherein the memory is used to store computer program code, and the computer program code includes computer instructions; when the computer instructions are executed by the processor , causing the electronic device to execute the above method.

In a fourth aspect, the present application provides a computer-readable storage medium. The computer-readable storage medium stores a computer program. When the computer program is run on an electronic device, it causes the electronic device to execute the above method.

Based on the implementation methods provided in the above aspects, this application can also be further combined to provide more implementation methods.

Description of the drawings

In order to explain the technical methods of the embodiments of the present application more clearly, the drawings required to be used in the embodiments will be briefly introduced below.

Figure 1 is a schematic structural diagram of an electronic device provided by this application;

Figure 2 is a software structure block diagram of the electronic device provided by this application;

Figure 3 is a schematic diagram of resource scheduling for electronic equipment provided by this application;

Figure 4 is a schematic structural diagram of the system probe module provided by this application;

Figure 5 is a signaling diagram of the resource scheduling method provided by this application;

Figure 6 is another signaling diagram of the resource scheduling method provided by this application;

Figure 7 is a schematic diagram of resource scheduling in the browser scenario provided by this application;

Figure 8 is a schematic structural diagram of a resource scheduling device provided by this application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. The terminology used in the following examples is for the purpose of describing specific embodiments only and is not intended to limit the application. As used in the specification and appended claims of this application, the singular expressions "a", "an", "said", "above", "the" and "the" are intended to also Expressions such as "one or more" are included unless the context clearly indicates otherwise. It should also be understood that in the embodiments of this application, "one or more" refers to one, two or more than two; "and/or" describes the association relationship of associated objects, indicating that three relationships can exist; for example, A and/or B can mean: A alone exists, A and B exist simultaneously, and B exists alone, where A and B can be singular or plural. The character "/" generally indicates that the related objects are in an "or" relationship.

Reference in this specification to "one embodiment" or "some embodiments" or the like means that a particular feature, structure or characteristic described in connection with the embodiment is included in one or more embodiments of the application. Therefore, the phrases "in one embodiment", "in some embodiments", "in other embodiments", "in other embodiments", etc. appearing in different places in this specification are not necessarily References are made to the same embodiment, but rather to "one or more but not all embodiments" unless specifically stated otherwise. The terms “including,” “includes,” “having,” and variations thereof all mean “including but not limited to,” unless otherwise specifically emphasized.

The plurality involved in the embodiments of this application refers to more than or equal to two. It should be noted that in the description of the embodiments of this application, words such as "first" and "second" are only used for the purpose of distinguishing the description, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating. Or suggestive order.

In order to describe the following embodiments clearly and concisely, a brief introduction to related concepts or technologies is first given:

Focus Window refers to the window that has focus. The focused window is the only window that can receive keyboard input. The way the focus window is determined is related to the system's Focus Mode. The top-level window of the focused window is called the active window (Active Window). Only one window can be active at a time. The focus window is most likely the window that the user currently needs to use. The focus window may be the window of the focus application (Application, APP), and the focus APP is the APP currently running in the foreground that can receive operations such as keyboard input and mouse operations.

A non-focus APP is an APP that is running in the foreground but cannot currently receive keyboard input, mouse operations, etc. That is, it generally refers to an APP that is running in the foreground but has no operations by the user.

A background APP is an APP that has been minimized to run in the background.

A process includes multiple threads, and threads can create windows. The focus process is the process to which the thread that created the focus window belongs.

Long-term turbo power consumption (Power Limit1, PL1) refers to the power consumption of the CPU under normal load, which is equivalent to the thermal design power consumption. The CPU's operating power consumption does not exceed PL1 most of the time.

Short-term turbo power consumption (Power Limit2, PL2) refers to the highest power consumption that the CPU can achieve in a short period of time, which has a duration limit. Generally, PL2 is larger than PL1, and PL1 and PL2 are The name of the platform, in 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).

CPMinCores refers to the minimum proportion of the number of logical processors that can be running. The value range can be 0 to 100. For example, if it is set to 20, if there are 10 logical processors, at least 2 logical processors are running. state.

CPMaxCores refers to the maximum proportion of the number of logical processors that can be running. The value range can be 0 to 100. For example, if it is set to 80, if there are 10 logical processors, up to 8 logical processors are running. state.

MaxPerformance refers to the upper limit of CPU performance, which can range from 0 to 100. For example, if it is set to 80, the CPU performance can reach 80% of the maximum performance.

MinPerformance refers to the lower limit of CPU performance, which can range from 0 to 100. For example, if it is set to 20, the CPU performance can be reduced to 20% of the maximum performance.

CPU energy efficiency ratio (Energy Performance Preference, EPP) is used to reflect the scheduling tendency of the CPU, and its value range can be 0 to 255. The smaller the CPU energy efficiency ratio, the CPU tends to have high performance; the higher the CPU energy efficiency ratio, the CPU tends to have low power consumption.

Energy efficiency-performance optimization gear (Energy Performance Optimize Gear, EPO Gear) is used to represent the intensity of DTT in adjusting the CPU energy efficiency ratio (EPP). The value range can be 1 to 5. The larger the value, the more energy-efficient it is when adjusting EPP; The smaller the value, the more performance-oriented the EPP adjustment is.

Electronic devices can use Windows as the operating system. When the hardware configuration is the same, there is not much difference in performance and battery life between electronic devices equipped with Windows 10 system and electronic devices equipped with Windows 11 system. The reason why electronic devices equipped with different operating systems have little difference in performance and battery life is the resource scheduling of electronic devices. The resource scheduling of electronic devices can be the resource scheduling mechanism configured by the Windows system. The resource scheduling mechanism of the Windows system is oriented to A common resource scheduling mechanism for all applications, that is, electronic devices can use the same resource scheduling mechanism for different applications.

The resources required by different applications may be different. For example, the resources required by office applications are smaller than those required by game applications. If the resource scheduling mechanism of the Window system is set based on the game application, then there will be a waste of resources when the electronic device uses the resource scheduling mechanism to configure resources for the office application. If the resource scheduling mechanism of the Windows system is set according to the office application, then there will be a problem of insufficient resources when the electronic device uses this resource scheduling mechanism to configure resources for the game application. Therefore, the electronic device using a universal resource scheduling mechanism cannot guarantee that the resources are used in all applications. Reasonable allocation in scenarios. In some application scenarios, there may be excessive performance problems, which reduces the battery life of electronic devices, thereby affecting the most important mobile application scenario experience of electronic devices. The mobile application scenario refers to the electronic device not connected to an external power supply. Battery powered scenarios in electronic devices. If the battery life of the electronic device is reduced and the electronic device is powered by the battery, the use time of the electronic device is shortened, which affects the use of the electronic device. For example, when the user is outdoors and there is no external power supply to connect, the usable time of the electronic device is shortened and the electronic device may not be able to be used. Satisfy users' use of electronic devices.

This application provides a resource scheduling method. The resource scheduling method can use two-level probes to identify application scenarios to determine the current application scenario of the electronic device. The scheduling strategy is determined based on the current application scenario of the electronic device. According to the scheduling Strategies for resource scheduling. Through this resource scheduling method, the electronic device can reasonably allocate resources for the electronic device according to the current application scenario of the electronic device, and ensure that the resources are reasonably allocated under the application scenario as much as possible, thereby reducing the power consumption of the electronic device, improving the battery life of the electronic device, and reducing the Impact on mobile application scenarios. Because electronic devices can Reasonably allocate resources according to the current application scenario of the electronic device, so that the resources can meet the resource requirements of the application scenario, ensure the smooth operation of the application in the application scenario, and improve the user experience. The two-level probe can also be called one of two-level events, two-level information, two-level data, etc.

The electronic device can be a tablet computer, desktop, laptop, notebook computer, ultra-mobile personal computer (UMPC), handheld computer, netbook, personal digital assistant (Personal Digital Assistant, PDA) and other devices. The structural diagram of the electronic device is shown in Figure 1. The electronic device may include: processor, external memory interface, internal memory, Universal Serial Bus (USB) interface, charging management module, power management module, battery, antenna 1. Antenna 2, mobile communication module, wireless communication module, sensor module, buttons, motors, indicators, audio modules, cameras, display screens, and Subscriber Identification Module (SIM) card interfaces, etc. The audio module can include speakers, receivers, microphones, headphone jacks, etc. The sensor module can include pressure sensors, gyroscope sensors, air pressure sensors, magnetic sensors, acceleration sensors, distance sensors, proximity light sensors, fingerprint sensors, temperature sensors, and touch sensors. , ambient light sensor, etc.

It can be understood that the structure illustrated in this embodiment does not constitute a specific limitation on the electronic device. In other embodiments, the electronic device may include more or fewer components than illustrated, some components may be combined, some components may be separated, or components may be arranged differently. The components illustrated may be implemented in hardware, software, or a combination of software and hardware. The interface connection relationships between the modules illustrated in this embodiment are only schematic illustrations and do not constitute structural limitations on the electronic equipment. In other embodiments, the electronic device may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

The processor may include one or more processing units. For example, the processor may include an application processor (Application Processor, AP), a modem processor, a graphics processor (Graphics Processing Unit, GPU), and an image signal processor (Image processor). 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. Among them, different processing units can be independent devices or integrated in one or more processors. The processor is the nerve center and command center of electronic equipment. The controller can generate operation control signals based on the instruction operation code and timing signals to complete the control of fetching and executing instructions.

The external memory interface can be used to connect external memory cards, such as Micro SD cards, to expand the storage capabilities of electronic devices. The external memory card communicates with the processor through the external memory interface to implement data storage functions. For example, save network configuration information, scheduling policy and other files in an external memory card. Internal memory may be used to store computer executable program code, which includes instructions. The processor executes instructions stored in the internal memory to perform various functional applications and data processing of the electronic device. For example, in this application, the processor causes the electronic device to execute the resource scheduling method provided by this application by running instructions stored in the internal memory.

The charging management module is used to receive charging input from the charger. Wherein, the charger may be a wired charger. While the charging management module charges the battery, it can also provide power to electronic devices through the power management module.

The power management module is used to connect the battery, charging management module and processor. The power management module receives input from the battery and/or charge management module to power the processor, internal memory, external memory, display, wireless communication module, etc. In some embodiments, the power management module and the charging management module can also be provided in the same device.

Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in an electronic device can be used to cover a single or multiple communication bands. Different antennas can also be reused to improve antenna utilization. For example: Antenna 1 can be reused as a diversity antenna for a wireless LAN. In other embodiments, antennas may be used in conjunction with tuning switches.

Mobile communication modules can provide wireless communication solutions including 2G/3G/4G/5G applied to electronic devices. Wireless communication modules can provide applications in electronic devices including Wireless Local Area Networks (WLAN) (such as Wireless Fidelity (Wi-Fi) network), Bluetooth (Bluetooth, BT), Global Navigation Satellite System ( Global Navigation Satellite System (GNSS), Frequency Modulation (FM), Near Field Communication (NFC), Infrared (IR) and other wireless communication solutions.

Electronic devices implement display functions through GPUs, displays, and application processors. GPU is an image processing microprocessor that connects the display and application processor. GPUs are used to perform mathematical and geometric calculations for graphics rendering. The processor may include one or more GPUs that execute program instructions to generate or alter display information. Electronic devices can achieve shooting functions through ISPs, cameras, video codecs, GPUs, displays, and application processors. Electronic devices can implement audio functions through audio modules, speakers, receivers, microphones, headphone jacks, and application processors. Such as music playback, recording, etc.

Pressure sensors are used to sense pressure signals and convert pressure signals into electrical signals. Gyroscope sensors can be used to determine the motion posture of electronic devices. Air pressure sensors measure air pressure. Magnetic sensors include Hall sensors. Electronic devices can use magnetic sensors to detect the opening and closing of the flip holster. Acceleration sensors can detect the acceleration of electronic devices in all directions (usually three axes). Distance sensor for measuring distance.

Proximity light sensors may include, for example, light emitting diodes (LEDs) and light detectors, such as photodiodes. The light emitting diode may be an infrared light emitting diode. Electronic devices emit infrared light through light-emitting diodes. Electronic devices use photodiodes to detect infrared reflected light from nearby objects. The ambient light sensor is used to sense ambient light brightness. The fingerprint sensor is used to collect fingerprints. Temperature sensor is used to detect temperature. Touch sensor, also known as "touch device". The touch sensor can be set on the display screen, and the touch sensor and the display screen form a touch screen, also called a "touch screen".

Buttons include power button, volume button, etc. The motor can produce vibration cues. The motor can be used to vibrate for incoming calls or for touch vibration feedback. The indicator can be an indicator light, which can be used to indicate charging status, power changes, or can be used to indicate messages, missed calls, notifications, etc. The SIM card interface is used to connect the SIM card. The SIM card can be inserted into or removed from the SIM card interface to achieve contact and separation from the electronic device.

The software system of the above-mentioned electronic device can adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. The embodiment of the present invention takes the Windows system with a layered architecture as an example to illustrate the software structure of the electronic device. Figure 2 is a software structure block diagram of an electronic device according to an embodiment of the present application.

The layered architecture divides the software into several layers, and each layer has clear roles and division of labor. The 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 2, the application layer can include music, video, games, office, social networking and other APPs. The application layer can also include a system probe module, a scene recognition engine, an execution scheduling engine, a policy configuration module and a housekeeper interface module. Only some applications are shown in the figure. The application layer may also include other applications, such as shopping applications, browsers, etc., which are not limited in this application. Among them, the system probe module is used to report status to the scene recognition engine; the scene recognition engine is used to complete the identification of application scenarios based on the status reported by the system probe module, and determine the scheduling policy based on the identified application scenarios. strategy; the execution scheduling engine is used to schedule the firmware layer according to the scheduling policy.

The policy configuration module is used to send multiple preconfigured scheduling strategies to the scene recognition engine. After the scene recognition engine recognizes the application scenario, it searches for a scheduling policy that matches the recognized application scenario from the multiple scheduling policies. The housekeeper interface module is used to provide the currently used system power mode to the scene recognition module. The scene recognition engine can select a scheduling strategy that matches the currently used system power mode and the current application scenario. The system power mode may be referred to as system power mode information.

The subsystem dynamic link library includes application programming interface (API) modules, which include Windows API, Windows native API, etc. Among them, both Windows API and Windows native API can provide system call entry and internal function support for APPs. The difference is that Windows native API is an API native to the Windows system. For example, Windows API can include user.dll, kernel.dll, and Windows native API can include ntdll.dll. Among them, user.dll is the Windows user interface interface, which can be used to perform operations such as creating windows and sending messages. kernel.dll is used to provide an interface for applications to access the kernel. ntdll.dll is an important Windows NT kernel-level file. When Windows starts, ntdll.dll resides in a specific write-protected area of memory so that other programs cannot occupy this memory area.

The driver layer can include process manager, virtual memory manager, security reference monitor, input output (Input Output, IO) manager, power manager (not shown in the figure), Windows Management Instrumentation (WMI) Plug-in, event driver (Event driver), system and chip (Operating System to System on Chip, OS2SOC) driver.

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, protects operating system resources, and performs runtime object protection and monitoring.

The I/O manager performs device-independent input/output and calls the appropriate device driver for further processing.

The power manager manages changes to a device's power state.

The WMI plug-in allows the execution scheduling engine to send scheduling policies to the firmware layer; the Event driver can interact with the graphics card driver, audio and video driver, camera driver, keyboard driver, etc., so that the system detection module can detect various events (also known as data or information), for example, interacting with the graphics card driver so that the system detection module can detect GPU video decoding events. The OS2SOC driver can be used by the execution scheduling engine to send scheduling policies to the firmware layer.

The firmware layer includes various hardware and hardware drivers configured for electronic devices. For example, the firmware layer includes CPU, mouse, etc. The firmware layer also includes mouse drivers. The hardware configured in electronic equipment may belong to different hardware platforms. For example, the hardware platforms include: (Advanced Micro Devices, AMD), and etc., the scheduling policies of these three hardware platforms can be different, so the execution scheduling engine can distinguish the hardware platform types when determining the scheduling policy.

It should be noted that this application takes the Windows system as an example. In other operating systems (such as Android systems, IOS systems, etc.), as long as the functions implemented by each functional module are similar to the embodiments of the present application, the implementation of the present application can also be implemented. plan.

Combined with the above-mentioned Figure 2, Figure 3 shows a schematic diagram of resource scheduling of an electronic device. The operating system package of the electronic device It includes a scene recognition engine, an execution scheduling engine and a chip scheduling engine. The scene recognition engine and the execution scheduling engine are located in the application layer. The scene recognition engine can run as a plug-in, and the execution scheduling engine can run as a service. The chip scheduling engine is located in the driver layer, and the chip scheduling engine The engine can be run as a service. The scene recognition engine can interact with the execution scheduling engine. After the scene recognition engine identifies the application scenario, it determines the scheduling strategy (such as a set of policy values) based on the application scenario, and sends the scheduling strategy to the execution scheduling engine. The execution scheduling engine receives the scheduling strategy. Finally, the reception result is returned to the scene recognition engine to indicate that the execution scheduling engine has received the scheduling policy. Then, the execution scheduling engine sends the scheduling policy to the chip scheduling engine, and the chip scheduling engine executes the scheduling policy. The scheduling policy executed by the chip scheduling engine may be a target resource scheduling policy.

The scene recognition engine includes a scene recognition module, a scene library, a policy scheduling module and a policy library. The execution scheduling engine includes a scene interaction module, a scheduling strategy fusion module and a scheduling executor. The chip scheduling engine includes WMI plug-in and OS2SOC driver. The following describes each module in the scene recognition engine, execution scheduling engine, and chip scheduling engine in conjunction with Figure 3 to illustrate the process of resource scheduling using these three engines.

In Figure 3, the scene recognition engine can interact with the system probe module, execution scheduling engine, policy configuration module and housekeeper interface module respectively. The housekeeper interface module can send the system power mode currently used by the electronic device to the scene recognition engine. The system power mode can assist the scene recognition engine in determining the scheduling strategy; the policy configuration module is used to send a variety of preconfigured scheduling strategies to the scene recognition engine. Scheduling strategies can be called various resource scheduling strategies.

The scene library in the scene recognition engine is used to store multiple application scenarios. For example, the application scenario includes multiple main scenes such as social scenes, office scenes, and browser scenes. Each main scene can be divided into multiple sub-scenarios. For example, the browser scene includes Browser Internet access scenarios, browser audio playback scenarios, browser video playback scenarios, etc. The policy library in the scene recognition engine is used to store multiple scheduling policies sent by the policy configuration module. The scheduling policy and the application scenario can have a one-to-one relationship, such as assigning a scheduling policy to each sub-scenario. For example, scheduling policies include large and small core scheduling and office policy library. The office policy library records scheduling policies related to office applications. Large and small core scheduling is the large and small core scheduling capability provided by the architecture of Intel's 12th generation platform, indicating that large cores are used first ( The strategic configuration is carried out by focusing on performance) or small core (biasing on energy efficiency).

The policy scheduling module can send a query and subscription scenario request to the scene recognition module. The query and subscription scenario request is used to trigger the scene recognition module to perform scene recognition. The query and subscription scenario request can be sent immediately after the electronic device is turned on, or it can be sent regularly. This embodiment does not limited.

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., and then the system probe module The needle module can report the status of the electronic device to the scene recognition module. The scene recognition module determines the current application scenario of the electronic device from the scenario library according to the status of the electronic device, and reports the application scenario to the policy scheduling module. The policy scheduling module can determine the scheduling policy from the policy library according to the current application scenario of the electronic device.

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

The policy scheduling module sends the scheduling policy to the scene interaction module. After receiving the scheduling policy, the scene interaction module returns a reception result to the policy scheduling module. The reception result is used to indicate that the scene interaction module successfully received the scheduling policy. field The scene interaction module sends the scheduling policy to the scheduling policy fusion module, and the scheduling policy fusion module parses and escapes the scheduling policy to parse and escape the policy parameters in the scheduling policy into parameters recognized by the hardware platform. The scheduling policy fusion module sends the parsed and escaped scheduling policy to the scheduling executor. The scheduling executor sends the parsed and escaped scheduling policy according to the hardware platform type.

For example if the hardware platform type is The scheduling executor can send the parsed and escaped scheduling policy (can be regarded as the first sub-policy) to the OS2SOC driver and the AMD driver; if the hardware platform type is The scheduling executor can send the parsed and escaped scheduling policy (can be regarded as the second sub-policy) to the Intel driver through the WMI plug-in. In this embodiment, the scheduling strategy may be a chip scheduling strategy, which achieves the best balance of power consumption by adjusting the energy efficiency ratio of the chip. For example, the scheduling policy may be the power consumption scheduling policy of the CPU.

If the hardware platform type is The scheduling executor can send the CPU energy efficiency ratio (EPP) instruction in the power consumption scheduling policy to the power manager to adjust the EPP of the CPU. The EPP is used to reflect the scheduling tendency of the CPU, and its value range is 0 to 255. . The smaller the CPU energy efficiency ratio, the CPU tends to have high performance; the higher the CPU energy efficiency ratio, the CPU tends to have low power consumption. In addition, the scheduling executor can also send long-term turbo power consumption (power limit1, PL1) and short-term turbo power consumption (power limit2, PL2) instructions in the power consumption scheduling policy to the OS2SOC driver to adjust the PL1 of the CPU. and PL2. PL1 refers to the power consumption of the CPU under normal load, which is equivalent to the thermal design power consumption. The CPU's operating power consumption does not exceed PL1 most of the time. PL2 refers to the highest power consumption that the CPU can achieve in a short period of time, which has a duration limit. Generally, PL2 is larger than PL1. If the hardware platform type is The scheduling executor can send the power consumption scheduling policy to the Intel DTT driver (Intel DTT in Figure 3) through the WMI plug-in. The scheduling policy can include the minimum value of PL1, the maximum value of PL1, PL2, the duration of PL2 and EPP, which are provided by Intel The DTT driver CPU runs based on this scheduling policy. After receiving the scheduling policy, the WMI plug-in, Intel DTT driver and OS2SOC driver can return the reception result. The reception result is used to indicate that the scheduling policy has been successfully received.

In this embodiment, the system probe module includes: a primary probe and a secondary probe. The primary probe includes a power status probe, a peripheral status probe, an audio and video status probe, a system load probe, etc. Second-level probes include APP status probes and APP behavior probes; first-level probes are used to determine/detect first-level events (can also be called first-level data or first-level information, etc.); second-level probes can use a The primary event detected by the primary probe is a secondary event (the secondary event can also be called secondary data or secondary information, etc.). The secondary event detected by multiple secondary probes represents the status of the electronic device.

Among them, the power status probe is used to obtain power status events, such as determining the remaining power of the power supply, etc. Peripheral status probes are used to obtain status events of peripheral devices in electronic devices, such as the status of mouse and keyboard, and determine whether there are mouse click events and keyboard input events, etc. The audio and video status probe is used to determine the events of the audio module and the events of the GPU, such as determining whether the audio module is turned on, determining the GPU video decoding event, and determining whether to play the video. For example, it can also determine whether to share the desktop, etc. The system load probe is used to determine the system load. For example, the system load probe can determine the application load and network IO events. The application load refers to the business volume requested by the electronic device from the server, business running time, etc.

The APP status probe is used to determine the running status of the APP. It is used to determine/detect the status of at least one APP itself. For example, the APP status probe is used to determine the running status of three types of APPs: focus APP, non-focus APP and background APP. detection. A background APP is an APP that has been minimized to run in the background. A focus APP is an APP that is visible in the foreground and has the focus. It generally refers to an APP that is running in the foreground and is being operated by the user. Although a non-focus APP is also visible in the foreground, the focus is not on the APP. Generally refers to an APP that runs in the foreground but is not operated by the user. The APP behavior probe is used to determine the state switching behavior of the APP, such as switching from the focus APP to the non-focus APP, or switching to the background APP, etc.

In this embodiment, the first-level probe can obtain the first-level event through the callback function. For example, the power status probe can subscribe to the power status event from the kernel state and determine the power status based on the callback function fed back by the kernel state. The power status is a first-level event of the power supply. The power status includes the battery (remaining) power, whether the power adapter is connected, etc. For example, the power status probe can send a request to subscribe to the power status event to the Event driver of the driver layer, and the Event driver forwards the request to the power manager. The power manager can use this Event driver to feedback the callback function to the power status probe, and the power status probe can determine the power status through the callback function, such as determining the battery level through the callback function.

Peripheral status probes can subscribe to peripheral events from the kernel state and determine peripheral events (i.e. status events of peripheral devices) based on the callback functions fed back by the kernel state to reflect the status of peripheral devices through peripheral events. Peripheral events It can be regarded as external device usage information. Peripheral events include mouse wheel sliding events, mouse click events, keyboard input events, microphone input events, camera input events, etc. For example, the peripheral status probe sends a request to subscribe to the mouse status event to the Event driver, and the Event driver will subscribe to the mouse status event. The request is forwarded to the mouse driver. The mouse driver can monitor the status/event of the mouse. After monitoring the click event of the mouse, it feeds back the callback function to the Event driver. The callback function can indicate that the click event of the mouse has occurred, that is, the peripheral device sends a message to the electronic device. The device entered an event.

The system load probe can subscribe to the system load in the kernel state and determine the system load based on the callback function fed back by the kernel state. The audio and video status probe can subscribe to audio and video events in the kernel state, and determine the current audio and video events of the electronic device based on the callback function fed back by the kernel state. Audio and video events may include GPU decoding events, etc. For example, the audio and video status probe can send a request to subscribe to the GPU decoding event to the Event driver, and the Event driver forwards the request to the graphics card driver. The graphics card driver can monitor the status of the GPU. After monitoring that the GPU is performing a decoding operation, the Event driver feeds back the callback function to the audio and video status probe to determine that the GPU is used.

Figure 4 shows the architecture diagram of the system probe module. The first-level probes include: process probe, focus change (full screen) probe, minimize probe, GPU probe, audio probe, Camera probe, PC Lid closing probe, PC bright screen probe, Windows lock probe, mouse and keyboard peripheral probe, AC/DC power probe, system mode probe and system load probe, etc.

The first-level probe can be the basic probe of the operating system of the electronic device (such as Windows system). The development interface of the operating system can be used as the first-level probe. The first-level probe can send a subscription event request to the Event driver. to get system events. Process probes are used to obtain system events related to process changes such as process creation and process exit in the operating system; focus change (full screen) probes and minimization probes are used to obtain system events related to APP behavior changes such as window switching.

The GPU probe and audio probe can correspond to the audio and video status probe in Figure 3 above. The GPU probe is used to obtain system events related to whether the GPU is used to determine whether to play the video and Display images, etc., and the audio probe is used to obtain system events related to whether the audio module is used. The PC cover closing probe is used to determine whether the electronic device is in a closed state. The closed state means that the first body and the second body of the electronic device overlap together. The first body is equipped with a CPU and the second body is provided with a display. screen (for example, a PC cover probe can be used to determine whether a laptop is closed). PC bright screen probe is used to determine whether the display screen of an electronic device is in a bright screen state. The Windows Lock Probe is used to determine whether the operating system is locked or unlocked. The mouse and keyboard peripheral probes can correspond to the design probes in Figure 3 above. The mouse and keyboard peripheral probes are used to determine system events of external devices such as the mouse and keyboard, such as determining whether there are click events on the mouse and input events on the keyboard. etc.

The AC/DC power probe can correspond to the power status probe in Figure 3 above. The AC/DC power probe is used to obtain the battery System events related to power distribution such as power and whether the power adapter is used. The system mode probe is used to determine the power mode of the operating system, such as determining whether the operating system is in power saving mode (Power Saving). The system load probe is used to obtain the system load of an electronic device. The system load is the average number of processes in the runnable state and processes in the uninterruptible state. A process in a runnable state refers to a process that is using the CPU or waiting to use the CPU. A process in an uninterruptible state is a process waiting for I/O access (for example, disk I/O).

The system events (i.e., first-level events) obtained by the first-level probe are reported to the second-level probe, and the second-level probe calculates and processes the first-level event to obtain the second-level event (the second-level probe here is equivalent to the The events reported by the first-level probes are summarized and analyzed to obtain the second-level events). Secondary probes include application switching probes, application running status probes, system working status probes, and power mode probes. The application switching probe corresponds to the APP behavior probe in Figure 3 above, and the application running status probe corresponds to the APP status probe in Figure 3 above.

The application switching probe can obtain the APP switching action event based on the system events obtained by the process probe, focus change (full screen) probe and minimization probe. The APP switching action event includes switching events between APPs and the running stage of the APP. Switching events, such as the focus APP switching from one APP to another APP, such as switching from a game APP to a browser APP, or the focus APP switching from one running stage to another running stage, such as the game APP switching from game login to in-game . The application switching probe can output the application name and application type of the focus APP, the application name and application type of the non-focus APP, and the application name and application type of the background APP. The application switching probe uses the focus change (full screen) probe and The system events obtained by the minimization probe can determine whether the APP switches (that is, the switching event between APPs is obtained), and which APP is switched to which APP after the switching occurs. The same application switching probe probes the process at different times. The obtained system events can be used to determine whether the running phase of the focus APP has changed, that is, the APP running phase switching event is obtained. The application name and application type can be configured according to the default APP name type.

The application switching probe combines the GPU probe, audio probe, and Camera probe to obtain the application running status probe; the application running status probe is based on the system events obtained by the application switching probe, GPU probe, audio probe, and Camera probe. , obtain the application name and application type of the focus APP, non-focus APP and background APP, as well as the running status of each APP. For example, the application running status probe outputs the application name, application type and running status of the focus APP, and outputs the application name, application type and running status of the non-focus APP. The application name, application type and running status are output. The application name, application type and running status of the background APP are output. The running status can be determined based on the system events obtained by the GPU probe, audio probe and Camera probe. One way can be: after calculating the application switching probe based on the process probe, focus change (full screen) probe and minimize probe, obtain whether the application uses the GPU through the GPU probe, audio probe and Camera probe , audio, and camera status. If the GPU and Camera are used, the APP running status is the video status. If the GPU and Camera are not used, and only audio is used, the APP running status is the audio status. The application that uses GPU, audio, and camera can be at least one of the focus APP, non-focus APP, and background APP.

For example, the application switching probe determines that the current focus APP is a video type. When running a video type APP, the electronic device may be in video browsing or video playback. Then the application running status probe can be further determined through the system events of the GPU probe. If the GPU probe obtains a system event indicating the use of the GPU 3D engine, it indicates that the GPU is used for 2D or 3D rendering operations. It can be inferred that the user is using an electronic device to browse video resources instead of playing videos, that is, the video APP is in the state of browsing videos. .

The system working status probe is obtained through the PC cover closing probe, PC bright screen probe, Windows lock probe, and mouse and keyboard peripheral probe. The system working status probe can be determined based on the system events obtained by these four first-level probes. The operating system is Whether it is in the state of user use; for example, the mouse and keyboard peripheral probe determines that there are mouse click events and keyboard input events, and the PC cover closing probe determines that the electronic device is not closed, and the PC bright screen probe determines that the display screen is on. Then the system working status probe can determine that the operating system is in a state used by the user.

The power mode probe uses the AC/DC power probe and the system mode probe to determine the system power mode based on the system events obtained by the AC/DC power probe and the system mode probe. The system power mode is used to indicate whether to use the power adapter. Use, whether in balance mode or performance mode, etc. For example, the AC/DC power probe can be used to determine whether the power supply is in the AC state or the DC state. The AC state can be used to determine that the power adapter is not used, and the DC state can be used to determine that the power adapter is used. The system mode probe can be used to determine the power mode of the operating system. , such as in the best energy efficiency mode, balanced mode, or best performance mode; the power mode probe can superpose the system events obtained by the AC/DC power probe and the system mode probe to obtain the system power mode, such as through The AC/DC circuit probe determines that it is in the DC state and the system mode probe determines that it is in balanced mode. Then the power mode probe can determine that the electronic device uses a power adapter and the power mode is in balanced mode.

Through the secondary events obtained by the above secondary probes, the system probe module can obtain the mixed state. The mixed state includes application state information and operating system state information. For example, the application state information includes at least one of the focus APP, non-focus APP and background APP. Information about an APP, such as the APP’s application name, application type and running status, etc. The operating system status information is used to indicate whether the operating system (which can also be an electronic device) is in the state used by the user, the system power mode, etc. Application status information may be called application running status information, and operating system status information includes system working status and system power mode information.

The secondary probe reports the mixed status (also called status reporting) to the scene recognition engine. The scene recognition engine identifies the current application scenario of the electronic device based on the information reported by the secondary probe. One way can be: the scene recognition engine can determine the original application scenario based on part of the information in the mixed state, and then correct/adjust the original application scenario based on the remaining information in the mixed state to determine the target application scenario. In one example, the scene recognition engine can determine the original application scenario based on the application status information in the mixed state (which may be application running status information), and then identify the original application scenario based on the operating system status information in the mixed state (such as system working status). Make corrections/adjustments to determine target application scenarios.

For example, the scene recognition engine can determine the original application scenario based on the secondary events related to the application status reported by the application running status probe; then the scenario recognition engine can determine the original application scenario based on the secondary events related to the device usage reported by the system working status probe. The scene is corrected once, and the scene is supplemented based on the power-related secondary events reported by the power mode probe. For example, after the scene recognition engine determines the original application scenario, if the operating system reported by the system working status probe is in a state used by the user, the scenario recognition engine determines the original application scenario as the target application scenario; if the operating system reported by the system working status probe is The system is not in the state of user use. The scene recognition engine corrects the original application scene, determines that the electronic device is in an idle scene, and uses the idle scene as the target application scene. In addition, the scene recognition engine can also use power mode probes to supplement target application scenarios. For example, the system power mode can be added to the target application scenario so that the scheduling policy can match the system power mode.

The scene recognition engine monitors the current application scenario of the electronic device through scene registration and makes scene decision-making. The scene decision-making is to determine the scheduling strategy that matches the application scenario. The scene recognition engine can search for matching scheduling policies from the configuration file based on the application scenario and the power mode of the operating system (issued to the scene recognition engine by the housekeeper interface module). The configuration file can be stored in the policy library, and the configuration file includes patterns. Configuration and scenario policy configuration, mode configuration The corresponding relationship between the power mode and the scene policy configuration is recorded in the center, and the corresponding relationship between the application scenario and the scheduling policy is recorded in the scene policy configuration. The scene recognition mode can configure different scene policy configurations for different power modes through mode configuration, so that the scheduling policy matches the needs of the power mode.

The scene recognition engine determines the scene policy configuration from the mode configuration according to the power mode of the operating system; then it searches for a matching scheduling policy from the scene policy configuration according to the application scenario. Specifically, it can predetermine multiple scenarios and corresponding scheduling policies. The corresponding relationship is then determined based on the corresponding relationship to determine the scheduling strategy that matches the current scenario. If the scene recognition engine finds the scheduling policy, the scene recognition engine can send the scheduling policy to the execution scheduling engine; if the scene recognition engine does not find the scheduling policy, the scene recognition engine sends the default scheduling policy to the execution scheduling engine. If the scenario recognition engine does not find the scheduling policy according to any application scenario, the scenario recognition engine can send the default scheduling policy to the execution scheduling engine. Therefore, for the application scenario where the scheduling policy is not found, the default scheduling policy is not found. A scheduling strategy common to the application scenarios of the scheduling strategy.

The default scheduling policy is also a preset scheduling policy. The default scheduling policy can be different from the scheduling policy in the scene policy configuration. It can also be a scheduling policy selected from the scene policy configuration as the default scheduling policy, such as selecting the number of uses. The scheduling policy with the most is the default scheduling policy. In this embodiment, the scheduling policy may be targeted at the power consumption scheduling policy of the CPU. The corresponding scheduling policy includes PL1 of the CPU, PL2 of the CPU, and EPP of the CPU. The scheduling policy is executed through drivers of different hardware platforms.

In addition, the mode configuration can also be used as a preset condition for determining whether to determine the scheduling policy. For example, when the mode configuration indicates that it is in AC mode (that is, the power adapter is used), the scene recognition engine may not execute the process of determining the scheduling policy, or the scene recognition engine may not perform the process of determining the scheduling policy. It is prohibited to deliver the scheduling policy to the execution scheduling engine after scheduling the policy.

One point to note here: the use of first-level probes can be determined based on the currently running APP. If the currently running APP is not the default APP, it is prohibited to use at least one first-level probe. The default APP can be used for resource scheduling of electronic devices. Adjusted APPs, such as video APPs, game APPs, browser APPs, etc. At least one of the process probe, the focus change (full screen) probe, and the minimize probe can obtain the application name and application type of the APP. Therefore, this embodiment can obtain the current running status through at least one of these three probes. The application name and application type of the APP are used to determine whether the currently running APP is a default APP. If not, the use of GPU probes, audio probes, Camera probes, PC cover closing probes, PC bright screen probes, and Windows probes is prohibited. Lock probe, mouse and keyboard peripheral probe, AC/DC power probe, system mode probe and system load probe, etc.

The signaling diagram of the resource scheduling method provided by this application is given in conjunction with Figure 3 and Figure 4. As shown in Figure 5, the resource scheduling method may include the following steps:

S501. The policy configuration module delivers multiple scheduling policies to the scene recognition engine, and the multiple scheduling policies are stored in the policy library; the policy configuration module can also deliver multiple application scenarios to the scene recognition engine, and the multiple application scenarios are stored in the scene library. middle. Of course, the policy configuration module can issue scene policy configuration to the scene recognition engine. The scene policy configuration includes scheduling policies and application scenarios. Scheduling policies and application scenarios can have a one-to-one relationship.

S502. The housekeeper interface module delivers the system power mode to the scene recognition engine. The system power mode is used to indicate whether to use the power adapter, whether it is in the system power saving mode or performance mode, etc.

S503. The policy scheduling module in the scene recognition engine sends a query and subscription scene request to the scene recognition module in the scene recognition engine. 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 made immediately after the electronic device is turned on. It can be sent or sent regularly, which is not limited in this embodiment.

S504. 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.

S505. The system probe module uses a two-level probe to obtain a mixed state. The mixed state includes application state information and operating system state information. For example, the application state information includes information about at least one APP among the focus APP, the non-focus APP, and the background APP. For example, APP application name, application type and running status, etc. The operating system status information is used to indicate whether the operating system is in a state used by the user, the power mode of the operating system, etc.

S506. The system probe module reports the mixed status to the scene recognition module.

S507. The scene identification module selects the application scene currently in which the electronic device is located from the scene library according to the mixed state, and reports the application scene to the policy scheduling module.

S508. The policy scheduling module selects a scheduling policy from the policy library according to the system power mode and application scenario. In this embodiment, step S502 may be executed before step S508. For example, step S502 may be executed after step S503.

S509. The policy scheduling module delivers the scheduling policy to the scene interaction module in the execution scheduling engine, and the scene interaction module feeds back the reception result to the policy scheduling module.

S510. The scene interaction module sends the scheduling policy to the scheduling policy fusion module in the execution scheduling engine.

S511. The scheduling policy fusion module parses and escapes the scheduling policy, so as to parse and escape the policy in the scheduling policy into parameters recognized by the hardware platform.

S512. The scheduling policy fusion module sends the parsed and escaped scheduling policy to the scheduling executor.

S513. The scheduling executor sends the parsed and escaped scheduling policy according to the hardware platform type.

The above-mentioned Figures 4 and 5 show a feasible way for the scene recognition engine to determine the application scenario based on the secondary events obtained by the secondary probe, and the execution scheduling engine to determine the scheduling strategy based on the application scenario. The scenario recognition engine and the execution scheduling engine can also Use secondary events in other ways. For example, in one example, the scene recognition engine determines the original application scenario based on the secondary events obtained by a part of the secondary probes, and determines the original scheduling strategy based on the original application scenarios; then the scenario recognition engine determines the original application scenario based on the secondary events obtained by the remaining secondary probes. The original application scenario and the original scheduling strategy are adjusted. That is to say, the original application scenario and the original scheduling strategy are determined through a part of the secondary probes, and then the original application scenario and the original scheduling strategy are adjusted through the secondary events obtained by the remaining secondary probes to obtain the target application scenario and the target scheduling strategy. . The signaling diagram is shown in Figure 6, which can include the following steps:

S601. The policy configuration module delivers multiple scheduling policies to the scene recognition engine, and the multiple scheduling policies are stored in the policy library; the policy configuration module can also deliver multiple application scenarios to the scene recognition engine, and the multiple application scenarios are stored in the scene library. middle. Of course, the policy configuration module can issue scene policy configuration to the scene recognition engine. Scene policy configuration includes scheduling policies and application scenarios. Scheduling policies and application scenarios have a one-to-one relationship.

S602. The housekeeper interface module delivers the system power mode to the scene recognition engine. The system power mode is used to indicate whether to use the power adapter, whether it is in the system power saving mode or performance mode, etc.

S603. The policy scheduling module in the scene recognition engine sends a query and subscription scene request to the scene recognition module in the scene recognition engine. 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 made immediately after the electronic device is turned on. It can be sent or sent regularly, which is not limited in this embodiment.

S604. The scene recognition engine 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.

S605. The system probe module uses the first-level probe to obtain the first-level event, and uses the second-level probe to combine the first-level event to obtain the second-level event. For example, the first-level probes include: process probe, focus change (full screen) probe, minimize probe, GPU probe, audio probe, Camera probe, PC lid closing probe, PC bright screen probe, and Windows lock Probes, mouse and keyboard peripheral probes, AC/DC power probes, system mode probes and system load probes, etc. The system probe module uses these first-level probes to obtain first-level events.

The secondary probes include the first part of the secondary probe and the second part of the secondary probe. The first part of the secondary probe is used to determine the application scenario, and the second part of the secondary probe is used to adjust the original scheduling policy. For example, the first part of the second-level probes includes application switching probes and application running status probes, and the second part of the second-level probes includes system working status probes and power mode probes. The secondary events of the first part of the secondary probes are reported to the scene recognition module, and the secondary events of the second part of the secondary probes can be reported to the scheduling policy fusion module in the execution scheduling engine.

S606. The scene recognition module selects the original application scenario where the electronic device is currently located from the scene library based on the secondary events obtained by the first part of the secondary probe, and reports the original application scenario to the policy scheduling module.

S607. The policy scheduling module selects the original scheduling policy from the policy library according to the system power mode and the original application scenario. In this embodiment, step S602 may be executed before step S607. For example, step S602 may be executed after step S603.

S608. The policy scheduling module adjusts the original application scenario according to the secondary events obtained by the second part of the secondary probe to obtain the target application scenario; it adjusts the original scheduling policy based on the target application scenario to obtain the target scheduling policy.

S609. The policy scheduling module sends the target scheduling policy to the scene interaction module in the execution scheduling engine, and the scene interaction module feeds back the reception result to the policy scheduling module.

S610. The scene interaction module sends the target scheduling policy to the scheduling policy fusion module in the execution scheduling engine.

S611. The scheduling policy fusion module parses and escapes the target scheduling policy, so as to parse and escape the policy in the target scheduling policy into parameters recognized by the hardware platform.

S612. The scheduling policy fusion module sends the parsed and escaped target scheduling policy to the scheduling executor.

S613. The scheduling executor parses the escaped target scheduling policy according to the hardware platform type.

The following is explained with an example. As shown in Figure 7, the process of the electronic device identifying the browser scene and scheduling resources for the browser scene is explained. When the user opens the chrome browser in the system interface of the operating system, the process probe can detect that the user has opened the chrome browser and confirm that the chrome process has been created. The focus change (full screen) probe and minimize probe can also detect the user. Open the chrome browser to determine the chrome browser as the focus APP. The application name and application type of the chrome browser can be obtained from the APP classification configuration. The process probe, focus change (full screen) probe and minimize probe will send the obtained first-level events to the application switching probe. For example, if a chrome process is created and the chrome browser is the focus APP, it will be sent to the application switching probe. The application switching probe determines that the currently focused APP is the Chrome browser.

After the user opens the Chrome browser, the GPU probe, audio probe, and Camera probe can feed back first-level events related to the GPU, audio, and camera while the user is using the Chrome browser. The application running status probe can be combined with the application The current focus APP determined by the switching probe is the chrome browser, first-level events related to GPU, audio and camera, and determines the running status of the chrome browser, such as surfing the Internet, playing videos, etc.

The scene recognition module can determine the application scenario based on the running status of the Chrome browser reported by the application running status probe. Of course, the application running status probe can combine application switching probes, GPU probes, audio probes and Camera probes. The events obtained by the needle are sent to the scene identification module. The scene identification module determines the main scene as the browser scene based on the events obtained by the application switching probe, and determines the sub-scene based on the events obtained by the GPU probe, audio probe and Camera probe. The scenario is the original application scenario in which the electronic device is currently located. In practical applications, application switching probes, GPU probes, audio probes and Camera probes can send events to the scene recognition module. Among them, the first-level events obtained by the process probe, focus change (full screen) probe and minimization probe can be used as main scene feature factors, and the events obtained by GPU probe, audio probe and Camera probe can be used as sub-scene feature factors. .

The scene identification module sends the original application scenario to the policy scheduling module, and the policy scheduling module determines the scheduling strategy. The scheduling strategy includes multiple policy parameters, and the policy parameters are obtained based on actual measurement and tuning. For example, browser scenarios include browser online scenarios, browser video playback scenarios, and browser voice scenarios. The browser online scenarios, browser video playback scenarios, and browser voice scenarios each correspond to a scheduling policy. For example, the browser Internet access scenario corresponds to browser policy 1, the browser video playback scenario corresponds to browser policy 2, and the browser voice scenario corresponds to browser policy 3. The scene recognition module recognizes that the original application scenario is a browser Internet scenario, then the policy scheduling module can determine the scheduling policy as browser policy 1. Browser policy 1 can include: PL1, PL2, EPP, CPMinCores, CPMaxCores, MaxPerformance and MinPerformance, PL1 and PL2 is the name of the Intel platform. On the 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). CPMinCores refers to the minimum proportion of the number of logical processors that can be in the running state, ranging from 0 to 100. For example, if it is set to 20, if there are 10 logical processors, at least 2 logical processors are in the running state; CPMaxCores is Refers to the maximum proportion of the number of logical processors that can be in the running state, ranging from 0 to 100. For example, if it is set to 80, if there are 10 logical processors, up to 8 logical processors are in the running state; MaxPerformance refers to the CPU The upper limit of performance, ranging from 0 to 100. For example, if it is set to 80, the performance of the CPU can reach 80% of the maximum performance; MinPerformance refers to the lower limit of performance of the CPU, ranging from 0 to 100. For example, if it is set to 20, the performance of the CPU can reach the lowest performance. down to 20% of maximum performance.

The policy scheduling module can adjust the original application scenario based on decision-making characteristic factors. For example, the decision-making characteristic factors can be detected by PC lid closing probe, PC bright screen probe, Windows lock probe, mouse and keyboard peripheral probe, AC/DC power probe, system mode probe and system load probe. Level 1 event. If the decision characteristic factor has an impact on the browser Internet scenario, the policy scheduling module adjusts the original application scenario. For example, the decision characteristic factor determines that the electronic device is in an idle state, and the policy scheduling module determines that the electronic device is in an idle state. From the browser The Internet access scene is adjusted to the idle scene, and the idle scene is the target application scene. Then, the policy parameters in the browser policy 1 are adjusted based on the idle scene to adapt to the idle electronic device. If the decision-making characteristic factors have no impact on the browser Internet scenario, the policy scheduling module will not adjust the original application scenario and the original scheduling policy (such as browser policy 1).

The policy scheduling module sends the final browser policy 1 to the scene interaction module. The scene interaction module writes the final browser policy 1 into the fusion scheduling queue. The scheduling policy fusion module obtains the final browser policy 1 from the fusion scheduling queue. And complete the escape according to the hardware platform type, and send it to the hardware platform through the scheduling executor.

The hardware platform is and For example, if the hardware platform is The policy scheduling fusion module determines the dynamic tuning technology policy number based on the obtained target scheduling policy (such as the final browser policy 1).

Dynamic tuning technology (DTT) is The company is in processor and Technology that automatically and dynamically allocates power consumption between independent graphics cards to optimize performance and extend battery life. It can improve CPU and GPU performance and intelligently balance workloads for mixed workloads. Understandably, DTT policy There can be a mapping relationship between the number and the target scheduling policy. For example, if a DTT policy table is built in advance, any target scheduling policy can be mapped to a certain DTT policy number in the DTT policy table through the policy parameters in it, as shown in Figure 7. Browser policy 1 corresponds to policy number 2.

Among them, the DTT policy number can be used to identify a DTT policy, and the DTT policy corresponding to the DTT policy number is used to adjust the PL1_MINI, PL1_MAX, PL2, PL2_TIME, and EPO Gear of the CPU. PL1_MINI is the minimum value of PL1, PL1_MAX is the maximum value of PL1, and PL2_TIME is the duration of PL2. Energy efficiency-performance optimization gear (Energy Performance Optimize Gear, EPO Gear) is used to represent the intensity of DTT in adjusting the CPU energy efficiency ratio (EPP). The value ranges from 1 to 5. The larger the value, the more energy efficiency is inclined when adjusting EPP; the smaller the value , the more performance-oriented when adjusting EPP.

The policy scheduling fusion module can send the DTT policy number to the scheduling executor. In an optional implementation, the policy scheduling fusion module can also directly send the functional DTT policy corresponding to the DTT policy number to the scheduling executor. The scheduling executor sends the DTT policy number to the Intel DTT driver, and the Intel DTT driver executes the DTT policy. The scheduling policy corresponding to the number is called the DTT performance control table as shown in Figure 7. The DTT performance control table is the scheduling policy corresponding to the DTT policy number and the scheduling policy sent by the upper-layer scheduling executor.

If the hardware platform is The scheduling policy fusion module can send instructions to adjust the EPP to the power manager through the scheduling executor, and the power manager can adjust the EPP of the CPU. In addition, the scheduling executor can also send instructions to adjust PL1 and PL2 to the OS2SOC driver node, and the OS2SOC driver node drives PL1 and PL2 of the CPU. As shown in Figure 7, the values of the AMD performance parameters and the values of the Windows parameters are set to the values of the corresponding policy parameters in the scheduling policy.

for and For these two hardware platforms, the scheduling strategy can use over-temperature protection as a basic strategy to prevent the temperature of electronic equipment from being too high and causing danger. In addition, if the scheduling policy module does not match the scheduling policy based on the application scenario, the default scheduling policy will be delivered. If the work of the scene recognition module to the scheduling executor fails, the Intel DTT driver can execute a self-built strategy. The self-built strategy includes multiple parameters. Resource scheduling is completed through the self-built strategy. The self-built strategy can be related to the current scene of the electronic device. A strategy, such as in the browser scenario, the self-built strategy is a browser scenario performance control strategy. Resource scheduling is completed through the self-built strategy, and the scheduling strategy is supplemented and improved by the self-built strategy.

In addition, this application also provides a resource scheduling device. The device is applied to electronic equipment. The operating system of the electronic device is a Windows system. The structural diagram of the resource scheduling device is shown in Figure 8. It may include: an acquisition unit 100, a determination unit 200 and Scheduling unit 300.

The acquisition unit 100 is used to obtain the basic status information of the electronic device based on the system probe module of the electronic device; process the basic status information to obtain the running status information of the electronic device, and the running status information of the electronic device includes the application running status of the electronic device. , at least one of system working status and system power mode information; the determining unit 200 is used to determine the application scenario in which the electronic device is located based on the operating status information of the electronic device; determine the application scenario related to the electronic device based on the application scenario in which the electronic device is located A target resource scheduling strategy that matches the application scenario. The target resource scheduling strategy includes a CPU power consumption scheduling strategy; the scheduling unit 300 is used to schedule resources for the electronic device according to the target resource scheduling strategy.

Among them, the running status information corresponds to the second-level event, and the basic status information corresponds to the first-level event. The basic status information includes: basic running information related to the application, audio and video usage information, power mode usage information, external device usage information and display usage information. At least one of the above, the basic running information related to the application at least includes the application name of the focus application and application type.

For example, the basic running information related to the application includes: the application name and application type of the focus application, the application name and application type of the non-focus application, the application name and application type of the background application; audio and video usage information includes: whether to use the graphics processor information, whether to use the audio module and whether to use the camera; power mode usage information includes: the power mode of the operating system and the power supply mode of the electronic device; external device usage information includes: information about whether to use external devices; display screen usage information Including: the screen bright information of the display screen, the lock screen unlock information of the display screen, and the information of whether the electronic device is in a closed state.

In some examples, the acquisition unit 100 processes the basic status information to obtain the running status information of the electronic device including: obtaining the application name and application type of the focus application, the application name and application type of the non-focus application, and the background information from the basic status information. The application name and application type of the application; if the audio and video usage information in the basic status information indicates that the application uses the graphics processor and camera, determine that the running state of the application is the video state, and the application includes at least one of the focus application, non-focus application and background application. kind; if the audio and video usage information in the basic status information indicates that the application uses the audio module, determine that the running state of the application is the audio state; if the audio and video usage information in the basic status information indicates that the application uses the graphics processor, camera and audio module, determine the application's running status. The running state is audio and video state.

In some examples, the acquisition unit 100 processes the basic status information to obtain the operating status information of the electronic device including: determining the current mode of the electronic device according to the power mode of the operating system; if the power supply mode of the electronic device is DC power supply, Make sure the electronic device does not use a power adapter; if the electronic device is powered by AC power, make sure the electronic device uses a power adapter.

In some examples, the basic status information includes external device usage information and display screen usage information. The acquisition unit 100 processes the basic status information, and obtains the running status information of the electronic device including: if the external device inputs an event to the electronic device, the display screen is in If the screen is in the unlocked state and the electronic device is not in the cover-closed state, it is determined that the electronic device is in the state of use by the user; if the external device inputs an event to the electronic device, the display is in the screen-on-unlocked state, and the electronic device is not in the cover-closed state, it is determined that the electronic device is in the state of being used by the user. It is in a state that is not in use by the user; if the electronic device is in a closed state and/or the display is in a bright-screen unlocked state, it is determined that the electronic device is in a state that is not in use by the user.

Optionally, the determining unit 200 determines the application scenario in which the electronic device is located based on the operating status information of the electronic device, including: determining the first application scenario in which the electronic device is located based on the first part of the information in the operating status information; The second part of the information is used to adjust the first application scenario and determine the second application scenario where the electronic device is located. The second application scenario where the electronic device is located is the application scenario where the electronic device is located. For example, the first application scenario is determined based on the application running status in the running status information and the system load of the electronic device; the first application scenario is adjusted based on the second part of the information in the running status information, and the second application scenario where the electronic device is located is determined. The application scenarios include: if the system working status information in the running status information indicates that the electronic device is in a state used by the user, the first application scenario is determined as the second application scenario; if the system working status information in the running status information indicates that the electronic device is in a state used by the user When not in use, it is determined that the electronic device is in an idle scene, and the idle scene is the second application scene.

When the determining unit 200 determines the target resource scheduling policy, if the electronic device does not use a power adapter, based on the application scenario and system power mode information of the electronic device, a target resource scheduling policy that matches the application scenario of the electronic device is determined; if The electronic device uses a power adapter, and the determining unit 200 prohibits determining a target resource scheduling policy that matches the application scenario in which the electronic device is located based on the application scenario in which the electronic device is located.

Optionally, the CPU power consumption scheduling strategy includes a first sub-strategy and a second sub-strategy, and the second sub-strategy is based on The dynamic tuning technology strategy determined by the first sub-strategy; the scheduling unit 300 adjusts the electronic device for resource scheduling according to the target resource scheduling policy, including: if the hardware platform type is the first type, resource scheduling for the electronic device according to the first sub-strategy; if the hardware platform The platform type is the second type, and resource scheduling is performed on the electronic device according to the second sub-policy. The first type may be AMD and the second type may be Intel.

Optionally, the method also includes: if the target resource scheduling strategy fails, obtain a preset self-built strategy; and perform resource scheduling for the electronic device according to the self-built strategy.

This application provides an electronic device. The electronic device includes: a memory and one or more processors; wherein the memory is used to store computer program codes, and the computer program codes include computer instructions; when the computer instructions are executed by the processor, the electronic device Execute the above method.

The present application provides a computer-readable storage medium. The computer-readable storage medium stores a computer program. When the computer program is run on an electronic device, it causes the electronic device to execute the above method.

The descriptions of the processes or structures corresponding to each of the above drawings have different emphasis. For parts that are not described in detail in a certain process or structure, please refer to the relevant descriptions of other processes or structures.

Claims

A resource scheduling method, characterized in that the method is applied to electronic equipment, and the operating system of the electronic equipment is a Windows system. The method includes:

Obtain basic status information of the electronic device based on the system probe module of the electronic device;

The basic status information is processed to obtain the running status information of the electronic device. The running status information of the electronic device includes at least one of the application running status, system working status and system power mode information of the electronic device. ;

Determine the application scenario in which the electronic device is located based on the operating status information of the electronic device;

Determine a target resource scheduling policy that matches the application scenario where the electronic device is located based on the application scenario where the electronic device is located, where the target resource scheduling policy includes a central processor power consumption scheduling policy;

Resource scheduling is performed on the electronic device according to the target resource scheduling policy.
The method according to claim 1, characterized in that the basic status information includes: at least one of basic operation information related to the application, audio and video usage information, power mode usage information, external device usage information and display screen usage information. In one method, the basic operation information related to the application at least includes the application name and application type of the focus application.
The method according to claim 2, characterized in that the basic operation information related to the application includes: the application name and application type of the focus application, the application name and application type of the non-focus application, the application name of the background application and App types;

The audio and video usage information includes: information on whether to use a graphics processor, information on whether to use an audio module, and information on whether to use a camera;

The power mode usage information includes: the power mode of the operating system and the power supply mode of the electronic device;

The external device usage information includes: information on whether the external device is used;

The display screen usage information includes: screen on information of the display screen, screen lock and unlock information of the display screen, and information on whether the electronic device is in a closed state.
The method according to any one of claims 1 to 3, characterized in that, processing the basic status information to obtain the operating status information of the electronic device includes:

Obtain the application name and application type of the focus application, the application name and application type of the non-focus application, and the application name and application type of the background application from the basic status information;

If the audio and video usage information in the basic status information indicates that the application uses a graphics processor and/or camera, it is determined that the running status of the application is the video status, and the application includes the focus application, the non-focus application and the background application. at least one of;

If the audio and video usage information in the basic status information indicates that the application uses the audio module, determine that the running status of the application is the audio status;

If the audio and video usage information in the basic status information indicates that the application uses a graphics processor, camera and audio module, it is determined that the running status of the application is the audio and video status.
The method according to claim 3 or 4, characterized in that said processing the basic status information to obtain the operating status information of the electronic device includes:

Determine the current mode of the electronic device according to the power mode of the operating system;

If the power supply mode of the electronic device is DC power supply, it is determined that the electronic device does not use the power adapter; if the power supply mode of the electronic device is regarded as AC power supply, it is determined that the electronic device uses the power adapter.
The method according to any one of claims 3 to 5, characterized in that the basic status information includes external device usage information and display screen usage information, and the basic status information is processed to obtain the electronic device usage information. The operating status information of the device includes:

If the external device inputs an event to the electronic device, the display screen is in a bright-screen unlocked state, and the electronic device is not in a closed state, it is determined that the electronic device is in a state for use by the user;

If the external device inputs an event to the electronic device, the display screen is in a bright-screen unlocked state, and the electronic device is not in a closed state, it is determined that the electronic device is in a state that is not in use by the user;

If the electronic device is in a closed state and/or the display screen is in a bright-screen unlocked state, it is determined that the electronic device is in a state that is not in use by the user.
The method according to any one of claims 1 to 6, wherein determining the application scenario in which the electronic device is located based on the operating status information of the electronic device includes:

Determine the first application scenario in which the electronic device is located based on the first part of the information in the operating status information;

According to the second part of the information in the running status information, the first application scenario is adjusted to determine the second application scenario where the electronic device is located, and the second application scenario where the electronic device is located is the Application scenarios for electronic devices.
The method according to claim 7, wherein determining the first application scenario in which the electronic device is located based on the first part of the information in the running status information includes: based on the application in the running status information. The operating status and the system load of the electronic device determine the first application scenario;

According to the second part of the information in the running status information, adjusting the first application scenario and determining the second application scenario in which the electronic device is located includes: if the system working status information in the running status information indicates The electronic device is in a state of being used by the user, and the first application scenario is determined as the second application scenario; if the system working status information in the running status information indicates that the electronic device is in a state of not being used by the user, It is determined that the electronic device is in an idle scene, and the idle scene is the second application scene.
The method according to any one of claims 1 to 8, characterized in that, based on the application scenario in which the electronic device is located, a target resource scheduling policy that matches the application scenario in which the electronic device is located is determined. The method includes: if the electronic device does not use a power adapter, based on the application scenario in which the electronic device is located and the system power mode information, determine a target resource scheduling strategy that matches the application scenario of the electronic device;

The method further includes: if the electronic device uses a power adapter, prohibiting determining a target resource scheduling policy that matches the application scenario in which the electronic device is located based on the application scenario in which the electronic device is located.
The method according to any one of claims 1 to 9, characterized in that the CPU power consumption scheduling strategy includes a first sub-strategy and a second sub-strategy, and the second sub-strategy is based on the first A dynamic tuning technology strategy determined by a sub-strategy;

The adjusting the electronic device for resource scheduling according to the target resource scheduling policy includes:

If the hardware platform type is the first type, perform resource scheduling on the electronic device according to the first sub-policy;

If the hardware platform type is the second type, perform resource allocation on the electronic device according to the second sub-policy Scheduling.
The method according to any one of claims 1 to 10, characterized in that the method further includes: if the target resource scheduling strategy fails, obtaining a preset self-built strategy; The electronic equipment performs resource scheduling.
An electronic device, characterized in that the electronic device includes: a memory and one or more processors;

Wherein, the memory is used to store computer program code, and the computer program code includes computer instructions; when the computer instructions are executed by the processor, the electronic device is caused to perform any one of claims 1 to 11 the method described.
A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program. When the computer program is run on an electronic device, the electronic device causes the electronic device to execute any of claims 1 to 11. method described in one item.