Server allocation method and device based on resource pool and electronic equipment

Abstract

The embodiment of the invention provides a server allocation method and device based on a resource pool and electronic equipment. The method comprises the following steps: in response to a server allocation request sent by a user side, determining a resource pool instance matched with the server allocation request from at least one resource pool instance according to first target requirement information in the server allocation request; wherein the server allocation request characterizes that a server is called by a user side, and a GRU matched with the server allocation request is determined from a resource pool instance matched with the server allocation request according to second target requirement information in the server allocation request; determining a server matched with the server distribution request from the GRU matched with the server distribution request according to third target requirement information in the server distribution request; and calling the determined server to carry out business processing service for the user side. The method is used for achieving the effect of efficiently and accurately distributing the servers.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a server allocation method, apparatus, and electronic device based on a resource pool. Background Technology

[0002] In a bank's big data center, servers are the key infrastructure supporting core business operations, and their allocation directly affects the operational efficiency of the bank's big data center.

[0003] In existing technology, staff manually search for servers that meet the requirements, confirm their availability, and then send the server's IP address to the user's client, who then connects and uses the server. This manual allocation method is inefficient, prone to human error, and cannot meet the bank's growing business needs and efficient server management.

[0004] Therefore, there is an urgent need for a solution that can efficiently and accurately allocate servers. Summary of the Invention

[0005] This application provides a server allocation method, apparatus, and electronic device based on a resource pool, which can achieve the effect of efficiently and accurately allocating servers.

[0006] In a first aspect, embodiments of this application provide a server allocation method based on a resource pool, wherein the resource pool includes at least one resource pool instance, the resource pool instance includes at least one resource unit group (GRU), and the GRU includes at least one server; the method includes:

[0007] In response to a server allocation request sent by a user, a resource pool instance matching the server allocation request is determined from the at least one resource pool instance based on the first target requirement information in the server allocation request; wherein, the server allocation request represents a request for the user to retrieve a server, and the server allocation request includes: the first target requirement information of the resource pool instance, the second target requirement information of the GRU, and the third target requirement information of the server;

[0008] Based on the second target requirement information in the server allocation request, determine the GRU that matches the server allocation request from the resource pool instances that match the server allocation request;

[0009] Based on the third target requirement information in the server allocation request, determine the server that matches the server allocation request from the GRUs that match the server allocation request;

[0010] The identified server is invoked to provide business processing services to the user terminal.

[0011] In one possible implementation, the first target requirement information includes server usage scenario information, data center location, and server configuration information; based on the first target requirement information in the server allocation request, determining a resource pool instance matching the server allocation request from the at least one resource pool instance includes:

[0012] Based on the first target requirement information in the server allocation request, a resource pool instance that meets the first target requirement information is determined from the at least one resource pool instance, and is the resource pool instance that matches the server allocation request.

[0013] In one possible implementation, the second target requirement information includes CPU architecture information, node type, and server quantity information; the node type indicates the type of server.

[0014] Based on the second target requirement information in the server allocation request, determine the GRU that matches the server allocation request from the resource pool instances that match the server allocation request, including:

[0015] Based on the CPU architecture information and node type in the second target requirement information, an initial number of GRUs are determined from the resource pool instances that match the server allocation request.

[0016] Based on the server quantity information in the second target requirement information, determine the GRU that matches the server quantity information from the initial multiple GRUs, and use it as the GRU that matches the server allocation request;

[0017] If the number of servers in the initial multiple GRUs does not meet the number of servers in the second target requirement information, then the initial multiple GRUs are expanded.

[0018] In one possible implementation, the third target requirement information includes the server network area and the server Internet Protocol (IP) address; based on the third target requirement information in the server allocation request, determining the server matching the server allocation request from the GRUs that match the server allocation request includes:

[0019] Based on the server network area and server IP address in the third target requirement information, a server matching the server IP address is determined from the GRUs that match the server allocation request.

[0020] In one possible implementation, based on the server network area and server IP address in the third target requirement information, servers matching the Internet Protocol IP address are determined from the GRUs that match the server allocation request. The process for identifying servers matching the server allocation request includes:

[0021] Based on the server network region in the third target requirement information, multiple initial servers matching the server network region are determined from the GRUs that match the server allocation request; if the server network region in the GRU does not meet the server network region in the third target requirement information, the GRU is expanded.

[0022] Based on the server IP address in the third target requirement information, a server matching the server IP address is determined from the initial plurality of servers, and is the server that matches the server allocation request; if the server network area in the initial plurality of servers does not meet the server network area in the third target requirement information, then the GRU is expanded.

[0023] In one possible implementation, the method further includes:

[0024] Based on the first target requirement information of the resource pool instance, the second target requirement information of the GRU, and the third target requirement information of the server in the server allocation request, a filtering process is performed on the resource pool instances that have not been connected to the resource pool to obtain a set of GRUs to be connected to the resource pool; and the servers in the set of GRUs to be connected to the resource pool are sorted according to the server's entry time to obtain a sorted set of GRUs to be connected to the resource pool; wherein, the entry time represents the time when the server enters the resource pool instance; the set of GRU sequences to be connected to the resource pool represents the set of servers in the set of GRUs to be connected to the resource pool arranged in order of entry time from earliest to latest;

[0025] From the top m servers in the sorted GRU set of the resource pool to be accessed, determine the servers to be accessed; where m is a positive integer greater than or equal to 1.

[0026] Connect the server to be connected to the GRU.

[0027] Secondly, embodiments of this application provide a server allocation apparatus based on a resource pool, wherein the resource pool includes at least one resource pool instance, the resource pool instance includes at least one resource unit group (GRU), and the GRU includes at least one server; the apparatus includes:

