Resource scheduling method, system and device, storage medium and program product
By obtaining and analyzing user usage scenarios and switching service operations, and dynamically adjusting resource priorities, the problem of improper resource allocation in use scenarios in traditional scheduling strategies is solved, and equipment fluency and resource efficiency are improved.
Patent Information
- Application Number
- CN202310524338.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-10
- Publication Date
- 2024-11-12
AI Technical Summary
Traditional scheduling strategies fail to dynamically adjust the priority of objects according to user habits and usage scenarios, resulting in timely dispatch of important processes in certain usage scenarios, causing the entire machine to be stuttered and affecting the user experience.
By obtaining predefined information of electronic devices, determining usage scenarios and sub-scenes, scheduling resources based on the object priority list of sub-scenes, sensing user switching service operations in real time, and adjusting object priority to achieve timely and accurate resource allocation.
It improves the smoothness of equipment usage, improves the efficiency of computing resources, and ensures the optimal allocation of resources in different usage scenarios, especially on mobile devices with limited resources.
Smart Images

Figure CN118939386A_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present application relate to the field of computer technology, and in particular, to a resource scheduling method, system, device, storage medium, and program product. Background Art
[0002] At present, the scheduling strategies used by electronic devices, especially mobile terminal devices, for scheduling objects (such as processes) include: First Come First Served (FCFS) scheduling algorithm and Round-Robin Scheduling (Round-Robin Scheduling) scheduling algorithm. However, the above scheduling strategies do not take users into consideration. For example, if the user's scenario is not taken into consideration, there is a situation where objects cannot be scheduled in time, which may easily cause the entire device to freeze and affect the user experience. Summary of the invention
[0003] A first aspect provides a resource scheduling method, the method comprising obtaining predefined information of an electronic device; determining a usage scenario of the electronic device based on the predefined information; determining a sub-scenario of the usage scenario based on a user's switching service operation on the electronic device; obtaining an object priority list of the sub-scenario to schedule resources of the electronic device based on the object priority list of the sub-scenario, wherein the object priority list of the sub-scenario is related to the object priority list of the usage scenario.
[0004] The above scheme predefines usage scenarios and sub-scenarios of usage scenarios. After determining the usage scenario of the electronic device, the sub-scenario of the usage scenario is determined according to the user's switching service operation on the electronic device. It can be known that the user's usage situation in the usage scenario can be further determined in a fine-grained manner, and objects can be timely and accurately allocated and scheduled for resources according to the object priority list corresponding to the sub-scenario, which is conducive to improving the smoothness of device use and improving the efficiency of computing resource utilization.
[0005] In one possible implementation, determining a sub-scenario of a usage scenario based on a user's switching service operation on an electronic device includes: determining a target service used by a user based on the user's switching service operation on an electronic device, and determining a sub-scenario of the usage scenario based on the service of the usage scenario and the target service.
[0006] The switching service operation can be used to indicate the service that needs to be used, such as entering a certain application, or it can be a switching service, such as exiting from application a and entering application b. The switching service operations input by the user to the electronic device in this usage scenario may include multiple. For example, entering the desktop is one switching service operation, and exiting the desktop and entering application a is another switching service operation. The target services used by the user include the services that the user has used and the services that are currently being used in this usage scenario. The services of the usage scenario are the services indicated by the objects in the object priority list of the usage scenario. According to the services indicated by the objects in the object priority list of the usage scenario, the services in the usage scenario and the order of use of each service in the usage scenario can be obtained.
[0007] The above scheme determines the services that the user will use in the usage scenario (i.e., the services of the usage scenario) based on the user's usage habits (service usage information), obtains the switching service operation, and the electronic device determines whether it conforms to the predefined sub-scenario based on the user's switching service operation on the electronic device, that is, judges whether it conforms to the predefined sub-scenario based on the target service, thereby determining the services that the user has used and is currently using in the usage scenario, and predicting the services that the user will use next, which is conducive to improving the fluency of device use and improving the efficiency of computing resource utilization.
[0008] In a possible implementation, when the number of target services includes two or more, the order in which the two or more target services are used in time is obtained; then determining the sub-scenario of the use scenario according to the service of the use scenario and the target service includes: determining the sub-scenario of the use scenario according to the service of the use scenario, the target service and the order. The order in which the two or more target services are used in time is also the order in which the two or more target services are used in the use scenario, and whether the order of use matches the preset sub-scenario is matched to accurately predict the services to be used in the subsequent period.
[0009] In one possible implementation, the method further includes: obtaining service usage information; determining an object priority list of a usage scenario based on the service usage information, wherein the scenario information associated with the service usage information matches the usage scenario. The above scheme determines the usage scenario and the object priority list of the usage scenario based on the matching information and the service usage information associated with each other, and the matching information and the service usage information associated with each other indicate the usage information of the user using the service under the matching information. For example, if the matching information is 12-14 o'clock, location company, and the service usage information associated with the matching information is: the usage information of the user using the service at 12-14 o'clock, location company.
[0010] In a possible implementation, the method further includes: determining, for each usage scenario, a sub-scenario of the usage scenario, and determining an object priority list corresponding to the sub-scenario according to the object priority list of the usage scenario.
[0011] In one possible implementation, the predefined information includes scenario information and / or service usage information; wherein the scenario information includes one or more of the following information: time information, geographic location information, WiFi connection status, weather information, Bluetooth headset connection status, vehicle-mounted Bluetooth connection status, flight travel information, power level of electronic devices, consumer order information, and user exercise status; wherein the service usage information includes one or more of the following information: service name and time of using the service.
[0012] In one possible implementation, the object priority list of the sub-scene is a part of the object priority list of the usage scene.
[0013] The second aspect provides a resource scheduling system, including: an electronic device, used to obtain scenario information and service usage information; a first server, used to configure the usage scenario and matching information that matches the usage scenario, the matching information including the scenario information; a second server, used to determine an object priority list of the usage scenario based on the service usage information; the second server is also used to determine a sub-scenario of the usage scenario based on the service of the usage scenario, and determine a priority list corresponding to the sub-scenario based on the object priority list of the usage scenario, wherein the service of the usage scenario is the service indicated by the object in the object priority list of the usage scenario.
[0014] The above solution is based on the collected scene information such as the user's time and space, geographical location, and the user's usage information of the service, and uses this to train the model, thereby obtaining an object priority mining model that changes with the user's scene and user habits. While ensuring smooth user use, it also improves the efficiency of the use of mobile device hardware resources, which is especially important for mobile devices with limited resources.
[0015] In a possible implementation, the first server is further configured to obtain scene information of the electronic device, and determine the usage scene of the electronic device according to the scene information. The usage scene of the user is sensed through the scene information, and the object priority is intelligently adjusted according to the usage scene.
[0016] In a possible implementation, the electronic device is further used to obtain a user's switching service operation on the electronic device, wherein the switching service operation is used to determine a sub-scenario of the usage scenario after determining the usage scenario of the electronic device. The object priority list is further refined to the sub-scenario granularity, and the user's switching service operation in the scenario is perceived in real time, so as to perceive the sub-scenario in the usage scenario in real time and adjust the object priority in time.
[0017] The third aspect provides an electronic device, including: a processor and a memory; the memory is used to store a computer program, the computer program includes program instructions; the processor is used to call the computer program to execute the resource scheduling method as described above.
[0018] A fourth aspect provides a computer storage medium, comprising computer instructions, which, when executed on an electronic device, enables the electronic device to execute the resource scheduling method as described above.
[0019] A fifth aspect provides a computer program product, which, when executed on a computer, enables the computer to execute the resource scheduling method as described above.
[0020] The technical effects obtained by the above-mentioned second, third, fourth and fifth aspects are similar to the technical effects obtained by the corresponding technical means in the first aspect, and will not be repeated here.
[0021] The beneficial effects of the technical solution provided by this application include at least:
[0022] In an embodiment of the present application, usage scenarios and sub-scenarios of usage scenarios are pre-defined. After the usage scenario of the electronic device is determined, the sub-scenario of the usage scenario is determined according to the user's switching service operation on the electronic device. It can be known that the user's usage situation in the usage scenario can be further determined in a fine-grained manner, and timely and accurate resource allocation and scheduling of objects are performed according to the object priority list corresponding to the sub-scenario, which is conducive to improving the fluency of device use and improving the efficiency of computing resource utilization. BRIEF DESCRIPTION OF THE DRAWINGS
[0023] Figure 1 A schematic diagram of the structure of the scheduling system provided for this application.
[0024] Figure 2 A schematic diagram of the structure of the acquisition module provided in an embodiment of the present application.
[0025] Figure 3 A schematic diagram of the structure of a scene determination module provided in an embodiment of the present application.
[0026] Figure 4 A schematic diagram of the structure of the first determination module provided in an embodiment of the present application.
[0027] Figure 5 A schematic diagram of the structure of the second determination module provided in an embodiment of the present application.
[0028] Figure 6 A schematic diagram of the structure of the object scheduling module provided in an embodiment of the present application.
[0029] Figure 7A schematic diagram of the structure of a resource scheduling system provided in an embodiment of the present application.
[0030] Figure 8 An interactive schematic diagram of a resource scheduling system provided in an embodiment of the present application.
[0031] Fig. 9 A schematic diagram of a first server definition scenario provided in an embodiment of the present application.
[0032] Fig.10 A schematic diagram of information obtained by an electronic device provided in an embodiment of the present application.
[0033] Fig.11 A schematic diagram of information mining by a second server provided in an embodiment of the present application.
[0034] Fig.12 A schematic diagram of electronic device scheduling provided in an embodiment of the present application.
[0035] Fig.13 A schematic diagram of the structure of another resource scheduling system provided in an embodiment of the present application.
[0036] Fig.14 A schematic diagram of another resource scheduling system interaction provided in an embodiment of the present application.
[0037] Fig.15 A schematic diagram of the structure of another resource scheduling system provided in an embodiment of the present application.
[0038] Fig.16 A schematic diagram of a resource scheduling method flow chart provided in an embodiment of the present application.
[0039] Fig.17 A schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application.
[0040] Fig.18 A schematic diagram of the software structure of an electronic device provided in an embodiment of the present application.
[0041] Fig.19 A schematic diagram of an electronic system for software and hardware interaction provided in an embodiment of the present application. DETAILED DESCRIPTION
[0042] In this article, the terms "comprises", "comprising" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device that includes a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of more restrictions, an element defined by the sentence "comprising a" does not exclude the presence of other identical elements in the process, method, article or device that includes the element.
[0043] In this application, "at least one" means one or more, and "more than one" means two or more than two. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The terms "first", "second", "third", "fourth", etc. (if any) in the specification, claims and drawings of this application are used to distinguish similar objects, rather than to describe a specific order or sequence.
[0044] In the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.
[0045] As the functions of terminal devices become increasingly powerful, the power consumption requirements of terminal devices are also increasing, while the development of battery-related technologies is very slow, resulting in terminal devices often having insufficient battery life, unable to meet user needs, and reducing the user experience in mobile scenarios. The operating system of the terminal device needs to accurately allocate and schedule resources (such as central processing unit (CPU) resources) for objects on the terminal device (such as currently running processes or threads or processes or threads in the ready state) to ensure the performance of the terminal device while satisfying the user's long battery life experience in mobile scenarios.
[0046] The scheduling strategies used by traditional operating systems include: first-come-first-served scheduling algorithm, time slice round-robin scheduling algorithm, and priority scheduling algorithm. Taking the process as the object of scheduling as an example, the first-come-first-served scheduling algorithm gives priority to the process that enters the ready queue first. The time slice round-robin scheduling algorithm allocates equal-length time slices to each process in a constant order, and does not consider any priority when processing all processes. The priority scheduling algorithm assigns a priority to each process, and each time a process switch is required, a process with the highest priority is found for scheduling. The priority scheduling algorithm is divided into static priority and dynamic priority. The static priority refers to the priority assigned to the process when it enters the system or is created. The static priority will not change during the life cycle of the process. The static priority is mainly determined by the process type, resource requirements, time requirements, and user requirements. The dynamic priority refers to the priority assigned to the process when it enters the system or is created. The difference between dynamic priority and static priority is that the dynamic priority of different processes is constantly adjusted dynamically over time. For example, the dynamic priority will increase as the waiting time for CPU resources increases, and decrease as the time using CPU resources increases. The Linux operating system distinguishes two types of processes: real-time processes and normal processes. Normal processes have static priorities and dynamic priorities. For normal processes, the dynamic priority is calculated based on the static priority. Real-time processes have static priorities, dynamic priorities, and real-time priorities, with the real-time priority being the highest. Real-time processes run before normal processes, and processes are called in order according to their priorities.
[0047] As mentioned above, the traditional first-come-first-served scheduling algorithm and time slice round-robin scheduling algorithm are relatively simple and fixed, and do not distinguish between users, usage scenarios, and scheduling objects, so that the scheduling of objects cannot be adjusted according to users and the scenarios in which users are located. The priority set for the process by the traditional priority scheduling algorithm does not take into account users and user usage scenarios. The process priority is relatively fixed in different usage scenarios, that is, the process priority cannot be dynamically adjusted according to users and the scenarios in which users are located.
[0048] The above traditional scheduling strategies are unable to adjust the priority of objects according to user habits and usage scenarios (or usage situations in the same usage scenario). If based on the original scheduling logic, such as the time slice round-robin scheduling algorithm to allocate resources to processes according to time slices, some important processes (such as processes used to execute interactive events) in some usage scenarios will not be scheduled in time, which may easily cause the whole machine to be stuck. The above traditional scheduling strategies cannot provide corresponding resource scheduling for different users, different user scenarios, and different usage situations in the same usage scenario. They are not very applicable and cannot ensure the optimal allocation of resources. Especially on devices with limited resources (for example: 6G RAM), users will often experience stuck in use, which reduces the user experience.
[0049] In view of this, the embodiments of the present application provide a resource scheduling method, system and related equipment, which define usage scenarios and sub-scenario under the usage scenarios according to the user's scenario information and service usage information, each usage scenario has its corresponding object priority list, and each sub-scenario of the usage scenario has its corresponding object priority list. The sub-scenario is related to the user's switching service operation, which refers to the operation of switching services on an electronic device. Based on the sub-scenario, the user's usage situation in the usage scenario can be determined. Timely and accurate resource allocation and scheduling of objects according to the object priority list corresponding to the sub-scenario is conducive to improving the fluency of device use and improving the efficiency of computing resource use.
[0050] Exemplarily, the process is used as the object for explanation. 1. Each usage scenario has its corresponding process priority list. For example: on the way to work in the morning, the user's usage habit is: first swipe to the negative one screen to view the recommended information, then return to the desktop, then click on the text message to view the message, and finally click on Huawei Video. The process priority list in the usage scenario on the way to work in the morning is: negative one screen> desktop> text message> Huawei Video. In the usage scenario of the company's lunch break, the user's usage habit is: first unlock the phone, then click on Huawei Video, and then click on the text message. The process priority list in the company's lunch break scenario is: desktop> Huawei Video> text message> negative one screen. 2. There are also different process priority lists in different usage scenarios of the same usage scenario. Take the above-mentioned company lunch break usage scenario as an example: when the user just unlocks the phone, the next service to be prioritized in the process priority list corresponding to the sub-scenario is Huawei Video. When the user exits the desktop and is using Huawei Video or has finished using Huawei Video, the next service to be prioritized in the process priority list corresponding to the sub-scenario is SMS.
[0051] The resource scheduling method provided in the embodiment of the present application can be applied to a physical machine, which may include a processor circuit integrated with each physical central processing unit (CPU), and the processor circuit may be integrated on a chip, which may run various operating systems (OS), such as Android, Hongmeng, Linux, Windows, UNIX systems, etc., that is, a system on chip (SOC) may be formed on the chip. The physical machine includes but is not limited to mobile phones, tablet computers, wearable devices (such as smart watches, smart bracelets, smart glasses, smart jewelry, etc.), vehicle-mounted equipment, augmented reality (AR) / virtual reality (VR) equipment, laptops, ultra-mobile personal computers (UMPC), netbooks, personal digital assistants (PDA), televisions, displays and other electronic devices, and the embodiment of the present application does not impose any restrictions on the specific type of electronic equipment. Exemplary embodiments of electronic devices include but are not limited to electronic devices equipped with or other operating systems, as well as other types of computer systems.
[0052] Figure 1 A schematic diagram of the structure of the scheduling system provided for this application.
[0053] The resource scheduling method provided in the embodiment of the present application can be applied to Figure 1 A scheduling system 100 is shown.
[0054] The scheduling system 100 is used to obtain the priority of the object (ie, the object priority) to obtain an object priority list, so as to perform resource scheduling based on the object priority list.
[0055] In the embodiments of the present application, an object may include one or more of the following: a task, a process, and a thread. A task represents a work element to be completed by a computer, and it is composed of one or more instruction sequences processed by a control program. A task can be carried by a process or a thread.
[0056] A task is an activity performed by software. In simple terms, it is an operation to achieve a certain purpose. A task is usually a single run of a program, such as reading data and putting it into memory, closing a file, opening a dialog box, etc.
[0057] A process refers to the execution of a program, which can be understood as a program running in the system. In simple terms, a process can be regarded as an independent program, which has a complete data space and code space in the memory. The data and variables owned by the process belong only to itself. Different processes are independent of each other, such as independent address space and independent resources. Each process runs in its dedicated and protected memory.
[0058] A process is the basic unit of resource allocation and can also be the basic unit of scheduling and operation. For example, when a user runs a program, the system creates a process and allocates resources to the process (such as memory space, disk space, input / output (I / O) devices, tables, etc.). The process is then placed in the ready queue of the process. If the process is selected by the process scheduler, the system will allocate the CPU and other related resources to it, so that the process can actually run. A process is a dynamic entity with its own life cycle, which reflects the entire dynamic process of a program running on a certain data set.
[0059] A thread is a program that runs independently in a process, that is, a thread exists in a process. Simply put, a thread is the basic execution unit of a process, and all tasks of a process are executed in a thread. A process can include one or more threads, and each thread shares the address space (such as code and global data or variables) and resources (such as memory resources, I / O resources, CPU resources, etc.) of the process, but each thread has its own stack and local variables. In other words, the global variables of a process are shared by all threads, and the resources allocated to the process by the system are available to all threads.
[0060] A thread is the smallest unit of computing in a process, that is, the basic unit of processor scheduling. If a process is understood as a task logically completed by the operating system, then a thread represents one of many possible subtasks to complete the task. Threads can be independently scheduled and executed on a processor, so multiple threads of a process can be executed on different processors.
[0061] A program has at least one process, and a process must have one and only one corresponding program. A process can have multiple threads, but at least one thread, and a thread can only belong to one process. The process is the basic unit of resource allocation (including CPU resources, memory resources, and input and output I / O resources), that is, resources are allocated to processes, and multiple threads in the same process share their resources. The thread is the basic unit of processor scheduling, that is, what actually runs on the processor is the thread. Each thread has an entry point for program execution, a sequential execution sequence, and an exit point for the program, but a thread cannot be executed alone and must form a process or exist in a program. Multiple threads in the same process can execute concurrently.
[0062] In the embodiment of the present application, the resources that can be scheduled by resource scheduling include but are not limited to: CPU resources, memory resources and I / O resources.
[0063] In the embodiment of the present application, each object has its corresponding priority. The object priority list obtained by the scheduling system 100 includes the priority of at least one object. Based on the object priority list, the object with the highest priority among the objects to be allocated resources or to be scheduled can be determined, so that the object with the highest priority can be determined as the next object to be allocated resources in priority. When the number of objects is two or more, and the object priority list only includes the priority of one object, then the object is the next object to be allocated resources in priority.
[0064] In an embodiment of the present application, the object priority list obtained based on the scheduling system 100 includes a process priority list and / or a thread priority list. The process priority list includes the priority of at least one process, and the thread priority list includes at least one thread priority. The process priority is used to indicate the importance of the process (or the service or task corresponding to the process) in the usage scenario. Each process has a corresponding priority, and the priority determines when it runs and the time it occupies resources. For example, the higher the priority of the process, the more likely it is to obtain CPU resources. The higher the priority of the process, the more CPU time slices it can occupy. The priority of the thread is similar to that of the process. The process competes for resources (such as CPU resources) in the system, and the thread competes for resources in the current process. The priority of the thread describes the importance of the thread in the scenario of running the program. Each thread has a corresponding priority, and the priority determines when it runs and the time it occupies resources. For example, the higher the priority of the thread, the more likely it is to obtain CPU resources. The higher the priority of the thread, the more CPU time slices it can occupy.
[0065] In some embodiments, the object priority list obtained based on the scheduling system 100 may include a task priority list, which includes at least one task priority. The priority of a task is similar to that of a process and will not be described in detail here.
[0066] In the embodiment of the present application, when the object priority list obtained by the scheduling system 100 is a process priority list, the object of scheduling is a process, and the scheduling system 100 can use the process priority list to schedule resources for the process. When the object priority list obtained by the scheduling system 100 is a thread priority list, the object of scheduling is a thread, and the scheduling system 100 can use the thread priority list to schedule resources for the thread.
[0067] In the embodiment of the present application, the scheduling system 100 defines a sub-scenario of a usage scenario, which is related to the user's operation behavior in the usage scenario, and the operation behavior triggers the operating system to schedule an object. In the embodiment of the present application, the object priority list obtained by the scheduling system 100 includes an object priority list in the usage scenario, and also includes an object priority list corresponding to the sub-scenario in the usage scenario, and the specific content will be introduced below.
[0068] The scheduling system 100 includes an acquisition module 101, a scene determination module 102, a first determination module 103, and a second determination module 104. The scheduling system 100 can be deployed in a server and / or an electronic device, and the specific application of the scheduling system 100 will be described in detail below.
[0069] The acquisition module 101 is used to acquire scene information and service usage information.
[0070] Among them, scene information and service usage information are all from electronic devices (such as Figure 7 The electronic device 701 or Fig.13 The electronic device 1301 or Fig.15 Electronic device 1501 is shown).
[0071] Among them, scene information includes but is not limited to: time information (such as time period, moment), geographic location information (user's longitude and latitude, time zone), WiFi connection status, weather information, Bluetooth headset connection status, car Bluetooth connection status, flight travel information, power of electronic devices, consumer order information and user's exercise status and other information. This application does not make specific limitations on this.
[0072] Among them, the service usage information is the usage information of the services provided by the user's electronic device, where the services provided by the electronic device used by the user include but are not limited to: applications, desktops, card-type services, and functional modules in a certain application. Usage information is not limited to: frequency of use, time of use, and order of use. Among them, when the number of services provided by the user's electronic device is two or more, the order of use is the order in which the two or more services are used in time. For example, in the above-mentioned company lunch break scenario, use the desktop first, and then use Huawei Video.
[0073] When the acquisition module 101 is integrated on an electronic device, the acquisition module 101 is used to collect scene data and service usage information on the electronic device to obtain scene information based on the scene data. For example, the acquisition module 101 includes an acceleration transducer of the electronic device, and the acceleration (or voltage signal) collected based on the acceleration transducer is the scene data, and the user's movement status is obtained based on the collected acceleration analysis. When the acquisition module 101 is not integrated on the electronic device, a corresponding acquisition module is deployed on the electronic device, and the acquisition module collects scene data and service usage information on the electronic device. The acquisition module 101 acquires the scene data and service usage information collected by the acquisition module deployed on the electronic device.
[0074] The scene information and service usage information obtained by the acquisition module 101 may come from electronic devices of different users, and / or from different types of electronic devices (such as mobile phones or watches, etc.), and / or from different situations of the same electronic device (such as different times and / or different locations, etc.).
[0075] See also Figure 2 The acquisition module 101 includes a service acquisition unit 111, a scene acquisition unit 121 and a sending unit 131.
[0076] The service acquisition unit 111 is used to obtain service usage information of the electronic device. For example, the service acquisition unit 111 is used to capture the application on the electronic device used by the user, and record the timestamp of using the application (such as the time when the application is opened) to obtain the historical usage information of the application. The service acquisition unit 111 can be used to capture the desktop on the electronic device used by the user, and record the timestamp of using the desktop (such as the time when the desktop is entered) to obtain the historical usage information of the desktop. The service acquisition unit 111 can be used to capture the module (function) of the application used by the user, and record the usage timestamp to obtain the historical usage information of the application module.
[0077] The scene acquisition unit 121 is used to acquire scene information. For example, the scene acquisition unit 121 acquires time information based on a timer, acquires geographic location information based on a global positioning system (GPS) of an electronic device, and acquires the user's motion status based on the acceleration sensor.
[0078] The sending unit 131 is used to send the obtained service usage information and scene information to the downstream (such as the scene determination module 102). The sending mode of the sending unit 131 can be scheduled batch sending or stream-based sending, which is not specifically limited in this application.
[0079] In some embodiments, the acquisition module 101 may further include a data donation unit 141. The data donation unit 141 is used to obtain data donation information donated by the application manufacturer to the operating system. The scene acquisition unit 121 may use the data donation information obtained from the data donation unit 141 as scene information. For example, application A donates the user's takeaway order information to the mobile phone manufacturer. The takeaway order information obtained by the data donation unit 141 is used as scene information. For another example, a sports application donates the user's sports data to the data donation unit 141, and the scene acquisition unit 121 may obtain the user's sports status based on the data donation unit 141.
[0080] In some embodiments, the acquisition module 101 may further include a first storage unit 151. The first storage unit 151 is used to store service usage information, scenario information, data donation information, etc. The sending unit 131 sends the information stored in the first storage unit 151 to the downstream.
[0081] The scenario determination module 102 is used to determine the usage scenario.
[0082] In an embodiment of the present application, the usage scenario defined by the scene determination module 102 is related to the scene information of the electronic device. The scene determination module 102 can determine the usage scenario based on the scene information of the electronic device obtained, such as determining the usage scenario based on the time and space information of the electronic device, such as the morning commute scene and the company lunch break scene in the above examples.
[0083] In other embodiments, the usage scenario defined by the scenario determination module 102 is related to the service information, which is the relevant information of the service used by the user, and the service used by the user is a service provided by the electronic device, such as an application, a desktop, etc. The relevant information includes the service name (such as the application name), the service type (such as interaction, game), etc. The scenario determination module 102 can determine the usage scenario based on the service information, such as determining the usage scenario based on the application currently used by the user, such as Huawei video scenario, SMS scenario, etc. In some embodiments, the scenario determination module 102 determines the usage scenario based on the service currently used by the user, such as a desktop scenario, a negative one screen scenario, etc.
[0084] In an embodiment of the present application, the scene determination module 102 can obtain service information from the service usage information, such as obtaining the service closest to the current moment used by the user from the service usage information, and determining the usage scene based on the service closest to the current moment used by the user. For example, at time T1, the user used the Huawei Video application, and at time T2, the user exited the Huawei Video and used the Sports Health application, and time T2 is the closest moment to the current moment, then it can be determined that the usage scene at the current moment is the Sports Health scene.
[0085] See also Figure 3 The scene determination module 102 includes: a configuration unit 112 and a second storage unit 122 .
[0086] The configuration unit 112 is used to obtain configuration information input by an operator or user. The configuration information includes a scenario name of a usage scenario and matching information for matching the usage scenario (such as the above-mentioned scenario information and service information). There is a corresponding relationship between the usage scenario and the matching information. For example, when the information obtained from the electronic device is consistent with the matching information of the usage scenario A, it can be determined that the electronic device is in the usage scenario A based on the obtained information. Or, when it is determined that the electronic device is in the usage scenario A, the information obtained from the electronic device is consistent with the matching information of the usage scenario A.
[0087] In some embodiments, the configuration unit 112 is used to provide a configuration interface for operators or users to input configuration information and obtain the configuration information. In some embodiments, the configuration unit 112 is responsible for scene management, including adding a new use scene, that is, adding a scene name and corresponding matching information, deleting a use scene, that is, deleting a scene name and corresponding matching information, editing a use scene, that is, editing a scene name and corresponding matching information, etc.
[0088] The second storage unit 122 is used to store configuration information. In other words, the second storage unit 122 stores the scene name of the usage scene and the matching information corresponding to the usage scene.
[0089] In some embodiments, the configuration information includes an identifier for uniquely identifying a usage scenario, such as a scenario ID, and matching information corresponding to the usage scenario. This application does not specifically limit the identifier for uniquely identifying a usage scenario.
[0090] In some embodiments, the scene determination module 102 further includes a first interface unit 132, and the first interface unit 132 is used to index the information stored in the second storage unit 122 and provide a query service interface to the outside.
[0091] In some embodiments, the scenario determination module 102 further includes an automatic configuration switch unit 142. The automatic configuration switch unit 142 can be turned on in response to a user's operation. When the switch of the automatic configuration switch unit 142 is turned on, the first determination module 103 is allowed to mine high-frequency matching information, and then generate a usage scenario based on the high-frequency matching information, thereby overcoming the problem that the usage scenarios of manual configuration are limited and the coverage rate is not high.
[0092] In some embodiments, high-frequency matching information and a unique identifier of a usage scenario generated based on the high-frequency matching information are stored. When storing the unique identifier of a usage scenario generated based on the high-frequency matching information, the unique identifier of the usage scenario can be randomly determined by the scheduling system 100, such as the scheduling system 100 randomly determining a scene name, and displaying the determined scene name and the corresponding high-frequency matching information on the configuration interface, which can be subsequently modified to a suitable scene name on the configuration interface.
[0093] In the embodiment of the present application, the scene determination module 102 pre-stores the matching information and the corresponding usage scenarios. The corresponding usage scenarios are matched from fine to coarse according to the granularity of the matching information. For example, if the time information is 4:30, the matching information stored by the scene determination module 102 includes: 4:30 (corresponding to the matching information A) and the time period from 4:00 to 5:00 (corresponding to the matching information B), then it is prioritized to determine whether the obtained information is consistent with the matching information A. If they are consistent, the usage scenario is determined to be the usage scenario corresponding to the matching information A. If they are inconsistent, it is continued to determine whether the obtained information is consistent with the matching information B.
[0094] In some embodiments, the corresponding usage scenarios are matched from most to least according to the amount of information that needs to be matched. For example, the time information (4:30), location information (located in the company) and WiFi connection status (not connected to WiFi) are obtained, and the scene determination module 102 stores the following matching information: matching information a includes time information (4:30) and location information (located in the company), matching information b: includes time information (4:30), location information (located in the company) and WiFi connection status (not connected to WiFi), then the obtained information is preferentially compared with the matching information b. If consistent, the usage scenario is determined to be the usage scenario corresponding to the matching information b. If inconsistent, continue to determine whether the obtained information is consistent with the matching information a.
[0095] In some embodiments, the scene determination module 102 stores the guaranteed scene to ensure that the corresponding scene can be matched when the usage scene is matched. The matching information corresponding to the guaranteed scene must contain any one or more of the following information: time information, geographic location information. When the scene information to be matched has only time period information, it can be determined which scene to fall into based on the time period information. For example, the scene determination module 102 stores the usage scenes corresponding to each time period, such as the usage scenes corresponding to the daytime time period and the night time period. If the scene information to be matched has only the geographic location, it can also be determined which scene to fall into based on the geographic location. Based on the influence of the user's living habits or biological clock, there will be corresponding usage service needs in fixed time periods, such as the need to open the takeaway application to buy food between 11-1 noon. Correspondingly, based on the location limitation, the changes in the role played by the user in society, etc., there will be corresponding usage service needs at a fixed address, such as the need to open the mailbox application in the company to facilitate work affairs.
[0096] The matching information corresponding to the guaranteed scenario can be set according to actual conditions, and this application does not make any specific limitations on this.
[0097] The first determination module 103 is used to determine an object priority list corresponding to a usage scenario.
[0098] The first determination module 103 can mine the user's usage habits of the service in the usage scenario based on the service usage information based on machine learning, pattern recognition algorithms, etc., and determine the corresponding object priority list in the usage scenario based on the usage habits.
[0099] In the usage scenario determined based on the scenario information, resource scheduling between processes is involved, and the object priority list corresponding to the usage scenario is a process priority list. In the usage scenario determined based on the service information, resource scheduling between threads is involved, and the object priority list corresponding to the usage scenario is a thread priority list.
[0100] In an embodiment of the present application, when the scene information and service usage information collected by the acquisition module 101 are sent downstream, the scene information and / or service usage information are input into the scene determination module 102 to determine the usage scene, and the service usage information is input into the first determination module 103 to determine the object priority list. When the above-mentioned scene information and service usage information are associated with each other, the determined usage scene corresponds to the determined object priority list, that is, the determined object priority list is the object priority corresponding to the usage scene. The scene information and service usage information are associated with each other including: the scene information and the service usage information are both from the same device, and the time of acquiring the scene information is associated with the time of acquiring the service usage information, such as for the same device, the scene information and service usage information obtained at 3-4 o'clock on the same day are associated with each other. When the service information is determined based on the service usage information, and then the usage scene is determined based on the service information, the determined usage scene corresponds to the object priority determined based on the service usage information.
[0101] In some embodiments, the acquisition module 101 may identify the scene information and service usage information associated with each other in advance. For example, if the scene information a and the service usage information b are identified to be associated with each other, the object priority list corresponding to the usage scene determined based on the scene information a is: the object priority list determined based on the service usage information b.
[0102] See also Figure 4 , the first determination module 103 includes a data engineering unit 113, a machine learning unit 123 and an output unit 133.
[0103] The data engineering unit 113 is used to process the service usage information input and output data obtained by the acquisition module 101 to obtain the data format required by the machine learning unit 123.
[0104] The machine learning unit 123 is used to process the service usage information processed by the data engineering unit 113, and mine the user's usage habits of using services to obtain an object priority list, which indicates the user's habit of using services and also indicates the user's habit of switching services. Accordingly, the obtained object priority list indicates the user's habit of using services and also indicates the user's habit of switching services. If the machine learning unit 123 includes a priority mining model, the machine learning unit 123 inputs the service usage information processed by the data engineering unit 113 into the priority mining model, processes the service usage information based on the parameters of the priority mining model, and mines the user's usage habits of using services to obtain an object priority list.
[0105] Among them, the priority mining model can use machine learning, pattern recognition algorithms and other algorithms to mine data. The priority mining model can be a neural network model, etc., and this application does not make specific limitations on this. Using machine learning, pattern recognition algorithms and other algorithms to mine data can refer to existing mature technologies, which will not be repeated here.
[0106] In the embodiment of the present application, the machine learning unit 123 can be used to mine the service usage information of multiple different users to mine the user's service usage habits that are universal. In other embodiments, the machine learning unit 123 can be used to mine the service usage information of the same user (such as service usage information collected at different times and locations) to mine the user's service usage habits.
[0107] In some embodiments, the machine learning unit 123 may employ a machine learning platform to accelerate the training and / or reasoning of a priority mining model.
[0108] In some embodiments, the scheduling system 100 can obtain associated scenario information and service usage information from multiple different devices. When the scenario information of the multiple devices matches the same usage scenario, the machine learning unit 123 determines the user's service usage habits in the usage scenario based on the service usage information of the multiple devices to obtain an object priority list in the usage scenario.
[0109] The output unit 133 is used to output the object priority list obtained by the machine learning unit 123.
[0110] In some embodiments, the data engineering unit 113 is used to process the scene information input and output data obtained by the acquisition module 101 to obtain the data format required by the machine learning unit 123. The machine learning unit 123 is used to process the scene information processed by the data engineering unit 113 to mine high-frequency scene information.
[0111] In some embodiments, the first determination module 103 further includes a scene mining switch unit 143. The switch of the scene mining switch unit 143 can be turned on in response to the operation of the user or operator. When the switch of the scene mining switch unit 143 is turned on, the machine learning unit 123 is allowed to mine out scene information that appears frequently (or appears frequently together), and automatically register the use scenario determined based on the scene information that appears frequently in the scene determination module 102, and the machine learning unit 123 mines out the object priority list under the use scenario.
[0112] For example, when the machine learning unit 123 mines out that the three scene information [12-14 o'clock, rain, takeaway order] often appear together, if the number of times they appear together reaches a preset threshold, then the three scene information are high-frequency co-occurring scene information. The preset threshold can be set according to the actual situation, such as 30, 50, 100, etc. When there is no matching information of the usage scene in the scene determination module 102 including the three high-frequency co-occurring scene information, the machine learning unit 123 automatically registers a new usage scene in the scene determination module 102, such as defining a new scene name XYZ, and the matching information of the new usage scene includes the above three high-frequency co-occurring scene information. And the machine learning unit 123 mines out the object priority list corresponding to the XYZ scene. When mining the object priority list corresponding to the XYZ scene, the machine learning unit 123 determines the service usage information associated with the three high-frequency co-occurring scene information (i.e. [12-14 o'clock, rain, takeaway order]). The associated service usage information corresponds to the device of the three high-frequency co-occurring scene information, and the acquisition time corresponds. For example, when the device obtains the three high-frequency co-occurring scene information, the service usage information obtained is service usage information a, then the service usage information a is the service usage information associated with the three high-frequency co-occurring scene information. In other words, for the same device, when the device obtains the three high-frequency co-occurring scene information, the service usage information obtained is the service usage information associated with the scene information. Alternatively, when the device obtains certain service usage information, the scene information obtained is the three high-frequency co-occurring scene information, then the service usage information is the service usage information associated with the three high-frequency co-occurring scene information.
[0113] The above-mentioned high-frequency co-occurring scene information may be high-frequency co-occurring scene information of multiple different devices, such as [12-14 o'clock, rain, takeaway order] often appears together in the scene information provided by device A, and [12-14 o'clock, rain, takeaway order] also often appears together in the scene information provided by other N devices, where N is an integer greater than or equal to 1. Or for a certain device, some scene information often appears together at a high frequency within a preset time period.
[0114] The second determination module 104 is used to determine the object priority list corresponding to the sub-scenario. The second determination module 104 is used to determine the sub-scenario of the usage scenario and determine the object priority list corresponding to the sub-scenario.
[0115] See also Figure 5 The second determining module 104 includes a sub-scene acquiring unit 114 , a third storage unit 124 and a second interface unit 134 .
[0116] The sub-scenario acquisition unit 114 is used to determine the sub-scenario of the usage scenario, and determine the object priority list corresponding to the sub-scenario based on the object priority list of the usage scenario. The object priority list corresponding to the usage scenario indicates the user's habit of using services in the usage scenario, and also indicates the user's habit of switching services in the usage scenario, such as switching the corresponding services in order from high to low priority. Specifically, the scheduling system 100 (such as the sub-scenario acquisition unit 114) determines the sub-scenario included in the usage scenario based on the services indicated by the object priority list of the usage scenario.
[0117] For example, in the process priority list corresponding to the company lunch break scenario, the priorities from high to low are: desktop process > Huawei video process > SMS process > negative one screen process, and the priorities of the services indicated in the process priority list are from high to low: desktop > Huawei video > SMS > negative one screen. The sub-scenario included in the company lunch break scenario is: [Desktop] sub-scenario, [Desktop, Huawei video] sub-scenario, and [Desktop, Huawei video, SMS] sub-scenario. Among them, the [Desktop] sub-scenario can be that the user is using the desktop or exiting the desktop, and the priorities in the process priority list corresponding to this sub-scenario are from high to low: Huawei video process > SMS process > negative one screen process. The [Desktop, Huawei video] sub-scenario can be that the user exits the desktop and enters Huawei video, or the user exits the desktop and enters Huawei video, or the user exits the desktop and exits Huawei video. The priorities in the process priority list corresponding to this sub-scenario are from high to low: SMS process > negative one screen process. Correspondingly, the process priority list corresponding to the [Desktop, Huawei video, SMS] sub-scenario includes: negative one screen process. The process with the highest priority in the process priority list is the next object to be allocated resources. For example, in the [Desktop, Huawei Video, SMS] sub-scenario, the next process to be allocated is the process of the negative one screen. The operating system can prepare resources for the process of the negative one screen in advance and allocate resources to the process of the negative one screen first.
[0118] For example, the Huawei Sports Health application provides a health module and a sports module, and the health module includes a sports record module, a heart health module, a pressure module, a sleep module, etc., and the sports module includes an outdoor running module and an indoor running module. Based on the Huawei Sports Health application used by the user, the usage scenario is determined to be the Huawei Sports Health usage scenario. The priorities in the thread priority list corresponding to the Huawei Sports Health usage scenario are as follows: the thread of the sleep module> the thread of the heart health module> the thread of the outdoor running module. The sub-scenarios included in the Huawei Sports Health usage scenario are: [Sleep Module] sub-scenario and [Sleep Module, Heart Health Module] sub-scenario. Among them, the [Sleep Module] sub-scenario can be that the user is using the sleep module in the health module or exiting the sleep module. The priorities in the process priority list corresponding to the sub-scenario are as follows: the thread of the heart health module> the thread of the outdoor running module. The [Sleep Module, Heart Health Module] sub-scenario can be that the user exits the sleep module and enters the heart health module, or the user exits the sleep module and enters the heart health module, or the user exits the heart health module after exiting the sleep module. The thread priority list corresponding to the sub-scenario includes: the thread of the outdoor running module. The thread with the highest priority in the thread priority list is the next object to be allocated resources. For example, in the [Sleep Module, Heart Health Module] sub-scenario, the next process to be allocated is the thread of the outdoor running module. The operating system can prepare resources for the thread of the outdoor running module in advance and allocate resources to the thread of the outdoor running module first.
[0119] The third storage unit 124 is used to store sub-scenes and their corresponding object priority lists. The third storage unit 124 is also used to store usage scenarios and their corresponding object priority lists. The third storage unit 124 is also used to store sub-scenes corresponding to usage scenarios, and can store unique identifiers of usage scenarios and corresponding sub-scenes. The unique identifier of the sub-scene can be a scene name or a scene ID, which is not specifically limited.
[0120] The second interface unit 134 is used to create an index for the information stored in the third storage unit 124 and provide a query service interface externally.
[0121] In some embodiments, after the first determination module 103 determines the object priority list corresponding to the usage scenario, the scheduling system 100 (the first determination module 103 or the second determination module 104) determines the sub-scenario of the usage scenario according to the object priority list corresponding to the usage scenario, and maintains the sub-scenario of the usage scenario in the scene determination module 102, so that the subsequent object scheduling module 105 can determine the usage scenario and the sub-scenario based on the scene determination module 103.
[0122] In some embodiments, the first determination module 102 and the second determination module 103 may be combined into the same module (eg, a determination module), which has or can implement the functions of the first determination module 102 and the second determination module 103 .
[0123] In some embodiments, the scheduling system 100 may further include an object scheduling module 105. The object scheduling module 105 is used to perform resource scheduling based on the object priority list. When the object scheduling module 105 performs resource scheduling based on the object priority list, the probability of high-priority objects obtaining resources is increased, such as allocating resources to high-priority objects by priority. The specific content of how the object scheduling module 105 increases the probability of high-priority objects obtaining resources can refer to existing mature technologies, and will not be repeated here.
[0124] See also Figure 6 The object scheduling module 105 includes a first request unit 115 , a first acquisition unit 125 , a second acquisition unit 135 , a second request unit 145 , a processing unit 155 , a generalization unit 165 , an adjustment unit 1705 and a fourth storage unit 185 .
[0125] The object scheduling module 105 is deployed in the electronic device. When the object scheduling module 105 is to perform resource scheduling, the above-mentioned units start to execute their corresponding functions.
[0126] The first request unit 115 is used to send a request to the acquisition module 101, and receive the scene information and service usage information returned by the acquisition module 101 in response to the request. Specifically, the first request unit 115 is used to request the acquisition module 101 to obtain the scene information and service usage information of the device (i.e., the electronic device deployed by the object scheduling module 105). The acquisition module 101 returns the scene information and service usage information associated with each other to the first request unit 115 in response to the request.
[0127] The first acquisition unit 125 is used to send a request to the scene determination module 102, which carries the scene information obtained by the first request unit 115, and receives an identifier of the usage scenario (such as a scene name) returned by the scene determination module 102 in response to the request, wherein the usage scenario is: the scene determination module 102 responds to the request and maps the scene information carried by the request to the corresponding usage scenario.
[0128] In some embodiments, the acquisition module 101 may also be used to acquire the user's switching service operation. The first request unit 115 is used to send a request to the acquisition module 101 and receive the user's switching service operation returned by the acquisition module 101 in response to the request.
[0129] In some embodiments, the first acquisition unit 125 can be used to send a request to the scene determination module 102, which carries the scene information obtained by the first request unit 115 and the user's switching service operation, and receives the identifier of the usage scenario (such as the scene name) and the sub-scene returned by the scene determination module 102 in response to the request, wherein the sub-scene is: the scene determination module 102 responds to the request and determines the sub-scene according to the object priority list corresponding to the usage scenario and the service usage information.
[0130] The second acquisition unit 135 is used to send a request to the second determination module 103, the request carrying the identifier of the usage scenario obtained by the first acquisition unit 125, and receive the object priority list corresponding to the usage scenario returned by the second determination module 103 in response to the request.
[0131] In some embodiments, the second acquisition unit 135 is used to send a request to the second determination module 103, which carries the usage scenario and sub-scenario obtained by the first acquisition unit 125, and receives the object priority list corresponding to the sub-scenario returned by the second determination module 103 in response to the request.
[0132] In some embodiments, the first determination module 103 stores the usage scenarios and the corresponding object priority lists mined therefrom. Then the second acquisition unit 135 may send a request to the first determination module 103 to obtain the object priority lists of the usage scenarios.
[0133] The second request unit 145 is used to obtain an object priority list of the electronic device where it is deployed, such as obtaining a process priority list and / or a thread priority list currently being used by the operating system of the electronic device.
[0134] The processing unit 155 is used to match the usage scenario and the sub-scenario, and obtain the corresponding object priority list.
[0135] Specifically, after the first acquisition unit 125 determines the usage scenario, the processing unit 155 obtains the service switching operation of the user on the electronic device under the usage scenario, and then determines the sub-scenario of the usage scenario according to the service switching operation, and obtains the object priority list corresponding to the sub-scenario from the second determination module 104. Among them, the service switching operation can be to enter a certain service, or switch from a certain service to another service, wherein the number of switching times is not specifically limited. The service switching operation indicates a series of actions of the user on the electronic device (operating system) that trigger the scheduling of the operating system, especially the transition scenes between services, such as: unlocking into the desktop, switching from one application to another application, returning to the desktop from an application (such as a third-party application), etc.
[0136] More specifically, the processing unit 155 determines the target service (including the services that have been used and the services that are being used) used by the user in the usage scenario according to the service switching operation, and determines the sub-scenario of the usage scenario based on the target service. When the number of target services includes two or more, the sub-scenario of the usage scenario is determined based on the two or more target services and the order of use of the two or more target services in time. Exemplarily, the processing unit 155 obtains the user's service switching operation in the usage scenario (such as the above-mentioned morning commute scene) including: unlocking into the desktop, exiting the desktop and entering the Huawei video application, then it is determined that the target service of the electronic device used by the user includes the desktop and the Huawei video application, and the order of use is from the desktop to the Huawei video, then it can be determined that the [desktop, Huawei video] sub-scenario in the above-mentioned morning commute scene matches.
[0137] It is understandable that the above service switching operation is extensible and is not limited to the above example. The service switching operation may include one or more operations, and the operation may be in the form of clicking or pressing, etc. The present application does not specifically limit the form of the operation.
[0138] The generalization unit 165 is used to turn on the switch in response to the user's operation. When the switch of the generalization unit 165 is turned on, if it cannot strictly match the pre-defined usage scenario (such as the usage scenario configured by the scenario determination module 102) and sub-scenario (such as the sub-scenario of the usage scenario determined by the second determination module 104), it is allowed to use similar usage scenarios and sub-scenarios. For example, when the information obtained is [12-14 o'clock, raining, takeaway order], but the first determination module 103 does not have matching information including [12-14 o'clock, raining, takeaway order], matching information similar to the information [18-20 o'clock, raining, takeaway order] can be used for matching, and then when the information is determined to be [12-14 o'clock, raining, takeaway order], its corresponding object priority list is the object priority list related to the usage scenario corresponding to the matching information [12-14 o'clock, raining, takeaway order]. The definition and maintenance of similar relationships are also carried by this generalization unit 165. The definition of similarity may include geographic location consistency, other information has errors, and time consistency, other information has errors. The range of the error can be set according to the actual situation, and the application does not specifically limit the definition of similarity. When the switch of the generalization unit 165 is turned off, it is necessary to strictly match the pre-defined usage scenario and sub-scenario, that is, the scenario information must completely correspond to the matching information to determine the usage scenario, and the services used and the order of the services used must completely match to determine the sub-scenario.
[0139] The adjustment unit 1705 is used to perform resource scheduling based on the obtained object priority list. The adjustment unit 1705 performs resource scheduling based on the obtained object priority list, including: directly allocating resources based on the object priority list, or adjusting the object priority list used on the operating system based on the object priority list to generate an adjusted object priority list. If the usage scenario or sub-scenario cannot be matched, the object priority list on the operating system is not operated.
[0140] In some embodiments, the functionality of the adjustment unit 1705 may be integrated into the processing unit 155 , that is, the processing unit 155 may perform resource scheduling based on the obtained object priority list.
[0141] The fourth storage unit 185 is used to store various types of data and temporary data, such as usage scenarios and their corresponding object priority lists, sub-scenario and their corresponding object priority lists, etc.
[0142] It can be understood that the above-mentioned modules can be functionally combined according to actual conditions (such as the first determination module and the second determination module are combined into a determination module), or functionally divided, and the above-mentioned units can also be functionally combined or functionally divided according to actual conditions, and this application does not make specific limitations on this.
[0143] The following is an exemplary introduction to an application scenario of the scheduling system 100.
[0144] like Figure 7 As shown, the resource scheduling system 700 includes an electronic device 701 , a first server 702 and a second server 703 .
[0145] The electronic device 701 may be any of the above electronic devices, and its hardware structure may refer to Fig.17 , its software system structure can refer to Fig.18 , this application does not specifically limit the type of electronic device 701.
[0146] The resource scheduling system 700 may include two or more electronic devices, which may belong to different users or may be devices of different types, etc. This application does not make any specific limitation on the two or more devices.
[0147] The first server 702 is used to provide a corresponding configuration interface, and the first server 702 can be implemented as a portal server on the cloud side. The second server 703 can be implemented as a cloud server, and the second server 703 can also be implemented as a server cluster. The application does not specifically limit the types of the first server 702 and the second server 703.
[0148] The acquisition module 101 and the object scheduling module 105 of the scheduling system 100 are deployed on the electronic device 701 , the scene determination module 102 of the scheduling system 100 is deployed on the first server 702 , and the first determination module 103 and the second determination module 104 of the scheduling system 100 are deployed on the second server 703 .
[0149] In some embodiments, the object scheduling module 105 can be implemented as a module of an operating system on the electronic device 701, and this application specifically defines this step.
[0150] The electronic device 701 collects its scene information and service usage information.
[0151] Please also read Figure 8 , the acquisition module 101 transmits the collected scene information and service usage information to the scene determination module 102. When the acquisition process of the object priority list in the scheduling system 100 (such as training the priority mining model or deriving the priority mining model) is triggered regularly, the acquisition module 101 can batch transmit the device data through the offline HIVE table mechanism; when the acquisition process of the object priority list is based on event real-time refresh, the acquisition module 101 can transmit the collected device data in real time through the message queue (MQ) mechanism.
[0152] The data format of IF1 transmitted from the acquisition module 101 to the scene determination module 102 is <user ID, [scene information], [service usage information]>.
[0153] Among them, the user ID field in the data format of IF1 is used to record the identifier used to distinguish other devices or other users. The user ID can be: the unique device identifier (UDID) of the device or the advertising identifier (OAID). In some embodiments, the user ID can also be the user's login account, such as the Huawei account used by the user to log in to a Huawei mobile phone. This application does not specifically limit this. The [Scene Information] field in the data format of IF1 is used to record the scene information collected by the electronic device 101, that is, the relevant information of the scene where the user is located. The relevant content of the scene information can be referred to above and will not be repeated here.
[0154] The [Service Usage Information] field in the data format of IF1 is used to record the service usage information collected by the electronic device 101. In the data format of IF1, [Scene Information] and [Service Usage Information] are related. The service usage information and scenario information uploaded by the same device at the same time are related to each other. [Service Usage Information] corresponds to the service usage record when the [Scene Information] is collected, that is, it corresponds to the sequence of services used by users in ascending time order under the [Scene Information]. The relevant content of the service usage information can be referred to above and will not be repeated here.
[0155] The scene determination module 102 manages the mapping relationship between the use scene and the matching information. The scene determination module 102 maintains the identifier of the use scene (such as the scene name) and the matching information. The scene determination module 102 can provide an application programming interface (Application Programming Interface, API) to the outside world using a RESTful (Representational State Transfer) protocol interface. The RESTful protocol interface is a specific implementation of the first interface unit 132. When the acquisition module 101 transfers data through the HIVE table mechanism or the MQ mechanism, it calls the application programming interface to perform scene matching.
[0156] The scenario determination module 102 matches the information in IF1 (such as scenario information or the above-mentioned service information) to the corresponding usage scenario, and determines the scenario name of the usage scenario corresponding to the information. After matching the corresponding usage scenario, the scenario determination module 102 outputs the data format of IF2 of the first determination module 102 as <user ID, usage scenario, [service usage information]>. The relevant content of the user ID in IF2 can refer to the above, and the relevant content of the [service usage information] in IF2 can refer to the above, which will not be repeated here. The usage scenario field in IF2 is the identifier of the usage scenario (such as the scenario name).
[0157] The first determination module 102 processes the [service usage information] in IF2, and then inputs it into the priority mining model for reasoning, so as to use the priority mining model to mine the user's usage habits in the usage scenario as an object priority list. The data format of IF3 transmitted from the first determination module 103 to the second determination module 104 is <user ID, usage scenario, [object priority list]>. The relevant content of the user ID in IF3 can refer to the above, and the relevant content of the usage scenario in IF3 can refer to the above, which will not be repeated here. The [object priority list] field in IF3 records the object priority list corresponding to the usage scenario in IF3, and the object priority list is mined by the priority mining model.
[0158] In some embodiments, the acquisition module 101 transmits the scene information and the corresponding service usage information to the first determination module 103. The first determination module 103 first matches the usage scenario corresponding to the [scene information] in the scene determination module 102 based on the obtained information (such as the scene information or the above-mentioned service information), that is, determines the usage scenario corresponding to the collected scene information.
[0159] The second determining module 104 further refines the object priority list of the scene granularity into the sub-scene granularity according to the object priority list in the usage scenario.
[0160] Specifically, the second determination module 104 further refines and splits the usage scenario of IF3 and the corresponding object priority list into sub-scenarios. The data format of IF4 output by the second determination module 104 is <user ID, usage scenario, [sub-scenario], [object priority list]>. Among them, the user ID and the relevant content of the usage scenario in IF4 can refer to the above, and the [sub-scenario] in IF4 is used to record the unique identifier of the corresponding sub-scenario (such as the scene name) to distinguish other sub-scenarios. It will not be repeated here.
[0161] When the number of sub-scenes of the usage scenario includes two or more, the data format of IF4 is <user ID, usage scenario, [sub-scene 1], [object priority list 1], [sub-scene 2], [object priority list 2]>, where [sub-scene 1] in IF4 is used to record the identifier (such as scene name) corresponding to sub-scene 1, and [sub-scene 2] is used to record the identifier (such as scene name) corresponding to sub-scene 2. Sub-scene 1 corresponds to [object priority list 1], and sub-scene 2 corresponds to [object priority list 2]. Sub-scene 1 and sub-scene 2 are both partial scenes under the usage scenario, and object priority list 1 and object priority list 2 are parts of the object priority list corresponding to the usage scenario.
[0162] Figure 8The data transmission process from IF1 to IF4 in the data mining corresponds to the process of training the priority mining model to obtain the object priority list. The above-mentioned training priority mining model process can be triggered to execute periodically or refreshed in real time based on events. Periodic triggering execution refers to using a scheduled task to obtain the scene information and service usage information of the past N days to retrain the priority mining model, overwrite the old model, and fully refresh the object priority list of all users in different usage scenarios. Event-based real-time refreshing means that the acquisition module 101 monitors the user's usage of the device (such as electronic device 701) in real time. Once the scene information and / or service usage information changes, the incremental data (i.e., the changed scene information and / or service usage information) is uploaded, and the first determination module 103 performs incremental training based on the incremental data. The second determination module 102 incrementally refreshes the object priority list of the user's sub-scene based on the new object priority list generated by the first determination module 103.
[0163] Figure 8 The data transmission process from IF5 to IF7 corresponds to the operating system scheduling process (including the process derived using the trained priority mining model).
[0164] The object scheduling module 105 calls the acquisition module 101 and the scene determination module 102 to determine whether the information (such as scene information or service information) collected by the acquisition module 101 hits a certain usage scene. If it hits, it determines that the current usage scene is hit, and obtains the object priority list corresponding to the usage scene from the first determination module 103. If the current operating system already has an object priority list, the object scheduling module 105 adjusts the existing object priority list of the operating system according to the object priority list obtained from the first determination module 103.
[0165] Specifically, the object scheduling module 105 requests data from the acquisition module 101 to obtain scene information and service usage information. Or the acquisition module 101 transmits the obtained scene information and service usage information to the object scheduling module 105. The data format of IF5 transmitted between the object scheduling module 105 and the acquisition module 101 is <[scene information], [service usage information]>. Since the data is transmitted locally on the device, there is no need to bring the user ID field. The relevant contents of the [scene information] field and the [service usage information] field in IF5 can refer to IF1. The object scheduling module 105 calls the application programming interface of the scene determination module 102 to map the <[scene information], [service usage information]> obtained from the acquisition module 101 into <[usage scenario], [service usage information]>, that is, the scene determination module 102 matches the [scene information] to the corresponding [usage scenario]. The data format of the IF6-input transmitted between the object scheduling module 105 and the scene determination module 102 is: <[scene information], [service usage information]>, and the data format of the IF6-output is: <[usage scenario], [service usage information]>.
[0166] In the embodiment of the present application, the object scheduling module 105 transmits the <[scenario information], [service usage information]> obtained from the acquisition module 101 to the scenario determination module 102. The scenario determination module 102 determines whether the scenario is hit according to the [scenario information]. If it is hit, it outputs the hit scenario (such as scenario ID or scenario name) to the object scheduling module 105, that is, the [usage scenario] in the data format of IF6-output. The object scheduling module 105 obtains the object priority list corresponding to the usage scenario from the first determination module 103 according to the scenario ID of the received usage scenario, and / or obtains the object priority list corresponding to the sub-scenario of the usage scenario from the second determination module 104.
[0167] The object scheduling module 105 obtains the usage scenario and its corresponding object priority list, as well as all sub-scenarios of the usage scenario and the object priority list corresponding to the sub-scenarios, which can be stored locally so that when the subsequent object scheduling module 105 matches the corresponding usage scenario or sub-scenario, the corresponding object priority list can be directly obtained locally, thereby reducing network communication transmission and improving performance.
[0168] In some embodiments, the second determination module can transmit the [scenario information] and [object priority list] related to the user ID to the corresponding device according to the user ID. For example, the first determination module 103 and the second determination module 104 mine the object priority list D corresponding to the usage scenario C based on the data from the device A, and then transmit the usage scenario C and the corresponding object priority list D to the device A according to the user ID of the device A.
[0169] The object scheduling module 105 determines the services that the user has used and the services that are being used (i.e., the target services) in the usage scenario according to the user's switching service operation, and determines the sub-scenario according to the target service. When the object scheduling module 105 obtains the object priority list corresponding to all sub-scenarios of the usage scenario, the object scheduling module 105 obtains the corresponding object priority list according to the sub-scenario in which it is located. When the object scheduling module 105 obtains the object priority list corresponding to the usage scenario, the object scheduling module 105 determines the object priority list corresponding to the current sub-scenario according to the current sub-scenario and the object priority list obtained from the first determination module 103. That is, the object scheduling module 105 integrates the function of splitting sub-scenario of the second determination module 104, and the object scheduling module 105 can generate the object priority list of the corresponding sub-scenario according to the current sub-scenario and the object priority list obtained from the first determination module 103.
[0170] In some embodiments, the object scheduling module 105 determines the sub-scenario it is in according to the services it has used and the services it is using, and obtains the object priority list corresponding to the sub-scenario from the second determination module 104 according to the sub-scenario it is in.
[0171] In the embodiment of the present application, the object scheduling module 105 determines the sub-scene in which it is located, and can also be: the sub-scene is defined in the scene determination module 102. The object scheduling module 105 transmits the <[scene information], [service usage information]> obtained from the acquisition module 101 to the scene determination module 102, and the scene determination module 102 determines whether the use scene is hit according to the [scene information]. When it is hit, the scene determination module 102 determines the current sub-scene according to the [service usage information], and outputs the use scene and its corresponding sub-scene to the object scheduling module 105, and obtains the object priority list corresponding to the sub-scene of the use scene from the second determination module 104 according to the received.
[0172] In some embodiments, the data obtained by the acquisition module 101 is transmitted to the scene management module 102 to perform the above-mentioned process from IF1 to IF4, and is also transmitted to the process scheduling module to perform the above-mentioned process from IF5 to IF7. For example, the user ID of the electronic device 701 is the advertising identifier: edffff6fe-6536-c8e3-67bb-6fbfffd. After the data obtained by the acquisition module 101 in the electronic device 701 performs the above-mentioned process from IF1 to IF4, the second determination module 104 obtains the <usage scenario, [sub-scenario], [object priority list]> corresponding to the user ID (advertising identifier: edffff6fe-6536-c8e3-67bb-6fbfffd). The object scheduling module 105 calls the application programming interface of the scene management module 102 to map the <[scene information], [service usage information]> obtained from the acquisition module 101 into <[usage scenario]>. The object scheduling module 105 obtains the <usage scenario, [sub-scenario], [object priority list]> corresponding to the user ID (advertising identifier: edffff6fe-6536-c8e3-67bb-6fbfffd) from the second determination module 102.
[0173] In some embodiments, the object scheduling module 105 can perform object scheduling based on the obtained object priority list to increase the probability of high-priority objects obtaining resources. The object scheduling module 105 can also adjust the object priority list in the current operating system based on the obtained object priority list, such as obtaining an existing object priority list of the operating system, adjusting the existing object priority list according to the obtained object priority list, and outputting the IF7 data format: [adjusted object priority list].
[0174] The following describes the intelligent scheduling provided by the embodiment of the present application, with the object being the process and the object scheduling module 105 including the process scheduling module.
[0175] For example, on the Mth day, in the company and the time period is 12-14 o'clock, the user uses the services of the electronic device 701 including: desktop, Huawei video, text messages, and the negative one screen. On the M+1st day, in the company and the time period is 12-14 o'clock, the user uses the services of the electronic device 701 including: desktop, text messages, and the negative one screen. On the M+2nd day, in the company and the time period is 12-14 o'clock, the user uses the services of the electronic device 701 including: desktop, Huawei video, text messages, and the negative one screen.
[0176] like Fig. 9 As shown, the scenario determination module 102 of the first server 702 defines the usage scenario corresponding to the matching information [12-14 o'clock, in the company] as 'lunch break in the company', and the usage scenario corresponding to the matching information [8-9 o'clock or 18-19 o'clock, in the company] as 'punching in and out of get off work'.
[0177] like Fig.10 As shown, the electronic device 701 collects the scene information [12-14 o'clock, in the company] and the service usage information corresponding to the scene information is [desktop, Huawei video, text message, negative one screen], [desktop, text message, negative one screen] and [desktop, Huawei video, text message, negative one screen].
[0178] The electronic device 701 collects the data from the Mth day to the M+2th day (i.e. Fig.10 The scene information and service usage information (as shown) and their corresponding user IDs are transmitted to the first server 702.
[0179] The first determination module 102 matches the usage scenario of 'lunch break at the company' based on the obtained scenario information.
[0180] Please also read Fig.11 , the first determination module 103 of the second server 703 inputs the data from the Mth day to the M+2th day into the priority mining model, and mines out the user habit of the "lunch break at the company" usage scenario as [desktop, Huawei video, text message, negative one screen] based on the priority mining model, and sets the user habit as the object priority list in the "lunch break at the company" usage scenario, that is, in the "lunch break at the company" usage scenario, the desktop has a higher priority than Huawei video, Huawei video has a higher priority than text message, and text message has a higher priority than negative one screen. The second determination module 104 splits the object priority list in the "lunch break at the company" usage scenario into object priority lists corresponding to three sub-scenarios, namely: <user ID, lunch break at the company, [desktop], [Huawei video, text message, negative one screen]>, <user ID, lunch break at the company, [desktop, Huawei video], [text message, negative one screen]>, <user ID, lunch break at the company, [desktop, Huawei video, text message], negative one screen]>. Among them, <User ID, Lunch break at the company, [Desktop, Huawei Video], [SMS, -1 screen]> indicates that the usage scenario is [12-14 o'clock, at the company], and the sub-scenario is [Desktop, Huawei Video]. That is, this sub-scenario indicates that the user exits the desktop and enters Huawei Video. This sub-scenario can be using Huawei Video or exiting Huawei Video. The object priority list corresponding to this sub-scenario is [SMS, -1 screen]. That is, in the sub-scenario, the service with the highest priority is SMS, and resources can be allocated to SMS first, followed by -1 screen.
[0181] For the same usage scenario, the above-mentioned priority mining model can mine universal user usage habits based on the service usage information of multiple different users, and then determine the object priority list in the usage scenario based on the mined user usage habits. When the user service usage information corresponding to the usage scenario is constantly updated and changed, and the mined user usage habits change, the object priority list in the usage scenario is determined based on the newly mined user usage habits. For example, device 1 collects service usage information a of user A in the company and the time period is 12-14 o'clock, and device 2 collects service usage information b of user B in the company and the time period is 12-14 o'clock. By analogy, device K collects service usage information k of the corresponding user in the company and the time period is 12-14 o'clock. The scene information collected by the above K devices matches the usage scenario of "lunch break in the company". The priority mining model mines the common user usage habits in the usage scenario of "lunch break in the company" based on the service usage information collected by the K devices (such as service usage information a, b...k), so as to determine the object priority list in the usage scenario.
[0182] like Fig.12 For example, on the M+3 day, in the company and the time period is 12-14 o'clock, it is detected that the user uses the desktop of the electronic device 701 (i.e., switching service operations). The process scheduling module of the electronic device 701 detects that the scene information collected by the acquisition module 101 hits the usage scenario <lunch break at the company>, and then obtains the process priority corresponding to the usage scenario [desktop, Huawei video, text message, negative one screen]. The process scheduling module detects that the scene information collected by the acquisition module 101 hits the sub-scenario <lunch break at the company, [desktop]>, and then obtains the process priority corresponding to the sub-scenario as [Huawei video, text message, negative one screen]. Based on the object priority list of the sub-scenario, the process priority of the current operating system [music application a, Huawei video] is adjusted to obtain [Huawei video, text message, negative one screen, music application a]. At this time, the operating system prioritizes resources to Huawei video, followed by text messages, negative one screen, and music application a last.
[0183] In an embodiment of the present application, the scheduling system 100 collects scene information such as the time and space, geographic location, and service usage information of the user, and trains the priority mining model with the scene information and service usage information, thereby obtaining a priority mining model that changes with the user's usage scenario and the user's service usage habits. The priority mining model obtains an object priority list that is more in line with the user's usage habits in the usage scenario through data mining, which ensures smooth user use while also improving the efficiency of resource use, which is especially important for electronic devices with limited resources. In particular, during mining and learning (i.e., training the priority mining model), the resource scheduling system 700 can bring together the data collected from all users to fully coordinate, and for long-tail users (users with sparse behavior, including new users) and long-tail scenarios, when the user's device is connected to the resource scheduling system 700, an object priority list that is more in line with the user's usage habits can also be obtained, that is, the object priority list can also be more in line with the usage habits of the long-tail user. The scheduling system 100 can also perceive the sub-scenario of the user's usage scenario in real time, and intelligently adjust the object priority list according to the sub-scenario to ensure timely and accurate resource allocation and scheduling based on the user's usage scenario, which is conducive to improving the smoothness of device use and the efficiency of computing resource use.
[0184] The following example introduces another application scenario of the scheduling system.
[0185] like Fig.13 As shown, the resource scheduling system 130 includes an electronic device 1301 and a first server 1302. The difference between the resource scheduling system 130 and the resource scheduling system 700 is that the object priority list generation is implemented in the electronic device 1301. That is, the electronic device 1301 is further integrated with the module of the second server 703 on the basis of the electronic device 701. Compared with the resource scheduling system 700, the resource scheduling system 130 is suitable for products, countries (regions) or user locations with strict privacy protection policies. Service usage information, scenario information, etc. cannot be uploaded to the server. The resource scheduling system 130 implements the derivation and training of the object priority list of the usage scenario and the object priority list of the sub-scenario locally on the electronic device.
[0186] Please also read Fig.14, the resource scheduling system 130 is similar to the operating system scheduling process in the resource scheduling system 700, but there are differences in the object priority list generation process in the resource scheduling system 130 and the resource scheduling system 700: the electronic device 1301 collects the scene information and service usage information of the local device, and the electronic device 1301 locally mines the object priority list under different usage scenarios and sub-scenarios of the local user. That is, the machine learning of the first determination module 101 is performed locally on the electronic device 1301, so the first determination module 103 does not need to integrate the machine learning platform, and the training data and object priority list are relatively simplified compared to the resource scheduling system 700.
[0187] The electronic device 1301 has a built-in priority mining model, which performs mining based on historical data of the electronic device 1301 , while the priority mining model in the resource scheduling system 700 can perform mining based on historical data provided by multiple different devices of multiple different users.
[0188] Specifically, during the object priority list generation process, data is transmitted within the electronic device 1301, so the data format in IF1-IF4 does not need to carry the "user ID" field.
[0189] In some embodiments, considering that the first determination module 103 needs to consume device computing resources, the object priority list generation process can reduce the regular execution frequency or reduce event sensitivity to reduce power consumption.
[0190] In the embodiment of the present application, the scheduling system 100 can perceive the user's usage scenario and sub-scenario in real time, and obtain an object priority list that is more in line with the user's usage habits in the scenario through data mining, which ensures smooth user use while also improving the efficiency of the use of mobile device hardware resources, which is especially important for mobile devices with limited resources. Furthermore, the generation of the object priority list is all on the electronic device side, which is more privacy-friendly.
[0191] The following is an exemplary introduction to another application scenario of the scheduling system 100.
[0192] like Fig.15 As shown, the resource scheduling system 150 includes an electronic device 1501. The difference between the resource scheduling system 150 and the resource scheduling system 130 is that the scene matching is implemented in the electronic device 1501. That is, the electronic device 1501 is based on the electronic device 1301 and also integrates the module of the first server 702. In other words, all modules of the scheduling system 100 are deployed in the electronic device 1501.
[0193] Specifically, during the scene matching process, data is transmitted within the electronic device 1301, so the data formats in IF1-IF4 do not need to carry the "user ID" field.
[0194] The scene determination module 102 may pre-store the mapping between the usage scene and the scene information, and the user may subsequently expand the usage scene. For example, the user may add, delete or edit the mapping between the usage scene and the scene information based on the configuration interface provided by the scene determination module 102. The scene determination module 102 may also start the switch of its automatic configuration switch unit 142 in response to the user's start-up operation.
[0195] In the resource scheduling system 150, the electronic device 1501 obtains a scheduling strategy to perform resource scheduling according to the scheduling strategy, which is to perform resource scheduling according to object priority. The object priority in the scheduling strategy is based on the scene information of the electronic device 1501 (such as Fig.15 time, address, WiFi, weather) and service usage information (such as Fig.15 As shown, the service situation of using electronic device 1501 is obtained.
[0196] In the resource scheduling system 130 and the resource scheduling system 150, the electronic device mines out an object priority list in a corresponding usage scenario based on its own information.
[0197] Fig.16 A schematic diagram of a resource scheduling method flow chart provided in an embodiment of the present application.
[0198] Step S161: The scheduling system stores the usage scenario and its corresponding object priority list, and / or stores the sub-scenario of the usage scenario and the object priority list corresponding to the sub-scenario.
[0199] In an embodiment of the present application, the scheduling system may define usage scenarios based on configuration information of operators and / or users, or define usage scenarios based on received high-frequency co-occurring scenario information, and the present application does not make specific limitations on this.
[0200] In the embodiment of the present application, the scheduling system obtains the service usage information, and determines the object priority list of the usage scenario according to the service usage information, wherein the scenario information associated with the service usage information matches the usage scenario. In other words, the scenario information and the service usage information are associated with each other, and when the scenario information matches a certain usage scenario, the object priority list of the usage scenario is mined by the scheduling system from the service usage information associated with the scenario information.
[0201] As shown in the above example, in the resource scheduling system 700, the scheduling system mines out an object priority list of usage scenarios based on the service usage information of multiple different electronic devices or multiple different users, while in the resource scheduling system 130 and the resource scheduling system 150, the scheduling system mines out an object priority list of usage scenarios based on the service usage information of a single electronic device.
[0202] In an embodiment of the present application, the scheduling system trains a priority mining model to obtain a trained priority mining model, and mines out an object priority list corresponding to the usage scenario based on the trained priority mining model, and then determines the sub-scenario of the usage scenario and the object priority list corresponding to the sub-scenario according to the object priority list corresponding to the usage scenario. The specific content can be referred to above and will not be repeated here.
[0203] In an embodiment of the present application, a server (such as the second server 703) can train a priority mining model, that is, the server can perform training based on scene information and service usage information provided by devices from different users. An electronic device (such as the electronic device 1301 or the electronic device 1501) can also train a priority mining model, that is, the electronic device performs training based on scene information and service usage information collected by itself. The trained priority mining model is used to mine the object priority list corresponding to each usage scenario.
[0204] The specific content of the training priority mining model can be referred to above and will not be repeated here.
[0205] In an embodiment of the present application, after the scheduling system obtains the object priority list of the usage scenario, it determines the sub-scenario of the usage scenario based on the object priority list. Specifically, the scheduling system obtains the service of the usage scenario according to the service indicated by the object in the object priority list, and determines the sub-scenario included in the usage scenario according to the service of the usage scenario. When the service of the usage scenario includes two or more, the scheduling system determines the order between the two or more services according to the object priority from high to low, and determines the sub-scenario included in the usage scenario according to the service and order of the usage scenario.
[0206] For example, taking the above-mentioned company lunch break scenario as an example, the corresponding process priority list is: Desktop> Huawei Video> SMS> Negative One Screen, then the objects in the process priority list are: Desktop, Huawei Video, SMS and Negative One Screen, and accordingly, the services corresponding to the objects (i.e., the services of the company lunch break scenario) are: Desktop, Huawei Video application, SMS application and Negative One Screen. It can be determined that the order of these services is Desktop, Huawei Video, SMS and Negative One Screen, respectively. It can be determined that the sub-scenario of this usage scenario includes the following three: [Desktop], [Desktop, Huawei Video] and [Desktop, Huawei Video, SMS]. The relevant content of each sub-scenario can be referred to above and will not be repeated here.
[0207] For another example, taking the above Huawei sports health usage scenario as an example, the corresponding thread priority list is: sleep module thread > heart health module thread > outdoor running module thread, then the objects in the thread priority list are: sleep module, heart health module and outdoor running module, and accordingly, the services corresponding to the objects (i.e., the services of Huawei sports health usage scenario) are: sleep module, heart health module and outdoor running module. It can be determined that the order of these services is: sleep module, heart health module and outdoor running module, and it can be determined that the sub-scenario of this usage scenario includes the following two: [sleep module], [sleep module, heart health module]. The relevant content of each sub-scenario can be referred to above, and will not be repeated here.
[0208] In the embodiment of the present application, the scheduling system determines the sub-scenario of each usage scenario, and determines the object priority list corresponding to the sub-scenario according to the object priority list of the usage scenario. When the usage scenario includes multiple sub-scenarios, the object priority lists corresponding to the multiple sub-scenarios are different. The specific content can be referred to above and will not be repeated here.
[0209] Step S162: the electronic device collects predefined information.
[0210] The predefined information is information of the electronic device that needs to be obtained in advance, and the predefined information includes scene information and / or service usage information.
[0211] In an embodiment of the present application, the electronic device may collect its scene information and / or service usage information by default. In some embodiments, a collection switch may be configured, and when the electronic device detects that the collection switch is turned on, the scene information and / or service usage information is collected.
[0212] The contents of the scene information and service usage information can be found above and will not be repeated here.
[0213] The scenario information and service usage information collected by the electronic device in step S162 can be used to train a priority mining model.
[0214] Step S163: The scheduling system determines the usage scenario of the electronic device according to the predefined information of the electronic device.
[0215] In the embodiment of the present application, the object scheduling module of the electronic device can schedule the scene determination module to determine the usage scene it is in. For example, the usage scene is determined based on the scene information, or the service information is determined based on the service usage information, and then the usage scene is determined according to the service information. The specific content can be referred to above and will not be repeated here.
[0216] Step S164: The electronic device determines a sub-scenario of the usage scenario according to the user's switching service operation on the electronic device.
[0217] In an embodiment of the present application, the electronic device determines the target service used by the user in the usage scenario (i.e., the usage scenario determined in step S163) based on the user's switching service operation. The target service includes the services that the user has used and the services that are being used in the usage scenario. Then, the sub-scenario of the usage scenario is determined based on the target service and the services of the usage scenario. The services of the usage scenario are the services indicated by the objects in the object priority list of the usage scenario.
[0218] Among them, the service usage information is related to the user's switching service operation, and the electronic device can determine the user's switching service operation on the electronic device in the usage scenario according to the service usage information obtained in step S163, and then determine the target service used by the user in the usage scenario. The switching service operation input by the user indicates the service used by the user, and the electronic device provides the corresponding service in response to the user's switching service operation. The electronic device records the service name and usage time of the target service used by the user to obtain the service usage information. The target service used by the user is the service on the electronic device.
[0219] In an embodiment of the present application, when the number of target services includes two or more, the order in which the two or more target services are used in time is obtained (that is, the order in which the two or more target services are used in the usage scenario is obtained); then determining the sub-scenario of the usage scenario based on the services of the usage scenario and the target services includes: determining the sub-scenario of the usage scenario based on the services, target services and order of the usage scenario.
[0220] In an embodiment of the present application, after determining a sub-scenario of a usage scenario, an object priority list of the sub-scenario pair is determined according to the object priority list of the usage scenario, and the object priority list of the sub-scenario is part of the object priority list of the usage scenario.
[0221] For example, at the company, the time is 13 o'clock, and the user enters the desktop of the mobile phone. The scene information obtained by the mobile phone includes: time 12-14 o'clock, geographic location company, the mobile phone detects the user's service switching operation (entering the desktop), and obtains the corresponding service usage information: entering the desktop at 13 o'clock. According to the scene information obtained by the mobile phone, the matching information of the company's lunch break usage scenario is matched (12 o'clock-14 o'clock, company), and it is determined that the mobile phone is in the company's lunch break usage scenario, and the object priority list corresponding to the company's lunch break usage scenario is obtained: [Desktop, Huawei Video, SMS, Negative One Screen], and based on the user's switching service operation, it is determined that the target service used by the user is the desktop, and it is determined that the mobile phone is in the [Desktop] sub-scene of the company's lunch break scene, and the object priority list corresponding to the sub-scene is obtained: [Huawei Video, SMS, Negative One Screen]. The mobile phone detects the user's service switching operation at 13:01 (exiting the desktop and entering Huawei Video), and obtains the corresponding service usage information: exiting the desktop and entering Huawei Video at 13:01. It is determined that the target services used by the user are desktop and Huawei Video, and the order of use of these two services in the company's lunch break usage scenario is: desktop first, then Huawei Video. It is determined that the mobile phone is in the [desktop, Huawei Video] sub-scene of the company's lunch break scene, and the object priority list corresponding to the sub-scene is: [SMS, negative one screen].
[0222] In some embodiments, step S164 may also be that the scheduling system determines a sub-scenario of the usage scenario according to the user's switching service operation on the electronic device, and the content of the sub-scenario of the usage scenario determined by the scheduling system is similar to the above.
[0223] Step S165: The electronic device obtains the object priority list of the sub-scene to schedule resources of the electronic device based on the object priority list of the sub-scene.
[0224] In an embodiment of the present application, the operating system of the electronic device can increase the probability of high-priority objects obtaining resources based on the object priority list, such as allocating resources to high-priority objects with priority, etc. If the operating system currently has an object priority list, the existing object priority list can be adjusted according to the object priority list of the usage scenario or sub-scenario obtained.
[0225] Fig.17 A schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application.
[0226] like Fig.17 As shown, the electronic device 170 includes a radio frequency (RF) circuit 171, a sensor module 172, an input device 173, an output device 174, a processor 175, a camera device 176, a wireless fidelity (WiFi) module 177, a memory 178 and a power supply 179.
[0227] The memory 178 is used to store computer programs, including application programs 1781, operating system programs 1782, and other data 1783. The processor 175 is used to read the computer programs in the memory 178 and then execute the methods defined by the computer programs. For example, the processor 175 reads the operating system program 1782 to run the operating system on the electronic device 170 and implement various functions of the operating system, or reads one or more application programs 1781 to run applications on the electronic device 170.
[0228] The operating system program 1782 includes a computer program that can implement the resource scheduling method provided in the embodiment of the present application, so that after the processor 175 reads the operating system program 1782 and runs the operating system, the operating system can have the resource scheduling method provided in the embodiment of the present application or have the function of the scheduling system 700.
[0229] Among them, other data 1783 may include data generated after the operating system program 1782 and / or the application program 1781 are run, and the data includes system data (such as configuration parameters of the operating system) and related data (such as object priority).
[0230] The processor 175 may include one or more processors (or processing units), for example, the processor 175 may include one or more central processing units, graphics processing units (GPUs), application processors (APs), image signal processors (ISPs), modem processors, digital signal processors (DSPs), baseband processors, neural-network processing units (NPUs), and / or video codecs. When the processor 175 includes multiple processors, the multiple processors may be integrated on the same chip or may be independent chips. A processor may include one or more processing cores.
[0231] The processor 175 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 175 is a cache memory. The memory may store instructions or data that the processor 175 has just used or cyclically used. If the processor 175 needs to use the instruction or data again, it may be directly called from the memory, thereby avoiding repeated access, reducing the waiting time of the processor 175, and improving the efficiency of the system.
[0232] The memory 178 may include internal memory and external memory. The internal memory may be a random access memory (RAM), a read-only memory (ROM), and a cache, etc. The external memory may be a hard disk, an optical disk, a universal serial bus (USB) disk, a floppy disk, or a tape drive, etc. Computer programs such as application programs may be stored in the external memory, and the processor may load the computer program from the external memory to the internal memory before executing the processing, and the operating system may be stored in the internal memory. In this way, the internal memory may store computer executable program codes, which may include instructions. The processor 175 executes various functional applications and data processing of the electronic device 170 by running the instructions stored in the internal memory.
[0233] The electronic device 170 may further include an input device 173 for receiving input digital information, character information or contact touch operation / contactless gesture, and generating signal input related to user settings and function control of the electronic device 170.
[0234] Exemplarily, the input device 173 may include a touch panel. A touch panel, also known as a touch screen, can collect user touch operations on or near it (such as operations performed by a user using a finger, stylus, or any other suitable object or accessory on or on the touch panel), and drive corresponding connection devices according to a pre-set program.
[0235] The input device 173 may also include but is not limited to one or more other input devices such as a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, etc. The user's switching service operation may be obtained based on the input device 173 .
[0236] The electronic device 170 may also include an output device 174, which can output information input by the user or provided to the user and various menu interfaces of the electronic device 170, etc. In the embodiment of the present application, it is mainly used to display the application process in the foreground or the desktop of the electronic device 170.
[0237] The output device 174 may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector.
[0238] A power source 179 and a camera device 176 for taking pictures or videos.
[0239] The electronic device 170 may further include a sensor module 172 , which includes one or more sensors, such as an acceleration sensor, a light sensor, a fingerprint sensor, a touch sensor, etc. Corresponding scene information may be obtained based on the sensor module 172 .
[0240] The wireless radio frequency circuit 171 is used for network communication with wireless network equipment. The wireless fidelity module 177 is used for WiFi communication with other equipment.
[0241] It is understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the electronic device 170. In other embodiments of the present application, the electronic device 170 may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.
[0242] The resource scheduling method provided in the embodiment of the present application can be implemented in Fig.18 The operating system shown in the figure can be Android, Hongmeng, Linux, Windows, UNIX system, etc.
[0243] For ease of understanding, the following Fig.18 and Fig. 9 , taking the Android operating system as an example, the implementation location of the method provided in the embodiment of the present application is introduced.
[0244] Fig.18 A schematic diagram of a soft structure of an electronic device provided in an embodiment of the present application.
[0245] like Fig.18 As shown, the software system of the electronic device can adopt a layered architecture. The layered architecture is to divide the software into several layers, each layer contains a large number of sub-modules or sub-systems, and the layers communicate with each other through software interfaces.
[0246] In some embodiments, the software system can be divided into four layers, from top to bottom, namely, the application (APP) layer, the application framework (framework) layer, the system runtime library layer (including C / C++ native libraries (native C / C++ libraries) and Android runtime (Android runtime)), and the kernel layer (kernel).
[0247] The application layer can include a series of application packages. Fig.18As shown, the application package may include camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message and other applications. The application is mainly in the user interface (user interface) aspect, and is usually written by calling the interface of the application framework layer using the JAVA language.
[0248] The application program in the electronic device can be in a running state or in a non-running state. When the application program is in a running state, the application program can be divided into a foreground application program and a background application program according to different running positions.
[0249] The foreground application runs in the foreground and is displayed on the display interface of the electronic device; the background application runs in the background and is not displayed on the display interface of the electronic device.
[0250] The application framework layer is a series of services and systems hidden behind each application, which is used to provide application programming interface (API) and programming framework for the applications in the application layer. The application framework layer includes some predefined functions. Fig.18 As shown, the application framework layer may include a window manager, a content provider, a view system, a telephony manager, a resource manager, a notification manager, and an activity manager, etc.
[0251] The window manager is used to manage window programs. The window manager can obtain the display screen size, determine whether there is a status bar, lock the screen, capture the screen, etc.
[0252] Content providers are used to store and retrieve data and make it accessible to applications. This data can include video, images, audio, calls made and received, browsing history and bookmarks, phone books, etc. Content providers allow applications to publish and share data.
[0253] The view system is used to build applications, and may include, for example, lists, grids, text boxes, buttons, and an embeddable world wide web browser. The display interface of an electronic device may be composed of one or more views. For example, the display interface of a text message notification icon may include a view for displaying text and a view for displaying images.
[0254] The phone manager is used to provide communication functions for the electronic device 170, such as management of call status (including connecting, hanging up, etc.).
[0255] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.
[0256] The notification manager enables applications to display notification information in the status bar. It can be used to convey notification-type messages and can disappear automatically after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also be a notification that appears in the system top status bar in the form of a chart or scroll bar text, such as notifications of applications running in the background, or a notification that appears on the screen in the form of a dialog window. For example, a text message is displayed in the status bar, a prompt sound is emitted, an electronic device vibrates, an indicator light flashes, etc.
[0257] The activity manager is used to manage all aspects of the application life cycle and activity stack, and provides common navigation back functions. The activity manager can be used to obtain information about the activities running in the system, such as processes, applications, services, and tasks. For example, the activity manager can be used to obtain global memory usage information, count memory information under processes, obtain running process information (such as obtaining the activities running in the front end and determining whether the application is running in the front end), etc.
[0258] The system runtime library layer is a collection of libraries located below the application framework layer. The system runtime library layer can include two parts, namely C / C++ native library and Android runtime.
[0259] Android runtime is the Android operating environment, including core libraries and virtual machines (such as Dalvik virtual machines). Android runtime is responsible for the scheduling and management of the Android system. The core library consists of two parts: one is the function that the Java language needs to call, and the other is the Android core library. The application layer and the application framework layer run in the virtual machine. The virtual machine executes the Java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform object life cycle management, stack management, process management, thread management, security and exception management, and garbage collection.
[0260] The C / C++ native library (also called the system library) supports the application framework and is an important link between the application framework layer and the kernel layer. It can include multiple functional modules, such as: surface manager (surfac emanager), media framework (media framework), standard C library (standard C library, libc), 2D engine, 3D engine, etc.
[0261] The surface manager is used to manage the display subsystem and provide the fusion of 2D and 3D layers for multiple applications.
[0262] The media framework supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc. The media framework can support a variety of audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.
[0263] The standard C library, also known as the system C library or C function library, is used to provide macros, type definitions, string operation functions, mathematical calculation functions, and input and output functions used in the C language.
[0264] A 2D engine is a graphics engine for two-dimensional drawing, including but not limited to vector graphics engines (such as the skia graphics library (SGL)), browser engines (such as webkit), relational database engines (such as SQLite), etc.
[0265] A 3D engine is a three-dimensional graphics engine used to implement three-dimensional graphics drawing, image rendering, synthesis and layer processing, etc. The 3D engine includes but is not limited to an open graphics library for embedded systems (OpenGL ES).
[0266] The kernel layer is the layer between hardware and software, which is used to provide essential functions of the operating system such as file management, memory management, process management, thread management, network protocol stack, device management (such as camera, keyboard, display, etc.). The kernel layer includes at least display driver, camera driver, audio driver, sensor driver, Bluetooth driver, etc.
[0267] The application framework layer, the system runtime layer and the kernel layer may constitute the operating system layer of the electronic device. Fig.18 The operating system layers shown can be considered as Fig.17 A specific implementation of the operating system program 1782 in Fig.18 The application layer in Fig.17 A specific implementation of the application 1781 in the embodiment of the present application. The resource scheduling method provided in the embodiment of the present application can be Fig.18 It is implemented in the operating system layer.
[0268] Fig.17 and Fig.18 The hardware architecture and software system involved in the embodiments of the present application are described separately. Fig.19 Further explanation is given from the perspective of software and hardware interaction, and a brief introduction is given to the object scheduling module involved in the method provided in the embodiment of the present application.
[0269] Virtual memory can be divided into kernel space and user space by the operating system. Kernel space is where kernel code runs, and user space is where user program code runs. When a process is executed in kernel code, it can be said that the process is in kernel running state (kernel state for short). When the process is executing the user's own code, it can be said that the process is in user running state (user state for short). Specifically, kernel state and user state are two operating levels of the operating system.
[0270] like Fig.19 As shown, the kernel space 20 is a kernel 21 (also called an operating system kernel, equivalent to Fig.18 The kernel layer shown in Figure 1 is the cornerstone, and the user space 10 is composed of Fig.18 The system runtime layer and the application framework layer shown are composed of an application 11, a library function 12 and a shell 13, and the kernel space 20 and the user space 10 of the system can be connected through a system call (syscall) 22. The user space 10 can be written in C++ and Java code, and the Java layer and the native layer (i.e., C / C++ layer) of the user space are connected through the Java native interface (java nativeinterface, JNI) technology, thereby connecting the entire system.
[0271] The kernel 21 can control the hardware resources of the computer and provide a standard interface for the hardware system 30 (eg, including a processor, memory, disk, printer, etc.) through a hardware abstraction layer (HAL) 23 .
[0272] The hardware abstraction layer 23 is a hardware interface layer abstracted from a specific hardware platform, responsible for implementing the functions and controls of the specific hardware platform, while providing a unified API interface for other software modules. Specifically, the hardware abstraction layer 23 can abstract the commonality of hardware operation and control, hide the hardware interface details of a specific platform, and provide a unified virtual hardware platform and control interface to the upper-level software to isolate other software modules from the underlying hardware, thereby facilitating the transplantation of the system on a new hardware platform.
[0273] The kernel 21 is a first-layer software expansion based on the hardware system 30, which is used to provide the most basic functions of the operating system and is the basis for the operation of the operating system. The kernel 21 is generally responsible for process scheduling and management, thread scheduling and management, file system management, memory management, device driver management, and network system management. Therefore, the kernel 21 can be divided into multiple modules according to the functions implemented, among which the module responsible for object scheduling is the object scheduling module.
[0274] The embodiment of the present application also provides a computer program product. When the computer program product is run on a computer, the computer is enabled to execute the above-mentioned related steps to implement the resource scheduling method and / or function in the above-mentioned method embodiments.
[0275] An embodiment of the present application also provides a computer storage medium, including computer instructions. When the computer instructions are executed on an electronic device, the electronic device executes the resource scheduling method and / or function of the above-mentioned embodiment.
[0276] Among them, the electronic device, computer storage medium, computer program product or chip system provided in the embodiments of the present application are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods provided above, and will not be repeated here.
[0277] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.
[0278] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0279] The unit described as a separate component may or may not be physically separated, and the component shown as a unit may be one physical unit or multiple physical units, that is, it may be located in one place or distributed in multiple different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiment.
[0280] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.
[0281] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to perform all or part of the steps of each embodiment method of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program code.
[0282] The above are only specific implementation methods of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application should be included in the protection scope of the present application.
Claims
1. A resource scheduling method, It is characterized in that The method comprises: Obtaining predefined information of the electronic device; Determining the usage scenario of the electronic device according to the predefined information; Determining a sub-scenario of the usage scenario according to a user's switching service operation on the electronic device; An object priority list of the sub-scenario is acquired to schedule resources of the electronic device based on the object priority list of the sub-scenario, wherein the object priority list of the sub-scenario is related to the object priority list of the usage scenario.
2. The resource scheduling method according to claim 1, It is characterized in that The sub-scenario of determining the usage scenario according to the user's switching service operation on the electronic device includes: Determining a target service used by a user according to a service switching operation of the electronic device by the user; A sub-scenario of the usage scenario is determined according to the service of the usage scenario and the target service, wherein the service of the usage scenario is a service indicated by an object in an object priority list of the usage scenario.
3. The resource scheduling method according to claim 2, It is characterized in that When the number of the target services includes two or more, obtaining a time sequence of use of the two or more target services; Then the determining of the sub-scenario of the usage scenario according to the service of the usage scenario and the target service includes: A sub-scenario of the usage scenario is determined according to the service of the usage scenario, the target service and the sequence.
4. The resource scheduling method according to any one of claims 1 to 3, It is characterized in that The method further comprises: Obtain information about service usage; An object priority list of usage scenarios is determined based on the service usage information, wherein scenario information associated with the service usage information matches the usage scenario.
5. The resource scheduling method according to claim 4, It is characterized in that The method further comprises: For each usage scenario, a sub-scenario of the usage scenario is determined, and an object priority list corresponding to the sub-scenario is determined according to the object priority list of the usage scenario.
6. The resource scheduling method according to claim 4 or 5, It is characterized in that The predefined information includes scenario information and / or service usage information; The scenario information includes one or more of the following information: time information, geographic location information, WiFi connection status, weather information, Bluetooth headset connection status, vehicle Bluetooth connection status, flight information, power level of electronic devices, consumer order information, and user exercise status; The service usage information includes one or more of the following information: service name and time of using the service.
7. The resource scheduling method according to any one of claims 1 to 6, It is characterized in that The object priority list of the sub-scenario is part of the object priority list of the usage scenario.
8. A resource scheduling system, It is characterized in that include: Electronic devices used to obtain scene information and service usage information; A first server is used to configure a usage scenario and matching information matching the usage scenario, wherein the matching information includes the scenario information; A second server is used to determine an object priority list of the usage scenario according to the service usage information; The second server is also used to determine a sub-scenario of the usage scenario based on the service of the usage scenario, and determine a priority list corresponding to the sub-scenario based on the object priority list of the usage scenario, wherein the service of the usage scenario is the service indicated by the object in the object priority list of the usage scenario.
9. The resource scheduling system as claimed in claim 8, It is characterized in that The first server is further used to obtain scenario information of the electronic device, and determine the usage scenario of the electronic device according to the scenario information.
10. The resource scheduling system according to claim 8 or 9, It is characterized in that The electronic device is further used to obtain a user's switching service operation on the electronic device, wherein the switching service operation is used to determine a sub-scenario of the usage scenario after determining the usage scenario of the electronic device.
11. An electronic device, It is characterized in that include: Processor and memory; The memory is used to store a computer program, wherein the computer program includes program instructions; The processor is used to call the computer program to execute the resource scheduling method as described in any one of claims 1 to 7.
12. A computer storage medium, It is characterized in that It comprises computer instructions, and when the computer instructions are executed on an electronic device, the electronic device executes the resource scheduling method as claimed in any one of claims 1 to 7.
13. A computer program product, It is characterized in that When the computer program product is executed on a computer, the computer is enabled to execute the resource scheduling method according to any one of claims 1 to 7.
Citation Information
Cited By
Mode switching method and device, electronic equipment and computer readable storage medium
CN121541957A
Method and apparatus used in node for wireless communication and artificial intelligence
WO2026137859A1
