Distributed resource management and control method, system, equipment and computer program product

Abstract

The embodiment of the invention provides a distributed resource management and control method, system and device and a computer program product, and the method comprises the steps: obtaining a resource attribute and a resource position corresponding to a distributed resource; based on the resource attributes and / or the resource positions, at least one alternative management and control center for managing and controlling the distributed resources is determined from a plurality of management and control centers, and the alternative management and control center is used for managing and controlling one or more distributed resources; determining management and control time delay corresponding to at least one alternative management and control center; and determining a target management and control center corresponding to the distributed resources in the at least one alternative management and control center based on the management and control time delay corresponding to the at least one alternative management and control center. In the embodiment, the resource management and control operation is realized through the management and control center corresponding to the distributed resources, so that the difficulty degree of resource management and control is effectively reduced, and the practicability of the method is improved.

Description

Technical Field

[0001] This application relates to the field of network technology, and in particular to a method, system, device, and computer program product for managing distributed resources. Background Technology

[0002] With the rapid development of the Internet of Things (IoT), 5G networks, and smart devices, the demand for data generation and computing is shifting from traditional centralized data centers to the network edge. Edge computing has been proposed to meet the needs of low latency, bandwidth saving, and data locality processing.

[0003] However, the distributed nature of edge computing brings new challenges to resource management: because resource allocation is decentralized, and resources are distributed globally and are numerous, the difficulty of resource management is increased. Summary of the Invention

[0004] This application provides a method, system, device, and computer program product for managing distributed resources. It enables resource management operations through a management center corresponding to the distributed resources, which not only ensures the quality and effectiveness of resource management but also reduces the difficulty of resource management.

[0005] In a first aspect, embodiments of this application provide a method for managing distributed resources, including:

[0006] Obtain the resource attributes and location corresponding to the distributed resource;

[0007] Based on the resource attributes and / or the resource location, at least one alternative control center is determined from a plurality of control centers for controlling the distributed resources, wherein the alternative control center is used to control one or more distributed resources;

[0008] Determine the control delay corresponding to each of the at least one alternative control center;

[0009] Based on the control latency corresponding to each of the at least one alternative control center, a target control center corresponding to the distributed resource is determined from the at least one alternative control center.

[0010] Secondly, embodiments of this application provide a distributed resource management and control system, including: a resource management and control device and multiple distributed resources and multiple management and control centers communicatively connected to the resource management and control device, wherein the management and control centers are used to manage and control one or more distributed resources;

[0011] A resource management device is used to acquire the resource attributes and resource locations corresponding to each distributed resource; based on the resource attributes and / or resource locations, determine at least one alternative management center from multiple management centers for managing the distributed resources; determine the management latency corresponding to each of the at least one alternative management center; and based on the management latency corresponding to each of the at least one alternative management center, determine a target management center corresponding to the distributed resource from the at least one alternative management center.

[0012] The target control center is connected to the distributed resources and is used to control the distributed resources.

[0013] Thirdly, embodiments of this application provide an electronic device, including: a memory and a processor; wherein the memory is used to store one or more computer instructions, wherein when the one or more computer instructions are executed by the processor, the distributed resource management method described in the first aspect is implemented.

[0014] Fourthly, embodiments of the present invention provide a computer storage medium for storing a computer program, which, when executed by a computer, enables the distributed resource management method described in the first aspect above.

[0015] Fifthly, embodiments of the present invention provide a computer program product, comprising: a computer program that, when executed by a processor of an electronic device, causes the processor to perform the steps in the distributed resource management method described in the first aspect above.

[0016] The distributed resource management method, system, device, and computer program product provided in this application obtain the resource attributes and location corresponding to the distributed resource, and determine at least one candidate management center from multiple management centers for managing the distributed resource based on the resource attributes and / or the resource location; determine the management delay corresponding to each of the at least one candidate management center, and then determine the target management center corresponding to the distributed resource from the at least one candidate management center based on the management delay corresponding to each of the at least one candidate management center, so as to use the target management center to manage the distributed resource. This effectively realizes that for distributed resources corresponding to various regions, resource management operations can be performed using the management center corresponding to the distributed resource, thereby reducing the difficulty of resource management and further improving the practicality of the method. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 A schematic diagram illustrating the principle of a distributed resource management method provided in this application embodiment;

[0019] Figure 2 A flowchart illustrating a method for managing distributed resources provided in an embodiment of this application;

[0020] Figure 3 A schematic diagram illustrating the process of obtaining the resource attributes corresponding to the distributed resource provided in this application embodiment;

[0021] Figure 4 A schematic diagram of the principle of a distributed resource management method provided for an application embodiment of this application. Figure 1 ;

[0022] Figure 5 A schematic diagram of the principle of a distributed resource management method provided for an application embodiment of this application. Figure 2 ;

[0023] Figure 6 A schematic diagram of the structure of a distributed resource management and control system provided in an embodiment of this application;

[0024] Figure 7 and Figure 6 A schematic diagram of the electronic device corresponding to the distributed resource management system provided in the embodiment. Detailed Implementation

[0025] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0026] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to limit the application. The singular forms “a,” “said,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms, unless the context clearly indicates otherwise. “Multiple” generally includes at least two, but does not exclude the inclusion of at least one.

[0027] It should be understood that the term "and / or" used in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0028] Depending on the context, the words “if” or “suppose” as used here can be interpreted as “when” or “in response to determination” or “in response to detection.” Similarly, depending on the context, the phrases “if determination” or “if detection (of the stated condition or event)” can be interpreted as “when determination” or “in response to determination” or “when detection (of the stated condition or event)” or “in response to detection (of the stated condition or event).”

[0029] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a product or system comprising a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a product or system. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the product or system that includes that element.

[0030] Furthermore, the timing of the steps in the following method embodiments is merely an example and not a strict limitation.

[0031] Terminology definition:

[0032] The General Data Protection Regulation (GDPR) is a key data protection law developed at the European Union level, aimed at strengthening and harmonizing the protection of citizens' personal data across all EU member states.

[0033] To understand the specific implementation process and principles of the technical solution in this embodiment, a brief explanation of the relevant technologies is provided below:

[0034] With the rapid development of the Internet of Things (IoT), 5G networks, and smart devices, the generation and computing demands of data are shifting from traditional centralized data centers to the network edge. Edge computing has emerged to meet the needs of low latency, bandwidth savings, and data locality processing. When utilizing edge resources for edge computing operations, accurate and effective management is often required to improve the stability and reliability of computing. Currently, the following methods are commonly used to manage edge resources:

[0035] Implementation Method 1: For edge resources, users pre-configure the mapping relationship between edge resources and management stations. Specifically, users often determine the management station used to manage edge resources based on experience. Once the management station corresponding to the edge resource is configured, it will remain fixed.

[0036] However, in the actual management of edge resources, the configured management site may not be a suitable management site for the edge resources. If the management site is continued to be used to control the edge resources, the management operation is easily affected by network bandwidth, communication transmission path and network latency, and thus the stability of resource control cannot be guaranteed.

[0037] Implementation Method 2: For edge resources in different regions, different management stations are pre-configured. Each management station is connected to a parent station. The parent station can manage the edge resources corresponding to all management stations. That is, the parent station has all control plane functions related to edge resources.

[0038] However, since the parent site needs to perform static dimension management on the management site, when the scale of the management site needs to be expanded, the complexity of the parent site's control rules will increase sharply with the increase in the number of management sites, thereby increasing the cost and difficulty of managing the management sites.

[0039] In summary, the distributed nature of edge computing brings new challenges to resource management:

[0040] (1) Challenges of resource decentralization: Due to the decentralized nature of resource allocation, and the fact that distributed resources can be distributed globally and are numerous, it is difficult to manage global distributed resources through a single center, thus increasing the difficulty of resource management.