[0028] The first matching module is used to respond to a server allocation request sent by the user terminal, and determine a resource pool instance that matches the server allocation request from the at least one resource pool instance according to the first target requirement information in the server allocation request; wherein, the server allocation request represents a request for the user terminal to call the server, and the server allocation request includes: the first target requirement information of the resource pool instance, the second target requirement information of the GRU, and the third target requirement information of the server;

[0029] The second matching module is used to determine the GRU that matches the server allocation request from the resource pool instances that match the server allocation request, based on the second target requirement information in the server allocation request.

[0030] The third matching module is used to determine the server that matches the server allocation request from the GRUs that match the server allocation request, based on the third target requirement information in the server allocation request.

[0031] The retrieval module is used to retrieve the identified server to provide business processing services to the user terminal.

[0032] In one possible implementation, the first target requirement information includes server usage scenario information, data center location, and server configuration information; the first matching module includes:

[0033] Based on the first target requirement information in the server allocation request, a resource pool instance that meets the first target requirement information is determined from the at least one resource pool instance, and is the resource pool instance that matches the server allocation request.

[0034] In one possible implementation, the second target requirement information includes CPU architecture information, node type, and server quantity information; the node type indicates the type of server; the second matching module includes:

[0035] Based on the CPU architecture information and node type in the second target requirement information, an initial number of GRUs are determined from the resource pool instances that match the server allocation request.

[0036] Based on the server quantity information in the second target requirement information, determine the GRU that matches the server quantity information from the initial multiple GRUs, and use it as the GRU that matches the server allocation request;

[0037] If the number of servers in the initial multiple GRUs does not meet the number of servers in the second target requirement information, then the initial multiple GRUs are expanded.

[0038] In one possible implementation, the third target requirement information includes the server network area and the server Internet Protocol (IP) address; the third matching module includes:

[0039] Based on the server network area and server IP address in the third target requirement information, a server matching the server IP address is determined from the GRUs that match the server allocation request.

[0040] In one possible implementation, based on the server network area and server IP address in the third target requirement information, servers matching the Internet Protocol IP address are determined from the GRUs that match the server allocation request. The process for identifying servers matching the server allocation request includes:

[0041] Based on the server network region in the third target requirement information, multiple initial servers matching the server network region are determined from the GRUs that match the server allocation request; if the server network region in the GRU does not meet the server network region in the third target requirement information, the GRU is expanded.

[0042] Based on the server IP address in the third target requirement information, a server matching the server IP address is determined from the initial plurality of servers, and is the server that matches the server allocation request; if the server network area in the initial plurality of servers does not meet the server network area in the third target requirement information, then the GRU is expanded.

[0043] In one possible implementation, the device further includes:

[0044] Based on the first target requirement information of the resource pool instance, the second target requirement information of the GRU, and the third target requirement information of the server in the server allocation request, a filtering process is performed on the resource pool instances that have not been connected to the resource pool to obtain a set of GRUs to be connected to the resource pool; and the servers in the set of GRUs to be connected to the resource pool are sorted according to the server's entry time to obtain a sorted set of GRUs to be connected to the resource pool; wherein, the entry time represents the time when the server enters the resource pool instance; the set of GRU sequences to be connected to the resource pool represents the set of servers in the set of GRUs to be connected to the resource pool arranged in order of entry time from earliest to latest;

[0045] From the top m servers in the sorted GRU set of the resource pool to be accessed, determine the servers to be accessed; where m is a positive integer greater than or equal to 1.

[0046] Connect the server to be connected to the GRU.

[0047] Thirdly, embodiments of this application provide an electronic device, including: a memory and a processor;

[0048] The memory stores computer-executed instructions;

[0049] The processor executes computer execution instructions stored in the memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above.

[0050] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect and / or various possible implementations of the first aspect.

[0051] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the first aspect and / or various possible implementations of the first aspect.

[0052] This application provides a server allocation method, apparatus, and electronic device based on a resource pool. In response to a server allocation request sent by a user, the method first accurately determines a matching resource pool instance from at least one resource pool instance based on the first target requirement information in the request. This resource pool instance serves as the basis for subsequent filtering. Next, based on the second target requirement information in the request, it further determines matching GRUs from the matched resource pool instances, gradually narrowing the filtering range. Finally, based on the third target requirement information in the request, it determines a matching server from the matched GRUs. This entire process, through hierarchical and progressively precise filtering, enables the user to quickly and accurately retrieve servers that meet their various requirements, effectively improving server allocation efficiency, reducing unnecessary time and resource waste during the allocation process, and thereby improving the response speed and quality of business processing services to meet the user's business processing needs. Attached Figure Description

[0053] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0054] Figure 1 A flowchart illustrating a server allocation method based on a resource pool provided in this application embodiment. Figure 1 ;

[0055] Figure 2 A flowchart illustrating a server allocation method based on a resource pool provided in this application embodiment. Figure 2 ;

[0056] Figure 3 A schematic diagram of a resource pool structure provided in this application embodiment. Figure 1 ;

[0057] Figure 4 A schematic diagram of a GRU structure provided in an embodiment of this application;

[0058] Figure 5 A schematic diagram of a resource pool structure provided in this application embodiment. Figure 2 ;

[0059] Figure 6 A schematic diagram of a server allocation device based on a resource pool provided in this application embodiment. Figure 1 ;

[0060] Figure 7 A schematic diagram of a server allocation device based on a resource pool provided in this application embodiment. Figure 2 ;

[0061] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0062] The accompanying drawings have illustrated specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to specific embodiments. Detailed Implementation

[0063] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0064] In the operation and management system of a bank's big data center, servers undoubtedly occupy a core position, serving as the infrastructure supporting the stable operation and efficient conduct of various key businesses. The rationality of their allocation directly affects the overall operational efficiency of the bank. A reasonable allocation ensures rapid response from business systems and efficient data processing, providing a solid guarantee for the bank's various financial services; conversely, it may lead to business processing delays, system lag, or even failures, causing significant economic losses and reputational damage to the bank.

