Capability orchestration method, apparatus, system, electronic device, and storage medium

Abstract

This invention provides a capability orchestration method, apparatus, system, electronic device, and storage medium, relating to the field of computing power networks. The method includes: selecting all capabilities to be evaluated from a capability library based on business requirements; connecting all preceding and following nodes of any node containing a capability to be evaluated to construct an evaluation process corresponding to that capability; traversing each capability to be evaluated to obtain all evaluation processes, and determining the target evaluation process identified from all evaluation processes as the capability orchestration result for business requirements; the capability library includes all atomic capabilities with capability tag attributes and applicable scenario attributes that meet different business requirements, as well as all combined capabilities with capability tag attributes and applicable scenario attributes. This invention achieves flexibility and continuity in orchestration through real-time perception, intent analysis, and dynamic orchestration, meeting the business needs of diverse scenarios.

Description

Technical Field

[0001] This invention relates to the field of computing power networks, and more particularly to a capability orchestration method, apparatus, system, electronic device, and storage medium. Background Technology

[0002] In computing networks managed by computing network operating systems, computing power heterogeneity is becoming increasingly diversified, and usage scenarios are changing. Especially in computing network scenarios, business scenarios are inexhaustible. Traditional static orchestration methods have limited support capabilities for cross-regional and cross-domain applications, and cannot adapt well to the diversification of business scenarios or flexibly cope with complex and uncertain environmental requirements. Summary of the Invention

[0003] This invention provides a capability orchestration method, apparatus, system, electronic device, and storage medium to address the inability of existing technologies to meet the complex scenario requirements of computing power networks. This invention solves the problems faced by static orchestration, such as fixed process templates, inability to respond to new services in a timely manner, and high difficulty in cross-domain operations, through dynamic orchestration, while meeting the needs of cross-regional and cross-domain multi-dimensional computing power orchestration in computing power network scenarios.

[0004] In a first aspect, the present invention provides a capability orchestration method, comprising:

[0005] Select all capabilities to be evaluated from the capability library based on business needs;

[0006] Connect all preceding nodes and all following nodes of any node containing a capability to be evaluated to construct an evaluation process corresponding to the capability to be evaluated.

[0007] Iterate through each capability to be evaluated, obtain all processes to be evaluated, and determine the target evaluation process from all processes to be evaluated as the capability orchestration result of the business requirement.

[0008] The capability library includes all atomic capabilities with capability tag attributes and applicable scenario attributes that meet different business needs, as well as all combined capabilities with capability tag attributes and applicable scenario attributes.

[0009] All the preceding nodes are determined by traversing backwards from the capability library based on the preceding conditions of the capability to be evaluated, with the capability to be evaluated as the current node. All the following nodes are determined by traversing backwards from the capability library based on the following conditions of the capability to be evaluated, with the capability to be evaluated as the current node.

[0010] According to the capability orchestration method provided by the present invention, before selecting all capabilities to be evaluated from the capability library based on business needs, the method further includes:

[0011] In response to a demand event, determine the orchestration request corresponding to the demand event;

[0012] Analyze the orchestration request to obtain the business requirements corresponding to the demand event;

[0013] The demand events include both internal and external events;

[0014] The internal events include scaling up, scaling down, migration, and configuration changes;

[0015] The external events include user order requests.

[0016] According to the capability orchestration method provided by the present invention, before selecting all capabilities to be evaluated from the capability library based on business needs, the method includes:

[0017] Determine the corresponding ability definition attributes for different types of abilities;

[0018] Based on the capability definition attributes of any capability, the capability is encapsulated into a service interface;

[0019] Traverse all capabilities to determine the service interface corresponding to each capability, and publish the service interface corresponding to all capabilities in the capability library;

[0020] The different types of abilities include atomic abilities, combination abilities, transformation abilities, and auxiliary abilities;

[0021] The capability definition attributes corresponding to the atomic capabilities and the combined capabilities include capability description, capability tag, applicable scenarios, input parameter description, output parameter description, preconditions, test cases, usage examples, call address, and preset definition attributes;

[0022] The capability definition attributes corresponding to the transformation capability include capability description, capability tag, applicable scenarios, input parameter description, output parameter description, usage examples, and calling address;

[0023] The capability definition attributes corresponding to the auxiliary capabilities include capability description, capability tag, applicable scenarios, data format, and data content.

[0024] According to the capability orchestration method provided by the present invention, the step of connecting all preceding nodes and all following nodes of any node containing a capability to be evaluated includes:

[0025] If any subsequent node forms a node loop with the preceding node, an execution node is created and connected to the preceding node to eliminate the node loop.

[0026] The execution node is determined based on the necessary execution conditions of the preceding node before the subsequent node.

[0027] According to the capability orchestration method provided by the present invention, the step of determining the target evaluation process identified from all the processes to be evaluated as the capability orchestration result of the business requirement includes:

[0028] Run any process to be evaluated to obtain the running status of the process;

[0029] The capability health assessment result and the pre-condition rule assessment result of the process to be assessed are calculated based on the operation status of the process to be assessed.

[0030] The final evaluation result of the process to be evaluated is determined based on the results of the capability health assessment and the results of the preliminary rule assessment.

[0031] Traverse all processes to be evaluated, obtain all final evaluation results, determine the target evaluation process based on all final evaluation results, and determine the target evaluation process as the capability orchestration result of the business requirement;

[0032] The capability health assessment results are determined based on the running status, total number of calls, average daily number of calls, average daily number of failures, average success rate, average response time, maximum response time, CPU utilization, memory utilization, and number of replicas.

[0033] The evaluation results of the pre-evaluation rules are determined based on the degree of integration and the degree of matching of each capability in the process to be evaluated.

[0034] The degree of integration is determined based on the waiting time and running time of each capability with its adjacent preceding and following nodes during the scheduling process.

[0035] The matching degree is determined based on the data transformation magnitude of each capability with its adjacent preceding and following nodes during the capability orchestration process.

