CN105530116B - Method and corresponding device for backing up and recovering virtualized network - Google Patents

Method and corresponding device for backing up and recovering virtualized network Download PDF

Info

Publication number
CN105530116B
CN105530116B CN201410579709.1A CN201410579709A CN105530116B CN 105530116 B CN105530116 B CN 105530116B CN 201410579709 A CN201410579709 A CN 201410579709A CN 105530116 B CN105530116 B CN 105530116B
Authority
CN
China
Prior art keywords
backup
nfvo
vnfm
vnf
request
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.)
Active
Application number
CN201410579709.1A
Other languages
Chinese (zh)
Other versions
CN105530116A (en
Inventor
蒋杏峰
周智伟
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to CN201410579709.1A priority Critical patent/CN105530116B/en
Priority to PCT/CN2015/083087 priority patent/WO2016062116A1/en
Publication of CN105530116A publication Critical patent/CN105530116A/en
Application granted granted Critical
Publication of CN105530116B publication Critical patent/CN105530116B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities

Abstract

The invention provides a backup method of a virtual network, which comprises the following steps: a network function virtualization scheduler NFVO receives a backup request, wherein the backup request comprises a VNF backup request or a VNFM backup request or a NFVO backup request; when the backup request is a VNF backup request, the NFVO performs VNF backup operation according to the VNF backup request; when the backup request is a VNFM backup request, the NFVO performs VNFM backup operation according to the VNFM backup request, and performs backup operation of each VNF managed by the VNFM after the VNFM backup is successful; when the backup request is an NFVO backup request, the NFVO performs NFVO backup operation according to the NFVO backup request, and performs the backup operation of each VNFM managed by the NFVO after the NFVO backup is successful; and performing backup operation of each VNF managed by each VNFM after each VNFM is successfully backed up. The scheme can effectively realize the quick backup and recovery of the physical resources of the mobile terminal.

Description

Method and corresponding device for backing up and recovering virtualized network
Technical Field
The present invention relates to the field of backup and recovery, and in particular, to a backup and recovery method and a corresponding device in a virtualized network.
Background
With the maturity of IT technology, more and more telecom operation models adopt Virtualization technology to reduce CAPEX (Capital Expenditure) and OPEX (Operating cost) thereof, and a Virtualization technology solution based on NFV (Network Function Virtualization) protocol standard can meet the technical implementation requirements of telecom operators to a great extent. Therefore, a solution for implementing core network virtualization deployment using the NFV standard architecture becomes a necessary choice for more and more operators.
The core idea of NFV is to implement hardware and software decoupling separation of telecommunication devices. In the NFV standard, each network element device is uniformly deployed on a CMS (Content Management System, cloud Management System) using a standard interface as an independent application function VNF (virtual network function), and orchestration and deployment of all network elements and network services in a core network are realized through an NFV-MANO domain, thereby realizing openness, automation, and intellectualization of a telecommunication network.
But the most potential risk is the data security problem due to the application of virtualization technology, and more so, due to the virtualization of the telecommunication core network. In the prior art, although the underlying CMS platform provides relatively comprehensive security guarantees, such as a main/standby mechanism, remote disaster recovery, and the like, rapid service recovery can be implemented from the hardware underlying. However, for a system across CMS platforms, the consistency of data backup of the entire system cannot be ensured by such a bottom backup, and the backup restoration of the network topology relationship between VNFs in the entire system cannot be realized, which has certain limitations.
Data backup of telecommunication network equipment can also be realized through functional entities in a service layer, for example, data backup and recovery of lower-level network Element equipment are realized through Element Management Systems (EMS) in a service domain, and data backup and recovery functions of a network Element can also be realized, which are traditional backup and recovery modes of telecommunication physical equipment. However, under virtualization technology, this approach exposes an inherent defect: fast backup and recovery of own physical resources, including a host, a network, etc., cannot be realized.
The invention content is as follows:
the invention aims to provide a method and a corresponding device for backing up and recovering a virtual network, so as to realize quick backing up and recovering of own physical resources.
In order to solve the above technical problem, the present application provides a backup method for a virtualized network, where the method includes:
a network function virtualization scheduler NFVO receives a backup request, wherein the backup request comprises a VNF backup request or a VNFM backup request or a NFVO backup request;
when the backup request is the VNF backup request, the NFVO performs VNF backup operation according to the VNF backup request;
when the backup request is the VNFM backup request, the NFVO performs VNFM backup operation according to the VNFM backup request, and performs backup operation of each VNF managed by the VNFM after the VNFM backup is successful;
when the backup request is the NFVO backup request, the NFVO performs NFVO backup operation according to the NFVO backup request, and performs backup operation of each VNFM managed by the NFVO after the NFVO backup is successful; and performing backup operation of each VNF managed by each VNFM after each VNFM is successfully backed up.
Preferably, the first and second liquid crystal films are made of a polymer,
when the backup request is the VNF backup request, the performing, by the NFVO, a VNF backup operation according to the VNF backup request includes:
the VNFM generates a VNF backup data packet according to the VNF backup request; the VNF backup package comprises backup data information of the VNF and configuration information of the VNF;
uploading the VNF backup data package through a CMS (cloud management system).
Preferably, the first and second liquid crystal films are made of a polymer,
when the backup request is the VNFM backup request, the NFVO performs VNFM backup operation according to the VNFM backup request, and the performing backup operation of each VNF managed by the VNFM after the VNFM backup is successful includes:
the VNFM generates a VNFM backup data packet according to the VNFM backup request, wherein the VNFM backup data packet comprises backup data information of each VNF managed by the VNFM, configuration information of the VNFM and configuration information of each VNF;
uploading the VNFM backup data packets through the CMS.
Preferably, the first and second liquid crystal films are made of a polymer,
when the backup request is the NFVO backup request, the NFVO performs NFVO backup operation according to the NFVO backup request, and performs backup operation of each VNFM managed by the NFVO after the NFVO backup is successful; and after each VNFM backup is successful, performing backup operation of each VNF managed by each VNFM, including:
the NFVO generates an NFVO backup data package according to the NFVO backup request, wherein the NFVO backup data package comprises backup data information of each VNF managed by the NFVO, configuration information of each VNFM managed by the NFVO and configuration information of each VNF;
uploading the NFVO backup data package through the CMS.
Preferably, the first and second liquid crystal films are made of a polymer,
the VNF configuration information comprises the VNF system configuration information and VNF-VNF topology association information;
the VNFM configuration information comprises the VNFM system configuration information, VNFM-VNF topology association information and NFVO-VNFM topology association information;
the NFVO configuration information includes virtual machine specification information, system configuration information of each VNFM and each VNF, and topology association information of NFVO-VNFM-VNF.
The invention also provides a method for recovering the virtualized network, which comprises the following steps:
the network function virtualization scheduler NFVO receives a recovery request, the recovery request comprising a VNF recovery request or a VNFM recovery request or a NFVO recovery request;
when the recovery request is the VNF recovery request, the NFVO performs VNF recovery operation according to the VNF recovery request;
when the recovery request is the VNFM recovery request, the NFVO performs VNFM recovery operation according to the VNFM recovery request;
and when the recovery request is the NFVO recovery request, the NFVO performs the NFVO recovery operation according to the NFVO recovery request.
Preferably, the first and second liquid crystal films are made of a polymer,
when the recovery request is the VNF recovery request, the performing, by the NFVO, a VNF recovery operation according to the VNF recovery request includes:
the VNFM receives the VNF recovery request, and performs instance recovery on the VNF according to the VNF recovery request;
the VNF performs data recovery on the VNF;
and sending a recovery success response message to the NFVO through the VNFM.
Preferably, the first and second liquid crystal films are made of a polymer,
when the recovery request is the VNFM recovery request, the performing, by the NFVO, a VNFM recovery operation according to the VNFM recovery request includes:
and the NFVO performs VNFM instance recovery and performs VNFM data recovery after the instance recovery is successful, wherein the VNFM recovered data is consistent with the data of each VNF managed by the VNFM.
Preferably, the first and second liquid crystal films are made of a polymer,
when the recovery request is the NFVO recovery request, the performing, by the NFVO, an NFVO recovery operation according to the NFVO recovery request includes:
and the NFVO performs the NFVO instance recovery, and performs the NFVO data recovery after the instance recovery is successful, wherein the data recovered by the NFVO is consistent with the data of each VNFM and each VNF managed by the NFVO.
The present invention also provides a backup device for a virtualized network, the device comprising:
the receiving module is used for receiving a backup request, wherein the backup request comprises a VNF backup request, a VNFM backup request or a NFVO backup request;
the NFVO is used for carrying out VNF backup operation according to the VNF backup request when the VNF backup request is the backup request; the NFVO is further configured to, when the backup request is the VNFM backup request, perform VNFM backup operation according to the VNFM backup request, and perform backup operation of each VNF managed by the VNFM after the VNFM backup is successful; the NFVO is further configured to, when the backup request is the NFVO backup request, perform an NFVO backup operation according to the NFVO backup request, and perform a backup operation of each VNFM managed by the NFVO after the NFVO backup is successful; and performing backup operation of each VNF managed by each VNFM after each VNFM is successfully backed up.
Preferably, the first and second liquid crystal films are made of a polymer,
the backup module is configured to, when the backup request is the VNF backup request, the NFVO performing VNF backup operation according to the VNF backup request, where the performing the VNF backup operation by the NFVO includes:
the VNFM generates a VNF backup data packet according to the VNF backup request; the VNF backup package comprises backup data information of the VNF and configuration information of the VNF;
uploading the VNF backup data package through a CMS (cloud management system).
Preferably, the first and second liquid crystal films are made of a polymer,
the backup module is further configured to, when the backup request is the VNFM backup request, perform, by the NFVO, a VNFM backup operation according to the VNFM backup request, and perform, after the VNFM backup is successful, a backup operation of each VNF managed by the VNFM:
the VNFM generates a VNFM backup data packet according to the VNFM backup request, wherein the VNFM backup data packet comprises backup data information of each VNF managed by the VNFM, configuration information of the VNFM and configuration information of each VNF;
uploading the VNFM backup data packets through the CMS.
Preferably, the first and second liquid crystal films are made of a polymer,
the backup module is further configured to, when the backup request is the NFVO backup request, perform, by the NFVO, an NFVO backup operation according to the NFVO backup request, and perform, after the NFVO backup is successful, a backup operation of each VNFM managed by the NFVO; and performing backup operation of each VNF managed by each VNFM after each VNFM backup is successful means:
the NFVO generates an NFVO backup data package according to the NFVO backup request, wherein the NFVO backup data package comprises backup data information of each VNF managed by the NFVO, configuration information of each VNFM managed by the NFVO and configuration information of each VNF;
uploading the NFVO backup data package through the CMS.
Preferably, the first and second liquid crystal films are made of a polymer,
the VNF configuration information comprises the VNF system configuration information and VNF-VNF topology association information;
the VNFM configuration information comprises the VNFM system configuration information, VNFM-VNF topology association information and NFVO-VNFM topology association information;
the NFVO configuration information includes virtual machine specification information, system configuration information of each VNFM and each VNF, and topology association information of NFVO-VNFM-VNF.
The present invention also provides a device for restoring a virtualized network, the device comprising:
a receiving module, configured to receive a recovery request, where the recovery request includes a VNF recovery request, a VNFM recovery request, or a NFVO recovery request;
a recovery module, configured to, when a recovery request is the VNF recovery request, perform, by the NFVO, a VNF recovery operation according to the VNF recovery request; the NFVO is further configured to perform a VNFM recovery operation according to the VNFM recovery request when the recovery request is the VNFM recovery request; and the NFVO is further configured to, when the recovery request is the NFVO recovery request, perform an NFVO recovery operation according to the NFVO recovery request.
Preferably, the first and second liquid crystal films are made of a polymer,
the recovery module is configured to, when the recovery request is the VNF recovery request, the NFVO performs VNF recovery operation according to the VNF recovery request, where the performing includes:
the VNFM receives the VNF recovery request, and performs instance recovery on the VNF according to the VNF recovery request;
the VNF performs data recovery on the VNF;
and sending a recovery success response message to the NFVO through the VNFM.
Preferably, the first and second liquid crystal films are made of a polymer,
the recovery device is further configured to, when the recovery request is the VNFM recovery request, the NFVO performs VNFM recovery operation according to the VNFM recovery request, where:
and the NFVO performs VNFM instance recovery and performs VNFM data recovery after the instance recovery is successful, wherein the VNFM recovered data is consistent with the data of each VNF managed by the VNFM.
Preferably, the first and second liquid crystal films are made of a polymer,
the recovery module is further configured to, when the recovery request is the NFVO recovery request, perform an NFVO recovery operation by the NFVO according to the NFVO recovery request, where the performing of the NFVO recovery operation by the NFVO according to the NFVO recovery request includes:
and the NFVO performs the NFVO instance recovery, and performs the NFVO data recovery after the instance recovery is successful, wherein the data recovered by the NFVO is consistent with the data of each VNFM and each VNF managed by the NFVO.
The scheme can realize the rapid backup and recovery of the physical resources of the system, not only can overcome the inherent defect of the traditional backup and recovery mode, save the recovery time required by the interruption of the system operation in a specific scene, reduce the operation risk and the operation and maintenance cost caused by the system software and hardware faults, but also can be used for rapidly realizing the cross-system copying and migration of the telecommunication service, and really realize the flexible deployment of the telecommunication service.
Drawings
Fig. 1 is a flowchart of VNF backup in the second embodiment of the present invention;
fig. 2 is a flowchart of VNF recovery in the second embodiment of the present invention;
FIG. 3 is a flowchart of a VNFM backup in a second embodiment of the present invention;
FIG. 4 is a flowchart of a VNFM backup in a second embodiment of the present invention;
fig. 5 is a flowchart of NFVO backup in the second embodiment of the present invention.
Detailed Description
To make the objects, technical solutions and advantages of the present application more apparent, embodiments of the present application will be described in detail below with reference to the accompanying drawings. It should be noted that the embodiments and features of the embodiments in the present application may be arbitrarily combined with each other without conflict.
The invention provides a method for adding a backup and recovery function on an Orchester module (resource orchestration scheduler, NFVO for short) in an NFV-MANO domain, and realizing the backup and recovery of VNFs unified data managed in a domain by matching with a VNFM (VNF management) module, which comprises the following steps:
1. backup of single or multiple VNFs within a domain.
2. Backup of single or multiple VNFMs within a domain.
3. Restoration of single or multiple VNFs within a domain.
4. Restoration of single or multiple VNFMs within a domain.
The backup content comprises virtual machine and network specification data, Guest OS mirror image resources and system configuration data, service data and the like, all backup data can define related backup granularity according to the attribute characteristics of the backup data on the premise of ensuring consistency, the backup data can be stored in third-party network shared storage or can be directly stored in cloud storage through CMS, and a user does not need to care about the storage position.
The practical applicable scenarios of this backup method include the following:
fast recovery after a VNF crash, such as VNF recovery due to a virtual machine Guest OS system corruption.
VNF migration, such as switching of underlying VMs.
3. System data backup recovery across CMSs, etc.
According to the NFV-MANO system architecture definition, the NFV-MANO domain mainly comprises 3 functional entities, which are NFVO, VNFM and VNFs in sequence according to the hierarchical scope. The backup and recovery method in the invention mainly surrounds the 3 functional entities. The concrete solving method is as follows:
1) the NFVO module provides a master control interface with a backup recovery function, and divides backup objects into three layers, namely an NFVO layer, a VNFM layer and a VNFs layer according to the range and the dependency relationship of the backup objects. And the backup data of each layer respectively generate an independent package, and the data backup is realized uniformly through a shared storage or cloud storage system.
2) The data information that the NFVO layer needs to backup includes:
a. virtual machine specification information, such as specification information of CPU, internal memory, storage, etc.
Mirror image and version configuration information of VNF and VNFM
Entire network topology description information of NFVO-VNFM-VNFs
3) The data information that needs to be backed up by the VNFM layer includes:
VNFM's own system configuration description information
VNFM-VNFs network topology description information
Network topology description information of VNFM-NFVO
4) The data information to be backed up by the VNFs layer includes:
VNF System configuration data information
VNF service operation data information
Network topology information between VNFs
5) The backup recovery method comprises the following steps:
and a, completing the data backup and recovery function of the NFVO layer by the NFVO module, directly acquiring backup data information from the NFVO, and packaging to call a CMS (management system) interface to realize cloud storage.
And b, the data backup and recovery functions of the VNFM layer and the VNFs layer are mainly realized by a VNFM module, wherein the service data of the VNFs can be acquired through the backup and recovery functions of the VNFs.
c. In order to ensure the consistency of data operated by the system, the backup recovery function requires that data backups of three levels have parent-child dependency relationship. Namely, NFVO and VNFM are parent and child, VNFM and VNFs are parent and child, the child layer backup must be consistent with the parent layer, when the parent layer data backup is completed, the child layer data backup needs to be triggered, otherwise, the child layer data backup is not triggered. To implement this constraint, each layer of backup packets must be time-stamped.
d. The restoration supports single-layer single VNF restoration and also supports system-level restoration of multiple layers of multiple VNFs.
e. When preparing multi-layer data recovery, the backup data preparation of each layer starts from a sub-layer, sub-layer backup data closest to a recovery time point is obtained according to a backup data time stamp, and then parent-layer backup data closest to the sub-layer time point is obtained.
One simple backup-restore timestamp example:
Figure BDA0000593519410000091
Figure BDA0000593519410000101
1) when the NFVO layer performs backup at 2014.8.1, data backup of VNFM and VNFs layers is triggered in conjunction.
2) When the VNFM performs backup at 2014.8.9, data backup at the VNFs layer is triggered in conjunction.
3) Single-layer data recovery: when the data of the VNFs of 2014.8.13 is required to be restored, the backup restoration function acquires the closest VNFs backup data according to the time stamp (2014.8.13) for restoration.
4) Multi-layer data recovery: if the data of the VNFs and the VNFM of 2014.8.13 is required to be restored, the backup restoration function first obtains the VNFs layer backup data closest to 2014.8.13 (2014.8.13), and then obtains the VNFM backup data closest to the time stamp of the VNFs backup data (2014.8.11) to prepare for restoration.
5) If the data of 2014.8.17 in the whole system under the management of NFVO is required to be restored, the backup restoration function selects the backup data of 2014.8.17 of VNFs, 2014.8.15 of VNFM and 2014.8.11 of O in turn for restoration.
6) The NFVO provides a backup recovery strategy and a backup data cleaning function, and data backup in a period is reserved according to the backup strategy. When data is cleaned, the data consistency of each layer needs to be ensured.
7) The NFVO supports concurrent operation of VNF backup recovery among different VNFMs, and VNF backup recovery under the same VNFM needs to be performed according to the sequence of topological dependence relationship among each other.
Example one
The invention provides a backup method of a virtual network, which comprises the following steps:
the method comprises the following steps: a network function virtualization scheduler NFVO receives a backup request, wherein the backup request comprises a VNF backup request or a VNFM backup request or a NFVO backup request;
step two: when the backup request is the VNF backup request, the NFVO performs VNF backup operation according to the VNF backup request;
when the backup request is the VNFM backup request, the NFVO performs VNFM backup operation according to the VNFM backup request, and performs backup operation of each VNF managed by the VNFM after the VNFM backup is successful;
when the backup request is the NFVO backup request, the NFVO performs NFVO backup operation according to the NFVO backup request, and performs backup operation of each VNFM managed by the NFVO after the NFVO backup is successful; and performing backup operation of each VNF managed by each VNFM after each VNFM is successfully backed up.
In particular, the method comprises the following steps of,
when the backup request is the VNF backup request, the performing, by the NFVO, a VNF backup operation according to the VNF backup request includes:
the VNFM generates a VNF backup data packet according to the VNF backup request; the VNF backup package comprises backup data information of the VNF and configuration information of the VNF;
uploading the VNF backup data package through a CMS (cloud management system).
When the backup request is the VNFM backup request, the NFVO performs VNFM backup operation according to the VNFM backup request, and the performing backup operation of each VNF managed by the VNFM after the VNFM backup is successful includes:
the VNFM generates a VNFM backup data packet according to the VNFM backup request, wherein the VNFM backup data packet comprises backup data information of each VNF managed by the VNFM, configuration information of the VNFM and configuration information of each VNF;
uploading the VNFM backup data packets through the CMS.
When the backup request is the NFVO backup request, the NFVO performs NFVO backup operation according to the NFVO backup request, and performs backup operation of each VNFM managed by the NFVO after the NFVO backup is successful; and after each VNFM backup is successful, performing backup operation of each VNF managed by each VNFM, including:
the NFVO generates an NFVO backup data package according to the NFVO backup request, wherein the NFVO backup data package comprises backup data information of each VNF managed by the NFVO, configuration information of each VNFM managed by the NFVO and configuration information of each VNF;
uploading the NFVO backup data package through the CMS.
The VNF configuration information comprises the VNF system configuration information and VNF-VNF topology association information;
the VNFM configuration information comprises the VNFM system configuration information, VNFM-VNF topology association information and NFVO-VNFM topology association information;
the NFVO configuration information includes virtual machine specification information, system configuration information of each VNFM and each VNF, and topology association information of NFVO-VNFM-VNF.
After the first step, before the second step, there may be:
step three: the NFVO checks whether a backup condition is met;
and when the backup condition is met, the NFVO performs corresponding backup operation according to the backup request.
The invention also provides a method for recovering the virtualized network, which corresponds to the backup method provided by the invention, and the method comprises the following steps:
step A: the network function virtualization scheduler NFVO receives a recovery request, the recovery request comprising a VNF recovery request or a VNFM recovery request or a NFVO recovery request;
and B: when the recovery request is the VNF recovery request, the NFVO performs VNF recovery operation according to the VNF recovery request;
when the recovery request is the VNFM recovery request, the NFVO performs VNFM recovery operation according to the VNFM recovery request;
and when the recovery request is the NFVO recovery request, the NFVO performs the NFVO recovery operation according to the NFVO recovery request.
In particular, the method comprises the following steps of,
when the recovery request is the VNF recovery request, the performing, by the NFVO, a VNF recovery operation according to the VNF recovery request includes:
the VNFM receives the VNF recovery request, and performs instance recovery on the VNF according to the VNF recovery request;
the VNF performs data recovery on the VNF;
and sending a recovery success response message to the NFVO through the VNFM.
When the recovery request is the VNFM recovery request, the performing, by the NFVO, a VNFM recovery operation according to the VNFM recovery request includes:
and the NFVO performs VNFM instance recovery and performs VNFM data recovery after the instance recovery is successful, wherein the VNFM recovered data is consistent with the data of each VNF managed by the VNFM.
When the recovery request is the NFVO recovery request, the performing, by the NFVO, an NFVO recovery operation according to the NFVO recovery request includes:
and the NFVO performs the NFVO instance recovery, and performs the NFVO data recovery after the instance recovery is successful, wherein the data recovered by the NFVO is consistent with the data of each VNFM and each VNF managed by the NFVO.
After step A and before step B, the following steps can be further included:
and C: the NFVO checks whether a recovery condition is met;
and when the recovery condition is met, the NFVO performs corresponding recovery operation according to the recovery request.
The present invention also provides a backup device for a virtualized network, the device comprising:
the receiving module is used for receiving a backup request, wherein the backup request comprises a VNF backup request, a VNFM backup request or a NFVO backup request;
the NFVO is used for carrying out VNF backup operation according to the VNF backup request when the VNF backup request is the backup request; the NFVO is further configured to, when the backup request is the VNFM backup request, perform VNFM backup operation according to the VNFM backup request, and perform backup operation of each VNF managed by the VNFM after the VNFM backup is successful; the NFVO is further configured to, when the backup request is the NFVO backup request, perform an NFVO backup operation according to the NFVO backup request, and perform a backup operation of each VNFM managed by the NFVO after the NFVO backup is successful; and performing backup operation of each VNF managed by each VNFM after each VNFM is successfully backed up.
Preferably, the first and second liquid crystal films are made of a polymer,
the backup module is configured to, when the backup request is the VNF backup request, the NFVO performing VNF backup operation according to the VNF backup request, where the performing the VNF backup operation by the NFVO includes:
the VNFM generates a VNF backup data packet according to the VNF backup request; the VNF backup package comprises backup data information of the VNF and configuration information of the VNF;
uploading the VNF backup data package through a CMS (cloud management system).
Preferably, the first and second liquid crystal films are made of a polymer,
the backup module is further configured to, when the backup request is the VNFM backup request, perform, by the NFVO, a VNFM backup operation according to the VNFM backup request, and perform, after the VNFM backup is successful, a backup operation of each VNF managed by the VNFM:
the VNFM generates a VNFM backup data packet according to the VNFM backup request, wherein the VNFM backup data packet comprises backup data information of each VNF managed by the VNFM, configuration information of the VNFM and configuration information of each VNF;
uploading the VNFM backup data packets through the CMS.
Preferably, the first and second liquid crystal films are made of a polymer,
the backup module is further configured to, when the backup request is the NFVO backup request, perform, by the NFVO, an NFVO backup operation according to the NFVO backup request, and perform, after the NFVO backup is successful, a backup operation of each VNFM managed by the NFVO; and performing backup operation of each VNF managed by each VNFM after each VNFM backup is successful means:
the NFVO generates an NFVO backup data package according to the NFVO backup request, wherein the NFVO backup data package comprises backup data information of each VNF managed by the NFVO, configuration information of each VNFM managed by the NFVO and configuration information of each VNF;
uploading the NFVO backup data package through the CMS.
Preferably, the first and second liquid crystal films are made of a polymer,
the VNF configuration information comprises the VNF system configuration information and VNF-VNF topology association information;
the VNFM configuration information comprises the VNFM system configuration information, VNFM-VNF topology association information and NFVO-VNFM topology association information;
the NFVO configuration information includes virtual machine specification information, system configuration information of each VNFM and each VNF, and topology association information of NFVO-VNFM-VNF.
The present invention also provides a device for restoring a virtualized network, which corresponds to the backup device of the virtualized network of the present invention, and the device comprises:
a receiving module, configured to receive a recovery request, where the recovery request includes a VNF recovery request, a VNFM recovery request, or a NFVO recovery request;
a recovery module, configured to, when a recovery request is the VNF recovery request, perform, by the NFVO, a VNF recovery operation according to the VNF recovery request; the NFVO is further configured to perform a VNFM recovery operation according to the VNFM recovery request when the recovery request is the VNFM recovery request; and the NFVO is further configured to, when the recovery request is the NFVO recovery request, perform an NFVO recovery operation according to the NFVO recovery request.
Preferably, the first and second liquid crystal films are made of a polymer,
the recovery module is configured to, when the recovery request is the VNF recovery request, the NFVO performs VNF recovery operation according to the VNF recovery request, where the performing includes:
the VNFM receives the VNF recovery request, and performs instance recovery on the VNF according to the VNF recovery request;
the VNF performs data recovery on the VNF;
and sending a recovery success response message to the NFVO through the VNFM.
Preferably, the first and second liquid crystal films are made of a polymer,
the recovery device is further configured to, when the recovery request is the VNFM recovery request, the NFVO performs VNFM recovery operation according to the VNFM recovery request, where:
and the NFVO performs VNFM instance recovery and performs VNFM data recovery after the instance recovery is successful, wherein the VNFM recovered data is consistent with the data of each VNF managed by the VNFM.
Preferably, the first and second liquid crystal films are made of a polymer,
the recovery module is further configured to, when the recovery request is the NFVO recovery request, perform an NFVO recovery operation by the NFVO according to the NFVO recovery request, where the performing of the NFVO recovery operation by the NFVO according to the NFVO recovery request includes:
and the NFVO performs the NFVO instance recovery, and performs the NFVO data recovery after the instance recovery is successful, wherein the data recovered by the NFVO is consistent with the data of each VNFM and each VNF managed by the NFVO.
Example two
The backup method and the recovery method of the virtualized network according to the present invention are further explained with reference to the drawings.
As shown in fig. 1, the procedure of VNF backup in this embodiment is as follows:
step 101: USER sends VNF backup request to NFVO.
Step 102: and after receiving the request, the NFVO firstly checks the command information, checks whether the command information meets the backup requirement, and returns the command information if the command information does not meet the backup requirement.
Step 103: the NFVO sends a VNF backup request to the VNFM.
Step 104: the VNFM collects and backs up managed backup data such as VNF system configuration information and topology association information.
Step 105: the VNFM sends a VNF data backup request to the VNF.
Step 106: and the VNF receives a backup request of the VNFM and starts business data backup.
Step 107: and after the VNF is successfully backed up, informing the VNFM that the backup is successful, and preparing to uniformly package to generate a backup data packet.
Step 108: and after the VNFM package is successful, the NFVO is informed of the successful backup, and the data is ready to be uploaded.
Step 109: the NFVO receives the VNFM response, informing the CMS to prepare to upload backup data.
Step 110: and the CMS feeds back that the NFVO data is successfully backed up.
Step 111: and the NFVO feeds back the success of USER data backup.
As shown in fig. 2, the VNF recovery processing flow in this embodiment is as follows:
step 201: USER sends VNF restore request to NFVO.
Step 202: and after receiving the request, the NFVO firstly checks to check whether the recovery requirement is met, if the check is passed, the next step is carried out, and if the check is not passed, the failure is returned.
Step 203: the NFVO notifies the CMS to prepare VNF backup data for recovery.
Step 204: after receiving the notification from the NFVO, the CMS checks and prepares the relevant resources, and notifies the NFVO after preparing OK.
Step 205: the NFVO sends a restore VNF request to the VNFM.
Step 206: after receiving the request of the NFVO, the VNFM starts VNF instance recovery first.
Step 207: and after the VNF instance is successfully recovered, the VNFM informs the VNF of recovering the service data.
Step 208: and the VNF receives a data recovery request of the VNFM and starts data recovery.
Step 209: and informing the VNFM after the VNF data recovery is successful.
Step 210: the VNFM informs the NFVO that the data recovery was successful.
Step 211: NFVO informs the USER that the data recovery is successful.
As shown in fig. 3, the procedure of VNFM backup in this embodiment is as follows:
step 301: USER sends VNFM data backup request to NFVO.
Step 302: and the NFVO checks after receiving the request and checks whether the backup condition is met.
Step 303: and after the NFVO verification is passed, the VNFM is notified to perform VNFM data backup.
Step 304: after receiving the backup request, the VNFM starts to perform VFNM data backup, and the VFNM data backup mainly comprises data such as VNFM self-system configuration data information, VNFM-VNFs network topology description information, NFVO-VNFM network topology description and the like.
Step 305: and after successful VNFM backup, packaging to generate a VNFM backup data packet, and simultaneously informing the VNF to perform data backup.
Step 306: and the VNF receives the backup request of the VNFM and starts to perform VNF data backup, wherein the VNF data backup comprises data such as new VNF system configuration data, VNF-VNF network topology information, VNF business data information and the like.
Step 307: and after successful VNF backup, packaging to generate a VNF backup data packet, and simultaneously feeding back that VNFM backup is successful and data is ready to be uploaded.
Step 308: and the VNFM receives the successful backup information of the VNF, feeds back the successful backup of the NFVO, and prepares data to be uploaded.
Step 309: and the NFVO receives the successful backup information of the VNFM and informs the CMS of preparing to upload 2 layer backup data packets.
Step 310: and if the backup data packet is uploaded successfully, the CMS feeds back that the uploading of the NFVO is finished.
Step 311: and the NFVO feeds back the success of USER data backup.
As shown in fig. 4, the procedure of VNFM recovery in this embodiment is as follows:
step 401: USER sends VNFM recovery request to NFVO.
Step 402: and the NFVO checks after receiving the request, and checks whether VNFM recovery conditions are met.
Step 403: and after the verification is passed, data recovery of the VNFM is started, the VNFM instance is recovered firstly, and after the recovery is successful, data recovery of the VFNM of the VNFM is performed.
Step 404: and after the data recovery is successful, the NFVO returns the USER recovery success.
As shown in fig. 5, the procedure of NFVO backup in this embodiment is as follows:
step 501: the USER sends an NFVO surface data backup request to the NFVO.
Step 502: and the NFVO checks after receiving the request and checks whether the backup condition is met.
Step 503: and starting to perform data backup on the NFVO after the verification is passed, wherein the data backup mainly comprises configuration description information such as specification information of all virtual machines, mirror images and versions of VNFM and VNFs and network topology information of NFVO-VNFM-VNFs.
Step 504: and packaging after the NFVO backup is successful, generating NFVO backup data, and simultaneously informing a VNFM to perform data backup.
Step 505: and the VNFM receives the backup request of the NFVO and starts to perform VNFM data backup, wherein the VNFM data backup comprises data information of VNFM self-configuration, VNFM-VNFs network topology description information, NFVO-VNFM network topology description and the like.
Step 506: and after successful VNFM backup, packaging to generate VNFM layer backup data, and simultaneously informing VNFs to perform data backup.
Step 507: and the VNF receives the backup request of the VNFM and starts to perform VNF data backup, wherein the VNF data backup comprises data such as new VNF system configuration data, VNF-VNF network topology information, VNF business data information and the like.
Step 508: and after successful VNF backup, packaging to generate VNF backup data, and simultaneously feeding back that VNFM backup is successful and the data is ready to be uploaded.
Step 509: and the VNFM receives the successful backup information of the VNF, feeds back the successful backup of the NFVO, and prepares data to be uploaded.
Step 510: and the NFVO receives the successful backup information of the VNFM and informs the CMS of preparing to upload 3 layers of backup data.
Step 511: and if the backup data is uploaded successfully, the CMS feeds back that the uploading of the NFVO data is finished.
Step 512: and the NFVO feeds back the success of the USER backup recovery.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention. It will be understood by those skilled in the art that all or part of the steps of the above methods may be implemented by instructing the relevant hardware through a program, and the program may be stored in a computer readable storage medium, such as a read-only memory, a magnetic or optical disk, and the like. Alternatively, all or part of the steps of the foregoing embodiments may also be implemented by using one or more integrated circuits, and accordingly, each module/module in the foregoing embodiments may be implemented in the form of hardware, and may also be implemented in the form of a software functional module. The present application is not limited to any specific form of hardware or software combination.