[0065] Currently, server allocation in bank big data centers relies primarily on manual labor. Staff must manually search through massive amounts of resources to find available servers, a tedious and time-consuming process. Confirming availability requires complex checks and tests, further increasing time costs. Afterward, the server IP address must be manually sent to the client. This model has significant drawbacks: inefficiency is a major concern, manual operation is slow and unable to meet ever-increasing business demands, often leading to business launch delays and impacting business expansion and competitiveness. Furthermore, human error is prone to occur, such as misreading information during searches or entering incorrect numbers when sending IP addresses. These small errors can have serious consequences, affecting business operations and even causing data loss or system crashes. With the development and innovation of banking services, the requirements for server allocation efficiency and accuracy are increasing, and the existing methods are no longer sufficient.

[0066] Therefore, this application provides a server allocation method, apparatus, and electronic device based on resource pools, which can solve the above-mentioned problems.

[0067] The following specific embodiments describe in detail the technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0068] Figure 1 A flowchart illustrating a server allocation method based on a resource pool provided in this application embodiment. Figure 1 ,like Figure 1 As shown, a resource pool contains at least one resource pool instance, and each resource pool instance includes at least one resource unit group (GRU), and each GRU includes at least one server. The method includes:

[0069] S101. In response to a server allocation request sent by the user, determine a resource pool instance that matches the server allocation request from at least one resource pool instance based on the first target requirement information in the server allocation request; wherein, the server allocation request represents a request for the user to call the server, and the server allocation request includes: the first target requirement information of the resource pool instance, the second target requirement information of the GRU, and the third target requirement information of the server.

[0070] For example, a resource pool includes at least one resource pool instance, and each resource pool instance includes at least one Resource Unit Group (GRU), and each GRU includes at least one server. The resource pool is the foundation of the entire architecture, containing at least one resource pool instance. A resource pool can be viewed as a logical collection used to manage and allocate server resources to meet the needs of different clients. Each resource pool instance is a specific implementation unit within the resource pool, containing at least one Resource Unit Group (GRU). Resource pool instances can be divided and configured based on different business needs, geographical location, security policies, and other factors. A GRU is the basic resource organization unit within a resource pool instance, and each GRU consists of three independent Resource Units (RUs). An RU can be understood as a specific server resource, such as a physical server or a virtual server instance. A server is the hardware or software entity that actually provides computing, storage, and networking services, and is the final resource carrier in the resource pool.

[0071] For example, a user client sends a server allocation request to the resource pool management system based on its own business needs. The server allocation request includes: first target requirement information for the resource pool instance, second target requirement information for the GRU, and third target requirement information for the server. This request indicates that the user client needs to access server resources to run its application or service.

[0072] The primary requirement for resource pool instances is that users may have specific requirements regarding the geographical location, business domain, and security level of the resource pool instances. For example, users may want the resource pool instances to be located in a particular data center to meet data compliance requirements.

[0073] The second objective requirement for GRU is that users may have specific needs regarding the performance, configuration, and availability of GRU. For example, users may require the servers within the GRU to have high computing power or specific software environments.

[0074] The third target requirement information for the server: This is the detailed requirement for a specific server, including the server's operating system, memory size, disk capacity, network bandwidth, etc. For example, a user might require the server to run a Linux operating system and have at least 16GB of memory. For example, a resource pool instance is defined as a pre-allocated collection of server resources, which may be divided according to dimensions such as region, performance level, and tenant isolation.

[0075] After receiving a server allocation request, the resource pool management system first filters and matches at least one resource pool instance based on the primary target requirement information in the request. The system iterates through all resource pool instances, checking whether each instance meets the user's requirements. For example, if the user requires the resource pool instance to be located in data center A, the system will only consider resource pool instances located in data center A for subsequent matching.

[0076] S102. Based on the second target requirement information in the server allocation request, determine the GRU that matches the server allocation request from the resource pool instances that match the server allocation request.

[0077] For example, after identifying resource pool instances that match the first target requirement information, the system further filters out eligible GRUs from these matching resource pool instances based on the second target requirement information in the request. For instance, if the user requires that the servers in the GRU have high-performance GPUs, the system will search for GRUs containing servers with that feature in the matching resource pool instances.

[0078] S103. Based on the third target requirement information in the server allocation request, determine the server that matches the server allocation request from the GRUs that match the server allocation request.

[0079] For example, based on the third target requirement information in the request, the system selects a server that meets the criteria from the matching GRUs. The system checks whether the server corresponding to each RU meets the specific requirements of the user client, such as operating system, memory, and disk. When the system finds servers that completely match all the target requirements of the user client, it assigns these servers to the user client. At the same time, the system records the server allocation information, including allocation time, user client information, server configuration, etc., for subsequent management and monitoring.

[0080] S104. Retrieve the identified server to provide business processing services to the user.

[0081] For example, the resource pool management system feeds back the server allocation results to the user, informing the user of the detailed information of the allocated server, such as the server IP address and login credentials, so that the user can successfully connect to and use these server resources.

[0082] This application provides a server allocation method based on a resource pool. In response to a server allocation request sent by a user, the method first accurately determines a matching resource pool instance from at least one resource pool instance based on the first target requirement information in the request. This resource pool instance serves as the basis for subsequent filtering. Next, based on the second target requirement information in the request, matching GRUs are further determined from the matched resource pool instances, gradually narrowing the filtering range. Finally, based on the third target requirement information in the request, a matching server is determined from the matched GRUs. The entire process, through hierarchical and progressively precise filtering, enables the user to quickly and accurately retrieve a server that meets their various requirements, effectively improving server allocation efficiency, reducing unnecessary time and resource waste during the allocation process, and thereby improving the response speed and quality of business processing services to meet the business processing needs of the user.