[0041] (2) Network connectivity challenges: Due to the global distribution of resources, cross-regional (national) resource management is prone to problems such as network outages and severe packet loss, which can lead to various resource management anomalies and thus make it impossible to guarantee the stability of resource management.

[0042] (3) Data compliance challenges: As regions and countries around the world have increasingly stringent requirements for data compliance, for example, the General Data Protection Regulation (GDPR) imposes strict restrictions on cross-border data transfer to countries or regions outside the EU. As can be seen from the above, how to achieve regional localization management in resource control is crucial for data compliance. Therefore, more flexible and agile resource control solutions are needed to address the challenges of data compliance.

[0043] To address the aforementioned technical problems, this embodiment provides a method, system, device, and computer program product for managing distributed resources. (See attached document.) Figure 1 As shown, the main body executing the distributed resource management and control method is the distributed resource management and control device 200. The distributed resource management and control device 200 can communicate with multiple distributed resources 100 and the target management center 300. The target management center 300 is one of multiple management centers, so that for any distributed resource 200, the target management center 300 adapted to the distributed resource 100 can be used to perform management and control operations on the distributed resource 100.

[0044] Specifically, the distributed resource management device 200 can be any programmable computing device with a certain distributed resource management capability. Furthermore, the basic structure of the distributed resource management device 200 may include at least one processor. The number of processors depends on the configuration and type of the distributed resource management device 200. The distributed resource management device 200 may also include memory, which can be volatile, such as RAM, or non-volatile, such as read-only memory (ROM), flash memory, etc., or both types may be included simultaneously. The memory typically stores an operating system (OS), one or more application programs, and may also store program data. In addition to the processing unit and memory, the distributed resource management device 200 also includes some basic configurations, such as a network interface card (NIC) chip, an I / O bus, a display component, and some peripheral devices. Optionally, some peripheral devices may include, for example, a keyboard, a mouse, a stylus, a printer, etc. Other peripheral devices are well known in the art and will not be described in detail here.

[0045] Furthermore, the distributed resource 100 can be configured on edge devices deployed in various regions. The distributed resource 100 can be specifically implemented as distributed computing resources or distributed storage resources, such as CPU resources, memory resources, etc. The edge devices can be any of the following: VR clients, video clients, vehicle terminals, smart wearable devices, handheld terminals, tablets, personal computers, etc. The distributed resource 100 can be network-connected with the distributed resource management device 200, and the target management center 300 can be network-connected with the distributed resource management device 200. This network connection can be wireless or wired. If the distributed resource 100 is connected to the distributed resource management device 200, and the target management center 300 is connected to the distributed resource management device 200, the mobile network standard can be any one of 4G (LTE), 4G+ (LTE+), 5G, 5.5G, 6G, etc.

[0046] In this embodiment of the application, the distributed resource management and control device 200 is used to obtain the resource attributes corresponding to the distributed resource 100, wherein the resource attributes may include at least one of the following: resource architecture, system type; after obtaining the resource attributes, the resource attributes can be analyzed and processed to determine at least one alternative management and control center for managing the distributed resource 100, wherein the alternative management and control center is used to manage one or more distributed resources 100.

[0047] After identifying at least one alternative control center, the control latency corresponding to each alternative control center can be determined from multiple control centers. Then, based on the control latency corresponding to each alternative control center, a target control center 300 corresponding to the distributed resource 100 can be determined from multiple control centers. A target control center 300 can correspond to one or more distributed resources 100. The target control centers 300 corresponding to distributed resources 100 in different regions can be the same or different. After determining the target control center 100 corresponding to each distributed resource 100, the distributed resource 100 can be controlled using the target control center 300, thereby effectively realizing stable control operations on the distributed resource 100.

[0048] In the above embodiments, by obtaining the resource attributes corresponding to the distributed resource 100, at least one alternative control center for controlling the distributed resource 100 is determined from multiple control centers based on the resource attributes. Then, based on the control latency corresponding to each of the at least one alternative control center, a target control center corresponding to the distributed resource 100 is determined from the at least one alternative control center. The distributed resource 100 can be controlled using the target control center. This effectively realizes that for the distributed resource 100 corresponding to each region, a target control center that is more suitable in terms of latency can be used. Furthermore, the target control center can conduct stable communication transmission with the distributed resource 100. This not only enables stable control operations on the distributed resource 100, but also reduces the difficulty of resource control and further improves the practicality of the method.

[0049] The following detailed description of some embodiments of the present invention is provided in conjunction with the accompanying drawings. Where there is no conflict between the embodiments, the following embodiments and features can be combined with each other. Furthermore, the timing of the steps in the following method embodiments is merely an example and not a strict limitation.

[0050] Figure 2 A flowchart illustrating a distributed resource management method provided in this application embodiment; see attached document. Figure 2 As shown, this embodiment provides a method for managing distributed resources. The execution subject of this method is a distributed resource management device. It can be understood that the distributed resource management device can be implemented as software, or a combination of software and hardware. Specifically, when the distributed resource management device is implemented as hardware, it can be various electronic devices with distributed resource management capabilities. When the distributed resource management device is implemented as software, it can be installed in the aforementioned electronic devices. Based on the aforementioned distributed resource management device, distributed resource management operations can be implemented. Specifically, the distributed resource management method may include the following steps:

[0051] Step S201: Obtain the resource attributes and resource location corresponding to the distributed resource.

[0052] Step S202: Based on resource attributes and / or resource location, determine at least one alternative control center from multiple control centers for managing distributed resources, wherein the alternative control center is used to manage one or more distributed resources.

[0053] Step S203: Determine the control delay corresponding to at least one alternative control center.

[0054] Step S204: Based on the control latency corresponding to each of the at least one alternative control center, determine the target control center corresponding to the distributed resource from the at least one alternative control center.

[0055] The specific implementation process and effects of each of the above steps are explained in detail below:

[0056] Step S201: Obtain the resource attributes and resource location corresponding to the distributed resource.

[0057] Distributed resources can refer to various resources deployed in a distributed manner, such as distributed computing resources or distributed storage resources. For distributed resources, there are corresponding resource attributes and resource locations. The resource attributes can include at least one of the following: resource architecture and system type. The resource architecture identifies the system architecture used to deploy the distributed resource, such as x86 system architecture, ARM system architecture, etc.; the system type identifies the system information used to deploy the distributed resource, such as Linux system, Windows system, Android system, etc.; and the resource location identifies the deployment location of the distributed resource, such as the deployment country, city, and region.

[0058] Because distributed resources with different attributes and locations require different management methods or strategies, when a user has management needs for distributed resources, in order to perform stable and effective management operations, the management device for distributed resources (hereinafter referred to as the "management device") can obtain the resource attributes and locations corresponding to the distributed resources. In some instances, the resource attributes and locations corresponding to distributed resources can be obtained through human-computer interaction. In this case, obtaining the resource attributes and locations corresponding to distributed resources may include: displaying a human-computer interaction interface; obtaining the execution operation input by the user in the human-computer interaction interface; and obtaining the resource attributes and locations corresponding to distributed resources based on the execution operation.

[0059] In other instances, the resource attributes and resource locations corresponding to distributed resources can be obtained not only through human-computer interaction but also through interactive operations with the distributed resources. In this case, obtaining the resource attributes corresponding to the distributed resources may include: generating an attribute query request corresponding to the distributed resources; sending the attribute query request to the distributed resources so that the distributed resources can perform attribute query operations based on the attribute query request to obtain the resource attributes and resource locations corresponding to the distributed resources.