Claims (16)

1. A backup method for a virtualized network, the method comprising:
a network function virtualization scheduler NFVO receives a backup request, wherein the backup request comprises a VNF backup request or a VNFM backup request or a NFVO backup request;
when the backup request is a VNF backup request, the NFVO performs VNF backup operation according to the VNF backup request;
when the backup request is a VNFM backup request, the NFVO performs VNFM backup operation according to the VNFM backup request, and performs backup operation of each VNF managed by the VNFM after the VNFM backup is successful;
when the backup request is an NFVO backup request, the NFVO performs NFVO backup operation according to the NFVO backup request, and performs backup operation of each VNFM managed by the NFVO after the NFVO backup is successful; and performing backup operation of each VNF managed by each VNFM after each VNFM is successfully backed up.
2. The method of claim 1, wherein:
when the backup request is a VNF backup request, the performing, by the NFVO, a VNF backup operation according to the VNF backup request includes:
the VNFM generates a VNF backup data packet according to the VNF backup request; the VNF backup package comprises backup data information of the VNF and configuration information of the VNF;
uploading the VNF backup data package through a CMS (cloud management system).
3. The method of claim 1, wherein:
when the backup request is a VNFM backup request, the NFVO performs VNFM backup operation according to the VNFM backup request, and the performing backup operation of each VNF managed by the VNFM after the VNFM backup is successful includes:
the VNFM generates a VNFM backup data packet according to the VNFM backup request, wherein the VNFM backup data packet comprises backup data information of each VNF managed by the VNFM, configuration information of the VNFM and configuration information of each VNF;
uploading the VNFM backup data package through a CMS (cloud management system).
4. The method of claim 1, wherein:
when the backup request is an NFVO backup request, the NFVO performs NFVO backup operation according to the NFVO backup request, and performs backup operation of each VNFM managed by the NFVO after the NFVO backup is successful; and after each VNFM backup is successful, performing backup operation of each VNF managed by each VNFM, including:
the NFVO generates an NFVO backup data package according to the NFVO backup request, wherein the NFVO backup data package comprises backup data information of each VNF managed by the NFVO, configuration information of each VNFM managed by the NFVO and configuration information of each VNF;
uploading the NFVO backup data packet through a cloud management system CMS.
5. The method of claim 2, 3 or 4, wherein:
the VNF configuration information comprises VNF system configuration information and VNF-VNF topology association information;
the VNFM configuration information comprises VNFM system configuration information, VNFM-VNF topology association information and NFVO-VNFM topology association information;
the NFVO configuration information includes virtual machine specification information, system configuration information of each VNFM and each VNF, and topology association information of NFVO-VNFM-VNF.
6. A method for recovering a virtualized network, the method comprising:
the network function virtualization scheduler NFVO receives a recovery request, the recovery request comprising a VNF recovery request or a VNFM recovery request or a NFVO recovery request;
when the recovery request is a VNF recovery request, the NFVO performs VNF recovery operation according to the VNF recovery request;
when the recovery request is a VNFM recovery request, the NFVO performs VNFM recovery operation according to the VNFM recovery request;
when the recovery request is an NFVO recovery request, the NFVO performs an NFVO recovery operation according to the NFVO recovery request;
wherein, when the recovery request is a VNFM recovery request, the performing, by the NFVO, a VNFM recovery operation according to the VNFM recovery request includes:
and the NFVO performs VNFM instance recovery and performs VNFM data recovery after the instance recovery is successful, wherein the VNFM recovered data is consistent with the data of each VNF managed by the VNFM.
7. The method of claim 6, wherein:
when the recovery request is a VNF recovery request, the performing, by the NFVO, a VNF recovery operation according to the VNF recovery request includes:
the VNFM receives the VNF recovery request, and performs instance recovery on the VNF according to the VNF recovery request;
the VNF performs data recovery on the VNF;
and sending a recovery success response message to the NFVO through the VNFM.
8. The method of claim 6, wherein:
when the recovery request is an NFVO recovery request, the performing, by the NFVO, an NFVO recovery operation according to the NFVO recovery request includes:
and the NFVO performs the NFVO instance recovery, and performs the NFVO data recovery after the instance recovery is successful, wherein the data recovered by the NFVO is consistent with the data of each VNFM and each VNF managed by the NFVO.
9. A backup apparatus for a virtualized network, the apparatus comprising:
the receiving module is used for receiving a backup request, wherein the backup request comprises a VNF backup request, a VNFM backup request or a NFVO backup request;
the NFVO is used for carrying out VNF backup operation according to the VNF backup request when the backup request is the VNF backup request; the NFVO is further configured to, when the backup request is a VNFM backup request, perform a VNFM backup operation according to the VNFM backup request, and perform a backup operation of each VNF managed by the VNFM after the VNFM backup is successful; the NFVO is further configured to perform an NFVO backup operation according to the NFVO backup request when the backup request is the NFVO backup request, and perform a backup operation of each VNFM managed by the NFVO after the NFVO backup is successful; and performing backup operation of each VNF managed by each VNFM after each VNFM is successfully backed up.
10. The apparatus of claim 9, wherein:
the backup module is configured to, when the backup request is a VNF backup request, the performing, by the NFVO, a VNF backup operation according to the VNF backup request includes:
the VNFM generates a VNF backup data packet according to the VNF backup request; the VNF backup package comprises backup data information of the VNF and configuration information of the VNF;
uploading the VNF backup data package through a CMS (cloud management system).
11. The apparatus of claim 9, wherein:
the backup module is further configured to, when the backup request is a VNFM backup request, perform, by the NFVO, a VNFM backup operation according to the VNFM backup request, and perform, after the VNFM backup is successful, a backup operation of each VNF managed by the VNFM:
the VNFM generates a VNFM backup data packet according to the VNFM backup request, wherein the VNFM backup data packet comprises backup data information of each VNF managed by the VNFM, configuration information of the VNFM and configuration information of each VNF;
uploading the VNFM backup data package through a CMS (cloud management system).
12. The apparatus of claim 9, wherein:
the backup module is further configured to, when the backup request is an NFVO backup request, perform an NFVO backup operation according to the NFVO backup request, and perform a backup operation of each VNFM managed by the NFVO after the NFVO backup is successful; and performing backup operation of each VNF managed by each VNFM after each VNFM backup is successful means:
the NFVO generates an NFVO backup data package according to the NFVO backup request, wherein the NFVO backup data package comprises backup data information of each VNF managed by the NFVO, configuration information of each VNFM managed by the NFVO and configuration information of each VNF;
uploading the NFVO backup data packet through a cloud management system CMS.
13. The apparatus of claim 10, 11 or 12, wherein:
the VNF configuration information comprises VNF system configuration information and VNF-VNF topology association information;
the VNFM configuration information comprises VNFM system configuration information, VNFM-VNF topology association information and NFVO-VNFM topology association information;
the NFVO configuration information includes virtual machine specification information, system configuration information of each VNFM and each VNF, and topology association information of NFVO-VNFM-VNF.
14. An apparatus for restoring a virtualized network, the apparatus comprising:
a receiving module, configured to receive a recovery request, where the recovery request includes a VNF recovery request, a VNFM recovery request, or a NFVO recovery request;
a recovery module, configured to, when a recovery request is a VNF recovery request, perform, by the NFVO, a VNF recovery operation according to the VNF recovery request; the NFVO is further configured to perform a VNFM recovery operation according to the VNFM recovery request when the recovery request is the VNFM recovery request; the NFVO is further configured to perform an NFVO recovery operation according to the NFVO recovery request when the recovery request is the NFVO recovery request;
when the recovery request is a VNFM recovery request, the NFVO performs VNFM recovery operation according to the VNFM recovery request, where the performing the VNFM recovery operation by the NFVO includes:
and the NFVO performs VNFM instance recovery and performs VNFM data recovery after the instance recovery is successful, wherein the VNFM recovered data is consistent with the data of each VNF managed by the VNFM.
15. The apparatus of claim 14, wherein:
the recovery module is configured to, when the recovery request is a VNF recovery request, perform, by the NFVO, a VNF recovery operation according to the VNF recovery request, where:
the VNFM receives the VNF recovery request, and performs instance recovery on the VNF according to the VNF recovery request;
the VNF performs data recovery on the VNF;
and sending a recovery success response message to the NFVO through the VNFM.
16. The apparatus of claim 14, wherein:
the recovery module is further configured to, when the recovery request is an NFVO recovery request, perform an NFVO recovery operation by the NFVO according to the NFVO recovery request, where the performing of the NFVO recovery operation by the NFVO according to the NFVO recovery request includes:
and the NFVO performs the NFVO instance recovery, and performs the NFVO data recovery after the instance recovery is successful, wherein the data recovered by the NFVO is consistent with the data of each VNFM and each VNF managed by the NFVO.
CN201410579709.1A 2014-10-24 2014-10-24 Method and corresponding device for backing up and recovering virtualized network Active CN105530116B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201410579709.1A CN105530116B (en) 2014-10-24 2014-10-24 Method and corresponding device for backing up and recovering virtualized network
PCT/CN2015/083087 WO2016062116A1 (en) 2014-10-24 2015-07-01 Virtualization network backup and recovery method and corresponding device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201410579709.1A CN105530116B (en) 2014-10-24 2014-10-24 Method and corresponding device for backing up and recovering virtualized network