[0083] Figure 2 A flowchart illustrating a server allocation method based on a resource pool provided in this application embodiment. Figure 2 ,like Figure 2 As shown, in this embodiment... Figure 1 Based on the embodiments, a server allocation method based on a resource pool is described in detail. The resource pool includes at least one resource pool instance, and each resource pool instance includes at least one resource unit group (GRU). Each GRU includes at least one server. The method includes:

[0084] S201. In response to a server allocation request sent by the user, the server allocation request indicates that the user requests the server, and the server allocation request includes: the first target requirement information of the resource pool instance, the second target requirement information of the GRU, and the third target requirement information of the server.

[0085] For example, this step can refer to step S101 above, and will not be repeated here.

[0086] S202. The first target requirement information includes server usage scenario information, data center location, and server configuration information; based on the first target requirement information in the server allocation request, determine the resource pool instance that meets the first target requirement information from at least one resource pool instance, which is the resource pool instance that matches the server allocation request.

[0087] For example, a resource pool instance is a pre-built and maintained set of allocable server resources. Each resource pool instance represents a specific, allocable server resource unit with specific attributes, such as supported use cases, location in the data center, and hardware configuration.

[0088] For example, server usage scenario information is extracted from the initial target requirement information. Different usage scenarios have different requirements for server performance, functionality, etc. For instance, in a big data analysis scenario, the server needs strong computing power and large-capacity storage; while in a web browsing scenario, the server's response speed and concurrency processing capabilities are more demanding. Based on the usage scenario requirements derived from the analysis, each instance in the resource pool is traversed to check whether the usage scenario supported by each instance matches the usage scenario in the request. Only resource pool instances that support the same or compatible usage scenarios can become candidate instances and enter the subsequent screening process.

[0089] For example, the user-specified data center location information is obtained from the first target requirement information. The selection of the data center location may be influenced by various factors, such as data transmission latency, network bandwidth, and compliance requirements. For instance, if the user's service is primarily geared towards specific users, selecting a specific data center can reduce network latency and improve user experience; if the user needs to meet data storage regulations in a specific region, a compliant data center location must be selected. Among the candidate resource pool instances already filtered by the usage scenario, the data center location of each instance is checked to ensure it matches the location specified in the request. Only resource pool instances with matching data center locations are retained in the candidate list for the next step of configuration information matching.

[0090] S203. The second target requirement information includes CPU architecture information, node type, and server quantity information; the node type indicates the type of server; based on the CPU architecture information and node type in the second target requirement information, an initial number of GRUs are determined from the resource pool instances that match the server allocation request; based on the server quantity information in the second target requirement information, GRUs that meet the server quantity information are determined from the initial number of GRUs, and these are the GRUs that match the server allocation request; if the server quantity information in the initial number of GRUs does not meet the server quantity information in the second target requirement information, then the initial number of GRUs are expanded.

[0091] For example, the second objective requires information including CPU architecture, node type, and number of servers. CPU architecture information specifies the type of central processing unit architecture used by the server, commonly x86 or ARM. Different CPU architectures differ in instruction sets, performance characteristics, and compatibility, making them suitable for different application scenarios and software environments. Node type provides different types of resource services in different application scenarios, indicating the type of server. For example, cloud scenarios include cloud management nodes, cloud computing nodes, cloud storage nodes, and cloud network nodes; on-premises scenarios include database nodes, big data nodes, and GPU nodes; and virtualization scenarios include management nodes, compute nodes, and network nodes. Different types of nodes have different focuses in hardware configuration and functionality to meet specific business needs. The number of servers specifies the number of servers to be included in the selected GRU, which is one of the key indicators for resource allocation.

[0092] For example, CPU architecture information and node type requirements are extracted from the second target requirement information. Clearly defining the user's desired CPU architecture type and required server node type helps narrow down the filtering scope and find GRUs that match specific hardware and functional characteristics. The resource pool instances previously identified as matching the server allocation request are then traversed. These resource pool instances are the result of filtering based on the first target requirement information (server usage scenario information, data center location, server configuration information), and have already preliminarily met some of the user's basic needs.

[0093] During the traversal, each resource pool instance's GRUs are examined to determine if their CPU architecture matches the CPU architecture information in the request, and if their node type meets the specified requirements. Only when both the CPU architecture and node type of a GRU meet the conditions is that GRU included in the initial set of multiple GRUs. This step ensures that the selected GRUs meet the user's core requirements in terms of hardware architecture and functional type.

[0094] For example, for the initial multiple GRUs obtained after filtering by CPU architecture and node type, the number of servers contained in each GRU is calculated. This step is to understand the distribution of the current filtering results in terms of the number of servers. The calculated number of servers for each GRU is compared with the number of servers in the second target requirement information. If the number of servers in a certain GRU is exactly equal to the number required in the request, then that GRU is directly identified as the GRU that matches the server allocation request.

[0095] If the number of servers in the initial multiple GRUs does not meet the number of servers required in the second objective requirement, that is, the number of servers in all GRUs is less than the number of requests, then these GRUs need to be expanded.

[0096] According to the preset expansion strategy, the required server resources are obtained from servers that have not yet joined the resource pool. After the expansion operation is completed, the expanded GRUs are verified to ensure that they not only meet the requirements in terms of the number of servers, but also still meet the second target requirements in terms of CPU architecture, node type, and other aspects. Only the verified GRUs can be finally determined as the GRUs that match the server allocation request.

[0097] S204. The third objective requirement information includes the server network area and the server Internet Protocol (IP) address. Based on the server network area and server IP address in the third objective requirement information, determine the server that matches the server IP address from the GRUs that match the server allocation request, and select the server that matches the server allocation request.