[0060] Specifically, the control device has a communication connection between the distributed resources and the control center. In order to accurately determine the target control center that is compatible with the distributed resources and to realize effective management and operation of the distributed resources, the control device can generate an attribute query request corresponding to the distributed resources. In some instances, the attribute query request can be generated through human-computer interaction, or it can be generated through a preset application or a preset response action. The attribute query request may include at least one of the following: the resource identity identifier of the distributed resources, the access address of the distributed resources, etc.

[0061] After receiving an attribute query request, the request can be sent to a distributed resource. Once the distributed resource receives the request, it can perform a query to obtain the resource attributes and location corresponding to the distributed resource. The distributed resource can then send the queried resource attributes and location to the control device, allowing the control device to obtain the corresponding resource attributes and location from the distributed resource.

[0062] Step S202: Based on resource attributes and / or resource location, determine at least one alternative control center from multiple control centers for managing distributed resources, wherein the alternative control center is used to manage one or more distributed resources.

[0063] The above steps can include the following three implementation methods: (1) determining at least one alternative control center from multiple control centers for managing distributed resources based on resource attributes; (2) determining at least one alternative control center from multiple control centers for managing distributed resources based on resource location; (3) determining at least one alternative control center from multiple control centers for managing distributed resources based on resource attributes and / or resource location. For implementation method (1), it is not necessary to obtain the resource location corresponding to the distributed resource; for implementation method (2), it is not necessary to obtain the resource attributes corresponding to the distributed resource. In addition, the specific implementation methods and effects of implementation methods (1) and (2) are similar to those of implementation method (3). The following explanation uses implementation method (3) as an example of determining at least one alternative control center:

[0064] Since distributed resources with different resource attributes and locations can be managed by different management centers, in order to ensure the quality and effectiveness of distributed resource management, after obtaining the resource attributes and locations, the resource attributes and locations can be analyzed and processed to determine at least one alternative management center from multiple management centers for managing distributed resources. The alternative management center is used to perform management operations on one or more distributed resources.

[0065] In some instances, at least one alternative control center can be determined through a preset mapping relationship. In this case, determining at least one alternative control center for managing distributed resources from multiple control centers based on resource attributes and resource locations may include: obtaining a preset mapping relationship between distributed resources with different resource attributes and locations and control centers; and performing query operations on multiple control centers based on the preset mapping relationship, resource attributes, and resource locations to determine at least one alternative control center for managing distributed resources. This effectively ensures the accuracy and reliability of determining at least one alternative control center corresponding to each distributed resource.

[0066] For example, the following mapping relationship is pre-configured: In region 1, distributed resources with the X86_linux attribute correspond to control center set 1, and distributed resources with the ARM_Android attribute correspond to control center set 2. Control center set 1 includes control center 11, control center 12, control center 13... control center 1N, and control center set 2 includes control center 21, control center 22, control center 23... control center 2N. When a user has a control requirement for distributed resources with the X86_linux attribute in region 1, the above mapping relationship can be used to determine at least one candidate control center from the multiple control centers included in control center set 1; when a user has a control requirement for distributed resources with the ARM_Android attribute in region 1, the above mapping relationship can be used to determine at least one candidate control center from the multiple control centers included in control center set 2, thereby effectively ensuring the accuracy and reliability of determining the candidate control centers.

[0067] In other instances, at least one alternative control center can be determined not only through a preset mapping relationship but also through the matching degree of resource attributes. In this case, determining at least one alternative control center for managing distributed resources from multiple control centers based on resource attributes and resource locations may include: obtaining the standard resource attributes and standard resource locations that each control center can stably manage; determining the matching degree of resource attributes based on the standard resource attributes and resource locations that each control center can stably manage within the same standard resource location; and determining the control center with a matching degree greater than or equal to a preset threshold as at least one alternative control center. This also ensures the accuracy and reliability of determining at least one alternative control center.

[0068] In other instances, to meet data compliance requirements in various regions and countries around the world, at least one alternative control center can be determined not only by resource attributes and resource location, but also by combining resource control policy constraints. In this case, determining at least one alternative control center from multiple control centers for managing distributed resources based on resource attributes and / or resource location may include: obtaining resource control policy constraints for managing distributed resources, which include: the mapping relationship between distributed resources and control centers for each resource attribute; and determining at least one alternative control center from multiple control centers for managing distributed resources based on at least one of resource attributes and resource location, as well as the resource control policy constraints.

[0069] The above step of "determining at least one alternative control center for managing distributed resources from multiple control centers based on at least one of resource attributes and resource location, and resource control strategy constraints" includes three implementation methods: (1) determining at least one alternative control center for managing distributed resources from multiple control centers based on resource attributes and resource control strategy constraints; (2) determining at least one alternative control center for managing distributed resources from multiple control centers based on resource location and resource control strategy constraints; (3) determining at least one alternative control center for managing distributed resources from multiple control centers based on resource attributes, resource location, and resource control strategy constraints. For the above implementation method (1), it is not necessary to obtain the resource location corresponding to the distributed resource; for the above implementation method (2), it is not necessary to obtain the resource attributes corresponding to the distributed resource. In addition, the specific implementation methods and effects of the above implementation methods (1) and (2) are similar to the specific implementation methods and effects of the above implementation method (3). The following explanation will take implementation method (3) as the specific implementation method for determining at least one alternative control center as an example:

[0070] Different countries and regions may have different resource management requirements (or data compliance requirements) for their distributed resources. For example, for distributed resources in various EU countries, the resource management requirement may be the General Data Protection Regulation (GDPR). To manage distributed resources reasonably and stably in these regions, resource management policy constraints can be obtained. These constraints can be pre-configured and stored in a preset area or device. By accessing the preset area or device, the resource management policy constraints for managing distributed resources can be obtained.

[0071] For resource management policy constraints, these can include the mapping relationship between distributed resources in various countries and regions and management centers. Taking GDPR as an example, resource management policy constraints can include the information in the following table:

[0072]

[0073] After obtaining the resource management policy constraints, resource attributes, and resource locations, a preliminary screening of management centers can be performed based on these constraints. This allows for the identification of at least one candidate management center that meets the resource management policy constraints and can be used to manage distributed resources. Furthermore, since distributed resources can be deployed in various countries and regions globally, and different countries and regions may have different resource management policy constraints, users can flexibly configure the resource management policy constraints according to the country and region to meet the data compliance requirements of each country and region. This enables the management of distributed resources in various countries and regions, ensuring the accuracy of the candidate management center selection and expanding the applicability and application scenarios of the method.

[0074] In some other instances, to improve the flexibility and reliability of the method, this embodiment can also perform flexible scaling operations on the control center that can manage distributed resources as needed. In this case, the method in this embodiment may also include: obtaining an expansion request corresponding to the control center; expanding the control center based on the expansion request to obtain multiple expanded control centers.

[0075] In situations where distributed resources are continuously deployed and added, the management center can be expanded to ensure stable control. This involves the management device of the distributed resources receiving expansion requests corresponding to the management center. In some instances, receiving these requests may include: displaying a human-machine interface; receiving user input on the interface; and receiving the corresponding expansion request based on the input. Alternatively, in other instances, receiving the expansion request may include: acquiring a client or third-party device connected to the management device, where the expansion request is stored; and actively or passively receiving the request. After receiving the expansion request, the management center can be expanded to multiple expanded management centers, with the number of expanded management centers exceeding the number of original management centers.

[0076] Correspondingly, the method in this embodiment may also include: obtaining a scaling-down request corresponding to the control center; performing a scaling-down operation on the control center based on the scaling-down request to obtain a scaled-down control center; the number of scaled-down control centers is less than the number of control centers before scaling-down, which effectively realizes that the control center can be flexibly scaled down based on the application scenario, which is conducive to ensuring the stability and reliability of the control of distributed resources.

