Business Allocation Method, Device, Product, Storage Medium and Equipment

Abstract

The present application discloses a service allocation method, apparatus, product, storage medium and device. The method includes: obtaining device attribute information of an entity heterogeneous device in the physical attribute dimension from the entity heterogeneous device; obtaining service requirement information of the entity heterogeneous device in the service requirement dimension according to historical service requirement conditions in historical requirement conditions of historical executed services; obtaining operation status information of the entity heterogeneous device in the operation status dimension according to the operation status of the entity heterogeneous device; creating a virtual heterogeneous device corresponding to the entity heterogeneous device, and associating the device attribute information, service requirement information and operation status information with the virtual heterogeneous device; determining a target entity heterogeneous device that matches the current requirement conditions of the service to be executed according to the device attribute information, service requirement information and operation status information associated with the virtual heterogeneous device, and allocating the service to be executed to the target entity heterogeneous device for execution. The present application provides better flexibility in service allocation.

Description

Technical Field

[0001] This application relates to the field of cloud computing technology, and particularly relates to a service allocation method, device, product, storage medium, and equipment. Background Art

[0002] With the development of network technology, the demand for rapid processing of services is increasing. In many cases, a large amount of computing resources are required to centrally process services. For example, when training an artificial intelligence model, a large number of heterogeneous devices are required to complete the model training process. To better process services, services can be allocated to corresponding heterogeneous devices for execution. However, in related technologies, the flexibility of service allocation is poor. Summary of the Invention

[0003] Embodiments of this application provide a service allocation method, device, product, storage medium, and equipment, which can make the service allocation more flexible.

[0004] Embodiments of this application provide a service allocation method, including:

[0005] Obtaining device attribute information of the entity heterogeneous device in the physical attribute dimension from the entity heterogeneous device;

[0006] Obtaining service requirement information of the entity heterogeneous device in the service requirement dimension according to the historical service requirement conditions in the historical requirement conditions of the executed services;

[0007] Obtaining operation status information of the entity heterogeneous device in the operation status dimension according to the operation status of the entity heterogeneous device;

[0008] Creating a virtual heterogeneous device corresponding to the entity heterogeneous device, and associating the device attribute information, the service requirement information, and the operation status information with the virtual heterogeneous device;

[0009] Determining a target entity heterogeneous device that matches the current requirement conditions of the service to be executed according to the device attribute information, service requirement information, and operation status information associated with the virtual heterogeneous device, and allocating the service to be executed to the target entity heterogeneous device for execution, where the current requirement conditions include at least one of current physical attribute requirement conditions, current service requirement conditions, and current operation status requirement conditions.

[0010] Correspondingly, embodiments of this application also provide a service allocation device, including:

[0011] A device creation module, configured to create a virtual heterogeneous device corresponding to the entity heterogeneous device;

[0012] A first information acquisition module, configured to acquire device attribute information of the entity heterogeneous device in the physical attribute dimension from the entity heterogeneous device;

[0013] A second information acquisition module, configured to acquire business requirement information of the entity heterogeneous device in the business requirement dimension according to historical business requirement conditions in historical requirement conditions of historical executed services;

[0014] A third information acquisition module, configured to acquire operation status information of the entity heterogeneous device in the operation status dimension according to the operation status of the entity heterogeneous device;

[0015] An information association module, configured to create a virtual heterogeneous device corresponding to the entity heterogeneous device, and associate the device attribute information, the business requirement information, and the operation status information with the virtual heterogeneous device;

[0016] A service allocation module, configured to determine a target entity heterogeneous device that matches the current requirement conditions of the service to be executed according to the device attribute information, business requirement information, and operation status information associated with the virtual heterogeneous device, and allocate the service to be executed to the target entity heterogeneous device for execution, where the current requirement conditions include at least one of current physical attribute requirement conditions, current business requirement conditions, and current operation status requirement conditions.

[0017] Optionally, the service allocation module is specifically configured to execute:

[0018] Determine candidate entity heterogeneous devices that match the current requirement conditions of the service to be executed according to the device attribute information, business requirement information, and operation status information associated with the virtual heterogeneous device;

[0019] Acquire historical stability information of the candidate entity heterogeneous devices, where the historical stability information is used to characterize the stability of the candidate entity heterogeneous devices within a historical period;

[0020] Screen target entity heterogeneous devices from the candidate entity heterogeneous devices according to the historical stability information.

[0021] Optionally, the service allocation module is specifically configured to execute:

[0022] Acquire the device requirement quantity of the service to be executed;

[0023] Screen target entity heterogeneous devices with the device requirement quantity from the candidate entity heterogeneous devices according to the historical stability information.

[0024] Optionally, the entity heterogeneous devices include different categories of entity heterogeneous devices, and the third information acquisition module is specifically configured to execute:

[0025] If the operating state of the entity heterogeneous device is a category conversion state, obtain the operating state information for describing the target category after the category conversion of the entity heterogeneous device.

[0026] Optionally, the entity heterogeneous devices of different categories include the entity heterogeneous devices of the first category and the entity heterogeneous devices of the second category. The third information acquisition module is specifically configured to execute:

[0027] Obtain the total utilization rate of the entity heterogeneous devices of the first category to obtain the first utilization rate;

[0028] If the first utilization rate is less than the first utilization rate threshold, determine the operating state of at least one idle entity heterogeneous device in the entity heterogeneous devices of the first category as the category conversion state, and determine the second category as the target category.

[0029] Optionally, the third information acquisition module is specifically configured to execute:

[0030] Obtain the total utilization rate of the entity heterogeneous devices of the second category to obtain the second utilization rate;

[0031] The step of, if the first utilization rate is less than the first utilization rate threshold, determining the operating state of at least one idle entity heterogeneous device in the entity heterogeneous devices of the first category as the category conversion state includes:

[0032] If the first utilization rate is less than the first utilization rate threshold and the second utilization rate is greater than the second utilization rate threshold, determine the operating state of at least one idle entity heterogeneous device in the entity heterogeneous devices of the first category as the category conversion state.

[0033] Optionally, the third information acquisition module is specifically configured to execute:

[0034] If the operating state of the entity heterogeneous device is an abnormal operating state, obtain the operating state information for describing the abnormality of the entity heterogeneous device.

[0035] Optionally, the second information acquisition module is specifically configured to execute:

[0036] If the historical service requirement condition includes a device health requirement condition, obtain the service requirement information for describing the health of the entity heterogeneous device, where the device health requirement condition is used to specify the minimum health that the entity heterogeneous device for executing the historical executed service needs to reach.

[0037] Optionally, the second information acquisition module is specifically configured to execute:

[0038] If the historical service requirement conditions include anti-affinity service requirement conditions, when the execution entity heterogeneous device assigned to execute the historical execution service executes the historical execution service, the service requirement information is generated. The anti-affinity service requirement conditions are used to specify anti-affinity services that cannot be executed by the same entity heterogeneous device simultaneously with the historical execution service, and the service requirement information is used to describe that the execution entity heterogeneous device cannot execute the anti-affinity services.

[0039] Optionally, the information association module is specifically configured to execute:

[0040] Obtain the service requirement update information of the entity heterogeneous device in the service requirement dimension according to the current service requirement conditions in the current requirement conditions;

[0041] Update the service requirement information associated with the virtual heterogeneous device according to the service requirement update information.

[0042] Correspondingly, an embodiment of the present application further provides a computer program product, including a computer program / instructions. When the computer program / instructions are executed by a processor, the steps of the service allocation method shown in the embodiments of the present application are implemented.

[0043] Correspondingly, an embodiment of the present application further provides a computer-readable storage medium, which is used to store a computer program. The computer program is loaded by a processor to execute any service allocation method provided by the embodiments of the present application.

[0044] Correspondingly, an embodiment of the present application further provides a computer device, including a memory and a processor; the memory stores a computer program, and the processor is used to run the computer program in the memory to execute any service allocation method provided by the embodiments of the present application.

[0045] In the embodiments of the present application, device attribute information of the entity heterogeneous device in the physical attribute dimension is obtained from the entity heterogeneous device; business requirement information of the entity heterogeneous device in the business requirement dimension is obtained according to the historical business requirement conditions in the historical requirement conditions of the historical executed business; operation status information of the entity heterogeneous device in the operation status dimension is obtained according to the operation status of the entity heterogeneous device; a virtual heterogeneous device corresponding to the entity heterogeneous device is created, and the device attribute information, the business requirement information, and the operation status information are associated with the virtual heterogeneous device; according to the device attribute information, business requirement information, and operation status information associated with the virtual heterogeneous device, a target entity heterogeneous device matching the current requirement conditions of the to-be-executed business is determined, and the to-be-executed business is assigned to the target entity heterogeneous device for execution. The current requirement conditions include at least one of the current physical attribute requirement conditions, current business requirement conditions, and current operation status requirement conditions. Thus, when performing business assignment, the entity heterogeneous device is assigned for the to-be-executed business according to the device attribute information, business requirement information, and operation status information associated with the virtual heterogeneous device corresponding to the entity heterogeneous device, without affecting the entity heterogeneous device that is currently executing the business, so there is no risk that the business being executed by the entity heterogeneous device will be interrupted. Therefore, there is no need to wait for the business to be completed before performing business assignment, and the flexibility of business assignment is relatively good. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] The following will clearly show the technical solutions and their beneficial effects of the present application by describing the specific embodiments of the present application in detail with reference to the accompanying drawings.

[0047] Figure 1a It is a schematic diagram of the business assignment system provided by the embodiments of the present application.

[0048] Figure 1b It is the first flowchart of the business assignment method provided by the embodiments of the present application.

[0049] Figure 2a It is the second flowchart of the business assignment method provided by the embodiments of the present application.

[0050] Figure 2b It is a schematic diagram of the scenario of the business assignment method provided by the embodiments of the present application.

[0051] Figure 2c It is a schematic diagram of the interaction between the business assignment program and the resource portrait center provided by the embodiments of the present application.

[0052] Figure 2d It is a schematic diagram of the resource portrait center provided by the embodiments of the present application.

[0053] Figure 3It is a schematic structural diagram of a service allocation device provided by an embodiment of the present application.

[0054] Figure 4 It is a schematic structural diagram of a computer device provided by an embodiment of the present application. Detailed implementation manners

[0055] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative efforts belong to the scope of protection of the present application.

[0056] Each embodiment provided by the present application can be implemented based on cloud technology. Among them, cloud technology refers to a hosting technology that unifies a series of resources such as hardware, software, and networks within a wide area network or a local area network to achieve data computing, storage, processing, and sharing.

[0057] Cloud technology is the general term for network technology, information technology, integration technology, management platform technology, application technology, etc. applied based on the cloud computing business model. It can form a resource pool, be used on demand, and is flexible and convenient. Cloud computing technology will become an important support. The background services of the technical network system require a large amount of computing and storage resources, such as video websites, picture websites, and more portal websites. With the high development and application of the Internet industry, in the future, each item may have its own identification mark and needs to be transmitted to the background system for logical processing. Data at different levels will be processed separately, and various industry data requires a powerful system background support, which can only be achieved through cloud computing.

[0058] Cloud Computing is a computing model that distributes computing tasks on a resource pool composed of a large number of computing devices, enabling various application systems to obtain computing power, storage space, and information services according to needs. The network that provides resources is called the "cloud". The resources in the "cloud" seem to be infinitely expandable to users, and can be obtained at any time, used on demand, expanded at any time, and paid according to usage.

[0059] As a basic cloud computing capabilities provider, a cloud computing resource pool will be established [abbreviated as the cloud platform, generally referred to as the IaaS (Infrastructure as a Service) platform], and various types of virtual resources will be deployed in the resource pool for external customers to select and use. The cloud computing resource pool mainly includes: computing devices (virtual machines, including operating systems), storage devices, and network devices. In one embodiment, resources can be partitioned from the cloud computing resource pool, and containers can be produced based on the partitioned resources, and corresponding services can be executed in the containers through the partitioned resources.

[0060] According to the logical function division, the PaaS (Platform as a Service) layer can be deployed on the IaaS layer, and the SaaS (Software as a Service) layer can be deployed on top of the PaaS layer. Or the SaaS can be directly deployed on the IaaS. PaaS is a platform for software operation, such as databases, web containers, etc. SaaS is various business software, such as web portals, SMS mass senders, etc. Generally speaking, SaaS and PaaS are the upper layers relative to IaaS.