[0098] For example, clearly define the network zone where the business expects the server to be located. Different network zones have different network performance, security policies, and access permissions. Determine the specific identification method for the network zone, such as defining it through a specific network address range, network name, or data center number. Specify the required server IP address type, whether it is IPv4 or IPv6. Obtain the specific IP address requirements, which can be an exact IP address, an IP address range, or an IP address pattern that conforms to specific rules. For example, it may require an IP address within a specific subnet, or an IP address ending in a specific number.

[0099] For example, a list of all GRUs that match the server allocation request is retrieved from the resource management system or database. These GRUs were selected in the previous steps based on other objective requirements (such as the first and second objective requirements mentioned above) and have already met certain business needs.

[0100] For example, the network region information of each server in the GRU is checked sequentially. The network region where the server is located is compared with the server network region in the third target requirement information. If the server's network region exactly matches the requirement (e.g., the network address range is the same or it belongs to the same specified network region identifier), the server is kept in the candidate list; otherwise, the server is excluded from the current filtering process. After network region filtering, a candidate list containing only servers that meet the network region requirements is obtained. The servers in this list meet the basic business requirements in terms of geographical location or network topology.

[0101] For example, for each server remaining in the candidate list after network area filtering, its assigned IP address information is checked. If the third target requirement specifies an exact IP address, the server's IP address is directly compared with the required IP address. If they match exactly, the server meets the requirement. If the requirement is an IP address range, such as 192.168.1.0 / 24, it is necessary to determine whether the server's IP address is within that range. This can be determined by converting the IP address to binary form and then performing logical operations with the start address of the address range and the subnet mask. For IP address patterns that conform to specific rules, such as the last digit of the IP address being even, corresponding rule-based judgment logic needs to be written to check whether the server's IP address meets the requirements. After IP address filtering, servers that completely match the server network area and server IP address in the third target requirement information are identified from the candidate list. These servers are the ones that ultimately match the server allocation request.

[0102] Record the information of the servers that meet the requirements after filtering, including server ID, server type, network region, IP address, and other detailed information. This information will be used for subsequent server allocation and configuration operations. If no servers that meet the requirements are found during the filtering process, expansion will be carried out according to the preset expansion rules.

[0103] In one example, based on the server network area in the third target requirement information, multiple initial servers matching the server allocation request are determined from the GRUs. If the server network area in the GRU does not match the server network area in the third target requirement information, the GRU is expanded. Based on the server IP address in the third target requirement information, servers matching the server IP address are determined from the initial multiple servers to be the servers matching the server allocation request. If the server network area in the initial multiple servers does not match the server network area in the third target requirement information, the GRU is expanded.

[0104] For example, the network region of each server is compared with the server network region in the third target requirement information. If they match, the server is added to the initial list of multiple servers. If they do not match, the server is recorded as not meeting the network region requirements.

[0105] For example, check if any of the current GRUs have server network regions that do not meet the requirements. If none of the current GRUs match the server network region in the third target requirement information, then the GRUs are expanded. Expansion can be achieved by transferring servers that meet the network region requirements from other resource pools to the current GRU, or by creating new server instances and adding them to the GRU. If some of the current GRUs have server network regions that match the third target requirement information, meaning some GRUs contain servers that meet the network region requirements, then continue with the subsequent steps; expansion of all GRUs is not necessary.

[0106] For example, examine the IP address information of each server in the list sequentially. If the third target requirement specifies an exact IP address, directly compare the server's IP address with the required IP address. If they match exactly, the server meets the requirements. If the requirement is a range of IP addresses, such as 192.168.10.10-192.168.10.20, determine if the server's IP address falls within this range. This can be done by converting the IP address to an integer and comparing it with the start and end integers of the address range. For IP addresses that meet specific rules, such as an odd last digit, write corresponding rule-based logic to check if the server's IP address meets the requirements. Identify the server as the one matching the server allocation request. Record detailed server information, including server ID, GRU, network zone, and IP address, for subsequent server allocation and configuration operations.

[0107] For example, check if there are still servers in the initial list of multiple servers whose network regions do not meet the third objective requirement. This may be because, although expansion was performed during the previous filtering based on network region, some servers still do not meet the requirements, or the newly added servers after expansion also have network region issues.

[0108] If present: Expand the corresponding GRU again. The resource search scope can be further broadened to find servers that meet the network area requirements and add them to the GRU from a wider resource pool. For example, if servers have already been allocated from other data centers in the same city, but the requirements are still not met, consider allocating servers from data centers in other cities.

[0109] If none exist: that is, all servers in the initial server list meet the requirements in terms of network area and IP address, or have already met the requirements through expansion, then the server filtering process is complete.

[0110] In one example, based on the first target requirement information of the resource pool instance, the second target requirement information of the GRU, and the third target requirement information of the server in the server allocation request, a filtering process is performed on the resource pool instances that have not been connected to the resource pool to obtain a set of GRUs to be connected to the resource pool; then, the servers in the set of GRUs to be connected to the resource pool are sorted according to their entry time to obtain a sorted set of GRUs to be connected to the resource pool; where the entry time represents the time when the server enters the resource pool instance; the set of GRU sequences to be connected to the resource pool represents the set of servers in the set of GRUs to be connected to the resource pool arranged in order of entry time from earliest to latest; from the top m servers in the sorted set of GRUs to be connected to the resource pool, the servers to be connected are determined; where m is a positive integer greater than or equal to 1; and the servers to be connected are connected to the GRUs.

[0111] For example, the list of resource pool instances not connected to the resource pool is traversed, and each resource pool instance is checked. The attributes of the resource pool instance are compared with the first target requirement information, such as whether the geographical location of the resource pool instance meets the requirements, whether the type matches, and whether the size is within the specified range. Resource pool instances that meet the first target requirement information are retained and placed in a temporary list.