[0077] Step S203: Determine the control delay corresponding to at least one alternative control center.

[0078] For distributed resources, different management and control centers can have different management and control latencies. Management and control latencies can directly affect the quality and effectiveness of managing and controlling distributed resources. Therefore, after determining at least one alternative management and control center, the management and control latencies of each alternative management and control center can be determined so that a target management and control center that is compatible with the distributed resources can be selected through the dimension of management and control latencies.

[0079] In this embodiment, the specific method for determining the control latency is not limited. In some instances, the control latency is associated with the attribute information of the candidate control centers. In this case, determining the control latency corresponding to at least one candidate control center may include: obtaining the attributes and operating status of the candidate control centers (including: configuration information, capability information, load information, etc. of the candidate control centers); determining the mapping relationship between the attributes and operating status and the control latency; and determining the control latency corresponding to at least one candidate control center based on the mapping relationship and the attributes and operating status.

[0080] In some other instances, control latency can be determined not only by the attributes and operating status of alternative control centers, but also by probe commands. In this case, determining the control latency corresponding to at least one alternative control center may include: generating latency probe commands; sending latency probe commands to distributed resources so that distributed resources can perform probe operations based on latency probe commands to obtain the control latency corresponding to at least one alternative control center for the distributed resources.

[0081] Specifically, in order to accurately determine the control latency corresponding to at least one alternative control center, a latency detection command can be generated. The latency detection command includes a test data packet and the corresponding identity identifier of each alternative control center. After obtaining the latency detection command, it can be sent to the distributed resource. After the distributed resource obtains the latency detection command, it performs a latency detection operation based on the latency detection command, thereby obtaining the control latency corresponding to at least one alternative control center for the distributed resource. This effectively ensures the accuracy and reliability of control latency detection.

[0082] Step S204: Based on the control latency corresponding to each of the at least one alternative control center, determine the target control center corresponding to the distributed resource from the at least one alternative control center.

[0083] After obtaining the control latency corresponding to at least one alternative control center, the target control center corresponding to the distributed resource can be determined from at least one alternative control center based on the control latency corresponding to each of the at least one alternative control center. In some instances, determining the target control center corresponding to the distributed resource from at least one alternative control center based on the control latency corresponding to each of the at least one alternative control center may include: determining an intermediate control center that meets the preset latency requirement based on the control latency corresponding to each alternative control center; and determining the target control center corresponding to the distributed resource based on the intermediate control center.

[0084] The system includes pre-configured preset latency requirements for managing distributed resources. These preset latency requirements can be determined based on user or application needs. For example, the preset latency requirements can be 10ms, 20ms, 50ms, 100ms, 150ms, etc. After obtaining the management latency corresponding to each candidate management center, an intermediate management center that meets the preset latency requirements can be determined based on the management latency corresponding to each candidate management center. The determined intermediate management center can be at least a part of at least one candidate management center.

[0085] After obtaining the intermediate control center, the target control center corresponding to the distributed resource can be determined based on the intermediate control center. Specifically, determining the target control center corresponding to the distributed resource based on the intermediate control center can include: if there is only one intermediate control center, then the intermediate control center is determined as the target control center; if there are multiple intermediate control centers, the resource control requirements corresponding to the distributed resource are obtained; and based on the resource control requirements, the target control center corresponding to the distributed resource is determined from among the multiple intermediate control centers.

[0086] For example, when at least one alternative control center includes control center A, control center B, control center C, and control center D, and the control latency corresponding to control center A is 67ms, control center B is 34ms, control center C is 75ms, and control center D is 48ms, if the preset latency requirement is 70ms, then three intermediate control centers that meet the preset latency requirement can be obtained, namely: control center A, control center B, and control center D; if the preset latency requirement is 50ms, then two intermediate control centers that meet the preset latency requirement can be obtained, namely: control center B and control center D; and if the preset latency requirement is 40ms, then one intermediate control center that meets the preset latency requirement can be obtained, namely control center B. As can be seen from the above, those skilled in the art can flexibly adjust and configure the preset latency requirement according to specific application scenarios or application requirements, and different preset latency requirements can determine different numbers of different intermediate control centers.

