A joint service orchestration method and device, electronic equipment and storage medium

Abstract

This application provides a joint service orchestration method, apparatus, electronic device, and storage medium. The method includes: sending a joint service orchestration request, causing a second operator to send a parameter request message to a first operator based on the joint service orchestration request; receiving the parameter request message; determining parameter data for a target service orchestration based on the parameter request message; sending the parameter data to the second operator, causing the second operator to determine the service to be executed and the computing resource pool information for the service to be executed based on the parameter data; the first operator executing other services to be executed in the target service orchestration and controlling the second operator to execute the services to be executed. This method meets the diverse service needs of users, provides a multi-operator joint service orchestration strategy, enhances the security of operators, and improves service orchestration efficiency and resource utilization.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method, apparatus, electronic device and storage medium for orchestrating joint services. Background Technology

[0002] With the rapid development of artificial intelligence, the demand for computing power has increased dramatically, directly impacting the application and deployment of AI services. A computing power network, a distributed computing network composed of multiple computing nodes, effectively solves the problem of high computing power demand. It can allocate and flexibly schedule computing, storage, and network resources on demand across the cloud, network, and edge. These nodes can provide services including firewalls, load balancing, and intrusion detection.

[0003] Typically, users require multiple, ordered services, thus placing high demands on service orchestration. Currently, in communication networks, the service orchestration strategy involves receiving service instance objects and service event objects from the service policy execution factory and updating the service store of the service policy orchestration factory. Then, based on a mapping table, it selects the operator access domain to link to the service event object; updates the service store of the operator access domain according to the linked service event object and the operator-specific service identifier; receives a first feedback dataset from the operator access domain; updates a second mapping table and sends a second feedback dataset to the service policy execution factory to complete the service policy orchestration. In this scheme, the requesting entity can link to multiple independent operators through switching rules to complete service orchestration.

[0004] However, existing methods still suffer from problems such as inefficient resource utilization and poor service orchestration. Summary of the Invention

[0005] This application provides a federated service orchestration method, apparatus, electronic device, and storage medium to solve the problems of unreasonable resource utilization and poor service orchestration efficiency in existing methods.

[0006] Firstly, this application provides a federated service orchestration method, applied to a first operating entity, including:

[0007] Send a joint service orchestration request to the second operator, so that the second operator sends a parameter request message to the first operator based on the joint service orchestration request. The joint service orchestration request is a request from the first operator to the second operator to perform the target service orchestration. The second operator and the first operator are different operators.

[0008] Receive parameter request message;

[0009] Based on the parameter request message, determine the parameter data for the target service orchestration. The parameter data includes the attribute parameters for the target service orchestration performed by the second operating entity.

[0010] The parameter data is sent to the second operating entity so that the second operating entity can determine the service to be executed and the computing power resource pool information of the service to be executed based on the parameter data. The service to be executed is the service in the target service orchestration, and the computing power resource pool information of the service to be executed includes the service information and service path of the service to be executed.

[0011] After the second operating entity determines the services to be executed and the computing resource pool information of the services to be executed based on the parameter data, the first operating entity executes other services to be executed in the target service orchestration and controls the second operating entity to execute the services to be executed.

[0012] Secondly, this application provides a federated service orchestration method, applied to a second operating entity, including:

[0013] Receive a joint service orchestration request sent by the first operating entity, which is the operating entity that performs the target service orchestration and is different from the operator of the second operating entity. The target service orchestration corresponds to the joint service orchestration request.

[0014] According to the joint service orchestration request, a parameter request message is sent to the first operating entity so that the first operating entity can send the target service orchestration parameter data to the second operating entity according to the parameter request message. The parameter data includes the attribute parameters of the second operating entity for the target service orchestration.

[0015] Based on the parameter data, determine the service to be executed and the computing resource pool information of the service to be executed. The service to be executed is the service in the target service orchestration, and the computing resource pool information of the service to be executed includes the service information and service path of the service to be executed.

[0016] After determining the service to be executed and the computing power resource pool information of the service to be executed, the system receives the instruction for the execution target service orchestration sent by the first operating entity. The instruction for the target service orchestration is used to control the first operating entity to execute other services to be executed in the target service orchestration and to control the second operating entity to execute the services to be executed.

[0017] Execute the service to be executed according to the instructions orchestrated by the target service.

[0018] Thirdly, this application provides a joint services orchestration apparatus, applied to a first operating entity, comprising:

[0019] The first sending module is used to send a joint service orchestration request to the second operator, so that the second operator can send a parameter request message to the first operator according to the joint service orchestration request. The joint service orchestration request is a request from the first operator to the second operator to perform target service orchestration. The second operator and the first operator are different operators.

[0020] The first receiving module is used to receive parameter request messages;

[0021] The first determining module is used to determine the parameter data of the target service orchestration based on the parameter request message. The parameter data includes the attribute parameters of the target service orchestration performed by the second operating entity.

[0022] The second sending module is used to send parameter data to the second operating entity so that the second operating entity can determine the service to be executed and the computing power resource pool information of the service to be executed based on the parameter data. The service to be executed is the service in the target service orchestration, and the computing power resource pool information of the service to be executed includes the service information and service path of the service to be executed.

[0023] The first execution module is used to execute other services in the target service orchestration after the second operating entity determines the service to be executed and the computing power resource pool information of the service to be executed based on the parameter data, and to control the second operating entity to execute the service to be executed.

[0024] Fourthly, this application provides a joint services orchestration apparatus for use in a second operating entity, comprising:

[0025] The second receiving module is used to receive the joint service orchestration request sent by the first operating entity. The first operating entity is the operating entity that performs the target service orchestration, and the operators of the first operating entity and the second operating entity are different. The target service orchestration corresponds to the joint service orchestration request.

[0026] The third sending module is used to send a parameter request message to the first operating entity according to the joint service orchestration request, so that the first operating entity can send the target service orchestration parameter data to the second operating entity according to the parameter request message. The parameter data includes the attribute parameters of the second operating entity for target service orchestration.

[0027] The second determining module is used to determine the service to be executed and the computing power resource pool information of the service to be executed based on the parameter data. The service to be executed is a service in the target service orchestration, and the computing power resource pool information of the service to be executed includes the service information and service path of the service to be executed.

[0028] The third receiving module is used to receive the execution target service orchestration instruction sent by the first operating entity after determining the service to be executed and the computing power resource pool information of the service to be executed. The execution target service orchestration instruction is used to control the first operating entity to execute other services to be executed in the target service orchestration and to control the second operating entity to execute the service to be executed.

[0029] The second execution module is used to execute the service to be executed according to the instructions orchestrated by the target service.

[0030] Fifthly, this application provides an electronic device, including: a processor, and a memory communicatively connected to the processor;

[0031] The memory stores instructions that the computer executes;

[0032] The processor executes computer execution instructions stored in memory to implement the joint services orchestration method of this application embodiment.

[0033] Sixthly, a computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the federated services orchestration method of the embodiments of this application.