Publications (2)

Publication Number Publication Date
CN105530116A CN105530116A (en) 2016-04-27
CN105530116B true CN105530116B (en) 2020-06-16

Family

ID=55760238

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201410579709.1A Active CN105530116B (en) 2014-10-24 2014-10-24 Method and corresponding device for backing up and recovering virtualized network

Country Status (2)

Country Link
CN (1) CN105530116B (en)
WO (1) WO2016062116A1 (en)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107786361A (en) * 2016-08-30 2018-03-09 中兴通讯股份有限公司 A kind of switching NFVO method, apparatus, VNFM/VIM and NFVO
US10742532B2 (en) * 2017-12-18 2020-08-11 Futurewei Technologies, Inc. Non-intrusive mechanism to measure network function packet processing delay
CN110545193B (en) * 2018-05-28 2021-04-09 华为技术有限公司 Virtual resource management method, virtual resource management equipment and server
CN109522159A (en) * 2018-11-26 2019-03-26 广州华商职业学院 A kind of project management information standby system and its method
CN111352767B (en) * 2018-12-24 2023-07-18 中国电信股份有限公司 Network function virtualization platform resource management method, backup platform and system
CN111092744B (en) * 2019-04-16 2023-08-01 中兴通讯股份有限公司 Method, device and equipment for recovering VNF (virtual network function) instance

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103843284A (en) * 2013-10-23 2014-06-04 华为技术有限公司 Disaster tolerance method, system and device of cloud application
CN104115447A (en) * 2014-04-14 2014-10-22 华为技术有限公司 Allowing destroy scheme configuration method and device under cloud computing architecture

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103973487B (en) * 2014-04-29 2018-07-24 上海上讯信息技术股份有限公司 A kind of configuration backup system and configuring management method based on interactive script
CN104050045B (en) * 2014-06-27 2017-06-27 华为技术有限公司 Virtual resource allocation method and device based on disk I/O
CN104253866B (en) * 2014-09-20 2018-03-27 华为技术有限公司 Software deployment method, system and the relevant device of virtual network function network element

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103843284A (en) * 2013-10-23 2014-06-04 华为技术有限公司 Disaster tolerance method, system and device of cloud application
CN104115447A (en) * 2014-04-14 2014-10-22 华为技术有限公司 Allowing destroy scheme configuration method and device under cloud computing architecture