[0036] According to the capability orchestration method provided by the present invention, before running any process to be evaluated, it further includes:

[0037] The process to be evaluated is scheduled to a computing power node to obtain the execution result of the computing power node;

[0038] If the execution result is successful, the process to be evaluated is run.

[0039] If the execution result is unsuccessful, reconnect all the preceding nodes and all the following nodes of the node containing the capability to be evaluated.

[0040] Secondly, a capability orchestration system is also provided, including an orchestration hub, a coordinator, and multiple orchestration branches;

[0041] The orchestration center and the multiple orchestration branches achieve operational state synchronization and execution rule synchronization through the coordinator;

[0042] The capability orchestration system further includes a memory and programs or instructions stored in the memory and executable on the orchestration hub. When the program or instructions are executed by the orchestration hub, the capability orchestration method is executed. The method includes: selecting all capabilities to be evaluated from the capability library according to business requirements; connecting all predecessor nodes and all successor nodes of any node containing the capability to be evaluated to construct an evaluation process corresponding to the capability to be evaluated; traversing each capability to be evaluated, obtaining all evaluation processes, and determining the target evaluation process determined from all evaluation processes as the capability orchestration result of the business requirements. The capability library includes all atomic capabilities that meet different business requirements and have capability tag attributes and applicable scenario attributes, as well as all combined capabilities that have capability tag attributes and applicable scenario attributes. All predecessor nodes are determined by traversing the capability library backward based on the prerequisite conditions of the capability to be evaluated, with the capability to be evaluated as the current node. All successor nodes are determined by traversing the capability library backward based on the prerequisite conditions of the capability to be evaluated, with the capability to be evaluated as the current node.

[0043] Thirdly, a capability orchestration apparatus is also provided, comprising:

[0044] Filtering unit: Used to filter all capabilities to be evaluated from the capability library based on business needs;

[0045] Construction Unit: Used to connect all preceding nodes and all following nodes of any node containing a capability to be evaluated, in order to construct the evaluation process corresponding to the capability to be evaluated;

[0046] Determining Unit: Used to traverse each capability to be evaluated, obtain all processes to be evaluated, and determine the target evaluation process determined from all processes to be evaluated as the capability orchestration result of the business requirement;

[0047] The capability library includes all atomic capabilities with capability tag attributes and applicable scenario attributes that meet different business needs, as well as all combined capabilities with capability tag attributes and applicable scenario attributes.

[0048] All the preceding nodes are determined by traversing backwards from the capability library based on the preceding conditions of the capability to be evaluated, with the capability to be evaluated as the current node. All the following nodes are determined by traversing backwards from the capability library based on the following conditions of the capability to be evaluated, with the capability to be evaluated as the current node.

[0049] Fourthly, an electronic device is also provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the capability orchestration method when executing the program.

[0050] Fifthly, a non-transitory computer-readable storage medium is also provided, on which a computer program is stored, which, when executed by a processor, implements the capability orchestration method.

[0051] This invention provides a capability orchestration method, apparatus, system, electronic device, and storage medium. By defining and encapsulating capability types, a capability library is constructed. Then, based on different business needs, all capabilities to be evaluated are selected from the capability library. By connecting all preceding and following nodes of any node containing a capability to be evaluated, dynamic orchestration of the process to be evaluated is achieved. Finally, based on capability evaluation and selection, the target evaluation process determined from all the processes to be evaluated is identified as the capability orchestration result for the business requirement. This invention achieves flexibility and continuity in orchestration through real-time perception, intent analysis, dynamic orchestration, and automatic scheduling, meeting the business needs of diverse scenarios. Attached Figure Description

[0052] To more clearly illustrate the technical solutions in this invention 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 invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0053] Figure 1 This is one of the flowcharts illustrating the capability orchestration method provided by the present invention;

[0054] Figure 2 This is the second flowchart illustrating the capability orchestration method provided by the present invention;

[0055] Figure 3 This is the third flowchart illustrating the capability orchestration method provided by the present invention;

[0056] Figure 4 This is a flowchart illustrating the capability orchestration results for determining the business requirements provided by the present invention;

[0057] Figure 5 This is the fourth flowchart illustrating the capability orchestration method provided by the present invention;

[0058] Figure 6 This is a schematic diagram of the structure of the evaluation process corresponding to the capability to be evaluated provided by the present invention;

[0059] Figure 7 This is a schematic diagram of the capability orchestration system provided by the present invention;

[0060] Figure 8 This is a schematic diagram of the capability orchestration device provided by the present invention;

[0061] Figure 9 This is a schematic diagram of the structure of the electronic device provided by the present invention. Detailed Implementation

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

[0063] Currently popular orchestration technologies are generally based on static orchestration. Static orchestration uses a design center to design reusable models, capabilities, and actions. The orchestration center then orchestrates capabilities and actions according to business scenario requirements to achieve process orchestration. Finally, the strategy center formulates relevant scheduling strategies to execute different process templates. Therefore, the processes, actions, and strategies of static orchestration all need to be configured in advance. During the pre-configuration, the business scenarios to be met need to be manually identified. Then, based on the specific requirements of the business scenario, fixed process templates are pre-drawn by manual drag-and-drop and published to the process template library. When the triggering conditions are met, the corresponding process is scheduled to be executed.

[0064] Static orchestration presents several challenges in practical applications, primarily: Firstly, it requires defining the business scenario and analyzing its requirements to select different capability components and create execution flow templates for scheduling. This necessitates manually redesigning a new flow template for each new scenario, leading to long deployment cycles. Furthermore, in computing network scenarios, the sheer number of business scenarios is overwhelming, making static orchestration ill-suited to the diverse and uncertain needs of these scenarios. Secondly, static orchestration typically involves only a single region or domain, offering limited support for cross-regional and cross-domain applications. The computing network operating system needs to connect to a wide range of diverse and heterogeneous computing resources, resulting in an exponential increase in the capability services involved in the orchestration hub, further lengthening the deployment cycle. While the rise of artificial intelligence and machine learning has introduced algorithms to assist capability selection, manual intervention for process creation is still required in orchestration.