[0034] This application provides a joint service orchestration method, apparatus, electronic device, and storage medium. The method involves sending a joint service orchestration request to a second operating entity, which in turn sends a parameter request message to a first operating entity based on the request. The method then receives the parameter request message, determines parameter data for the target service orchestration based on the message, including attribute parameters for the second operating entity's target service orchestration, and sends the parameter data to the second operating entity. This allows the second operating entity to determine the service to be executed and the computing resource pool information for that service, where the service to be executed is a service within the target service orchestration, and the computing resource pool information includes service information and service path. The method then proceeds to the second operating entity... Based on the parameter data, after determining the services to be executed and the computing resource pool information for those services, the first operating entity executes other services to be executed in the target service orchestration and controls the means by which the second operating entity executes those services. This allows the operating entity to quickly collaborate with other operators who can provide services to complete the service orchestration requested by the user when it is unable to provide all the services required by the user. This satisfies the diverse service needs of users and makes reasonable use of the computing resources of different operators during joint service orchestration, improving resource utilization. It also provides a method for determining whether multiple operators should collaborate during joint service orchestration, enhancing the security of the operating entity and improving the efficiency of service orchestration. Attached Figure Description

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

[0036] Figure 1 A flowchart illustrating a federated services orchestration method provided in an embodiment of this application;

[0037] Figure 2 A flowchart illustrating another federated service orchestration method provided in this application embodiment;

[0038] Figure 3 A flowchart illustrating yet another federated service orchestration method provided in an embodiment of this application;

[0039] Figure 4 A detailed flowchart illustrating yet another federated service orchestration method provided in an embodiment of this application;

[0040] Figure 5 A message interaction diagram illustrating yet another federated service orchestration method provided in this application embodiment;

[0041] Figure 6 A schematic diagram of a federated services orchestration apparatus provided in an embodiment of this application;

[0042] Figure 7 A schematic diagram of another federated services orchestration apparatus provided in the embodiments of this application;

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

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

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

[0046] In existing technologies, a service policy orchestration factory, a service policy execution factory providing an interface to users of the communication network through an application programming interface, and at least one operator access domain are set up in the communication network. This method can manage, distribute, and execute user services on one or more operator access domains. The aforementioned domains and factories can be operated by the same or different entities or enterprises. This invention adopts a method of linking a requesting entity with multiple operator access domains. When the current operator access domain or slice cannot provide sufficient services, it will use handover rules to instruct the current network to move the requesting entity to another wireless network with sufficient available resources. Although it can provide users with diverse services, the orchestration process becomes cumbersome, and the handover rules are not always applicable. It is necessary to generate proprietary service policies according to different service requirements, which is not very effective for service orchestration. Therefore, current service orchestration technology cannot fully meet the orchestration requirements of multiple operators and multiple services. This is mainly reflected in the lack of a completely transparent and open method for how multiple operators decide whether to jointly conduct service orchestration.

[0047] To address the aforementioned issues, user-required services can be categorized, and services that cannot be provided can be assigned to other operators for collaborative service orchestration. This necessitates a method for determining how and whether operators should collaborate, thereby improving the success rate and efficiency of collaborative orchestration. This application proposes a method for multiple operators to collaboratively provide service orchestration. Specifically, when the first operator cannot provide all services to the user through service orchestration, it sends information about the unavailable services to the second operator via a collaborative service orchestration request. This allows users to focus solely on the services they receive without needing to know which operator is providing the service, ensuring a superior user experience. The second operator determines whether to collaborate with the first operator based on the collaborative service orchestration request and a blacklist / whitelist. If collaboration is agreed upon, a parameter request is sent to the first operator. The process involves the first operator determining the target service orchestration parameters based on the received parameter request message and sending them to the second operator. The second operator then searches for a computing resource pool that can provide the target service orchestration based on the parameter data. If available, it determines the service to be executed and the computing resource pool information for that service. Upon receiving the computing resource pool information for the service to be executed, the first operator executes other services in the target service orchestration and controls the second operator to execute those services. This application utilizes joint service orchestration requests, blacklists / whitelists, and parameter data to determine the collaboration between operators, improving the security of each operator's entity and preventing operators from refusing to collaborate due to privacy concerns or experiencing low efficiency in joint orchestration service execution. It also ensures the rational allocation of computing resources and improves resource utilization.

[0048] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will be described below with reference to the accompanying drawings.

[0049] This application provides a joint service orchestration method, apparatus, electronic device, and storage medium, applied to a first operating entity. This operating entity can be a network service orchestration management platform of an operator. The network service orchestration management platform is used to receive and send service requests, and to decompose computing power service requests into tasks and services, achieving integrated service orchestration to provide services to users. To distinguish between network service orchestration management platforms of different operators, this application uses the terms "first operating entity" and "second operating entity." This embodiment does not impose special restrictions on the type of the first operating entity, as long as it can send a joint service orchestration request to the second operating entity, enabling the second operating entity to send a parameter request message to the first operating entity based on the joint service orchestration request; receive the parameter request message; determine the parameter data of the target service orchestration based on the parameter request message; send the parameter data to the second operating entity, enabling the second operating entity to determine the service to be executed and the computing power resource pool information of the service to be executed based on the parameter data; after the second operating entity determines the service to be executed and the computing power resource pool information of the service to be executed based on the parameter data, the first operating entity executes other services to be executed in the target service orchestration and controls the second operating entity to execute the services to be executed.

[0050] This embodiment provides a federated service orchestration method, wherein the implementing entity of the federated service orchestration method can be a first operating entity, such as... Figure 1 As shown, this federated service orchestration method includes the following steps:

[0051] S101. Send a joint service orchestration request to the second operator, so that the second operator sends a parameter request message to the first operator according to the joint service orchestration request, wherein the joint service orchestration request is a request from the first operator to the second operator to perform the target service orchestration, and the second operator and the first operator are different operators.

[0052] Service orchestration can refer to the automatic setting, coordination, or management of user service needs by an operator to provide accurate services to users, while joint service orchestration can refer to the cooperation of multiple operators to achieve the purpose of service orchestration.

[0053] The parameter request message can be sent by the second operating entity and can be used by the first operating entity to determine the target service content of the joint service orchestration request. The target service can be the service that the first operating entity requests the second operating entity to execute in the target service orchestration.

[0054] Operators can be the providers of computing network architecture. Different operators have different computing network architectures. The computing network architecture includes a service provision layer, a service orchestration management layer, a network control layer, a computing management layer, and a computing resource layer / network forwarding layer. Its core is the service orchestration management layer, which is mainly responsible for collecting information on computing resources, network resources, storage resources, and algorithm resources across the entire network, as well as optimizing resource selection from a global perspective, generating computing allocation strategies, establishing connection channels, and deploying network components.

[0055] In this embodiment of the application, the joint service orchestration request includes the operator identifier ID, the type of service to be jointly orchestrated, and the request time.

[0056] The operator entity identifier ID is used to distinguish different operator entities. The service type and request time for joint orchestration are used by the second operator entity to decide whether to proceed with joint orchestration after determining the first operator entity identifier ID.

[0057] In this embodiment of the application, the method of sending a joint service orchestration request to a second operating entity, so that the second operating entity sends a parameter request message to the first operating entity according to the joint service orchestration request, may include:

[0058] Receive service request messages, which are messages from users requesting computing resource services.

[0059] Based on the service request message, determine whether the first computing resource pool meets the computing resources required by the service request message. The first computing resource pool is all the computing resource pools owned by the first operating entity.

[0060] If the first computing resource pool cannot meet the computing resources required for the service request message, then the service request message is determined to be a federated service orchestration request message.

[0061] Based on the joint service orchestration request message, send a joint service orchestration request to the second operating entity;

[0062] Receive parameter request messages.

[0063] The computing resource service requested by the user can be a single service or a combination of multiple simple services. When the first operating entity receives the service request message, it can decompose and classify the service request message to identify service requirements that cannot be provided, and then conduct joint service orchestration with the second operating entity.

[0064] This description only illustrates one possible scenario where the first and second operating entities collaborate. There could also be multiple operating entities from different operators, such as a third or fourth. These multiple operating entities can simultaneously send joint service orchestration request messages to the second operating entity, and the first operating entity can also simultaneously send joint service orchestration request messages to multiple operating entities. In other words, multiple operating entities can provide shared service messages for joint orchestration. The second operating entity periodically publishes shared service messages for joint orchestration to other trusted operating entities, and can also receive shared service messages for joint orchestration published by other operating entities. These messages include information such as service type and service location.

[0065] S102, Receive parameter request message.

[0066] The parameter request message can be the service type, the estimated service duration, the service location range, the service security level, or other service parameter messages corresponding to the federated service orchestration.

[0067] In this embodiment of the application, the method for receiving a parameter request message may include:

[0068] Receive the first response message, which indicates whether the second operating entity agrees to or rejects the joint service orchestration request;

[0069] If the first response message indicates agreement to the joint service orchestration, then a parameter request message is received, wherein the parameter request message is used by the first operating entity to determine the target service content of the joint service orchestration request;

[0070] If the first response message indicates a rejection of federation, then the federation service orchestration request is stopped.

[0071] The "stop joint service orchestration request" indicates that the second operator refuses to join with the first operator. The first operator can send the joint orchestration request to other operators that are different from the second operator to join until the joint service orchestration task is completed.

[0072] S103. Based on the parameter request message, determine the parameter data for the target service orchestration. The parameter data includes the attribute parameters for the second operating entity to orchestrate the target service.

[0073] The target service orchestration can be a service orchestration executed by the second operating entity, corresponding to the joint service orchestration sent by the first operating entity.

[0074] In this embodiment of the application, the method for determining the parameter data of the target service orchestration based on the parameter request message may include:

[0075] Based on the parameter request message, the target service is determined. The target service is the service that the first operating entity requests the second operating entity to perform the target service orchestration.

[0076] Locate the parameter data in the target service that corresponds to the parameter request message.

[0077] The target service can be determined based on the service type in the parameter request message. For example, if the service type is video rendering, then the target service is video rendering. Then, the parameter data in the video rendering service is retrieved, such as the estimated service duration of 20 days, the service location being unlimited, and the service security level being general. This parameter data can provide a basis for the second operating entity to determine the service to be executed.

[0078] S104. Send the parameter data to the second operating entity so that the second operating entity can determine the service to be executed and the computing power resource pool information of the service to be executed based on the parameter data. The service to be executed is the service in the target service orchestration, and the computing power resource pool information of the service to be executed includes the service information and service path of the service to be executed.

[0079] Among them, the service to be executed can be the service that the second operating entity determines to jointly orchestrate with the first operating entity, and the service to be executed can be one or more services in the target service.

[0080] The computing power resource pool information for the service to be executed can be determined by the second computing power resource pool of the second operating entity. The second computing power resource pool can be all the computing power resource pools owned by the second operating entity.

[0081] S105. After the second operating entity determines the service to be executed and the computing power resource pool information of the service to be executed based on the parameter data, the first operating entity executes other services to be executed in the target service orchestration and controls the second operating entity to execute the services to be executed.

[0082] Among them, other services to be executed can be services provided by the first operating entity alone through service orchestration, or services provided by joint service orchestration with other operating entities other than the second operating entity.

[0083] Controlling the execution of services by a second operating entity can be achieved through the establishment of service path connection channels and network deployment.

[0084] In this embodiment of the application, after the second operating entity determines the service to be executed and the computing resource pool information of the service to be executed based on parameter data, the method by which the first operating entity executes other services to be executed in the target service orchestration and controls the second operating entity to execute the services to be executed may include:

[0085] Send parameter data to the second operating entity;

[0086] Receive the return message from the second operating entity;

[0087] If the second operating entity returns a message indicating that it refuses to provide the service to be performed, then the federated service orchestration request is stopped;

[0088] If the return message from the second operating entity indicates that the service to be executed and the computing power resource pool information of the service to be executed are confirmed, then a first execution confirmation message is sent to the second operating entity so that the second operating entity can perform the service resource preparation work for the service to be executed according to the first execution confirmation message. The first execution confirmation message is a message from the first operating entity to the second operating entity to execute the joint service orchestration instruction.

[0089] Receive a service resource preparation completion message sent by the second operating entity. The service resources include network resources and second computing power resource pool resources that the second operating entity needs to configure before executing the service to be executed.

[0090] Based on the service resource preparation completion message, execute other pending services in the target service orchestration, and control the second operating entity to execute the pending services according to the service resource.

[0091] In this embodiment of the application, after the first operating entity executes other services to be executed in the target service orchestration and controls the second operating entity to execute the services to be executed, the joint service orchestration method may further include:

[0092] Send a target service orchestration completion message to the second operating entity so that the second operating entity can send a reclaim request message to the first operating entity based on the target service orchestration completion message. The reclaim request message is a request from the second operating entity to reclaim service resources.

[0093] Receive recycling request messages;

[0094] Based on the recycling request message, the computing resource pool information received by the first operating entity will be deleted;

[0095] A first recovery confirmation message is sent to the second operating entity so that the second operating entity can recover the service resources based on the first recovery confirmation message.

[0096] The joint service orchestration method provided in this application embodiment can provide a way to determine how and whether multiple operators' operating entities should join forces, so as to achieve the purpose of quickly joining forces to provide services to users, meet the diverse needs of users for services, and make reasonable use of the computing resources of different operators during joint service orchestration, thereby improving resource utilization and service orchestration efficiency.

[0097] This application provides another method, apparatus, electronic device, and storage medium for federated service orchestration, applied to a second operating entity. This embodiment does not impose any particular restriction on the type of the second operating entity, as long as it can receive the federated service orchestration request sent by the first operating entity; send a parameter request message to the first operating entity based on the federated service orchestration request, so that the first operating entity sends parameter data for the target service orchestration to the second operating entity based on the parameter request message; determine the service to be executed and the computing power resource pool information for the service to be executed based on the parameter data; after determining the service to be executed and the computing power resource pool information for the service to be executed, receive the instruction to execute the target service orchestration sent by the first operating entity; and execute the service to be executed according to the instruction for the target service orchestration.

[0098] This embodiment provides another federated service orchestration method, in which the implementing entity can be a second operating entity, such as... Figure 2 As shown, this federated service orchestration method includes the following steps:

[0099] S201. Receive a joint service orchestration request sent by the first operating entity, where the first operating entity is the operating entity that performs the target service orchestration and the first operating entity is different from the operator of the second operating entity. The target service orchestration corresponds to the joint service orchestration request.

[0100] Among them, a joint service orchestration request can be a request issued by the first operator to the second operator because the first operator is unable to provide the service required by the user.

[0101] S202. Based on the joint service orchestration request, a parameter request message is sent to the first operating entity, so that the first operating entity sends the target service orchestration parameter data to the second operating entity according to the parameter request message. The parameter data includes the attribute parameters of the second operating entity for the target service orchestration.

[0102] The joint service orchestration request includes the operator's identifier ID of the first operator, the type of service to be jointly orchestrated, and the request time.