[0087] After obtaining the intermediate control center, the number of intermediate control centers can be determined. If there is only one intermediate control center, it can be directly designated as the target control center to accurately manage distributed resources. If there are multiple intermediate control centers, to improve the quality and effectiveness of distributed resource management, resource management requirements corresponding to the distributed resources can be obtained. These requirements can be determined through human-computer interaction and may include one of the following: resource management cost requirements (reflecting the user's willingness to pay), resource management quality requirements (reflecting the user's desired management effect), resource management latency requirements, resource management strategies (reflecting the user's desired management methods), etc.

[0088] After obtaining the resource management requirements, the target management center corresponding to the distributed resource can be determined from multiple intermediate management centers based on the resource management requirements. In some instances, multiple intermediate management centers can be directly filtered using the resource management requirements to obtain one or more intermediate management centers that meet the resource management requirements. Then, one intermediate management center can be determined as the target management center corresponding to the distributed resource; or, any one of the multiple intermediate management centers can be determined as the target management center corresponding to the distributed resource.

[0089] In other instances, the target control center can be determined not only based on resource control requirements but also based on control costs. In this case, when there are multiple intermediate control centers, the control costs corresponding to each intermediate control center can be determined. The target control center is then determined based on both resource control requirements and control costs.

[0090] To enable users to reliably manage distributed resources with minimal cost, after acquiring multiple intermediate management centers, the management cost corresponding to each intermediate management center can be determined. The management cost can be determined through a preset mapping relationship. Determining the management cost of each intermediate management center can include: acquiring a preset mapping relationship between the identity identifier of the intermediate management center and the management cost; and using the preset mapping relationship and the identity identifier of each intermediate management center to determine the management cost corresponding to each intermediate management center.

[0091] After obtaining the control costs, intermediate control centers can be screened based on these costs to obtain the target control center with the lowest control costs. This effectively ensures the accuracy and reliability of determining the target control center.

[0092] In other instances, to improve the practicality of the method, the method in this embodiment may further include:

[0093] Step S205: Use the target control center to manage and control distributed resources.

[0094] After obtaining the target control center, it can be used to manage and control distributed resources. In some instances, managing and controlling distributed resources using the target control center may include: updating and adjusting the status of distributed resources; and / or managing and adjusting the utilization rate of distributed resources; and / or modifying or adjusting the relevant configurations of distributed resources, thereby effectively achieving the quality and effect of managing and controlling distributed resources.

[0095] The distributed resource management method provided in this embodiment obtains the resource attributes and location corresponding to the distributed resource, and determines at least one candidate management center from multiple management centers based on the resource attributes and / or resource location for managing the distributed resource; determines the management delay corresponding to each of the at least one candidate management center, and then determines the target management center corresponding to the distributed resource from the at least one candidate management center based on the management delay corresponding to each of the at least one candidate management center, so as to use the target management center to manage the distributed resource. This effectively realizes that for distributed resources corresponding to various regions, resource management operations can be carried out using the management center corresponding to the distributed resource. This not only ensures the quality and effect of resource management, but also reduces the difficulty of resource management, and further improves the practicality of the method.

[0096] Figure 3 This is a flowchart illustrating the process of obtaining resource attributes corresponding to distributed resources, provided in an embodiment of this application. Based on the above embodiments, refer to the appendix... Figure 3 As shown, the resource attributes corresponding to a distributed resource can include the resource architecture. In this case, the distributed resource architecture can be obtained through attribute query operations. Furthermore, performing an attribute query operation based on an attribute query request to obtain the resource attributes corresponding to the distributed resource can include:

[0097] Step S301: Based on the attribute query request, generate a first architecture query instruction for determining the resource architecture.

[0098] When the resource attributes corresponding to the distributed resource include resource architecture, after the distributed resource obtains an attribute query request, a first architecture query instruction for determining the resource architecture can be generated based on the attribute query request. The first architecture query instruction can be automatically generated by the distributed resource based on the attribute query request, or it can be obtained by the distributed resource accessing a preset area based on the attribute query request. In some instances, the first architecture query instruction can be any one of the following: the "wmic cpu get Architecture" instruction or the "uname -m" instruction.

[0099] Step S302: Perform an architecture query operation based on the first architecture query instruction to determine the resource architecture of the distributed resources.

[0100] After obtaining the first architecture query instruction, an architecture query operation can be performed based on the first architecture query instruction to determine the resource architecture of the distributed resources. In some instances, performing an architecture query operation based on the first architecture query instruction to determine the resource architecture of the distributed resources may include: performing an architecture query operation based on the first architecture query instruction to obtain query response information; and determining the resource architecture of the distributed resources based on the query response information.

[0101] Specifically, determining the resource architecture of a distributed resource based on the query response information may include: when the query response information is the first response information, the resource architecture of the distributed resource is determined to be the first resource architecture; when the query response information is the second response information, the resource architecture of the distributed resource is determined to be the second resource architecture.

[0102] For example, taking the first resource architecture as x86 architecture and the second resource architecture as ARM architecture, when the first architecture query instruction is "wmic cpu get Architecture", an architecture query operation can be performed based on the first architecture query instruction, and the query response information can be obtained. When the query response information is "0" or "9", it can be determined that the resource architecture of the distributed resource is x86 architecture; when the query response information is "5", it can be determined that the resource architecture of the distributed resource is ARM architecture.

[0103] When the first architecture query command is "uname-m", an architecture query operation can be performed based on the first architecture query command, and the query response information can be obtained. When the query response information is "x86_64", the resource architecture of the distributed resource can be determined to be x86 architecture; when the query response information is "aarch64", the resource architecture of the distributed resource can be determined to be ARM architecture, thus effectively ensuring the stable determination of the resource architecture.

[0104] In some other instances, resource attributes may include not only resource architecture but also system type. To accurately determine the resource architecture of a distributed resource, after generating a first architecture query instruction for determining the resource architecture, the method in this embodiment may further include: determining whether the distributed resource can normally execute the first architecture query instruction to perform an architecture query operation; if the distributed resource can normally execute the first architecture query instruction to perform an architecture query operation, then determining the system type of the distributed resource as a first preset type; if the distributed resource cannot normally execute the first architecture query instruction to perform an architecture query operation, then generating a second architecture query instruction for determining the resource architecture, the second architecture query instruction being different from the first architecture query instruction; and performing an architecture query operation based on the second architecture query instruction to determine the resource architecture of the distributed resource.

[0105] Specifically, whether a first architecture query instruction can be executed normally in a distributed resource depends on the resource type. After generating the first architecture query instruction to determine the resource architecture, it can be first determined whether the distributed resource can normally execute the first architecture query instruction to perform an architecture query operation. In some instances, determining whether the distributed resource can normally execute the first architecture query instruction to perform an architecture query operation may include: the distributed resource performing an architecture query operation based on the first architecture query instruction; detecting whether a query response information is received within a preset time period; if a query response information is received within the preset time period, it is determined that the distributed resource can normally execute the first architecture query instruction; if no query response information is received within the preset time period, it is determined that the distributed resource cannot normally execute the first architecture query instruction.

[0106] When it is determined that the distributed resource can normally execute the first architecture query instruction to perform an architecture query operation, the system type of the distributed resource can be determined as the first preset type. In some instances, the first preset type can be the "Windows" system. When the distributed resource cannot normally execute the first architecture query instruction to perform an architecture query operation, in order to accurately determine the resource architecture of the distributed resource, a second architecture query instruction can be generated to determine the resource architecture. The second architecture query instruction is different from the first architecture query instruction. For example, when the first architecture query instruction is the "wmic cpuget Architecture" instruction, the second architecture query instruction is the "uname -m" instruction; or, when the first architecture query instruction is the "uname -m" instruction, the second architecture query instruction is the "wmic cpu get Architecture" instruction.

[0107] After obtaining the second architecture query instruction, an architecture query operation can be performed based on the second architecture query instruction to determine the resource architecture of the distributed resource. Specifically, performing an architecture query operation based on the second architecture query instruction to determine the resource architecture of the distributed resource may include: performing an architecture query operation based on the second architecture query instruction to obtain query response information; if the query response information is a first preset response, then the resource architecture of the distributed resource is determined to be the first resource architecture; if the query response information is a second preset response, then the resource architecture of the distributed resource is determined to be the second resource architecture.

[0108] For example, taking the first architecture query instruction as "wmic cpu get Architecture" and the second architecture query instruction as "uname -m" as an example, if the first architecture query instruction cannot be executed normally, the second architecture query instruction can be generated. Then, the architecture query operation can be performed based on the "uname -m" instruction. If the query response information of the second architecture query instruction is "x86_64", then the resource architecture of the distributed resource is determined to be x86 architecture; if the query response information of the second architecture query instruction is "aarch64", then the resource architecture of the distributed resource is determined to be ARM architecture. This effectively realizes the accurate determination of the resource architecture.

[0109] Furthermore, regarding resource attributes, since resource attributes include not only resource architecture but also system type, after determining the resource architecture of the distributed resource through an architecture query operation based on the second architecture query instruction, in order to accurately determine the system type, the method in this embodiment may further include: generating a first type query instruction for determining the system type of the distributed resource; determining the system type of the distributed resource as a second preset type when the first type query instruction can be executed normally; generating a second type query instruction for determining the system type of the distributed resource when the first type query instruction cannot be executed normally; and determining the system type of the distributed resource as a third preset type when the second type query instruction can be executed normally.

[0110] Specifically, after determining the resource architecture of the distributed resources by performing an architecture query operation based on the second architecture query instruction, in order to accurately determine the system type, a first type query instruction for determining the system type of the distributed resources can be generated. The generation method of the "first type query instruction" is similar to the generation method of the "second architecture query instruction" mentioned above. For details, please refer to the above description and will not be repeated here.

[0111] For example, taking the first type of query command "getprop|grep ro.bu i ld.vers ion.release" and the second type of query command "cat / etc / os-release" as examples, after generating the first type of query command to determine the system type of the distributed resource, a system type query operation can be performed based on the first type of query command. If the first type of query command can be executed normally, the system type of the distributed resource can be determined to be the second preset type, which can be "Android". If the first type of query command cannot be executed normally, the second type of query command is generated to determine the system type of the distributed resource. If the second type of query command ("cat / etc / os-release") can be executed normally, the system type of the distributed resource can be determined to be the third preset type, which can be "Linux". This effectively realizes the stable determination of system type and resource architecture.

[0112] In this embodiment, a first architecture query instruction for determining the resource architecture is generated based on the attribute query request. Then, an architecture query operation is performed based on the first architecture query instruction to determine the resource architecture of the distributed resources. This effectively realizes the accurate determination of the resource architecture of the distributed resources, which facilitates the management and control of the distributed resources based on the determined resource architecture, further improving the practicality of the method.

[0113] For specific applications, please refer to the appendix. Figures 4-5 As shown, this embodiment provides a method for managing distributed edge cloud resources. The execution entity of this method is a management and control platform, which can communicate with the management and control resource cluster pool and the distributed resources. The management and control resource cluster pool can include different types of cluster pools, such as an X86_Linux resource pool and an ARM_Android resource pool. These resource pools can include multiple management and control centers, such as management and control centers located in Shanghai, Beijing, Chengdu, Western Europe, the United States, and Southeast Asia. These management and control centers may have different management and control latency and costs. The distributed resources can be shared resources used by multiple users or exclusive resources used by a single user. The management and control centers can accurately and effectively manage the corresponding distributed resources from the perspectives of resource classification, resource deployment location, operator (China Mobile, China Unicom, etc.), latency to the resource pool where the management and control center is located, and resource cost.

[0114] Specifically, taking edge cloud resources as a distributed resource as an example, this method may include the following steps:

[0115] Step 1: Obtain the CPU architecture, operating system (OS) type, and resource location corresponding to the edge cloud resources.

[0116] The management and control platform can communicate with the application access layer, which allows one or more users to access the resource management and control platform to perform distributed resource management and control operations. For example, the management and control platform can be used by users 1, 2, 3, and 4. The management and control platform can obtain management and control requirements from various routers (e.g., router 1, router 2, router 3, and router 4), generate different deployment rules for management and control based on these requirements, and synchronize the management and control resource cluster pool to the routers so that the routers can directly connect to the management and control resource cluster pool.

[0117] Specifically, the CPU architecture can be any one of the following: x86 architecture or RAM architecture, and the operating system type can be any one of the following: Windows type, Linux type, Android type. The CPU architecture and operating system type mentioned above can be stored inside the CPU of each edge resource.

[0118] To enable the management platform to obtain the CPU architecture and operating system type corresponding to the edge cloud resources, the platform can generate architecture query requests "wmic cpu get Arch itecture" and "uname-m" corresponding to the distributed resources. Then, based on these requests, it can perform an architecture query operation to determine the CPU architecture corresponding to the edge resource's CPU. Specifically:

[0119] If the architecture query request "wmic cpu get Architecture itecture" executes successfully, the query response information can be obtained. Based on the query response information, the CPU architecture corresponding to the edge resource CPU can be determined. For example, if the query response information is "0" or "9", the CPU architecture is determined to be x86 architecture; if the query response information is "5", the CPU architecture is determined to be RAM architecture. Furthermore, if the architecture query request "wmic cpu get Architecture itecture" executes successfully, the operating system type can be determined to be Windows.

[0120] If the architecture query request "wmic cpu get Arch itemcture" fails, the system checks if the architecture query request "uname -m" succeeds. If "uname -m" succeeds, the query response information can be obtained, and the CPU architecture corresponding to the edge resource CPU can be determined based on the response information. For example, if the query response information is "x86_64", the CPU architecture is determined to be x86; if the query response information is "aarch64", the CPU architecture is determined to be RAM. Furthermore, if the architecture query request "uname -m" succeeds, the operating system type can be determined to be either Linux or Android.

[0121] To determine the specific operating system type within either Linux or Android, a first-type query request "getprop|grep ro.bu i ld.vers ion.re lease" can be generated. Based on this first-type query request "getprop|grep ro.bu i ld.vers ion.re lease", the operating system type is determined. Specifically, if the first-type query request "getprop|grep ro.bu i ld.vers ion.re lease" executes successfully, the operating system type is determined to be Android.

[0122] If the first type of query request "getprop|grep ro.bu i ld.vers ion.re lease" fails to execute, a second type of query request "cat / etc / os-re lease" can be generated. The operating system type is then determined based on the second type of query request "cat / etc / os-re lease". Specifically, if the second type of query request "cat / etc / os-release" executes successfully, the operating system type is determined to be Linux. If the second type of query request "cat / etc / os-re lease" fails to execute, an error message "error" can be displayed.

[0123] Similarly, resource locations can be obtained through location query requests. In this case, the management platform can generate a location query request corresponding to the distributed resource, and then send the query request to the distributed resource so that the distributed resource can perform a location query operation based on the location query request, obtain the resource location of the distributed resource, and return the resource deployment location to the management platform, thereby enabling the management platform to reliably obtain the resource location.

[0124] Step 2: Obtain the resource management policy constraints used to manage edge cloud resources. The resource management policy constraints include the mapping relationship between edge cloud resources of each resource attribute and the management center.

[0125] In the process of managing edge resources, to meet requirements such as data transmission, data processing, personal information security, and privacy data security, administrators can configure resource management policy constraints corresponding to edge resources based on the data compliance requirements of various countries and regions. Specifically, administrators can configure resource management policies before performing edge cloud resource management operations. After the management platform obtains the resource management policies, it can process them to generate resource management policy constraints. These constraints can be specifically mapping policy rules between the edge resource area and the management center. For example, when the data compliance requirement is GDPR, the management policy rules that comply with EU GDPR requirements can be shown in the table below:

[0126]

[0127]

[0128] Step 3: Based on the CPU architecture, operating system, resource location, and resource management policy constraints, determine at least one alternative management center for managing edge cloud resources.

[0129] Specifically, multiple control centers are pre-initialized in various regions globally for different CPU architectures and operating types, i.e., the initialization of distributed control clusters is performed. Each distributed control cluster includes multiple control centers. For example, for edge resources such as x86_Linux / x86_Windows / x86_Android / ARM_Linux / ARM_Windows / ARM_Android, control centers can be initialized in regions such as Beijing, Shanghai, Chengdu, Shenzhen, Hohhot, Frankfurt (Germany), London (UK), Virginia (USA), California (USA), Tokyo (Japan), Mumbai (India), Singapore, Kuala Lumpur (Malaysia), and Jakarta (Indonesia), thus obtaining initial control centers. Furthermore, users can flexibly scale the initial control centers up or down as needed to meet the control requirements of different edge cloud resources.

[0130] In some instances, after determining the CPU architecture, operating system, and resource location of edge cloud resources, the initial control center can be filtered based on the CPU architecture and operating system to obtain a filtered control center; then, the filtered control center can be filtered based on resource control policy constraints to obtain at least one alternative control center for controlling edge cloud resources.

[0131] In other instances, after determining the CPU architecture, operating system, and resource location of edge cloud resources, the initial control center can be filtered based on resource management policy constraints and resource location to obtain a filtered control center; then, the filtered control centers can be filtered based on CPU architecture and operating system to obtain at least one alternative control center for managing edge cloud resources.

[0132] The filtering of the initial control center based on resource management policy constraints and resource location may include: obtaining the regional information of the edge cloud resource, which may include the country, region, province, etc.; and then filtering the initial control center based on the regional information of the edge cloud resource and the resource management policy constraints to obtain the filtered control center that meets the resource management policy. For example, if the edge cloud resource is located in Greece, the control center corresponding to the edge resource in Greece can be determined by automatically querying the resource management policy constraints. Then, the control center in this region is selected as the filtered control center.

[0133] After determining the CPU architecture and operating system of the edge cloud resources, at least one alternative control center can be selected from the filtered control centers to manage the edge cloud resources. For example, when the edge cloud resources are cloud gaming AIC resources, the CPU architecture is ARM, and the OS type is Android, the control center corresponding to the ARM_Android type is selected as the alternative control center, thus realizing the initial screening operation of the control center.

[0134] Step 4: Determine the control delay corresponding to at least one alternative control center.

[0135] After acquiring at least one alternative control center, in order to achieve ultra-low latency resource control operations, the control platform can generate a latency detection script, distribute the script to edge cloud resources, and execute latency detection commands to obtain the control latency corresponding to each of the at least one alternative control center. In some instances, when executing latency detection commands on edge cloud resources, multiple latency detection operations can be performed, such as 4, 5, or 6 times, thereby determining multiple latency information corresponding to the edge cloud resources. These multiple latency information values ​​are then averaged to obtain the control latency corresponding to each of the at least one alternative control center.

[0136] Step 5: Based on the control latency corresponding to each of the at least one alternative control center, determine the target control center corresponding to the edge cloud resource from the at least one alternative control center.

[0137] After obtaining the control latency corresponding to at least one alternative control center, the alternative control centers can be sorted based on their respective control latency to obtain the sorting information of at least one alternative control center. Then, the alternative control center with the lowest control latency can be determined as the target control center corresponding to the edge cloud resource.

[0138] Step 6: Use the target control center to manage and control edge cloud resources.

[0139] Specifically, after determining the target control center, the nodes in the target control center can be used to generate resource management commands, which can then be sent to edge cloud resources so that the edge cloud resources can complete resource management actions based on the resource management commands. The resource management actions can include at least one of the following: edge cloud resource status detection operations, edge cloud resource utilization configuration operations, edge cloud resource resource status management operations, edge cloud resource resource status update operations, etc.

[0140] In addition, in order to meet the different management and control needs of users for edge cloud resources, edge cloud resources can be labeled according to different management and control levels. For example, management and control operations for high-cost edge cloud resources, management and control operations for low-cost edge cloud resources, and management and control operations for medium-cost edge cloud resources. It can be understood that the above-mentioned different levels of management and control operations can correspond to different management and control quality and effects. In specific applications, users can select different levels of management and control operations according to different management and control needs, thereby effectively improving the flexibility and reliability of the management and control operations.

[0141] The technical solution provided in this application embodiment effectively avoids the defects in related technologies such as "(1) the complexity of configuring and managing the mapping relationship between distributed resources and the control center, which requires configuration for each edge node and has too many control rules that are difficult to manage; (2) the inability to select a suitable control center, resulting in low overall resource control efficiency and even stability problems." Specifically, by performing latency detection and sorting on global distributed edge resources to determine the appropriate control center, the network connectivity between edge resources and the control center is guaranteed, and more reliable resource control is achieved. For multiple control centers, users can horizontally expand the control centers that support resource control capabilities according to their needs, thereby increasing the scale of resource management. In addition, multiple control centers achieve high availability and disaster recovery capabilities for edge resource control. When a single control center fails, it only affects the edge resource control within the region, which can reduce the failure explosion radius. Furthermore, since the control center can be determined by flexible policy rules, it can meet the data compliance requirements of various countries and regions, further ensuring the stability and reliability of the control center in controlling distributed resources.

[0142] Figure 6 A schematic diagram of the structure of a distributed resource management system provided in this application embodiment; see attached figure. Figure 6 As shown, this embodiment provides a distributed resource management and control system, which may include: a resource management and control device 11 and multiple distributed resources and multiple management and control centers 12 that are communicatively connected to the resource management and control device 11, wherein the management and control center 12 is used to manage and control one or more distributed resources;

[0143] Resource management device 11 is used to acquire the resource attributes and resource locations corresponding to each distributed resource; based on the resource attributes and / or the resource locations, determine at least one alternative management center from multiple management centers for managing the distributed resources; determine the management delay corresponding to each of the at least one alternative management center; and based on the management delay corresponding to each of the at least one alternative management center, determine the target management center 13 corresponding to the distributed resource from the at least one alternative management center.

[0144] The target control center 13 communicates with the distributed resources and is used to manage and control the distributed resources.

[0145] In some instances, when the resource management device 11 obtains the resource attributes and resource location corresponding to the distributed resource, the resource management device 11 is used to: generate an attribute query request corresponding to the distributed resource; send the attribute query request to the distributed resource so that the distributed resource can perform an attribute query operation based on the attribute query request to obtain the resource attributes and resource location corresponding to the distributed resource.

[0146] In some instances, resource attributes include: resource architecture; when the resource management device 11 performs an attribute query operation based on the attribute query request to obtain the resource attributes corresponding to the distributed resource, the resource management device 11 is used to: generate a first architecture query instruction for determining the resource architecture based on the attribute query request; and perform an architecture query operation based on the first architecture query instruction to determine the resource architecture of the distributed resource.

[0147] In some instances, when the resource management device 11 performs an architecture query operation based on the first architecture query instruction to determine the resource architecture of the distributed resources, the resource management device 11 is used to: perform an architecture query operation based on the first architecture query instruction to obtain query response information; and determine the resource architecture of the distributed resources based on the query response information.

[0148] In some instances, when the resource management device 11 determines the resource architecture of a distributed resource based on the query response information, the resource management device 11 is used to: determine the resource architecture of the distributed resource as the first resource architecture when the query response information is the first response information; and determine the resource architecture of the distributed resource as the second resource architecture when the query response information is the second response information.

[0149] In some instances, resource attributes also include: system type; after generating a first architecture query instruction for determining the resource architecture, the resource management device 11 in this embodiment is further configured to: determine whether the distributed resource can normally execute the first architecture query instruction to perform an architecture query operation; when the distributed resource can normally execute the first architecture query instruction to perform an architecture query operation, then determine that the system type of the distributed resource is a first preset type; when the distributed resource cannot normally execute the first architecture query instruction to perform an architecture query operation, then generate a second architecture query instruction for determining the resource architecture, the second architecture query instruction being different from the first architecture query instruction; perform an architecture query operation based on the second architecture query instruction to determine the resource architecture of the distributed resource.

[0150] In some instances, after determining the resource architecture of the distributed resource by performing an architecture query operation based on the second architecture query instruction, the resource management device 11 in this embodiment is further configured to: generate a first type query instruction for determining the system type of the distributed resource; if the first type query instruction can be executed normally, then determine the system type of the distributed resource as a second preset type; if the first type query instruction cannot be executed normally, then generate a second type query instruction for determining the system type of the distributed resource; if the second type query instruction can be executed normally, then determine the system type of the distributed resource as a third preset type.

[0151] In some instances, when the resource management device 11 determines at least one alternative management center from a plurality of management centers for managing distributed resources based on resource attributes and / or the resource location, the resource management device 11 performs the following actions: obtaining resource management policy constraints for managing distributed resources, the resource management policy constraints including: the mapping relationship between distributed resources and management centers for each resource attribute; and determining at least one alternative management center from a plurality of management centers for managing distributed resources based on at least one of the resource attributes and the resource location, and the resource management policy constraints.

[0152] In some instances, when the resource management device 11 determines the management latency corresponding to at least one alternative management center, the resource management device 11 performs the following actions: generating a latency detection command; sending the latency detection command to the distributed resource so that the distributed resource performs a detection operation based on the latency detection command to obtain the management latency corresponding to at least one alternative management center for the distributed resource.

[0153] In some instances, when the resource management device 11 determines the target management center corresponding to the distributed resource from at least one candidate management center based on the management latency corresponding to each candidate management center, the resource management device 11 is used to perform: determining an intermediate management center that meets the preset latency requirement based on the management latency corresponding to each candidate management center; and determining the target management center corresponding to the distributed resource based on the intermediate management center.

[0154] In some instances, when the resource management device 11 determines the target management center corresponding to the distributed resource based on the intermediate management center, the resource management device 11 performs the following: when there is only one intermediate management center, the intermediate management center is determined as the target management center; when there are multiple intermediate management centers, the resource management requirements corresponding to the distributed resource are obtained; and based on the resource management requirements, the target management center corresponding to the distributed resource is determined from among the multiple intermediate management centers.

[0155] Figure 6 The distributed resource management system shown can execute Figure 1-Figure 5 For the methods shown in the embodiments, the parts not described in detail in this embodiment can be referred to the following: Figure 1-Figure 5 The relevant descriptions of the illustrated embodiments are provided below. For the execution process and technical effects of this technical solution, please refer to [link / reference]. Figure 1-Figure 5 The descriptions in the illustrated embodiments will not be repeated here.

[0156] In one possible design, Figure 6 The structure of the distributed resource management system shown can be implemented as an electronic device. (See attached document.) Figure 7As shown, the distributed resource management system in this embodiment can be implemented as an electronic device. Specifically, the electronic device may include a first processor 21 and a first memory 22. The first memory 22 is used to store data executed by the corresponding electronic device. Figure 2 In the program of the distributed resource management method provided in the illustrated embodiment, the first processor 21 is configured to execute the program stored in the first memory 22.

[0157] The program includes one or more computer instructions, wherein when executed by the first processor 21, the one or more computer instructions can perform the following steps: obtaining the resource attributes and resource location corresponding to the distributed resource; determining at least one alternative control center from multiple control centers for controlling the distributed resource based on the resource attributes and / or the resource location, wherein the alternative control center is used to control one or more distributed resources; determining the control delay corresponding to each of the at least one alternative control center; and determining the target control center corresponding to the distributed resource from the at least one alternative control center based on the control delay corresponding to each of the at least one alternative control center.

[0158] Furthermore, the first processor 21 is also used to perform the aforementioned Figure 2 All or part of the steps in the illustrated embodiments. The electronic device may also include a first communication interface 23 for communication between the electronic device and other devices or communication networks.

[0159] In addition, embodiments of the present invention provide a computer storage medium for storing computer software instructions used by an electronic device, which includes instructions for executing the above-described... Figure 2 The program involved in the distributed resource management method in the illustrated embodiment.

[0160] Furthermore, embodiments of the present invention provide a computer program product, comprising: a computer program, which, when executed by a processor of an electronic device, causes the processor to perform... Figure 2 The method for managing distributed resources in the illustrated embodiment.

[0161] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0162] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and 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 modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0163] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of a necessary general-purpose hardware platform, or by a combination of hardware and software. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a computer product. This application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0164] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable device, generate instructions for implementing the flowchart... Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0165] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 a process or multiple processes and / or boxes Figure 1 The functions specified in one or more boxes. These computer program instructions may also be loaded onto a computer or other programmable device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0166] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory. Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0167] Computer-readable media include both permanent and non-permanent, removable and non-removable media that can store data using any method or technology. Data can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transfer medium that can be used to store data accessible by a computing device. As defined herein, computer-readable media do not include transient computer-readable media, such as modulated data signals and carrier waves.