[0112] For each resource pool instance in the temporary list, retrieve all GRU information contained therein. Check whether the attributes of each GRU meet the second objective requirements, such as whether the functional characteristics are met, whether the performance indicators are met, and whether the server configuration meets the requirements. Collect the GRUs that meet the second objective requirements to form a set of GRUs to be connected to the resource pool.

[0113] Based on the third objective requirement information, the servers in the GRU set are filtered (optional refinement step). Further examination is performed on the server information contained in each GRU in the resource pool to be accessed. Server attributes are matched against the third objective requirement information, such as checking if the server's network zone is correct, if the IP address meets the requirements, and if the operating system version and software installation meet business needs. GRUs containing servers that do not meet the third objective requirement information are excluded, ensuring that all servers in the GRU set of the resource pool to be accessed meet all objective requirements.

[0114] For example, for each server in the GRU set of the resource pool to be accessed, the time information of its entry into the resource pool instance is obtained from the resource management system, i.e., the entry time. The entry time is usually recorded in the form of a timestamp, accurate to the second or millisecond. A suitable sorting algorithm (such as quicksort, mergesort, etc.) is used to sort the servers in the GRU set of the resource pool to be accessed in ascending order of their entry time. After sorting, the sorted GRU set of the resource pool to be accessed is obtained. At this time, the servers in the set are arranged in order of their entry time, forming a GRU sequence set of the resource pool to be accessed.

[0115] Based on business needs, resource pool load, and system design requirements, determine the number of servers, *m*, to select from the sorted GRU set of the resource pool to be connected. *m* should be a positive integer greater than or equal to 1; for example, its specific value can be determined based on factors such as the current amount of idle resources in the resource pool and the minimum server requirements of the business. From the sorted GRU set, select the top *m* servers as the servers to be connected. These servers, having joined the pool earlier, may have a higher priority and be connected to the target GRU. Connect the servers to be connected to the target GRU.

[0116] S205. Retrieve the identified server to provide business processing services to the user.

[0117] For example, this step can refer to step S104 above, and will not be repeated here.

[0118] This application provides a server allocation method based on a resource pool. First, it filters out suitable resource pool instances based on the first target requirement information of the resource pool instances (such as server usage scenario, data center location, server configuration, etc.). Then, it further filters and determines the GRUs matching the request based on the second target requirement information of the GRUs (such as CPU architecture, node type, number of servers, etc.). If the initial number of GRUs is insufficient, it expands the pool. For the third target requirement information (including server network region and IP address), it first determines multiple initial servers based on network region; if the region requirement is not met, it expands the pool. Finally, it determines the final matching server based on IP address. This effectively solves the technical problems of low server allocation efficiency and inability to accurately match user needs in existing technologies. Simultaneously, dynamic expansion and management of unconnected resources ensure the continuity and stability of server allocation, thereby improving the smoothness and success rate of user-end business processing.

[0119] Figure 3 A schematic diagram of a resource pool structure provided in this application embodiment. Figure 1 ,like Figure 3As shown, a resource pool contains at least one resource pool instance, and a resource pool instance includes at least one resource unit group (GRU), and a GRU includes at least one server.

[0120] A resource pool instance is a concrete implementation or subset of a resource pool, representing a set of resources with specific attributes or configurations within the pool. A Resource Unit Group (GRU) is the basic resource management unit within a resource pool instance, representing a collection of resource units (such as servers, storage volumes, etc.) with similar attributes and functions. GRUs abstract and encapsulate underlying resource units, providing a unified resource interface and management view for upper-layer applications or services. A server is the basic resource unit within a Resource Unit Group (GRU), representing an actual physical or virtual computing device. Servers provide fundamental resources such as computing, storage, and networking, serving as the platform for upper-layer applications or services to run.

[0121] Figure 4 A schematic diagram of a GRU structure is provided for an embodiment of this application, as shown below. Figure 4 As shown, a GRU includes three minimum resource pool units (RUs). Each minimum resource pool unit includes a power distribution cabinet and at least one server rack, in which at least one server is deployed.

[0122] The RU (Runner Unit) is the smallest resource unit in the GRU (Gateway Unit System). It integrates power distribution and server deployment functions, providing basic computing resources for upper-layer applications or services. The power distribution cabinet is the power distribution center in the RU, responsible for introducing external power and distributing it to servers and other equipment within the cabinet. Power distribution cabinets typically have safety functions such as overload protection and short-circuit protection to ensure the stability and security of power distribution. They may also be equipped with power metering and monitoring functions for real-time monitoring and management of power usage. The server rack is the physical carrier in the RU, used to deploy and secure servers and other network equipment. Servers are the core computing resources in the RU, responsible for running upper-layer applications or services, processing data requests, and storing data.

[0123] Figure 5 A schematic diagram of a resource pool structure provided in this application embodiment. Figure 2 ,like Figure 5 As shown, the resource pool includes at least one resource pool instance, the resource pool instance includes at least one GRU, the GRU includes three RUs, and the racks connected to each RU are mutually exclusive.

[0124] Each RU is connected to a rack that does not overlap with others; that is, a server for one RU is deployed only in a specific rack and does not share a rack with other RUs. Physical isolation reduces the probability of single points of failure and improves server high availability. Each RU's rack is located in a different physical location (e.g., different racks, different data center areas), preventing multiple RUs from failing simultaneously due to a single physical event (e.g., fire, flood). Each RU's power distribution cabinet has independent power supply, preventing power failures (e.g., power distribution cabinet failure, short circuit) from affecting multiple RUs. Each RU's rack is connected to an independent network switch or port, preventing the spread of network failures (e.g., switch failure, port congestion).