[0103] In this embodiment of the application, the method for sending a parameter request message to the first operating entity based on a federated service orchestration request may include:

[0104] Based on the joint service orchestration request, a second response message is determined to be sent to the first operating entity. The second response message indicates whether the second operating entity agrees to or rejects the joint service orchestration request. The second response message corresponds to the first response message.

[0105] If the second reply message indicates agreement to the joint operation, a parameter request message is sent to the first operating entity.

[0106] If the second response message indicates a refusal to join, then the request for joint service orchestration with the first operating entity is terminated.

[0107] The second response message can be a response from the second operating entity to the joint service orchestration request message from the first operating entity. This response message can be either an agreement by the second operating entity to join forces with the first operating entity or a refusal to join forces with the first operating entity.

[0108] In this embodiment of the application, the method for determining the second response message to be sent to the first operating entity based on the federated service orchestration request may include:

[0109] Based on the operator identifier ID in the joint orchestration request, determine whether the first operator is in the joint service orchestration whitelist. The joint service orchestration whitelist is a list of cooperating operators set up by the second operator.

[0110] If the service is on the joint service orchestration whitelist, a second response message indicating agreement to the joint service will be sent to the first operating entity.

[0111] If it is not in the joint service orchestration whitelist, then determine whether the first operating entity is in the joint service orchestration blacklist. The joint service orchestration blacklist is a list of operating entities that the second operating entity does not cooperate with.

[0112] If the service is on the blacklist, a second response message will be sent to the first operating entity to refuse the service.

[0113] If not on the joint service orchestration blacklist, the second response message is determined based on the service type and request time of the joint service orchestration request, and then sent to the first operating entity.

[0114] The joint service orchestration whitelist is a set of priority operating entities set by the second operating entity based on historical joint service orchestration. When an operating entity that issues a joint service orchestration request is in the joint service orchestration whitelist, the second operating entity will directly agree to the joint service orchestration rather than deciding whether to join based on the service type and the current request time.

[0115] The joint service orchestration blacklist is a set of operating entities that the second operating entity sets up based on historical joint service orchestration and refuses to cooperate with. When an operating entity that issues a joint service orchestration request is on the joint service orchestration blacklist, the second operating entity will directly refuse to join rather than making a decision on whether to join based on the service type and the current request time.

[0116] The request time can be determined by the second operating entity to determine whether it has a second computing power resource pool with spare capacity to provide services for the current joint service orchestration of the first operating entity.

[0117] S203. Based on the parameter data, determine the service to be executed and the computing resource pool information of the service to be executed. The service to be executed is the service in the target service orchestration, and the computing resource pool information of the service to be executed includes the service information and service path of the service to be executed.

[0118] The computing resource pool for the service to be executed can be one or more computing resource pools in the second computing resource pool.

[0119] In this embodiment of the application, the method for determining the service to be executed and the computing resource pool information of the service to be executed based on parameter data may include:

[0120] Obtain data from the second computing power resource pool, which is the entire computing power resource pool owned by the second operating entity;

[0121] The execution conditions are determined based on the parameter data and the data from the second computing power resource pool;

[0122] If the execution conditions indicate that the second operating entity meets the service execution requirements, then the computing power resource pool to provide the service to be executed is determined.

[0123] Based on the computing power resource pool that provides the service to be executed, obtain the service path from the computing power resource pool to the first operating entity;

[0124] The computing resource pool information is sent to the first operating entity. The computing resource pool information includes service information and service paths of the services to be executed.

[0125] Among them, the service path from the computing power resource pool to the first operating entity to obtain the service to be executed can be obtained through the computing power network system. The computing power network system includes server nodes and routing nodes. Based on the resource occupancy rate and weight of the link between each server node and each routing node at the current time, the service resource scenario type corresponding to the link between the server node and the corresponding routing node at the current time is determined, and the shortest computing power network path of the corresponding service resource is determined.

[0126] The computing resource pool information can be obtained by sending multicast query messages from the computing server nodes in the multicast source. The multicast query message is used to request computing resource information of a specified service type.

[0127] In this embodiment of the application, the method for determining execution conditions based on parameter data and data from the second computing power resource pool may include:

[0128] If the execution conditions indicate that the second operating entity does not meet the service execution requirements, a message refusing to provide the service to be executed is sent to the first operating entity.

[0129] The execution condition indicates that the second operating entity does not meet the service execution requirements, which may be that the parameter data contains service data that the second operating entity cannot provide.

[0130] S204. After determining the service to be executed and the computing power resource pool information of the service to be executed, receive the instruction for the execution target service orchestration sent by the first operating entity. The instruction for the target service orchestration is used to control the first operating entity to execute other services to be executed in the target service orchestration and to control the second operating entity to execute the services to be executed.

[0131] In this embodiment of the application, after determining the service to be executed and the computing resource pool information of the service to be executed, the method for receiving the instruction from the first operating entity to orchestrate the execution target service may include:

[0132] Receive a second execution confirmation message sent by the first operating entity. The second execution confirmation message is a message in which the second operating entity executes the joint service orchestration instruction issued by the first operating entity.

[0133] Based on the second execution confirmation message, the service resource preparation work for the service to be executed is initiated. The service resource preparation work includes the network configuration and computing resource pool configuration work before the second operating entity executes the service to be executed.

[0134] Send a message to the primary operating entity indicating that service resources are ready.

[0135] Among them, network configuration can enable the network to perceive the computing power needs of users or the primary operator in real time, as well as its own computing power status.

[0136] S205. Execute the service to be executed according to the instructions arranged by the target service.

[0137] In this embodiment of the application, after executing the service to be executed according to the instructions of the target service orchestration, the federated service orchestration method may further include:

[0138] Receive the target service orchestration completion message sent by the first operating entity;

[0139] Based on the target service orchestration completion message, a recovery request message is sent to the first operating entity, wherein the recovery request message is a message from the second operating entity requesting the recovery of service resources;

[0140] Receive a second recovery confirmation message, which corresponds to the first recovery confirmation message sent by the first operating entity;

[0141] Based on the second confirmation message, service resources have been reclaimed.

[0142] The joint service orchestration method provided in this application embodiment can provide a way to determine how and whether multiple operators' operating entities should join forces, so as to achieve the purpose of quickly joining forces to provide services to users and meet the diverse needs of users for services. At the same time, by using a method to determine whether multiple operators should join forces during joint service orchestration, the security of operating entities is enhanced and the efficiency of service orchestration is improved.

[0143] Figure 3 Another federated service orchestration method provided for embodiments of this application, such as Figure 3 As shown, the method includes the following steps:

[0144] S301. The operator receives a joint service orchestration request message from other operators.

[0145] Other operating entities include, but are not limited to, the first operating entity. They can be operating entities from multiple different operators, such as the third operating entity, the fourth operating entity, etc. Multiple operating entities can send request messages to the second operating entity simultaneously.

[0146] The joint service orchestration request message has been described in detail in the above embodiments and will not be elaborated here.

[0147] Among them, the operating entities can provide shared service messages that can be jointly orchestrated. The second operating entity can periodically publish shared service messages that can be jointly orchestrated to other trusted operating entities, and can also receive shared service messages that can be jointly orchestrated from other operating entities. These messages include service type, service location, etc.