[0168] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A method for managing distributed resources, characterized in that, include: Obtain the resource attributes and location corresponding to the distributed resource; Based on the resource attributes and / or the resource location, at least one alternative control center is determined from a plurality of control centers for controlling the distributed resource; Determine the control delay corresponding to each of the at least one alternative control center; Based on the control latency corresponding to each of the at least one alternative control center, a target control center corresponding to the distributed resource is determined from the at least one alternative control center.

2. The method according to claim 1, characterized in that, Retrieve the resource attributes and location corresponding to the distributed resource, including: Generate an attribute query request corresponding to the distributed resource; The attribute query request is sent to the distributed resource so that the distributed resource can perform an attribute query operation based on the attribute query request to obtain the resource attributes and resource location corresponding to the distributed resource.

3. The method according to claim 2, characterized in that, The resource attributes include: resource architecture; based on the attribute query request, an attribute query operation is performed to obtain the resource attributes corresponding to the distributed resource, including: Based on the attribute query request, a first architecture query instruction for determining the resource architecture is generated; Based on the first architecture query instruction, an architecture query operation is performed to determine the resource architecture of the distributed resource.

4. The method according to claim 3, characterized in that, Based on the first architecture query instruction, an architecture query operation is performed to determine the resource architecture of the distributed resource, including: Perform an architecture query operation based on the first architecture query command to obtain query response information; Based on the query response information, the resource architecture of the distributed resource is determined.