[0065] To overcome the technical drawbacks of static orchestration in practical applications, this invention adopts a perception-based dynamic orchestration approach to meet the needs of business development. Figure 1 This is one of the flowcharts illustrating the capability orchestration method provided by the present invention. The present invention provides a capability orchestration method, including:

[0066] Select all capabilities to be evaluated from the capability library based on business needs;

[0067] Connect all preceding nodes and all following nodes of any node containing a capability to be evaluated to construct an evaluation process corresponding to the capability to be evaluated.

[0068] Iterate through each capability to be evaluated, obtain all processes to be evaluated, and determine the target evaluation process from all processes to be evaluated as the capability orchestration result of the business requirement.

[0069] The capability library includes all atomic capabilities with capability tag attributes and applicable scenario attributes that meet different business needs, as well as all combined capabilities with capability tag attributes and applicable scenario attributes.

[0070] All the preceding nodes are determined by traversing backwards from the capability library based on the preceding conditions of the capability to be evaluated, with the capability to be evaluated as the current node. All the following nodes are determined by traversing backwards from the capability library based on the following conditions of the capability to be evaluated, with the capability to be evaluated as the current node.

[0071] In step 101, all capabilities to be evaluated are selected from the capability library according to business requirements. The business requirements include at least the requirements for the capability's tag attributes and applicable scenario attributes. According to the following optional embodiments, multiple capabilities to be evaluated can be obtained, and then all capabilities to be evaluated can be selected from the capability library according to business requirements.

[0072] In an optional embodiment, if the tag attribute in the business requirement matches the capability tag attribute of a certain type of capability in the capability library, then the capability is determined to be a capability to be evaluated.

[0073] In another optional embodiment, if the applicable scenario attribute in the business requirement matches the applicable scenario attribute of a certain type of capability in the capability library, then the capability is determined to be a capability to be evaluated.

[0074] In another optional embodiment, if the tag attribute and applicable scenario attribute in the business requirement both match the tag attribute and applicable scenario attribute corresponding to a certain type of capability in the capability library, then the capability is determined to be a capability to be evaluated.

[0075] In another optional embodiment, a first correlation between the tag attribute in the business requirement and the tag attribute of a certain type of capability in the capability library can be determined, and a second correlation between the applicable scenario attribute in the business requirement and the applicable scenario attribute of a certain type of capability in the capability library can be determined. Capabilities whose product of the first correlation and the second correlation is greater than a preset correlation value are determined as capabilities to be evaluated.

[0076] The capability library includes all atomic capabilities with capability tag attributes and applicable scenario attributes that meet different business needs, as well as all combined capabilities with capability tag attributes and applicable scenario attributes. The capability library includes at least two types of capabilities: atomic capabilities and combined capabilities. Atomic capabilities are indivisible basic capabilities, such as applying for a virtual network card. Combined capabilities are large-granular capability modules composed of other capabilities, which meet the standard of capability definition and unified input and output.

[0077] Optionally, the classification of capabilities includes, but is not limited to, atomic capabilities, combinatorial capabilities, transformation capabilities, and auxiliary capabilities. The transformation capability refers to the transformation of data, such as data format conversion, data type conversion, and data structure mapping. The auxiliary capabilities are added as additional attributes to atomic capabilities, combinatorial capabilities, and transformation capabilities, providing additional parameters or data, and cannot be executed independently.

[0078] In step 102, all predecessor nodes and all successor nodes of any node containing a capability to be evaluated are connected to construct an evaluation process corresponding to the capability to be evaluated. In such an embodiment, all predecessor nodes are determined by traversing backward from the capability library based on the capability to be evaluated as the current node and the prerequisites of the capability to be evaluated. Each capability attribute of the capability to be evaluated includes its prerequisites, that is, the prerequisite capability nodes that need to be completed to realize the capability node to be evaluated. After obtaining the prerequisite capability node, it is determined whether there are any preceding prerequisite capability nodes based on the prerequisite capability node, and then traversing backward in sequence. The known capability nodes are traversed and their prerequisite capability nodes are filtered according to their prerequisites and capability evaluation data. The execution order is set to the current capability node order minus 1. If the current node order number is 0, then the order number of the prerequisite capability node is less than 0. The prerequisite nodes are traversed recursively until there are no prerequisites, that is, the prerequisites of the capability currently being traversed are empty, which is the starting prerequisite node. The execution order is to execute sequentially from the starting prerequisite node to the node containing the capability to be evaluated according to the order number.

[0079] All subsequent nodes are determined by traversing the capability library backwards based on the subsequent conditions of the capability to be evaluated, with the capability to be evaluated as the current node. Similar to the method for determining the preceding nodes, in this embodiment, all subsequent nodes are determined by traversing the capability library backwards based on the subsequent conditions of the capability to be evaluated, with the capability to be evaluated as the current node. Each capability attribute of the capability to be evaluated includes its subsequent conditions, i.e., the subsequent capability nodes that need to be completed to achieve the capability node to be evaluated. After obtaining the subsequent capability nodes, based on the subsequent conditions... A capability node determines whether it has subsequent capability nodes, and then traverses sequentially. When traversing a known capability node, it filters its subsequent capability nodes based on its postconditions and capability evaluation data, and sets the execution order to the current capability node's sequence number plus 1. If the current node's sequence number is 0, then the sequence number of the subsequent capability node is greater than 0. The subsequent nodes are traversed recursively until there are no postconditions, that is, the postconditions of the capability being traversed are empty, which is the end of the preceding node. The execution order is to execute sequentially from the node where the capability to be evaluated is located to the end of the subsequent node according to the sequence number.

