CN114301914A

CN114301914A - Cloud edge coordination method and device and storage medium

Info

Publication number: CN114301914A
Application number: CN202111617192.7A
Authority: CN
Inventors: 陈杲; 黄蓉; 黄倩; 范斌; 扈翠敏
Original assignee: China United Network Communications Group Co Ltd
Current assignee: China United Network Communications Group Co Ltd
Priority date: 2021-12-27
Filing date: 2021-12-27
Publication date: 2022-04-08
Anticipated expiration: 2041-12-27
Also published as: CN114301914B

Abstract

The application provides a cloud-edge coordination method, a cloud-edge coordination device and a storage medium, which relate to the technical field of communication. The method comprises the following steps: a server of a first public cloud sends a cloud edge coordination request in a first format to a first cloud connector; the method comprises the steps that a cloud edge cooperative request is used for requesting an MEC system to achieve cloud edge cooperative configuration with a first public cloud; the first cloud connector converts the cloud edge collaboration request from a first format to a second format; the first cloud connector sends the cloud edge cooperation request in the second format to the MEPM, so that the MEC system responds to the cloud edge cooperation request in the second format to achieve cloud edge cooperation configuration of the first public cloud and the MEC system. The method and the device are used for achieving the cloud-edge collaboration process of the public cloud and the MEC system and solving the problem that the MEC system is difficult to dock a plurality of public clouds.

Description

Cloud edge coordination method and device and storage medium

Technical Field

The present application relates to the field of communications technologies, and in particular, to a cloud-edge coordination method, apparatus, and storage medium.

Background

As the 5th Generation Mobile Communication Technology (5G) wireless network starts to advance to the depth of business and vertical industry digital transformation, people have higher requirements for low latency of network computing power, and thus edge computing Technology begins to show up. The edge computing technology is an open platform integrating network, computing, storage and application core capabilities on one side close to an object or a data source, can provide nearby services for users, and meets the low-delay requirements of people. As a specific implementation of Edge Computing technology, a Multi-access Edge Computing (MEC) system gradually becomes a key infrastructure for carrying various innovative applications. The cloud-edge cooperation is used as the core of the edge computing technology, and refers to the cooperation of public cloud and MEC systems in the aspects of computing resources, security policies, application management, business management and the like, so as to provide various network computing services for users.

With the trend of cloud computing, the MEC system should not limit which public cloud the user uses to provide network computing services for the user, and should support multiple public clouds to access the MEC system for the user to select. In the prior art, different public clouds are provided by different manufacturers, but because interface standards of the public clouds of the different manufacturers are not consistent, when an MEC system is accessed into a plurality of public clouds, each public cloud needs to be configured separately according to the interface standards of the different public clouds, so as to realize a cloud-edge coordination function between each public cloud and the MEC system. For an operator, when a plurality of public clouds need to be docked, the deployment difficulty of the operator is greatly increased by the single deployment scheme, so that the existing MEC system is difficult to dock the plurality of public clouds.

Disclosure of Invention

The application provides a cloud-edge coordination method, a cloud-edge coordination device and a storage medium, which can enable an MEC system to conveniently butt joint a plurality of public clouds and realize a cloud-edge coordination function between the MEC system and each public cloud.

In a first aspect, the present application provides a cloud edge coordination method, which is applied to a multi-access edge computing MEC system, where the MEC system includes: the method comprises the following steps that a multi-access edge computing platform management unit (MEPM) is connected with a plurality of cloud connectors, the cloud connectors correspond to a plurality of public clouds in a one-to-one mode, the cloud connectors comprise a first cloud connector, and the method comprises the following steps: a first cloud connector receives a cloud edge collaboration request in a first format from a server of a first public cloud; the first public cloud is a public cloud corresponding to the first cloud connector, the cloud edge coordination request is used for requesting the MEC system to realize cloud edge coordination configuration with the first public cloud, and the first format meets the interface standard of a server of the first public cloud; the first cloud connector converts the cloud edge collaboration request from a first format to a second format; the second format meets the interface standard of the MEC system; the first cloud connector sends the cloud edge cooperation request in the second format to the MEPM, so that the MEC system responds to the cloud edge cooperation request in the second format to achieve cloud edge cooperation configuration of the first public cloud and the MEC system.

In one possible implementation, the MEPM is connected to a plurality of cloud connectors through a standard interface of the MEC system; the standard interfaces of the MEC system include: the multi-access edge manages the Mm2 interface, the Mm3 interface.

In another possible implementation manner, the 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 comprises: the MEO receives a resource query request sent by a server from a first public cloud; the MEO sends 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.

