Wireless computing power task migration method and device and computer readable storage medium

Abstract

The embodiment of the invention provides a wireless computing power task migration method, a wireless computing power task migration device, communication equipment, a chip and a computer readable storage medium, the method is applied to a first cloud platform or a first cloud site, and the method comprises the following steps: sending a first request to a second cloud platform or a second cloud site; the first request is a migration request of a calculation task and / or service; if a first response sent by the second cloud platform or the second cloud site is received, sending a second request to the second cloud platform or the second cloud site; the first response represents that the computing task and / or service is successfully deployed in the second cloud platform or the second cloud site; the second request is used for requesting to transmit data of the calculation task and / or service.

Description

Technical Field

[0001] Embodiments of the present application relate to the field of mobile communication technologies, and in particular, to a method for migrating wireless computing power tasks, a device for migrating wireless computing power tasks, a communication device, a chip, and a computer-readable storage medium. Background Art

[0002] In existing standard solutions, a wireless cloud network deploys base station software on a general server cloudification platform to achieve high availability of wireless-side hardware resources, and at the same time provides the possibility for wireless resource sharing and deploying edge applications (as well as related computing tasks and / or services, etc.) with high latency requirements using idle resources. When the cloud platform resources cannot meet the resource requirements of computing tasks and / or services and a computing task and / or service migration needs to be initiated, in existing solutions, the management and orchestrator mainly senses problems such as insufficient cloud platform resources, and then the management and orchestrator selects task migration and resource reallocation according to the resources of the computing task and / or service and multiple managed cloud platforms. However, due to the centralized deployment of the management and orchestration module and the long distance from the task data source, the existing computing task and / or service migration method cannot meet the requirements of tasks with high latency requirements. Summary of the Invention

[0003] Embodiments of the present application provide a method for migrating wireless computing power tasks, a device for migrating wireless computing power tasks, a communication device, a chip, and a computer-readable storage medium.

[0004] The method for migrating wireless computing power tasks provided by the embodiments of the present application, which is applied to a first cloud platform or a first cloud site, includes:

[0005] Sending a first request to a second cloud platform or a second cloud site; the first request is a migration request for a computing task and / or service;

[0006] If a first response sent by the second cloud platform or the second cloud site is received, then sending a second request to the second cloud platform or the second cloud site; the first response indicates that the computing task and / or service is successfully deployed in the second cloud platform or the second cloud site; the second request is used to request the transmission of data of the computing task and / or service.

[0007] The method for migrating wireless computing power tasks provided by the embodiments of the present application, which is applied to a second cloud platform or a second cloud site, includes:

[0008] Receiving a first request sent by a first cloud platform or a first cloud site or a fifth request sent by a first network element; the first request is a migration request for a computing task and / or service; the fifth request is a migration request for a computing task and / or service;

[0009] Deploying the computing task and / or service based on the first request or the fifth request;

[0010] If the computing task and / or service is successfully deployed, send a first response to the first cloud platform or the first cloud site; or, send a seventh response to the first network element; wherein, the first response indicates that the computing task and / or service is successfully deployed in the second cloud platform or the second cloud site; the seventh response indicates that the computing task and / or service is successfully deployed in the second cloud platform or the second cloud site;

[0011] Receive a second request sent by the first cloud platform or the first cloud site or a sixth request sent by the first network element; the second request is used to request the transmission of data of the computing task and / or service; the sixth request is used to request the transmission of data of the computing task and / or service.

[0012] The wireless computing power task migration device provided by an embodiment of the present application is applied to a first cloud platform or a first cloud site, and includes:

[0013] A first sending unit: configured to send a first request to a second cloud platform or a second cloud site; the first request is a migration request for a computing task and / or service;

[0014] A first receiving unit: configured to receive a first response sent by the second cloud platform or the second cloud site; the first response indicates that the computing task and / or service is successfully deployed in the second cloud platform or the second cloud site; the first sending unit: is further configured to send a second request to the second cloud platform or the second cloud site; the second request is used to request the transmission of data of the computing task and / or service.

[0015] The wireless computing power task migration device provided by an embodiment of the present application is applied to a second cloud platform or a second cloud site, and includes:

[0016] A second receiving unit: configured to receive a first request sent by a first cloud platform or a first cloud site or a fifth request sent by a first network element; the first request is a migration request for a computing task and / or service; the fifth request is a migration request for a computing task and / or service;

[0017] A deployment unit: configured to deploy the computing task and / or service based on the first request or the fifth request;

[0018] The second sending unit: configured to send a first response to the first cloud platform or the first cloud site if the computing task and / or service is successfully deployed; or, send a seventh response to the first network element; wherein, the first response indicates that the computing task and / or service is successfully deployed in the second cloud platform or the second cloud site; the seventh response indicates that the computing task and / or service is successfully deployed in the second cloud platform or the second cloud site; The second receiving unit: is further configured to receive a second request sent by the first cloud platform or the first cloud site or a sixth request sent by the first network element;; The second request is used to request the transmission of data of the computing task and / or service; The sixth request is used to request the transmission of data of the computing task and / or service.

[0019] The communication device provided by the embodiment of the present application includes: a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute any wireless computing power task migration method provided by the embodiment of the present application.

[0020] The chip provided by the embodiment of the present application includes: a processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes any wireless computing power task migration method provided by the embodiment of the present application.

[0021] The computer-readable storage medium provided by the embodiment of the present application is characterized in that it is used to store a computer program, and the computer program enables a computer to execute any wireless computing power task migration method provided by the embodiment of the present application.

[0022] Through the wireless computing power task migration method provided by the embodiment of the present application, the first cloud platform or the first cloud site sends a computing task and / or service migration request to the second cloud platform or the second cloud site. If the first response sent by the second cloud platform or the second cloud site is received, a second request is sent to the second cloud platform or the second cloud site, and the first cloud platform or the first cloud site directly performs task migration with the second cloud platform or the second cloud site, improving the real-time performance of cross-cloud migration of computing tasks and / or services and meeting the low-latency requirements of tasks. Description of the Drawings

[0023] The drawings described herein are used to provide a further understanding of the present application and form a part of the present application. The illustrative embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation of the present application. In the drawings:

[0024] Figure 1 is the implementation process schematic of the wireless computing power task migration method provided by the embodiment of the present application Figure 1 ;

[0025] Figure 2Schematic implementation process of the wireless computing power task migration method provided by the embodiments of this application Figure 2 ;

[0026] Figure 3 Schematic implementation process of the wireless computing power task migration method provided by Example 1 of this application Figure 3

[0027] Figure 4 Schematic implementation process of the wireless computing power task migration method provided by Example 2 of this application Figure 4 ;

[0028] Figure 5 Schematic implementation process of the wireless computing power task migration method provided by Example 3 of this application Figure 5 ;

[0029] Figure 6 Schematic implementation process of the wireless computing power task migration method provided by Example 4 of this application Figure 6 ;

[0030] Figure 7 Schematic structural composition diagram of the wireless computing power task migration device 700 provided by the embodiments of this application;

[0031] Figure 8 Schematic structural composition diagram of the wireless computing power task migration device 800 provided by the embodiments of this application;

[0032] Figure 9 Schematic structural diagram of a communication device provided by the embodiments of this application;

[0033] Figure 10 Schematic structural diagram of the chip provided by the embodiments of this application. Detailed implementation manners

[0034] Next, the technical solutions in the embodiments of this application will be described with reference to the accompanying drawings in the embodiments of this application. Obviously, the described embodiments are some, but not all, of the embodiments of this application. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in this application without creative efforts shall fall within the protection scope of this application.

[0035] It should be noted that in the embodiments of this application, the term "and / or" only describes the association relationship of associated objects and indicates that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the embodiments of this application, the character " / " generally represents an "or" relationship between the associated objects before and after.

[0036] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect corresponding relationship between two parties, may also indicate an associated relationship between the two parties, or may be a relationship such as indication and being indicated, configuration and being configured, etc.

[0037] To facilitate the understanding of the technical solutions of the embodiments of the present application, the related technologies of the embodiments of the present application are described below. The following related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and all of them fall within the protection scope of the embodiments of the present application.

[0038] Existing solutions focus on selecting appropriate nodes for computing offloading and related algorithms according to resources and user delay bandwidth requirements. For future deployment of base station software and other application-related computing tasks and / or services based on a general server cloud platform, since there are a large number of wireless cloud platforms, there may be a hierarchical relationship between cloud platforms and interfaces that may exist for different cloud platform types. Existing solutions cannot solve the problems of low latency requirements for cross-cloud migration of computing tasks and / or services, as well as possible failures, and cloud platform reselection, migration of computing tasks and / or services, and data transmission in response to failures.

[0039] Figure 1 Schematic implementation process of the wireless computing power task migration method provided for the embodiments of the present application Figure 1 , such as Figure 1 shown, the embodiments of the present application provide a wireless computing power task migration method, which is applied to a first cloud platform or a first cloud site. The method includes the following steps:

[0040] Step 101: Send a first request to a second cloud platform or a second cloud site; the first request is a computing task and / or service migration request.

[0041] When the resources of the first cloud platform or the first cloud site cannot meet the computing task and / or service requirements, a computing task and / or service migration request is initiated to the second cloud platform or the second cloud site, and the current task is migrated to the second cloud platform or the second cloud site.

[0042] In an optional implementation manner of the present application, the first request carries at least one of the following information:

[0043] First cloud platform or first cloud site identifier, second cloud platform or second cloud site identifier, computing task and / or service identifier, computing task and / or service type, and parameters required for computing task and / or service deployment.

[0044] The parameters required for computing task and / or service deployment include a computing task and / or service software package or software package address, a computing task and / or service description file, etc.

[0045] In an alternative embodiment of the present application, before sending the first request to the second cloud platform or the second cloud site, the method further includes:

[0046] Sending a third request to at least one cloud platform and / or cloud site; the third request is used to request the computing resource status of the cloud platform and / or cloud site; or,

[0047] Sending a third request to at least one cloud platform and / or cloud site; the third request carries the computing requirements of the computing task and / or service.

[0048] In an alternative embodiment of the present application, the method further includes:

[0049] Receiving at least one second response sent by the at least one cloud platform and / or cloud site; the second response characterizes the computing resource status of the cloud platform and / or cloud site; based on the at least one second response and the computing requirements of the computing task and / or service, determining the second cloud platform or the second cloud site from the at least one cloud platform and / or cloud site; or,

[0050] Receiving at least one third response sent by the at least one cloud platform and / or cloud site; the third response characterizes whether the cloud platform and / or cloud site supports the computing task and / or service; based on the at least one third response, determining the second cloud platform or the second cloud site from the at least one cloud platform and / or cloud site.

[0051] Based on the interface between cloud platforms and / or cloud sites, the first cloud platform or the first cloud site initiates a computing power capacity perception process to one or more cloud platforms and / or cloud sites, requesting the computing resource status of the cloud platforms and / or cloud sites. The computing resource status includes at least one of the following parameters: computing power resource type, total computing power resource, occupied computing power resource, reserved computing power resource, unused computing power resource, available computing power resource, etc., CPU frequency, I / O read and write times, and computing task and / or service throughput, and selects the second cloud platform or the second cloud site according to the computing requirements of the computing task and / or service and the cloud platform resource status. Among them, the computing requirements of the computing task and / or service include the amount of computing data, computing power resource type, number of computing power resources, number of tasks related to the current computing task and / or service, deployment location of related tasks, and bandwidth required for the computing task and / or service.

[0052] Step 102: If the first response sent by the second cloud platform or the second cloud site is received, then send a second request to the second cloud platform or the second cloud site; the first response characterizes that the computing task and / or service is successfully deployed in the second cloud platform or the second cloud site; the second request is used to request the transmission of the data of the computing task and / or service.

[0053] In an optional implementation manner of the present application, if a fourth response sent by the second cloud platform or the second cloud site is received, the second cloud platform or the second cloud site is re-determined; wherein, the fourth response indicates that the deployment of the computing task and / or service fails in the second cloud platform or the second cloud site; or,

[0054] If the first response or the fourth response is not received within a first preset time, the first request is re-sent to the second cloud platform or the second cloud site; if the number of times of sending the first request to the second cloud platform or the second cloud site exceeds a first preset number of times, the second cloud platform or the second cloud site is re-determined; wherein, the fourth response indicates that the deployment of the computing task and / or service fails in the second cloud platform or the second cloud site.

[0055] In an optional implementation manner of the present application, a fifth response sent by the second cloud platform or the second cloud site is received; the fifth response indicates that the data is successfully received by the second cloud platform or the second cloud site;

[0056] Delete the data stored locally.

[0057] In an optional implementation manner of the present application, if a sixth response sent by the second cloud platform or the second cloud site is received, the second cloud platform or the second cloud site is re-determined; wherein, the sixth response indicates that the data is not successfully received by the second cloud platform or the second cloud site; or,

[0058] If the fifth response or the sixth response is not received within a second preset time, the second request is re-sent to the second cloud platform or the second cloud site; if the number of times of sending the second request to the second cloud platform or the second cloud site exceeds a second preset number of times, the second cloud platform or the second cloud site is re-determined; wherein, the fifth response indicates that the data is successfully received by the second cloud platform or the second cloud site; the sixth response indicates that the data is not successfully received by the second cloud platform or the second cloud site.

[0059] In an optional implementation manner of the present application, the types of cloud platforms and / or cloud sites in the at least one cloud platform and / or cloud site include at least one of the following:

[0060] The first type of cloud platform and / or cloud site, which is the cloud platform and / or cloud site managed by the first cloud platform or the first cloud site;

[0061] The second type of cloud platform and / or cloud site, which is the cloud platform and / or cloud site that manages the first cloud platform or the first cloud site;

[0062] The third type of cloud platform and / or cloud site, where the third type of cloud platform and / or cloud site is a cloud platform and / or cloud site that belongs to the same O-Cloud as the first cloud platform or the first cloud site; and,

[0063] The fourth type of cloud platform and / or cloud site, where the fourth type of cloud platform and / or cloud site is a cloud platform and / or cloud site that does not belong to the same O-Cloud as the first cloud platform or the first cloud site.

[0064] In an optional implementation manner of the present application, determining the second cloud platform or the second cloud site from the at least one cloud platform and / or cloud site includes:

[0065] Determining the second cloud platform or the second cloud site from the at least one cloud platform and / or cloud site according to the priority relationship of the cloud platform and / or cloud site; where the cloud platform priority relationship includes at least one of the following:

[0066] The priority of the first type of cloud platform and / or cloud site is higher than the priority of the second type of cloud platform and / or cloud site;

[0067] The priority of the second type of cloud platform and / or cloud site is higher than the priority of the third type of cloud platform and / or cloud site; and,

[0068] The priority of the third type of cloud platform and / or cloud site is higher than the priority of the fourth type of cloud platform and / or cloud site.

[0069] In an optional implementation manner of the present application, if the number of times of re-determining the second cloud platform or the second cloud site exceeds the third preset number of times, a fifth request is sent to the first network element; the fifth request is a migration request for the computing task and / or service;

[0070] Receiving a seventh response sent by the first network element; the seventh response indicates that the computing task and / or service is successfully deployed in the cloud platform or cloud site managed by the first network element;

[0071] Sending a sixth request to the first network element; the sixth request is used to request the transmission of data of the computing task and / or service.

[0072] Receiving an eighth response sent by the first network element; the eighth response indicates that the data is successfully received by the cloud platform or cloud site managed by the first network element.

[0073] Here, the third preset number of times is related to the number of cloud platforms and / or cloud sites included in the at least one cloud platform and / or cloud site.

[0074] In an optional implementation manner of the present application, the fifth request carries at least one of the following information:

[0075] The first cloud platform or the first cloud site identifier, the computing task and / or service identifier, the computing task and / or service type, and the parameters required for the deployment of the computing task and / or service.

[0076] The first network element includes at least one of the following: the Management and Orchestration Function (SMO), the Federation O-Cloud Orchestration and Management (FOCOM), the Network Function Orchestration (NFO), the Non-Real-Time Radio Intelligent Controller (Non-RT RIC), the Near-Real-Time Radio Intelligent Controller (Near-RT RIC), the Network Function Virtualization Orchestrator (NFVO), the Mobile Edge Orchestration (MEO), the Virtual Network Function Manager (VNFM), and the Container Network Function Manager (CNFM).

[0077] Figure 2 Schematic diagram of the implementation process of the wireless computing power task migration method provided by the embodiments of this application Figure 2 , such as Figure 2 As shown, the embodiments of this application provide a wireless computing power task migration method, which is applied to the second cloud platform or the second cloud site. The method includes the following steps:

[0078] Step 201: Receive the first request sent by the first cloud platform or the first cloud site, or the fifth request sent by the first network element; the first request is a migration request for a computing task and / or service; the fifth request is a migration request for a computing task and / or service.

[0079] In an alternative embodiment of this application, the first request carries at least one of the following information:

[0080] The first cloud platform or the first cloud site identifier, the second cloud platform or the second cloud site identifier, the computing task and / or service identifier, the computing task and / or service type, and the parameters required for the deployment of the computing task and / or service.

[0081] In an alternative embodiment of this application, the fifth request carries at least one of the following information:

[0082] The first cloud platform or the first cloud site identifier, the computing task and / or service identifier, the computing task and / or service type, and the parameters required for the deployment of the computing task and / or service.

[0083] In an alternative embodiment of this application, the first network element includes at least one of the following: the Management and Orchestration Function (SMO), the Federation O-Cloud Orchestration and Management (FOCOM), the Network Function Orchestration (NFO), the Non-Real-Time Radio Intelligent Controller (Non-RT RIC), the Near-Real-Time Radio Intelligent Controller (Near-RT RIC), the Network Function Virtualization Orchestrator (NFVO), the Mobile Edge Orchestration (MEO), the Virtual Network Function Manager (VNFM), and the Container Network Function Manager (CNFM).

[0084] In an alternative embodiment of the present application, before receiving the first request sent by the first cloud platform or the first cloud site or the fifth request sent by the first network element, it further includes:

[0085] Receiving a third request sent by the first cloud platform or the first cloud site or the first network element; the third request is used to request the computing resource situation of the second cloud platform or the second cloud site; or

[0086] Receiving a fourth request sent by the first cloud platform or the first cloud site or the first network element; the fourth request carries the computing requirements of the computing task and / or service.

[0087] In an alternative embodiment of the present application, based on the third request, obtaining the computing resource situation of the second cloud platform or the second cloud site; sending a second response to the first cloud platform or the first cloud site or the first network element; the second response characterizes the computing resource situation of the second cloud platform or the second cloud site; or,

[0088] Based on the fourth request and the computing resource situation of the second cloud platform or the second cloud site, determining whether to support the computing task and / or service; sending a third response to the first cloud platform or the first cloud site or the first network element; the third response characterizes whether the second cloud platform or the second cloud site supports the computing task and / or service.

[0089] In an alternative embodiment of the present application, the computing resource situation includes at least one of the following: computing power resource type, total computing power resource, occupied computing power resource, reserved computing power resource, unused computing power resource, available computing power resource and other parameters, CPU frequency, I / O read / write times, computing task and / or service throughput;

[0090] The computing requirements include at least one of the following: computing data volume, computing power resource type, number of computing power resources, number of tasks related to the current computing task and / or service, deployment location of related tasks, and bandwidth required for the computing task and / or service.

[0091] Step 202: Deploy the computing task and / or service based on the first request or the fifth request.

[0092] Step 203: If the computing task and / or service is successfully deployed, send a first response to the first cloud platform or the first cloud site; or, send a seventh response to the first network element; wherein, the first response indicates that the computing task and / or service is successfully deployed in the second cloud platform or the second cloud site; the seventh response indicates that the computing task and / or service is successfully deployed in the second cloud platform or the second cloud site; receive a second request sent by the first cloud platform or the first cloud site or a sixth request sent by the first network element; the second request is used to request the transmission of data of the computing task and / or service; the sixth request is used to request the transmission of data of the computing task and / or service.

[0093] In an alternative embodiment of the present application, if the computing task and / or service is not successfully deployed, send a fourth response to the first cloud platform or the first cloud site and the first network element; the fourth response indicates that the computing task and / or service fails to be deployed in the second cloud platform or the second cloud site.

[0094] If the data is not successfully received, send a sixth response to the first cloud platform or the first cloud site or the first network element; the sixth response indicates that the data is not successfully received by the second cloud platform or the second cloud site.

[0095] The solution of the present application is further described below with specific examples.

[0096] Example 1

[0097] Figure 3 The implementation process schematic of the wireless computing power task migration method provided for Example 1 of the present application Figure 3 , as Figure 3 shown, in this example, the wireless computing power task migration method includes the following steps:

[0098] Step 301: Computing resource request and response.

[0099] Based on the interface between cloud platforms, the first cloud platform or the first cloud site initiates a computing power capability perception process to one or more cloud platforms or cloud sites, requests the computing resource situation of the cloud platform or cloud site (corresponding to the second request), and the computing resource situation includes but is not limited to parameters such as computing resource type, total computing resource, occupied computing resource, and available computing resource, and selects the second cloud platform or the second cloud site according to the computing requirements of the computing task and / or service and the cloud platform resource situation. Among them, the computing requirements include task computing data volume, computing resource type requirements, computing resource quantity requirements, the number of currently task-related tasks, and the deployment location of related tasks. The second cloud platform or the second cloud site feeds back its own computing resource situation (corresponding to the second response).

[0100] Step 302: Task migration request.

[0101] When the first cloud platform or the first cloud site resources cannot meet the computing tasks and / or service requirements, a computing task and / or service migration request (corresponding to the first request) is sent to the second cloud platform or the second cloud site to migrate the current task to the second cloud platform or the second cloud site. The computing task and / or service migration request includes: the identifier of the first cloud platform or the first cloud site, the identifier of the second cloud platform or the second cloud site, the identifier of the computing task and / or service, the type of the computing task and / or service, and the parameters required for the deployment of the computing task and / or service, including the computing task and / or service software package or the software package address, the computing task and / or service description file, etc.

[0102] If the second cloud platform or the second cloud site successfully deploys the computing task and / or service, step 303: task migration response (ACK) is executed. After the second cloud platform or the second cloud site completes the deployment of the computing task and / or service, a computing task and / or service migration ACK response (corresponding to the first response) is sent to the first cloud platform or the first cloud site to feedback that the task has been successfully deployed.

[0103] If the second cloud platform or the second cloud site fails to deploy the computing task and / or service, step 304: task migration response (NACK) is executed. When the second cloud platform or the second cloud site fails to deploy the computing task and / or service, for example, due to other computing tasks and / or services preempting resources or computing hardware failures, etc., resulting in insufficient current computing-related resources, and the second cloud platform or the second cloud site cannot recover the failure within a specific time threshold (T1), a computing task and / or service migration NACK response (corresponding to the fourth response) is sent to the first cloud platform or the first cloud site, and the cause of the failure is fed back to the first cloud platform or the first cloud site. The cause of the failure in the NACK response includes at least one of the following: the computing task and / or service software package reception fails, the software package address is unreachable (including network failure, address error, or no permission), the computing task and / or service description file reception fails, the computing task and / or service description file parsing fails, and the computing task and / or service startup fails (including no cloud platform permission, software version error, cloud platform resource limitation, cloud platform resource insufficiency, etc.). After receiving the NACK response from the second cloud platform or the second cloud site, the first cloud platform or the first cloud site needs to reselect the second cloud platform or the second cloud site.

[0104] Step 305: Retransmit the task migration request.

[0105] After the first cloud platform or the first cloud site sends a computing task and / or a service migration request, it waits for a response from the second cloud platform or the second cloud site. When the first cloud platform or the first cloud site does not receive a response from the second cloud platform or the second cloud site after exceeding the specified time threshold (T2, corresponding to the first preset time), it initiates a retransmission, that is, resends the computing task and / or the service migration request to the second cloud platform or the second cloud site. When the number of retransmissions exceeds the specified threshold (N1, corresponding to the first preset number of times), the first cloud platform or the first cloud site considers the second cloud platform or the second cloud site unreachable and needs to reselect the second cloud platform or the second cloud site.

[0106] Step 306: Data transfer request related to the task.

[0107] After the first cloud platform or the first cloud site receives a response indicating successful migration of the computing power task from the second cloud platform or the second cloud site, it sends a data transfer request (corresponding to the second request) to the second cloud platform or the second cloud site to send the computing task and / or service-related data to the second cloud platform or the second cloud site.

[0108] If the second cloud platform or the second cloud site successfully receives and / or caches the task-related data, perform Step 307: Data transfer response (ACK). After the second cloud platform or the second cloud site completes data reception and caching, it sends a data transfer ACK response (corresponding to the fifth response) to the first cloud platform or the first cloud site, feedbacking that the task-related data has been successfully received. After the first cloud platform or the first cloud site receives the ACK response from the second cloud platform or the second cloud site, it deletes the local cached data.

[0109] If the second cloud platform or the second cloud site fails to receive the task-related data, perform Step 308: Task migration response (NACK). When the second cloud platform or the second cloud site fails to receive data, for example, due to other storage tasks preempting resources or storage hardware failures and other problems resulting in insufficient storage-related resources, and the second cloud platform or the second cloud site cannot recover the failure within a specific time threshold (T3), it sends a data transfer NACK response (corresponding to the sixth response) to the first cloud platform or the first cloud site and feedbacks the cause of the failure to the first cloud platform or the first cloud site. Among them, the cause of the failure in the NACK response can include: data reception failure (including no permission to deposit, insufficient cloud platform resources), data verification failure, etc. At this time, after the first cloud platform or the first cloud site receives the NACK response from the second cloud platform or the second cloud site, it needs to reselect the second cloud platform or the second cloud site.

[0110] 309: Request for retransmitting data.

[0111] After the first cloud platform or the first cloud site sends a data transmission, it waits for a response from the second cloud platform or the second cloud site. When the first cloud platform or the first cloud site does not receive a response from the second cloud platform or the second cloud site after exceeding the specified time threshold (T4, corresponding to the second preset time), a retransmission is initiated, that is, a computing task and / or a service-related data transmission request is resent to the second cloud platform or the second cloud site. When the number of retransmissions exceeds the specified threshold (N2, corresponding to the second preset number of times), the first cloud platform or the first cloud site considers that the second cloud platform or the second cloud site is unreachable and needs to reselect the second cloud platform or the second cloud site.

[0112] Example 2

[0113] Figure 4 Schematic diagram of the implementation process of the wireless computing power task migration method provided in Example 2 of this application Figure 4 , Exemplarily, based on the O-RAN architecture cloud platform management and orchestration architecture, O-Cloud includes an Infrastructure Management Services (IMS) for managing infrastructure resources, and multiple Deployment Management Services (DMS) for managing workloads (for example, for tasks Pods deployed based on Kubernetes containerization as the workloads to be managed); SMO includes FOCOM (interacting with O-Cloud IMS) and NFO (interacting with O-Cloud DMS). For the task migration and data transmission mentioned in the embodiments of this application, when the first cloud platform or the first cloud site and the second cloud platform or the second cloud site are both deployed in O-Cloud, task migration and data transmission requests and responses can be carried out through DMS. When the first cloud platform or the first cloud site and the second cloud platform or the second cloud site are deployed across O-Cloud, task migration and data transmission requests and responses can be carried out through IMS. Based on the O-RAN architecture, IMS is responsible for the computing power resource coordination within O-Cloud and the selection / reselection of cloud platforms across O-Cloud. When the resources of the current O-Cloud cannot meet the task computing power requirements, IMS senses the computing power resources of other O-Clouds, and selects the second cloud platform or the second cloud site according to the task computing requirements and the cloud platform resource situation; or IMS sends the computing power requirements of the task to other nearby O-Cloud IMSs, and after receiving multiple responses from other O-Cloud IMSs on whether the task meets the task requirements, combines the task computing power requirements to select a suitable second cloud platform or the second cloud site. In this example, the wireless computing power task migration method includes the following steps:

[0114] When other cloud platforms / cloud sites in O-Cloud1 meet the task computing power requirements, perform step 401: Re-select the second cloud platform or the second cloud site in O-Cloud1 and deploy the task.

[0115] When other cloud platforms / cloud sites in O-Cloud1 meet the task computing power requirements, IMS1 re-selects the second cloud platform or the second cloud site in O-Cloud1 and initiates task deployment to the second cloud platform or the second cloud site.

[0116] When other cloud platforms / cloud sites in O-Cloud1 meet the task computing power requirements, perform step 402 or step 403.

[0117] Step 402: Re-select the second cloud platform or the second cloud site according to the task requirements and computing resource perception and perform task migration / data transfer. When all cloud platforms / cloud sites in O-Cloud1 do not meet the task computing power requirements, IMS1 selects the second cloud platform or the second cloud site according to other O-Cloud computing resources perceived through the perception interaction process, based on the task computing requirements and the cloud platform resource situation.

[0118] Step 403: Re-select the second cloud platform or the second cloud site according to the task requirements and computing resource perception and perform task migration / data transfer. When all cloud platforms / cloud sites in O-Cloud1 do not meet the task computing power requirements, IMS1 sends the computing power requirements of the task to nearby O-Cloud2 IMS2 and O-Cloud3 IMS3, and after receiving multiple responses from IMS2 and IMS3 on whether the task meets the task requirements, combines the task computing power requirements to select a suitable second cloud platform or the second cloud site. In this example, candidate cloud platform 1 is the re-selected second cloud platform or the second cloud site.

[0119] Example 3

[0120] Figure 5 Schematic of the implementation process of the wireless computing power task migration method provided for Example 3 of this application Figure 5, Exemplarily, for the scenario of a hierarchical cloud platform architecture for multi-cloud deployment, for example, for the O-RAN architecture, within an O-Cloud, it includes a Central Cloud, a Regional Cloud, and an Edge Cloud. In this example, the first cloud platform or the first cloud site can be the Central Cloud, the Regional Cloud, or the Edge Cloud. When the first cloud platform or the first cloud site is the Central Cloud, the second cloud platform or the second cloud site it manages and the candidate cloud platform are the Regional Cloud. When the cloud platform is the Regional Cloud, the second cloud platform or the second cloud site it manages and the candidate cloud platform are the Edge Cloud. When the first cloud platform or the first cloud site has other cloud platforms it manages, the first cloud platform or the first cloud site first selects a candidate cloud platform for task migration from the cloud platforms it manages. When the resources of the managed cloud platform do not meet the task requirements, it initiates the selection of candidate cloud platforms and the migration of computing tasks and / or services in adjacent O-Clouds; or selects candidate cloud platforms through the cloud platform centralized management and orchestration function SMO and performs the migration of computing tasks and / or services. The wireless computing power task migration method includes the following steps:

[0121] When the other cloud platforms managed by the first cloud platform or the first cloud site meet the resource requirements for computing tasks and / or services, such as the resource requirements for computing tasks and / or services, etc., then perform step 5011 and step 5012.

[0122] Step 5011: Re-select the managed candidate cloud.

[0123] The first cloud platform or the first cloud site selects the cloud platform it manages as the candidate cloud platform.

[0124] Step 5012: Task migration / data transfer request / response.

[0125] The first cloud platform or the first cloud site sends a task migration and task-related data transfer request to the candidate cloud platform and receives the candidate cloud platform's response; for the detailed process, refer to Example 1 and it will not be elaborated here.

[0126] When the other cloud platforms managed by the first cloud platform or the first cloud site do not meet the resource requirements for computing tasks and / or services, if the cloud platforms included in the adjacent O-Cloud meet the resource requirements for computing tasks and / or services: perform step 5021, step 5022, and step 5023.

[0127] Step 5021: Task migration / data transfer request.

[0128] The first cloud platform or the first cloud site sends a task migration and task-related data transfer request to the adjacent O-Cloud. Among them, the request can be sent to the Central Cloud, Regional Cloud or Edge Cloud of the adjacent O-Cloud, depending on the composition method of the internal hierarchical cloud platforms in the O-Cloud and the interface definition method.

[0129] Step 5022: Select candidate cloud task migration / data transfer.

[0130] The cloud platforms in the adjacent O-Cloud allocate corresponding resources and deploy computing tasks and / or services according to the computing tasks and / or service resource requirements. For the detailed process, refer to Example 1 and will not be elaborated here; or select candidate cloud platforms according to the relationship of its internal hierarchical cloud platforms and initiate computing task and / or service migration and data transfer requests.

[0131] Step 5023: Task migration / data transfer response.

[0132] The adjacent O-Cloud sends a task migration and task-related data transfer response to the first cloud platform or the first cloud site.

[0133] When there is no adjacent O-Cloud for the O-Cloud to which the first cloud platform or the first cloud site belongs, the interface between O-Clouds does not exist, the adjacent O-Cloud is unreachable, or the resources of the adjacent O-Cloud do not meet the requirements of the computing tasks and / or services to be migrated, due to the high deployment location of the SMO, which has all cloud platform information and the ability to centrally manage cloud platforms across O-Clouds, the SMO is used to select candidate cloud platforms and perform task migration, and Steps 5031, 5032, 5033 and 5034 are executed.

[0134] Step 5031: Task migration / data transfer request.

[0135] The first cloud platform or the first cloud site sends a task migration and task-related data transfer request to the management and orchestration function SMO.

[0136] Step 5032: Select candidate cloud platforms.

[0137] The SMO selects compliant O-Clouds and candidate cloud platforms among the O-Clouds and cloud platforms it manages according to the computing tasks and / or service resource requirements.

[0138] Step 5033: Task migration / data transfer request / response.

[0139] The SMO sends a task migration and task-related data transfer request to the candidate cloud platforms, and receives the response sent by the candidate cloud platforms after the corresponding task migration or data transfer is completed on the candidate cloud platforms.

[0140] Step 5034: Task migration / data transfer response (ACK / NACK).

[0141] The SMO sends a task migration and task-related data transfer response to the first cloud platform or the first cloud site.

[0142] Example 4 Figure 6 Schematic diagram of the implementation process of the wireless computing power task migration method provided in Example 4 of this application Figure 6 , the first cloud platform or the first cloud site can be a Regional Cloud or an Edge Cloud. When the cloud platform is a Regional Cloud, the cloud platform that manages it is a Central Cloud; when the first cloud platform or the first cloud site is an Edge Cloud, the cloud platform that manages it is a Regional Cloud. When the first cloud platform or the first cloud site is a Regional Cloud and does not have a managed Edge Cloud or the resources of its managed Edge Cloud are insufficient, or when the first cloud platform or the first cloud site is an Edge Cloud, the first cloud platform or the first cloud site first initiates a computing task and / or service migration and data transfer request from the cloud platform that manages it (Central Cloud or Regional Cloud, hereinafter referred to as the "managing cloud platform"). When the managing cloud platform and its managed resources do not meet the task requirements, it initiates the selection of candidate cloud platforms in adjacent O-Clouds and computing tasks and / or service migrations; or selects candidate cloud platforms through the SMO and performs computing tasks and / or service migrations. In this example, the wireless computing power task migration method includes the following steps:

[0143] When the first cloud platform or the first cloud site is a managed cloud platform and does not have other managed cloud platforms or the resources of its managed cloud platform are insufficient, it sends a computing task and / or service migration and data transfer request to the managing cloud platform, and executes steps 6011, 6012, 6013, and 6014.

[0144] Step 6011: Task migration / data transfer request.

[0145] The first cloud platform or the first cloud site sends a task migration and task-related data transfer request to the managing cloud platform, such as Central Cloud (when the first cloud platform or the first cloud site is a Regional Cloud) or Regional Cloud (when the first cloud platform or the first cloud site is an Edge Cloud).

[0146] Step 6012: Select candidate cloud platforms.

[0147] The management cloud platform selects eligible candidate cloud platforms (belonging to the same O-Cloud or across O-Clouds, according to the internal hierarchical cloud platform relationship) from the cloud platforms it manages based on the computing tasks and / or service resource requirements.

[0148] Step 6013: Task migration / data transfer request / response.

[0149] The management cloud platform sends a task migration and task-related data transfer request to the candidate cloud platforms, and after the candidate cloud platforms complete the corresponding task migration or data transfer, receives the response sent by the candidate cloud platforms.

[0150] Step 6014: Task migration / data transfer response (ACK / NACK).

[0151] The management cloud platform sends a task migration and task-related data transfer response to the first cloud platform or the first cloud site.

[0152] When the management cloud platform and the resources it manages do not meet the resource requirements for computing tasks and / or services, the first cloud platform or the first cloud site requests task migration and task-related data transfer from the adjacent O-Cloud, and executes steps 6021, 6022, and 6023.

[0153] Step 6021: Task migration / data transfer request.

[0154] The first cloud platform or the first cloud site sends a task migration and task-related data transfer request to the adjacent O-Cloud. Among them, the request can be sent to the Central Cloud, Regional Cloud, or Edge Cloud of the adjacent O-Cloud, depending on the composition of the internal hierarchical cloud platforms in the O-Cloud and the interface definition method.

[0155] Step 6022: Select candidate cloud for task migration / data transfer.

[0156] The cloud platforms in the adjacent O-Cloud allocate corresponding resources and deploy computing tasks and / or services according to the computing tasks and / or service resource requirements. For the detailed process, refer to Example 1 and will not be elaborated here; or select candidate cloud platforms according to their internal hierarchical cloud platform relationship and initiate requests for computing task and / or service migration and data transfer.

[0157] Step 6023: Task migration / data transfer response.

[0158] The adjacent O-Cloud sends a task migration and task-related data transfer response to the first cloud platform or the first cloud site.

[0159] When there is no adjacent O-Cloud for the O-Cloud to which the first cloud platform or the first cloud site belongs, the interface between O-Clouds does not exist, the adjacent O-Cloud is unreachable, or the resources of the adjacent O-Cloud do not meet the requirements of the computing tasks and / or services to be migrated, the first cloud platform or the first cloud site requests task migration and task-related data transmission from the Management and Orchestration Function (SMO), and executes steps 6031, 6032, 6033, and 6034.

[0160] Step 6031: Task migration / data transmission request.

[0161] The first cloud platform or the first cloud site sends a task migration and task-related data transmission request to the Management and Orchestration Function (SMO).

[0162] Step 6032: Select candidate cloud platforms.

[0163] Based on the computing task and / or service resource requirements, the SMO selects the compliant O-Clouds and candidate cloud platforms from the O-Clouds and cloud platforms it manages.

[0164] Step 6033: Task migration / data transmission request / response.

[0165] The SMO sends a task migration and task-related data transmission request to the candidate cloud platforms, and after the candidate cloud platforms complete the corresponding task migration or data transmission, receives the response sent by the candidate cloud platforms.

[0166] Step 6034: Task migration / data transmission response (ACK / NACK).

[0167] The SMO sends a task migration and task-related data transmission response to the first cloud platform or the first cloud site.

[0168] In an optional implementation manner of this application, a method for determining the task migration threshold from the first cloud platform or the first cloud site on the wireless side to the destination cloud platform, i.e., the second cloud platform or the second cloud site, and the data transmission threshold related to the task migration is proposed. Based on the service delay requirement, this embodiment combines the network status and the task computing ability to determine the delay T during the task migration process proposed in this solution. migration It includes the waiting migration time threshold T1 of the destination cloud platform, i.e., the second cloud platform or the second cloud site, the waiting response time threshold T2 of the first cloud platform or the first cloud site, and the retransmission migration request times threshold N1 of the first cloud platform or the first cloud site; and the delay T during the data transmission process. transfer It includes the waiting data reception time threshold T3 of the destination cloud platform, i.e., the second cloud platform or the second cloud site, the waiting response time threshold T4 of the first cloud platform or the first cloud site, and the retransmission data times threshold N2 of the first cloud platform or the first cloud site. Among them, T migration= T2 × N1, T1 < T2, T transfer = T4 × N2, T3 < T4.

[0169] The end-to-end latency of the service is generally composed of the task calculation time and the data transmission time in the network. For the case of real-time triggering of task migration and data transmission between the first cloud platform or the first cloud site and the destination platform, the sum of the above latencies needs to meet the end-to-end latency requirement T delay , as follows:

[0170] T computing + T transminssion + T migration + T transfer ≤ T delay .

[0171] Among them, if the data transmission is carried out simultaneously with the task migration, then:

[0172] T computing + T transminssion = max{T migration , T transfer}, where T computing is the task calculation time, and T transminssion is the data transmission time in the network.

[0173] In addition, for services with periodic data arrivals, such as video services, etc., when task migration and data transmission support non-real-time triggering, the task migration latency can be customized based on the actual requirements of the service. To ensure data synchronization during task processing, after the task migration is completed, the data transmission latency needs to be completed within the service arrival period T period , as follows: T transfer < T period .

[0174] An embodiment of the present application proposes a wireless computing power task migration method, which is used in the scenario of co-deployment of wireless network functions and applications based on a general server cloud platform. Based on the newly added interface between adjacent wireless cloud platforms, when the computing and storage resources of the first cloud platform or the first cloud site on the wireless side cannot meet the computing tasks and / or service requirements, a computing task and / or service migration and data transmission related to the computing task and / or service are initiated to the second cloud platform or the second cloud site. For the faults in the process of computing task and / or service migration and data transmission, based on the hierarchical cloud platform structure on the wireless side and the cause of the fault, retransmission related to computing task and / or service migration and data transmission is performed, and processes related to cloud platform reselection, computing task and / or service and data forwarding are initiated to adjacent cloud platforms, upper management cloud platforms, or centralized management and orchestration functions, etc., to solve the problem that cloud platforms in the existing solution are unaware of each other. By the management and orchestrator perceiving the insufficient resources of the cloud platform and according to the computing task and / or service requirements and the resource conditions of multiple managed cloud platforms, the problem that the task migration and resource reallocation latency is large and cannot meet the task requirements, especially those with high latency requirements, is solved. By enhancing the perception ability between cloud platforms, the real-time performance of cross-cloud migration of computing tasks and / or services is improved to meet the low-latency requirements of tasks.

[0175] An embodiment of the present application also provides a wireless computing power task migration device 700, refer to Figure 7 , the wireless computing power task migration device 700 in this embodiment is applied to the first cloud platform or the first cloud site, and includes:

[0176] The first sending unit 710: is used to send a first request to the second cloud platform or the second cloud site; the first request is a computing task and / or service migration request;

[0177] The first receiving unit 720: is used to receive the first response sent by the second cloud platform or the second cloud site; the first response indicates that the computing task and / or service is successfully deployed in the second cloud platform or the second cloud site;

[0178] The first sending unit 710: is further used to send a second request to the second cloud platform or the second cloud site; the second request is used to request the transmission of data of the computing task and / or service.

[0179] In an embodiment of the present application, the first sending unit 710: is used to send a third request to at least one cloud platform and / or cloud site; the third request is used to request the computing resource conditions of the cloud platform and / or cloud site; or,

[0180] The first sending unit 710: is used to send a fourth request to at least one cloud platform and / or cloud site; the fourth request includes the computing requirements of the computing task and / or service.

[0181] In an embodiment of the present application, the first receiving unit 720 is configured to receive at least one second response sent by the at least one cloud platform and / or cloud site; the second response characterizes the computing resource situation of the cloud platform and / or cloud site; based on the at least one second response and the computing requirements of the computing task and / or service, determine the second cloud platform or the second cloud site from the at least one cloud platform and / or cloud site; or,

[0182] The first receiving unit 720 is configured to receive at least one third response sent by the at least one cloud platform and / or cloud site; the third response characterizes whether the cloud platform and / or cloud site supports the computing task and / or service; based on the at least one third response, determine the second cloud platform or the second cloud site from the at least one cloud platform and / or cloud site.

[0183] In an embodiment of the present application, the computing resource situation includes at least one of the following: computing power resource type, total computing power resource, occupied computing power resource, reserved computing power resource, unused computing power resource, available computing power resource and other parameters, CPU frequency, I / O read and write times, and computing task and / or service throughput;

[0184] The computing requirements include at least one of the following: amount of computing data, computing power resource type, number of computing power resources, number of tasks related to the current computing task and / or service, deployment location of related tasks, and bandwidth required for the computing task and / or service.

[0185] In an embodiment of the present application, the first receiving unit 720 is configured to re-determine the second cloud platform or the second cloud site if a fourth response sent by the second cloud platform or the second cloud site is received; wherein the fourth response characterizes that the deployment of the computing task and / or service in the second cloud platform or the second cloud site fails; or, if the first response or the fourth response is not received within the first preset time; then re-send the first request to the second cloud platform or the second cloud site; if the number of times of sending the first request to the second cloud platform or the second cloud site exceeds the first preset number of times; then re-determine the second cloud platform or the second cloud site; wherein the fourth response characterizes that the deployment of the computing task and / or service in the second cloud platform or the second cloud site fails.

[0186] In an embodiment of the present application, the first receiving unit 720 is configured to receive a fifth response sent by the second cloud platform or the second cloud site; the fifth response characterizes that the data is successfully received by the second cloud platform or the second cloud site; delete the data stored locally.

[0187] In an embodiment of the present application, the first receiving unit 720 is configured to: if a sixth response sent by the second cloud platform or the second cloud site is received, re-determine the second cloud platform or the second cloud site; wherein the sixth response indicates that the data has not been successfully received by the second cloud platform or the second cloud site; or, if the fifth response or the sixth response is not received within a second preset time, re-send the second request to the second cloud platform or the second cloud site; if the number of times of sending the second request to the second cloud platform or the second cloud site exceeds a second preset number of times, re-determine the second cloud platform or the second cloud site; wherein the fifth response indicates that the data has been successfully received by the second cloud platform or the second cloud site; and the sixth response indicates that the data has not been successfully received by the second cloud platform or the second cloud site.

[0188] In an embodiment of the present application, the types of cloud platforms and / or cloud sites in the at least one cloud platform and / or cloud site include at least one of the following: a first type of cloud platform and / or cloud site, which is a cloud platform and / or cloud site managed by the first cloud platform or the first cloud site; a second type of cloud platform and / or cloud site, which is a cloud platform and / or cloud site that manages the first cloud platform or the first cloud site; a third type of cloud platform and / or cloud site, which is a cloud platform and / or cloud site belonging to the same O-Cloud as the first cloud platform or the first cloud site; and a fourth type of cloud platform and / or cloud site, which is a cloud platform and / or cloud site that does not belong to the same O-Cloud as the first cloud platform or the first cloud site.

[0189] In an embodiment of the present application, the first receiving unit 720 is configured to determine the second cloud platform or the second cloud site from the at least one cloud platform and / or cloud site according to the priority relationship of the cloud platform and / or cloud site; wherein the priority relationship of the cloud platform and / or cloud site includes at least one of the following: the priority of the first type of cloud platform and / or cloud site is higher than the priority of the second type of cloud platform and / or cloud site; the priority of the second type of cloud platform and / or cloud site is higher than the priority of the third type of cloud platform and / or cloud site; and the priority of the third type of cloud platform and / or cloud site is higher than the priority of the fourth type of cloud platform and / or cloud site.

[0190] In an embodiment of the present application, the first sending unit 710: is configured to send a fifth request to the first network element if the number of times of re-determining the second cloud platform or the second cloud site exceeds a third preset number; the fifth request is a migration request for the computing task and / or service; the first receiving unit 720: is configured to receive a seventh response sent by the first network element; the seventh response indicates that the computing task and / or service is successfully deployed in the cloud platform or cloud site managed by the first network element; the first sending unit 710: is configured to send a sixth request to the second network element; the sixth request is used to request the transmission of data of the computing task and / or service; the first receiving unit 720: is configured to receive an eighth response sent by the first network element; the eighth response indicates that the data is successfully received by the cloud platform or cloud site managed by the first network element.

[0191] In an embodiment of the present application, the first network element includes at least one of the following: Service Management and Orchestration (SMO), Federation O-Cloud Orchestration and Management (FOCOM), Network Function Orchestration (NFO), Non-Real-Time Radio Intelligent Controller (Non-RT RIC), Near-Real-Time Radio Intelligent Controller (Near-RT RIC), Network Function Virtualization Orchestrator (NFVO), Mobile Edge Orchestration (MEO), Virtual Network Function Manager (VNFM), and Container Network Function Manager (CNFM).

[0192] In an embodiment of the present application, the first request carries at least one of the following information: first cloud platform or first cloud site identifier, second cloud platform or second cloud site identifier, computing task and / or service identifier, computing task and / or service type, and parameters required for the deployment of the computing task and / or service.

[0193] In an embodiment of the present application, the fifth request carries at least one of the following information: first cloud platform or first cloud site identifier, computing task and / or service identifier, computing task and / or service type, and parameters required for the deployment of the computing task and / or service.

[0194] Those skilled in the art should understand that Figure 7 The implementation functions of the units in the wireless computing power task migration device 700 shown can be understood with reference to the relevant descriptions of the foregoing method. Figure 7 The functions of the units in the wireless computing power task migration device 700 shown can be implemented by a program running on a processor or by specific logic circuits.

[0195] An embodiment of the present application further provides a wireless computing power task migration device 800. Referring to Figure 8 , the wireless computing power task migration device 800 in this embodiment is applied to a second cloud platform or a second cloud site and includes:

[0196] Second receiving unit 810: configured to receive a first request sent by a first cloud platform or a first cloud site, or a fifth request sent by a first network element; the first request is a migration request for a computing task and / or a service; the fifth request is a migration request for a computing task and / or a service;

[0197] Deployment unit 820: configured to deploy the computing task and / or the service based on the first request or the fifth request;

[0198] Second sending unit 830: configured to, if the computing task and / or the service is successfully deployed, send a first response to the first cloud platform or the first cloud site; or, send a seventh response to the first network element; wherein, the first response indicates that the computing task and / or the service is successfully deployed in the second cloud platform or the second cloud site; the seventh response indicates that the computing task and / or the service is successfully deployed in the second cloud platform or the second cloud site;

[0199] The second receiving unit 810: is further configured to receive a second request sent by the first cloud platform or the first cloud site, or a sixth request sent by the first network element; the second request is used to request to transmit data of the computing task and / or the service; the sixth request is used to request to transmit data of the computing task and / or the service.

[0200] In an embodiment of the present application, the first network element includes at least one of the following: a Management and Orchestration Function (SMO), a Federation O-Cloud Orchestration and Management (FOCOM), a Network Function Orchestration (NFO), a Non-Real-Time Radio Intelligent Controller (Non-RT RIC), a Near-Real-Time Radio Intelligent Controller (Near-RT RIC), a Network Function Virtualization Orchestrator (NFVO), a Mobile Edge Orchestration (MEO), a Virtual Network Function Manager (VNFM), and a Container Network Function Manager (CNFM).

[0201] In an embodiment of the present application, the second receiving unit 810: is further configured to receive a third request sent by the first cloud platform or the first cloud site or the first network element; the third request is used to request the computing resource situation of the second cloud platform or the second cloud site; or,

[0202] The second receiving unit 810: is further configured to receive a fourth request sent by the first cloud platform or the first cloud site or the first network element; the fourth request carries the computing requirements of the computing task and / or the service.

[0203] The second sending unit 830: is configured to obtain the computing resource situation of the second cloud platform or the second cloud site based on the second request; send a second response to the first cloud platform or the first cloud site or the first network element; the second response indicates the computing resource situation of the second cloud platform or the second cloud site; or,

[0204] The second sending unit 830: determines whether to support the computing task and / or service based on the fourth request and the computing resource situation of the second cloud platform or the second cloud site; sends a third response to the first cloud platform or the first cloud site or the first network element; the third response indicates whether the second cloud platform or the second cloud site supports the computing task and / or service.

[0205] In the embodiments of the present application, the computing resource situation includes at least one of the following: computing power resource type, total computing power resource, occupied computing power resource, reserved computing power resource, unused computing power resource, available computing power resource and other parameters, CPU frequency, I / O read / write times, computing task and / or service throughput;

[0206] The computing requirements include at least one of the following: computing data volume, computing power resource type, computing power resource quantity, number of tasks related to the current computing task and / or service, deployment location of related tasks, and bandwidth required for the computing task and / or service.

[0207] In the embodiments of the present application, the second sending unit 830: is used to send a fourth response to the first cloud platform or the first cloud site or the first network element if the computing task and / or service fails to be deployed successfully; the fourth response indicates that the deployment of the computing task and / or service fails in the second cloud platform or the second cloud site; the second sending unit 830: is used to send a sixth response to the first cloud platform or the first cloud site or the first network element if the data fails to be received successfully and / or fails to be cached successfully; the sixth response indicates that the data fails to be received successfully by the second cloud platform or the second cloud site.

[0208] In the embodiments of the present application, the first request carries at least one of the following information: first cloud platform or first cloud site identifier, second cloud platform or second cloud site identifier, computing task and / or service identifier, computing task and / or service type, and parameters required for the deployment of the computing task and / or service.

[0209] In the embodiments of the present application, the fifth request carries at least one of the following information:

[0210] First cloud platform or first cloud site identifier, computing task and / or service identifier, computing task and / or service type, and parameters required for the deployment of the computing task and / or service.

[0211] Those skilled in the art should understand that Figure 8 The implementation functions of the units in the wireless computing power task migration device 800 shown can be understood with reference to the relevant descriptions of the foregoing method. Figure 8The functions of the units in the wireless computing power task migration device 800 shown can be implemented by a program running on a processor or by specific logic circuits.

[0212] Figure 9 It is a schematic structural diagram of a communication device 900 provided by an embodiment of the present application. Figure 9 The communication device 900 shown includes a processor 910. The processor 910 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0213] Optionally, as Figure 9 shown, the communication device 900 may further include a memory 920. Among them, the processor 910 can call and run a computer program from the memory 920 to implement the method in the embodiment of the present application.

[0214] Among them, the memory 920 can be a separate device independent of the processor 910 or integrated in the processor 910.

[0215] Optionally, as Figure 9 shown, the communication device 900 may further include a transceiver 930. The processor 910 can control the transceiver 930 to communicate with other devices. Specifically, it can send information or data to other devices or receive information or data sent by other devices.

[0216] Among them, the transceiver 930 can include a transmitter and a receiver. The transceiver 930 may further include antennas, and the number of antennas can be one or more.

[0217] The communication device 900 can specifically be the wireless computing power task migration device 700 / wireless computing power task migration device 800 in the embodiment of the present application, and the communication device 900 can implement the corresponding processes implemented by the wireless computing power task migration device 700 / wireless computing power task migration device 800 in each method of the embodiment of the present application. For the sake of brevity, it will not be elaborated here.

[0218] Figure 10 It is a schematic structural diagram of a chip in an embodiment of the present application. Figure 10 The chip 1000 shown includes a processor 1010. The processor 1010 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0219] Optionally, as Figure 10 shown, the chip 1000 may further include a memory 1020. Among them, the processor 1010 can call and run a computer program from the memory 1020 to implement the method in the embodiment of the present application.

[0220] Among them, the memory 1020 can be a separate device independent of the processor 1010, or can be integrated in the processor 1010.

[0221] Optionally, the chip 1000 may further include an input interface 1030. Among them, the processor 1010 can control the input interface 1030 to communicate with other devices or chips. Specifically, it can obtain information or data sent by other devices or chips.

[0222] Optionally, the chip 1000 may further include an output interface 1040. Among them, the processor 1010 can control the output interface 1040 to communicate with other devices or chips. Specifically, it can output information or data to other devices or chips.

[0223] The chip can be applied to the wireless computing power task migration device 700 / the wireless computing power task migration device 800 in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the wireless computing power task migration device 700 / the wireless computing power task migration device 800 in the various methods of the embodiments of the present application. For the sake of brevity, it will not be elaborated here.

[0224] It should be understood that the chip mentioned in the embodiments of the present application can also be referred to as a system-on-chip, system chip, chip system or system-on-chip, etc.

[0225] It should be understood that the processor in the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiments can be completed by the integrated logic circuit in the hardware of the processor or instructions in the form of software. The above-mentioned processor can be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. It can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor. The software module can be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. This storage medium is located in the memory, and the processor reads the information in the memory and combines its hardware to complete the steps of the above method.

[0226] It can be understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchlink dynamic random access memory (SLDRAM), and direct rambus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include but not be limited to these and any other suitable types of memory.

[0227] It should be understood that the above-mentioned memory is by way of example but not limitation. For example, the memory in the embodiments of the present application may also be a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate SDRAM (DDR SDRAM), an enhanced SDRAM (ESDRAM), a synch link DRAM (SLDRAM), and a direct rambus random access memory (DR RAM), etc. That is to say, the memory in the embodiments of the present application is intended to include but not be limited to these and any other suitable types of memory.

[0228] The embodiments of the present application also provide a computer-readable storage medium for storing a computer program. The computer-readable storage medium can be applied to the wireless computing power task migration device 700 / the wireless computing power task migration device 800 in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the wireless computing power task migration device 700 / the wireless computing power task migration device 800 in each method of the embodiments of the present application. For the sake of brevity, details are not described herein again.

[0229] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in connection with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in hardware or software depends on the specific application and design constraints of the technical solution. A person skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0230] Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments, and details are not described herein again.

[0231] In several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces. The indirect coupling or communication connection of the devices or units can be in electrical, mechanical, or other forms.

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

[0233] In addition, the functional units in each embodiment of the present application can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit.

[0234] When the above-mentioned functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, a server, or a wireless computing power task migration device 700 / wireless computing power task migration device 800, etc.) to execute all or part of the steps of the methods described in various embodiments of this application. The aforementioned storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs that can store program codes.

[0235] As described above, the above is only the specific implementation manner of this application, but the protection scope of this application is not limited thereto. Any person skilled in the art within the technical scope disclosed by this application can easily think of changes or substitutions, which should all be covered within the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

1. A wireless computing power task migration method, characterized in that, Applied to the first cloud platform or the first cloud site, including: Sending a first request to the second cloud platform or the second cloud site; the first request is a migration request for a computing task and / or a service; If receiving a first response sent by the second cloud platform or the second cloud site, sending a second request to the second cloud platform or the second cloud site; the first response indicates that the computing task and / or the service is successfully deployed in the second cloud platform or the second cloud site; the second request is used to request the transmission of data of the computing task and / or the service.

2. The method according to claim 1, wherein Before sending the first request to the second cloud platform or the second cloud site, the method further includes: Sending a third request to at least one cloud platform and / or cloud site; the third request is used to request the computing resource situation of the cloud platform and / or cloud site; or, Sending a fourth request to at least one cloud platform and / or cloud site; the fourth request includes the computing requirements of the computing task and / or the service.

3. The method according to claim 2, characterized in that, Further includes: Receiving at least one second response sent by the at least one cloud platform and / or cloud site; the second response indicates the computing resource situation of the cloud platform and / or cloud site; Based on the at least one second response and the computing requirements of the computing task and / or the service, determining the second cloud platform or the second cloud site from the at least one cloud platform and / or cloud site; or, Receiving at least one third response sent by the at least one cloud platform and / or cloud site; the third response indicates whether the cloud platform and / or cloud site supports the computing task and / or the service; based on the at least one third response, determining the second cloud platform or the second cloud site from the at least one cloud platform and / or cloud site.

4. The method according to claim 3, wherein The computing resource situation includes at least one of the following: computing power resource type, total computing power resource, occupied computing power resource, reserved computing power resource, unused computing power resource, available computing power resource and other parameters, CPU frequency, I / O read and write times, and computing task and / or service throughput; The computing requirements include at least one of the following: computing data volume, computing power resource type, number of computing power resources, number of tasks related to the current computing task and / or service, deployment location of related tasks, and bandwidth required for the computing task and / or service.

5. The method according to claim 1, characterized in that, Further includes: If receiving a fourth response sent by the second cloud platform or the second cloud site, re-determining the second cloud platform or the second cloud site; wherein, the fourth response indicates that the computing task and / or the service is deployed unsuccessfully in the second cloud platform or the second cloud site; or, If not receiving the first response or the fourth response within a first preset time; re-sending the first request to the second cloud platform or the second cloud site; if the number of times of sending the first request to the second cloud platform or the second cloud site exceeds a first preset number of times; re-determining the second cloud platform or the second cloud site; wherein, the fourth response indicates that the computing task and / or the service is deployed unsuccessfully in the second cloud platform or the second cloud site.

6. The method according to claim 1, wherein Further includes: Receive a fifth response sent by the second cloud platform or the second cloud site; the fifth response indicates that the data has been successfully received by the second cloud platform or the second cloud site; Delete the data stored locally.

7. The method according to claim 1, wherein It further includes: If a sixth response sent by the second cloud platform or the second cloud site is received; then re-determine the second cloud platform or the second cloud site; wherein, the sixth response indicates that the data has not been successfully received by the second cloud platform or the second cloud site; or, If the fifth response or the sixth response is not received within a second preset time; then re-send the second request to the second cloud platform or the second cloud site; if the number of times of sending the second request to the second cloud platform or the second cloud site exceeds a second preset number of times; then re-determine the second cloud platform or the second cloud site; wherein, the fifth response indicates that the data has been successfully received by the second cloud platform or the second cloud site; the sixth response indicates that the data has not been successfully received by the second cloud platform or the second cloud site.

8. The method according to any one of claims 3 to 4, wherein The types of cloud platforms and / or cloud sites in the at least one cloud platform and / or cloud site include at least one of the following: The first type of cloud platform and / or cloud site, which is the cloud platform and / or cloud site managed by the first cloud platform or the first cloud site; The second type of cloud platform and / or cloud site, which is the cloud platform and / or cloud site that manages the first cloud platform or the first cloud site; The third type of cloud platform and / or cloud site, which is the cloud platform and / or cloud site that belongs to the same O-Cloud as the first cloud platform or the first cloud site; and, The fourth type of cloud platform and / or cloud site, which is the cloud platform and / or cloud site that does not belong to the same O-Cloud as the first cloud platform or the first cloud site.

9. The method according to claim 8, characterized in that Determining the second cloud platform or the second cloud site from the at least one cloud platform and / or cloud site includes: Determining the second cloud platform or the second cloud site from the at least one cloud platform and / or cloud site according to the priority relationship of the cloud platform and / or cloud site; wherein, the priority relationship of the cloud platform includes at least one of the following: The priority of the first type of cloud platform and / or cloud site is higher than the priority of the second type of cloud platform and / or cloud site; The priority of the second type of cloud platform and / or cloud site is higher than the priority of the third type of cloud platform and / or cloud site; and, The priority of the third type of cloud platform and / or cloud site is higher than the priority of the fourth type of cloud platform and / or cloud site.

10. The method according to claim 5 or 7, characterized in that It further includes: If the number of times of re-determining the second cloud platform or the second cloud site exceeds a third preset number of times, then send a fifth request to the first network element; The fifth request is a migration request for the computing task and / or service; Receive a seventh response sent by the first network element; The seventh response indicates that the computing task and / or service has been successfully deployed in the cloud platform or cloud site managed by the first network element; Send a sixth request to the first network element; The sixth request is used to request the transmission of data of the computing task and / or service; Receive the eighth response sent by the first network element; The eighth response indicates that the data has been successfully received by the cloud platform or cloud site managed by the first network element.

11. The method according to claim 10, wherein The first network element includes at least one of the following: Service Management and Orchestration (SMO), Federation O-Cloud Orchestration and Management (FOCOM), Network Function Orchestration (NFO), Non-Real-Time Radio Intelligent Controller (Non-RT RIC), Near-Real-Time Radio Intelligent Controller (Near-RT RIC), Network Function Virtualization Orchestrator (NFVO), Mobile Edge Orchestration (MEO), Virtual Network Function Manager (VNFM), and Container Network Function Manager (CNFM).

12. The method according to any one of claims 1 to 7, 9, and 11, characterized in that The first request carries at least one of the following information: First cloud platform or first cloud site identifier, second cloud platform or second cloud site identifier, computing task and / or service identifier, computing task and / or service type, and parameters required for the deployment of the computing task and / or service.

13. The method according to claim 10, wherein The fifth request carries at least one of the following information: First cloud platform or first cloud site identifier, computing task and / or service identifier, computing task and / or service type, and parameters required for the deployment of the computing task and / or service.

14. A wireless computing power task migration method, characterized in that, Applied to the second cloud platform or second cloud site, including: Receive the first request sent by the first cloud platform or first cloud site or the fifth request sent by the first network element; the first request is a migration request for the computing task and / or service; the fifth request is a migration request for the computing task and / or service; Deploy the computing task and / or service based on the first request or the fifth request; If the computing task and / or service is successfully deployed, send a first response to the first cloud platform or first cloud site; or, send a seventh response to the first network element; wherein, the first response indicates that the computing task and / or service has been successfully deployed in the second cloud platform or second cloud site; the seventh response indicates that the computing task and / or service has been successfully deployed in the second cloud platform or second cloud site; Receive the second request sent by the first cloud platform or first cloud site or the sixth request sent by the first network element; the second request is used to request the transmission of data of the computing task and / or service; the sixth request is used to request the transmission of data of the computing task and / or service.

15. The method according to claim 14, wherein The first network element includes at least one of the following: Service Management and Orchestration (SMO), Federation O-Cloud Orchestration and Management (FOCOM), Network Function Orchestration (NFO), Non-Real-Time Radio Intelligent Controller (Non-RT RIC), Near-Real-Time Radio Intelligent Controller (Near-RT RIC), Network Function Virtualization Orchestrator (NFVO), Mobile Edge Orchestration (MEO), Virtual Network Function Manager (VNFM), and Container Network Function Manager (CNFM).

16. The method according to claim 14, wherein Before receiving the first request sent by the first cloud platform or first cloud site or the fifth request sent by the first network element, further includes: Receive a third request sent by the first cloud platform or the first cloud site or the first network element; the third request is used to request the computing resource status of the second cloud platform or the second cloud site; or, Receive a fourth request sent by the first cloud platform or the first cloud site or the first network element; the fourth request carries the computing requirements of the computing task and / or service.

17. The method according to claim 16, wherein It further includes: Based on the third request, obtain the computing resource status of the second cloud platform or the second cloud site; send a second response to the first cloud platform or the first cloud site or the first network element; the second response characterizes the computing resource status of the second cloud platform or the second cloud site; or, Based on the fourth request and the computing resource status of the second cloud platform or the second cloud site, determine whether to support the computing task and / or service; send a third response to the first cloud platform or the first cloud site or the first network element; the third response characterizes whether the second cloud platform or the second cloud site supports the computing task and / or service.

18. The method according to claim 16, wherein The computing resource status includes at least one of the following: computing power resource type, total computing power resource, occupied computing power resource, reserved computing power resource, unused computing power resource, available computing power resource and other parameters, CPU frequency, I / O read / write times, computing task and / or service throughput; The computing requirements include at least one of the following: computing data volume, computing power resource type, number of computing power resources, number of tasks related to the current computing task and / or service, deployment location of related tasks, and bandwidth required for the computing task and / or service.

19. The method according to claim 14, wherein It further includes: If the computing task and / or service fails to be deployed successfully, send a fourth response to the first cloud platform or the first cloud site or the first network element; The fourth response characterizes that the deployment of the computing task and / or service fails in the second cloud platform or the second cloud site; If the data fails to be received successfully, send a sixth response to the first cloud platform or the first cloud site or the first network element; The sixth response characterizes that the data is not successfully received by the second cloud platform or the second cloud site.

20. The method according to any one of claims 14 to 19, characterized in that The first request carries at least one of the following information: First cloud platform or first cloud site identifier, second cloud platform or second cloud site identifier, computing task and / or service identifier, computing task and / or service type, and parameters required for the deployment of the computing task and / or service; The fifth request carries at least one of the following information: First cloud platform or first cloud site identifier, computing task and / or service identifier, computing task and / or service type, and parameters required for the deployment of the computing task and / or service.

21. A wireless computing power task migration device, characterized in that, Applied to the first cloud platform or the first cloud site, it includes: A first sending unit: used to send a first request to the second cloud platform or the second cloud site; the first request is a migration request for the computing task and / or service. The first receiving unit: configured to receive the first response sent by the second cloud platform or the second cloud site; the first response indicates that the computing task and / or service is successfully deployed in the second cloud platform or the second cloud site; the first sending unit: further configured to send a second request to the second cloud platform or the second cloud site; the second request is used to request the transmission of the data of the computing task and / or service.

22. A wireless computing power task migration device, characterized in that, Applied to the second cloud platform or the second cloud site, including: The second receiving unit: configured to receive the first request sent by the first cloud platform or the first cloud site or the fifth request sent by the first network element; the first request is a migration request for a computing task and / or service; the fifth request is a migration request for a computing task and / or service; The deployment unit: configured to deploy the computing task and / or service based on the first request or the fifth request; The second sending unit: configured to, if the computing task and / or service is successfully deployed, send a first response to the first cloud platform or the first cloud site; or, send a seventh response to the first network element; wherein, the first response indicates that the computing task and / or service is successfully deployed in the second cloud platform or the second cloud site; the seventh response indicates that the computing task and / or service is successfully deployed in the second cloud platform or the second cloud site; the second receiving unit: further configured to receive the second request sent by the first cloud platform or the first cloud site or the sixth request sent by the first network element;; the second request is used to request the transmission of the data of the computing task and / or service; the sixth request is used to request the transmission of the data of the computing task and / or service.

23. A communication device, characterized in that, Including: A processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the wireless computing power task migration method according to any one of claims 1-13, or the wireless computing power task migration method according to any one of claims 14-20.

24. A chip, characterized in that, Including: A processor, configured to call and run a computer program from a memory, so that the device installed with the chip executes the wireless computing power task migration method according to any one of claims 1-13, or the wireless computing power task migration method according to any one of claims 14-20.

25. A computer-readable storage medium, characterized in that, Used to store a computer program, the computer program enables a computer to execute the wireless computing power task migration method according to any one of claims 1-13, or the wireless computing power task migration method according to any one of claims 14-20.

Images