[0080] Optionally, all preceding nodes and all following nodes of any node containing a capability to be evaluated are connected. The execution order of the evaluation process corresponding to the capability to be evaluated is the entire process executed sequentially according to the sequence number, from the preceding node to the node containing the capability to be evaluated, and from the node containing the capability to be evaluated to the following node.

[0081] In step 103, each capability to be evaluated is traversed to obtain all processes to be evaluated. The target evaluation process determined from all the processes to be evaluated is determined as the capability orchestration result of the business requirement. In step 101, multiple capabilities to be evaluated were obtained. In step 102, a corresponding process to be evaluated was determined for any capability to be evaluated. In step 103, each capability to be evaluated is traversed to obtain all processes to be evaluated. There are many methods to determine the target evaluation process from all the processes to be evaluated. For example, any process to be evaluated can be randomly determined as the capability orchestration result of the business requirement. Another example is to issue and schedule all processes to be evaluated, and determine the capability orchestration result of the business requirement from the executable processes to be evaluated. Yet another example is to input all processes to be evaluated into the running evaluation model, determine the optimal process to be evaluated based on the running evaluation model, and determine the optimal process to be evaluated as the capability orchestration result of the business requirement.

[0082] Optionally, the connection between all preceding nodes and all following nodes of any node containing the capability to be evaluated includes:

[0083] If any subsequent node forms a node loop with the preceding node, an execution node is created and connected to the preceding node to eliminate the node loop.

[0084] The execution node is determined based on the necessary execution conditions of the preceding node before the subsequent node.

[0085] In such an embodiment, all preceding and following nodes of any node containing a capability to be evaluated are connected. Based on the execution order, each preceding and following capability node is configured serially, in parallel, or through branches. Transformation capabilities are added according to parameter mapping needs, and auxiliary capabilities are added according to capability configuration needs. In dynamic orchestration, it is not necessary to forcibly merge multiple processes into one; instead, multiple independent process branches can exist. These independent process branches are all issued and executed as part of the overall orchestration process. Each process branch is analyzed, and loops are eliminated by adding corresponding execution nodes, ultimately generating multiple directed acyclic graphs, such as... Figure 6 As shown, Figure 6 This is a schematic diagram of the structure of the evaluation process corresponding to the capability to be evaluated provided by the present invention. The present invention eliminates node loops by creating execution nodes and connecting the execution nodes with the preceding nodes. The main function of adding execution nodes in the present invention is to add an additional execution node to remove the dependency relationship of the loop, so that a loop becomes multiple preceding capability branches, such as by adding an additional preceding capability node or an auxiliary capability to provide the necessary execution conditions.

[0086] Optionally, after parsing the orchestration requirement parameters, the present invention fills in the input parameters of each node according to the input parameter requirements of the capability nodes. The orchestration requirement parameters include, but are not limited to, specification requirements, regional requirements, security requirements, and performance requirements.

[0087] The demands of current business are becoming increasingly agile and flexible. In particular, the deepening of computing power networks in business scenarios has prompted the deep integration of existing technologies such as computing power, network, data, and artificial intelligence. As a central component of the computing power network operating system, orchestration also needs to become more agile and flexible to meet the needs of business development. This invention achieves orchestration and scheduling of diverse heterogeneous computing power in computing power network scenarios through operations such as capability release, real-time perception, capability matching, dynamic orchestration, automatic scheduling, and operation evaluation, thereby meeting the orchestration needs of diverse scenarios.

[0088] This invention provides a capability orchestration method, apparatus, system, electronic device, and storage medium. By defining and encapsulating capability types, a capability library is constructed. Then, based on different business needs, all capabilities to be evaluated are selected from the capability library. By connecting all preceding and following nodes of any node containing a capability to be evaluated, dynamic orchestration of the process to be evaluated is achieved. Finally, based on capability evaluation and selection, the target evaluation process determined from all the processes to be evaluated is identified as the capability orchestration result for the business requirement. This invention achieves flexibility and continuity in orchestration through real-time perception, intent analysis, dynamic orchestration, and automatic scheduling, meeting the business needs of diverse scenarios.

[0089] Figure 2 This is the second flowchart of the capability orchestration method provided by the present invention. Before selecting all capabilities to be evaluated from the capability library according to business needs, it also includes:

[0090] In response to a demand event, determine the orchestration request corresponding to the demand event;

[0091] Analyze the orchestration request to obtain the business requirements corresponding to the demand event;

[0092] The demand events include both internal and external events;

[0093] The internal events include scaling up, scaling down, migration, and configuration changes;

[0094] The external events include user order requests.

[0095] In step 201, the present invention adopts a real-time sensing method to respond to the demand events in real time, analyzes orchestration requests, and starts the orchestration process. A connection is established between the daemon process and the sensing center to receive orchestration requests in real time. The demand events include internal events and external events. The internal events include scaling up, scaling down, migration, and configuration changes. The external events include user order demands.

[0096] In step 202, the orchestration request is analyzed to obtain the business requirements corresponding to the demand event. This invention can analyze the orchestration request in real time through the relevant rules of intent policy and machine learning algorithms, construct a demand analysis model, and input the orchestration request into the demand analysis model to obtain the business requirements output by the demand analysis model.

[0097] Figure 3 This is the third flowchart of the capability orchestration method provided by the present invention. Before selecting all capabilities to be evaluated from the capability library according to business needs, it includes:

[0098] Determine the corresponding ability definition attributes for different types of abilities;

[0099] Based on the capability definition attributes of any capability, the capability is encapsulated into a service interface;

[0100] Traverse all capabilities to determine the service interface corresponding to each capability, and publish the service interface corresponding to all capabilities in the capability library;

[0101] The different types of abilities include atomic abilities, combination abilities, transformation abilities, and auxiliary abilities;

[0102] The capability definition attributes corresponding to the atomic capabilities and the combined capabilities include capability description, capability tag, applicable scenarios, input parameter description, output parameter description, preconditions, test cases, usage examples, call address, and preset definition attributes;