In a second aspect, the present application provides a cloud-edge coordination method, which is applied to a server of a first public cloud, where the first public cloud is accessed to a multi-access edge computing MEC system through a first cloud connector, and the MEC system includes: edge computing platform management unit MEPM is inserted more, and the MEPM is connected with a plurality of cloud connectors, a plurality of cloud connectors and a plurality of public cloud one-to-one, and a plurality of public clouds include first public cloud, and the cloud connector that corresponds with first public cloud that first cloud connector includes for a plurality of cloud connectors, this method includes: a server of a first public cloud sends a cloud edge coordination request in a first format to a first cloud connector; the method comprises the steps that a cloud edge cooperation request is used for requesting an MEC system to achieve cloud edge cooperation configuration with a first public cloud, so that a first cloud connector converts the cloud edge cooperation request from a first format to a second format, and the MEC system responds to the cloud edge cooperation request in the second format to achieve cloud edge cooperation configuration of 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.

In a possible implementation manner, the MEC system further includes: a multi-access edge orchestrator MEO; before the server of the first public cloud sends the cloud-edge coordination request in the first format to the first cloud connector, the method further includes: a server of a first public cloud sends a resource query request to an MEO; a server of the first public cloud receives a resource query response from the MEO; wherein the resource query response comprises information of the MEPM and information of the first cloud connector; the method for sending the cloud edge coordination request in the first format to the first cloud connector by the server of the first public cloud comprises the following steps: and 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.

The cloud edge cooperation method provided by the application is used for expanding the MEPM in a standard MEC system, and connecting a plurality of cloud connectors to the MEPM, wherein the plurality of cloud connectors are respectively used for butt joint of a plurality of public clouds, specifically, the cloud connectors can receive cloud edge cooperation requests from servers corresponding to the public clouds and convert the cloud edge cooperation requests into requests meeting the standard format of the MEC system, so that the MEC system can respond to the cloud edge cooperation requests to realize cloud edge cooperation configuration of the public clouds and the MEC system. Therefore, for different public clouds, the cloud edge cooperative configuration of the public clouds and the MEC system can be realized by adopting a unified flow, and the difficulty of docking the MEC system with the public clouds is reduced.

Furthermore, based on the existing standards and processes of the MEC system, the provided public cloud access function can fully utilize the functional components and processes of the MEC system, so that the MEC system can be conveniently docked with a plurality of public clouds by an operator, more public cloud selection spaces are provided for users, and a multi-cloud scene under a future trend is met.

In addition, the embodiment of the application is expanded on a standard MEC system, and accords with a multi-level architecture of the existing MEC system. When the public cloud is accessed into the MEC system, the MEC system can deploy the public cloud in a grading way according to the requirements of time delay and the like of different manufacturers, the resource scheduling advantage of the MEC system is fully exerted, and better service and use experience are brought to users and public cloud manufacturers. The multi-level architecture of the MEC system can be integrated with Open-Radio Access Network (O-RAN) and other wireless networks, for example, the MEC can be deeply combined with a 5G cloud small base station, so that the MEC system is more suitable for being deployed in private networks of vertical industries such as parks and factories, and can meet the diversified requirements of the vertical industries.

In a third aspect, the present application provides a cloud-edge coordination apparatus, which is applied to a multi-access edge computing MEC system, where the MEC system includes: the multi-access edge computing platform management unit (MEPM) is connected with a plurality of cloud connectors, the cloud connectors correspond to a plurality of public clouds one by one, the cloud connectors comprise first cloud connectors, and the first cloud connectors comprise cloud edge coordination devices; the cloud edge coordination device comprises: the device comprises a receiving module, a conversion module and a sending module; the conversion module is connected with the sending module; the system comprises a receiving module, a sending module and a receiving module, wherein the receiving module is used for receiving a cloud edge cooperation request in a first format from a server of a first public cloud; the first public cloud is a public cloud corresponding to the first cloud connector, the cloud edge coordination request is used for requesting the MEC system to realize cloud edge coordination configuration with the first public cloud, and the first format meets the interface standard of a server of the first public cloud; the conversion module is used for converting the cloud edge cooperation request from a first format to a second format; the second format meets the 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 the cloud-edge coordination configuration between the first public cloud and the MEC system.

In a fourth aspect, the present application provides a cloud edge coordination apparatus, which is applied to a server of a first public cloud, where the first public cloud accesses a multi-access edge computing MEC system through a first cloud connector, and the MEC system includes: edge computing platform management unit MEPM is inserted more, and MEPM is connected with a plurality of cloud connectors, a plurality of cloud connectors and a plurality of public cloud one-to-one, and a plurality of public clouds include first public cloud, and first cloud connector include for a plurality of cloud connectors with the cloud connector that first public cloud corresponds, this cloud limit is in coordination the device and includes: a sending module; the sending module is used for sending the cloud edge coordination request in the first format to the first cloud connector; the method comprises the steps that a cloud edge cooperation request is used for requesting an MEC system to achieve cloud edge cooperation configuration with a first public cloud, so that a first cloud connector converts the cloud edge cooperation request from a first format to a second format, and the MEC system responds to the cloud edge cooperation request in the second format to achieve cloud edge cooperation configuration of 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.

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