[0148] S302. The operating entity determines whether it is in the blacklist of joint service orchestration based on its operating entity ID. If it is in the blacklist, it sends a message rejecting joint service orchestration to other operating entities. If it is not in the blacklist, it determines whether it is in the whitelist of joint service orchestration. If it is, it sends a message agreeing to joint orchestration to other operating entities, and then executes S303. If it is not in the whitelist, it determines whether to conduct joint service orchestration with other operating entities based on the joint orchestration service type and request time. If it disagrees, it sends the result of disagreeing to conduct joint orchestration to other operating entities. If it agrees, it executes S303.

[0149] The joint service orchestration blacklist refers to the set of operators that the second operator refuses to participate in joint service orchestration. This set records the identifier ID of the refusing operator and the reason for the refusal. Any joint request sent by an operator in this set will be rejected by the second operator. When the second operator wants to re-enter the joint service orchestration, it can remove that operator from the blacklist. The joint service orchestration whitelist refers to the set of operators that have established a joint with the second operator. This set records the identifier ID of the joint operator and the joint information. Any joint request sent by an operator in this set will be accepted by the second operator. The joint service orchestration blacklist and whitelist are established based on the second operator's historical joint service orchestration information, which can enhance the operator's security and improve the efficiency of joint service orchestration.

[0150] S303. The operator sends a request for specific parameters to other operators for joint service orchestration.

[0151] The parameters have been described in detail in the above embodiments and will not be repeated here.

[0152] S304. After receiving the message, other operating entities shall reply with specific parameters in response to the message.

[0153] The message content includes the parameters sent by the second operating entity in S303 for joint service orchestration; the specific parameters in the reply can be parameter data that matches the parameter content sent by the second operating entity. In some embodiments, the parameter data corresponding to the service type can be video rendering, the parameter data corresponding to the estimated service duration can be 30 days, the parameter data corresponding to the service location range can be unlimited, and the parameter data corresponding to the service security level can be general. This mainly describes the correspondence between the message content and the specific parameters in the reply, without making any special restrictions on the types of the message content and the specific parameters in the reply.

[0154] S305. After receiving the specific parameter message, the operating entity determines whether its computing power resource pool can provide the service. If it cannot provide the service, it replies to other operating entities that it refuses to provide the joint service orchestration request. The message content includes that the required service cannot be provided. If the operating entity's capacity resource pool contains a service request that meets the requirements in S304, then proceed to S306.

[0155] Among them, the capability resource pool can be the entire computing power resource pool belonging to the second operating entity.

[0156] S306. Based on the content in S304, the operating entity decides on the capability resource pool for providing services, calculates the service path from the capability resource pool to other operating entities, and then sends the service information of the capability resource pool and the boundary device IDs connected to other operating entities in the service path to other operating service entities.

[0157] Among them, the resource pool for decision-making to provide services refers to the resource pool selected according to a set rule that can undertake the service. The set rule can be logical area, service resource type, network scale, etc.; the service situation of the resource pool refers to the service capacity of the resource pool itself that decides to provide the service capability. For example, if the first operating entity needs a firewall service, then when the second operating entity sends firewall service resources, it will provide the first operating entity with the maximum computing power that the resource can support the first operating entity to perform model training; the boundary device ID that connects with other operating entities in the service path is a unique identifier that distinguishes the joint orchestration of each operating entity and is calculated by the computing nodes in the resource pool.

[0158] S307. After receiving the orchestration results, other operating entities shall return a confirmation message.

[0159] S308. After receiving the confirmation message, the operating entity will start the services in the capability resource pool and complete the corresponding network configuration and other preparations.

[0160] Specifically, upon receiving confirmation, the service in the capability resource pool is activated, and the installation, deployment, network configuration, and other initialization tasks of the corresponding service are automatically completed according to the specific parameters obtained from S304.

[0161] S309. After the joint service is provided, the operating entity shall reclaim the corresponding service resources and network resources.

[0162] S310, Joint Service Orchestration Completed.

[0163] Figure 4 This is a schematic flowchart illustrating another federated service orchestration method provided in an embodiment of this application. For example... Figure 4As shown, after receiving a joint service orchestration request from other operators (including the first operator), the second operator determines whether the other operators meet the joint service orchestration conditions. If not, it rejects the joint service orchestration; if so, it sends a message agreeing to the joint service orchestration to the other operators; it requests the other operators to provide joint service orchestration parameter messages; it receives and parses the joint service orchestration parameters; based on the service parameters, the second operator determines whether it can provide the corresponding service; if not, it rejects the joint service orchestration; if so, it selects a resource pool to provide the service and orchestrates the relevant paths; it sends the orchestration results to the other operators; after receiving confirmation messages from the other operators, it completes the service resource pool preparation work; it sends a service resource preparation completion message to the other operators; the other operators perform joint service orchestration and send a joint service orchestration completion message to the second operator; the second operator reclaims the corresponding service resources and network resources.

[0164] Figure 5 This is a schematic diagram illustrating the message interaction of another federated service orchestration method provided in this application embodiment. The message interaction process of the federated service orchestration method can be found in the previous sections. Figure 3 and Figure 4 The specific implementation examples are not described in detail here.

[0165] Figure 6 This is a schematic diagram of a joint services orchestration apparatus provided in an embodiment of this application, applied to a first operating entity. For example... Figure 6 As shown, the joint service orchestration apparatus 60 includes: a first sending module 601, a first receiving module 602, a first determining module 603, a second sending module 604, and a first execution module 605. Wherein:

[0166] The first sending module 601 is used to send a joint service orchestration request to the second operating entity, so that the second operating entity sends a parameter request message to the first operating entity according to the joint service orchestration request. The joint service orchestration request is a request from the first operating entity to the second operating entity to perform target service orchestration. The second operating entity is a different operator from the first operating entity.

[0167] The first receiving module 602 is used to receive parameter request messages;

[0168] The first determining module 603 is used to determine the parameter data of the target service orchestration based on the parameter request message. The parameter data includes the attribute parameters of the second operating entity for orchestrating the target service.

[0169] The second sending module 604 is used to send parameter data to the second operating entity so that the second operating entity can determine the service to be executed and the computing power resource pool information of the service to be executed based on the parameter data. The service to be executed is a service in the target service orchestration, and the computing power resource pool information of the service to be executed includes the service information and service path of the service to be executed.

[0170] The first execution module 605 is used to execute other services to be executed in the target service orchestration after the second operating entity determines the service to be executed and the computing power resource pool information of the service to be executed based on the parameter data, and to control the second operating entity to execute the service to be executed.

[0171] In this embodiment of the application, the first sending module 601 can also be used for:

[0172] Receive service request messages, which are service messages from user clients requesting computing resources;

[0173] Based on the service request message, determine whether the first computing resource pool meets the computing resources required by the service request message. The first computing resource pool is all the computing resource pools owned by the first operating entity.

[0174] If the first computing resource pool cannot meet the computing resources required for the service request message, then the service request message is determined to be a federated service orchestration request message.

[0175] Based on the joint service orchestration request message, send a joint service orchestration request to the second operating entity;

[0176] Receive parameter request messages.

[0177] In this embodiment of the application, the first receiving module 602 can also be used for:

[0178] Receive the first response message, which indicates whether the second operating entity agrees to or rejects the joint service orchestration request;

[0179] If the first response message indicates agreement to the joint service orchestration, then a parameter request message is received, wherein the parameter request message is used by the first operating entity to determine the target service content of the joint service orchestration request;

