CN114070851A - Service recovery method, storage medium and system based on MEC edge cloud - Google Patents
Service recovery method, storage medium and system based on MEC edge cloud Download PDFInfo
- Publication number
- CN114070851A CN114070851A CN202111350289.6A CN202111350289A CN114070851A CN 114070851 A CN114070851 A CN 114070851A CN 202111350289 A CN202111350289 A CN 202111350289A CN 114070851 A CN114070851 A CN 114070851A
- Authority
- CN
- China
- Prior art keywords
- service
- edge cloud
- mec
- node
- mec edge
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000011084 recovery Methods 0.000 title claims abstract description 127
- 238000000034 method Methods 0.000 title claims abstract description 25
- 238000003860 storage Methods 0.000 title claims abstract description 10
- 238000004590 computer program Methods 0.000 claims description 6
- 238000012423 maintenance Methods 0.000 claims description 2
- 230000015654 memory Effects 0.000 description 8
- 230000005540 biological transmission Effects 0.000 description 6
- 238000004891 communication Methods 0.000 description 4
- 238000012544 monitoring process Methods 0.000 description 2
- 230000010076 replication Effects 0.000 description 2
- 238000004904 shortening Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Hardware Redundancy (AREA)
Abstract
The invention provides a service recovery method, a storage medium and a system based on an MEC edge cloud, wherein the method comprises the following steps: the method comprises the steps of obtaining a service performance requirement of a production center, selecting an MEC edge cloud node which can meet the service performance requirement from a plurality of MEC edge cloud nodes, creating a service recovery node on the selected MEC edge cloud node, and enabling a disaster recovery center which performs data backup on the production center to send backup data and a backup system to the service recovery node so that the service recovery node performs service recovery by using the backup data and starts the backup system.
Description
Technical Field
The invention relates to the technical field of cloud computing, in particular to a business recovery method, a storage medium and a system based on MEC edge cloud.
Background
The traditional wireless communication disaster recovery scheme generally adopts a two-place-three-center scheme (a production center, a city-sharing disaster recovery center and a remote disaster recovery center), the production center is provided with a service system to support and run terminal application services, under daily conditions, the city-sharing disaster recovery center and the remote disaster recovery center are respectively in communication connection with the production center through high-speed links, and then service data of the production center is backed up in a synchronous replication/asynchronous replication mode. When a disaster occurs in the production center, the service data may be lost, so that the service cannot be continuously operated.
With the development of a 5G network, a service system of a production center supports and operates a plurality of low-delay terminal application services with high requirements on ultra-low delay and ultra-large bandwidth, such as automatic driving, industrial control, remote medical treatment and the like, the end-to-end delay is generally required to be less than 5ms when the low-delay terminal application operates, and the same disaster recovery center and a different disaster recovery center are generally away from the production center by tens of kilometers or even hundreds of kilometers, so that the end-to-end delay between the disaster recovery center and the terminal application is greater than 100ms after emergency switching of the disaster recovery, and therefore, after the emergency switching of the disaster recovery, the disaster recovery center cannot meet the service performance requirements of the low-delay terminal application.
Disclosure of Invention
The invention aims to solve the technical problem of how to quickly establish a service recovery node meeting the service performance requirement based on an MEC edge cloud node when a disaster recovery center cannot meet the service performance requirement so as to ensure the continuity and the service quality of a service.
The inventor finds that an MEC (Multi-access Edge Computing) Edge cloud is a cloud resource pool and a cloud platform which are deployed at the Edge side of a network close to a production center, is widely distributed and close to the production center, and operates in a local network where the production center is located, so that the waiting time and the network cost of data to and from terminal applications are reduced, and the congestion and the burden of an operator core network and a transmission network are greatly reduced, thereby greatly shortening the network delay between a service recovery node and the terminal applications, and reducing the bandwidth pressure of the service recovery node and the terminal applications. Accordingly, the inventors provide the following technical solutions to solve the above technical problems:
the invention provides a business recovery system based on an MEC edge cloud, which comprises a production center, a disaster recovery management platform, an MEC management platform and a plurality of MEC edge cloud nodes, wherein the disaster recovery center is connected with the MEC edge cloud nodes; the production center supports the operation and maintenance of the terminal application service and sends data backup to the disaster backup center, and the production center uploads the service performance requirement to the disaster backup management platform; the MEC management platform performs unified management and scheduling on a plurality of MEC edge cloud nodes; after the disaster recovery management platform acquires the service performance requirement of the production center, the disaster recovery management platform executes a service recovery node creating step a: selecting an MEC edge cloud node capable of meeting the service performance requirement from a plurality of MEC edge cloud nodes through an MEC management platform, and creating a service recovery node on the selected MEC edge cloud node; after the disaster recovery management platform creates a service recovery node, the disaster recovery management platform enables a disaster recovery center to send backup data and a backup system to the service recovery node; and after receiving the backup data and the backup system, the service recovery node performs service recovery by using the backup data and starts the backup system.
Preferably, after acquiring the service performance requirement of the production center, the disaster recovery management platform determines whether the disaster recovery center can meet the service performance requirement, and if so, does not execute the service recovery node creating step a and instead causes the disaster recovery center to perform service recovery.
Preferably, the service performance requirement includes a requirement for a delay and/or a bandwidth of the terminal application to access the service system.
Preferably, in the service recovery node creating step a, if there are a plurality of MEC edge cloud nodes that can meet the service performance requirement, the disaster recovery management platform selects one of the plurality of MEC edge cloud nodes with the strongest service performance through the MEC management platform, and creates a service recovery node on the selected MEC edge cloud node.
Preferably, after the disaster recovery management platform obtains the service performance requirement of the production center, if no MEC edge cloud node can meet the service performance requirement, the disaster recovery management platform does not execute the service recovery node creating step a, but executes the service recovery node creating step b: and selecting one of the MEC edge cloud nodes with the service performance closest to the service performance requirement through the MEC management platform, and creating a service recovery node on the selected MEC edge cloud node.
Preferably, the MEC management platform determines whether each MEC edge cloud node can meet the service performance requirement according to a distance between each MEC edge cloud node and the production center, and 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.
Preferably, the production center supports the operation of an automated driving service, an industrial control service and/or a telemedicine service.
Preferably, there are a plurality of disaster recovery centers.
Preferably, the disaster recovery center is the same city disaster recovery center or a different place disaster recovery center.
The invention also provides a business recovery method based on the MEC edge cloud, which comprises the following steps:
A. acquiring the service performance requirement of a production center;
B. selecting an MEC edge cloud node capable of meeting the service performance requirement from a plurality of MEC edge cloud nodes;
C. creating a service recovery node on the selected MEC edge cloud node;
D. and the disaster backup center which performs data backup on the production center sends the backup data and the backup system to the service recovery node, so that the service recovery node performs service recovery by using the backup data and starts the backup system.
Preferably, after the service performance requirement of the production center is obtained in the step a, it is determined whether the disaster recovery center can meet the service performance requirement, and if so, the step B, C, D is not executed and the disaster recovery center is enabled instead.
Preferably, the service performance requirement includes a requirement for a delay and/or a bandwidth of the terminal application to access the service system.
Preferably, the step B includes:
B1. acquiring a plurality of MEC edge cloud nodes;
B2. and judging whether an MEC edge cloud node can meet the service performance requirement, and if the MEC edge cloud node can meet the service performance requirement, selecting the MEC edge cloud node.
Preferably, in the step B2, if it is determined that there are a plurality of MEC edge cloud nodes that can meet the service performance requirement, one with the strongest service performance is selected from the plurality of 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, one of the plurality of MEC edge cloud nodes having the service performance closest to the service performance requirement is selected.
Preferably, in the step B2, it is determined whether each MEC edge cloud node can meet the service performance requirement according to a distance between each MEC edge cloud node and the production center, and specifically, the closer the distance between each MEC edge cloud node and the production center is, the more the service performance of the MEC edge cloud node can meet the service performance requirement.
The present invention also provides a computer-readable storage medium, on which a computer program of a disaster recovery management platform is stored, where the computer program, when executed by a processor, implements the steps in the service recovery method as described above, where the step B is executed by an MEC management platform.
The invention has the following beneficial effects: the MEC edge cloud nodes can greatly shorten the network time delay between the service recovery nodes and the terminal application and reduce the bandwidth pressure, so that under the condition that a production center fails, the disaster recovery management platform acquires the service performance requirement of the production center, then selects an MEC edge cloud node which can meet the service performance requirement from a plurality of MEC edge cloud nodes, creates a service recovery node on the MEC edge cloud node which can meet the service performance requirement, and then enables the disaster recovery center to send backup data and a backup system to the service recovery node, the service recovery node performs service recovery by using the backup data and starts the backup system, and thus the service recovery nodes which meet the service performance requirement are quickly established based on the MEC edge cloud nodes, and the continuity and the service quality of the service are ensured.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic structural diagram of an embodiment of a service restoration system based on an MEC edge cloud in the present invention;
fig. 2 is a schematic flowchart of an embodiment of a service restoration method based on an MEC edge cloud in the present invention.
Detailed Description
In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, 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 invention.
In the present invention, the term "comprises" and any variation thereof is intended to cover a non-exclusive inclusion. For example, a process, method, apparatus, product, or apparatus that comprises a list of steps or elements is not limited to those listed but may alternatively include other steps or elements not listed or inherent to such process, method, product, or apparatus.
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 invention. The appearances of the 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 explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
As shown in fig. 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 a plurality of MEC edge cloud nodes, where the plurality of MEC edge cloud nodes includes a first MEC edge cloud node 5 and a second MEC edge cloud node 6. The production center 1 is provided with a service system 8 to support running terminal application services such as an automatic driving service, an industrial control service, and a telemedicine service. The disaster recovery center 2 is a city disaster recovery center or a remote disaster recovery center, and is deployed with a service backup system for backing up service data of the production center 1 and recovering services, and in other embodiments, there may be a plurality of disaster recovery centers 2. The MEC edge cloud nodes 5 and 6 are cloud resource pools and cloud platforms deployed on the network edge side close to the production center 1, are widely distributed and close to the production center 1, perform operation in a local network where the production center 1 is located, reduce the waiting time and network cost of data to and from the terminal application, and greatly reduce congestion and burden on an operator core network and a transmission network, thereby greatly shortening network delay and bandwidth pressure when service data is transmitted to the terminal application.
The disaster recovery backup management platform 3 is respectively in communication connection with the production center 1, the disaster recovery backup center 2 and the MEC management platform 4, the MEC management platform 4 manages two MEC edge cloud nodes 5 and 6, and the production center 1 is in communication connection with the disaster recovery backup center 2. The disaster recovery management platform 3 includes a computer-readable storage medium and a processor connected to each other, where a computer program of the disaster recovery management platform 3 is stored on the computer-readable storage medium, and when the computer program is executed by the processor, the method implements the MEC edge cloud based service restoration method shown in fig. 2, where the method includes the following step A, B, C, D.
A. And acquiring the service performance requirement of the production center 1.
The production center 1 synchronously or asynchronously transmits service data to the disaster recovery center 2 for backup in the process of supporting and operating the automatic driving service, the industrial control service and the remote medical service. Because the automatic driving service, the industrial control service and the telemedicine service are low-delay terminal application services with high requirements on ultra-low delay and ultra-large bandwidth, the service performance requirements of the production center 1 include that the end-to-end delay of the terminal application is less than 5ms when the terminal application runs by using service data. When the terminal application service is operated, the production center 1 uploads service importance information containing service performance requirements to the disaster recovery management platform 3, that is, before the disaster recovery management platform 3 fails to operate continuously due to a failure of the production center 1, the service performance requirements of the production center 1 can be obtained according to the service importance information, and the end-to-end time delay when the terminal application operates by using the service data is less than 5 ms. There are various ways for the system to know whether the production center has a fault, for example: (1) the disaster recovery center 2 is made to regularly visit the production center 1, and if the disaster recovery center cannot visit the production center, the system judges that the production center 1 has a fault; (2) the production center 1 is enabled to report the monitoring heartbeat data to the disaster recovery center 2 periodically, and if the disaster recovery center 2 does not receive the monitoring heartbeat data, the system judges that the production center 1 has a fault.
In this embodiment, since the production center 1 supports and operates the terminal application service, under the condition that the disaster preparation center 2 is closer to the production center 1, the service data transmission distance between the disaster preparation center 2 and the terminal application supported and operated by the production center 1 is closer, so the end-to-end time delay between the disaster preparation center 2 and the terminal application is shorter, and under the condition that the disaster preparation center 2 is farther from the production center 1, the service data transmission distance between the disaster preparation center 2 and the terminal application supported and operated by the production center 1 is farther, so the end-to-end time delay between the disaster preparation center 2 and the terminal application is longer. That is, the closer the disaster recovery center 2 is to the production center 1, the shorter the end-to-end time delay between the disaster recovery center 2 and the terminal application supported by the production center 1. The disaster recovery management platform 3 analyzes the end-to-end time 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 accordingly determines whether the end-to-end time delay meets the service performance requirement of the production 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 5 ms. The disaster recovery management platform 3 analyzes the end-to-end time delay between the disaster recovery center 2 and the terminal application supported and operated by the production center 1 according to the distance between the production center 1 and the disaster recovery center 2, for example, if the distance between the production center 1 and the disaster recovery center 2 is 4 km, the end-to-end time delay between the disaster recovery center 2 and the terminal application supported and operated by the production center 1 is 4ms, and the distance between the production center 1 and the disaster recovery center 2 is 100 km, the end-to-end time delay between the disaster recovery center 2 and the terminal application supported and operated by the production center 1 is 100ms (the correspondence between the distance and the end-to-end time delay in this embodiment is merely an exemplary example, and the actual correspondence may be changed according to actual situations). After the end-to-end delay between the disaster recovery center 2 and the terminal application is obtained, whether the end-to-end delay is less than 5ms is judged: if the end-to-end time 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 service performance requirement of the production center 1, i.e. the disaster recovery center 2 can be directly utilized to support the operation of the automatic driving service, the industrial control service and the remote medical service, so the disaster recovery management platform 3 enables the disaster recovery center 2 to utilize the backup service data to perform service recovery; if the end-to-end time 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 service performance requirement of the production center 1, that is, the disaster recovery center 2 cannot support and run the automatic driving service, the industrial control service and the remote medical service, so that the service recovery node creating step a is executed to create a service recovery node on the MEC edge cloud node, and the service recovery node creating step a includes the following step B, C.
B. And selecting an MEC edge cloud node which can meet the service performance requirement from the plurality of MEC edge cloud nodes.
In this embodiment, under the condition that the MEC edge cloud node is closer to the production center 1, the service data transmission distance between the MEC edge cloud node and the terminal application supported and operated by the production center 1 is closer, so the end-to-end time delay between the MEC edge cloud node and the terminal application is shorter, and under the condition that the MEC edge cloud node is farther from the production center 1, the service data transmission distance between the MEC edge cloud node and the terminal application supported and operated by the production center 1 is farther, so the end-to-end time delay between the MEC edge cloud node and the terminal application is longer. That is, the closer the MEC edge cloud node is to the production center 1, the shorter the end-to-end time delay between the MEC edge cloud node and the terminal application supported and operated by the production center 1 is. Therefore, although the MEC edge cloud can shorten the network delay when transmitting the service data in real time with the terminal application, it is not always necessary that both MEC edge cloud nodes 5 and 6 can meet the service performance requirement of the production center 1. The disaster recovery backup management platform 3 sends location information of the production center 1 and a request for applying allocation of an MEC edge cloud node to the MEC management platform 4 when judging that the disaster recovery backup center 2 cannot meet the service performance requirement of the production center 1, the MEC management platform 4 obtains the location information of a first MEC edge cloud node 5 and the location information of a second MEC edge cloud node 6 which are operated in a local network where the production center 1 is located according to the location information, then calculates the distance between the production center 1 and the first MEC edge cloud node 5 and the distance between the production center 1 and the second MEC edge cloud node 6, analyzes the end-to-end time delay between the first MEC edge cloud node 5 and a terminal application supported and operated by the production center 1 and the end-to-end time delay between the second MEC edge cloud node 6 and the terminal application supported and operated by the production center 1 according to the location information, and judges the two MEC edge cloud nodes 5, 5 and the second MEC edge cloud node 6, Whether the end-to-end delay between 6 and the terminal application is less than 5ms or not, if the end-to-end delay is less than 5ms, it means that the corresponding MEC edge cloud node can meet the service performance requirement of the production center 1, if the end-to-end delay is not less than 5ms, it means that the corresponding MEC edge cloud node cannot meet the service performance requirement of the production center 1, then the disaster recovery management platform 3 judges whether there is an MEC edge cloud node in the two MEC edge cloud nodes 5 and 6 that can meet the service performance requirement, if there is an MEC edge cloud node that can meet the service performance requirement, 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, 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 that the end-to-end delay between the first MEC edge cloud node 5 and the terminal application supported and operated by the production center 1 is 4ms and less than 5ms, and analyzes that the end-to-end delay between the second MEC edge cloud node 6 and the terminal application is 6ms and more than 5ms, that is, the first MEC edge cloud node 5 can meet the service performance requirement, and the second MEC edge cloud node 6 cannot meet the service performance requirement, so the disaster recovery management platform 3 selects the first MEC edge cloud node 5 through the MEC management platform 4;
in other embodiments, the distance between the production center 1 and the first MEC edge cloud node 5 is 4 km, the distance between the production center 1 and the second MEC edge cloud node 6 is 3 km, the MEC management platform 4 analyzes that the end-to-end delay between the first MEC edge cloud node 5 and the terminal application supported and operated by the production center 1 is 4ms and less than 5ms, the end-to-end delay between the second MEC edge cloud node 6 and the terminal application is 3ms and less than 5ms, namely, the first MEC edge cloud node 5 and the second MEC edge cloud node 6 can both meet the service performance requirement, so the disaster recovery backup management platform 3 selects one of the two MEC edge cloud nodes 5 and 6 with the shortest end-to-end time delay through the MEC management platform 4, namely, the service performance is the strongest one, so the disaster recovery management platform 3 selects the second MEC edge cloud node 6 through the MEC management platform 4.
C. And creating a service recovery node on the selected MEC edge cloud node.
No matter 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 creates 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, referring to fig. 1, the disaster recovery management platform 3 creates a service restoration node 7 on the selected first MEC edge cloud node 5.
It should be noted that, if none of the two MEC edge cloud nodes 5 and 6 can meet the service performance requirement, the disaster recovery management platform 3 does not execute the service recovery node creating step a, but executes the service recovery node creating step b: the disaster recovery management platform 3 selects one of the two MEC edge cloud nodes 5 and 6 with service performance closest to the service performance requirement through the MEC management platform 4, for example: an end-to-end delay between the first MEC edge cloud node 5 and the terminal application is 6ms and more than 5ms, an end-to-end delay between the second MEC edge cloud node 6 and the terminal application is 7ms and more than 5ms, that is, no MEC edge cloud node in the first MEC edge cloud node 5 and the second MEC edge cloud node 6 can meet the service performance requirement of the production center 1, so that the disaster recovery management platform 3 selects one of the two MEC edge cloud nodes 5 and 6, of which the service performance is closest to the service performance requirement through the MEC management platform 4, that is, the disaster recovery management platform 3 selects the first MEC edge cloud node 5 through the MEC management platform 4, and then creates the service recovery node 7 on the first MEC edge cloud node 5.
D. And the disaster recovery center 2 which carries out data backup on the production center 1 sends the backup data and the backup system to the service recovery node 7, so that the service recovery node 7 carries out service recovery by using the backup data and starts the backup system.
After a service recovery node 7 is created on a first MEC edge cloud node 5 which can meet the service performance requirement of a production center 1, a disaster recovery management platform 3 enables a disaster recovery center 2 to send backup service data and a backup system to the service recovery node 7 of the first MEC edge cloud node 5, the service recovery node 7 performs service recovery on an automatic driving service, an industrial control service and a remote medical service of the production center 1 by using the backup service data, and starts the backup system to perform service data backup on the service center 1, so that the service recovery node 7 which meets the service performance requirement is quickly established based on the MEC edge cloud node, and the continuity and the service quality of the services such as the automatic driving service, the industrial control service and the remote medical service are ensured.
The embodiment of the business recovery system based on the MEC edge cloud described above is only illustrative, wherein the system modules may or may not be physically separated, and the components displayed as the modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Through the above detailed description of the embodiments, those skilled in the art will clearly understand that the embodiments may be implemented by software plus a necessary general hardware platform, and may also be implemented by hardware. Based on such understanding, the above technical solutions may be embodied in the form of a software product, which may be stored in a computer-readable storage medium, where the storage medium includes a Read-Only Memory (ROM), a Random Access Memory (RAM), a Programmable Read-Only Memory (PROM), an Erasable Programmable Read-Only Memory (EPROM), a One-time Programmable Read-Only Memory (OTPROM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc-Read-Only Memory (CD-ROM), or other disk memories, CD-ROMs, or other magnetic disks, A tape memory, or any other medium readable by a computer that can be used to carry or store data.
Finally, it should be noted that: the embodiment of the present invention discloses a service recovery system based on MEC edge cloud, which is only a preferred embodiment of the present invention, and is only used for illustrating the technical solution of the present invention, not limiting the same; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those skilled in the art; the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims (17)
1. A business recovery system based on MEC edge cloud is characterized in that:
the system comprises a production center, a disaster backup management platform, an MEC management platform and a plurality of MEC edge cloud nodes;
the production center supports the operation and maintenance of the terminal application service and sends data backup to the disaster backup center, and the production center uploads the service performance requirement to the disaster backup management platform;
the MEC management platform performs unified management and scheduling on a plurality of MEC edge cloud nodes;
after the disaster recovery management platform acquires the service performance requirement of the production center, the disaster recovery management platform executes a service recovery node creating step a: selecting an MEC edge cloud node capable of meeting the service performance requirement from a plurality of MEC edge cloud nodes through an MEC management platform, and creating a service recovery node on the selected MEC edge cloud node;
after the disaster recovery management platform creates a service recovery node, the disaster recovery management platform enables a disaster recovery center to send backup data and a backup system to the service recovery node;
and after receiving the backup data and the backup system, the service recovery node performs service recovery by using the backup data and starts the backup system.
2. The service restoration system based on the MEC edge cloud according to claim 1, wherein the disaster recovery management platform determines whether the disaster recovery center can meet the service performance requirement after acquiring the service performance requirement of the production center, and if so, the disaster recovery management platform does not execute the service restoration node creating step a and instead causes the disaster recovery center to perform service restoration.
3. The MEC edge cloud based service restoration system according to claim 1, wherein the service performance requirements include a delay and/or bandwidth requirement for a terminal application to access the service system.
4. The service restoration system according to claim 1, wherein in the service restoration node creating step a, if there are a plurality of MEC edge cloud nodes that can meet the service performance requirement, the disaster recovery management platform selects one of the plurality of MEC edge cloud nodes with the strongest service performance through the MEC management platform, and creates a service restoration node on the selected MEC edge cloud node.
5. The service restoration system based on the MEC edge cloud according to claim 1, wherein after the disaster recovery management platform obtains the service performance requirement of the production center, if no MEC edge cloud node can meet the service performance requirement, the disaster recovery management platform does not perform the service restoration node creating step a, but performs the service restoration node creating step b: and selecting one of the MEC edge cloud nodes with the service performance closest to the service performance requirement through the MEC management platform, and creating a service recovery node on the selected MEC edge cloud node.
6. The service recovery system based on the MEC edge cloud according to claim 4 or 5, wherein the MEC management platform determines whether each MEC edge cloud node can meet the service performance requirement according to a distance between each MEC edge cloud node and the production center, and 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.
7. The MEC edge cloud based service restoration system according to claim 1, wherein the production center support runs an automated driving service, an industrial control service and/or a telemedicine service.
8. The MEC edge cloud based business recovery system according to claim 1 or 7, wherein there are a plurality of disaster recovery centers.
9. The MEC edge cloud based business recovery system of claim 8, wherein the disaster recovery center is a same city disaster recovery center or a different location disaster recovery center.
10. A service recovery method based on MEC edge cloud is characterized by comprising the following steps:
A. acquiring the service performance requirement of a production center;
B. selecting an MEC edge cloud node capable of meeting the service performance requirement from a plurality of MEC edge cloud nodes;
C. creating a service recovery node on the selected MEC edge cloud node;
D. and the disaster backup center which performs data backup on the production center sends the backup data and the backup system to the service recovery node, so that the service recovery node performs service recovery by using the backup data and starts the backup system.
11. The method for recovering a service based on an MEC edge cloud according to claim 10, wherein after the service performance requirement of the production center is obtained in the step a, it is determined whether the disaster recovery center can meet the service performance requirement, and if so, the step B, C, D is not executed, and instead, the disaster recovery center is made to perform service recovery.
12. The method for business recovery based on MEC edge cloud of claim 10, wherein the business performance requirements include a requirement on a delay and/or a bandwidth of a terminal application accessing the business system.
13. The MEC edge cloud based traffic restoration method according to claim 10, wherein the step B comprises:
B1. acquiring a plurality of MEC edge cloud nodes;
B2. and judging whether an MEC edge cloud node can meet the service performance requirement, and if the MEC edge cloud node can meet the service performance requirement, selecting the MEC edge cloud node.
14. The method for restoring a service based on MEC edge clouds according to claim 13, wherein in step B2, if it is determined that there are a plurality of MEC edge cloud nodes satisfying the service performance requirement, then one of the plurality of MEC edge cloud nodes with the strongest service performance is selected.
15. The method for restoring services based on MEC edge clouds according to claim 13, wherein in step B2, if it is determined that no MEC edge cloud node can meet the service performance requirement, one of the plurality of MEC edge cloud nodes with the service performance closest to the service performance requirement is selected.
16. The method for restoring service based on MEC edge cloud according to any one of claims 13 to 15, wherein in step B2, it is determined whether each MEC edge cloud node can meet the service performance requirement according to a distance between each MEC edge cloud node and the production center, and specifically, the closer the distance between the MEC edge cloud node and the production center, the more the service performance of the MEC edge cloud node can meet the service performance requirement.
17. Computer readable storage medium, on which a computer program of a disaster recovery management platform is stored, wherein said computer program, when being executed by a processor, implements the steps in the service restoration method according to any of the claims 10 to 12, wherein said step B is performed by an MEC management platform.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111350289.6A CN114070851A (en) | 2021-11-15 | 2021-11-15 | Service recovery method, storage medium and system based on MEC edge cloud |
| PCT/CN2022/113470 WO2023082749A1 (en) | 2021-11-15 | 2022-08-19 | Service recovery method and system based on mec edge cloud, and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111350289.6A CN114070851A (en) | 2021-11-15 | 2021-11-15 | Service recovery method, storage medium and system based on MEC edge cloud |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114070851A true CN114070851A (en) | 2022-02-18 |
Family
ID=80272246
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111350289.6A Pending CN114070851A (en) | 2021-11-15 | 2021-11-15 | Service recovery method, storage medium and system based on MEC edge cloud |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN114070851A (en) |
| WO (1) | WO2023082749A1 (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114520811A (en) * | 2022-04-20 | 2022-05-20 | 柏科数据技术（深圳）股份有限公司 | Production center data recovery method, system, terminal equipment and storage medium |
| WO2023082749A1 (en) * | 2021-11-15 | 2023-05-19 | 中电信数智科技有限公司 | Service recovery method and system based on mec edge cloud, and storage medium |
| WO2023109062A1 (en) * | 2021-12-14 | 2023-06-22 | 中电信数智科技有限公司 | Cloud disaster recovery system and method, electronic device, and storage medium |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116521452B (en) * | 2023-06-30 | 2023-09-22 | 建信金融科技有限责任公司 | Disaster recovery system and business processing method based on disaster recovery system |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110572448A (en) * | 2019-08-30 | 2019-12-13 | 烽火通信科技股份有限公司 | distributed edge cloud system architecture |
| CN110769039A (en) * | 2019-10-09 | 2020-02-07 | 腾讯科技（深圳）有限公司 | Resource scheduling method and device, electronic equipment and computer readable storage medium |
| CN111612933A (en) * | 2020-05-18 | 2020-09-01 | 上海齐网网络科技有限公司 | Augmented reality intelligent inspection system based on edge cloud server |
| CN111800282A (en) * | 2019-04-08 | 2020-10-20 | 阿里巴巴集团控股有限公司 | Network system, instance management and control method, device and storage medium |
| CN111800285A (en) * | 2019-04-08 | 2020-10-20 | 阿里巴巴集团控股有限公司 | Instance migration method and device and electronic equipment |
| US20210144515A1 (en) * | 2019-11-12 | 2021-05-13 | Verizon Patent And Licensing Inc. | Systems and methods for multi-access edge computing node selection |
| CN113190378A (en) * | 2020-12-31 | 2021-07-30 | 华数云科技有限公司 | Edge cloud disaster recovery method based on distributed cloud platform |
| CN113190347A (en) * | 2021-04-21 | 2021-07-30 | 武汉卓尔信息科技有限公司 | Edge cloud system and task management method |
| CN113259260A (en) * | 2020-02-11 | 2021-08-13 | 华为技术有限公司 | Method and device for deploying application instance and scheduling application instance |
| CN113572821A (en) * | 2021-07-05 | 2021-10-29 | 山东师范大学 | Edge cloud node task cooperative processing method and system |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10728138B2 (en) * | 2018-12-21 | 2020-07-28 | At&T Intellectual Property I, L.P. | Analytics enabled radio access network (RAN)- aware content optimization using mobile edge computing |
| CN113301078B (en) * | 2020-05-22 | 2022-05-06 | 阿里巴巴集团控股有限公司 | Network system, service deployment and network division method, device and storage medium |
| CN114070851A (en) * | 2021-11-15 | 2022-02-18 | 中国电信集团系统集成有限责任公司 | Service recovery method, storage medium and system based on MEC edge cloud |
-
2021
- 2021-11-15 CN CN202111350289.6A patent/CN114070851A/en active Pending
-
2022
- 2022-08-19 WO PCT/CN2022/113470 patent/WO2023082749A1/en unknown
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111800282A (en) * | 2019-04-08 | 2020-10-20 | 阿里巴巴集团控股有限公司 | Network system, instance management and control method, device and storage medium |
| CN111800285A (en) * | 2019-04-08 | 2020-10-20 | 阿里巴巴集团控股有限公司 | Instance migration method and device and electronic equipment |
| CN110572448A (en) * | 2019-08-30 | 2019-12-13 | 烽火通信科技股份有限公司 | distributed edge cloud system architecture |
| CN110769039A (en) * | 2019-10-09 | 2020-02-07 | 腾讯科技（深圳）有限公司 | Resource scheduling method and device, electronic equipment and computer readable storage medium |
| US20210144515A1 (en) * | 2019-11-12 | 2021-05-13 | Verizon Patent And Licensing Inc. | Systems and methods for multi-access edge computing node selection |
| CN113259260A (en) * | 2020-02-11 | 2021-08-13 | 华为技术有限公司 | Method and device for deploying application instance and scheduling application instance |
| CN111612933A (en) * | 2020-05-18 | 2020-09-01 | 上海齐网网络科技有限公司 | Augmented reality intelligent inspection system based on edge cloud server |
| CN113190378A (en) * | 2020-12-31 | 2021-07-30 | 华数云科技有限公司 | Edge cloud disaster recovery method based on distributed cloud platform |
| CN113190347A (en) * | 2021-04-21 | 2021-07-30 | 武汉卓尔信息科技有限公司 | Edge cloud system and task management method |
| CN113572821A (en) * | 2021-07-05 | 2021-10-29 | 山东师范大学 | Edge cloud node task cooperative processing method and system |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023082749A1 (en) * | 2021-11-15 | 2023-05-19 | 中电信数智科技有限公司 | Service recovery method and system based on mec edge cloud, and storage medium |
| WO2023109062A1 (en) * | 2021-12-14 | 2023-06-22 | 中电信数智科技有限公司 | Cloud disaster recovery system and method, electronic device, and storage medium |
| CN114520811A (en) * | 2022-04-20 | 2022-05-20 | 柏科数据技术（深圳）股份有限公司 | Production center data recovery method, system, terminal equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2023082749A1 (en) | 2023-05-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114070851A (en) | Service recovery method, storage medium and system based on MEC edge cloud | |
| CN111385107B (en) | Main/standby switching processing method and device for server | |
| CN109245926B (en) | Intelligent network card, intelligent network card system and control method | |
| CN103581276A (en) | Cluster management device and system, service client side and corresponding method | |
| CN103888277A (en) | Gateway disaster recovery backup method, apparatus and system | |
| CN105357057B (en) | A kind of acentric monitoring management node strange land redundancy approach | |
| CN110457176A (en) | For the monitoring method of distributed system, device, storage medium and electronic equipment | |
| CN109391691A (en) | The restoration methods and relevant apparatus that NAS is serviced under a kind of single node failure | |
| CN101227333B (en) | Disaster tolerance network managing system and login method of network managing subscriber end | |
| CN201985898U (en) | Communication service load balancing system | |
| EP3660679B1 (en) | Data backup method, device and system | |
| CN106027313B (en) | Network link disaster tolerance system and method | |
| CN116233148A (en) | Cloud edge data synchronization method, system, device and computer storage medium | |
| CN112543113A (en) | Method, device, equipment and medium for flexible Ethernet to respond to link failure | |
| CN102868945A (en) | Upgrading method optical network unit (ONU) in Ethernet passive optical network (EPON) | |
| CN114554615A (en) | Service switching method, device and network equipment | |
| CN114143903A (en) | Method, device, equipment and medium for configuring network slice PDU session | |
| CN110266790B (en) | Edge cluster management method and device, edge cluster and readable storage medium | |
| CN110794791A (en) | Data transmission method for cigarette factory manufacturing execution system and cigarette shred manufacturing centralized control system | |
| CN109474694A (en) | A kind of management-control method and device of the NAS cluster based on SAN storage array | |
| CN108540215A (en) | Photosphere restores the method and system that selection is inherited in 1+1 heavy-routes channel in WSON | |
| CN111918316B (en) | Base station maintenance method and base station maintenance device | |
| WO2022254662A1 (en) | Target information collection device, method, and program | |
| CN117793185A (en) | Information stream processing method and device | |
| CN116192244A (en) | OSU-oriented protected service protection switching method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: Room 1308, 13th floor, East Tower, 33 Fuxing Road, Haidian District, Beijing 100035 Applicant after: China Telecom Digital Intelligence Technology Co.,Ltd. Address before: Room 1308, 13th floor, East Tower, 33 Fuxing Road, Haidian District, Beijing 100035 Applicant before: CHINA TELECOM GROUP SYSTEM INTEGRATION Co.,Ltd. |