5. The method according to claim 4, characterized in that, Based on the query response information, the resource architecture of the distributed resource is determined, including: When the query response information is the first response information, the resource architecture of the distributed resource is determined to be the first resource architecture; When the query response information is the second response information, the resource architecture of the distributed resource is determined to be the second resource architecture.

6. The method according to claim 3, characterized in that, The resource attribute further includes: system type; after generating a first architecture query instruction for determining the resource architecture, the method further includes: Determine whether the distributed resource can normally execute the first architecture query instruction to perform an architecture query operation; When the distributed resource is able to execute the first architecture query instruction to perform an architecture query operation normally, the system type of the distributed resource is determined to be the first preset type; When the distributed resource cannot execute the first architecture query instruction to perform the architecture query operation normally, a second architecture query instruction is generated to determine the resource architecture. The second architecture query instruction is different from the first architecture query instruction. Based on the second architecture query instruction, an architecture query operation is performed to determine the resource architecture of the distributed resource.

7. The method according to claim 6, characterized in that, After determining the resource architecture of the distributed resource by performing an architecture query operation based on the second architecture query instruction, the method further includes: Generate a first-type query instruction for determining the system type of the distributed resource; If the first type of query instruction can be executed normally, then the system type of the distributed resource is determined to be the second preset type; If the first type of query instruction cannot be executed normally, a second type of query instruction is generated to determine the system type of the distributed resource; If the second type of query instruction can be executed normally, then the system type of the distributed resource is determined to be the third preset type.