[0180] If the first response message indicates a rejection of federation, then the federation service orchestration request is stopped.

[0181] In this embodiment of the application, the first determining module 603 can also be used for:

[0182] Based on the parameter request message, the target service is determined. The target service is the service that the first operating entity requests the second operating entity to perform the target service orchestration.

[0183] Locate the parameter data in the target service that corresponds to the parameter request message.

[0184] In this embodiment of the application, the first execution module 605 can also be used for:

[0185] Send parameter data to the second operating entity;

[0186] Receive the return message from the second operating entity;

[0187] If the second operating entity returns a message indicating that it refuses to provide the service to be performed, then the federated service orchestration request is stopped;

[0188] If the return message from the second operating entity indicates that the service to be executed and the computing power resource pool information of the service to be executed are confirmed, then a first execution confirmation message is sent to the second operating entity so that the second operating entity can perform the service resource preparation work for the service to be executed according to the first execution confirmation message. The first execution confirmation message is a message from the first operating entity to the second operating entity to execute the joint service orchestration instruction.

[0189] Receive a service resource preparation completion message sent by the second operating entity. The service resources include network resources and computing power resource pool resources that the second operating entity needs to configure before executing the service to be executed.

[0190] Based on the service resource preparation completion message, execute other pending services in the target service orchestration, and control the second operating entity to execute the pending services according to the service resource.

[0191] In this embodiment of the application, the first execution module 605 can also be used for:

[0192] After the first operating entity executes other pending services in the target service orchestration and controls the second operating entity to execute the pending services;

[0193] Send a target service orchestration completion message to the second operating entity so that the second operating entity can send a reclaim request message to the first operating entity based on the target service orchestration completion message. The reclaim request message is a request from the second operating entity to reclaim service resources.

[0194] Receive recycling request messages;

[0195] Based on the recycling request message, the computing resource pool information received by the first operating entity will be deleted;

[0196] A first recovery confirmation message is sent to the second operating entity so that the second operating entity can recover the service resources based on the first recovery confirmation message.

[0197] As can be seen from the above, a joint service orchestration apparatus according to an embodiment of this application includes a first sending module 601, used to send a joint service orchestration request to a second operator, so that the second operator sends a parameter request message to the first operator according to the joint service orchestration request. The joint service orchestration request is a request from the first operator to the second operator to perform target service orchestration, and the second operator and the first operator are different operators; a first receiving module 602, used to receive the parameter request message; and a first determining module 603, used to determine the parameter data of the target service orchestration according to the parameter request message. The parameter data includes the target service orchestration parameters performed by the second operator. The system includes: a service orchestration attribute parameter; a second sending module 604, used to send parameter data to a second operating entity, so that the second operating entity can determine the service to be executed and the computing power resource pool information of the service to be executed based on the parameter data, wherein the service to be executed is a service in the target service orchestration, and the computing power resource pool information of the service to be executed includes the service information and service path of the service to be executed; and a first execution module 605, used to execute other services to be executed in the target service orchestration after the second operating entity determines the service to be executed and the computing power resource pool information of the service to be executed based on the parameter data, and to control the second operating entity to execute the services to be executed. Therefore, this application embodiment can provide a method for determining how and whether multiple operators' operating entities should collaborate based on the joint service orchestration device, achieving the goal of quickly collaborating to provide services to users, meeting users' diverse service needs, and rationally utilizing the computing power resources of different operators during joint service orchestration, thereby improving resource utilization and service orchestration efficiency.

[0198] Figure 7 This is a schematic diagram of another collaborative service orchestration apparatus provided in an embodiment of this application, applied to a second operating entity. For example... Figure 7 As shown, the joint service orchestration apparatus 70 includes: a second receiving module 701, a third sending module 702, a second determining module 703, a third receiving module 704, and a second execution module 705. Wherein:

[0199] The second receiving module 701 is used to receive a joint service orchestration request sent by the first operating entity, wherein the first operating entity is the operating entity that performs the target service orchestration, and the first operating entity is different from the operator of the second operating entity, and the target service orchestration corresponds to the joint service orchestration request;

[0200] The third sending module 702 is used to send a parameter request message to the first operating entity according to the joint service orchestration request, so that the first operating entity sends the target service orchestration parameter data to the second operating entity according to the parameter request message. The parameter data includes the attribute parameters of the second operating entity for the target service orchestration.

[0201] The second determining module 703 is used to determine the service to be executed and the computing power resource pool information of the service to be executed based on the parameter data. The service to be executed is a service in the target service orchestration, and the computing power resource pool information of the service to be executed includes the service information and service path of the service to be executed.

[0202] The third receiving module 704 is used to receive the execution target service orchestration instruction sent by the first operating entity after determining the service to be executed and the computing power resource pool information of the service to be executed. The execution target service orchestration instruction is used to control the first operating entity to execute other services to be executed in the target service orchestration and to control the second operating entity to execute the service to be executed.

[0203] The second execution module 705 is used to execute the service to be executed according to the instructions orchestrated by the target service.

[0204] In this embodiment of the application, the third sending module 702 can also be used for:

[0205] Based on the joint service orchestration request, a second response message is determined to be sent to the first operating entity. The second response message indicates whether the second operating entity agrees to or rejects the joint service orchestration request. The second response message corresponds to the first response message.

[0206] If the second reply message indicates agreement to the joint operation, a parameter request message is sent to the first operating entity.

[0207] If the second response message indicates a refusal to join, then the request for joint service orchestration with the first operating entity is terminated.

[0208] In this embodiment of the application, the third sending module 702 can also be used for:

[0209] Based on the operator identifier ID in the joint orchestration request, determine whether the first operator is in the joint service orchestration whitelist. The joint service orchestration whitelist is a list of cooperating operators set up by the second operator.

[0210] If the service is on the joint service orchestration whitelist, a second response message indicating agreement to the joint service will be sent to the first operating entity.

[0211] If it is not in the joint service orchestration whitelist, then determine whether the first operating entity is in the joint service orchestration blacklist. The joint service orchestration blacklist is a list of operating entities that the second operating entity does not cooperate with.

[0212] If the service is on the blacklist, a second response message will be sent to the first operating entity to refuse the service.

[0213] If not on the joint service orchestration blacklist, the second response message is determined based on the service type and request time of the joint service orchestration request, and then sent to the first operating entity.

[0214] In this embodiment of the application, the second determining module 703 can also be used for:

[0215] Obtain data from the second computing power resource pool, which is the entire computing power resource pool owned by the second operating entity;

[0216] The execution conditions are determined based on the parameter data and the data from the second computing power resource pool;

[0217] If the execution conditions indicate that the second operating entity meets the service execution requirements, then the computing power resource pool to provide the service to be executed is determined.

[0218] Based on the computing power resource pool that provides the service to be executed, obtain the service path from the computing power resource pool to the first operating entity;

[0219] The computing resource pool information is sent to the first operating entity. The computing resource pool information includes service information and service paths of the services to be executed.

[0220] In this embodiment of the application, the second determining module 703 can also be used for:

[0221] If the execution conditions indicate that the second operating entity does not meet the service execution requirements, a message refusing to provide the service to be executed is sent to the first operating entity.

[0222] In this embodiment of the application, the third receiving module 704 can also be used for:

[0223] Receive a second execution confirmation message sent by the first operating entity. The second execution confirmation message is a message in which the second operating entity executes the joint service orchestration instruction issued by the first operating entity.