In a fifth aspect, the present application provides a cloud edge coordination apparatus, which is applied to a multi-access edge computing MEC system, and the cloud edge coordination apparatus includes: a processor and a memory; the memory stores instructions executable by the processor; the processor is configured to execute the instructions such that the MEC system implements the method of any of the first or second aspects described above.

In a sixth aspect, the present application provides a 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 one of the first or second aspects described above.

The beneficial effects of the third to sixth aspects may refer to the corresponding descriptions of the first aspect or the second aspect, and are not repeated.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is a schematic diagram illustrating a system composition of cloud-edge collaboration provided in the present application;

fig. 2 is a schematic diagram of the composition of an MEC system provided herein;

FIG. 3 is a schematic diagram of the composition of another MEC system provided herein;

fig. 4 is a schematic flow chart of a cloud-edge coordination method provided in the present application;

fig. 5 is a schematic flow chart of another cloud-edge coordination method provided in the present application;

FIG. 6 is a flowchart illustrating an application instantiation method provided by the present application;

FIG. 7 is a flowchart illustrating an application termination method according to the present application;

fig. 8 is a schematic composition diagram of a cloud-edge coordination apparatus provided in the present application;

fig. 9 is a schematic composition diagram of another cloud-edge coordination apparatus provided in the present application;

fig. 10 is a schematic structural diagram of a cloud-edge coordination apparatus provided in the present application.

Detailed Description

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, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, 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 "exemplary" or "for example" are used to mean serving as examples, illustrations or descriptions. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

For the convenience of clearly describing the technical solutions of the embodiments of the present application, in the embodiments of the present application, the terms "first", "second", and the like are used for distinguishing the same items or similar items with basically the same functions and actions, and those skilled in the art can understand that the terms "first", "second", and the like are not limited in number or execution order.

At present, MEC systems have become a key infrastructure to carry a variety of innovative applications. The MEC system not only needs to utilize 5G of network capability with large bandwidth, low time delay, high reliability and multiple connections, but also needs to be fused with cloud computing, big data and artificial intelligence technologies to enable the industry of all social industries (including manufacturing industry, smart cities, retail industry, medical industry, education industry, transportation industry, digital government and the like) to carry out industry upgrading and enterprise digital transformation. In addition, with the development of the cloud computing technology, the distributed cloud architecture of the "central cloud + MEC system" starts to take a full head, the cloud architecture extends from the center to the edge, and the distributed deployment of the cloud computing service at the edge side of the network step by step is a development trend of a future computing form, that is, the edge computing technology is a development trend of the future computing form. The cloud edge coordination is the core of the distributed cloud architecture, and therefore, the enhancement of the cloud edge coordination capability is the core of the development of the edge computing technology. The central cloud is a centralized public cloud.

As shown in fig. 1, from the perspective of system composition, cloud-edge collaboration mainly includes three layers, namely, collaboration of a public cloud and an MEC system on the Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and application as a Service (SaaS) levels, and meanwhile, collaboration in terms of charging, operation and maintenance monitoring, security, and the like needs to be considered.

The cooperation on the IaaS level refers to resource cooperation between a public cloud IaaS and an Edge (Edge) IaaS, the cooperation on the SaaS level refers to application service cooperation between the public cloud SaaS and the Edge SaaS, and the cooperation on the PaaS level refers to deployment cooperation, intelligent cooperation, service arrangement cooperation and data cooperation between the public cloud PaaS and the Edge PaaS. The cloud-edge cooperation can be embodied as online, deployment (instantiation), monitoring, changing, termination and the like of a cloud application in the MEC system, so as to provide various network computing services for users.

With the trend of cloud computing, the MEC system should not limit which public cloud the user uses to provide network computing services for the user, and should support multiple public clouds to access the MEC system for the user to select. In addition, since the MEC system needs to be deployed in a hierarchical manner according to the difference of manufacturers to which the public cloud belongs and the difference of the time delay requirements in the actual deployment process, the public cloud needs to conform to the multi-level architecture of the MEC system when accessing the MEC system. Because each public cloud is provided by each manufacturer, the interface standards of the public clouds of each manufacturer are not consistent, and the MEC system needs to be configured according to the interface standards of each public cloud when accessing a plurality of public clouds to realize the cloud-edge coordination function. The coupling of this scheme is too high, and it is too difficult for the operator to interface with multiple public clouds. If the MEC system is unable to support multiple public clouds, the space in which the user can select the public clouds may be limited, resulting in a degradation of the user experience.

In this background technology, an embodiment of the present application provides a cloud-edge coordination method, by which an MEC system can be conveniently docked with a plurality of public clouds and a cloud-edge coordination function between the MEC system and each public cloud is implemented, thereby reducing deployment difficulty of an operator.