[0103] The capability definition attributes corresponding to the transformation capability include capability description, capability tag, applicable scenarios, input parameter description, output parameter description, usage examples, and calling address;

[0104] The capability definition attributes corresponding to the auxiliary capabilities include capability description, capability tag, applicable scenarios, data format, and data content.

[0105] In step 301, the capability definition attributes corresponding to different types of capabilities are determined. The capability definition is a static attribute definition of the capability. The main fields of atomic capabilities and composite capabilities include capability description, capability tag, applicable scenario, input parameter description, output parameter description, preconditions, test cases, usage examples, call address, and other custom attributes. The main fields of transformation capabilities include capability description, capability tag, applicable scenario, input parameter description, output parameter description, usage examples, and scheduling address. Auxiliary capabilities include capability description, capability tag, applicable scenario, data format, and data content. Among them, capability tag and applicable scenario are the primary conditions for capability matching.

[0106] In step 302, based on the capability definition attributes of any capability, the capability is encapsulated into a service interface. The capability encapsulation encapsulates the capability into a service interface according to the requirements of the capability definition. In addition, each capability, especially atomic capabilities and composite capabilities, must provide both forward and reverse operations. The forward operation is used for execution, while the reverse operation is used for rollback.

[0107] In step 303, all capabilities are traversed to determine the service interface corresponding to each capability, so as to publish the service interfaces corresponding to all capabilities in the capability library. Publishing the service interfaces corresponding to all capabilities means that standardized capabilities are published to the production environment through an audit process. Through the standardized management of capability publication, all capabilities have a standard structure and necessary parameters, and are in an audited state.

[0108] Figure 4 This is a flowchart illustrating the process of determining the capability orchestration result for the business requirement provided by the present invention. The step of determining the target evaluation process from all processes to be evaluated as the capability orchestration result for the business requirement includes:

[0109] Run any process to be evaluated to obtain the running status of the process;

[0110] The capability health assessment result and the pre-condition rule assessment result of the process to be assessed are calculated based on the operation status of the process to be assessed.

[0111] The final evaluation result of the process to be evaluated is determined based on the results of the capability health assessment and the results of the preliminary rule assessment.

[0112] Traverse all processes to be evaluated, obtain all final evaluation results, determine the target evaluation process based on all final evaluation results, and determine the target evaluation process as the capability orchestration result of the business requirement;

[0113] The capability health assessment results are determined based on the running status, total number of calls, average daily number of calls, average daily number of failures, average success rate, average response time, maximum response time, CPU utilization, memory utilization, and number of replicas.

[0114] The evaluation results of the pre-evaluation rules are determined based on the degree of integration and the degree of matching of each capability in the process to be evaluated.

[0115] The degree of integration is determined based on the waiting time and running time of each capability with its adjacent preceding and following nodes during the scheduling process.

[0116] The matching degree is determined based on the data transformation magnitude of each capability with its adjacent preceding and following nodes during the capability orchestration process.

[0117] In step 401, any process to be evaluated is run to obtain the running status of the process to be evaluated. The running evaluation tracks the running status of each capability in the process to be evaluated in real time and evaluates the running status of each capability, mainly including capability health evaluation and pre-rule evaluation. The running status includes running status, such as normal status, abnormal status or offline status, total number of calls, average number of calls per day, average number of failures per day, average success rate, average response time, maximum response time, CPU utilization, memory utilization, number of replicas, waiting time for specific capabilities and their upstream and downstream connections during process scheduling, running time, degree of data transformation required for upstream and downstream capabilities during data flow in the orchestration process, etc.

[0118] In step 402, the capability health assessment result and the pre-evaluation rule assessment result of the process to be evaluated are calculated based on the operation status of the process to be evaluated. The capability health assessment mainly analyzes the health status of capabilities based on historical operational data, such as operating status, total number of calls, average daily number of calls, average daily number of failures, average success rate, average response time, maximum response time, CPU utilization, memory utilization, and number of replicas. The assessment algorithms for different capability tags are specified through the rule setting interface according to the above-mentioned health assessment calculation rules. Through the capability health assessment, capabilities can be sorted and filtered based on their health status, and the optimal capability solutions that meet the conditions are selected.

[0119] The aforementioned pre-configuration rule evaluation mainly assesses the selected pre-configuration capabilities during dynamic capability orchestration, including integration degree and matching degree. The integration degree is mainly calculated by analyzing and calculating the waiting time and running time of specific capabilities and their upstream and downstream connections during process scheduling. The matching degree is mainly the degree to which upstream and downstream capabilities in the orchestration process need to undergo data transformation during data flow. Optionally, capability combinations with higher integration and matching degrees will be given priority for use as combined capabilities. Capability evaluation mainly provides data support for capability selection through quantitative analysis of capabilities.

[0120] In step 403, the final evaluation result of the process to be evaluated is determined based on the capability health assessment result and the prerequisite rule assessment result. In one optional embodiment, the product of the capability health assessment result and the prerequisite rule assessment result is determined as the final evaluation result of the process to be evaluated. In another optional embodiment, the final evaluation result of the process to be evaluated is determined based on a weighted average algorithm.

[0121] In another alternative embodiment, the present invention can select the optimal capability based on operational evaluation. The selection criteria are capability health assessment results, integration degree, and matching degree. As a selection method, combined capabilities take precedence over multiple atomic capabilities, and verified capabilities are superior to unverified capabilities. This stage mainly selects atomic capabilities and combined capabilities, while transformation capabilities and auxiliary capabilities are automatically extracted according to business and process needs during dynamic orchestration.

[0122] In step 404, all processes to be evaluated are traversed, and all final evaluation results are obtained according to the methods in steps 401 to 403. The target evaluation process is determined based on all the final evaluation results, and the target evaluation process is determined as the capability orchestration result of the business requirement. In such an embodiment, after obtaining all the final evaluation results, the process to be evaluated corresponding to the final evaluation result with the highest value among the final evaluation results is determined as the target evaluation process, and the target evaluation process is determined as the capability orchestration result of the business requirement.