[0224] Based on the second execution confirmation message, the service resource preparation work for the service to be executed is initiated. The service resource preparation work includes the network configuration and computing resource pool configuration work before the second operating entity executes the service to be executed.

[0225] Send a message to the primary operating entity indicating that service resources are ready.

[0226] In this embodiment of the application, the second execution module 705 can also be used for:

[0227] Receive the target service orchestration completion message sent by the first operating entity;

[0228] Based on the target service orchestration completion message, a recovery request message is sent to the first operating entity, wherein the recovery request message is a message from the second operating entity requesting the recovery of service resources;

[0229] Receive a second recovery confirmation message, which corresponds to the first recovery confirmation message sent by the first operating entity;

[0230] Based on the second confirmation message, service resources have been reclaimed.

[0231] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 8 As shown, the electronic device 80 includes:

[0232] The electronic device 80 may include a processor 801 with one or more processing cores, a memory 802 with one or more computer-readable storage media, a communication component 803, and other components. The processor 801, memory 802, and communication component 803 are connected via a bus 804.

[0233] In the specific implementation process, at least one processor 801 executes computer execution instructions stored in memory 802, causing at least one processor 801 to execute the above-described joint service orchestration method.

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

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

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

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

[0238] In some embodiments, a computer program product is also provided, including a computer program or instructions that, when executed by a processor, implement the steps in any of the above-described federated services orchestration methods.

[0239] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0240] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by instructions, or by instructions controlling related hardware. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0241] To this end, embodiments of this application provide a computer-readable storage medium storing a plurality of instructions that can be loaded by a processor to execute steps in any of the federated services orchestration methods provided in embodiments of this application.

[0242] The storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0243] According to one aspect of this application, a computer program product or computer program is provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium.

[0244] Because the instructions stored in the storage medium can execute the steps of any of the federated services orchestration methods provided in the embodiments of this application, the beneficial effects achievable by any of the federated services orchestration methods provided in the embodiments of this application can be realized, as detailed in the preceding embodiments, which will not be repeated here. Other embodiments of this application will readily conceive of by those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary technical means in the art not disclosed in this application. The specification and embodiments are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0245] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A federated service orchestration method, characterized in that, Applied to the first operating entity, the method includes: A joint service orchestration request is sent to the second operator, the joint service orchestration request including the operator's identifier ID, the service type requested for joint orchestration, and the request time, so that the second operator can determine whether to agree to the joint orchestration based on the joint service orchestration request. If the joint orchestration is agreed, a parameter request message is sent to the first operator. The joint service orchestration request is a request from the first operator to the second operator to perform the target service orchestration. The second operator is a different operator from the first operator. Receive the parameter request message; the parameter request message includes service type, estimated service duration, service location range, and service security level; Based on the parameter request message, determine the parameter data for the target service orchestration, the parameter data including the attribute parameters for the target service orchestration performed by the second operating entity; The parameter data is sent to the second operating entity so that the second operating entity can determine the service to be executed and the computing power resource pool information of the service to be executed based on the parameter data. The service to be executed is a service in the target service orchestration, and the computing power resource pool information of the service to be executed includes the service information and service path of the service to be executed. Send the parameter data to the second operating entity; Receive the return message from the second operating entity; If the second operating entity returns a message indicating a refusal to provide the service to be performed, then the federated service orchestration request is terminated. If the return message from the second operating entity indicates that the service to be executed and the computing power resource pool information of the service to be executed are determined, then a first execution confirmation message is sent to the second operating entity so that the second operating entity can perform the service resource preparation work of the service to be executed according to the first execution confirmation message. The first execution confirmation message is a message from the first operating entity to the second operating entity to execute a joint service orchestration instruction. Receive a service resource preparation completion message sent by the second operating entity, wherein the service resources include network resources and second computing power resource pool resources that the second operating entity needs to configure before executing the service to be executed; Based on the service resource preparation completion message, execute other pending services in the target service orchestration, and control the second operating entity to execute the pending services based on the service resources.

2. The method according to claim 1, characterized in that... The second operator determines whether to agree to the joint service orchestration request based on the request. If the joint service orchestration request is agreed upon, the second operator sends a parameter request message to the first operator, including: Receive a service request message, wherein the service request message is a service message from a user requesting computing resources; Based on the service request message, it is determined whether the first computing resource pool meets the computing resources required by the service request message. The first computing resource pool is all the computing resource pools owned by the first operating entity. If the first computing power resource pool cannot meet the computing power resources required by the service request message, then the service request message is determined to be a federated service orchestration request message; Based on the joint service orchestration request message, a joint service orchestration request is sent to the second operating entity; Receive the parameter request message.

3. The method according to claim 1, characterized in that, Receiving the parameter request message includes: Receive a first reply message, which is a message in which the second operating entity agrees to or rejects the joint service orchestration request; If the first reply message indicates agreement to the joint service orchestration, then the parameter request message is received, wherein the parameter request message is used by the first operating entity to determine the target service content of the joint service orchestration request; If the first response message indicates a rejection of federation, then the federation service orchestration request is stopped.

4. The method according to claim 1, characterized in that... The step of determining the parameter data of the target service orchestration based on the parameter request message includes: Based on the parameter request message, the target service is determined, which is the service for which the first operating entity requests the second operating entity to perform target service orchestration; Locate the parameter data in the target service that corresponds to the parameter request message.

5. The method according to claim 1, characterized in that, The method further includes: After the first operating entity executes other services to be executed in the target service orchestration, and controls the second operating entity to execute the services to be executed; Send a target service orchestration completion message to the second operating entity, so that the second operating entity sends a reclaim request message to the first operating entity based on the target service orchestration completion message, wherein the reclaim request message is a request from the second operating entity to reclaim service resources; Receive the recycling request message; According to the recycling request message, the computing power resource pool information received by the first operating entity is deleted; A first recovery confirmation message is sent to the second operating entity so that the second operating entity can recover the service resources based on the first recovery confirmation message.

6. A federated service orchestration method, characterized in that, Applied to a second operating entity, the method includes: The system receives a joint service orchestration request sent by a first operating entity. The joint service orchestration request includes an operating entity identifier ID, the service type requested for joint orchestration, and the request time. The first operating entity is the operating entity that performs the target service orchestration, and the first operating entity is different from the operator of the second operating entity. The target service orchestration corresponds to the joint service orchestration request. Based on the joint service orchestration request, determine whether to agree to joint operation. If the joint operation is agreed to, send a parameter request message to the first operator, so that the first operator sends the target service orchestration parameter data to the second operator based on the parameter request message, which includes service type, estimated service duration, service location range, and service security level. The parameter data includes attribute parameters for the second operator to orchestrate the target service. Based on the parameter data, the service to be executed and the computing resource pool information of the service to be executed are determined, wherein the service to be executed is a service in the target service orchestration, and the computing resource pool information of the service to be executed includes the service information and service path of the service to be executed. After determining the service to be executed and the computing power resource pool information of the service to be executed, the system receives an instruction from the first operating entity to execute the target service orchestration. The instruction for the target service orchestration is used to control the first operating entity to execute other services to be executed in the target service orchestration and to control the second operating entity to execute the service to be executed. Execute the service to be executed according to the instructions orchestrated by the target service; After determining the service to be executed and the computing resource pool information of the service to be executed, the step of receiving an instruction from the first operating entity to execute the target service orchestration includes: Receive a second execution confirmation message sent by the first operating entity. The second execution confirmation message is a message in which the second operating entity executes the joint service orchestration instruction issued by the first operating entity. The second execution confirmation message corresponds to the message in which the joint service orchestration instruction issued by the first operating entity is sent. According to the second execution confirmation message, the service resource preparation work for the service to be executed is initiated. The service resource preparation work includes network configuration and computing resource pool configuration before the second operating entity executes the service to be executed. Send a message to the first operating entity indicating that service resources are ready.