[0061] Each embodiment provided in this application can also be applied to the implementation of artificial intelligence technology. Among them, artificial intelligence (AI) is to use a digital computer or a machine controlled by a digital computer to simulate, extend, and expand human intelligence, perceive the environment, acquire knowledge, and use knowledge to obtain the best results of theory, methods, technologies, and application systems. In other words, artificial intelligence is a comprehensive technology in computer science. It attempts to understand the essence of intelligence and produce a new intelligent machine that can react in a way similar to human intelligence. Artificial intelligence is also to study the design principles and implementation methods of various intelligent machines to enable the machines to have the functions of perception, reasoning, and decision-making. Artificial intelligence technology is an interdisciplinary subject, involving a wide range of fields, including both hardware-level technologies and software-level technologies. Artificial intelligence basic technologies generally include technologies such as sensors, dedicated artificial intelligence chips, cloud computing, distributed storage, big data processing technologies, operation / interaction systems, mechatronics, etc. Artificial intelligence software technologies mainly include several major directions such as computer vision technology, speech processing technology, natural language processing technology, and machine learning / deep learning.

[0062] Embodiments of the present application provide a service allocation method and related devices. The related devices may include a service allocation device, a computer device, a computer-readable storage medium, and a computer program product. The service allocation method may be executed on a terminal or on a server. The service allocation device may be specifically integrated in the computer device, and the computer device may be a device such as a terminal or a server.

[0063] Please refer to Figure 1a , Figure 1a which is a schematic diagram of the service allocation system provided by the embodiments of the present application. The service allocation system 10 includes a plurality of entity heterogeneous devices 110, a plurality of virtual heterogeneous devices 120, a service allocation program 130, a database 140, and a plurality of heterogeneous card containers 150.

[0064] Among them, the service allocation system 10 is logically divided into a product layer, an access layer, a virtual scheduling layer, and a physical resource layer. The service allocation method provided by the embodiments of the present application is executed in the virtual scheduling layer.

[0065] A user may submit services that need to be executed by the entity heterogeneous device 110 in the product layer, such as Huayuan model training services, vision model training services, speech model training services, game model training services, medical model training services, and natural language processing (NLP) training services, etc.

[0066] A plurality of virtual heterogeneous devices 120, a service distribution program 130, and a database 140 are located in the virtual scheduling layer. Among them, the service distribution program 130 is a computer program. Each virtual heterogeneous device 120 is created by the service distribution program 130. Each virtual heterogeneous device 120 corresponds to each physical heterogeneous device 110. The service distribution program 130 obtains the device attribute information of the physical heterogeneous device 110 in the physical attribute dimension from the physical heterogeneous device 110. The service distribution program 130 also obtains the service demand information of the physical heterogeneous device 110 in the service demand dimension according to the historical service demand conditions in the historical demand conditions of the executed services. The service distribution program 130 also obtains the operation state information of the physical heterogeneous device 110 in the operation state dimension according to the operation state of the physical heterogeneous device 110. The service distribution program 130 also associates and stores the device attribute information, service demand information, and operation state information with the virtual heterogeneous device 120 in the database 140. When a user submits a service to be executed, such as a voice model training task, the service distribution program 130 determines the target physical heterogeneous device 110 that matches the current demand conditions of the service to be executed according to the device attribute information, service demand information, and operation state information associated with the virtual heterogeneous device 120. Among them, the current demand conditions include at least one of the current physical attribute demand conditions, the current service demand conditions, and the current operation state demand conditions. The service distribution program 130 distributes the service to be executed to the target physical heterogeneous device 110 for execution.

[0067] A plurality of physical heterogeneous devices 110 are located in the physical resource layer. The physical heterogeneous device 110 has the characteristic of high computing power and can also be called heterogeneous artificial intelligence acceleration hardware. The physical heterogeneous device 110 may include, but is not limited to, a Graphics Processing Unit (GPU), a Neural network Processing Unit (NPU), a Tensor Processing Unit (TPU), a Field Programmable Gate Array (FPGA) hardware, etc. It should be noted that the plurality of physical heterogeneous devices 110 may include physical heterogeneous devices 110 of different manufacturers and different types, such as multiple GPUs, NPUs, and TPUs of different manufacturers.

[0068] The heterogeneous card container 150 is located in the access layer. Whenever a user submits a business to be executed, the service allocator 130 will complete the production of the heterogeneous card container 150 based on the target entity heterogeneous device 110 assigned to the business to be executed, and execute the business to be executed in the heterogeneous card container 150 through the target entity heterogeneous device 110. That is to say, different businesses to be executed will be executed in different heterogeneous card containers 150 to achieve isolation between different businesses.

[0069] The following will be described in detail respectively. It should be noted that the description order of the following embodiments does not limit the preferred order of the embodiments.

[0070] It can be understood that in the specific implementation of this application, when it comes to data such as user information, when the above embodiments of this application are applied to specific products or technologies, user permission or consent needs to be obtained, and the collection, use, and processing of relevant data need to comply with relevant laws, regulations, and standards in relevant countries and regions.

[0071] Please refer to Figure 1b , Figure 1b which is the first process schematic diagram of the service allocation method provided by the embodiment of this application. The process may include:

[0072] In 101, device attribute information of the entity heterogeneous device in the physical attribute dimension is obtained from the entity heterogeneous device.

[0073] In 102, according to the historical service demand condition in the historical demand condition of the historical executed service, the service demand information of the entity heterogeneous device in the service demand dimension is obtained.

[0074] In 103, according to the operation status of the entity heterogeneous device, the operation status information of the entity heterogeneous device in the operation status dimension is obtained.

[0075] In 104, a virtual heterogeneous device corresponding to the entity heterogeneous device is created, and the device attribute information, service demand information, and operation status information are associated with the virtual heterogeneous device.

[0076] Among them, the virtual heterogeneous device corresponds to the entity heterogeneous device and is a virtual object used to uniquely represent a certain entity heterogeneous device, and can be regarded as the identification object of a certain entity heterogeneous device. When the environment of multiple entity heterogeneous devices is deployed and put on the shelf, virtual heterogeneous devices corresponding to each entity heterogeneous device can be created.

[0077] It can be understood that since the physical heterogeneous devices may be removed due to maintenance, replacement, etc., and may also be added due to actual requirements, in order to better screen and match the physical heterogeneous devices for services, it is possible to synchronously detect whether the physical heterogeneous devices are removed or whether new physical heterogeneous devices are added by means of timed polling. If it is detected that a certain physical heterogeneous device is removed, the virtual heterogeneous device corresponding to the physical heterogeneous device can be deleted. If it is detected that a new physical heterogeneous device is added, the virtual heterogeneous device corresponding to the physical heterogeneous device can be created.

[0078] The device attribute information of the physical heterogeneous device in the physical attribute dimension is used to describe the basic physical attributes of the physical heterogeneous device, including but not limited to the device IP of the physical heterogeneous device, the heterogeneous card type, the heterogeneous card driver information, and the geographical information of the device.

[0079] For example, the device attribute information can be as shown in the following table.

[0080] Basic Information Information Description Change Frequency Device IP Network IP Address Information of the Device No Change after Configuration Heterogeneous Card Type of the Device Heterogeneous Card Model No Change after Confirmation Heterogeneous Card Driver Information Version Information of the Heterogeneous Driver Low-Frequency Upgrade Operation Geographical Information of the Device City-Room of the Device Location No Change after Confirmation ...... ...... ......

[0081] In this embodiment, the device attribute information of each physical heterogeneous device in the physical attribute dimension can be obtained from each physical heterogeneous device, and the device attribute information of each physical heterogeneous device in the physical attribute dimension can be associated with the virtual heterogeneous device corresponding to each physical heterogeneous device.

[0082] It can be understood that since the physical heterogeneous devices may be removed due to maintenance, replacement, etc., and may also be added due to actual requirements, therefore, the virtual heterogeneous devices corresponding to the corresponding physical heterogeneous devices will also be deleted or created accordingly. In this embodiment, the device attribute information of the physical heterogeneous device in the physical attribute dimension can be synchronously obtained by means of timed polling, so as to associate the device attribute information of the newly added physical heterogeneous device obtained with the virtual physical heterogeneous device corresponding to the physical heterogeneous device. When the virtual heterogeneous device is deleted, the device attribute information associated with the virtual heterogeneous device will also be deleted accordingly. Moreover, since some device attribute information will be changed, such as the heterogeneous card driver information will have low-frequency upgrade operations, by synchronously obtaining the device attribute information of the physical heterogeneous device by means of timed polling, it is also possible to synchronously update the device attribute information associated with the virtual heterogeneous device.

[0083] During the operation of heterogeneous physical devices, iterative operation is required, such as performing anomaly detection on heterogeneous physical devices, and when the overall utilization rate of a certain type of heterogeneous physical device is relatively low, converting the types of some idle heterogeneous physical devices in this type of heterogeneous physical device into other types, so that the heterogeneous physical devices can quickly respond to problems in the live network. Since this iterative operation affects service allocation, it is necessary to generate corresponding information related to service allocation to better allocate suitable heterogeneous physical devices for services. Since the iterative operation involves the operation status of heterogeneous physical devices, the operation status information of heterogeneous physical devices in the dimension of operation status can be obtained according to the operation status of heterogeneous physical devices.

[0084] In an optional embodiment, the heterogeneous physical devices include different types of heterogeneous physical devices. Obtaining the operation status information of heterogeneous physical devices in the dimension of operation status according to the operation status of heterogeneous physical devices includes:

[0085] If the operation status of the heterogeneous physical device is a category conversion status, obtain the operation status information used to describe the target category after the category conversion of the heterogeneous physical device.

[0086] In this embodiment, after the environmental deployment of multiple heterogeneous physical devices is completed, technicians can divide the multiple heterogeneous physical devices into multiple different types of heterogeneous physical devices and set the types for different types of heterogeneous physical devices. Then, the service allocation program can generate the operation status information used to describe the type of each heterogeneous physical device. The service allocation program can obtain the operation status information used to describe the type of each heterogeneous physical device and associate the operation status information used to describe the type of each heterogeneous physical device with the virtual heterogeneous device corresponding to each heterogeneous physical device.

[0087] Subsequently, when the operation status of the heterogeneous physical device is a category conversion status, the service allocation program can generate the operation status information used to describe the target category after the category conversion of the heterogeneous physical device. The service allocation program can obtain the operation status information used to describe the target category after the category conversion of the heterogeneous physical device and update the operation status information used to describe the type of the heterogeneous physical device associated with the virtual heterogeneous device corresponding to the heterogeneous physical device based on this operation status information.

[0088] For example, during the operation of physical heterogeneous devices, there may be physical heterogeneous devices that need to undergo category conversion. It is possible to determine that the operation state of the physical heterogeneous device is the category conversion state, determine the target category after the category conversion of the physical heterogeneous device, generate operation state information for describing the target category after the category conversion of the physical heterogeneous device, delete the operation state information for describing the category of the physical heterogeneous device to be converted associated with the virtual heterogeneous device corresponding to the physical heterogeneous device, and associate the operation state information for describing the target category after the category conversion of the physical heterogeneous device with the virtual heterogeneous device corresponding to the physical heterogeneous device, so as to update the operation state information for describing the category of the physical heterogeneous device associated with the virtual heterogeneous device corresponding to the physical heterogeneous device.

[0089] It should be noted that when a certain physical heterogeneous device is a physical heterogeneous device assigned to a certain service, and the operation state requirement condition of the service specifies that the category of the physical heterogeneous device executing the service is the category before the category conversion of the physical heterogeneous device, after generating the operation state information for describing the target category after the category conversion of the physical heterogeneous device, if the physical heterogeneous device does not execute the service, the service will not be assigned to the physical heterogeneous device for execution subsequently.

[0090] In an optional embodiment, different categories of physical heterogeneous devices include physical heterogeneous devices of the first category and physical heterogeneous devices of the second category. If the operation state of the physical heterogeneous device is the category conversion state, before obtaining the operation state information for describing the target category after the category conversion of the physical heterogeneous device, it further includes:

[0091] Obtain the total utilization rate of the physical heterogeneous devices of the first category to obtain the first utilization rate;

[0092] If the first utilization rate is less than the first utilization rate threshold, determine the operation state of at least one idle physical heterogeneous device among the physical heterogeneous devices of the first category as the category conversion state, and determine the second category as the target category.

[0093] For example, the first category can be the private pool device category, and the second category can be the shared pool device category. The first category can also be the shared pool device category, and the second category can also be the private pool device category. Among them, the entity heterogeneous devices in the private pool device category can only be used by a certain service alone, while the entity heterogeneous devices in the shared pool device category can be used jointly by multiple services. Taking the first category as the private pool device category and the second category as the shared pool device category as an example, when the total utilization rate of the entity heterogeneous devices in the private pool device category, that is, the first total utilization rate, is low, in order to improve the utilization rate of the entity heterogeneous devices in the private pool device category, a technician can preset a utilization rate threshold as the first utilization rate threshold in advance, and when it is set that the first total utilization rate is less than this first utilization rate threshold, determine the operating state of at least one idle entity heterogeneous device in the entity heterogeneous devices in the private pool device category as the category conversion state, and determine the shared pool device category as the target category. Then, when the first total utilization rate is less than the first utilization rate threshold, the operating state of at least one idle entity heterogeneous device in the entity heterogeneous devices in the private pool device category can be determined as the category conversion state, and the shared pool device category can be determined as the target category.

[0094] In an optional embodiment, before determining the operating state of at least one idle entity heterogeneous device in the entity heterogeneous devices of the first category as the category conversion state if the first utilization rate is less than the first utilization rate threshold, it further includes:

[0095] Obtain the total utilization rate of the entity heterogeneous devices in the second category to obtain the second utilization rate;

[0096] If the first utilization rate is less than the first utilization rate threshold, determining the operating state of at least one idle entity heterogeneous device in the entity heterogeneous devices of the first category as the category conversion state includes:

[0097] If the first utilization rate is less than the first utilization rate threshold and the second utilization rate is greater than the second utilization rate threshold, determine the operating state of at least one idle entity heterogeneous device in the entity heterogeneous devices of the first category as the category conversion state.

[0098] For example, taking the first category as the private pool device category and the second category as the shared pool device category as an example, considering the scenario where the overall utilization rate of the entity heterogeneous devices in the private pool device category is relatively low, and the overall utilization rate of the entity heterogeneous devices in the shared pool device category is also relatively low. At this time, it is not very meaningful to convert some of the entity heterogeneous devices in the private pool device category into entity heterogeneous devices in the shared pool device category. Therefore, in this embodiment, when the overall utilization rate of the entity heterogeneous devices in the private pool device category, that is, the first overall utilization rate, is relatively low, and the overall utilization rate of the entity heterogeneous devices in the shared pool device category, that is, the second overall utilization rate, is relatively high, the operating state of at least one idle entity heterogeneous device in the entity heterogeneous devices in the private pool device category can be determined as the category conversion state, and the shared pool device category can be determined as the target category.

[0099] Specifically, a technician can pre-set a utilization rate threshold as the first utilization rate threshold, and then set another utilization rate threshold as the second utilization rate threshold. When the first overall utilization rate is less than this first utilization rate threshold, it is considered that the overall utilization rate of the entity heterogeneous devices in the private pool device category is relatively low. When the second overall utilization rate is greater than this second utilization rate threshold, it is considered that the overall utilization rate of the entity heterogeneous devices in the shared pool device category is relatively high. Then, when the first overall utilization rate is less than this first utilization rate threshold and the second overall utilization rate is greater than this second utilization rate threshold, the operating state of at least one idle entity heterogeneous device in the entity heterogeneous devices in the private pool device category can be determined as the category conversion state, and the shared pool device category can be determined as the target category.

[0100] In a possible implementation manner, the number of entity heterogeneous devices with the operating state of category conversion state can be set by the technician in real time. If the number set by the technician in real time is 10, then, the operating state of any 10 entity heterogeneous devices among all the idle entity heterogeneous devices in the entity heterogeneous devices of the first category can be determined as the category conversion state.

[0101] In another possible implementation manner, a conversion ratio can be pre-set. After determining all the idle entity heterogeneous devices in the entity heterogeneous devices of the first category, the product of the number of idle entity heterogeneous devices and this conversion ratio can be used as the number of entity heterogeneous devices with the operating state of category conversion state. For example, assuming the conversion ratio is 0.3 and the number of all idle entity heterogeneous devices in the entity heterogeneous devices of the first category is 20, then the number of entity heterogeneous devices with the operating state of category conversion state is 6. Then, the operating state of any 6 entity heterogeneous devices among the idle entity heterogeneous devices in the entity heterogeneous devices of the first category can be determined as the category conversion state.

[0102] In an alternative embodiment, according to the operating state of the physical heterogeneous device, obtain the operating state information of the physical heterogeneous device in the dimension of the operating state, including:

[0103] If the operating state of the physical heterogeneous device is an abnormal operating state, obtain the operating state information used to describe the abnormality of the physical heterogeneous device.

[0104] For example, it is also possible to determine the physical heterogeneous device with an abnormality from the physical heterogeneous devices, determine the operating state of the physical heterogeneous device as an abnormal operating state, and generate the operating state information used to describe the abnormality of the physical heterogeneous device; the operating state information can be obtained and associated with the virtual heterogeneous device corresponding to the physical heterogeneous device.

[0105] For example, assume that the physical heterogeneous device D11 has an abnormality. Then, it can be determined that the operating state of the physical heterogeneous device D11 is an abnormal operating state. Then, the operating state information used to describe the abnormality of the physical heterogeneous device D11 can be generated; the operating state information used to describe the abnormality of the physical heterogeneous device D11 can be obtained and associated with the virtual heterogeneous device D21 corresponding to the physical heterogeneous device D11.

[0106] In a possible implementation manner, when the physical heterogeneous device executes a service, if there are many abnormal situations or a high frequency of performance abnormalities, it can be determined that the physical heterogeneous device has an abnormality.

[0107] When a certain physical heterogeneous device recovers from an abnormal operating state to a normal operating state, it is also possible to delete the operating state information used to describe the abnormality of the physical heterogeneous device associated with the virtual heterogeneous device corresponding to the physical heterogeneous device.

[0108] It can be understood that the operating state information associated with a certain virtual physical heterogeneous device can only include the operating state information used to describe the category of the physical heterogeneous device corresponding to the virtual physical heterogeneous device; it can also only include the operating state information used to describe the abnormality of the physical heterogeneous device corresponding to the virtual physical heterogeneous device; it can also include the operating state information used to describe the category of the physical heterogeneous device corresponding to the virtual physical heterogeneous device and the operating state information used to describe the abnormality of the physical heterogeneous device corresponding to the virtual physical heterogeneous device.

[0109] It can be understood that users will submit the services that need to be executed on the service allocation system. The service allocation program in the service allocation system will screen and allocate the entity heterogeneous devices for the services, and allocate the services submitted by the users to the entity heterogeneous devices for execution, so as to implement the execution of the services submitted by the users. When submitting the services that need to be executed, users will submit the requirement conditions of the services. The requirement conditions of the services include at least one of the physical attribute requirement conditions, service requirement conditions, and operation status requirement conditions. The physical attribute requirement conditions are used to specify the conditions that the device attribute information of the entity heterogeneous device required for service execution needs to meet in the physical attribute dimension. The service requirement conditions are used to specify the conditions that the service requirement information of the entity heterogeneous device required for service execution needs to meet in the service requirement dimension. The operation status requirement conditions are used to specify the conditions that the operation status information of the entity heterogeneous device required for service execution needs to meet in the operation status dimension.

[0110] It can be understood that the device attribute information of the entity heterogeneous device in the physical attribute dimension can be directly obtained from the entity heterogeneous device, and the operation status information of the entity heterogeneous device in the operation status dimension can be obtained according to the operation status of the entity heterogeneous device during the actual operation process of the entity heterogeneous device. For the service requirement information of the entity heterogeneous device in the service requirement dimension, it needs to be obtained according to the service requirement conditions in the requirement conditions of the service. Based on the above description, the conditions corresponding to the device attribute information in the requirement conditions can be determined as the physical attribute requirement conditions, the conditions corresponding to the operation status information in the requirement conditions can be determined as the operation status requirement conditions, and the remaining conditions in the requirement conditions can be determined as the service requirement conditions.

[0111] For example, assume that the requirement conditions of a certain service include the device IP requirement condition, the device health requirement condition, and the device category requirement condition. Among them, the device IP requirement condition is used to specify the device IP of the entity heterogeneous device required for the execution of this service, the device health requirement condition is used to specify the minimum health level that the entity heterogeneous device required for the execution of this service needs to reach, and the device category requirement condition is used to specify the category of the entity heterogeneous device required for the execution of this service. Since the device attribute information includes the device IP information, therefore, this device IP requirement condition corresponds to the device attribute information. Since the operation status information includes the information used to describe the category of the entity heterogeneous device, therefore, this device category requirement condition corresponds to the operation status information. However, neither the device attribute information nor the operation status information can correspond to the device health requirement condition. Therefore, the device health requirement condition can be determined as the service requirement condition.

[0112] In an optional embodiment, obtaining the service requirement information of the entity heterogeneous device in the service requirement dimension according to the historical service requirement conditions in the historical requirement conditions of the historical executed services includes:

[0113] If the historical service requirement conditions include equipment health requirement conditions, obtain service requirement information for describing the health of entity heterogeneous devices. The equipment health requirement conditions are used to specify the minimum health that the entity heterogeneous devices for executing the historical executed service need to achieve.

[0114] For example, the service requirement conditions of a certain historical executed service submitted by a user include equipment health requirement conditions, and the equipment health requirement conditions are used to specify the minimum health that the entity heterogeneous devices for executing the historical executed service need to achieve. Therefore, it can be known that service requirement information for describing the health of entity heterogeneous devices needs to be obtained to match the equipment health requirement conditions. Then, when there is no service requirement information for describing the health of entity heterogeneous devices, prompt information for indicating the health of the input entity heterogeneous devices can be output to indicate the health of the input entity heterogeneous devices. After seeing this prompt information, technicians can input the health of the entity heterogeneous devices according to the accumulated experience, so that the service allocation program obtains service requirement information for describing the health of entity heterogeneous devices. The service requirement information for describing the health of entity heterogeneous devices obtained by the service allocation program can be service requirement information for describing the health of each entity heterogeneous device corresponding to each entity heterogeneous device. The service allocation program can associate the service requirement information for describing the health of each entity heterogeneous device with the virtual heterogeneous devices corresponding to each entity heterogeneous device.

[0115] It can be understood that since the health of entity heterogeneous devices is not constant, the health of the input entity heterogeneous devices can be indicated regularly to realize the regular update of the service requirement information for describing the health of the entity heterogeneous devices corresponding to each virtual heterogeneous device.

[0116] It can also be understood that since entity heterogeneous devices will be removed due to maintenance, replacement, etc., and will also be added due to actual needs, the virtual heterogeneous devices corresponding to the corresponding entity heterogeneous devices will also be deleted or added accordingly. In this embodiment, the health of the input entity heterogeneous devices can be indicated regularly, so as to associate the obtained service requirement information for describing the health of the newly added entity heterogeneous devices with the virtual entity heterogeneous devices corresponding to the entity heterogeneous devices. When a virtual heterogeneous device is deleted, the service requirement information for describing the health of the entity heterogeneous device corresponding to the virtual heterogeneous device associated with it will also be deleted accordingly.

[0117] It can be understood that when there is business requirement information for describing the health of entity heterogeneous devices, if the business requirement conditions of the historical executed business submitted by the user include device health requirement conditions, the entity heterogeneous devices assigned to the historical executed business can be directly screened according to the business requirement information associated with the virtual heterogeneous devices; or the business requirement information for describing the health of the entity heterogeneous devices corresponding to each virtual heterogeneous device can be updated first, and then the entity heterogeneous devices assigned to the historical executed business can be screened according to the business requirement information associated with the virtual heterogeneous devices.

[0118] Subsequently, the target entity heterogeneous devices assigned to the to-be-executed business can also be directly screened according to the business requirement information, or the business requirement information for describing the health of the entity heterogeneous devices corresponding to each virtual heterogeneous device can be updated first, and then the target entity heterogeneous devices assigned to the to-be-executed business can be screened according to the business requirement information associated with the virtual heterogeneous devices.

[0119] In an optional embodiment, according to the historical business requirement conditions in the historical requirement conditions of the historical executed business, the business requirement information of the entity heterogeneous devices in the business requirement dimension is obtained, including:

[0120] If the historical business requirement conditions include anti-affinity business requirement conditions, when the entity heterogeneous devices assigned to the historical executed business execute the historical executed business, business requirement information is generated. The anti-affinity business requirement conditions are used to specify anti-affinity businesses that cannot be executed by the same entity heterogeneous device as the historical executed business at the same time, and the business requirement information is used to describe that the entity heterogeneous devices cannot execute the anti-affinity businesses.