[0123] Optionally, before running any process to be evaluated, the following is also included:

[0124] The process to be evaluated is scheduled to a computing power node to obtain the execution result of the computing power node;

[0125] If the execution result is successful, the process to be evaluated is run.

[0126] If the execution result is unsuccessful, reconnect all the preceding nodes and all the following nodes of the node containing the capability to be evaluated.

[0127] Those skilled in the art will understand that automatic scheduling mainly involves issuing and scheduling the execution of processes based on the capability orchestration results. The process is issued to relevant computing power nodes for execution through task scheduling management, and the success or failure of execution is determined based on the execution result. If the execution result is unsuccessful, the result is fed back to the orchestration center, which then reconnects all preceding and following nodes of the node containing the capability to be evaluated. The orchestration center adjusts the orchestration process based on the error content, determines the capability orchestration result, and issues the process again. If the execution result is successful, the process to be evaluated is run.

[0128] In an optional embodiment, if the number of reconnections or the number of failed responses exceeds the maximum limit for the number of failures, the entire process fails, the executed tasks are rolled back, and the orchestration center is notified for further processing, such as generating an intervention instruction to instruct the application for manual intervention.

[0129] Figure 5This is the fourth flowchart of the capability orchestration method provided by the present invention. The present invention constructs, improves and updates the capability library through capability release, so that after real-time perception of orchestration requirements, capability identification is provided based on capability matching. After selecting the capabilities to be evaluated from the capability library, dynamic orchestration is performed, and the process to be evaluated determined according to the capabilities to be evaluated is input into the runtime library for automatic scheduling and process distribution. If the scheduling feedback result is not satisfactory, dynamic orchestration is performed again. If the scheduling feedback result is satisfactory, the process to be evaluated is further input into the evaluation library to obtain the running status output by the evaluation library, and then the capability orchestration result of the business requirement is determined based on the running status.

[0130] Optionally, the dynamic orchestration under the computing power network operating system first processes the orchestratable capabilities into services and application interfaces to build a capability library, standardizes the capability model, including entry format, exit format, preconditions, etc., and performs unified registration, review, release and management of capabilities; then, by analyzing business needs and real-time perceived business and resource status, it dynamically identifies capability services that meet the conditions through matching according to certain rules and strategies, and can also use artificial intelligence algorithms to assist in identification; then, the orchestration center automatically assembles the matched capability services into an executable process model based on the identification results and screening algorithms, and distributes it after passing the execution simulation test; finally, the scheduling center automatically schedules each computing power node to execute the relevant capability services to complete the business or resource changes.

[0131] This invention standardizes and decomposes capabilities through real-time dynamic orchestration based on perception, and then automatically analyzes and dynamically combines them according to the needs of business scenarios. Except in abnormal situations, no manual intervention is required, reducing labor costs. Dynamic orchestration greatly shortens the time for manually selecting service capabilities and drawing process templates, and shortens the launch cycle of new services from the original time cycle of weeks to the current time cycle of minutes or even seconds. As capabilities and operational evaluations are continuously learned and improved, the activation of highly similar services will become increasingly convenient.

[0132] Figure 7 This is a schematic diagram of the capability orchestration system provided by the present invention. The present invention provides a capability orchestration system, including an orchestration center 1, a coordinator 2, and multiple orchestration branches 3;

[0133] The orchestration center 1 and the multiple orchestration branches 3 achieve operational state synchronization and execution rule synchronization through the coordinator 2;

[0134] It also includes a memory and programs or instructions stored in the memory and executable on the orchestration hub 1. When the program or instructions are executed by the orchestration hub 1, the capability orchestration method is executed. The method includes: selecting all capabilities to be evaluated from the capability library according to business requirements; connecting all predecessor nodes and all successor nodes of any node containing the capability to be evaluated to construct an evaluation process corresponding to the capability to be evaluated; traversing each capability to be evaluated, obtaining all evaluation processes, and determining the target evaluation process determined from all evaluation processes as the capability orchestration result of the business requirements; the capability library includes all atomic capabilities that meet different business requirements and have capability tag attributes and applicable scenario attributes, as well as all combined capabilities that have capability tag attributes and applicable scenario attributes; all predecessor nodes are determined by traversing forward from the capability library based on the prerequisite conditions of the capability to be evaluated, with the capability to be evaluated as the current node; all successor nodes are determined by traversing backward from the capability library based on the prerequisite conditions of the capability to be evaluated, with the capability to be evaluated as the current node.

[0135] This invention realizes the cloud-edge integrated orchestration, cross-network orchestration, and cross-domain orchestration capabilities of the computing power network operating system through a dynamic orchestration distributed deployment method. It unifies the orchestration and scheduling of cross-regional central cloud, edge cloud, and other heterogeneous computing power such as intelligent computing and supercomputing. It adopts a collaborative approach between the orchestration hub and orchestration branches, with the orchestration hub responsible for centralized perception analysis and global process orchestration, and the orchestration branches responsible for the sub-process orchestration of their respective regions.

[0136] Figure 8 This is a schematic diagram of the capability orchestration device provided by the present invention. The present invention provides a capability orchestration device, including a screening unit 41: used to screen all capabilities to be evaluated from the capability library according to business needs. The working principle of the screening unit 41 can be referred to the aforementioned step 101, and will not be repeated here.

[0137] The capability orchestration device further includes a construction unit 42: used to connect all the preceding nodes and all the following nodes of any node where the capability to be evaluated is located, so as to construct the evaluation process corresponding to the capability to be evaluated. The working principle of the construction unit 42 can be referred to the aforementioned step 102, and will not be repeated here.

[0138] The capability orchestration device further includes a determination unit 43: used to traverse each capability to be evaluated, obtain all processes to be evaluated, and determine the target evaluation process determined from all processes to be evaluated as the capability orchestration result of the business requirement. The working principle of the determination unit 43 can be referred to the aforementioned step 103, and will not be repeated here.