The cloud edge coordination method provided by the application can be applied to an MEC system shown in FIG. 2. As shown in fig. 2, the MEC System includes two levels, an MEC System Level (MEC System Level) and an MEC Host Level (MEC Host Level). Wherein the MEC System level includes an Operations Support System (OSS) and a Multi-access Edge organizer (MEO). The MEC host level includes: an MEC Platform management unit (MEPM), a Virtualization Infrastructure management unit (VIM), and an MEC host.

The OSS is configured to receive requests external to the request and authorize the requests. The authorized request is forwarded to the MEO for further processing.

The MEO is a core functional component of the MEC system level, and mainly has the following functions: the method comprises the steps of deploying and maintaining an overall resource view, available mobile edge services and a topological structure of an MEC system according to an MEC host; selecting an appropriate MEC host according to a constraint condition (such as delay of MEC application, etc.) to provide available resources and available services for MEC application instantiation; triggering MEC application instantiation or termination; triggering MEC application relocation, etc.

The MEPM is the core of the MEC host level, and is mainly responsible for the following functions: managing the lifecycle of the application, including notifying the MEO of relevant information; providing element management functions for the MEP; managing application rules and requirements, including service authorization, traffic rules, local Domain Name System (DNS) configuration, and resolving conflicts; and receiving fault reports and performance speed measurement data from the VIM for further optimizing the VIM and the like.

VIM is primarily responsible for the following functions: allocating, managing, and releasing virtualized resources (such as computing resources, storage resources, and network resources); preparing a virtualization infrastructure to run a software image; performance and fault information is collected and reported about the virtualized resources.

The MEC host, which may be a physical host, is mainly used to provide computing, storage, and network resources for the MEC application. The MEC hosts are typically deployed in different scenarios according to different latency requirements. For example, for a service with low network delay requirement, the MEC host may be deployed in a core computer room in the city. For services with high network delay requirements, the MEC host needs to be further sunk to a convergence or access computer room. If the service has high requirements on network delay and strict requirements on data security and privacy, the MEC host can be deployed in a machine room on the client side site.

The MEC host includes a Multi-access Edge Computing Platform (MEP), a Virtualization Infrastructure (VI), and an MEC application.

MEPs are responsible for the following functions: providing an environment in which MEC applications can be deployed, brought online, run, and provide MEC services; receiving a DNS record from the MEPM and responsively configuring the DNS proxy/server; receive traffic rules from the MEPM, application or service and configure the data plane.

The VI primarily provides computing, storage, and network resources for the MEC applications, and may provide persistent storage and time-related information for the MEC applications.

The MEC application may include an application program of a virtual machine running on the virtualization infrastructure, and may also include an application program running on a container. The MEC application may interact with the mobile edge platform to provide MEC services and may also interact with the MEPs to perform procedures related to the MEC application lifecycle, such as: indicating availability of MEC applications, relocating user status, etc. In addition to this, MEC applications also have some rules and requirements, such as: but also rules and requirements for required resources, maximum delay, required services or useful services.

In the MEC system shown in fig. 2, components between MEC hosts and within the MEC host may communicate with each other through a Multi-access Edge point (Mp) interface of the Multi-access Edge platform. The MEC host and other devices in the MEC system may communicate with each other through a Multi-access Edge management (Mm) interface, and other devices in the MEC system except the MEC host may also communicate with each other through the Mm interface.

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

It should be noted that the illustrated components of the present embodiment do not constitute a specific limitation on the MEC system. That is, fig. 2 is only an exemplary diagram, 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 some devices may be combined, some devices may be split, or a different arrangement of devices. For example, the MEC system may include other devices, etc. in addition to the devices shown in fig. 2. In addition, in this embodiment, names of the devices and names of interfaces between the devices in fig. 2 are not limited. For example, in addition to the names shown in fig. 2, the devices and interfaces between the devices may be named by other names, without limitation.

According to the cloud-edge coordination method provided by the embodiment of the application, the MEPM in the MEC system is subjected to function expansion, and a plurality of cloud connectors are added to complete butt joint with a plurality of public clouds. As shown in fig. 3, in the MEC system, the MEPM is connected to a cloud connector 1-a cloud connector n, and the cloud connector 1-the cloud connector n are used for respectively completing the docking between the MEC system and the public cloud 1-the public cloud n. Each cloud connector is a device exclusive to each public cloud manufacturer, and therefore the public cloud 1-the public cloud n and the cloud connector 1-the cloud connector n correspond to each other one by one. The public cloud interacts with the MEPM through the corresponding cloud connector, configuration management of the MEC host resources, the MEPs and the MEC application is achieved through the function of the MEPM, and cloud-side cooperative configuration of the public cloud and the MEC system is achieved. The cloud connector is connected with the MEPM through a standard interface of the MEC system. Illustratively, the standard interface in the MEC system may be an Mm2 interface or an Mm3 interface, that is, the cloud connector may be connected with the MEPM by using an Mm2 interface between the OSS and the MEPM, or by using an Mm3 interface between the MEO and the MEPM.