7. The method according to claim 6, characterized in that, The step of determining whether to agree to the joint service orchestration request, and sending a parameter request message to the first operator if the joint service orchestration request is agreed to, includes: Based on the joint service orchestration request, a second response message is determined to be sent to the first operator. The second response message is a message in which the second operator agrees to or rejects the joint service orchestration request. The second response message corresponds to the first response message received by the first operator. If the second reply message indicates agreement to the joint operation, then the parameter request message is sent to the first operating entity; If the second response message indicates a refusal to join, then the joint service orchestration request with the first operating entity is terminated.

8. The method according to claim 7, characterized in that, The step of determining the second response message to be sent to the first operator based on the federated service orchestration request includes: Based on the operator identifier ID in the joint service orchestration request, determine whether the first operator is in the joint service orchestration whitelist, where the joint service orchestration whitelist is a list of cooperating operators set up by the second operator; If the service is in the joint service orchestration whitelist, then send the second reply message to the first operator to indicate agreement to the joint service. If the first operating entity is not in the joint service orchestration whitelist, then it is determined whether the first operating entity is in the joint service orchestration blacklist, which is a list of operating entities that the second operating entity does not cooperate with. If the service is on the blacklist, a second response message for refusing to join is sent to the first operator. If the service is not in the joint service orchestration blacklist, the second response message is determined based on the service type and the request time of the joint service orchestration request, and the second response message is sent to the first operating entity.

9. The method according to claim 6, characterized in that, The step of determining the service to be executed and the computing resource pool information of the service to be executed based on the parameter data includes: Obtain data from the second computing resource pool, which is the total computing resource pool owned by the second operating entity; The execution conditions are determined based on the parameter data and the data from the second computing power resource pool; If the execution conditions indicate that the second operating entity meets the service execution requirements, then the computing power resource pool that provides the service to be executed is determined. Based on the computing power resource pool that provides the service to be executed, obtain the service path from the computing power resource pool of the service to be executed to the first operating entity; The computing power resource pool information is sent to the first operating entity, and the computing power resource pool information includes the service information and service path of the service to be executed.

10. The method according to claim 9, characterized in that, The method further includes: If the execution conditions indicate that the second operating entity does not meet the service execution requirements, a message refusing to provide the service to be executed is sent to the first operating entity.

11. The method according to claim 6, characterized in that, After executing the service to be executed according to the instructions orchestrated by the target service, the method further includes: Receive the target service orchestration completion message sent by the first operating entity; Based on the target service orchestration completion message, a recycling request message is sent to the first operating entity, wherein the recycling request message is a message from the second operating entity requesting the recycling of service resources; Receive a second recovery confirmation message, which corresponds to the first recovery confirmation message sent by the first operating entity; The service resources are reclaimed based on the second recovery confirmation message.

12. A joint services orchestration apparatus, characterized in that, Applied to the first operating entity, the device includes: The first sending module is used to send a joint service orchestration request to the second operator. The joint service orchestration request includes an operator identifier ID, the service type requested for joint orchestration, and the request time, so that the second operator can determine whether to agree to the joint orchestration based on the joint service orchestration request. If the second operator agrees to the joint orchestration, it sends a parameter request message to the first operator. The joint service orchestration request is a request from the first operator to the second operator to perform a target service orchestration. The second operator is a different operator from the first operator. The first receiving module is used to receive the parameter request message; the parameter request message includes service type, estimated service duration, service location range, and service security level. The first determining module is used to determine the parameter data of the target service orchestration based on the parameter request message, wherein the parameter data includes the attribute parameters of the second operating entity for orchestrating the target service; The second sending module is used to send the parameter data to the second operating entity, so that the second operating entity can determine the service to be executed and the computing power resource pool information of the service to be executed based on the parameter data. The service to be executed is a service in the target service orchestration, and the computing power resource pool information of the service to be executed includes the service information and service path of the service to be executed. The first execution module is configured to: send the parameter data to the second operating entity; receive a return message from the second operating entity; if the return message from the second operating entity indicates a refusal to provide the service to be executed, then stop the joint service orchestration request; if the return message from the second operating entity indicates a confirmed service to be executed and information about the computing resource pool for the service to be executed, then send a first execution confirmation message to the second operating entity, so that the second operating entity can perform service resource preparation work for the service to be executed according to the first execution confirmation message, wherein the first execution confirmation message is a message from the first operating entity to the second operating entity instructing the execution of joint service orchestration; receive a service resource preparation completion message from the second operating entity, wherein the service resources include network resources and second computing resource pool resources that the second operating entity needs to configure before executing the service to be executed; execute other services to be executed in the target service orchestration according to the service resource preparation completion message, and control the second operating entity to execute the service to be executed according to the service resources.

13. A joint services orchestration apparatus, characterized in that, Applied to a second operating entity, the device includes: The second receiving module is used to receive a joint service orchestration request sent by the first operating entity. The joint service orchestration request includes an operating entity identifier ID, the service type requested for joint orchestration, and the request time. The first operating entity is the operating entity that performs the target service orchestration, and the first operating entity is different from the operator of the second operating entity. The target service orchestration corresponds to the joint service orchestration request. The third sending module is used to determine whether to agree to the joint service orchestration request based on the joint service orchestration request. If the joint service orchestration request is agreed, the module sends a parameter request message to the first operating entity so that the first operating entity sends the target service orchestration parameter data to the second operating entity based on the parameter request message, which includes the service type, the estimated service duration, the service location range, and the service security level. The parameter data includes the attribute parameters of the second operating entity for the target service orchestration. The second determining module is used to determine the service to be executed and the computing power resource pool information of the service to be executed based on the parameter data, wherein the service to be executed is a service in the target service orchestration, and the computing power resource pool information of the service to be executed includes the service information and service path of the service to be executed. The third receiving module is used to receive, after determining the service to be executed and the computing power resource pool information of the service to be executed, an instruction sent by the first operating entity to execute the target service orchestration. The instruction to execute the target service orchestration is used to control the first operating entity to execute other services to be executed in the target service orchestration and to control the second operating entity to execute the service to be executed. The second execution module is used to execute the service to be executed according to the instructions orchestrated by the target service; The third receiving module is further configured to receive a second execution confirmation message sent by the first operating entity, wherein the second execution confirmation message is a message in which the second operating entity executes the joint service orchestration instruction issued by the first operating entity, and the second execution confirmation message corresponds to the message in which the joint service orchestration instruction issued by the first operating entity is sent; based on the second execution confirmation message, the service resource preparation work for the service to be executed is initiated, wherein the service resource preparation work includes network configuration and computing resource pool configuration work before the second operating entity executes the service to be executed; and a service resource preparation completion message is sent to the first operating entity.

14. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the federated services orchestration method as described in any one of claims 1 to 11.

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

Images