[0125] The server ultimately serves specific business scenarios. These scenarios include cloud-based, on-premises, and virtualization scenarios, each with corresponding supported node types. For example, cloud-based scenarios include cloud management nodes, cloud computing nodes, cloud storage nodes, cloud network nodes, and container cloud nodes. On-premises scenarios include database nodes, big data nodes, and GPU nodes. Virtualization scenarios include management nodes, compute nodes, and network nodes.

[0126] Each server has server configuration information, which includes one or more of the following: basic server information and component information. The basic server information includes one or more of the following: manufacturer information, server type, physical form, and operating system compatibility. The component information includes one or more of the following: component type, component manufacturer and model, and specifications.

[0127] Figure 6 A schematic diagram of a server allocation device based on a resource pool provided in this application embodiment. Figure 1 ,like Figure 6 As shown, a resource pool contains at least one resource pool instance, and each resource pool instance includes at least one resource unit group (GRU). Each GRU includes at least one server. This embodiment provides a server allocation device 60 based on a resource pool, comprising:

[0128] The first matching module 601 is used to respond to a server allocation request sent by the user terminal, and determine a resource pool instance that matches the server allocation request from at least one resource pool instance according to the first target requirement information in the server allocation request; wherein, the server allocation request represents a request for the user terminal to call the server, and the server allocation request includes: the first target requirement information of the resource pool instance, the second target requirement information of the GRU, and the third target requirement information of the server.

[0129] The second matching module 602 is used to determine the GRU that matches the server allocation request from the resource pool instances that match the server allocation request, based on the second target requirement information in the server allocation request.

[0130] The third matching module 603 is used to determine the server that matches the server allocation request from the GRUs that match the server allocation request based on the third target requirement information in the server allocation request.

[0131] The retrieval module 604 is used to retrieve the identified server to provide business processing services to the user.

[0132] This embodiment provides a server allocation device based on a resource pool, which can execute the method provided in the above-described method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0133] Figure 7 A schematic diagram of a server allocation device based on a resource pool provided in this application embodiment. Figure 2 ,like Figure 7 As shown, a resource pool contains at least one resource pool instance, and each resource pool instance includes at least one resource unit group (GRU). Each GRU includes at least one server. This embodiment provides a server allocation device 70 based on a resource pool, comprising:

[0134] The first matching module 701 is used to respond to a server allocation request sent by the user terminal, and determine a resource pool instance that matches the server allocation request from at least one resource pool instance according to the first target requirement information in the server allocation request; wherein, the server allocation request represents a request for the user terminal to call the server, and the server allocation request includes: the first target requirement information of the resource pool instance, the second target requirement information of the GRU, and the third target requirement information of the server.

[0135] The second matching module 702 is used to determine the GRU that matches the server allocation request from the resource pool instances that match the server allocation request, based on the second target requirement information in the server allocation request.

[0136] The third matching module 703 is used to determine the server that matches the server allocation request from the GRUs that match the server allocation request based on the third target requirement information in the server allocation request.

[0137] The retrieval module 704 is used to retrieve the identified server to provide business processing services to the user.

[0138] In one possible implementation, the first target requirement information includes server usage scenario information, data center location, and server configuration information; the first matching module 701 includes:

[0139] Based on the first target requirement information in the server allocation request, determine the resource pool instance that meets the first target requirement information from at least one resource pool instance, and select the resource pool instance that matches the server allocation request.

[0140] In one possible implementation, the second target requirement information includes CPU architecture information, node type, and server quantity information; the node type indicates the type of server; the second matching module 702 includes:

[0141] Based on the CPU architecture information and node type in the second target requirement information, the initial multiple GRUs are determined from the resource pool instances that match the server allocation request;

[0142] Based on the server quantity information in the second target requirement information, determine the GRU that matches the server quantity information from the initial multiple GRUs, and use it as the GRU that matches the server allocation request.

[0143] If the number of servers in the initial multiple GRUs does not meet the number of servers required in the second objective requirement, then the initial multiple GRUs will be expanded.

[0144] In one possible implementation, the third target requirement information includes the server network area and the server Internet Protocol (IP) address; the third matching module 703 includes:

[0145] Based on the server network area and server IP address in the third target requirement information, determine the server that matches the server IP address from the GRUs that match the server allocation request, and then assign the server that matches the server allocation request.

[0146] In one possible implementation, based on the server network area and server IP address in the third target requirement information, servers matching the Internet Protocol IP address are determined from the GRUs that match the server allocation request. This process includes:

[0147] Based on the server network area in the third objective requirement information, identify the initial multiple servers that match the server allocation request from the GRUs; if the server network area in the GRU does not meet the server network area in the third objective requirement information, then expand the GRU.

[0148] Based on the server IP address in the third objective requirement information, a server matching the server IP address is determined from the initial multiple servers, and a server matching the server allocation request is assigned; if the server network area in the initial multiple servers does not meet the server network area in the third objective requirement information, then the GRU is expanded.

[0149] In one possible implementation, the device 70 further includes:

[0150] Based on the first target requirement information of the resource pool instance, the second target requirement information of the GRU, and the third target requirement information of the server in the server allocation request, a filtering process is performed on the resource pool instances that have not been connected to the resource pool to obtain a set of GRUs to be connected to the resource pool; and the servers in the set of GRUs to be connected to the resource pool are sorted according to the server's entry time to obtain a sorted set of GRUs to be connected to the resource pool; where the entry time represents the time when the server enters the resource pool instance; and the set of GRU sequences to be connected to the resource pool represents the set of servers in the set of GRUs to be connected to the resource pool arranged in order of entry time from earliest to latest.

[0151] From the top m servers in the sorted GRU set of the resource pool to be accessed, determine the servers to be accessed; where m is a positive integer greater than or equal to 1.