It should be noted that, in implementation, the cloud-edge coordination method provided in the embodiment of the present application does not directly relate to the modules such as OSS and VI in the MEC system shown in fig. 2, and therefore, the MEC system shown in fig. 3 does not show these modules.

In addition, as shown in fig. 3, the embodiment of the application conforms to a multi-level deployment mode adopted by the MEC system, can provide standardized cloud services and access requirements of cloud resources, and supports unified deployment (realization of cloud-edge cooperation) of cloud applications on the MEC system. The scheme is expanded on the original function of the existing MEC system, and the expanded MEPM, MEP and wireless network PaaS form a multi-stage PaaS framework to gradually open the network capability in sequence. For example, the wireless Network opens the wireless Network information, including the traditional base station information (e.g., context information related to the user, used to implement monitoring and real-time analysis of the user control process and the service flow, and obtain the wireless Network state, i.e., the characteristics, etc., related to the user) and the information specific to the Open-Radio Access Network (O-RAN) base station to the MEP. The MEP applies Network capabilities such as a Radio Network Information Service (RNIS), a Location Service (LS), a Bandwidth Service (BMS), and the like to the MEC through the MP1 interface upward.

The cloud-edge coordination method provided by the embodiment of the present application is described in detail below with reference to the accompanying drawings. The cloud edge coordination method provided by the application can be implemented by the MEC system shown in fig. 3. In addition, as described in the foregoing embodiment, the MEPM of the MEC system is connected with a plurality of cloud connectors, the plurality of cloud connectors correspond to a plurality of public clouds in a one-to-one manner, and the public clouds can interact with the MEPM through the cloud connectors corresponding to the public clouds, so as to finally realize the cloud-edge cooperative configuration with the MEC system. Different public clouds interact with the MEPM through corresponding cloud connectors, and the implementation process of the cloud edge cooperative configuration of the MEC system is similar to that of the cloud edge cooperative configuration of the MEC system, and the following embodiments shown in fig. 4 to 7 introduce the cloud edge cooperative configuration method of the embodiment of the present application in an example where the first public cloud (the first public cloud is any one of a plurality of public clouds, for example, any one of a public cloud 1-a public cloud n shown in fig. 3) and the MEC system implement the cloud edge cooperative configuration. Among them, the cloud connector corresponding to the first public cloud is hereinafter referred to as a first cloud connector.

Fig. 4 is a schematic flow chart of a cloud edge coordination method according to an embodiment of the present application. As shown in fig. 4, the method may include the steps of:

s401, the server of the first public cloud sends the cloud edge cooperation request of the first format to the first cloud connector.

The cloud edge coordination request is used for requesting the MEC system to realize cloud edge coordination configuration with the first public cloud, and the first format meets the interface standard of the server of the first public cloud.

The cloud connector is exclusive equipment for each public cloud manufacturer, so that the server of the public cloud and the cloud connector are communicated through interface standards specified by each public cloud manufacturer. The server of the first public cloud can send a cloud edge coordination request in a first format to the corresponding first cloud connector through a standard interface of the server so as to request the MEC system to realize cloud edge coordination configuration with the first public cloud.

S402, the first cloud connector converts the cloud edge cooperation request from a first format to a second format.

Wherein the second format meets the interface standard of the MEC system.

The first cloud connector can receive a cloud-edge cooperation request from a server of the first public cloud through a standard interface of the first cloud connector, and converts the cloud-edge cooperation request from a first format into a second format meeting the interface standard of the MEC system.

And S403, the first cloud connector sends the cloud edge coordination request in the second format to the MEPM.

The second format is a format meeting the interface standard of the MEC system, so that the first cloud connector can send the cloud edge collaboration request of the second format to the MEPM through the standard interface of the MEC system, so that the MEC system responds to the cloud edge collaboration request of the second format to achieve cloud edge collaboration configuration of the first public cloud and the MEC system.

The technical scheme provided by the embodiment at least has the following beneficial effects: in the embodiment of the application, the MEPMs in the standard MEC system are expanded, a plurality of cloud connectors are connected to the MEPMs, the cloud connectors are respectively used for being connected with a plurality of public clouds, specifically, the cloud connectors can receive cloud edge cooperation requests from servers corresponding to the public clouds and convert the cloud edge cooperation requests into requests meeting the standard format of the MEC system, and therefore the MEC system can respond to the cloud edge cooperation requests to achieve cloud edge cooperation configuration of the public clouds and the MEC system. Therefore, for different public clouds, the cloud edge cooperative configuration of the public clouds and the MEC system can be realized by adopting a unified flow, and the difficulty of docking the MEC system with the public clouds is reduced.