[0139] The capability library includes all atomic capabilities with capability tag attributes and applicable scenario attributes that meet different business needs, as well as all combined capabilities with capability tag attributes and applicable scenario attributes.

[0140] All the preceding nodes are determined by traversing backwards from the capability library based on the preceding conditions of the capability to be evaluated, with the capability to be evaluated as the current node. All the following nodes are determined by traversing backwards from the capability library based on the following conditions of the capability to be evaluated, with the capability to be evaluated as the current node.

[0141] This invention provides a capability orchestration method, apparatus, system, electronic device, and storage medium. By defining and encapsulating capability types, a capability library is constructed. Then, based on different business needs, all capabilities to be evaluated are selected from the capability library. By connecting all preceding and following nodes of any node containing a capability to be evaluated, dynamic orchestration of the process to be evaluated is achieved. Finally, based on capability evaluation and selection, the target evaluation process determined from all the processes to be evaluated is identified as the capability orchestration result for the business requirement. This invention achieves flexibility and continuity in orchestration through real-time perception, intent analysis, dynamic orchestration, and automatic scheduling, meeting the business needs of diverse scenarios.

[0142] Figure 9 This is a schematic diagram of the structure of the electronic device provided by the present invention. For example... Figure 9 As shown, the electronic device may include: a processor 910, a communication interface 920, a memory 930, and a communication bus 940, wherein the processor 910, the communication interface 920, and the memory 930 communicate with each other through the communication bus 940. The processor 910 can call logical instructions in the memory 930 to execute a capability orchestration method, which includes: selecting all capabilities to be evaluated from a capability library according to business requirements; connecting all predecessor nodes and all successor nodes of any node containing a capability to be evaluated to construct an evaluation process corresponding to the capability to be evaluated; traversing each capability to be evaluated, obtaining all evaluation processes, and determining the target evaluation process determined from all evaluation processes as the capability orchestration result of the business requirements; the capability library includes all atomic capabilities that meet different business requirements and have capability tag attributes and applicable scenario attributes, as well as all combined capabilities that have capability tag attributes and applicable scenario attributes; all predecessor nodes are determined by traversing forward from the capability library based on the prerequisite conditions of the capability to be evaluated, with the capability to be evaluated as the current node; all successor nodes are determined by traversing backward from the capability library based on the prerequisite conditions of the capability to be evaluated, with the capability to be evaluated as the current node.

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

[0144] On the other hand, the present invention also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute a capability orchestration method provided by the above methods. The method includes: selecting all capabilities to be evaluated from a capability library according to business requirements; connecting all predecessor nodes and all successor nodes of any node containing a capability to be evaluated to construct an evaluation process corresponding to the capability to be evaluated; traversing each capability to be evaluated to obtain all evaluation processes, and determining the target evaluation process determined from all evaluation processes as the capability orchestration result of the business requirements; the capability library includes all atomic capabilities that meet different business requirements and have capability tag attributes and applicable scenario attributes, as well as all combined capabilities that have capability tag attributes and applicable scenario attributes; all predecessor nodes are determined by traversing forward from the capability library based on the prerequisite conditions of the capability to be evaluated, with the capability to be evaluated as the current node; all successor nodes are determined by traversing backward from the capability library based on the successor conditions of the capability to be evaluated, with the capability to be evaluated as the current node.

[0145] In another aspect, the present invention also provides a non-transitory computer-readable storage medium storing a computer program thereon. When executed by a processor, the computer program implements the capability orchestration method provided by the above methods. The method includes: selecting all capabilities to be evaluated from a capability library according to business requirements; connecting all predecessor nodes and all successor nodes of any node containing a capability to be evaluated to construct an evaluation process corresponding to the capability to be evaluated; traversing each capability to be evaluated, obtaining all evaluation processes, and determining the target evaluation process determined from all evaluation processes as the capability orchestration result of the business requirements; the capability library includes all atomic capabilities that meet different business requirements and have capability tag attributes and applicable scenario attributes, as well as all combined capabilities that have capability tag attributes and applicable scenario attributes; all predecessor nodes are determined by traversing forward from the capability library based on the prerequisite conditions of the capability to be evaluated, with the capability to be evaluated as the current node; all successor nodes are determined by traversing backward from the capability library based on the prerequisite conditions of the capability to be evaluated, with the capability to be evaluated as the current node.

[0146] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the 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.

[0147] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. 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 software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0148] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention 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 of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A capability orchestration method, characterized in that, include: Select all capabilities to be evaluated from the capability library based on business needs; Connect all preceding nodes and all following nodes of any node containing a capability to be evaluated to construct an evaluation process corresponding to the capability to be evaluated. Iterate through each capability to be evaluated, obtain all processes to be evaluated, and determine the target evaluation process from all processes to be evaluated as the capability orchestration result of the business requirement. The capability library includes all atomic capabilities with capability tag attributes and applicable scenario attributes that meet different business needs, as well as all combined capabilities with capability tag attributes and applicable scenario attributes. Each capability attribute to be evaluated includes its preconditions and postconditions. All preconditions are determined by traversing backwards from the capability library based on the preconditions of the capability to be evaluated, with the capability to be evaluated as the current node. All postconditions are determined by traversing backwards from the capability library based on the postconditions of the capability to be evaluated, with the capability to be evaluated as the current node. The business requirements include at least requirements for capability tag attributes and applicable scenario attributes. The step of filtering all capabilities to be evaluated from the capability library based on business requirements includes: Based on the tag attributes and / or applicable scenario attributes in the business requirements, all capabilities to be evaluated are filtered from the capability library; The capability orchestration result, which determines the target evaluation process from all the processes to be evaluated as the business requirement, includes: Run any process to be evaluated to obtain the running status of the process; The capability health assessment result and the pre-condition rule assessment result of the process to be assessed are calculated based on the operation status of the process to be assessed. The final evaluation result of the process to be evaluated is determined based on the results of the capability health assessment and the results of the preliminary rule assessment. Traverse all processes to be evaluated, obtain all final evaluation results, determine the target evaluation process based on all final evaluation results, and determine the target evaluation process as the capability orchestration result of the business requirement; The capability health assessment results are determined based on the running status, total number of calls, average daily number of calls, average daily number of failures, average success rate, average response time, maximum response time, CPU utilization, memory utilization, and number of replicas. The evaluation results of the pre-evaluation rules are determined based on the degree of integration and the degree of matching of each capability in the process to be evaluated. The degree of integration is determined based on the waiting time and running time of each capability with its adjacent preceding and following nodes during the scheduling process. The matching degree is determined based on the data transformation magnitude of each capability with its adjacent preceding and following nodes during the capability orchestration process.

2. The capability orchestration method according to claim 1, characterized in that, Before selecting all capabilities to be evaluated from the capability library based on business needs, the process also includes: In response to a demand event, determine the orchestration request corresponding to the demand event; Analyze the orchestration request to obtain the business requirements corresponding to the demand event; The demand events include both internal and external events; The internal events include scaling up, scaling down, migration, and configuration changes; The external events include user order requests.

3. The capability orchestration method according to claim 1, characterized in that, Before selecting all capabilities to be evaluated from the capability library based on business needs, the process includes: Determine the corresponding ability definition attributes for different types of abilities; Based on the capability definition attributes of any capability, the capability is encapsulated into a service interface; Traverse all capabilities to determine the service interface corresponding to each capability, and publish the service interface corresponding to all capabilities in the capability library; The different types of abilities include atomic abilities, combination abilities, transformation abilities, and auxiliary abilities; The capability definition attributes corresponding to the atomic capabilities and the combined capabilities include capability description, capability tag, applicable scenarios, input parameter description, output parameter description, preconditions, test cases, usage examples, call address, and preset definition attributes; The capability definition attributes corresponding to the transformation capability include capability description, capability tag, applicable scenarios, input parameter description, output parameter description, usage examples, and calling address; The capability definition attributes corresponding to the auxiliary capabilities include capability description, capability tag, applicable scenarios, data format, and data content.

4. The capability orchestration method according to claim 1, characterized in that, The connection between all preceding nodes and all following nodes of any node containing the capability to be evaluated includes: If any subsequent node forms a node loop with the preceding node before it, an execution node is created and connected to the preceding node to eliminate the node loop. The execution node is determined based on the necessary execution conditions of the preceding node before the subsequent node.

5. The capability orchestration method according to claim 1, characterized in that, Before running any process to be evaluated, the following is also included: The process to be evaluated is scheduled to a computing power node to obtain the execution result of the computing power node; If the execution result is successful, the process to be evaluated is run. If the execution result is unsuccessful, reconnect all the preceding nodes and all the following nodes of the node containing the capability to be evaluated.

6. A capability orchestration system, characterized in that, This includes the orchestration center, coordinator, and multiple orchestration branches; The orchestration center and the multiple orchestration branches achieve operational state synchronization and execution rule synchronization through the coordinator; The capability orchestration system further includes a memory and a program or instruction stored in the memory and executable on the orchestration hub, wherein the program or instruction, when executed by the orchestration hub, performs the capability orchestration method as described in any one of claims 1 to 5.

7. A capability orchestration device, characterized in that, include: Filtering unit: Used to filter all capabilities to be evaluated from the capability library based on business needs; Construction Unit: Used to connect all preceding nodes and all following nodes of any node containing a capability to be evaluated, in order to construct the evaluation process corresponding to the capability to be evaluated; Determining Unit: Used to traverse each capability to be evaluated, obtain all processes to be evaluated, and determine the target evaluation process determined from all processes to be evaluated as the capability orchestration result of the business requirement; The capability library includes all atomic capabilities with capability tag attributes and applicable scenario attributes that meet different business needs, as well as all combined capabilities with capability tag attributes and applicable scenario attributes. Each capability attribute to be evaluated includes its preconditions and postconditions. All preconditions are determined by traversing backwards from the capability library based on the preconditions of the capability to be evaluated, with the capability to be evaluated as the current node. All postconditions are determined by traversing backwards from the capability library based on the postconditions of the capability to be evaluated, with the capability to be evaluated as the current node. The business requirements include at least requirements for capability tag attributes and applicable scenario attributes. The step of filtering all capabilities to be evaluated from the capability library based on business requirements includes: Based on the tag attributes and / or applicable scenario attributes in the business requirements, all capabilities to be evaluated are filtered from the capability library; The capability orchestration result, which determines the target evaluation process from all the processes to be evaluated as the business requirement, includes: Run any process to be evaluated to obtain the running status of the process; The capability health assessment result and the pre-condition rule assessment result of the process to be assessed are calculated based on the operation status of the process to be assessed. The final evaluation result of the process to be evaluated is determined based on the results of the capability health assessment and the results of the preliminary rule assessment. Traverse all processes to be evaluated, obtain all final evaluation results, determine the target evaluation process based on all final evaluation results, and determine the target evaluation process as the capability orchestration result of the business requirement; The capability health assessment results are determined based on the running status, total number of calls, average daily number of calls, average daily number of failures, average success rate, average response time, maximum response time, CPU utilization, memory utilization, and number of replicas. The evaluation results of the pre-evaluation rules are determined based on the degree of integration and the degree of matching of each capability in the process to be evaluated. The degree of integration is determined based on the waiting time and running time of each capability with its adjacent preceding and following nodes during the scheduling process. The matching degree is determined based on the data transformation magnitude of each capability with its adjacent preceding and following nodes during the capability orchestration process.

8. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the capability orchestration method as described in any one of claims 1 to 5.

9. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the capability orchestration method as described in any one of claims 1 to 5.

Images