8. The method according to any one of claims 1-6, characterized in that, Based on the resource attributes and / or the resource location, at least one alternative control center is determined from a plurality of control centers for controlling the distributed resource, including: Obtain resource management policy constraints for managing the distributed resources, the resource management policy constraints including: the mapping relationship between distributed resources of each resource attribute and the management center; Based on at least one of the resource attributes and the resource location, and the resource management policy constraints, at least one alternative management center is determined from multiple management centers to manage the distributed resource.

9. The method according to any one of claims 1-6, characterized in that, Determining the control latency corresponding to each of the at least one alternative control center includes: Generate delay detection commands; The latency detection command is sent to the distributed resource so that the distributed resource performs a detection operation based on the latency detection command to obtain the control latency corresponding to each of the at least one alternative control center for the distributed resource.

10. The method according to any one of claims 1-6, characterized in that, Based on the control latency corresponding to each of the at least one alternative control center, a target control center corresponding to the distributed resource is determined from the at least one alternative control center, including: Based on the control latency corresponding to each alternative control center, an intermediate control center that meets the preset latency requirements is determined. Based on the intermediate control center, the target control center corresponding to the distributed resource is determined.

11. The method according to claim 10, characterized in that, Based on the intermediate control center, the target control center corresponding to the distributed resource is determined, including: When there is only one intermediate control center, the intermediate control center is designated as the target control center. When there are multiple intermediate control centers, obtain the resource control requirements corresponding to the distributed resources; Based on the resource management requirements, a target management center corresponding to the distributed resource is determined from multiple intermediate management centers.

12. A distributed resource management and control system, characterized in that, include: The resource management device, multiple distributed resources and multiple management centers are communicatively connected to the resource management device, wherein the management centers are used to manage one or more distributed resources; A resource management device is used to acquire the resource attributes and resource locations corresponding to each distributed resource; based on the resource attributes and / or resource locations, determine at least one alternative management center from multiple management centers for managing the distributed resources; determine the management latency corresponding to each of the at least one alternative management center; and based on the management latency corresponding to each of the at least one alternative management center, determine a target management center corresponding to the distributed resource from the at least one alternative management center. The target control center is connected to the distributed resources and is used to control the distributed resources.

13. An electronic device, characterized in that, include: A memory and a processor; wherein the memory is used to store one or more computer instructions, wherein the one or more computer instructions, when executed by the processor, implement the method as described in any one of claims 1-11.

14. A computer program product, characterized in that, include: A computer program, when executed by a processor of an electronic device, causes the processor to perform the steps of the method of any one of claims 1-11.

Images