WO2023082749A1

WO2023082749A1 - Service recovery method and system based on mec edge cloud, and storage medium

Info

Publication number: WO2023082749A1
Application number: PCT/CN2022/113470
Authority: WO
Inventors: 陈世亮; 杨梅; 杨磊; 丁涛; 朱庭俊; 苏悦; 翟晓羽; 张宇峰; 李忠
Original assignee: 中电信数智科技有限公司
Priority date: 2021-11-15
Filing date: 2022-08-19
Publication date: 2023-05-19
Also published as: CN114070851A

Abstract

Provided in the present invention are a service recovery method and system based on an MEC edge cloud, and a storage medium. The method comprises: acquiring service performance requirements of a production center; selecting, from among a plurality of MEC edge cloud nodes, an MEC edge cloud node that is capable of meeting the service performance requirements; creating a service recovery node on the selected MEC edge cloud node; and enabling a disaster recovery center, which has performed data backup on the production center, to send backup data and a backup system to the service recovery node, such that the service recovery node performs service recovery by using the backup data, and starts the backup system. In this way, the service recovery node, which meets the service performance requirements, is quickly established on the basis of the MEC edge cloud node, thereby guaranteeing the continuity and quality of service of a service.

Description

A service recovery method, storage medium and system based on MEC edge cloud

technical field

The present invention relates to the technical field of cloud computing, in particular to a service recovery method, storage medium and system based on MEC edge cloud.

Background technique

The traditional wireless communication disaster recovery solution generally adopts the two-site three-center solution (production center, same-city disaster recovery center, and remote disaster recovery center). The production center is equipped with a business system to support the operation of terminal application services. The center and the remote disaster recovery center respectively communicate with the production center through high-speed links, and then back up the business data of the production center in the form of synchronous replication/asynchronous replication. When a disaster occurs in the production center, its business data may be lost, resulting in the inability to run the business continuously. In this case, a disaster recovery emergency switch can be performed, so that the disaster recovery center can use the backup data to restore the business and maintain the continuous operation of the business.

With the development of 5G networks, the business system of the production center supports the operation of many low-latency terminal application services that have high requirements for ultra-low latency and ultra-large bandwidth, such as autonomous driving, industrial control, and telemedicine. Low-latency terminal applications The end-to-end delay is usually required to be less than 5ms during operation, and the disaster recovery center in the same city and the remote disaster recovery center are usually tens of kilometers or even hundreds of kilometers away from the production center. The end-to-end delay between them is greater than 100ms. Therefore, after the disaster recovery emergency switchover, the disaster recovery center cannot meet the service performance requirements of low-latency terminal applications.

Contents of the invention

The technical problem to be solved by the present invention is how to quickly establish a business recovery node that meets the business performance requirements based on the MEC edge cloud node when the disaster recovery center cannot meet the business performance requirements, so as to ensure business continuity and service quality.

The inventors found that MEC (Multi-access Edge Computing, multi-access edge computing) edge cloud is a cloud resource pool and cloud platform deployed on the edge side of the network close to the production center, which is widely distributed and close to the production center. Computing in the local network where the data is located can reduce the waiting time and network cost for data to and from the terminal application, and greatly reduce the congestion and burden of the operator's core network and transmission network, thereby greatly shortening the time between the service recovery node and the terminal application. Reduce network delay and reduce bandwidth pressure. Accordingly, the inventor provides the following technical solutions to solve the above technical problems:

The present invention provides a service recovery system based on MEC edge cloud, including a production center, a disaster recovery center, a disaster recovery management platform, an MEC management platform, and multiple MEC edge cloud nodes; the production center supports the operation and maintenance of terminal application services , and send data backup to the disaster recovery center, and the production center uploads business performance requirements to the disaster recovery management platform; the MEC management platform performs unified management and scheduling on multiple MEC edge cloud nodes; After the service performance requirements of the center, execute the service recovery node creation step a: select the MEC edge cloud node that can meet the service performance requirements from among the multiple MEC edge cloud nodes through the MEC management platform, and select the MEC edge cloud node on the selected MEC edge cloud node Create a business recovery node; after the disaster recovery management platform creates the business recovery node, the disaster recovery center will send the backup data and the backup system to the business recovery node; after the business recovery node receives the backup data and the backup system , use the backup data for business recovery and start the backup system.

Preferably, after the disaster recovery management platform obtains the business performance requirements of the production center, it judges whether the disaster recovery center can meet the business performance requirements, and if so, does not execute the business recovery node creation step a but instead Make the disaster recovery center perform business recovery.

Preferably, the service performance requirements include requirements on time delay and/or bandwidth for terminal applications to access the service system.

Preferably, in the step a of creating the business recovery node, if there are multiple MEC edge cloud nodes that can meet the business performance requirements, the disaster recovery management platform selects services among the multiple MEC edge cloud nodes through the MEC management platform The one with the strongest performance creates service recovery nodes on selected MEC edge cloud nodes.

Preferably, after the disaster recovery management platform obtains the business performance requirements of the production center, if no MEC edge cloud node can meet the business performance requirements, the disaster recovery management platform does not execute the business recovery node creation step a, Instead, execute step b of creating a service recovery node: use the MEC management platform to select one of the multiple MEC edge cloud nodes whose service performance is closest to the service performance requirement, and create a service recovery node on the selected MEC edge cloud node.

Preferably, the MEC management platform judges whether each MEC edge cloud node can meet the service performance requirements according to the distance between each MEC edge cloud node and the production center, specifically, the MEC edge cloud node and the The closer the distance between the production centers is, the closer the service performance of the MEC edge cloud node is to the service performance requirement.

Preferably, the production center supports the operation of automatic driving business, industrial control business and/or telemedicine business.

Preferably, there are multiple disaster recovery centers.

Preferably, the disaster recovery center is an intra-city disaster recovery center or a remote disaster recovery center.

The present invention also provides a service recovery method based on MEC edge cloud, comprising the following steps:

A. Obtain the business performance requirements of the production center;

B. Select an MEC edge cloud node that can meet the business performance requirements among multiple MEC edge cloud nodes;

C. Create a service recovery node on the selected MEC edge cloud node;

D. Make the disaster recovery center that has backed up the data of the production center send the backup data and the backup system to the service recovery node, so that the service recovery node can use the backup data to perform service recovery and start the backup system.

Preferably, after obtaining the business performance requirements of the production center in the step A, it is judged whether the disaster recovery center can meet the business performance requirements, and if it can meet, the steps B, C, and D are not executed Instead, the disaster recovery center is ordered to perform business recovery.

Preferably, said step B includes:

B1. Obtain multiple MEC edge cloud nodes;

B2. Determine whether there is an MEC edge cloud node that can meet the service performance requirements, and if there is a MEC edge cloud node that can meet the service performance requirements, select the MEC edge cloud node.

Preferably, in the step B2, if it is determined that there are multiple MEC edge cloud nodes that can meet the service performance requirements, select the one with the strongest service performance among the multiple MEC edge cloud nodes.

Preferably, in the step B2, if it is determined that no MEC edge cloud node can meet the service performance requirement, select one of the multiple MEC edge cloud nodes whose service performance is closest to the service performance requirement.

Preferably, in the step B2, according to the distance between each MEC edge cloud node and the production center, it is judged whether each MEC edge cloud node can meet the business performance requirements, specifically, the MEC edge cloud node and The closer the distance between the production centers is, the better the service performance of the MEC edge cloud nodes can meet the service performance requirements.

The present invention also provides a computer-readable storage medium, on which a computer program of a disaster recovery management platform is stored, and when the computer program is executed by a processor, the steps in the above-mentioned business recovery method are implemented, wherein the steps B is executed through the MEC management platform.

The invention has the following beneficial effects: since the MEC edge cloud node can greatly shorten the network delay between the service recovery node and the terminal application, and reduce the bandwidth pressure, the disaster recovery management platform obtains the production information when the production center fails. The business performance requirements of the center, and then select the MEC edge cloud node that can meet the business performance requirements among multiple MEC edge cloud nodes, create a business recovery node on the MEC edge cloud node that can meet the business performance requirements, and then make the disaster recovery The center sends the backup data and the backup system to the business recovery node, and the business recovery node uses the backup data to restore the business and start the backup system. In this way, the business recovery node that meets the business performance requirements can be quickly established based on the MEC edge cloud node, thereby ensuring business continuity and quality of service.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings that need to be used in the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present invention. For those skilled in the art, other drawings can also be obtained based on these drawings without creative effort.

Fig. 1 is a schematic structural diagram of an embodiment of a service recovery system based on MEC edge cloud in the present invention;

Fig. 2 is a schematic flowchart of an implementation manner of a method for service restoration based on an MEC edge cloud in the present invention.

Detailed ways

In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only It is a part of embodiments of the present invention, but not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

In the present invention, the term "comprising" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, device, product or equipment comprising a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units not listed, or optionally further includes For other steps or units inherent in these processes, methods, products or devices.

Reference herein to an "embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the present invention. The occurrences of this phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is understood explicitly and implicitly by those skilled in the art that the embodiments described herein can be combined with other embodiments.

This embodiment provides a service recovery system based on the MEC edge cloud, as shown in Figure 1, the system includes a production center 1, a disaster recovery center 2, a disaster recovery management platform 3, an MEC management platform 4, and multiple MEC edge cloud nodes , wherein the multiple MEC edge cloud nodes include a first MEC edge cloud node 5 and a second MEC edge cloud node 6 . The production center 1 is equipped with a business system 8 to support and run terminal application business, such as automatic driving business, industrial control business and telemedicine business. The disaster recovery center 2 is a disaster recovery center in the same city or a remote disaster recovery center, which deploys a business backup system for backing up the business data of the production center 1 and for business recovery. In other embodiments, the number of disaster recovery centers 2 can be Multiple. MEC

edge cloud nodes

5 and 6 are cloud resource pools and cloud platforms deployed on the edge of the network close to production center 1. They are widely distributed and close to production center 1. Computing is performed in the local network where production center 1 is located, reducing data The waiting time and network cost to and from the terminal application greatly reduce the congestion and burden on the operator's core network and transmission network, thereby greatly reducing the network delay and bandwidth pressure when transmitting business data to the terminal application.

The disaster recovery management platform 3 communicates with the production center 1, the disaster recovery center 2 and the MEC management platform 4 respectively. The MEC management platform 4 manages the two MEC

edge cloud nodes

5 and 6, and the communication between the production center 1 and the disaster recovery center 2 connect. The disaster recovery management platform 3 includes a computer-readable storage medium and a processor connected to each other, and the computer-readable storage medium is stored with a computer program of the backup management platform 3, and when the computer program is executed by the processor, the computer program shown in FIG. 2 is realized. A method for restoring services based on MEC edge cloud, the method includes the following steps A, B, C, and D.

A. Obtain the business performance requirements of production center 1.

In the process of supporting the operation of automatic driving business, industrial control business and telemedicine business, production center 1 synchronously or asynchronously transmits business data to disaster recovery center 2 for backup. Because autonomous driving services, industrial control services, and telemedicine services are low-latency terminal application services that have high requirements for ultra-low latency and ultra-large bandwidth, the service performance requirements of production center 1 include The end-to-end delay is less than 5ms. When the production center 1 is running the terminal application business, it uploads the business importance information including business performance requirements to the disaster recovery management platform 3, that is, the disaster recovery management The business performance requirements of the production center 1 can be obtained only by the importance information, including the end-to-end delay of less than 5 ms when the terminal application uses business data to run. Among them, there are many ways for the system to know whether the production center is faulty, for example: (1) order the disaster recovery center 2 to visit the production center 1 regularly, if it is found that the access is not available, the system will determine that the production center 1 is faulty; (2) order the production center 2 to visit the production center 1 regularly; Center 1 regularly reports monitoring heartbeat data to disaster recovery center 2. If disaster recovery center 2 does not receive the monitoring heartbeat data, the system determines that production center 1 is faulty.

In this embodiment, since the production center 1 supports the operation of terminal application services, when the disaster recovery center 2 is relatively close to the production center 1, the business data transmission between the disaster recovery center 2 and the terminal application supported by the production center 1 The distance is relatively short, so the end-to-end delay between the disaster recovery center 2 and the terminal application is relatively short, and when the disaster recovery center 2 is far from the production center 1, the disaster recovery center 2 and the production center 1 support the operation The service data transmission distance between the terminal applications is relatively long, which results in relatively long end-to-end delay between the disaster recovery center 2 and the terminal applications. That is, the closer the disaster recovery center 2 is to the production center 1, the shorter the end-to-end delay between the disaster recovery center 2 and the terminal applications supported by the production center 1 is. The disaster recovery management platform 3 analyzes the end-to-end delay between the disaster recovery center 2 and the terminal application according to the distance between the production center 1 and the disaster recovery center 2, and determines whether the end-to-end delay meets the requirements of production. The business performance requirements of Center 1, specifically:

In this embodiment, the end-to-end delay between the disaster recovery center 2 and the terminal application is required to be less than 5ms. Therefore, the disaster recovery management platform 3 analyzes the end-to-end delay between the terminal applications supported by the disaster recovery center 2 and the production center 1 according to the distance between the production center 1 and the disaster recovery center 2. For example, the distance between the production center 1 and the disaster recovery center 2 If the distance between backup center 2 is 4 kilometers, the end-to-end delay between disaster recovery center 2 and the terminal application supported by production center 1 is 4ms, and the distance between production center 1 and disaster recovery center 2 is 100 km, then the end-to-end delay between the disaster recovery center 2 and the terminal application supported by the production center 1 is 100ms (the correspondence between the distance and the end-to-end delay in this embodiment is only an exemplary example, The actual corresponding relationship will be changed according to the actual situation). After obtaining the end-to-end delay between the disaster recovery center 2 and the terminal application, determine whether the end-to-end delay is less than 5ms: if the end-to-end delay between the disaster recovery center 2 and the terminal application is less than 5ms, It means that the disaster recovery center 2 can meet the business performance requirements of the production center 1, that is, directly using the disaster recovery center 2 can support the operation of automatic driving business, industrial control business and telemedicine business, so the disaster recovery management platform 3 makes the disaster recovery center 2 Use the business data backed up to restore the business; if the end-to-end delay between the disaster recovery center 2 and the terminal application is not less than 5ms, it means that the disaster recovery center 2 cannot meet the business performance requirements of the production center 1, namely Direct use of the disaster recovery center 2 cannot support the operation of automatic driving services, industrial control services, and telemedicine services. Therefore, the service recovery node creation step a is performed to create a service recovery node on the MEC edge cloud node. The service recovery node creation step a includes the following Steps B and C.

B. Select the MEC edge cloud node that can meet the business performance requirements among multiple MEC edge cloud nodes.

In this embodiment, when the MEC edge cloud node is relatively close to the production center 1, the business data transmission distance between the MEC edge cloud node and the terminal application supported by the production center 1 is relatively short, so the MEC edge cloud node and the terminal The end-to-end delay between applications is relatively short, and when the MEC edge cloud node is far away from the production center 1, the business data transmission distance between the MEC edge cloud node and the terminal application supported by the production center 1 is relatively short. The end-to-end delay between the MEC edge cloud node and the terminal application is relatively long. That is, the closer the MEC edge cloud node is to the production center 1, the shorter the end-to-end delay between the MEC edge cloud node and the terminal application supported by the production center 1. Therefore, although the MEC edge cloud can shorten the network delay when transmitting business data with the terminal application in real time, it is not necessarily true that the two MEC

edge cloud nodes

5 and 6 can meet the business performance requirements of the production center 1. Therefore, when the disaster recovery management platform 3 judges that the disaster recovery center 2 cannot meet the business performance requirements of the production center 1, it sends the location information of the production center 1 to the MEC management platform 4 and sends a request for allocating MEC edge cloud nodes. Based on this, the management platform 4 obtains the location information of the first MEC edge cloud node 5 and the location information of the second MEC edge cloud node 6 that perform calculations in the local network where the production center 1 is located, and then calculates the location information of the production center 1 and the first MEC edge cloud node. The distance between the cloud nodes 5, the distance between the production center 1 and the second MEC edge cloud node 6, and then analyze the end-to-end between the first MEC edge cloud node 5 and the terminal application supported by the production center 1 Delay, the end-to-end delay between the second MEC edge cloud node 6 and the terminal application supported by the production center 1, and then judge the end-to-end time delay between the two MEC

edge cloud nodes

5 and 6 and the terminal application Whether the delay is less than 5ms. If the end-to-end delay is less than 5ms, it means that the corresponding MEC edge cloud node can meet the business performance requirements of production center 1. If the end-to-end delay is not less than 5ms, it means that the corresponding MEC edge cloud node If the business performance requirements of the production center 1 cannot be met, then the disaster recovery management platform 3 judges whether there is an MEC edge cloud node among the two MEC

edge cloud nodes

5 and 6 that can meet the business performance requirements. To meet the business performance requirements, the disaster recovery management platform 3 selects the MEC edge cloud node, for example:

In this embodiment, the distance between the production center 1 and the first MEC edge cloud node 5 is 4 kilometers, and the distance between the production center 1 and the second MEC edge cloud node 6 is 6 kilometers, and the MEC management platform 4 analyzes accordingly The end-to-end delay between the first MEC edge cloud node 5 and the terminal application supported by the production center 1 is 4ms, which is less than 5ms, and the end-to-end time delay between the second MEC edge cloud node 6 and the terminal application is analyzed. The delay is 6 ms, greater than 5 ms, that is, the first MEC edge cloud node 5 can meet the service performance requirements, but the second MEC edge cloud node 6 cannot meet the service performance requirements, so the disaster recovery management platform 3 selects the second MEC management platform 4 through the MEC management platform 4 A MEC edge cloud node 5;

In other embodiments, the distance between the production center 1 and the first MEC edge cloud node 5 is 4 kilometers, the distance between the production center 1 and the second MEC edge cloud node 6 is 3 kilometers, and the MEC management platform 4 is based on this It is analyzed that the end-to-end delay between the first MEC edge cloud node 5 and the terminal application supported by the production center 1 is 4ms, less than 5ms, and the end-to-end delay between the second MEC edge cloud node 6 and the terminal application 3ms, which is also less than 5ms, that is, both the first MEC edge cloud node 5 and the second MEC edge cloud node 6 can meet the service performance requirements, so the disaster recovery management platform 3 is connected to the two MEC edge cloud nodes through the MEC management platform 4 Select the one with the shortest end-to-end delay among 5 and 6, that is, select the one with the strongest service performance, so the disaster recovery management platform 3 selects the second MEC edge cloud node 6 through the MEC management platform 4 .

C. Create a service recovery node on the selected MEC edge cloud node.

Whether the disaster recovery management platform 3 selects the first MEC edge cloud node 5 or the second MEC edge cloud node 6, the disaster recovery management platform 3 will create a service recovery node 7 on the selected MEC edge cloud node. Taking the first MEC edge cloud node 5 selected in this embodiment as an example, as shown in FIG. 1 , the disaster recovery management platform 3 creates a service recovery node 7 on the selected first MEC edge cloud node 5 .

It should be noted that if no MEC edge cloud node among the two MEC edge cloud nodes 5 and 6 can meet the service performance requirements, the disaster recovery management platform 3 will not execute step a of creating the service recovery node, but execute the service recovery node instead Creation step b: The disaster recovery management platform 3 selects the one whose service performance is closest to the service performance requirement among the two MEC edge cloud nodes 5 and 6 through the MEC management platform 4, for example: the first MEC edge cloud node 5 and the terminal application The end-to-end delay between the second MEC edge cloud node 6 and the terminal application is 7ms, which is also greater than 5ms, that is, the first MEC edge cloud node 5 and the second MEC edge cloud node 5 and the second Among the MEC edge cloud nodes 6, there is no MEC edge cloud node that can meet the business performance requirements of the production center 1, so the disaster recovery management platform 3 selects the business performance closest to the two MEC edge cloud nodes 5 and 6 through the MEC management platform 4 One of the business performance requirements is that the disaster recovery management platform 3 selects the first MEC edge cloud node 5 through the MEC management platform 4, and then creates a service recovery node 7 on the first MEC edge cloud node 5.

D. Make the disaster recovery center 2 that has backed up the data of the production center 1 send the backup data and the backup system to the service recovery node 7, so that the service recovery node 7 can use the backup data to perform business recovery and start the backup system.

After the business recovery node 7 is created on the first MEC edge cloud node 5 that can meet the business performance requirements of the production center 1, the disaster recovery management platform 3 instructs the disaster recovery center 2 to send the backed up business data and backup system to the first On the business recovery node 7 of the MEC edge cloud node 5, the business recovery node 7 uses the backup business data to restore the automatic driving business, industrial control business and telemedicine business of the production center 1, and starts the backup system to restore the business center 1. The backup of business data, in this way, can quickly establish a business recovery node 7 that meets the business performance requirements based on the MEC edge cloud node, so as to ensure the continuity and service quality of autonomous driving business, industrial control business, telemedicine business and other business.

The above-described embodiment of the service recovery system based on the MEC edge cloud is only illustrative, where the system modules may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may Located in one place, or can be distributed to several network modules. Part or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. It can be understood and implemented by those skilled in the art without any creative efforts.

Through the specific description of the above embodiments, those skilled in the art can clearly understand that each implementation manner can be implemented by means of software plus a necessary general-purpose hardware platform, and of course also by hardware. Based on this understanding, the above-mentioned technical solution essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, and the storage medium includes a read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), programmable read-only memory (Programmable Read-only Memory, PROM), erasable programmable read-only memory (Erasable Programmable Read Only Memory, EPROM ), One-time Programmable Read-Only Memory (OTPROM), Electronically Erasable Programmable Read-Only Memory (EEPROM), Compact Disc Read -Only Memory, CD-ROM) or other optical disk storage, magnetic disk storage, tape storage, or any other computer-readable medium that can be used to carry or store data.

Finally, it should be noted that: the MEC edge cloud-based service recovery system disclosed in the embodiment of the present invention is only a preferred embodiment of the present invention, and is only used to illustrate the technical solution of the present invention, not to limit it; although The present invention has been described in detail with reference to the aforementioned embodiments, and those skilled in the art should understand that it can still modify the technical solutions described in the aforementioned embodiments, or perform equivalent replacements for some of the technical features; and these The modification or replacement does not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the various embodiments of the present invention.

Claims

A service recovery system based on MEC edge cloud, characterized by:

Including production center, disaster recovery center, disaster recovery management platform, MEC management platform and multiple MEC edge cloud nodes;

The production center supports the operation and maintenance of terminal application services, and sends data backup to the disaster recovery center, and the production center uploads business performance requirements to the disaster recovery management platform;

The MEC management platform performs unified management and scheduling on multiple MEC edge cloud nodes;

After the disaster recovery management platform obtains the business performance requirements of the production center, it executes the business recovery node creation step a: selects the MEC edge cloud node that can meet the business performance requirements from among the multiple MEC edge cloud nodes through the MEC management platform , create a service recovery node on the selected MEC edge cloud node;

After the disaster recovery management platform creates the business recovery node, it instructs the disaster recovery center to send the backup data and the backup system to the business recovery node;

After the service restoration node receives the backup data and the backup system, it uses the backup data to restore the service and starts the backup system.
The business recovery system based on MEC edge cloud according to claim 1, wherein the disaster recovery management platform judges whether the disaster recovery center can meet the business performance requirements after obtaining the business performance requirements of the production center, If it is satisfied, the step a of creating the service recovery node is not executed, but the disaster recovery center is ordered to perform service recovery instead.
The service recovery system based on MEC edge cloud according to claim 1, wherein the service performance requirements include requirements on delay and/or bandwidth for terminal applications to access service systems.
The service recovery system based on MEC edge cloud according to claim 1, characterized in that, in step a of creating the service recovery node, if there are multiple MEC edge cloud nodes that can meet the service performance requirements, disaster recovery The management platform selects the one with the strongest service performance among the multiple MEC edge cloud nodes through the MEC management platform, and creates a service recovery node on the selected MEC edge cloud node.
The business recovery system based on MEC edge cloud according to claim 1, wherein after the disaster recovery management platform obtains the business performance requirements of the production center, if there is no MEC edge cloud node that can meet the business performance requirements , the disaster recovery management platform does not execute the business recovery node creation step a, but executes the business recovery node creation step b: select the business performance closest to the business performance requirements from the multiple MEC edge cloud nodes through the MEC management platform One, create a service recovery node on the selected MEC edge cloud node.
The service recovery system based on MEC edge cloud according to claim 4 or 5, wherein the MEC management platform judges whether each MEC edge cloud node is The service performance requirement can be met. Specifically, the closer the distance between the MEC edge cloud node and the production center is, the closer the service performance of the MEC edge cloud node is to the service performance requirement.
The service restoration system based on MEC edge cloud according to claim 1, wherein the production center supports the operation of automatic driving service, industrial control service and/or telemedicine service.
The service recovery system based on MEC edge cloud according to claim 1 or 7, characterized in that there are multiple disaster recovery centers.
The service recovery system based on MEC edge cloud according to claim 8, wherein the disaster recovery center is an intra-city disaster recovery center or a remote disaster recovery center.
A kind of service recovery method based on MEC edge cloud, it is characterized in that, comprises the steps:

A. Obtain the business performance requirements of the production center;

B. Select an MEC edge cloud node that can meet the business performance requirements among multiple MEC edge cloud nodes;

C. Create a service recovery node on the selected MEC edge cloud node;

D. Make the disaster recovery center that has backed up the data of the production center send the backup data and the backup system to the service recovery node, so that the service recovery node can use the backup data to perform service recovery and start the backup system.
According to the MEC edge cloud-based service recovery method according to claim 10, it is characterized in that, after obtaining the service performance requirements of the production center in the step A, it is judged whether the disaster recovery center can satisfy the service If the performance requirements can be met, the above-mentioned steps B, C, and D are not executed, but the disaster recovery center is ordered to perform business recovery instead.
The method for service recovery based on MEC edge cloud according to claim 10, wherein the service performance requirements include requirements on delay and/or bandwidth for terminal applications to access service systems.
The service recovery method based on MEC edge cloud according to claim 10, wherein said step B comprises:

B1. Obtain multiple MEC edge cloud nodes;

B2. Determine whether there is an MEC edge cloud node that can meet the service performance requirements, and if there is a MEC edge cloud node that can meet the service performance requirements, select the MEC edge cloud node.
According to the MEC edge cloud-based service recovery method according to claim 13, it is characterized in that, in said step B2, if it is judged that there are multiple MEC edge cloud nodes that can meet the service performance requirements, then among these multiple Select the one with the strongest service performance among the MEC edge cloud nodes.
The method for recovering business based on MEC edge cloud according to claim 13, wherein in said step B2, if it is judged that no MEC edge cloud node can meet the service performance requirements, then at multiple MEC edge cloud nodes Select the one whose service performance is closest to the service performance requirement.
According to the MEC edge cloud-based business recovery method according to any one of claims 13 to 15, it is characterized in that, in the step B2, according to the distance between each MEC edge cloud node and the production center, it is judged that each MEC Whether the edge cloud node can meet the business performance requirements, specifically, the closer the distance between the MEC edge cloud node and the production center, the more the business performance of the MEC edge cloud node can meet the business performance Require.
A computer-readable storage medium on which is stored a computer program of a disaster recovery management platform, wherein when the computer program is executed by a processor, the steps in the business recovery method according to any one of claims 10 to 12 are realized , wherein, the step B is executed through the MEC management platform.