[0152] Connect the server to be connected to GRU.

[0153] This embodiment provides a server allocation device based on a resource pool, which can execute the method provided in the above-described method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0154] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 8 As shown, the electronic device 80 provided in this embodiment includes at least one processor 801 and a memory 802. Optionally, the device 80 further includes a communication component 803. The processor 801, memory 802, and communication component 803 are connected via a bus 804.

[0155] In a specific implementation, at least one processor 801 executes computer execution instructions stored in memory 802, causing at least one processor 801 to perform the above-described method.

[0156] The specific implementation process of processor 801 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0157] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0158] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0159] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0160] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0161] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method.

[0162] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0163] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.

[0164] The division of units is merely a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0165] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0166] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0167] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0168] Those skilled in the art will appreciate that all or part of the steps in the above-described method embodiments can be implemented using hardware associated with program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0169] Finally, it should be noted that other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein, and is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A server allocation method based on a resource pool, characterized in that, The resource pool includes at least one resource pool instance, the resource pool instance includes at least one resource unit group (GRU), and the GRU includes at least one server. The method includes: In response to a server allocation request sent by a user, a resource pool instance matching the server allocation request is determined from the at least one resource pool instance based on the first target requirement information in the server allocation request; wherein, the server allocation request represents a request for the user to retrieve a server, and the server allocation request includes: the first target requirement information of the resource pool instance, the second target requirement information of the GRU, and the third target requirement information of the server; Based on the second target requirement information in the server allocation request, determine the GRU that matches the server allocation request from the resource pool instances that match the server allocation request; Based on the third target requirement information in the server allocation request, determine the server that matches the server allocation request from the GRUs that match the server allocation request; The identified server is invoked to provide business processing services to the user terminal.

2. The method according to claim 1, characterized in that, The first target requirement information includes server usage scenario information, data center location, and server configuration information; based on the first target requirement information in the server allocation request, a resource pool instance matching the server allocation request is determined from the at least one resource pool instance, including: Based on the first target requirement information in the server allocation request, a resource pool instance that meets the first target requirement information is determined from the at least one resource pool instance, and is the resource pool instance that matches the server allocation request.

3. The method according to claim 1, characterized in that, The second target requirement information includes CPU architecture information, node type, and server quantity information; the node type indicates the type of server. Based on the second target requirement information in the server allocation request, determine the GRU that matches the server allocation request from the resource pool instances that match the server allocation request, including: Based on the CPU architecture information and node type in the second target requirement information, an initial number of GRUs are determined from the resource pool instances that match the server allocation request. Based on the server quantity information in the second target requirement information, determine the GRU that matches the server quantity information from the initial multiple GRUs, and use it as the GRU that matches the server allocation request; If the number of servers in the initial multiple GRUs does not meet the number of servers in the second target requirement information, then the initial multiple GRUs are expanded.

4. The method according to claim 1, characterized in that, The third target requirement information includes the server network area and the server Internet Protocol (IP) address; based on the third target requirement information in the server allocation request, the server matching the server allocation request is determined from the GRUs that match the server allocation request, including: Based on the server network area and server IP address in the third target requirement information, a server matching the server IP address is determined from the GRUs that match the server allocation request.

5. The method according to claim 4, characterized in that, Based on the server network area and server IP address in the third target requirement information, servers matching the Internet Protocol IP address are determined from the GRUs that match the server allocation request. These servers that match the server allocation request include: Based on the server network region in the third target requirement information, multiple initial servers matching the server network region are determined from the GRUs that match the server allocation request; if the server network region in the GRU does not meet the server network region in the third target requirement information, the GRU is expanded. Based on the server IP address in the third target requirement information, a server matching the server IP address is determined from the initial plurality of servers, and is the server that matches the server allocation request; if the server network area in the initial plurality of servers does not meet the server network area in the third target requirement information, then the GRU is expanded.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: Based on the first target requirement information of the resource pool instance, the second target requirement information of the GRU, and the third target requirement information of the server in the server allocation request, a filtering process is performed on the resource pool instances that have not been connected to the resource pool to obtain a set of GRUs to be connected to the resource pool; and the servers in the set of GRUs to be connected to the resource pool are sorted according to the server's entry time to obtain a sorted set of GRUs to be connected to the resource pool; wherein, the entry time represents the time when the server enters the resource pool instance; the set of GRU sequences to be connected to the resource pool represents the set of servers in the set of GRUs to be connected to the resource pool arranged in order of entry time from earliest to latest; From the top m servers in the sorted GRU set of the resource pool to be accessed, determine the servers to be accessed; where m is a positive integer greater than or equal to 1. Connect the server to be connected to the GRU.

7. A server allocation device based on a resource pool, characterized in that, The resource pool includes at least one resource pool instance, the resource pool instance includes at least one resource unit group (GRU), the GRU includes at least one server, and the apparatus includes: The first matching module is used to respond to a server allocation request sent by the user terminal, and determine a resource pool instance that matches the server allocation request from the at least one resource pool instance according to the first target requirement information in the server allocation request; wherein, the server allocation request represents a request for the user terminal to call the server, and the server allocation request includes: the first target requirement information of the resource pool instance, the second target requirement information of the GRU, and the third target requirement information of the server; The second matching module is used to determine the GRU that matches the server allocation request from the resource pool instances that match the server allocation request, based on the second target requirement information in the server allocation request. The third matching module is used to determine the server that matches the server allocation request from the GRUs that match the server allocation request, based on the third target requirement information in the server allocation request. The retrieval module is used to retrieve the identified server to provide business processing services to the user terminal.

8. An electronic device, characterized in that, include: Memory, processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-6.

10. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method described in any one of claims 1-6.

Images