Also Published As

Publication number Publication date
WO2016062116A1 (en) 2016-04-28
CN105530116A (en) 2016-04-27

Similar Documents

Publication Publication Date Title
CN105530116B (en) Method and corresponding device for backing up and recovering virtualized network
CN109729143B (en) Deploying a network-based cloud platform on a terminal device
CN107515776B (en) Method for upgrading service continuously, node to be upgraded and readable storage medium
US8966318B1 (en) Method to validate availability of applications within a backup image
CN107209710B (en) Node system, server device, scaling control method, and program
US10185637B2 (en) Preserving management services with distributed metadata through the disaster recovery life cycle
US8910172B2 (en) Application resource switchover systems and methods
US20190163763A1 (en) Centralized Multi-Cloud Workload Protection with Platform Agnostic Centralized File Browse and File Retrieval Time Machine
WO2020248507A1 (en) Container cloud-based system resource monitoring method and related device
US11119829B2 (en) On-demand provisioning of customized developer environments
CN110581782B (en) Disaster tolerance data processing method, device and system
WO2017041525A1 (en) Virtual network function reconstruction method and device
CN106657167B (en) Management server, server cluster, and management method
EP2959387B1 (en) Method and system for providing high availability for state-aware applications
CN113032085A (en) Management method, device, server, management system and medium of cloud operating system
US20230082186A1 (en) Container-Based Application Data Protection Method and System
CN110737503B (en) Management method and device for container service snapshot
CN115292003A (en) Server failure recovery method and device, electronic equipment and storage medium
CN110554933A (en) Cloud management platform, and cross-cloud high-availability method and system for cloud platform service
CN111355605A (en) Virtual machine fault recovery method and server of cloud platform
CN106557386A (en) Method, the apparatus and system of standby virtual network interface card virtual machine are disposed based on KVM
CN112241293A (en) Application management method, device, equipment and medium for industrial internet cloud platform
CN116820686B (en) Physical machine deployment method, virtual machine and container unified monitoring method and device
CN110545193B (en) Virtual resource management method, virtual resource management equipment and server
EP3661140B1 (en) Method for applying for common service resource and related device

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant