CN114301914A - Cloud edge coordination method and device and storage medium - Google Patents

Abstract

The present application provides a cloud-edge collaboration method, device, and storage medium, and relates to the field of communication technologies. The method can make the MEC system more convenient to connect to multiple public clouds and realize the cloud-edge collaboration function between the MEC system and each public cloud. The method includes: a server of the first public cloud sends a cloud-side collaboration request in a first format to a first cloud connector; wherein, the cloud-side collaboration request is used to request the MEC system to implement the cloud-side collaboration configuration with the first public cloud; A cloud connector converts the cloud-side collaboration request from the first format to the second format; the first cloud connector sends the cloud-side collaboration request in the second format to MEPM, so that the MEC system responds to the cloud-side collaboration request in the second format to realize the first A public cloud and the cloud-side collaborative configuration of the MEC system. The present application is used to solve the problem that the MEC system is difficult to connect to multiple public clouds in the process of realizing the cloud-side collaboration between the public cloud and the MEC system.

Description

A cloud-edge collaboration method, device and storage medium

technical field

The present application relates to the field of communication technologies, and in particular, to a cloud-edge collaboration method, device, and storage medium.

Background technique

With the commercial use of 5th Generation Mobile Communication Technology (5G) wireless networks and the in-depth development of the digital transformation of vertical industries, people have higher requirements for the low latency of network computing capabilities. Therefore, edge computing technology Start to shine. Edge computing technology refers to an open platform that integrates network, computing, storage and application core capabilities on the side close to the object or data source, which can provide users with nearby services and meet people's low-latency requirements. As a concrete realization of edge computing technology, Multi-access Edge Computing (MEC) system has gradually become the key infrastructure for carrying various innovative applications. Among them, cloud-edge collaboration, as the core of edge computing technology, refers to the collaboration of public cloud and MEC systems in computing resources, security policies, application management, and business management to provide users with various network computing services.

As multi-cloud becomes the trend of cloud computing, the MEC system should not restrict which public cloud users use to provide network computing services, and should support multiple public clouds to access the MEC system for users to choose and use. In the prior art, different public clouds are provided by different manufacturers, but because the interface standards of different manufacturers' public clouds are inconsistent, when the MEC system accesses multiple public clouds, it is necessary to configure each interface standard for different public clouds separately. Public cloud to realize the cloud-edge collaboration function between each public cloud and the MEC system. For operators, when they need to connect to multiple public clouds, this separate deployment solution greatly increases the difficulty of operator deployment, making it difficult for existing MEC systems to connect to multiple public clouds.

SUMMARY OF THE INVENTION

The present application provides a cloud-edge coordination method, device, and storage medium, which can make the MEC system more convenient to connect to multiple public clouds and realize the cloud-edge coordination function between the MEC system and each public cloud.

In a first aspect, the present application provides a cloud-edge collaboration method, which is applied to a multi-access edge computing MEC system. The MEC system includes: a multi-access edge computing platform management unit MEPM, and the MEPM is connected with a plurality of cloud connectors, a plurality of The cloud connectors are in one-to-one correspondence with multiple public clouds, the multiple cloud connectors include a first cloud connector, and the method includes: the first cloud connector receives a cloud-side collaboration request in a first format from a server of the first public cloud ; Wherein, the first public cloud is the public cloud corresponding to the first cloud connector, the cloud-side collaboration request is used to request the MEC system to implement the cloud-side collaborative configuration with the first public cloud, and the first format satisfies the server of the first public cloud The first cloud connector converts the cloud-side collaboration request from the first format to the second format; the second format satisfies the interface standard of the MEC system; the first cloud connector sends the second-format cloud-side collaboration request to MEPM , so that the MEC system responds to the cloud-side collaboration request in the second format to implement the cloud-side collaboration configuration of the first public cloud and the MEC system.

In a possible implementation manner, the MEPM is connected to multiple cloud connectors through a standard interface of the MEC system; the standard interfaces of the MEC system include: a multi-access edge management Mm2 interface and an Mm3 interface.

In another possible implementation manner, the above-mentioned MEC system further includes: a multi-access edge orchestrator MEO; before the first cloud connector receives the cloud-edge collaboration request in the first format from the server of the first public cloud, the method further includes: The steps include: the MEO receives a resource query request sent from the server of the first public cloud; the MEO sends a resource query response to the server of the first public cloud; wherein the resource query response includes information of the MEPM and information of the first cloud connector.

In a second aspect, the present application provides a cloud-edge collaboration method, which is applied to a server of a first public cloud. The first public cloud accesses a multi-access edge computing MEC system through a first cloud connector, and the MEC system includes: a multi-access edge computing MEC system. Into the edge computing platform management unit MEPM, the MEPM is connected to multiple cloud connectors, and the multiple cloud connectors correspond to multiple public clouds one-to-one. The multiple public clouds include the first public cloud, and the first cloud connector is multiple clouds. The connector includes a cloud connector corresponding to the first public cloud, and the method includes: a server of the first public cloud sends a cloud-side collaboration request in a first format to the first cloud connector; wherein the cloud-side collaboration request is used for requesting The MEC system implements the cloud-edge collaborative configuration with the first public cloud, so that the first cloud connector converts the cloud-edge collaborative request from the first format to the second format, so that the MEC system responds to the cloud-edge collaborative request in the second format to realize the first A public cloud and the cloud-side collaborative configuration of the MEC system; the first format meets the interface standard of the server of the first public cloud, and the second format meets the interface standard of the MEC system.

In a possible implementation manner, the above-mentioned MEC system further includes: a multi-access edge orchestrator MEO; before the server of the first public cloud sends a cloud-edge collaboration request in the first format to the first cloud connector, the above-mentioned method further includes: : the server of the first public cloud sends a resource query request to the MEO; the server of the first public cloud receives a resource query response from the MEO; wherein the resource query response includes the information of the MEPM and the information of the first cloud connector; the first public cloud The server sending the cloud-side collaboration request in the first format to the first cloud connector includes: the first public cloud sends the cloud-side collaboration request in the first format to the first cloud connector according to the resource query response.

The cloud-edge collaboration method provided in this application extends the MEPM in the standard MEC system, and connects multiple cloud connectors to the MEPM. The multiple cloud connectors are respectively used to connect to multiple public clouds. Specifically, the cloud The connector can receive the cloud-side collaboration request from the server corresponding to the public cloud, and convert the cloud-side collaboration request into a request that conforms to the standard format of the MEC system, so that the MEC system can respond to the cloud-side collaboration request to realize the cloud of the public cloud and the MEC system. Edge collaborative configuration. In this way, for different public clouds, a unified process can be used to realize the cloud-side collaborative configuration of the public cloud and the MEC system, which reduces the difficulty of connecting the MEC system to multiple public clouds.

Further, the embodiments of the present application are based on the existing standards and processes of the MEC system, and the provided public cloud access function can make full use of the functional components and processes of the MEC system, which further facilitates operators to realize that the MEC system is connected to multiple public clouds, and provides Give users more space to choose public cloud, in line with the multi-cloud scenario under the future trend.

In addition, the embodiments of the present application are extended on the standard MEC system, which conforms to the multi-level architecture of the existing MEC system. When the public cloud is connected to the MEC system, the MEC system can deploy the public cloud in stages according to the requirements of different manufacturers, such as the delay, etc., to give full play to the resource scheduling advantages of the MEC system, and bring better services and experience to users and public cloud manufacturers. . The multi-level architecture of the MEC system can also be integrated with wireless networks such as Open-Radio Access Network (O-RAN). It can be deployed on private networks in vertical industries to meet the diverse needs of vertical industries.

In a third aspect, the present application provides a cloud-edge coordination device, which is applied to a multi-access edge computing MEC system. The MEC system includes: a multi-access edge computing platform management unit MEPM, and the MEPM is connected with a plurality of cloud connectors, a plurality of The cloud connectors correspond to multiple public clouds one-to-one, and the multiple cloud connectors include a first cloud connector, and the first cloud connector includes a cloud-edge coordination device; the cloud-edge coordination device includes: a receiving module, a conversion module, and a sending module the receiving module, the conversion module is connected with the sending module; the receiving module is used to receive the cloud-side collaboration request in the first format from the server of the first public cloud; wherein, the first public cloud is a public cloud corresponding to the first cloud connector Cloud, the cloud-side collaboration request is used to request the MEC system to implement the cloud-side collaborative configuration with the first public cloud, and the first format satisfies the interface standard of the server of the first public cloud; the conversion module is used to convert the cloud-side collaboration request from the first public cloud. The format is converted into the second format; the second format meets the interface standard of the MEC system; the sending module is used to send the cloud-side collaboration request in the second format to the MEPM, so that the MEC system responds to the cloud-side collaboration request in the second format and realizes the first public Cloud and MEC system cloud-side collaborative configuration.

In a possible implementation manner, the MEPM is connected to multiple cloud connectors through a standard interface of the MEC system; the standard interfaces of the MEC system include: a multi-access edge management Mm2 interface and an Mm3 interface.

In a fourth aspect, the present application provides a cloud-edge coordination device, which is applied to a server of a first public cloud. The first public cloud is connected to a multi-access edge computing MEC system through a first cloud connector, and the MEC system includes: a multi-access edge computing MEC system. Access the edge computing platform management unit MEPM. The MEPM is connected to multiple cloud connectors, and the multiple cloud connectors correspond to multiple public clouds one-to-one. The multiple public clouds include the first public cloud, and the first cloud connectors are multiple The cloud connector includes a cloud connector corresponding to the first public cloud, and the cloud-edge coordination device includes: a sending module; a sending module is configured to send a cloud-edge coordination request in the first format to the first cloud connector; The side collaboration request is used to request the MEC system to implement the cloud-side collaboration configuration with the first public cloud, so that the first cloud connector converts the cloud-side collaboration request from the first format to the second format, so that the MEC system responds to the second format. The cloud-side collaboration request implements the cloud-side collaborative configuration of the first public cloud and the MEC system; the first format meets the interface standard of the server of the first public cloud, and the second format meets the interface standard of the MEC system.

In a possible implementation manner, the above-mentioned MEC system further includes: a multi-access edge orchestrator MEO; a sending module, which is further configured to send a resource query request to the MEO; the above-mentioned cloud-edge coordination device further includes a receiving module; the receiving module is used for Receive a resource query response from the MEO; wherein, the resource query response includes the information of the MEPM and the information of the first cloud connector; the sending module is specifically configured to send the cloud edge in the first format to the first cloud connector according to the resource query response Collaborative request.

In a fifth aspect, the present application provides a cloud-edge collaboration device, which is applied to a multi-access edge computing MEC system. The cloud-edge collaboration device includes: a processor and a memory; the memory stores instructions executable by the processor; the processor is configured with When executing the instruction, the MEC system is made to implement the method of any one of the first aspect or the second aspect.

In a sixth aspect, the present application provides a computer-readable storage medium, the computer-readable storage medium comprising: computer software instructions; when the computer software instructions are run in the multi-access edge computing MEC system, the MEC system is made to realize the above-mentioned first The method of any of the aspects or the second aspect.

For the beneficial effects of the third aspect to the sixth aspect, reference may be made to the corresponding description of the first aspect or the second aspect, and details are not repeated here.

Description of drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the accompanying drawings required for the description of the embodiments or the prior art. Obviously, the drawings in the following description are only These are some embodiments of the present application. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings without any creative effort.

Fig. 1 is a kind of system composition schematic diagram of cloud-edge collaboration provided by this application;

Fig. 2 is the composition schematic diagram of a kind of MEC system that this application provides;

3 is a schematic diagram of the composition of another MEC system provided by the application;

4 is a schematic flowchart of a cloud-edge collaboration method provided by the present application;

5 is a schematic flowchart of another cloud-edge collaboration method provided by the present application;

6 is a schematic flowchart of an application instantiation method provided by the present application;

7 is a schematic flowchart of an application termination method provided by the present application;

8 is a schematic diagram of the composition of a cloud-edge collaboration device provided by the present application;

FIG. 9 is a schematic diagram of the composition of another cloud-edge collaboration device provided by the present application;

FIG. 10 is a schematic structural diagram of a cloud-edge collaboration device provided by the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

It should be noted that, in the embodiments of the present application, words such as "exemplarily" or "for example" are used to represent examples, illustrations or descriptions. Any embodiment or design described in the embodiments of the present application as "exemplarily" or "such as" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplarily" or "such as" is intended to present the related concepts in a specific manner.

In order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish the same items or similar items with basically the same functions and functions. Those skilled in the art can understand that words such as "first" and "second" are not intended to limit the quantity and execution order.

At present, the MEC system has become a key infrastructure for carrying various innovative applications. The MEC system not only needs to utilize the large bandwidth, low latency, high reliability and multi-connection network capabilities of 5G, but also requires integration with cloud computing, big data and artificial intelligence technologies to empower all walks of life in society (including manufacturing, smart cities, Retail industry, medical industry, education industry, transportation industry and digital government, etc.) to carry out industrial upgrading and digital transformation of enterprises. In addition, with the development of cloud computing technology, the distributed cloud architecture of "central cloud + MEC system" has begun to emerge. The cloud architecture extends from the center to the edge, and the distributed deployment of cloud computing services on the edge side of the network is the development of future computing forms. Trend, that is, edge computing technology is the development trend of future computing forms. Among them, cloud-edge collaboration is the core of the distributed cloud architecture. Therefore, enhancing the cloud-edge collaboration capability is the core of the development of edge computing technology. The above-mentioned central cloud is a centralized public cloud.

As shown in Figure 1, from the perspective of system composition, cloud-side collaboration mainly includes three levels, namely the public cloud and MEC system in Infrastructure as a Service (IaaS), Platform as a Service (Platform as a Service) , PaaS) and application as a service (Software as a Service, SaaS) level coordination, but also need to consider the coordination of billing, operation and maintenance monitoring, security and other aspects.

Among them, the collaboration at the IaaS level refers to the resource collaboration between the public cloud IaaS and edge (Edge) IaaS, the collaboration at the SaaS level refers to the application service collaboration between the public cloud SaaS and Edge SaaS, and the collaboration at the PaaS level refers to It is the deployment collaboration, intelligent collaboration, service orchestration collaboration and data collaboration between public cloud PaaS and Edge PaaS. Cloud-side collaboration can be embodied in the online, deployment (instantiation), monitoring, change, and termination of cloud applications in the MEC system to provide users with various network computing services.

As multi-cloud becomes the trend of cloud computing, the MEC system should not restrict which public cloud users use to provide network computing services, and should support multiple public clouds to access the MEC system for users to choose and use. In addition, since the MEC system needs to be deployed in stages according to the different manufacturers of the public cloud and different latency requirements during the actual deployment process, the public cloud needs to conform to the multi-level architecture of the MEC system when accessing the MEC system. Since each public cloud is provided by each manufacturer, and the interface standards of the public clouds of different manufacturers are inconsistent, the MEC system needs to be configured according to the interface standards of each public cloud when connecting to multiple public clouds to realize the cloud-side collaboration function. The coupling of this solution is too high, and it is too difficult for operators to connect to multiple public clouds. If the MEC system cannot support multiple public clouds, it will limit the space for users to choose from public clouds, resulting in a decrease in user experience.

Under this background technology, the embodiments of the present application provide a cloud-edge collaboration method. Using this method, the MEC system can be easily connected to multiple public clouds and realize the cloud-edge collaboration function between the MEC system and each public cloud. The deployment difficulty of operators is reduced.

The cloud-edge collaboration method provided in this application can be applied to the MEC system as shown in FIG. 2 . As shown in FIG. 2 , the MEC system includes two levels: a MEC system level (MEC System Level) and a MEC host level (MEC Host Level). The MEC system level includes an operations support system (Operations Support System, OSS) and a multi-access edge orchestrator (Multi-access Edge Orchestrator, MEO). The MEC host level includes: a MEC platform management unit (Multi-access Edge Computing Platform Manager, MEPM), a virtualization infrastructure management unit (Virtualization Infrastructure Manager, VIM) and an MEC host.

OSS is used to receive external requests and authorize these requests. Authorized requests are forwarded to the MEO for further processing.

MEO is the core functional component at the MEC system level. It mainly has the following functions: maintain the overall resource view, available mobile edge services and topology of the MEC system according to the MEC host deployment; The MEC host provides available resources and available services for MEC application instantiation; triggers MEC application instantiation or termination; triggers MEC application relocation, etc.

MEPM is the core of the MEC host level and is mainly responsible for the following functions: Manage application life cycle, including informing MEO of relevant information; provide element management functions for MEP; manage application rules and requirements, including service authorization, traffic rules, local domain name System (Domain Name System, DNS) configuration and conflict resolution; receive fault reports and performance speed measurement data from VIM for further optimization of VIM, etc.

VIM is mainly responsible for the following functions: allocate, manage, and release virtualized resources (such as computing resources, storage resources, and network resources); prepare virtualized infrastructure to run software images; collect and report performance and failure information about virtualized resources.

The MEC host, which can be a physical host, is mainly used to provide computing, storage, and network resources for MEC applications. MEC hosts are generally deployed in different scenarios according to different latency requirements. For example, for services that do not require high network latency, MEC hosts can be deployed in core computer rooms in prefectures and cities. For services with high network latency requirements, the MEC host needs to be further moved to the aggregation or access room. If the service not only has high requirements on network delay, but also has strict requirements on data security and privacy, the MEC host can be deployed in the computer room on the client side.

The MEC host includes a multi-access edge computing platform (Multi-access Edge Computing Platform, MEP), a virtualization infrastructure (Virtualization Infrastructure, VI) and an MEC application.

The MEP is responsible for the following functions: Provide an environment in which MEC applications can deploy, go live, run, and provide MEC services; Receive DNS records from MEPM and configure DNS proxies/servers responsively; Receive traffic rules from MEPM, applications, or services and configure the data plane.

VI mainly provides computing, storage and network resources for MEC applications, and can provide continuous storage and time-related information for MEC applications.

MEC applications can include applications running on virtual machines on the virtualization infrastructure, or applications running on containers. MEC applications can interact with mobile edge platforms to provide MEC services, and can also interact with MEPs to perform processes related to the MEC application lifecycle, such as: indicating MEC application availability, relocating user status, etc. Besides, the MEC application also has some rules and requirements, such as: there are also rules and requirements such as required resources, maximum delay, required services or useful services.

In the MEC system shown in FIG. 2 , the MEC hosts and components in the MEC hosts can communicate with each other through an interface (Multi-access Edge point, Mp) of the multi-access edge platform. The MEC host and other devices in the MEC system can communicate with each other through the Multi-access Edge management (Mm) interface, and other devices in the MEC system except the MEC host can also communicate with each other through the Mm interface.

For example, as shown in Figure 2: Mm1 is used for the interaction between MEO and OSS, Mm2 is used for the interaction between OSS and MEPM, Mm3 is used for the interaction between MEO and MEPM, and Mm4 is used for the interaction between MEO and VIM. Interaction, Mm5 is used for the interaction between MEPM and MEP, Mm6 is used for the interaction between MEPM and VIM, and Mm5 is used for the interaction between VIM and VI. Mp1 is used for interaction between MEP and MEC applications, Mp2 is used for interaction between MEP and VI, and Mp3 is used for interaction between MEP and MEPs in other MEC hosts.

It should be pointed out that the composition illustrated in this embodiment does not constitute a specific limitation on the MEC system. That is, FIG. 2 is only an exemplary drawing, and the present embodiment does not limit the number and types of devices included in the MEC system. In other embodiments, the MEC system may include more or fewer devices than shown, or combine some devices, or split some devices, or different device arrangements. For example, in addition to the devices shown in FIG. 2 , the MEC system may also include other devices and the like. In addition, the name of each device and the name of the interface between the devices in FIG. 2 are not limited in this embodiment. For example, in addition to the names shown in FIG. 2 , various devices and interfaces between devices can also be named with other names, which are not limited.

The cloud-edge collaboration method provided by the embodiments of the present application completes the connection with multiple public clouds by expanding the functions of MEPM in the above-mentioned MEC system and adding multiple cloud connectors. As shown in FIG. 3 , in the above MEC system, MEPM is connected with cloud connector 1 - cloud connector n, and cloud connector 1 - cloud connector n are used to complete the connection between the MEC system and public cloud 1 - public cloud n respectively. Among them, each cloud connector is an exclusive device of each public cloud manufacturer, therefore, public cloud 1 - public cloud n and cloud connector 1 - cloud connector n correspond one-to-one. The public cloud interacts with MEPM through the corresponding cloud connector, and realizes the configuration management of MEC host resources, MEP and MEC applications through the functions of MEPM itself, so as to realize the cloud-side collaborative configuration of the public cloud and the MEC system. The cloud connector connects with the MEPM through the standard interface of the MEC system. Exemplarily, the standard interface in the MEC system can be the Mm2 interface or the Mm3 interface, that is, the cloud connector can use the Mm2 interface between the OSS and the MEPM to connect with the MEPM, or use the Mm3 interface between the MEO and the MEPM. connect.

It should be noted that the implementation of the cloud-edge collaboration method provided by the embodiment of the present application does not directly involve the OSS and VI and other modules in the MEC system shown in FIG. 2. Therefore, the MEC system shown in FIG. 3 does not show these modules. module.

In addition, as shown in FIG. 3 , the embodiment of the present application conforms to the multi-level deployment method adopted by the MEC system, can provide standardized cloud services and cloud resource access requirements, and support the unified deployment of cloud applications on the MEC system (cloud-side collaboration implementation). This solution expands the original functions of the existing MEC system. The expanded MEPM, MEP and wireless network PaaS form a multi-level PaaS architecture, which gradually opens up network capabilities. For example, the wireless network combines wireless network information, including traditional base station information (such as user-related context information, used for monitoring and real-time analysis of user control process, service flow, and obtaining user-related wireless network status or features, etc.) and open Information specific to a radio access network (Open-Radio Access Network, O-RAN) base station is opened to the MEP. The MEP opens network capabilities such as Radio Network Information Service (RNIS), Location Service (LS) and Bandwidth Management Service (BMS) to MEC applications upward through the MP1 interface.

The cloud-edge collaboration method provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings. The cloud-edge collaboration method provided by the present application may be implemented by the MEC system shown in FIG. 3 above. In addition, as described in the foregoing embodiments, the MEPM of the MEC system is connected with a plurality of cloud connectors, and the plurality of cloud connectors correspond to a plurality of public clouds one-to-one, and these public clouds can communicate with each other through their corresponding cloud connectors. MEPM interacts, and finally realizes the cloud-side collaborative configuration with the MEC system. Different public clouds interact with MEPM through corresponding cloud connectors, and the implementation process of cloud-edge collaborative configuration with the MEC system is similar. Any one of the clouds, for example, any one of the public cloud 1-public cloud n shown in FIG. 3 ) and the MEC system realize the cloud-edge collaboration configuration as an example, and the cloud-side collaboration method in the embodiment of the present application is introduced. The cloud connector corresponding to the first public cloud is hereinafter referred to as the first cloud connector.

FIG. 4 is a schematic flowchart of a cloud-edge collaboration method provided by an embodiment of the present application. As shown in Figure 4, the method may include the following steps:

S401. The server of the first public cloud sends a cloud-side collaboration request in a first format to the first cloud connector.

The cloud-side collaboration request is used to request the MEC system to implement the cloud-side collaborative configuration with the first public cloud, and the first format satisfies the interface standard of the server of the first public cloud.

The cloud connector is an exclusive device of each public cloud manufacturer. Therefore, the public cloud server and the cloud connector communicate with each other through the interface standards specified by each public cloud manufacturer. The server of the first public cloud can send a cloud-side collaboration request in the first format to the corresponding first cloud connector through its own standard interface, so as to request the MEC system to implement the cloud-side collaboration configuration with the first public cloud.

S402. The first cloud connector converts the cloud-side collaboration request from the first format to the second format.

Wherein, the second format satisfies the interface standard of the MEC system.

The first cloud connector can receive the cloud-side collaboration request from the server of the first public cloud through its own standard interface, and convert the cloud-side collaboration request from the first format to the second format that satisfies the interface standard of the MEC system.

S403. The first cloud connector sends a cloud-side collaboration request in the second format to the MEPM.

The second format is a format that satisfies the interface standard of the MEC system. Therefore, the first cloud connector can send a cloud-side collaboration request in the second format to the MEPM through the standard interface of the MEC system, so that the MEC system can respond to the cloud-side collaboration in the second format. Request to realize the cloud-side collaborative configuration of the first public cloud and the MEC system.

The technical solutions provided by the above embodiments bring at least the following beneficial effects: in the embodiments of the present application, the MEPM in the standard MEC system is extended, and multiple cloud connectors are connected to the MEPM, and the multiple cloud connectors are respectively used for Connecting to multiple public clouds, specifically, the cloud connector can receive cloud-side collaboration requests from servers corresponding to the public cloud, and convert the cloud-side collaboration request into a request that conforms to the standard format of the MEC system, so that the MEC system can respond to the cloud-side collaboration request The collaborative request realizes the cloud-side collaborative configuration of the public cloud and the MEC system. In this way, for different public clouds, a unified process can be used to realize the cloud-side collaborative configuration of the public cloud and the MEC system, which reduces the difficulty of connecting the MEC system to multiple public clouds.

FIG. 5 is a schematic flowchart of another cloud-edge collaboration method provided by an embodiment of the present application. As shown in Figure 5, the method may include:

S501. The server of the first public cloud sends a resource query request to the MEO.

Before the public cloud, such as the first public cloud and the cloud-side collaboration of the MEC system, the server of the first public cloud can first obtain the resource information of the MEC system, such as computing resources, network resources and storage resources, etc. Select resources suitable for cloud-side collaborative deployment. MEO is the core unit of the management capability of the MEC system. It has the function of deploying and maintaining the overall resource view of the MEC system, and can select appropriate resources for other devices to use according to constraints (such as network delay, etc.). Therefore, in some embodiments, in the public cloud, if the cloud-side collaborative configuration of the first public cloud and the MEC system needs to be performed, the server of the first public cloud may send a resource query request to the MEO to request to query the available resources of the MEC system resource information.

S502. The MEO sends a resource query response to the server of the first public cloud.

The resource query response is used to indicate resource information of resources in the MEC system that are suitable for collaborative deployment of the first public cloud and cloud-edge. It may include information on computing resources and network resources suitable for the first public cloud and cloud-side collaborative deployment.

In some embodiments, after receiving the resource query request sent by the server of the first public cloud, the MEO determines the most suitable resources of the MEC system according to the resource query request, available resources in the MEC system and wireless network conditions, such as It includes resources such as MEPM and the first cloud connector, and then carries the information of these resources, such as the information of MEPM and the information of the first cloud connector, in the resource query response and sends it to the server of the first public cloud.

S503. The server of the first public cloud sends the cloud-side collaboration request in the first format to the first cloud connector.

The cloud-side collaboration request is used for the MEC system to implement the cloud-side collaborative configuration of the first public cloud and the MEC system, and the first format satisfies the interface standard of the server of the first public cloud.

In the embodiment of the present application, the MEC system is connected to multiple cloud connectors, and the multiple cloud connectors correspond to multiple public clouds one-to-one. Since the cloud connector is the exclusive device of each public cloud manufacturer, the cloud connector interacts with the public cloud server through the interface standard customized by each public cloud manufacturer, so each public cloud can directly send cloud edge to its own exclusive cloud connector Collaborative request.

In some embodiments, after receiving the resource query response, the server of the first public cloud may, according to the information of the MEPM and the information of the first cloud connector in the resource query response, send a request to the first public cloud server through a standard interface of the public cloud server. The cloud connector sends the cloud-side collaboration request in the first format for the MEC system to realize the cloud-side collaborative configuration of the public cloud and the MEC system.

S504. The first cloud connector converts the cloud-side collaboration request from the first format to the second format.

Wherein, the second format satisfies the interface standard of the MEC system.

The multiple public clouds connected to the MEC system are usually provided by different manufacturers, and the interface standards of the public clouds of different manufacturers are often inconsistent. The request formats are often inconsistent, and cloud-side collaboration requests in these formats usually do not meet the interface standards of the MEC system. In the embodiment of the present application, after the server of the public cloud sends a cloud-side collaboration request in the first format to the corresponding cloud connector, the cloud connector can convert the request sent by the server of the public cloud into a request that conforms to the The format of the MEC system interface standard so that the request can be recognized by the MEC system.

In some embodiments, after receiving the cloud-side collaboration request, the first cloud connector checks and adapts the cloud-side collaboration request, and can send the cloud-side collaboration request to the first public cloud server that meets the interface standard of the first public cloud. The first format is converted into a second format that satisfies the interface standard of the MEC system. The interface standard of the public cloud server is independently defined by each public cloud manufacturer, which is not limited in this embodiment of the present application. The second format satisfies the interface standard of the MEC system.

S505. The first cloud connector sends a cloud-side collaboration request in the second format to the MEPM.

Among them, the request converted by the cloud connector conforms to the interface standard of the MEC system and is a format compatible with MEPM. So MEPM can receive and recognize the request sent by the cloud connector and perform corresponding actions.

In some embodiments, after converting the cloud-side collaboration request from the first format to the second format, the first cloud connector may send an identifiable cloud-side collaboration request to the MEPM through a standard interface in the MEC system for use in The MEC system realizes the cloud-side collaborative configuration of the first public cloud and the MEC system.

It is understandable that although the interface standards of the public clouds of different manufacturers are inconsistent, through the corresponding cloud connectors, the requests sent by the servers corresponding to the public clouds can be uniformly converted into a format compatible and recognized by the MEC system, which conforms to the current standards of the MEC system. process, the MEC system can be connected to multiple public clouds without large-scale transformation of the MEC system.

The MEC system implementing the cloud-edge collaborative configuration of the first public cloud and the MEC system may include the following S506-S507.

S506, the MEPM interacts with the VIM, so that the VIM completes the virtualized resource configuration of cloud-side collaboration.

The main function of VIM is to allocate, manage and release virtualized resources (such as computing resources, storage resources and network resources). Therefore, in some embodiments, after receiving the cloud-side collaboration request in the second format, the MEPM may respond to the cloud-side collaboration request and interact with the VIM to complete the computing resources, storage resources and network required for cloud-side collaboration Relevant configuration of virtualized resources such as resources.

S507, the MEPM interacts with the MEP, so that the MEP completes the configuration of cloud-edge collaboration.

MEPM is mainly used to provide element management functions for MEP and to manage the rules and requirements of the application. The MEP is mainly used to provide mobile edge services for MEC applications, for example, it can provide services for the discovery and use of MEC applications. MEC applications can be deployed, launched, run or terminated on the MEP (cloud-side collaboration). Therefore, the MEP needs to obtain the cloud-edge collaboration configuration from the MEPM to complete the actual configuration of the MEC application. In some embodiments, after the VIM completes the virtualized resource configuration for cloud-edge collaboration, the MEPM may interact with the MEP, and transmit the cloud-side collaboration configuration information to the MEP, so that the MEP completes the deployment, online, operation or deployment of the MEC application according to the configuration information. The cloud-side collaborative configuration is terminated, and the cloud-side collaborative configuration of the first public cloud and the MEC system is finally realized.

It should be noted that, according to different scenarios of cloud-edge collaboration, the execution order of the above S506 and S507 may also be different. Similarly, in different scenarios, the configuration information of cloud-edge collaboration transmitted by MEPM and MEP may also be different. For example, application instantiation and application termination in cloud-edge collaboration differ in the steps described above.

The following takes application instantiation (application deployment) in cloud-side collaboration as an example to describe the process of cloud-side collaboration in this embodiment of the present application, as shown in FIG. 6 .

S601. The server of the first public cloud sends a resource query request to the MEO.

As described in S501, a public cloud, such as the first public cloud, needs to obtain information such as computing resources, network resources, and storage resources of the MEC system before instantiating the application.

In some embodiments, the server of the first public cloud may send a resource query request to the MEO, for querying information about the MEPM and the first cloud connector corresponding to the MEC host suitable for deploying the MEC application.

S602. The MEO sends a resource query response to the server of the first public cloud.

In some embodiments, after receiving the resource query request sent by the server of the first public cloud, the MEO determines the MEC host that is most suitable for deploying the MEC application according to the resource query request, available resources of the MEC host and wireless network conditions, and The MEPM and the cloud connector corresponding to the MEC host send a resource query response containing relevant information of the MEC host, the MEPM and the first cloud connector to the server of the first public cloud.

S603. The server of the first public cloud sends an application instantiation request in the first format to the first cloud connector.

The application instantiation request may be one of the above cloud-side collaboration requests. The application instantiation request can be used to request the application instantiation of the cloud application of the public cloud in the MEC system.

In some embodiments, after receiving the resource query response, the server of the first public cloud may send the cloud server to the first cloud connector according to the MEC host in the resource query response, as well as the corresponding information of MEPM and the first cloud connector. The application instantiation request of the application in the MEC system.

S604. The first cloud connector converts the application instantiation request from the first format to the second format.

As described in S503 and S504, the first format satisfies the interface standard of the server of the public cloud, and the second format satisfies the interface standard of the MEC system.

In some embodiments, after receiving the application instantiation request, the first cloud connector checks and adapts the application instantiation request. The first format is converted into a second format that satisfies the interface standard of the MEC system.

S605. The first cloud connector sends an application instantiation request in the second format to the MEPM.

The application instantiation request in the second format may be received and recognized by the MEPM. Therefore, in some embodiments, after converting the application instantiation request from the first format to the second format, the first cloud connector can send the MEPM-identifiable application instantiation request to the MEPM through a standard interface in the MEC system , which is used to request the application instantiation of the cloud application on the MEC system.

S606. The MEPM sends a resource allocation request to the VIM.

The resource allocation request carries demand information of resources such as computing, storage, and network required for application instantiation.

In some embodiments, after receiving the application instantiation request in the second format, the MEPM may, in response to the request, send a resource allocation request to the VIM to request the VIM to allocate computing resources, storage resources, and network resources required for the instantiation of the application. virtual resource.

S607. The VIM sends a resource allocation response to the MEPM.

In some embodiments, after receiving the resource allocation request, the VIM sends a resource allocation response to the MEPM according to the resource allocation request. The resource allocation response is used to indicate that the MEPM requests resources successfully, and is also used to indicate information of resources allocated for application instantiation.

S608. The MEPM sends a configuration request message to the MEP.

The configuration request information is used for the MEP to complete the configuration of application instantiation.

In some embodiments, after receiving the resource allocation response, the MEPM may send configuration request information to the MEP, where the configuration request information is used to transmit application instantiation configuration information and information about resources allocated for application instantiation. For example, the configuration information may be Including business rules and DNS rules, etc., so that the MEP completes the configuration of application instantiation.

S609, the MEP completes the configuration of the application instantiation.

In some embodiments, after receiving the configuration request message, the MEP may complete the configuration of the application instantiation according to the configuration request message. Afterwards, the MEP can launch the MEC application.

S610. The MEP sends a configuration response message to the MEPM,

In some embodiments, after completing the application instantiation of the MEC application, the MEP may send a configuration response message to the corresponding MEPM, where the configuration response message may carry the application instance identifier of the MEC application.

S611. The MEPM sends an application instantiation response to the first cloud connector.

In some embodiments, after receiving the configuration response message from the MEP, the MEPM may send an application instantiation response carrying the application instance identifier of the MEC application to the corresponding first cloud connector.

S612. The first cloud connector sends an application instantiation response to the server of the first public cloud.

In some embodiments, after receiving the application instantiation response, the first cloud connector may send the application instantiation response to the corresponding server of the first public cloud, where the application instantiation response carries the application instance identifier.

S613. The server of the first public cloud sends an application instantiation response to the MEO.

In some embodiments, after receiving the application instantiation response, the server of the first public cloud may send the application instantiation response carrying the application instance identifier to the MEO, thereby completing the entire application instantiation process.

It should be noted that the related technologies for the implementation of application instantiation have been formulated to support virtual machine-based application descriptors (TOSCA) and container-based cloud native application descriptors (YAML), and the industry has formulated how to implement application instantiation. Therefore, the specific process of application instantiation will not be described in detail here in this embodiment of the present application.

When the deployed (instantiated) application instance is no longer needed, in order to save resources, the application instance can also be terminated, and the resources occupied by the application instance can be released. The following describes the process of application termination with reference to the process shown in FIG. 7 .

S701. The server of the first public cloud sends a resource query request to the MEO.

S702. The MEO sends a resource query response to the server of the first public cloud.

The specific description of S701 and S702 may refer to the description of the corresponding content in S501 and S502, which will not be repeated here.

S703. The server of the first public cloud sends an application termination request in the first format to the first cloud connector.

In some embodiments, the application termination request may be one of the above cloud-side collaboration requests. After receiving the resource query response, the server of the first public cloud may send an application termination request to the first cloud connector according to the resource query response. The application termination request may be used to request the MEC system to terminate an instance of the MEC application, and the application termination request may include an application instance identifier of the MEC application.

S704. The first cloud connector converts the application termination request from the first format to the second format.

For the description of the first format and the second format, reference may be made to the corresponding descriptions of S503 and S504, and details are not repeated here.

In some embodiments, after receiving the application termination request, the first cloud connector checks and adapts the application termination request, and can convert the cloud-side collaboration request into a first format that satisfies the interface standard of the server of the first public cloud , converted into a second format that satisfies the interface standard of the MEC system.

S705. The first cloud connector sends an application termination request in the second format to the MEPM.

The application termination request in the second format may be received and recognized by the MEPM. Therefore, in some embodiments, after converting the application termination request from the first format to the second format, the first cloud connector may send an identifiable application termination request to the MEPM through a standard interface in the MEC system for the purpose of Requests the MEC system to terminate the instance of the MEC application.

S706. The MEPM sends a termination request message to the MEP.

Different from the process of application instantiation, in the process of application termination, MEPM needs to first notify MEP to terminate the MEC application, and then notify VIM to release the virtualized resources allocated by VIM for the MEC application when the application is instantiated.

Therefore, in some embodiments, after receiving the application termination request sent by the first cloud connector, the MEPM may, in response, send a termination request message to the MEP, where the termination request message is used to request the MEP to terminate the instance of the MEC application, or Say is used to request the MEP to destroy the instance of the MEC application. The termination request message carries the application instance identifier of the MEC application.

S707, the MEP completes the configuration of application termination.

In some embodiments, after receiving the termination request message, the MEP may complete the termination operation of the MEC application or the operation of destroying the MEC application according to the application instance identifier of the MEC application in the termination request message.

S708, the MEP sends a termination response message to the MEPM

In some embodiments, after completing the termination operation of the MEC application, the MEP may send a termination response message to the corresponding MEPM. The application termination response message is used to indicate that the MEC application has been terminated or destroyed. The application termination response message carries the application instance identifier of the MEC application.

S709. The MEPM sends a resource deletion request to the VIM.

In some embodiments, after receiving the termination response message, the MEPM sends a resource deletion request carrying the application instance identifier of the MEC application to the VIM, where the resource deletion request is used to request the VIM to delete the virtualized resources related to the running of the MEC application .

S710. The VIM sends a resource deletion response to the MEPM.

In some embodiments, after receiving the resource deletion request, the VIM deletes the virtualized resources of the MEC application according to the application instance identifier of the MEC application in the resource deletion request. Then, a resource deletion response is sent to the MEPM, where the resource deletion response is used to indicate that the MEC application is successfully terminated and the resources occupied by the application instance of the MEC application are deleted.

S711. The MEPM sends an application termination response to the first cloud connector.

In some embodiments, after receiving the resource deletion response, the MEPM sends an application termination response to the corresponding first cloud connector. The application termination response is used to indicate that the MEC application is terminated successfully and the resources occupied by the application instance of the MEC application have been deleted.

S712. The first cloud connector sends an application termination response to the server of the first public cloud.

In some embodiments, after receiving the configuration response, the first cloud connector sends an application termination response to the corresponding server of the first public cloud.

S713. The server of the first public cloud sends an application termination response to the MEO.

In some embodiments, after receiving the application termination response, the server of the first public cloud sends the application termination response to the MEO, thereby completing the entire application termination process.

The technical solutions provided by the above embodiments bring at least the following beneficial effects. In the embodiments of the present application, the MEPM in the standard MEC system is extended, and multiple cloud connectors are connected to the MEPM, and the multiple cloud connectors are respectively used for Connecting to multiple public clouds, specifically, the cloud connector can receive cloud-side collaboration requests from servers corresponding to the public cloud, and convert the cloud-side collaboration request into a request that conforms to the standard format of the MEC system, so that the MEC system can respond to the cloud-side collaboration request The collaborative request realizes the cloud-side collaborative configuration of the public cloud and the MEC system. In this way, for different public clouds, a unified process can be used to realize the cloud-side collaborative configuration of the public cloud and the MEC system, which reduces the difficulty of connecting the MEC system to multiple public clouds.

Further, the embodiments of the present application are based on the existing standards and processes of the MEC system, and the provided public cloud access function can make full use of the functional components and processes of the MEC system, which further facilitates operators to realize that the MEC system is connected to multiple public clouds, and provides Give users more space to choose public cloud, in line with the multi-cloud scenario under the future trend.

In addition, the embodiments of the present application are extended on the standard MEC system, which conforms to the multi-level architecture of the existing MEC system. When the public cloud is connected to the MEC system, the MEC system can deploy the public cloud in stages according to the requirements of different manufacturers, such as the delay, etc., to give full play to the resource scheduling advantages of the MEC system, and bring better services and experience to users and public cloud manufacturers. . The multi-level architecture of the MEC system can also be integrated with wireless networks such as Open-Radio Access Network (O-RAN). It can be deployed on private networks in vertical industries to meet the diverse needs of vertical industries.

In an exemplary embodiment, the present application also provides a cloud-edge collaboration device. The cloud-edge coordination apparatus may include one or more functional modules for implementing the cloud-edge coordination method in the above method embodiments.

For example, FIG. 8 is a schematic diagram of the composition of a cloud-side coordination apparatus provided by an embodiment of the present application. The cloud-side collaboration apparatus can be applied to an MEC system. The MEC system includes: an MEPM, and the MEPM is connected with a plurality of cloud connectors, and a plurality of cloud connectors are connected to the MEPM. The cloud connectors are in one-to-one correspondence with the plurality of public clouds, and the plurality of cloud connectors include the first cloud connector. The first cloud connector includes a cloud-side coordination device; as shown in FIG. 8 , the cloud-side coordination device includes: a receiving module 801 , a converting module 802 and a sending module 803 . The receiving module 801 , the converting module 802 and the sending module 803 are connected.

A receiving module 801, configured to receive a cloud-side collaboration request in a first format from a server of a first public cloud; wherein the first public cloud is a public cloud corresponding to the first cloud connector, and the cloud-side collaboration request is used to request MEC The system realizes the collaborative configuration with the cloud-side of the first public cloud, and the first format satisfies the interface standard of the server of the first public cloud.

The conversion module 802 is configured to convert the cloud-side collaboration request from the first format to the second format; the second format satisfies the interface standard of the MEC system.

The sending module 803 is configured to send a cloud-side collaboration request in the second format to the MEPM, so that the MEC system responds to the cloud-side collaboration request in the second format to implement the cloud-side collaboration configuration of the first public cloud and the MEC system.

In some embodiments, the MEPM is connected to multiple cloud connectors through standard interfaces of the MEC system; the standard interfaces of the MEC system include: Mm2 interface, Mm3 interface.

For example, FIG. 9 is a schematic diagram of the composition of a cloud-side coordination apparatus provided by an embodiment of the present application. The cloud-side coordination apparatus can be applied to a server of a first public cloud, and the first public cloud is connected to the MEC system through a first cloud connector , the MEC system includes: MEPM, the MEPM is connected with multiple cloud connectors, the multiple cloud connectors are in one-to-one correspondence with multiple public clouds, the multiple public clouds include the first public cloud, and the first cloud connector is multiple cloud connectors The connector includes a cloud connector corresponding to the first public cloud. As shown in FIG. 9 , the cloud-side collaboration apparatus includes: a sending module 901 .

A sending module 901 is configured to send a cloud-side collaboration request in a first format to the first cloud connector; wherein, the cloud-side collaboration request is used to request the MEC system to implement the cloud-side collaboration configuration with the first public cloud, so that the first cloud is connected The device converts the cloud-side collaboration request from the first format to the second format, and then makes the MEC system respond to the cloud-side collaboration request in the second format to realize the cloud-side collaboration configuration between the first public cloud and the MEC system; the first format satisfies the first public cloud-side collaboration request. The interface standard of the cloud server, and the second format satisfies the interface standard of the MEC system.

In some embodiments, the above-mentioned MEC system further includes: MEO.

The sending module 901 is further configured to send a resource query request to the MEO.

The above cloud-edge coordination apparatus further includes a receiving module 902; the receiving module 902 is configured to receive a resource query response from the MEO; wherein the resource query response includes information of the MEPM and information of the first cloud connector.

The sending module 901 is specifically configured to send the cloud-side collaboration request in the first format to the first cloud connector according to the resource query response.

In an exemplary embodiment, an embodiment of the present application further provides a cloud-edge coordination apparatus, which is applied to an MEC system. FIG. 10 is a schematic structural diagram of a cloud-side collaboration apparatus provided by an embodiment of the present application. As shown in FIG. 10 , the cloud-side collaboration apparatus may include: a processor 1001 and a memory 1002 ; Instructions; when the processor 1001 is configured to execute the instructions, the MEC system enables the MEC system to implement the methods described in the foregoing method embodiments.

In an exemplary embodiment, the embodiments of the present application further provide a computer-readable storage medium, on which computer program instructions are stored; when the computer program instructions are executed by a computer, the computer is made to implement the method described in the foregoing embodiments. . The computer-readable storage medium may be a non-transitory computer-readable storage medium, for example, the non-transitory computer-readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.

In an exemplary embodiment, an embodiment of the present application further provides a computer program product, when the computer program product runs on a computer, the computer executes the above-mentioned relevant method steps, so as to realize the cloud-edge collaboration in the above-mentioned embodiment method.

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto, and any changes or substitutions within the technical scope disclosed in the present application should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims (10)

1. A cloud edge coordination method is applied to a multi-access edge computing (MEC) system, and the MEC system comprises: a multi-access edge computing platform management unit (MEPM) having a plurality of cloud connectors connected thereto, the plurality of cloud connectors in one-to-one correspondence with a plurality of public clouds, the plurality of cloud connectors including a first cloud connector, the method comprising:

the first cloud connector receives a cloud-edge collaboration request in a first format from a server of a first public cloud; wherein the first public cloud is a public cloud corresponding to the first cloud connector, the cloud-edge cooperative request is used to request the MEC system to implement cloud-edge cooperative configuration with the first public cloud, and the first format satisfies an interface standard of a server of the first public cloud;

the first cloud connector converts the cloud edge collaboration request from the first format to a second format; the second format satisfies an interface standard of the MEC system;

the first cloud connector sends the cloud-edge collaboration request in the second format to the MEPM, so that the MEC system responds to the cloud-edge collaboration request in the second format to achieve cloud-edge collaboration configuration of the first public cloud and the MEC system.

2. The method of claim 1, wherein the MEPM is connected to the plurality of cloud connectors through a standard interface of an MEC system;

the standard interface of the MEC system comprises: the multi-access edge manages the Mm2 interface, the Mm3 interface.

3. The method of claim 1 or 2, wherein the MEC system further comprises: a multi-access edge orchestrator MEO;

before the first cloud connector receives a cloud-edge collaboration request in a first format from a server of a first public cloud, the method further comprises:

the MEO receives a resource query request sent by a server from the first public cloud;

the MEO sending a resource query response to a server of the first public cloud; wherein the resource query response includes information of the MEPM and information of the first cloud connector.

4. A cloud-edge coordination method is applied to a server of a first public cloud, the first public cloud accesses a multi-access edge computing (MEC) system through a first cloud connector, and the MEC system comprises: a multi-access edge computing platform management unit (MEPM) connected with a plurality of cloud connectors, the plurality of cloud connectors in one-to-one correspondence with a plurality of public clouds including the first public cloud, the first cloud connector being a cloud connector included in the plurality of cloud connectors that corresponds to the first public cloud, the method comprising:

the server of the first public cloud sends a cloud edge coordination request in a first format to the first cloud connector;

the cloud-edge cooperative request is used for requesting the MEC system to realize the cloud-edge cooperative configuration with the first public cloud, so that the first cloud connector converts the cloud-edge cooperative request from the first format to a second format, and the MEC system responds to the cloud-edge cooperative request in the second format to realize the cloud-edge cooperative configuration between the first public cloud and the MEC system;

the first format satisfies an interface standard of a server of the first public cloud, and the second format satisfies an interface standard of the MEC system.

5. The method of claim 4, wherein the MEC system further comprises: a multi-access edge orchestrator MEO;

before the server of the first public cloud sends the cloud-edge collaboration request in the first format to the first cloud connector, the method further includes:

a server of the first public cloud sends a resource query request to the MEO;

a server of the first public cloud receiving a resource query response from the MEO; wherein the resource query response includes information of the MEPM and information of the first cloud connector;

the server of the first public cloud sending a cloud edge coordination request in a first format to the first cloud connector, including:

and the server of the first public cloud sends the cloud edge coordination request in the first format to the first cloud connector according to the resource query response.

6. A cloud edge coordination apparatus, applied to a multi-access edge computing (MEC) system, the MEC system comprising: a multi-access edge computing platform management unit (MEPM) connected with a plurality of cloud connectors, the plurality of cloud connectors corresponding to a plurality of public clouds one-to-one, the plurality of cloud connectors comprising a first cloud connector, the first cloud connector comprising the cloud edge coordination device; the cloud edge coordination device comprises: the receiving module, the conversion module and the sending module are connected;

the receiving module is used for receiving a cloud edge coordination request in a first format from a server of a first public cloud; wherein the first public cloud is a public cloud corresponding to the first cloud connector, the cloud-edge cooperative request is used to request the MEC system to implement cloud-edge cooperative configuration with the first public cloud, and the first format satisfies an interface standard of a server of the first public cloud;

the conversion module is configured to convert the cloud edge coordination request from the first format to a second format; the second format satisfies an interface standard of the MEC system;

the sending module is configured to send the cloud-edge coordination request in the second format to the MEPM, so that the MEC system responds to the cloud-edge coordination request in the second format to implement cloud-edge coordination configuration between the first public cloud and the MEC system.

7. The cloud-edge coordination device according to claim 6, wherein said MEPM is connected to said plurality of cloud connectors via a standard interface of an MEC system;

the standard interface of the MEC system comprises: the multi-access edge manages the Mm2 interface, the Mm3 interface.

8. A cloud edge coordination apparatus, applied to a server of a first public cloud, the first public cloud accessing a multi-access edge computing MEC system through a first cloud connector, the MEC system comprising: a multi-access edge computing platform management unit (MEPM) connected with a plurality of cloud connectors, the plurality of cloud connectors and a plurality of public clouds one-to-one, the plurality of public clouds include the first public cloud, the first cloud connector is the cloud connector that the plurality of cloud connectors include with the first public cloud corresponds, the cloud edge coordination apparatus includes: a sending module;

the sending module is configured to send a cloud edge coordination request in a first format to the first cloud connector;

the cloud-edge cooperative request is used for requesting the MEC system to realize the cloud-edge cooperative configuration with the first public cloud, so that the first cloud connector converts the cloud-edge cooperative request from the first format to a second format, and the MEC system responds to the cloud-edge cooperative request in the second format to realize the cloud-edge cooperative configuration between the first public cloud and the MEC system;

the first format satisfies an interface standard of a server of the first public cloud, and the second format satisfies an interface standard of the MEC system.

9. A cloud edge coordination device applied to a multi-access edge computing (MEC) system, the cloud edge coordination device comprising: a processor and a memory;

the memory stores instructions executable by the processor;

the processor is configured to, when executing the instructions, cause the MEC system to implement the method of any of claims 1-5.

10. A computer-readable storage medium, the computer-readable storage medium comprising: computer software instructions;

the computer software instructions, when executed in a multi-access edge computing, MEC, system, cause the MEC system to implement the method of any of claims 1-5.

Images