[0121] For example, the business requirement conditions of a certain historical executed business submitted by the user include anti-affinity business requirement conditions, and the anti-affinity business requirement conditions are used to specify anti-affinity businesses that cannot be executed by the same entity heterogeneous device as this business at the same time. Then, when the entity heterogeneous devices assigned to the historical executed business execute the historical executed business, the business allocation program can generate business requirement information for describing that the entity heterogeneous devices cannot execute the anti-affinity businesses. The business allocation program can obtain the business requirement information and associate the business requirement information with the virtual heterogeneous devices corresponding to the entity heterogeneous devices. Subsequently, the target entity heterogeneous devices assigned to the to-be-executed business can be screened according to the business requirement information. It can be understood that when the to-be-executed business is the anti-affinity business, the screened target entity heterogeneous devices assigned to the to-be-executed business do not include the entity heterogeneous devices. When the historical executed business is completed, the business requirement information can also be deleted so that the matching entity heterogeneous devices can participate in the screening of the target entity heterogeneous devices of the anti-affinity business submitted subsequently.

[0122] It can be understood that the service requirement information associated with a virtual entity heterogeneous device may only include the service requirement information for describing the health of the entity heterogeneous device corresponding to the virtual entity heterogeneous device; it may also only include the service requirement information for describing that the entity heterogeneous device corresponding to the virtual entity heterogeneous device cannot execute the corresponding anti-affinity service; it may also include the service requirement information for describing the health of the entity heterogeneous device corresponding to the virtual entity heterogeneous device and the service requirement information for describing that the entity heterogeneous device corresponding to the virtual entity heterogeneous device cannot execute the corresponding anti-affinity service.

[0123] In 105, according to the device attribute information, service requirement information, and operation status information associated with the virtual heterogeneous device, determine the target entity heterogeneous device that matches the current requirement conditions of the service to be executed, and allocate the service to be executed to the target entity heterogeneous device for execution. The current requirement conditions include at least one of the current physical attribute requirement conditions, current service requirement conditions, and current operation status requirement conditions.

[0124] In this embodiment, when it is necessary to screen for the target entity heterogeneous device for the service to be executed, the target entity heterogeneous device that matches the current requirement conditions of the service to be executed can be determined according to the device attribute information, service requirement information, and operation status information associated with the virtual heterogeneous device, and the service to be executed is allocated to the target entity heterogeneous device for execution. Among them, the service to be executed and the historical executed service are relative concepts, and the historical executed service is the service submitted before the service to be executed.

[0125] For example, assume that the current requirement conditions for the business to be executed include device IP requirement conditions, device health requirement conditions, and device category requirement conditions. The network IP addresses specified by the device IP requirement conditions include network IP addresses P1, P2... Pn. The minimum health requirement specified by the device health requirement conditions is 85%. The device category specified by the device category requirement conditions is the shared pool device category. Then, the network IP address in the device attribute information associated with the target virtual heterogeneous device needs to be any one of the network IP addresses P1, P2... Pn. The health described in the business requirement information associated with the target virtual heterogeneous device and used to describe the health of the entity heterogeneous device corresponding to the target virtual heterogeneous device needs to be greater than or equal to 85%. The business requirement information associated with the target virtual heterogeneous device does not include the business requirement information used to describe that the entity heterogeneous device corresponding to the target virtual heterogeneous device cannot execute the business to be executed. The device category described in the operation status information associated with the target virtual heterogeneous device and used to describe the category of the entity heterogeneous device corresponding to the target virtual heterogeneous device needs to be the shared pool device category. The operation status information associated with the target virtual heterogeneous device does not include the operation status information used to describe that the entity heterogeneous device corresponding to the target virtual heterogeneous device has an abnormality. Based on the above method, the target virtual heterogeneous device that matches the current requirement conditions of the business to be executed can be determined, and the entity heterogeneous device corresponding to the target virtual heterogeneous device is the target entity heterogeneous device that matches the current requirement conditions of the business to be executed. After the target entity heterogeneous device is determined, the business to be executed can be assigned to the target entity heterogeneous device for execution.

[0126] In an optional embodiment, determining the target entity heterogeneous device that matches the current requirement conditions of the business to be executed according to the device attribute information, business requirement information, and operation status information associated with the virtual heterogeneous device includes:

[0127] Determining candidate entity heterogeneous devices that match the current requirement conditions of the business to be executed according to the device attribute information, business requirement information, and operation status information associated with the virtual heterogeneous device;

[0128] Obtaining the historical stability information of the candidate entity heterogeneous devices, where the historical stability information is used to characterize the stability of the candidate entity heterogeneous devices within a historical period;

[0129] Screening the target entity heterogeneous devices from the candidate entity heterogeneous devices according to the historical stability information.

[0130] In this embodiment, to better execute the to-be-executed service, when screening for the target entity heterogeneous device for the to-be-executed service, the stability of the entity heterogeneous device can be taken as a consideration factor to screen for the target entity heterogeneous device. Specifically, first, according to the device attribute information, service requirement information, and operation status information associated with the virtual heterogeneous device, the candidate entity heterogeneous devices that match the current requirement conditions of the to-be-executed service can be determined, and then, further based on the historical stability information of the candidate entity heterogeneous devices, the target entity heterogeneous devices can be screened from the candidate entity heterogeneous devices.

[0131] For example, it can be timed, such as reporting the working status of each entity heterogeneous device, such as the running state or the failed state, to the resource portrait center every 10 seconds. The resource portrait center constructs the device stability portrait of each entity heterogeneous device based on the reported working status. This device stability portrait can present the stability of the entity heterogeneous device within the historical duration, such as within the past 7 days. For example, in the form of a numerical value according to the time series, such as presenting the stability of the entity heterogeneous device within the historical duration every 10 minutes. The larger the numerical value, the better the stability. This device stability portrait can be used as the historical stability information of the entity heterogeneous device. After the service allocation program screens out the candidate entity heterogeneous devices, the candidate entity heterogeneous devices can be input into the resource portrait center, and the resource portrait center can screen the target entity heterogeneous devices from the candidate entity heterogeneous devices according to the device stability portrait of the candidate entity heterogeneous devices.

[0132] In an optional embodiment, screening the target virtual heterogeneous device from the candidate virtual heterogeneous devices according to the historical stability information includes:

[0133] Obtain the device requirement quantity of the to-be-executed service;

[0134] According to the historical stability information, screen the target virtual heterogeneous devices with the device requirement quantity from the candidate virtual heterogeneous devices.

[0135] When the user submits the to-be-executed service, the device requirement quantity of the to-be-executed service will also be set, that is, the number of entity heterogeneous devices for executing the to-be-executed service. Then, after determining the candidate entity heterogeneous devices that match the current requirement conditions of the to-be-executed service according to the device attribute information, service requirement information, and operation status information associated with the virtual heterogeneous device, the target entity heterogeneous devices with this device requirement quantity can be further screened from the candidate entity heterogeneous devices according to the historical stability information of the candidate entity heterogeneous devices.

[0136] For example, assume that the required number of devices is 5 and there are 10 candidate entity heterogeneous devices. These 10 candidate entity heterogeneous devices can form a list of candidate entity heterogeneous devices. After screening out the list of candidate entity heterogeneous devices, the computer device inputs the list of candidate entity heterogeneous devices into the resource portrait center. The resource portrait center can calculate the standard deviation of the values used to characterize the stability of each candidate entity heterogeneous device in the past 7 days based on the device stability portrait of each candidate entity heterogeneous device, sort the candidate entity heterogeneous devices in the list of candidate entity heterogeneous devices in descending order of the standard deviation, and determine the top 5 candidate entity heterogeneous devices with higher rankings as the target entity heterogeneous devices to obtain a list of target entity heterogeneous devices. The resource portrait center can output the list of target entity heterogeneous devices to the service allocation program. The service allocation program then obtains the list of target entity heterogeneous devices and can allocate the services to be executed to the list of target entity heterogeneous devices for execution.

[0137] In an optional embodiment, screening target entity heterogeneous devices from candidate entity heterogeneous devices according to historical stability information includes:

[0138] Obtaining the required number of devices for the service to be executed;

[0139] Screening target entity heterogeneous devices with the required number of devices from candidate entity heterogeneous devices according to historical stability information.

[0140] In this embodiment, to better execute the service to be executed, when screening target entity heterogeneous devices for the service to be executed, the stability of the entity heterogeneous devices can be used as a consideration factor to screen the target entity heterogeneous devices. Specifically, first, according to the device attribute information, service requirement information, and operation status information associated with the virtual heterogeneous device, determine the candidate entity heterogeneous devices that match the current requirement conditions of the service to be executed, and then further determine the stability trend of the candidate entity heterogeneous devices according to the historical stability information of the candidate entity heterogeneous devices; according to the stability trend, screen the target entity heterogeneous devices from the candidate entity heterogeneous devices.

[0141] For example, if it is determined that a certain candidate entity heterogeneous device is becoming more and more stable based on the device stability value of the candidate entity heterogeneous device, it can be determined that the stability trend of the candidate entity heterogeneous device is relatively good; if it is determined that a certain candidate entity heterogeneous device is becoming more and more unstable based on the device stability value of the candidate entity heterogeneous device, it can be determined that the stability trend of the candidate entity heterogeneous device is relatively poor, and the candidate entity heterogeneous devices with relatively good stability trends among the candidate entity heterogeneous devices can be determined as the target entity heterogeneous devices.

[0142] In an optional embodiment, before determining a target virtual heterogeneous device that matches the current requirement conditions of the service to be executed according to the device attribute information, service requirement information, and operation status information associated with the virtual heterogeneous device, it further includes:

[0143] According to the current service requirement conditions in the current requirement conditions, obtain the service requirement update information of the physical heterogeneous device in the dimension of service requirements;

[0144] Update the service requirement information associated with the virtual heterogeneous device according to the service requirement update information.

[0145] In this embodiment, the service requirement information associated with the virtual heterogeneous device is also updated according to the current service requirement conditions of the service to be executed. For example, assume that the current service requirement conditions include the device health requirement condition, and this device health requirement condition is used to specify the minimum health that the physical heterogeneous device for executing the service to be executed needs to achieve. Therefore, it can be known that the service requirement information for describing the health of the physical heterogeneous device needs to be obtained to match this device health requirement condition. When there is service requirement information for describing the health of the physical heterogeneous device, considering that the health of the device is not constant, in order to better screen the target physical heterogeneous device for the service to be executed, a prompt message for indicating the health of the input physical heterogeneous device can be output to indicate the health of the input physical heterogeneous device. After seeing this prompt message, technicians can input the current health of the physical heterogeneous device according to the accumulated experience, so that the service allocation program obtains the service requirement update information for describing the current health of the physical heterogeneous device. The service requirement update information for describing the current health of the physical heterogeneous device obtained by the service allocation program can be the service requirement update information for describing the current health of each physical heterogeneous device corresponding to each physical heterogeneous device. The service allocation program can replace the service requirement information for describing the health of each physical heterogeneous device associated with the virtual heterogeneous device corresponding to each physical heterogeneous device with the service requirement update information for describing the current health of each physical heterogeneous device to achieve the update of the service requirement information. When there is no service requirement information for describing the health of the physical heterogeneous device, a prompt message for indicating the health of the input physical heterogeneous device can be output to indicate the health of the input physical heterogeneous device. After seeing this prompt message, technicians can input the health of the physical heterogeneous device according to the accumulated experience, so that the service allocation program obtains the service requirement update information for describing the current health of the physical heterogeneous device. The service allocation program can use the service requirement update information for describing the current health of each physical heterogeneous device as the service requirement information for describing the health of each physical heterogeneous device associated with the virtual heterogeneous device corresponding to each physical heterogeneous device to achieve the update of the service requirement information associated with the virtual heterogeneous device. Subsequently, the target physical heterogeneous device that matches the current requirement conditions of the service to be executed can be determined according to the device attribute information, service requirement information, and operation status information associated with the virtual heterogeneous device.

[0146] Since the association operation of directly associating device attribute information, service requirement information, and operation status information with heterogeneous physical devices may cause the risk of interruption of the services being executed on the heterogeneous physical devices, it is necessary to wait until the services being executed are completed before performing the association operation of associating the device attribute information, service requirement information, and operation status information with the heterogeneous physical devices. And allocating a target heterogeneous physical device for the service to be executed needs to wait until after the device attribute information, service requirement information, and operation status information are associated with the heterogeneous physical devices, and then allocate a target heterogeneous physical device for the service to be executed according to the device attribute information, service requirement information, and operation status information, resulting in poor flexibility in service allocation. In the embodiments of the present application, device attribute information of a heterogeneous physical device in the physical attribute dimension is obtained from the heterogeneous physical device; according to the historical service requirement conditions in the historical requirement conditions of the historical executed services, service requirement information of the heterogeneous physical device in the service requirement dimension is obtained; according to the operation status of the heterogeneous physical device, operation status information of the heterogeneous physical device in the operation status dimension is obtained; a virtual heterogeneous device corresponding to the heterogeneous physical device is created, and the device attribute information, service requirement information, and operation status information are associated with the virtual heterogeneous device; according to the device attribute information, service requirement information, and operation status information associated with the virtual heterogeneous device, a target heterogeneous physical device that matches the current requirement conditions of the service to be executed is determined, and the service to be executed is allocated to the target heterogeneous physical device for execution. The current requirement conditions include at least one of the current physical attribute requirement conditions, current service requirement conditions, and current operation status requirement conditions. Thus, by associating the device attribute information, service requirement information, and operation status information with the virtual heterogeneous device corresponding to the heterogeneous physical device, since this association operation does not directly act on the heterogeneous physical device and does not cause the risk of interruption of the services being executed on the heterogeneous physical device, there is no need to wait until the services being executed are completed before performing the association operation of associating the device attribute information, service requirement information, and operation status information with the virtual heterogeneous device corresponding to the heterogeneous physical device. Therefore, a target heterogeneous physical device can be allocated for the service to be executed in a timely manner according to the device attribute information, service requirement information, and operation status information associated with the virtual heterogeneous device, and the flexibility of service allocation is better.

[0147] Please refer to Figure 2a and Figure 2b , Figure 2a which is the second process schematic diagram of the service allocation method provided by the embodiments of the present application. Figure 2b which is the scenario schematic diagram of the service allocation method provided by the embodiments of the present application. The process may include:

[0148] 201. Obtain device attribute information of a heterogeneous physical device in the physical attribute dimension from the heterogeneous physical device.

[0149] 202. Obtain the business requirement information of the entity heterogeneous devices in the dimension of business requirements according to the historical business requirement conditions in the historical requirement conditions of the historical executed services.

[0150] 203. Obtain the operation status information of the entity heterogeneous devices in the dimension of operation status according to the operation status of the entity heterogeneous devices.

[0151] 204. Create virtual heterogeneous devices corresponding to the entity heterogeneous devices, and associate the device attribute information, business requirement information and operation status information with the virtual heterogeneous devices.

[0152] For example, assume that multiple entity heterogeneous devices include entity heterogeneous devices D11, D12, D13... D1n, then create virtual heterogeneous devices D21, D22, D23... D2n corresponding to entity heterogeneous devices D11, D12, D13... D1n respectively. Wherein, n is a positive integer greater than 3.

[0153] It can be understood that since entity heterogeneous devices may be removed due to maintenance, replacement, etc., and may also be added due to actual requirements, in order to better screen and match entity heterogeneous devices for services, it is possible to synchronously detect whether entity heterogeneous devices are removed or whether new entity heterogeneous devices are added by timed polling. If it is detected that a certain entity heterogeneous device is removed, the virtual heterogeneous device corresponding to this entity heterogeneous device can be deleted. If it is detected that a new entity heterogeneous device is added, a virtual heterogeneous device corresponding to this entity heterogeneous device can be created.

[0154] For example, assume that entity heterogeneous device D12 is removed, then the virtual heterogeneous device D22 corresponding to entity heterogeneous device D12 can be deleted. Assume that a new entity heterogeneous device D1(n + 1) is added, then a virtual heterogeneous device D2(n + 1) corresponding to this entity heterogeneous device D1(n + 1) can be created.

[0155] Among them, the device attribute information of the entity heterogeneous devices in the physical attribute dimension is used to describe the basic physical attributes of the entity heterogeneous devices, including but not limited to the device IP of the entity heterogeneous devices, heterogeneous card types, heterogeneous card driver information, and geographical information of the devices.

[0156] For example, the device attribute information of entity heterogeneous devices D11, D12, D13... D1n can be obtained from entity heterogeneous devices D11, D12, D13... D1n respectively, and the device attribute information of entity heterogeneous devices D11, D12, D13... D1n is associated with virtual heterogeneous devices D21, D22, D23... D2n respectively.

[0157] It can be understood that since physical heterogeneous devices may be removed due to maintenance, replacement, etc., and may also be added due to actual requirements, corresponding virtual heterogeneous devices corresponding to the physical heterogeneous devices will be deleted or added accordingly, and some device attribute information will be modified. For example, there will be low-frequency upgrade operations for heterogeneous card driver information. In this embodiment, the device attribute information of physical heterogeneous devices can be synchronously obtained by timed polling, so as to realize the synchronous update of the device attribute information associated with virtual heterogeneous devices.

[0158] In this embodiment, the business requirement information of physical heterogeneous devices in the dimension of business requirements can also be obtained according to the historical business requirement conditions in the historical requirements conditions of historical executed services, and the business requirement information can be associated with virtual heterogeneous devices. Subsequently, physical heterogeneous devices that match the services can be screened based on the business requirement information.

[0159] For example, the business requirement conditions of a certain historical executed service submitted by a user include device health requirement conditions. When there is no business requirement information for describing the health of physical heterogeneous devices, the business requirement information for describing the health of each physical heterogeneous device can be obtained and associated with the virtual heterogeneous devices corresponding to each physical heterogeneous device.

[0160] For example, the business requirement information for describing the health of physical heterogeneous devices D11, D12, D13......D1n will be associated with virtual heterogeneous devices D21, D22, D23......D2n respectively.

[0161] It can be understood that since physical heterogeneous devices may be removed due to maintenance, replacement, etc., and may also be added due to actual requirements, corresponding virtual heterogeneous devices corresponding to the physical heterogeneous devices will be deleted or added accordingly. In this embodiment, the health of the input physical heterogeneous devices can be indicated at regular intervals, so as to associate the obtained business requirement information for describing the health of the newly added physical heterogeneous devices with the virtual physical heterogeneous devices corresponding to the physical heterogeneous devices. When a virtual heterogeneous device is deleted, the business requirement information for describing the health of the physical heterogeneous device corresponding to the virtual heterogeneous device associated with it will also be deleted accordingly.

[0162] When there is business requirement information for describing the health of each physical heterogeneous device, if the business requirement conditions of a certain historical executed service submitted by a user include device health requirement conditions, the physical heterogeneous devices for executing the historical executed service can be directly screened according to the business requirement information associated with each virtual heterogeneous device; or the business requirement information for describing the health of the physical heterogeneous device corresponding to each virtual heterogeneous device associated with each virtual heterogeneous device can be updated first, and then the physical heterogeneous devices for executing the historical executed service can be screened according to the business requirement information associated with each virtual heterogeneous device.

[0163] For another example, assume that the business requirement conditions of a certain historical executed service submitted by a user include anti-affinity business requirement conditions. Then, when the execution entity heterogeneous device assigned to execute the historical executed service executes the historical executed service, it is possible to obtain business requirement information used to describe that the execution entity heterogeneous device cannot execute the anti-affinity business, and associate the business requirement information with the virtual heterogeneous device corresponding to the execution entity heterogeneous device.

[0164] For example, assume that the business requirement conditions of the historical executed service B1 submitted by a user include anti-affinity business requirement conditions. The anti-affinity business requirement conditions indicate that service B1 cannot be executed by the same entity heterogeneous device as services B2, B3, and B4. The execution entity heterogeneous devices include the entity heterogeneous device D12. Then, when the entity heterogeneous device D12 executes the historical executed service B1, it is possible to generate business requirement information used to describe that the entity heterogeneous device D12 cannot execute services B2, B3, and B4; it is possible to obtain the business requirement information and associate the business requirement information with the virtual heterogeneous device D22.

[0165] Since during the operation of an entity heterogeneous device, iterative operation operations need to be continuously performed to enable the entity heterogeneous device to quickly respond to problems in the live network, and the iterative operation operations will affect service allocation, it is necessary to correspondingly generate information related to service allocation to better allocate a suitable entity heterogeneous device for the service. Since the iterative operation operations involve the operation state of the entity heterogeneous device, it is possible to obtain the operation state information of the entity heterogeneous device in the operation state dimension according to the operation state of the entity heterogeneous device.

[0166] For example, multiple entity heterogeneous devices include entity heterogeneous devices of different categories. During the operation of the entity heterogeneous device, there may be an entity heterogeneous device that needs to perform category conversion. It is possible to determine that the operation state of the entity heterogeneous device is the category conversion state, determine the target category after the category conversion of the entity heterogeneous device, and then generate operation state information used to describe the target category after the category conversion of the entity heterogeneous device, delete the operation state information used to describe the category of the entity heterogeneous device associated with the virtual heterogeneous device corresponding to the entity heterogeneous device, and associate the operation state information used to describe the target category after the category conversion of the entity heterogeneous device with the virtual heterogeneous device corresponding to the entity heterogeneous device, so as to update the operation state information used to describe the category of the entity heterogeneous device associated with the virtual heterogeneous device corresponding to the entity heterogeneous device.

[0167] In an alternative embodiment, after the environmental deployment of multiple entity heterogeneous devices is completed, technicians can also divide the multiple entity heterogeneous devices into multiple different categories of entity heterogeneous devices and set the categories for different categories of entity heterogeneous devices on the service allocation program. Then, the service allocation program can generate operation status information for describing the category of each entity heterogeneous device. The service allocation program can obtain the operation status information for describing the category of each entity heterogeneous device and associate the operation status information for describing the category of each entity heterogeneous device with the virtual heterogeneous device corresponding to each entity heterogeneous device. Subsequently, after obtaining the operation status information for describing the target category after the category conversion of a certain entity heterogeneous device, the operation status information for describing the category of the entity heterogeneous device associated with the virtual heterogeneous device corresponding to the entity heterogeneous device can be updated based on this operation status information.

[0168] For example, assume that the multiple entity heterogeneous devices include entity heterogeneous devices D11, D12......D1200, and the virtual heterogeneous devices corresponding to entity heterogeneous devices D11, D12......D1200 are D21, D22......D2200. Among them, entity heterogeneous devices D11, D12,.....D1100 are classified as entity heterogeneous devices in the private pool device category, and entity heterogeneous devices D1101, D1102......D1200 are classified as entity heterogeneous devices in the shared pool device category. Then, the operation status information with the category of private pool device for describing entity heterogeneous device D11 is associated with virtual heterogeneous device D21, the operation status information with the category of private pool device for describing entity heterogeneous device D12 is associated with virtual heterogeneous device D22...... the operation status information with the category of private pool device for describing entity heterogeneous device D1100 is associated with virtual heterogeneous device D2100, the operation status information with the category of shared pool device for describing entity heterogeneous device D1101 is associated with virtual heterogeneous device D2101, the operation status information with the category of shared pool device for describing entity heterogeneous device D1102 is associated with virtual heterogeneous device D2102...... the operation status information with the category of shared pool device for describing entity heterogeneous device D1200 is associated with virtual heterogeneous device D2200.

[0169] After obtaining the operation status information describing the target category of the entity heterogeneous devices D13, D14......D120 after category conversion to the shared pool device category, the operation status information describing the entity heterogeneous device D13 with the category of private pool device associated with the virtual heterogeneous device D23 can be updated to the operation status information describing the entity heterogeneous device D13 with the category of shared pool device, and the operation status information describing the entity heterogeneous device D14 with the category of private pool device associated with the virtual heterogeneous device D24 can be updated to the operation status information describing the entity heterogeneous device D14 with the category of shared pool device...... The operation status information describing the entity heterogeneous device D120 with the category of private pool device associated with the virtual heterogeneous device D220 can be updated to the operation status information describing the entity heterogeneous device D120 with the category of shared pool device.

[0170] For another example, an entity heterogeneous device with an anomaly can be determined from the entity heterogeneous devices, the operation status of the entity heterogeneous device can be determined as an abnormal operation status, and operation status information describing the anomaly of the entity heterogeneous device can be generated; the operation status information can be obtained and associated with the virtual heterogeneous device corresponding to the entity heterogeneous device.

[0171] For example, assuming that the entity heterogeneous devices D133, D135, and D146 have anomalies, then, the operation status of the entity heterogeneous devices D133, D135, and D146 can be determined as an abnormal operation status. After obtaining the operation status information describing the anomalies of the entity heterogeneous devices D133, D135, and D146, the operation status information describing the anomaly of the entity heterogeneous device D133 is associated with the virtual heterogeneous device D233, the operation status information describing the anomaly of the entity heterogeneous device D134 is associated with the virtual heterogeneous device D234, and the operation status information describing the anomaly of the entity heterogeneous device D135 is associated with the virtual heterogeneous device D235.

[0172] When an entity heterogeneous device with an anomaly returns to normal, the operation status information describing the anomaly of the entity heterogeneous device associated with the virtual heterogeneous device corresponding to the entity heterogeneous device with the anomaly can also be deleted.

[0173] In an optional embodiment, the device attribute information, business requirement information, and operation status information can be associated with the virtual heterogeneous device and stored in a database.

[0174] 205. Obtain the business requirement update information of the entity heterogeneous device in the dimension of business requirements according to the current business requirement condition in the current requirement condition of the business to be executed.

[0175] 206. Update the service requirement information associated with the virtual heterogeneous device according to the service requirement update.

[0176] In this embodiment, the service requirement information associated with the virtual heterogeneous device is updated according to the current service requirement conditions of the service to be executed. For example, assume that the current service requirement conditions include the device health requirement condition. When there is service requirement information for describing the health of the physical heterogeneous device, the service requirement update information for describing the current health of the physical heterogeneous device can be obtained to replace the service requirement information for describing the health of each physical heterogeneous device associated with the virtual heterogeneous device corresponding to each physical heterogeneous device. When there is no service requirement information for describing the health of the physical heterogeneous device, the service requirement update information for describing the current health of each physical heterogeneous device can be obtained as the service requirement information for describing the health of each physical heterogeneous device associated with the virtual heterogeneous device corresponding to each physical heterogeneous device, so as to update the service requirement information associated with the virtual heterogeneous device.

[0177] 207. Determine candidate physical heterogeneous devices that match the current requirement conditions of the service to be executed according to the device attribute information, service requirement information, and operation status information associated with the virtual heterogeneous device.

[0178] For example, please refer to Figure 2c . Assume that the target service requirement conditions include the device IP requirement condition, the device health requirement condition, and the device category requirement condition. Among them, the network IP addresses specified by the device IP requirement condition include network IP addresses P1, P2......Pn, the minimum health specified by the device health requirement condition is 85%, and the device category specified by the device category requirement condition is the shared pool device category. Then, the network IP address in the device attribute information associated with the virtual heterogeneous device corresponding to the output candidate physical heterogeneous device needs to be any one of the network IP addresses P1, P2......Pn. The health described by the service requirement information for describing the health of the candidate physical heterogeneous device associated with the virtual heterogeneous device corresponding to the output candidate physical heterogeneous device needs to be greater than or equal to 85%. The service requirement information associated with the virtual heterogeneous device corresponding to the output candidate physical heterogeneous device does not include the service requirement information for describing that the candidate physical heterogeneous device cannot execute the service to be executed. The device category described by the operation status information for describing the category of the candidate physical heterogeneous device associated with the virtual heterogeneous device corresponding to the output candidate physical heterogeneous device needs to be the shared pool device category. The operation status information associated with the virtual heterogeneous device corresponding to the output candidate physical heterogeneous device does not include the operation status information for describing that the candidate physical heterogeneous device has an abnormality. Based on the above method, at least one candidate physical heterogeneous device that meets the target service requirement conditions can be screened from the physical heterogeneous devices.

[0179] 208. Obtain the historical stability information of candidate entity heterogeneous devices, where the historical stability information is used to describe the stability of candidate entity heterogeneous devices within a historical duration.

[0180] 209. Obtain the device demand quantity of the to-be-executed service.

[0181] 210. Screen the target entity heterogeneous devices with the device demand quantity from the candidate entity heterogeneous devices according to the historical stability information.

[0182] 211. Allocate the to-be-executed service to the target entity heterogeneous devices for execution.

[0183] For example, it can be timed. For instance, report the working status of each entity heterogeneous device, such as the running status or the failed status, to the resource portrait center every 10 seconds. The resource portrait center constructs the device stability portrait of each entity heterogeneous device based on the reported working status. The device stability portrait can present the stability of the entity heterogeneous device within a historical duration, such as within the past 7 days. For example, present the stability of the entity heterogeneous device within the historical duration in the form of a numerical value (with an upper limit of 1) at time intervals, such as every 10 minutes. This device stability portrait can be used as the historical stability information of the entity heterogeneous device.

[0184] For example, if the working status of the entity heterogeneous device is in the running state within 10 minutes, the corresponding numerical value N1 representing the stability of the entity heterogeneous device; if the number of times the status of the entity heterogeneous device is in the failed state within 10 minutes is between 1 and 10 times, the corresponding numerical value N2 representing the stability of the entity heterogeneous device; if the number of times the status of the entity heterogeneous device is in the failed state within 10 minutes is between 11 and 20 times, the corresponding numerical value N3 representing the stability of the entity heterogeneous device; if the number of times the status of the entity heterogeneous device is in the failed state within 10 minutes is between 21 and 30 times, the corresponding numerical value N4 representing the stability of the entity heterogeneous device; if the number of times the status of the entity heterogeneous device is in the failed state within 10 minutes is between 31 and 40 times, the corresponding numerical value N5 representing the stability of the entity heterogeneous device; if the number of times the status of the entity heterogeneous device is in the failed state within 10 minutes is between 41 and 50 times, the corresponding numerical value N6 representing the stability of the entity heterogeneous device; if the number of times the status of the entity heterogeneous device is in the failed state within 10 minutes is more than 51 times, the corresponding numerical value N7 representing the stability of the entity heterogeneous device. Among them, N1 > N2 > N3 > N4 > N5 > N6 > N7. The larger the numerical value representing the stability of the entity heterogeneous device, the better the stability of the entity heterogeneous device. The resource portrait center can determine the corresponding numerical value for each entity heterogeneous device based on the reported working status, and construct the device stability portrait of each entity heterogeneous device to represent the stability of each entity heterogeneous device. For example, the device stability portrait of each entity heterogeneous device can be as Figure 2d shown.

[0185] Please continue to refer to Figure 2c, assuming that the number of equipment requirements is 3, there are 10 candidate entity heterogeneous devices, and the 10 candidate entity heterogeneous devices can constitute a candidate entity heterogeneous device list. The business allocation program inputs the candidate entity heterogeneous device list into the resource portrait center. The resource portrait center can calculate the standard deviation of the numerical value used to characterize the stability of each candidate entity heterogeneous device in the past 7 days based on the device stability portrait of each candidate entity heterogeneous device, and sort the candidate entity heterogeneous devices in the candidate entity heterogeneous device list in descending order of standard deviation, and determine the top three candidate entity heterogeneous devices as target entity heterogeneous devices to obtain a target entity heterogeneous device list. If the standard deviations of multiple candidate entity heterogeneous devices at the top are the same, and the number of the multiple candidate entity heterogeneous devices is greater than 3, then any three candidate entity heterogeneous devices can be selected from the multiple candidate entity heterogeneous devices to be determined as target entity heterogeneous devices to obtain a target entity heterogeneous device list. If the working status of each candidate entity heterogeneous device in the candidate entity heterogeneous device list in the past 7 days is running, you can select any 3 candidate entity heterogeneous devices from the candidate entity heterogeneous device list to determine them as target entity heterogeneous devices, and obtain a target entity heterogeneous device list. The resource profiling center can output the target entity heterogeneous device list to the business allocation program. The business allocation program allocates the business to be executed to the target entity heterogeneous device list for execution. For example, assuming that the target entity heterogeneous device list includes target entity heterogeneous devices D11, D15 and D50, then the business allocation program allocates the business to be executed to the target entity heterogeneous devices D11, D15 and D50 for execution.

[0186] In an optional embodiment, the working status of each entity heterogeneous device, such as the running status or the failed status, can be reported to the resource portrait center at regular intervals, such as every 10 minutes. After the resource portrait center receives the candidate entity heterogeneous device list, the resource portrait center can determine the number of times each candidate entity heterogeneous device reported the failed status in the past 7 days; sort the candidate entity heterogeneous devices in the candidate entity heterogeneous device list in order from small to large times, and determine the top three candidate entity heterogeneous devices as the target entity heterogeneous devices to obtain the target entity heterogeneous device list. The resource portrait center can output the target entity heterogeneous device list to the business allocation program. The business allocation program allocates the to-be-executed business to the target entity heterogeneous device list for execution.

[0187] In a possible implementation manner, assume that the target entity heterogeneous device list L1 assigned to the to-be-executed service B1 includes entity heterogeneous devices D11, D15, and D50. If the user submits another to-be-executed service B2, and it is determined through the service allocation method provided by the embodiments of the present application that the target entity heterogeneous device list L2 assigned to the to-be-executed service B2 includes entity heterogeneous devices D13, D15, and D20, then the entity heterogeneous device D15 can be removed from the target entity heterogeneous device list L1 and added to the target entity heterogeneous device list L2. During the process of removing the entity heterogeneous device D15 from the target entity heterogeneous device list L1, if the entity heterogeneous device D15 is executing the to-be-executed service B1, it will not affect the normal execution of the to-be-executed service B1. After the calculation of the to-be-executed service B1 on the entity heterogeneous device D15 is completed, the entity heterogeneous device D15 will then execute the to-be-executed service B2 and no longer execute the to-be-executed service B1.

[0188] It can be understood that if the service requirement conditions of the to-be-executed service include anti-affinity service requirement conditions, then when the target entity heterogeneous device assigned to the to-be-executed service executes the to-be-executed service, the service allocation program can generate service requirement information for describing the anti-affinity service that the target entity heterogeneous device cannot execute this to-be-executed service. The service allocation program can obtain this service requirement information and associate this service requirement information with the virtual heterogeneous device corresponding to the target entity heterogeneous device. Subsequently, the entity heterogeneous devices assigned to the service newly submitted by the user can be screened according to this service requirement information. It can be understood that when the service newly submitted by the user is the anti-affinity service of the to-be-executed service, the entity heterogeneous devices screened and assigned to the service newly submitted by the user do not include this target entity heterogeneous device. When this to-be-executed service is completed, this service requirement information can also be deleted so that this target entity heterogeneous device can participate in the screening of the target entity heterogeneous devices for executing the anti-affinity service of the to-be-executed service submitted subsequently.

[0189] For example, assume that the business requirement conditions of the to-be-executed service B5 submitted by the user include anti-affinity business requirement conditions, and the anti-affinity business requirement conditions indicate that service B5 cannot be executed by the same entity heterogeneous device as services B6, B7, and B8. The target entity heterogeneous device includes entity heterogeneous device D11. Then, when the entity heterogeneous device D11 executes the to-be-executed service B5, service requirement information can be generated to describe that the entity heterogeneous device D11 cannot execute services B6, B7, and B8; the service requirement information can be obtained and associated with the virtual heterogeneous device D21 of the corresponding entity heterogeneous device D11. When the newly submitted service by the user is service B6, the selected entity heterogeneous device assigned to service B6 does not include the entity heterogeneous device D11. When the to-be-executed service is completed, the service requirement information can also be deleted so that the entity heterogeneous device D11 can participate in the screening of entity heterogeneous devices for executing services B7 and B8.

[0190] Since the association operation of directly associating device attribute information, service requirement information, and operation status information with entity heterogeneous devices may cause the risk of interruption of the services being executed on the entity heterogeneous devices, it is necessary to wait until the services being executed are completed before performing the association operation of associating the device attribute information, service requirement information, and operation status information with the entity heterogeneous devices. And allocating a target entity heterogeneous device for the service to be executed needs to wait until after associating the device attribute information, service requirement information, and operation status information with the entity heterogeneous devices, and then allocating a target entity heterogeneous device for the service to be executed according to the device attribute information, service requirement information, and operation status information, resulting in poor flexibility in service allocation. In the embodiment of the present application, device attribute information of the entity heterogeneous device in the physical attribute dimension is obtained from the entity heterogeneous device; service requirement information of the entity heterogeneous device in the service requirement dimension is obtained according to the historical service requirement conditions in the historical requirement conditions of the historical executed services; operation status information of the entity heterogeneous device in the operation status dimension is obtained according to the operation status of the entity heterogeneous device; a virtual heterogeneous device corresponding to the entity heterogeneous device is created, and the device attribute information, service requirement information, and operation status information are associated with the virtual heterogeneous device; a target entity heterogeneous device that matches the current requirement conditions of the service to be executed is determined according to the device attribute information, service requirement information, and operation status information associated with the virtual heterogeneous device, and the service to be executed is allocated to the target entity heterogeneous device for execution. The current requirement conditions include at least one of the current physical attribute requirement conditions, current service requirement conditions, and current operation status requirement conditions. Thus, by associating the device attribute information, service requirement information, and operation status information with the virtual heterogeneous device corresponding to the entity heterogeneous device, since this association operation does not directly act on the entity heterogeneous device and does not cause the risk of interruption of the services being executed on the entity heterogeneous device, there is no need to wait until the services being executed are completed before performing the association operation of associating the device attribute information, service requirement information, and operation status information with the virtual heterogeneous device corresponding to the entity heterogeneous device. Therefore, a target entity heterogeneous device can be allocated for the service to be executed in a timely manner according to the device attribute information, service requirement information, and operation status information associated with the virtual heterogeneous device, and the flexibility of service allocation is better.

[0191] Furthermore, in the business allocation method provided by the embodiments of the present application, by associating the operation state information used to describe the abnormal state of the corresponding entity heterogeneous device with the virtual heterogeneous device corresponding to the entity heterogeneous device at the virtual scheduling layer, the annotation of device exceptions can be realized at the virtual scheduling layer. This can avoid interfering with the relocation operation due to the inability to annotate device exceptions at the physical resource layer when relocating entity heterogeneous devices due to entity heterogeneous device exceptions, etc., thereby improving the processing efficiency of entity heterogeneous devices with exceptions and indirectly reducing the waste of the time cost of the available time of entity heterogeneous devices. Moreover, abstracting the relocation scheduling function of entity heterogeneous devices facilitates the environmental deployment and shelving of entity heterogeneous devices at the physical resource layer. During the shelving process, there is no need to couple the functional requirements of the business, which improves the convenience of unified resource operation.

[0192] Please refer to Figure 3 , Figure 3 which is a schematic structural diagram of the business allocation device provided by the embodiments of the present application. The business allocation device includes: a first information acquisition module 301, a second information acquisition module 302, a third information acquisition module 303, an information association module 304, and a business allocation module 305.

[0193] The first information acquisition module 301 is used to acquire the device attribute information of the entity heterogeneous device in the physical attribute dimension from the entity heterogeneous device;

[0194] The second information acquisition module 302 is used to acquire the business requirement information of the entity heterogeneous device in the business requirement dimension according to the historical business requirement conditions in the historical requirement conditions of the historical executed business;

[0195] The third information acquisition module 303 is used to acquire the operation state information of the entity heterogeneous device in the operation state dimension according to the operation state of the entity heterogeneous device;

[0196] The information association module 304 is used to create a virtual heterogeneous device corresponding to the entity heterogeneous device, and associate the device attribute information, the business requirement information, and the operation state information with the virtual heterogeneous device;

[0197] The business allocation module 305 is used to determine a target entity heterogeneous device that matches the current requirement conditions of the to-be-executed business according to the device attribute information, the business requirement information, and the operation state information associated with the virtual heterogeneous device, and allocate the to-be-executed business to the target entity heterogeneous device for execution, where the current requirement conditions include at least one of the current physical attribute requirement conditions, the current business requirement conditions, and the current operation state requirement conditions.

[0198] Optionally, the business allocation module 305 is specifically used to execute:

[0199] Determine candidate entity heterogeneous devices that match the current requirement conditions of the business to be executed according to the device attribute information, service requirement information, and operation status information associated with the virtual heterogeneous device;

[0200] Obtain the historical stability information of the candidate entity heterogeneous device, where the historical stability information is used to characterize the stability of the candidate entity heterogeneous device within a historical time period;

[0201] Screen the target entity heterogeneous device from the candidate entity heterogeneous devices according to the historical stability information.

[0202] Optionally, the service allocation module 305 is specifically configured to execute:

[0203] Obtain the device requirement quantity of the business to be executed;

[0204] Screen the target entity heterogeneous device of the device requirement quantity from the candidate entity heterogeneous devices according to the historical stability information.

[0205] Optionally, the entity heterogeneous device includes entity heterogeneous devices of different categories, and the third information acquisition module 303 is specifically configured to execute:

[0206] If the operation status of the entity heterogeneous device is a category conversion status, obtain the operation status information for describing the target category after the category conversion of the entity heterogeneous device.

[0207] Optionally, the entity heterogeneous devices of different categories include entity heterogeneous devices of the first category and entity heterogeneous devices of the second category, and the third information acquisition module 303 is specifically configured to execute:

[0208] Obtain the total utilization rate of the entity heterogeneous devices of the first category to obtain the first utilization rate;

[0209] If the first utilization rate is less than the first utilization rate threshold, determine the operation status of at least one idle entity heterogeneous device in the entity heterogeneous devices of the first category as the category conversion status, and determine the second category as the target category.

[0210] Optionally, the third information acquisition module 303 is specifically configured to execute:

[0211] Obtain the total utilization rate of the entity heterogeneous devices of the second category to obtain the second utilization rate;

[0212] If the first utilization rate is less than the first utilization rate threshold, then determining the operation status of at least one idle entity heterogeneous device in the entity heterogeneous devices of the first category as the category conversion status includes:

[0213] If the first utilization rate is less than the first utilization rate threshold and the second utilization rate is greater than the second utilization rate threshold, determine the operation status of at least one idle entity heterogeneous device in the first category of entity heterogeneous devices as the category conversion status.

[0214] Optionally, the third information acquisition module 303 is specifically configured to execute:

[0215] If the operation status of the entity heterogeneous device is an abnormal operation status, acquire operation status information used to describe the abnormality of the entity heterogeneous device.

[0216] Optionally, the second information acquisition module 302 is specifically configured to execute:

[0217] If the historical service requirement condition includes a device health requirement condition, acquire service requirement information used to describe the health of the entity heterogeneous device, where the device health requirement condition is used to specify the minimum health that the entity heterogeneous device executing the historical executed service needs to reach.

[0218] Optionally, the second information acquisition module 302 is specifically configured to execute:

[0219] If the historical service requirement condition includes an anti-affinity service requirement condition, generate the service requirement information when the execution entity heterogeneous device assigned to execute the historical service executes the historical service, where the anti-affinity service requirement condition is used to specify an anti-affinity service that cannot be executed by the same entity heterogeneous device as the historical service at the same time, and the service requirement information is used to describe that the execution entity heterogeneous device cannot execute the anti-affinity service.

[0220] Optionally, the information association module 304 is specifically configured to execute:

[0221] Acquire service requirement update information of the entity heterogeneous device in the service requirement dimension according to the current service requirement condition in the current requirement condition;

[0222] Update the service requirement information associated with the virtual heterogeneous device according to the service requirement update information.

[0223] In the embodiment of the present application, the first information acquisition module 301 acquires device attribute information of the entity heterogeneous device in the physical attribute dimension from the entity heterogeneous device; the second information acquisition module 302 acquires service requirement information of the entity heterogeneous device in the service requirement dimension according to the historical service requirement conditions in the historical requirement conditions of the historical executed service; the third information acquisition module 303 acquires operation state information of the entity heterogeneous device in the operation state dimension according to the operation state of the entity heterogeneous device; the information association module 304 creates a virtual heterogeneous device corresponding to the entity heterogeneous device, and associates the device attribute information, the service requirement information, and the operation state information with the virtual heterogeneous device; the service allocation module 305 determines a target entity heterogeneous device that matches the current requirement conditions of the service to be executed according to the device attribute information, the service requirement information, and the operation state information associated with the virtual heterogeneous device, and allocates the service to be executed to the target entity heterogeneous device for execution. The current requirement conditions include at least one of a current physical attribute requirement condition, a current service requirement condition, and a current operation state requirement condition. Thus, when performing service allocation, the entity heterogeneous device for the service to be executed is allocated according to the device attribute information, the service requirement information, and the operation state information associated with the virtual heterogeneous device corresponding to the entity heterogeneous device, which will not affect the entity heterogeneous device executing the service, and thus there is no risk that the service being executed by the entity heterogeneous device will be interrupted. Therefore, there is no need to wait for the service to be completed before performing service allocation, and the flexibility of service allocation is relatively good.

[0224] The embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed on a computer, the computer is caused to execute the service allocation method provided in this embodiment.

[0225] The embodiment of the present application further provides a computer device, including a memory and a processor. The processor is configured to execute the service allocation method provided in this embodiment by calling the computer program stored in the memory.

[0226] In addition, the embodiment of the present application further provides a computer device, which may be a device such as a terminal or a server. As Figure 4 shown, it shows a schematic structural diagram of the computer device involved in the embodiment of the present application. Specifically:

[0227] The computer device may include a processor 401 with one or more processing cores, a memory 402 with one or more storage media, a power supply 403, an input unit 404, and other components. Those skilled in the art can understand that Figure 4 the structural diagram of the computer device shown in

[0228] Wherein:

[0229] The processor 401 is the control center of the computer device, connecting various parts of the entire computer device through various interfaces and circuits. By running or executing software programs and / or modules stored in the memory 402, and by invoking the data stored in the memory 402, it executes various functions of the computer device and processes data, thereby exercising overall control over the computer device. Optionally, the processor 401 may include one or more processing cores; preferably, the processor 401 may integrate an application processor and a modem processor. Among them, the application processor mainly processes the operating system, user interface, application programs, etc., and the modem processor mainly processes wireless communications. It can be understood that the above-mentioned modem processor may not be integrated into the processor 401 either.

[0230] The memory 402 can be used to store software programs and modules. The processor 401 executes various functional applications and data processing by running the software programs and modules stored in the memory 402. The memory 402 mainly includes a program storage area and a data storage area. Among them, the program storage area can store the operating system, application programs required for at least one function (such as the sound playback function, image playback function, etc.); the data storage area can store data created according to the use of the computer device. In addition, the memory 402 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices. Correspondingly, the memory 402 may also include a memory controller to provide the processor 401 with access to the memory 402.

[0231] The computer device further includes a power supply 403 for supplying power to each component. Preferably, the power supply 403 can be logically connected to the processor 401 through a power management system, thereby implementing functions such as management of charging, discharging, and power consumption management through the power management system. The power supply 403 may also include any components such as one or more DC or AC power supplies, a recharge system, a power failure detection circuit, a power converter or inverter, and a power status indicator.

[0232] The computer device may further include an input unit 404, which can be used to receive input digital or character information, and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.

[0233] Although not shown, the computer device may further include a display unit and the like, which will not be elaborated here. Specifically, in this embodiment, the processor 401 in the computer device will load the executable files corresponding to the processes of one or more application programs into the memory 402 according to the following instructions, and the processor 401 will run the application programs stored in the memory 402 to implement various functions as follows:

[0234] Obtain the device attribute information of the entity heterogeneous device in the physical attribute dimension from the entity heterogeneous device;

[0235] Obtain the business requirement information of the entity heterogeneous device in the business requirement dimension according to the historical business requirement conditions in the historical requirement conditions of the executed business;

[0236] Obtain the operation status information of the entity heterogeneous device in the operation status dimension according to the operation status of the entity heterogeneous device;

[0237] Create a virtual heterogeneous device corresponding to the entity heterogeneous device, and associate the device attribute information, the business requirement information, and the operation status information with the virtual heterogeneous device;

[0238] According to the device attribute information, business requirement information, and operation status information associated with the virtual heterogeneous device, determine the target entity heterogeneous device that matches the current requirement conditions of the business to be executed, and allocate the business to be executed to the target entity heterogeneous device for execution. The current requirement conditions include at least one of the current physical attribute requirement conditions, current business requirement conditions, and current operation status requirement conditions.

[0239] Optionally, the determining the target entity heterogeneous device that matches the current requirement conditions of the business to be executed according to the device attribute information, business requirement information, and operation status information associated with the virtual heterogeneous device includes:

[0240] Determine the candidate entity heterogeneous device that matches the current requirement conditions of the business to be executed according to the device attribute information, business requirement information, and operation status information associated with the virtual heterogeneous device;

[0241] Obtain the historical stability information of the candidate entity heterogeneous device, where the historical stability information is used to characterize the stability of the candidate entity heterogeneous device within the historical duration;

[0242] Screen the target entity heterogeneous device from the candidate entity heterogeneous devices according to the historical stability information.

[0243] Optionally, the screening the target entity heterogeneous device from the candidate entity heterogeneous devices according to the historical stability information includes:

[0244] Obtain the device requirement quantity of the business to be executed;

[0245] Based on the historical stability information, the target entity heterogeneous devices with the required quantity of devices are screened from the candidate entity heterogeneous devices.

[0246] Optionally, the entity heterogeneous devices include entity heterogeneous devices of different categories. According to the operating status of the entity heterogeneous devices, the operating status information of the entity heterogeneous devices in the dimension of the operating status is obtained, including:

[0247] If the operating status of the entity heterogeneous device is a category conversion status, the operating status information for describing the target category after the category conversion of the entity heterogeneous device is obtained.

[0248] Optionally, the entity heterogeneous devices of different categories include entity heterogeneous devices of the first category and entity heterogeneous devices of the second category. Before obtaining the operating status information for describing the target category after the category conversion of the entity heterogeneous device if the operating status of the entity heterogeneous device is a category conversion status, it further includes:

[0249] Obtain the total utilization rate of the entity heterogeneous devices of the first category to obtain the first utilization rate;

[0250] If the first utilization rate is less than the first utilization rate threshold, determine the operating status of at least one idle entity heterogeneous device in the entity heterogeneous devices of the first category as the category conversion status, and determine the second category as the target category.

[0251] Optionally, before determining the operating status of at least one idle entity heterogeneous device in the entity heterogeneous devices of the first category as the category conversion status if the first utilization rate is less than the first utilization rate threshold, it further includes:

[0252] Obtain the total utilization rate of the entity heterogeneous devices of the second category to obtain the second utilization rate;

[0253] Determining the operating status of at least one idle entity heterogeneous device in the entity heterogeneous devices of the first category as the category conversion status if the first utilization rate is less than the first utilization rate threshold includes:

[0254] If the first utilization rate is less than the first utilization rate threshold and the second utilization rate is greater than the second utilization rate threshold, determine the operating status of at least one idle entity heterogeneous device in the entity heterogeneous devices of the first category as the category conversion status.

[0255] Optionally, obtaining the operating status information of the entity heterogeneous device in the dimension of the operating status according to the operating status of the entity heterogeneous device includes:

[0256] If the operating state of the entity heterogeneous device is an abnormal operating state, obtain the operating state information used to describe the abnormality of the entity heterogeneous device.

[0257] Optionally, according to the historical business requirement conditions in the historical requirement conditions of the historical executed service, obtain the business requirement information of the entity heterogeneous device in the dimension of business requirements, including:

[0258] If the historical business requirement conditions include device health requirement conditions, obtain the business requirement information used to describe the health of the entity heterogeneous device, and the device health requirement conditions are used to specify the minimum health that the entity heterogeneous device executing the historical executed service needs to reach.

[0259] Optionally, according to the historical business requirement conditions in the historical requirement conditions of the historical executed service, obtain the business requirement information of the entity heterogeneous device in the dimension of business requirements, including:

[0260] If the historical business requirement conditions include anti-affinity business requirement conditions, when the execution entity heterogeneous device assigned to the historical executed service executes the historical executed service, generate the business requirement information, and the anti-affinity business requirement conditions are used to specify the anti-affinity services that cannot be executed by the same entity heterogeneous device as the historical executed service at the same time, and the business requirement information is used to describe that the execution entity heterogeneous device cannot execute the anti-affinity services.

[0261] Optionally, before determining the target virtual heterogeneous device that matches the current requirement conditions of the service to be executed according to the device attribute information, business requirement information, and operating state information associated with the virtual heterogeneous device, further include:

[0262] According to the current business requirement conditions in the current requirement conditions, obtain the business requirement update information of the entity heterogeneous device in the dimension of business requirements;

[0263] Update the business requirement information associated with the virtual heterogeneous device according to the business requirement update information.

[0264] Those of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructions or by controlling related hardware through instructions. The instructions can be stored in a storage medium and loaded and executed by a processor.

[0265] For this reason, an embodiment of the present application provides a storage medium, in which multiple instructions are stored, and the instructions can be loaded by a processor to execute the steps in any one of the service allocation methods provided by the embodiments of the present application. For example, the instructions can execute the following steps:

[0266] Device attribute information of the entity heterogeneous device in the physical attribute dimension is obtained from the entity heterogeneous device;

[0267] According to the historical business requirement conditions in the historical requirement conditions of the historical executed business, business requirement information of the entity heterogeneous device in the business requirement dimension is obtained;

[0268] According to the operation status of the entity heterogeneous device, operation status information of the entity heterogeneous device in the operation status dimension is obtained;

[0269] A virtual heterogeneous device corresponding to the entity heterogeneous device is created, and the device attribute information, the business requirement information, and the operation status information are associated with the virtual heterogeneous device;

[0270] According to the device attribute information, business requirement information, and operation status information associated with the virtual heterogeneous device, a target entity heterogeneous device that matches the current requirement conditions of the business to be executed is determined, and the business to be executed is assigned to the target entity heterogeneous device for execution. The current requirement conditions include at least one of the current physical attribute requirement conditions, the current business requirement conditions, and the current operation status requirement conditions.

[0271] Wherein, the storage medium may include: read-only memory (ROM, Read Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disc, etc.

[0272] Since the instructions stored in the storage medium can execute the steps in any of the service allocation methods provided in the embodiments of the present application, the beneficial effects that can be achieved by any of the service allocation methods provided in the embodiments of the present application can be realized. For details, see the previous embodiments and will not be elaborated here.

[0273] Wherein, according to one aspect of the present application, a computer program product or a computer program is provided. The computer program product or the computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the service allocation method provided in the above-mentioned invention content and embodiments.

[0274] The above has introduced in detail a service allocation method, device, product, storage medium, and equipment provided by an embodiment of the present application. Specific examples are used herein to elaborate on the principle and implementation manner of the present application. The description of the above embodiments is only used to help understand the method and its core idea of the present application; at the same time, for those skilled in the art, according to the idea of the present application, there will be changes in the specific implementation manner and application scope. In summary, the content of this specification should not be construed as a limitation on the present application.

Claims

1. A service allocation method, characterized in that: include: Acquire device attribute information of the physical heterogeneous device in a physical attribute dimension from the physical heterogeneous device; According to the historical business requirement conditions in the historical requirement conditions of the historical execution business, business requirement information of the entity heterogeneous device in the business requirement dimension is obtained, including: if the historical business requirement conditions include anti-affinity business requirement conditions, when the execution entity heterogeneous device assigned to the historical execution business executes the historical execution business, the business requirement information is generated, the anti-affinity business requirement conditions are used to specify the anti-affinity business that cannot be executed by the same entity heterogeneous device at the same time as the historical execution business, and the business requirement information is used to describe that the execution entity heterogeneous device cannot execute the anti-affinity business; According to the operation status of the physical heterogeneous device, obtaining the operation status information of the physical heterogeneous device in the operation status dimension; Creating a virtual heterogeneous device corresponding to the physical heterogeneous device, and associating the device attribute information, the business requirement information, and the operation status information with the virtual heterogeneous device; According to the device attribute information, business requirement information and operation status information associated with the virtual heterogeneous device, determine the target physical heterogeneous device that matches the current requirement conditions of the business to be executed, and allocate the business to be executed to the target physical heterogeneous device for execution. The current requirement conditions include at least one of the current physical attribute requirement conditions, the current business requirement conditions and the current operation status requirement conditions.

2. The service allocation method according to claim 1, characterized in that: The step of determining a target physical heterogeneous device that matches the current demand conditions of the service to be executed according to the device attribute information, service demand information, and operation status information associated with the virtual heterogeneous device includes: Determine, based on device attribute information, business requirement information, and operation status information associated with the virtual heterogeneous device, a candidate physical heterogeneous device that matches the current requirement conditions of the business to be executed; Acquire historical stability information of the candidate entity heterogeneous device, where the historical stability information is used to characterize the stability of the candidate entity heterogeneous device over a historical period of time; A target physical heterogeneous device is screened from the candidate physical heterogeneous devices according to the historical stability information.

3. The service allocation method according to claim 2, characterized in that: The step of screening a target entity heterogeneous device from the candidate entity heterogeneous devices according to the historical stability information includes: Obtain the number of equipment required for the business to be executed; According to the historical stability information, target physical heterogeneous devices having the required number of devices are screened from the candidate physical heterogeneous devices.

4. The service allocation method according to any one of claims 1 to 3, characterized in that: The physical heterogeneous devices include physical heterogeneous devices of different categories, and obtaining the operation status information of the physical heterogeneous devices in the operation status dimension according to the operation status of the physical heterogeneous devices includes: If the operation state of the physical heterogeneous device is a category conversion state, then operation state information for describing a target category after the category conversion of the physical heterogeneous device is obtained.

5. The service allocation method according to claim 4, characterized in that: The different categories of physical heterogeneous devices include physical heterogeneous devices of a first category and physical heterogeneous devices of a second category. If the operation state of the physical heterogeneous device is a category conversion state, before obtaining the operation state information of the target category after the category conversion of the physical heterogeneous device, it also includes: Obtaining a total utilization rate of the physical heterogeneous devices of the first category to obtain a first utilization rate; If the first utilization is less than a first utilization threshold, the operating state of at least one idle physical heterogeneous device in the first category of physical heterogeneous devices is determined as a category conversion state, and the second category is determined as the target category.

6. The service allocation method according to claim 5, characterized in that: If the first utilization rate is less than a first utilization rate threshold, before determining the operation state of at least one idle physical heterogeneous device in the first category of physical heterogeneous devices as a category conversion state, the method further includes: Obtaining a total utilization rate of the physical heterogeneous devices of the second category to obtain a second utilization rate; If the first utilization rate is less than a first utilization rate threshold, determining the operation state of at least one idle physical heterogeneous device in the first category of physical heterogeneous devices as a category conversion state includes: If the first utilization is less than a first utilization threshold and the second utilization is greater than a second utilization threshold, the operation state of at least one idle physical heterogeneous device in the first category of physical heterogeneous devices is determined as a category conversion state.

7. The service allocation method according to any one of claims 1 to 3, characterized in that: The obtaining, according to the operation status of the physical heterogeneous device, the operation status information of the physical heterogeneous device in the operation status dimension includes: If the operation state of the physical heterogeneous device is an abnormal operation state, operation state information for describing that the physical heterogeneous device has an abnormality is obtained.

8. The service allocation method according to any one of claims 1 to 3, characterized in that: The acquiring, according to the historical business requirement conditions in the historical requirement conditions for historically executing the business, the business requirement information of the entity heterogeneous device in the business requirement dimension includes: If the historical service requirement conditions include device health requirement conditions, then business requirement information for describing the health of the physical heterogeneous devices is obtained, and the device health requirement conditions are used to specify the minimum health that the physical heterogeneous devices that execute the historical execution services must achieve.

9. The service allocation method according to claim 1, characterized in that: Before determining the target virtual heterogeneous device matching the current demand conditions of the to-be-executed service according to the device attribute information, service demand information and operation status information associated with the virtual heterogeneous device, the method further includes: According to the current business demand condition in the current demand condition, obtaining business demand update information of the physical heterogeneous device in the business demand dimension; The business requirement information associated with the virtual heterogeneous device is updated according to the business requirement update information.

10. A service distribution device, characterized in that: include: A first information acquisition module is used to acquire device attribute information of the physical heterogeneous device in a physical attribute dimension from the physical heterogeneous device; A second information acquisition module is used to acquire business demand information of the entity heterogeneous device in a business demand dimension according to a historical business demand condition in a historical demand condition of a historically executed business, including: if the historical business demand condition includes an anti-affinity business demand condition, then when the execution entity heterogeneous device assigned to the historically executed business executes the historically executed business, the business demand information is generated, the anti-affinity business demand condition is used to specify an anti-affinity business that cannot be executed by the same entity heterogeneous device at the same time as the historically executed business, and the business demand information is used to describe that the execution entity heterogeneous device cannot execute the anti-affinity business; A third information acquisition module is used to acquire the operation status information of the physical heterogeneous device in the operation status dimension according to the operation status of the physical heterogeneous device; An information association module, used to create a virtual heterogeneous device corresponding to the physical heterogeneous device, and associate the device attribute information, the business requirement information and the operation status information with the virtual heterogeneous device; A service allocation module is used to determine a target physical heterogeneous device that matches the current demand conditions of the service to be executed based on the device attribute information, service demand information and operation status information associated with the virtual heterogeneous device, and allocate the service to be executed to the target physical heterogeneous device for execution, wherein the current demand conditions include at least one of the current physical attribute demand conditions, the current service demand conditions and the current operation status demand conditions.

11. A computer program product comprising a computer program or instructions, characterized in that When the computer program or instruction is executed by a processor, the service allocation method according to any one of claims 1 to 9 is implemented.

12. A computer-readable storage medium, characterized in that: The computer-readable storage medium is used to store a computer program, and the computer program is loaded by a processor to execute the service allocation method according to any one of claims 1 to 9.

13. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that: When the processor executes the computer program, the service allocation method according to any one of claims 1 to 9 is implemented.

Images