Fig. 5 is a schematic flow chart of another cloud edge coordination method according to the embodiment of the present application. As shown in fig. 5, the method may include:

s501, the server of the first public cloud sends a resource query request to the MEO.

Before a public cloud is needed, for example, the first public cloud and the cloud-side cooperation of the MEC system, a server of the first public cloud may first obtain resource information of the MEC system, for example, information including computing resources, network resources, storage resources, and the like, so as to select resources suitable for cloud-side cooperation deployment. The MEO is a core unit of the management capability of the MEC system, has a function of deploying and maintaining an overall resource view of the MEC system, and can select an appropriate resource for other devices according to a constraint condition (such as network delay). Therefore, in some embodiments, when the public cloud requires cloud-edge cooperative configuration of the first public cloud and the MEC system, the server of the first public cloud may send a resource query request to the MEO to request to query the resource information of the available resources of the MEC system.

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

The resource query response is used for indicating resource information of resources suitable for cooperative deployment of the first public cloud edge in the MEC system. Information suitable for computing resources and network resources co-deployed by the first public cloud may be included.

In some embodiments, after receiving the resource query request sent by the server of the first public cloud, the MEO determines the most suitable resource of the MEC system, such as a resource including the MEPM and the first cloud connector, according to the resource query request, the available resource in the MEC system, and the wireless network condition, and then carries information of the resource, such as information of the MEPM and information of the first cloud connector, in the resource query response to send to the server of the first public cloud.

S503, the server of the first public cloud sends the cloud edge coordination request in the first format to the first cloud connector.

The cloud edge cooperation request is used for the MEC system to achieve cloud edge cooperation configuration of the first public cloud and the MEC system, and the first format meets an interface standard of a server of the first public cloud.

In the embodiment of the application, the MEC system has access to a plurality of cloud connectors, and the plurality of cloud connectors correspond to a plurality of public clouds one to one. The cloud connector is exclusive equipment for each public cloud manufacturer, and the cloud connector and the server of the public cloud interact through the interface standard defined by each public cloud manufacturer, so that each public cloud can directly send a cloud edge cooperation request to the exclusive cloud connector.

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

S504, the first cloud connector converts the cloud edge cooperation request from the first format to the second format.

Wherein the second format meets the interface standard of the MEC system.

The multiple public clouds in which the MEC system is docked are usually provided by different manufacturers, and the interface standards of the public clouds of the manufacturers are often inconsistent, so that when cloud-edge collaborative configuration is performed, the formats of cloud-edge collaborative requests sent by servers of the public clouds are often inconsistent, and the cloud-edge collaborative requests in the formats also do not usually meet the interface standards of the MEC system. In this embodiment of the application, after the server of the public cloud sends the cloud-edge cooperative request in the first format to the corresponding cloud connector, and the cloud connector receives the request, the request sent by the server of the public cloud may be converted into a format meeting the interface standard of the MEC system, so that the MEC system may identify the request.

In some embodiments, the first cloud connector checks and adapts the cloud-edge coordination request after receiving the cloud-edge coordination request, and may convert the cloud-edge coordination request from a first format that satisfies an interface standard of a server of the first public cloud to a second format that satisfies an interface standard of the MEC system. The interface standard of the server of the public cloud is independently defined by each public cloud manufacturer, and the embodiment of the application does not limit the interface standard. The second format satisfies the interface standard of the MEC system.

And S505, the first cloud connector sends the cloud edge coordination request in the second format to the MEPM.

The request converted by the cloud connector conforms to the interface standard of the MEC system and is in an MEPM compatible format. The MEPM may receive and recognize the request sent by the cloud connector and perform the corresponding operation.

In some embodiments, after the cloud-edge coordination request is converted from the first format to the second format, the first cloud connector may send an identifiable cloud-edge coordination request to the MEPM through a standard interface in the MEC system, so that the MEC system realizes cloud-edge coordination configuration of the first public cloud and the MEC system.

It can be understood that although the interface standards of the public clouds of the manufacturers are not consistent, the requests sent by the servers corresponding to the public clouds can be uniformly converted into a format which can be compatibly recognized by the MEC system through the corresponding cloud connectors, the standard process of the conventional MEC system is met, and the MEC system can be connected with a plurality of public clouds without large-scale transformation of the MEC system.

The implementation of the cloud-edge cooperative configuration of the first public cloud and the MEC system by the MEC system may include the following steps S506 to S507.

S506, the MEPM interacts with the VIM, so that the VIM completes cloud-edge coordinated virtualized resource configuration.

The VIM's primary function 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-edge collaboration request in the second format, the MEPM may respond to the cloud-edge collaboration request, and interact with the VIM to complete the relevant configuration of the virtualized resources, such as computing resources, storage resources, and network resources, required by the cloud-edge collaboration.

And S507, the MEPM interacts with the MEP, so that the MEP completes the configuration of cloud edge cooperation.

The MEPM is mainly used to provide element management functions for MEPs and to manage rules and requirements of applications. MEPs are mainly used to provide mobile edge services for MEC applications, such as: services may be provided for discovery and use of MEC applications. The MEC application may be deployed, brought online, run, or terminated on the MEP (cloud-edge collaboration). Therefore, MEPs need to acquire the configuration of cloud edge coordination from MEPMs to complete the actual configuration of the MEC application. In some embodiments, after the VIM completes the configuration of the cloud-edge-coordinated virtualized resources, the MEPM may interact with the MEP, and transmit the configuration information of the cloud-edge-coordination to the MEP, so that the MEP completes the cloud-edge-coordination configuration such as deployment, online, operation, or termination of the MEC application according to the configuration information, and finally, the cloud-edge-coordination configuration of the first public cloud and the MEC system is realized.

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

The following describes a flow of cloud-edge collaboration according to an embodiment of the present application, taking instantiation (application deployment) of an application in cloud-edge collaboration as an example, 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, the public cloud, for example, the first public cloud, needs to acquire information of computing resources, network resources, and storage resources of the MEC system before performing application instantiation.

In some embodiments, a server of the first public cloud may send a resource query request to the MEO for querying information of the first cloud connector and the MEPM 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 a resource query request sent by a server of a first public cloud, an MEO determines, according to the resource query request, available resources of the MEC host, and wireless network conditions, an MEC host that is most suitable for deploying the MEC application, and an MEPM and a cloud connector corresponding to the MEC host, and sends a resource query response including information related to 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 the application instantiation request in the first format to the first cloud connector.

The application instantiation request may be one of the cloud edge collaboration requests described above. The application instantiation request may be used to request application instantiation of a cloud application of a public cloud to the MEC system.

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

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, the first cloud connector, upon receiving the application instantiation request, checks and adapts the application instantiation request, which may be converted from a first format that satisfies the interface standards of the servers of the first public cloud to a second format that satisfies the interface standards of the MEC system.

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

Wherein the application instantiation request in the second format can be received and identified 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 may send, to the MEPM, an application instantiation request recognizable by the MEPM through a standard interface in the MEC system, for requesting the application instantiation of the cloud-end application on the MEC system.

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

The resource allocation request carries requirement information of resources such as computation, storage and network required by application instantiation.

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

S607, VIM sends a resource allocation response to MEPM.

In some embodiments, the VIM, upon receiving the resource allocation request, sends a resource allocation response to the MEPM in accordance with the resource allocation request. The resource allocation response is used to indicate that the MEPM requested the resource successfully and is also used to indicate information that the allocated resource is instantiated for the application.

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

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

In some embodiments, the MEPM, upon receiving the resource allocation response, may send to the MEP configuration request information conveying application instantiation configuration information and information of resources allocated for application instantiation, e.g., the configuration information may include business rules, DNS rules, etc., so that the MEP completes the configuration of application instantiation.

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

In some embodiments, the MEP, upon receiving the configuration request message, may complete the configuration of the application instantiation from the configuration request message. Thereafter, the MEP may launch the MEC application.

S610, MEP sends configuration response message to 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.

And 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 a server of the corresponding 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 process of instantiating the entire application.

It should be noted that, support for a virtual machine based application descriptor (TOSCA) and a container based cloud native application descriptor (YAML) are formulated in the implementation related technology for application instantiation, and a unified standard for how to implement application instantiation has been formulated in the industry, so detailed processes of application instantiation in this embodiment are not described herein.

When the deployed (instantiated) application instance is no longer needed, the application instance can be terminated and the resources occupied by the application instance can be released in order to save resources. The flow of application termination will be described below with reference to the flow 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.

For the specific description of S701 and S702, reference may be made to the description of corresponding contents in S501 and S502, which is not repeated herein.

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

In some embodiments, the application termination request may be one of the cloud-edge collaboration requests described above. 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 identification of the MEC application.

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

The descriptions of the first format and the second format may refer to the corresponding descriptions of S503 and S504, which are not described herein again.

In some embodiments, the first cloud connector checks and adapts the application termination request after receiving the application termination request, and may convert the cloud-edge collaboration request from a first format that satisfies interface standards of servers of the first public cloud to a second format that satisfies interface standards of the MEC system.

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

Wherein the application termination request in the second format may be received and recognized by the MEPM. Thus, 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 over a standard interface in the MEC system for requesting the MEC system to terminate an 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, the MEPM needs to notify the MEP to terminate the MEC application first, and then notify the VIM to release the virtualized resources allocated to the MEC application by the VIM when the application is instantiated.

Therefore, in some embodiments, after receiving the application termination request sent by the first cloud connector, the MEPM may send, in response, 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 to request the MEP to destroy the instance of the MEC application. The termination request message carries an application instance identifier of the MEC application.

And S707, the MEP completes the configuration of the application termination.

In some embodiments, after receiving the termination request message, the MEP may complete a termination operation of the MEC application or destroy an operation of 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, the MEP may send a termination response message to the corresponding MEPM after completing the termination operation of the MEC application. 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 an 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 resource 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 resource 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 to delete the resources occupied by the application instance of the MEC application.

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

In some embodiments, the MEPM sends an application termination response to the corresponding first cloud connector after receiving the resource deletion response. The application termination response is used to indicate that the MEC application terminated successfully and that 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, the first cloud connector, upon receiving the configuration response, sends an application termination response to the server of the corresponding first public cloud.

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

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

The technical solution provided in the foregoing embodiment has at least the following beneficial effects that in the embodiment of the present application, the MEPM in the standard MEC system is expanded, the MEPM is connected to a plurality of cloud connectors, and the plurality of cloud connectors are respectively used for connecting a plurality of public clouds, specifically, the cloud connectors can receive cloud edge coordination requests from servers corresponding to the public clouds, and convert the cloud edge coordination requests into requests conforming to the standard format of the MEC system, so that the MEC system can respond to the cloud edge coordination requests to implement cloud edge coordination configuration of the public clouds and the MEC system. Therefore, for different public clouds, the cloud edge cooperative configuration of the public clouds and the MEC system can be realized by adopting a unified flow, and the difficulty of docking the MEC system with the public clouds is reduced.

In an exemplary embodiment, the present application further provides a cloud-edge coordination apparatus. The cloud-edge coordination device may include one or more functional modules, which are used to implement the cloud-edge coordination method of the foregoing method embodiments.

For example, fig. 8 is a schematic composition diagram of a cloud-edge coordination apparatus provided in an embodiment of the present application, where the cloud-edge coordination apparatus is applicable to an MEC system, and the MEC system includes: the MEPM is connected with a plurality of cloud connectors, and a plurality of cloud connectors and a plurality of public clouds one-to-one, a plurality of cloud connectors include first cloud connector. The first cloud connector comprises a cloud edge coordination device; as shown in fig. 8, the cloud edge coordination apparatus 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 edge coordination request in a first format from a server of a first public cloud; the first public cloud is a public cloud corresponding to the first cloud connector, the cloud edge coordination request is used for requesting the MEC system to realize cloud edge coordination configuration with the first public cloud, and the first format meets the interface standard of a server of the first public cloud.

A conversion module 802, configured to convert the cloud edge collaboration request from a first format to a second format; the second format satisfies the interface standard of the MEC system.

The sending module 803 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 the cloud-edge coordination configuration between the first public cloud and the MEC system.

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

For example, fig. 9 is a schematic composition diagram of a cloud-side coordination apparatus according to an embodiment of the present disclosure, where the cloud-side coordination apparatus is applicable to a server of a first public cloud, and the first public cloud accesses an MEC system through a first cloud connector, where the MEC system includes: the MEPM is connected with a plurality of cloud connectors, and a plurality of cloud connectors and a plurality of public clouds one-to-one, a plurality of public clouds include first public cloud, and the cloud connector that corresponds with first public cloud that a plurality of cloud connectors include is first cloud connector. As shown in fig. 9, the cloud edge coordination apparatus includes: a sending module 901.

A sending module 901, configured to send a cloud edge coordination request in a first format to a first cloud connector; the method comprises the steps that a cloud edge cooperation request is used for requesting an MEC system to achieve cloud edge cooperation configuration with a first public cloud, so that a first cloud connector converts the cloud edge cooperation request from a first format to a second format, and the MEC system responds to the cloud edge cooperation request in the second format to achieve cloud edge cooperation configuration of 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.

In some embodiments, the MEC system further comprises: MEO.

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

The cloud edge coordination apparatus further includes a receiving module 902; a receiving module 902, 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 edge coordination request in the first format to the first cloud connector according to the resource query response.

In an exemplary embodiment, the 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-edge cooperative apparatus provided in an embodiment of the present application, and as shown in fig. 10, the cloud-edge cooperative apparatus may include: a processor 1001 and a memory 1002; the memory 1002 stores instructions executable by the processor 1001; the processor 1001 is configured to execute instructions that, when executed, cause the MEC system to implement the method as described in the aforementioned method embodiments.

In an exemplary embodiment, the present application further provides a computer-readable storage medium having stored thereon computer program instructions; the computer program instructions, when executed by a computer, cause the computer to implement a method as described in the preceding 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 a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.

In an exemplary embodiment, the present application further provides a computer program product, which when running on a computer, causes the computer to execute the above related method steps to implement the cloud edge coordination method in the above embodiment.

The above is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

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;

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;

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.