Nothing Special   »   [go: up one dir, main page]

WO2018024204A1 - 虚拟网元的管理方法及装置 - Google Patents

虚拟网元的管理方法及装置 Download PDF

Info

Publication number
WO2018024204A1
WO2018024204A1 PCT/CN2017/095517 CN2017095517W WO2018024204A1 WO 2018024204 A1 WO2018024204 A1 WO 2018024204A1 CN 2017095517 W CN2017095517 W CN 2017095517W WO 2018024204 A1 WO2018024204 A1 WO 2018024204A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
backup
virtual network
virtual
service
Prior art date
Application number
PCT/CN2017/095517
Other languages
English (en)
French (fr)
Inventor
祝伟宏
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2018024204A1 publication Critical patent/WO2018024204A1/zh

Links

Images

Classifications

    • 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
    • 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
    • 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/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements

Definitions

  • the embodiments of the present invention relate to the field of communications, and in particular, to a method and an apparatus for managing a virtual network element.
  • the interface between the Network Management System (NMS) and the Element Management System (EMS) is called the northbound interface (Itf-N).
  • EMS mainly completes the network element management layer (EML) function in the ITU (International Telecommunication Union – International Telecommunications Union) TMN, which completes the management functions of one or more mobile communication devices, usually different devices.
  • EML network element management layer
  • the NMS mainly performs the network management layer (NML) function in the ITU TMN and is responsible for the management of all network elements in a managed network.
  • NML network management layer
  • the entire subnet can be managed through its own EMS management.
  • NFV Network Functions Virtualization
  • the original physical network element device is Instead of decoupling the network function from the specific hardware, the virtualized network function (VNF) is decoupled from the underlying network function virtualization infrastructure (NFVI).
  • NFVI network function virtualization infrastructure
  • the traditional maintenance management function of the VNF instance is performed by the EMS, and the life cycle management function of the VNF is completed by the VNF manager VNFM.
  • the underlying virtual infrastructure is managed by the Virtual Infrastructure Manager (VIM).
  • VIM Virtual Infrastructure Manager
  • the specific network service is generally completed by one or more VNF instances.
  • the management of the network service is carried out by the NFV arranger NFVO.
  • a network service instance After the virtualization of the network function is realized, from the application level, when a network service instance is to be established, an instance of the VNF required by the network service is required, and then one or more VNF instances are formed.
  • a network service instance provides network services through network service instances.
  • the self-healing function can be implemented by methods such as active/standby switching and cell compensation. It is realized by using professional hardware, the cost is relatively high, and the active/standby switch cannot be universally applied. For a virtualized network environment, since there is no physical hardware, it cannot be implemented by hardware switching, and there is no effective solution for the self-healing function of the network.
  • the embodiment of the invention provides a method and a device for managing a virtual network element, so as to at least solve the technical problem that the virtual network element cannot be switched in the related art.
  • a method for managing a virtual network element includes: determining that a virtual network element is faulty, wherein the virtual network element is implemented by virtualizing NFV technology by using a network function; The service assumed by the virtual network element is switched to the backup network element.
  • the switching of the service carried by the virtual network element to the backup network element according to the preset policy includes one of: determining a backup network element corresponding to the virtual network element, and undertaking the virtual network element The service is switched to the backup network element; a backup network element is determined from the backup network element group corresponding to the virtual network element, and the service undertaken by the virtual network element is switched to the backup network element; The backup network element corresponding to the virtual network element switches the service assumed by the virtual network element to the multiple backup network elements.
  • the method further includes: restarting the virtual network element, deleting the virtual network element, and rebuilding the The virtual network element.
  • the method before the switching the service assumed by the virtual network element to the backup network element according to the preset policy, the method further includes: a virtual network function descriptor VNFD and/or a network service description in the virtual network element.
  • VNFD virtual network function descriptor
  • a specified policy for indicating whether the virtual network element needs to be backed up is added to the NSD.
  • related data of the preset policy is configured according to the specified policy.
  • determining, by the backup network element group corresponding to the virtual network element, that one backup network element includes one of the following: determining, by using the network element with the least current traffic among all the network elements of the backup network element group, The backup network element is determined, and the network element closest to the virtual network element among all the network elements of the backup network element group is determined as the backup network element.
  • the method further includes: establishing a backup relationship table for the virtual network element, where the backup relationship table is used to describe The corresponding relationship between the virtual network element and the backup network element; or the information of the backup network element is added to the management object of the virtual network element.
  • the backup relationship table includes: an identifier of the virtual network element, an identifier of the backup network element, and a corresponding relationship between the virtual network element and the backup network element.
  • the information of the backup network element includes: identifier information of the backup network element of the virtual network element; or the backup network corresponding to the virtual network element
  • the information of the backup network element includes: identifier information of each backup network element in the backup network element group of the virtual network element.
  • the information about the backup network element further includes: attribute information for indicating whether the virtual network element has a backup network element.
  • a management device for a virtual network element including: a determining module, configured to determine that a virtual network element is faulty, wherein the virtual network element is implemented by a network function virtualization NFV technology;
  • the switching module is configured to switch the service assumed by the virtual network element to the backup network element according to the preset policy.
  • the switching module includes one of the following: a first switching unit, configured to determine a backup network element corresponding to the virtual network element, and switch the service assumed by the virtual network element to the backup network
  • the second switching unit is configured to determine a backup network element from the backup network element group corresponding to the virtual network element, and switch the service assumed by the virtual network element to the backup network element;
  • the unit is configured to determine a plurality of backup network elements corresponding to the virtual network element, and switch the service assumed by the virtual network element to the multiple backup network elements.
  • the device further includes: a processing module, configured to be in the switching module according to the pre After the policy is configured to switch the service of the virtual network element to the backup network element, perform one of the following operations: restarting the virtual network element, deleting the virtual network element, and reconstructing the virtual network element.
  • a processing module configured to be in the switching module according to the pre After the policy is configured to switch the service of the virtual network element to the backup network element, perform one of the following operations: restarting the virtual network element, deleting the virtual network element, and reconstructing the virtual network element.
  • the device further includes: a first adding module, configured to be virtualized in the virtual network element before the switching module switches the service assumed by the virtual network element to the backup network element according to the preset policy a specified policy for indicating whether the virtual network element needs to be backed up is added to the network function descriptor VNFD and/or the network service descriptor NSD; the configuration module is configured to be in the instantiation process of the virtual network element, according to the Specifies the policy to configure related data of the preset policy.
  • a first adding module configured to be virtualized in the virtual network element before the switching module switches the service assumed by the virtual network element to the backup network element according to the preset policy a specified policy for indicating whether the virtual network element needs to be backed up is added to the network function descriptor VNFD and/or the network service descriptor NSD
  • the configuration module is configured to be in the instantiation process of the virtual network element, according to the Specifies the policy to configure related data of the preset policy.
  • the second switching unit is further configured to determine, as the backup network element, a network element that has the least amount of current traffic in all network elements of the backup network element group; or, the backup network element group The network element closest to the virtual network element among all the network elements is determined as the backup network element.
  • the device further includes: an establishing module, configured to establish a backup relationship table for the virtual network element, before the switching the service assumed by the virtual network element to the backup network element according to the preset policy, the backup The relationship table is used to describe the correspondence between the virtual network element and the backup network element.
  • the second adding module is configured to add the information of the backup network element to the management object of the virtual network element.
  • a storage medium is also provided.
  • the storage medium is arranged to store program code for performing the following steps:
  • the service assumed by the virtual network element is switched to the backup network element according to a preset policy.
  • the virtual network element is faulty, wherein the virtual network element is implemented by the network function virtualized NFV technology; and the service assumed by the virtual network element is switched to the backup network element according to the preset policy.
  • FIG. 1 is a network function virtualization architecture diagram according to an embodiment of the present invention.
  • FIG. 2 is a flowchart of a method for managing a virtual network element according to an embodiment of the present invention
  • FIG. 3 is a structural block diagram of a management apparatus of a virtual network element according to an embodiment of the present invention.
  • FIG. 4 is a flowchart of a self-healing method of a virtual network element according to an embodiment of the present invention.
  • FIG. 1 is a network function virtualization architecture diagram according to an embodiment of the present invention.
  • the network architecture includes: NFVI, VNF, EMS, and NMS.
  • BSS Business Support System
  • OSS Operation Support System
  • NFVO NFV Orchestrator
  • VNFM VNF Manager
  • VIM Virtual Infrastructure Manager
  • FIG. 2 is a flowchart of a method for managing a virtual network element according to an embodiment of the present invention. As shown in FIG. 2, the process includes The following steps:
  • Step S202 determining that the virtual network element is faulty, wherein the virtual network element is implemented by virtualizing the NFV technology by using a network function;
  • Step S204 Switch the service assumed by the virtual network element to the backup network element according to the preset policy.
  • the virtual network element is faulty, and the virtual network element is implemented by the network function virtualized NFV technology; and the service assumed by the virtual network element is switched to the backup network element according to the preset policy.
  • the service assumed by the virtual network element is switched to the backup network element according to the preset policy.
  • the backup network element in this embodiment may also be a virtual network element. Of course, it may also be a physical device that can implement the same function.
  • the execution body of the foregoing step may be a control end of the virtual network element, but is not limited thereto.
  • switching the service assumed by the virtual network element to the backup network element according to the preset policy includes the following strategies:
  • the backup network element corresponding to the virtual network element is determined, and the service assumed by the virtual network element is switched to multiple backup network elements. Optionally, you can split the service and switch to multiple backup NEs.
  • the embodiment may also: restart the virtual network element, delete the virtual network element, and reconstruct the virtual network element.
  • the method before the service of the virtual network element is switched to the backup network element according to the preset policy, the method further includes:
  • VNFD virtual network function descriptor
  • NSD network service descriptor
  • the filling of the specific data in the backup switching policy may be manually configured or filled in automatically when the VNF is instantiated; Whether the VNF needs to be backed up in the VNFD and/or the NSD, so that when the VNF is instantiated, the VNFD or NSD policy can be used to determine whether the relevant data in the backup switching policy needs to be filled in, and when needed, Instantiate the VNF instance for backup.
  • determining a backup network element from the backup network element group (including multiple backup network elements) corresponding to the virtual network element can be implemented in the following manner:
  • the network element with the smallest current traffic among all the NEs of the backup NE group is determined as the backup network element.
  • the network element closest to the virtual network element among all the NEs of the backup NE group is determined as the backup network element.
  • the method further includes: establishing a backup relationship table for the virtual network element, where the backup relationship table is used to describe the virtual network element and the backup network element. Correspondence relationship; or, add information of the backup network element to the management object of the virtual network element.
  • the backup relationship table includes: a virtual network element identifier, a backup network element identifier, and a corresponding relationship between the virtual network element and the backup network element, for example, one or more network elements are simultaneously used as a backup of one network element. That is, the service of one network element can be shared at the same time.
  • the information of the backup network element when the virtual network element corresponds to one backup network element, includes: the identifier information of the backup network element of the virtual network element; and the backup network element group corresponding to the virtual network element
  • the information of the backup network element includes: identifier information of each backup network element in the backup network element group of the virtual network element. Further, the information of the backup network element further includes: attribute information for indicating whether the virtual network element has a backup network element.
  • the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation.
  • the technical solution of the present invention which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a plurality of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform various embodiments of the present invention. The method described.
  • a management device for a virtual network element is also provided.
  • the device is used to implement the foregoing embodiments and preferred embodiments, and details are not described herein.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 3 is a structural block diagram of a management apparatus of a virtual network element according to an embodiment of the present invention. As shown in FIG. 3, the apparatus includes:
  • the determining module 30 is configured to determine that the virtual network element is faulty, wherein the virtual network element is implemented by virtualizing the NFV technology by using a network function;
  • the switching module 32 is configured to switch the service assumed by the virtual network element to the backup network element according to the preset policy.
  • the switching module 32 may further include: a first switching unit configured to determine a backup network element corresponding to the virtual network element, and switch the service assumed by the virtual network element to the backup network element; and the second switching unit is set to be virtual and virtual The backup network element corresponding to the network element determines a backup network element, and switches the service assumed by the virtual network element to the backup network element; the third switching unit is configured to determine multiple backup network elements corresponding to the virtual network element, and The service assumed by the virtual NE is switched to multiple backup NEs.
  • the second switching unit is further configured to: determine, as the backup network element, the network element with the smallest current traffic among all the network elements of the backup network element group; or, the virtual network of all the network elements of the backup network element group The nearest NE is determined as the backup NE.
  • the device further includes: a processing module, configured to: after the switching module switches the service assumed by the virtual network element to the backup network element according to the preset policy, perform one of the following operations: restarting the virtual network element, deleting the virtual network element, Rebuild the virtual network element.
  • a processing module configured to: after the switching module switches the service assumed by the virtual network element to the backup network element according to the preset policy, perform one of the following operations: restarting the virtual network element, deleting the virtual network element, Rebuild the virtual network element.
  • the device further includes: a first adding module, configured to: before the switching module switches the service assumed by the virtual network element to the backup network element according to the preset policy, the virtual network function descriptor VNFD and/or in the virtual network element. Or added in the network service descriptor NSD to indicate that the virtual network element is The specified policy is required to be backed up.
  • the configuration module is configured to configure related data of the preset policy according to the specified policy during the instantiation of the virtual network element.
  • the device further includes: an establishing module, configured to establish a backup relationship table for the virtual network element before the service assumed by the virtual network element is switched to the backup network element according to the preset policy, where the backup relationship table is used to describe the virtual network element Corresponding relationship with the backup network element; or the second adding module is configured to add the information of the backup network element to the management object of the virtual network element.
  • an establishing module configured to establish a backup relationship table for the virtual network element before the service assumed by the virtual network element is switched to the backup network element according to the preset policy, where the backup relationship table is used to describe the virtual network element Corresponding relationship with the backup network element
  • the second adding module is configured to add the information of the backup network element to the management object of the virtual network element.
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination.
  • the forms are located in different processors.
  • This embodiment is an optional embodiment according to the present invention, and is used to specifically describe the present application:
  • the network technology virtualization (NFV) technology is adopted in the related art, and the virtual network element (virtualized network function) is a software function module running on a virtual network infrastructure built by a general hardware facility. Therefore, the self-healing of the virtual network element can be implemented by means of backup switching, that is, a virtual network element (network element B) for each virtual network element (network element A) that needs to support self-healing is allocated (network element B, C%), when the network element A fails, it directly switches its assumed service to a backup network element. In this way, the self-healing process is faster and has less impact on the user experience.
  • FIG. 4 is a flowchart of a self-healing method of a virtual network element according to an embodiment of the present invention, including:
  • each virtual network element that needs to support self-healing is assigned one or more virtual network elements for backup, namely:
  • the backup switching operation is performed, including but not limited to, switching the service assumed by the faulty network element to the backup network element.
  • the faulty network element is subjected to subsequent processing, and the specific operations include, but are not limited to, one of the following: restarting the faulty network element, deleting the faulty network element, and reconstructing the faulty network element;
  • the specific data in the backup switching policy can be filled in manually, or automatically filled in when the VNF is instantiated.
  • the VNF can be added to the VNFD and/or NSD.
  • the VNFD or NSD policy can be used to determine whether the relevant data in the backup switching policy needs to be filled in.
  • the VNF instance used for backup can also be instantiated.
  • a backup switching policy for self-healing is defined, that is, each virtual network element that needs to support self-healing is assigned a virtual network element for backup;
  • Performing a backup switching operation including but not limited to switching the service assumed by the faulty network element A to the backup network element B;
  • the faulty network element A is subjected to subsequent processing, and the specific operations include, but are not limited to, one of the following: restarting the faulty network element, deleting the faulty network element, and reconstructing the faulty network element;
  • a backup switching policy for self-healing is configured, that is, each virtual network element A that needs to support self-healing is allocated a plurality of virtual network elements for backup, that is, a backup network element group is created;
  • a network element B for backup is selected from the predetermined backup network element group according to a predetermined backup switching policy.
  • the selection policy of the backup network element includes but is not limited to A combination of one or more of the following:
  • the selected NE is the least amount of traffic in all NEs in the backup NE group.
  • the selected NE is the closest to all faulty NEs in all NEs in the backup NE group.
  • Performing a backup switching operation including but not limited to switching the service assumed by the faulty network element A to the backup network element B;
  • the faulty network element A is subjected to subsequent processing, and the specific operations include, but are not limited to, one of the following: restarting the faulty network element, deleting the faulty network element, and reconstructing the faulty network element;
  • Each element in the list includes the identifier of the NE to be backed up and the identifier of the NE used for backup.
  • a network element serves as a backup of one network element at the same time, that is, it can simultaneously share the services of one network element.
  • the backup policy is expressed. When, then:
  • VNFInfo add an attribute indicating whether it has the attribute of the backup network element and the identifier of the backup network element
  • VNFInfo In the virtual network element (VNF instance) management object (VNFInfo): only the attribute of the identifier of the backup network element is added. When the value of this attribute is empty, it indicates that there is no backup. When it is not empty, it indicates that there is a backup network element.
  • VNFInfo add an attribute indicating whether it has a backup network element, and a backup network element list attribute, where the backup network element group list includes all network elements that can be backed up. Identification; or
  • VNFInfo In the virtual network element (VNF instance) management object (VNFInfo): only add the backup network element list attribute.
  • This backup network element group list contains the identifiers of all the network elements that can be backed up. When this attribute value is empty, it indicates There is no backup. When it is not empty, it indicates that there is a backup NE.
  • the method of the present embodiment is used to overcome the problem that the self-healing function of the network does not have a mature solution in the network function virtualization environment in the prior art.
  • a network element self-healing method based on a virtual network element (virtualized network function) backup policy for implementing virtual network element (virtualized network function) self-healing in a virtualized environment is proposed to solve the above virtualization
  • a self-healing method for a virtual network element (virtualized network function), the specific steps are as follows:
  • a backup switching policy for self-healing is defined, that is, each virtual network element that needs to support self-healing is assigned one or more virtual network elements for backup.
  • Perform backup switchover including but not limited to operations such as switching the service assumed by the faulty NE to the backup NE.
  • performing subsequent processing on the faulty network element including but not limited to one of the following: deleting and restarting;
  • a virtual network element (virtualized network function) self-healing method (1 to 1) the specific steps are as follows:
  • a backup switching policy for self-healing is defined, that is, each virtual network element that needs to support self-healing is assigned a virtual network element for backup;
  • Performing a backup switching operation including but not limited to switching the service assumed by the faulty network element A to the backup network element B;
  • the faulty network element A is subjected to subsequent processing, and the specific operations include, but are not limited to, one of the following: restarting the faulty network element, deleting the faulty network element, and reconstructing the faulty network element;
  • a self-healing method (one-to-many) of virtual network elements (virtualized network functions), the specific steps are as follows:
  • a backup switching policy for self-healing is configured, that is, one or more virtual network elements for backup are allocated for each virtual network element that needs to support self-healing, that is, a backup network element group is created;
  • a network element B for backup is selected from the predetermined backup network element group according to a predetermined backup switching policy.
  • the selection policy of the backup network element includes but is not limited to A combination of one or more of the following:
  • the selected NE is the least amount of traffic in all NEs in the backup NE group.
  • the selected NE is the closest to all faulty NEs in all NEs in the backup NE group.
  • Perform backup switching operations including but not limited to switching the services undertaken by the faulty network element A to the standby Network element B;
  • the faulty network element A is subjected to subsequent processing, and the specific operations include, but are not limited to, one of the following: restarting the faulty network element, deleting the faulty network element, and reconstructing the faulty network element;
  • a virtual network element (virtualized network function) self-healing method (1 to 1) the specific steps are as follows:
  • Each element in the list includes the identifier of the NE to be backed up and the ID of the NE to be backed up. The more virtual network element allocates a virtual network element for backup;
  • Performing a backup switching operation including but not limited to switching the service assumed by the faulty network element A to the backup network element B;
  • the faulty network element A is subjected to subsequent processing, and the specific operations include, but are not limited to, one of the following: restarting the faulty network element, deleting the faulty network element, and reconstructing the faulty network element;
  • a self-healing method (one-to-many) of virtual network elements (virtualized network functions), the specific steps are as follows:
  • a backup switching policy for self-healing is established, that is, a backup relationship list backupPolicyList is created.
  • Each element in the list includes: a list onePolicy, the list contains the identifier of the network element to be backed up, and all the network elements that can be used for backup.
  • the identifier, that is, the network elements in the onePolicy of this list can be backed up by each other;
  • one or more network elements for backup are selected from the predetermined backup network element group according to a predetermined backup switching policy, and the selection policy of the backup network element includes but It is not limited to a combination of one or more of the following:
  • the selected NE is the least amount of traffic in all NEs in the backup NE group.
  • the selected NE is the closest to all faulty NEs in all NEs in the backup NE group.
  • Performing a backup switching operation including but not limited to switching the service assumed by the faulty network element A to the backup network element;
  • the faulty network element A is subjected to subsequent processing, and the specific operations include, but are not limited to, one of the following: restarting the faulty network element, deleting the faulty network element, and reconstructing the faulty network element;
  • the NMS creates a backup switchover policy list, which is used to store the self-healing backup switchover policy.
  • Each element in the list includes the identifier of the NE to be backed up and the ID of the NE to be backed up.
  • the self-healing virtual network element allocates a virtual network element for backup;
  • the NMS When the NMS detects that a virtual network element A is faulty, the NMS searches for the backup switching relationship policy list. If the identifier of the network element A is found to match the identifier of one network element B recorded by an element of the list, the network is Element A has a backup network element B;
  • the NMS performs a backup switching operation. Specifically, the operations performed include but are not limited to:
  • heal network service is invoked through the interface of the NMS (OSS) and the NFVO (Os-Ma-Nfvo), and an operation indication for replacing the network element A with the network element B is given in the input parameter healNSData or healVNFData.
  • Specific instructions include but are not limited to:
  • the faulty network element A is subjected to subsequent processing, and the specific operations include, but are not limited to, one of the following: restarting the faulty network element, deleting the faulty network element, and reconstructing the faulty network element;
  • a virtual network element (virtualized network function) self-healing method (1-to-many, self-healing module in NMS (OSS)), the specific steps are as follows:
  • the NMS establishes a backup switching policy for self-healing, that is, creates a backup relationship list backupPolicyList.
  • Each element in the list includes: a list onePolicy, the list contains the identifier of the network element to be backed up, and all the network elements that can be used for backup.
  • logo that is to say this The network elements in the list onePolicy can be backed up to each other;
  • the NMS When the NMS detects that a virtual network element A is faulty, the NMS searches for each element onePolicy in the backup switching policy list backupPolicyList, and if it can find the identifier of the network element A and an element record of one of the onePolicy list (onePolicyX). If a network element identifier matches, the network element A has a backup network element group onePolicyX. According to the predetermined backup switching policy, a network element B for backup is selected from the backup network element group onePolicyX, and the selection policy of the backup network element is selected. This includes, but is not limited to, a combination of one or more of the following:
  • the selected NE is the least amount of traffic in all NEs in the backup NE group.
  • the selected NE is the closest to all faulty NEs in all NEs in the backup NE group.
  • the NMS performs backup switching operations, including but not limited to:
  • the NMS (OSS) and the NFVO interface (Os-Ma-Nfvo) are used to invoke the network service scaling (Scale Network Service) operation to expand the capacity.
  • the backup network element B is added to the network service where the network element A is located, and the faulty network element A is assumed. The service is switched to the backup network element B.
  • the NMS and the NFVO interface (Os-Ma-Nfvo) invokes a Scale Network Service operation to perform the capacity reduction, and the faulty network element A is moved out of the network service where the network element is located;
  • a virtual network element (virtualized network function) self-healing method (1 to 1, self-healing module in EMS), the specific steps are as follows:
  • the NMS creates a backup switching relationship policy on the EMS through the northbound interface.
  • the main function is to add the attribute of the backup NE instance (BackupNE) to the management object of the virtual NE. If the value is empty, the NMS has no backup NE. If it is not empty, its value is the backup NE instance identifier);
  • the EMS When the EMS detects that a virtual network element A is faulty, the EMS checks the value of the BackupNE attribute in the management object of the network element A. If the value is not empty, the network element B corresponding to the backup NE attribute value is the faulty network element A. Backup network element;
  • the EMS performs a backup switching operation. Specifically, the operations performed include, but are not limited to:
  • the operation of the Heal Network Service is invoked through the interface of the EMS and the NFVO (or the EMS through the NMS), and an operation indication for replacing the network element A with the network element B is given in the input parameter healNSData or healVNFData.
  • Specific instructions include but are not limited to:
  • the faulty network element A is subjected to subsequent processing, and the specific operations include, but are not limited to, one of the following: restarting the faulty network element, deleting the faulty network element, and reconstructing the faulty network element;
  • a virtual network element (virtualized network function) self-healing method (1 to many, self-healing module in VNFM), the specific steps are as follows:
  • the NMS establishes a backup switching policy for self-healing in the VNFM through the EMS.
  • a backup relationship list backupPolicyList is added to the management object VNFInfo that records the VNF instance information corresponding to the virtual network element.
  • the list includes all VNFs that can be used for backup.
  • the identifier of the instance, that is, the VNF instance in the list can be used as a backup of the VNF instance; if the list is empty, the VNF instance is not backed up;
  • the VNFM When the VNFM detects that a VNF instance A is faulty, the VNFM searches for the backup switching relationship policy list backupPolicyList in the management object VNFInfo corresponding to the faulty VNF instance. If the list is not empty, it indicates that the faulty VNF instance A has a backup, according to the reservation.
  • the backup switching policy selects a network element B for backup from the backup network element backupPolicyList.
  • the selection policy of the backup network element includes but is not limited to one or more combinations of the following manners:
  • the selected NE is the least amount of traffic in all NEs in the backup NE group.
  • the selected NE is the closest to all faulty NEs in all NEs in the backup NE group.
  • the VNFM performs backup switching operations, including but not limited to:
  • the network service expansion (Scale Network Service) operation is invoked through the interface of the VNFM and the NFVO to expand the capacity, and the backup network element B is added to the network service where the network element A is located. The service undertaken by the element A is switched to the backup network element B;
  • the scale network service operation is invoked through the interface of the VNFM and the NFVO to perform the capacity reduction, and the faulty network element A is removed from the network service where the network element is located;
  • a virtual network element (virtualized network function) self-healing method (1 to many, self-healing module in NFVO), the specific steps are as follows:
  • a backup switching policy for self-healing is established.
  • a backup relationship list backupPolicyList is added to the management object VNFInfo that records the VNF instance information corresponding to the virtual network element.
  • the list contains the identifiers of all VNF instances corresponding to the network elements that can be used for backup. That is, the VNF instance in the list can be used as a backup of the VNF instance; if the list is empty, the VNF instance is not backed up;
  • the NFVO When the NFVO detects that a VNF instance A is faulty, the NFVO searches for the backup switching relationship policy list backupPolicyList in the management object VNFInfo corresponding to the faulty VNF instance. If the list is not empty, it indicates that the faulty VNF instance A has a backup, according to the reservation.
  • the backup switching policy selects a network element B for backup from the backup network element backupPolicyList.
  • the selection policy of the backup network element includes but is not limited to one or more combinations of the following manners:
  • the selected NE is the least amount of traffic in all NEs in the backup NE group.
  • the selected NE is the closest to all faulty NEs in all NEs in the backup NE group.
  • NFVO performs backup switching operations, including but not limited to:
  • the network service of the network element A is added to the network service where the network element A is located, and the service assumed by the faulty network element A is switched to the backup network element B;
  • the network service is scaled down by the Scale Network Service operation, and the faulty network element A is removed from the network service where the network element is located;
  • Embodiments of the present invention also provide a storage medium.
  • the foregoing storage medium may be configured to store program code for performing the following steps:
  • S2 Switch the service assumed by the virtual network element to the backup network element according to the preset policy.
  • the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • a mobile hard disk e.g., a hard disk
  • magnetic memory e.g., a hard disk
  • the processor determines that the virtual network element is faulty according to the stored program code in the storage medium, where the virtual network element is implemented by the network function virtualization NFV technology;
  • the processor performs to switch the service assumed by the virtual network element to the backup network element according to the preset policy according to the stored program code in the storage medium.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the method and apparatus for managing a virtual network element have the following beneficial effects: by transferring the service assumed by the virtual network element to the backup network element, the virtual network element cannot be solved in the related technology.
  • the technical problem of switching improves the self-healing capability of the virtual network element.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明提供实施例了一种虚拟网元的管理方法及装置，其中，该方法包括：确定虚拟网元出现故障，其中，所述虚拟网元通过网络功能虚拟化NFV技术实现；根据预设策略将所述虚拟网元承担的业务切换到备份网元。通过本发明实施例，解决了相关技术中不能对虚拟网元进行切换的技术问题，提高了虚拟网元的自愈能力。

Description

虚拟网元的管理方法及装置 技术领域
本发明实施例涉及通信领域，具体而言，涉及一种虚拟网元的管理方法及装置。
背景技术
在无线通讯系统的管理领域，网络管理系统(Network Management System–NMS)与网元管理系统(Element Management System–EMS)之间的接口称为北向接口(Itf-N)。EMS主要完成ITU(International Telecommunication Union–国际电信联盟)TMN(Telecommunications Management Network-电信管理网络)中的网元管理层(EML)功能，即完成一个或多个移动通信设备的管理功能，通常不同设备供应商之间的EMS无法通用。NMS主要完成ITU TMN中的网络管理层(NML)功能，负责一个被管网络内所有网元的管理。对于被管网络(称为子网)内存在多个设备供应商的情况，可以通过各自的EMS管理达到管理整个子网的目的。
相关技术中，为了提高通讯网络的灵活性，降低管理成本，由运营商发起提出了网络功能虚拟化(Network Functions Virtualization-NFV)概念，在使用NFV技术的情况下，原来的物理网元设备由虚拟化网络功能(Virtualized Network Function-VNF)代替，使得网络功能与具体硬件解耦，如图1，VNF与底层的网络功能虚拟化基础架构(Network Functions Virtualization Infrastructure-NFVI)隔离。对于VNF的管理，通过EMS对VNF实例进行传统的维护管理功能，而VNF的生命周期管理功能则通过VNF管理器VNFM完成。底层的虚拟基础架构由虚拟基础架构管理器(VIM)进行管理。而具体的网络业务，则一般通过一个或多个VNF实例来完成。对网络业务的管理，则通过NFV编排器NFVO来进行。实现网络功能虚拟化后，从应用层面来看，要建立一个网络业务实例时，需要先生成网络业务需要的VNF的实例，再由一个或多个VNF实例组成一个 网络业务实例，通过网络业务实例来提供网络业务。
对于相关技术中的网络来说，自愈功能可以通过主备切换、小区补偿等方法来实现。是通过采用专业硬件来实现，成本比较高，主备切换不能普遍应用。而对于虚拟化网络环境下，由于没有实体硬件，不能通过硬件切换来实现，网络的自愈功能也没有有效的解决方案。
针对相关技术中存在的上述问题，目前尚未发现有效的解决方案。
发明内容
本发明实施例提供了一种虚拟网元的管理方法及装置，以至少解决相关技术中不能对虚拟网元进行切换的技术问题。
根据本发明的一个实施例，提供了一种虚拟网元的管理方法，包括：确定虚拟网元出现故障，其中，所述虚拟网元通过网络功能虚拟化NFV技术实现；根据预设策略将所述虚拟网元承担的业务切换到备份网元。
可选地，根据预设策略将所述虚拟网元承担的业务切换到备份网元包括以下之一：确定与所述虚拟网元对应的一个备份网元，并将所述虚拟网元承担的业务切换到所述备份网元；从与所述虚拟网元对应的备份网元组中确定一个备份网元，并将所述虚拟网元承担的业务切换到所述备份网元；确定与所述虚拟网元对应的多个备份网元，将所述虚拟网元承担的业务切换到所述多个备份网元。
可选地，在根据预设策略将所述虚拟网元承担的业务切换到备份网元之后，所述方法还包括以下之一：重启所述虚拟网元、删除所述虚拟网元、重建所述虚拟网元。
可选地，在根据预设策略将所述虚拟网元承担的业务切换到备份网元之前，所述方法还包括：在所述虚拟网元的虚拟网络功能描述符VNFD和/或网络服务描述符NSD中添加用于指示所述虚拟网元是否需要备份的指定策略；在所述虚拟网元的实例化过程中，根据所述指定策略配置所述预设策略的相关数据。
可选地，从与所述虚拟网元对应的备份网元组中确定一个备份网元包括以下之一：将所述备份网元组的所有网元中当前业务量最少的网元确定为所述备份网元；将所述备份网元组的所有网元中距离所述虚拟网元最近的网元确定为所述备份网元。
可选地，在根据预设策略将所述虚拟网元承担的业务切换到备份网元之前，所述方法还包括：为所述虚拟网元建立备份关系表，所述备份关系表用于描述所述虚拟网元与所述备份网元的对应关系；或者，在所述虚拟网元的管理对象中添加所述备份网元的信息。
可选地，所述备份关系表包括：所述虚拟网元的标识、所述备份网元的标识、所述虚拟网元与所述备份网元的对应关系。
可选地，在所述虚拟网元对应一个备份网元时，所述备份网元的信息包括：所述虚拟网元的备份网元的标识信息；或，在所述虚拟网元对应备份网元组时，所述备份网元的信息包括：所述虚拟网元的备份网元组中各个备份网元的标识信息。
可选地，所述备份网元的信息还包括：用于表征所述虚拟网元是否存在备份网元的属性信息。
根据本发明的另一个实施例，提供了一种虚拟网元的管理装置，包括：确定模块，设置为确定虚拟网元出现故障，其中，所述虚拟网元通过网络功能虚拟化NFV技术实现；切换模块，设置为根据预设策略将所述虚拟网元承担的业务切换到备份网元。
可选地，所述切换模块包括以下之一：第一切换单元，设置为确定与所述虚拟网元对应的一个备份网元，并将所述虚拟网元承担的业务切换到所述备份网元；第二切换单元，设置为从与所述虚拟网元对应的备份网元组中确定一个备份网元，并将所述虚拟网元承担的业务切换到所述备份网元；第三切换单元，设置为确定与所述虚拟网元对应的多个备份网元，将所述虚拟网元承担的业务切换到所述多个备份网元。
可选地，所述装置还包括：处理模块，设置为在所述切换模块根据预 设策略将所述虚拟网元承担的业务切换到备份网元之后，执行以下操作之一：重启所述虚拟网元、删除所述虚拟网元、重建所述虚拟网元。
可选地，所述装置还包括：第一添加模块，设置为在所述切换模块根据预设策略将所述虚拟网元承担的业务切换到备份网元之前，在所述虚拟网元的虚拟网络功能描述符VNFD和/或网络服务描述符NSD中添加用于指示所述虚拟网元是否需要备份的指定策略；配置模块，设置为在所述虚拟网元的实例化过程中，根据所述指定策略配置所述预设策略的相关数据。
可选地，所述第二切换单元还设置为：将所述备份网元组的所有网元中当前业务量最少的网元确定为所述备份网元；或，将所述备份网元组的所有网元中距离所述虚拟网元最近的网元确定为所述备份网元。
可选地，所述装置还包括：建立模块，设置为在根据预设策略将所述虚拟网元承担的业务切换到备份网元之前，为所述虚拟网元建立备份关系表，所述备份关系表用于描述所述虚拟网元与所述备份网元的对应关系；或者，第二添加模块，设置为在所述虚拟网元的管理对象中添加所述备份网元的信息。
根据本发明的又一个实施例，还提供了一种存储介质。该存储介质设置为存储用于执行以下步骤的程序代码：
确定虚拟网元出现故障，其中，所述虚拟网元通过网络功能虚拟化NFV技术实现；
根据预设策略将所述虚拟网元承担的业务切换到备份网元。
通过本发明，确定虚拟网元出现故障，其中，所述虚拟网元通过网络功能虚拟化NFV技术实现；根据预设策略将所述虚拟网元承担的业务切换到备份网元。通过将虚拟网元承担的业务转移到备份网元，可以解决相关技术中不能对虚拟网元进行切换的技术问题，提高了虚拟网元的自愈能力。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据本发明实施例的网络功能虚拟化架构图；
图2是根据本发明实施例的虚拟网元的管理方法的流程图；
图3是根据本发明实施例的虚拟网元的管理装置的结构框图；
图4是根据本发明实施例的一种虚拟网元的自愈方法的流程图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
实施例1
本申请实施例可以运行于图1所示的网络架构上，图1是根据本发明实施例的网络功能虚拟化架构图，如图1所示，该网络架构包括：NFVI、VNF、EMS、NMS(包括，业务支撑系统(Business Support System，简称为BSS)、运营支撑系统(Operation Support System，简称为OSS))、NFV编排器(NFVO)、VNF管理器(VNFM)、虚拟基础架构管理器(VIM)，其中，各个模块之前通过接口进行连接，如，Os-Ma，Se-Ma等。
在本实施例中提供了一种运行于上述网络架构的虚拟网元的管理方法，图2是根据本发明实施例的虚拟网元的管理方法的流程图，如图2所示，该流程包括如下步骤：
步骤S202，确定虚拟网元出现故障，其中，虚拟网元通过网络功能虚拟化NFV技术实现；
步骤S204，根据预设策略将虚拟网元承担的业务切换到备份网元。
通过上述步骤，确定虚拟网元出现故障，其中，虚拟网元通过网络功能虚拟化NFV技术实现；根据预设策略将虚拟网元承担的业务切换到备份网元。通过将虚拟网元承担的业务转移到备份网元，可以解决相关技术中不能对虚拟网元进行切换的技术问题，提高了虚拟网元的自愈能力。
本实施例中的备份网元可以也是虚拟网元，当然，也可以是可以实现相同功能的实体设备。
可选地，上述步骤的执行主体可以为虚拟网元的控制端，但不限于此。
可选的，根据预设策略将虚拟网元承担的业务切换到备份网元包括以下几种策略：
确定与虚拟网元对应的一个备份网元，并将虚拟网元承担的业务切换到备份网元；
从与虚拟网元对应的备份网元组中确定一个备份网元，并将虚拟网元承担的业务切换到备份网元；
确定与虚拟网元对应的多个备份网元，将虚拟网元承担的业务切换到多个备份网元。可选的，可以将业务拆分后切换到多个备份网元中。
可选的，在根据预设策略将虚拟网元承担的业务切换到备份网元之后，本实施例还可以：重启虚拟网元、删除虚拟网元、重建虚拟网元。
可选的，在根据预设策略将虚拟网元承担的业务切换到备份网元之前，方法还包括：
S11，在虚拟网元的虚拟网络功能描述符VNFD(Virtual NetworkFunctions Descriptor)和/或网络服务描述符NSD(Network Sevice Descriptor)中添加用于指示虚拟网元是否需要备份的指定策略；
S12，在虚拟网元的实例化过程中，根据指定策略配置预设策略的相关数据。
上述备份切换策略(预设策略)中具体数据的填写，可以是人工进行配置填写，也可以在VNF实例化时自动填写；当是进行自动填写时，可 以先在VNFD和/或NSD中增加VNF是否需要备份的策略，这样进行VNF实例化时，可以根据VNFD或NSD中的策略决定是否需要填写备份切换策略中的相关数据，当需要时，还可以同时实例化用于备份的VNF实例。
可选的，从与虚拟网元对应的备份网元组(包括多个备份网元)中确定一个备份网元可以通过以下方式来实现：
将备份网元组的所有网元中当前业务量最少的网元确定为备份网元；
将备份网元组的所有网元中距离虚拟网元最近的网元确定为备份网元。
可选的，在根据预设策略将虚拟网元承担的业务切换到备份网元之前，方法还包括：为虚拟网元建立备份关系表，备份关系表用于描述虚拟网元与备份网元的对应关系；或者，在虚拟网元的管理对象中添加备份网元的信息。
可选的，上述备份关系表包括：虚拟网元的标识、备份网元的标识、虚拟网元与备份网元的对应关系，如1个或多个网元同时作为1个网元的备份，即可以同时分担1个网元的业务。
在根据本实施例的可选实施方式中，在虚拟网元对应一个备份网元时，备份网元的信息包括：虚拟网元的备份网元的标识信息；在虚拟网元对应备份网元组时，备份网元的信息包括：虚拟网元的备份网元组中各个备份网元的标识信息。进一步的，备份网元的信息还包括：用于表征虚拟网元是否存在备份网元的属性信息。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所 述的方法。
实施例2
在本实施例中还提供了一种虚拟网元的管理装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图3是根据本发明实施例的虚拟网元的管理装置的结构框图，如图3所示，该装置包括：
确定模块30，设置为确定虚拟网元出现故障，其中，虚拟网元通过网络功能虚拟化NFV技术实现；
切换模块32，设置为根据预设策略将虚拟网元承担的业务切换到备份网元。
切换模块32还可以包括：第一切换单元，设置为确定与虚拟网元对应的一个备份网元，并将虚拟网元承担的业务切换到备份网元；第二切换单元，设置为从与虚拟网元对应的备份网元组中确定一个备份网元，并将虚拟网元承担的业务切换到备份网元；第三切换单元，设置为确定与虚拟网元对应的多个备份网元，将虚拟网元承担的业务切换到多个备份网元。
可选的，第二切换单元还设置为：将备份网元组的所有网元中当前业务量最少的网元确定为备份网元；或，将备份网元组的所有网元中距离虚拟网元最近的网元确定为备份网元。
可选的，装置还包括：处理模块，设置为在切换模块根据预设策略将虚拟网元承担的业务切换到备份网元之后，执行以下操作之一：重启虚拟网元、删除虚拟网元、重建虚拟网元。
可选的，述装置还包括：第一添加模块，设置为在切换模块根据预设策略将虚拟网元承担的业务切换到备份网元之前，在虚拟网元的虚拟网络功能描述符VNFD和/或网络服务描述符NSD中添加用于指示虚拟网元是 否需要备份的指定策略；配置模块，设置为在虚拟网元的实例化过程中，根据指定策略配置预设策略的相关数据。
可选的，装置还包括：建立模块，设置为在根据预设策略将虚拟网元承担的业务切换到备份网元之前，为虚拟网元建立备份关系表，备份关系表用于描述虚拟网元与备份网元的对应关系；或者，第二添加模块，设置为在虚拟网元的管理对象中添加备份网元的信息。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
实施例3
本实施例是根据本发明的可选实施例，用于对本申请进行具体详细的说明：
在5G(new radio)阶段，相关技术中采用了网络功能虚拟化(NFV)技术，虚拟网元(虚拟化网络功能)是运行在通用硬件设施构建的虚拟网络基础架构之上的软件功能模块，所以虚拟网元的自愈可以采用备份切换的方式实现，即先为每个需要支持自愈的虚拟网元(网元A)分配一个用于或多个备份的虚拟网元(网元B、C……)，当网元A出现故障时，则直接将其承担的业务切换到某一个备份网元，采用这种方式，自愈过程更加快捷，对用户体验的影响更小。
通过本实施例，克服现有技术中在网络功能虚拟化环境下，网络的自愈功能如何实现还没有成熟的方案的问题。通过提出一种用于在虚拟化环境下实现虚拟网元(虚拟化网络功能)自愈的、给予虚拟网元(虚拟化网络功能)的备份策略的网元自愈方法，为解决上述虚拟化网络环境下还没有成熟的网元自愈方案的问题提供一种高效、可行的解决方案。
本实施例采用的技术方案如下，图4是根据本发明实施例的一种虚拟网元的自愈方法的流程图，包括：
制定用于自愈的备份切换策略(相当于上述实施例中的预设策略)， 即为每个需要支持自愈的虚拟网元分配一个或多个用于备份的虚拟网元，即：
1对1备份方案；或，1对多备份方案；
当一个需要支持自愈的虚拟网元出现故障时，根据预定的备份切换策略确定一个用于备份的网元；
执行备份切换操作，包括但不限于将故障网元承担的业务切换到备份网元；
可选的，对故障网元进行后续处理，具体操作包括但不限于如下之一：重启故障网元、删除故障网元、重建故障网元；
上述备份切换策略中具体数据的填写，可以是人工进行配置填写，也可以在VNF实例化时自动填写；当是进行自动填写时，可以先在VNFD和/或NSD中增加VNF是否需要备份的策略，这样进行VNF实例化时，可以根据VNFD或NSD中的策略决定是否需要填写备份切换策略中的相关数据，当需要时，还可以同时实例化用于备份的VNF实例。
当采用1对1备份方案时，具体步骤如下：
制定用于自愈的备份切换策略，即为每个需要支持自愈的虚拟网元分配一个用于备份的虚拟网元；
当一个需要支持自愈的虚拟网元A出现故障时，根据预定的备份切换策略确定一个用于备份的网元B；
执行备份切换操作，包括但不限于将故障网元A承担的业务切换到备份网元B；
可选的，对故障网元A进行后续处理，具体操作包括但不限于如下之一：重启故障网元、删除故障网元、重建故障网元；
当采用1对多备份方案时，具体步骤如下：
制定用于自愈的备份切换策略，即为每个需要支持自愈的虚拟网元A分配多个用于备份的虚拟网元，即创建一个备份网元组；
当一个需要支持自愈的虚拟网元A出现故障时，根据预定的备份切换策略从预定的备份网元组中选出一个用于备份的网元B，备份网元的选择策略包括但不限于如下方式的一个或多个的组合：
选中的网元是备份网元组中的所有网元中当前业务量最少的；
选中的网元是备份网元组中的所有网元中离故障网元A距离最近的；
执行备份切换操作，包括但不限于将故障网元A承担的业务切换到备份网元B；
可选的，对故障网元A进行后续处理，具体操作包括但不限于如下之一：重启故障网元、删除故障网元、重建故障网元；
对于备份策略，可以采用如下方案之一：
建立一个专门的备份关系表；
在网元管理对象中增加备份网元信息；
当采用建立一个专门的备份关系表的方式来表达备份策略时，则
对于是1对1的备份策略，则可以建立一个备份关系列表，列表中的每个元素包括：需要备份的网元的标识、用于备份的网元的标识；
对于是1对多的备份策略，则可以如下方法之一：
建立一个备份关系列表，列表中的元素包括：
需要备份的网元的标识
一个列表，列表中包含所有可用于备份的网元的标识；
建立一个备份关系列表，列表中的元素包括：
一个列表，列表中包含需要备份的网元的标识、及所有可用于备份的网元的标识；也即是说这个列表中的网元可以相互备份，或者，这个列表中的1个或多个网元同时作为1个网元的备份，即可以同时分担1个网元的业务；
当采用在网元管理对象中增加备份网元信息的方式来表达备份策略 时，则：
对于是1对1的备份策略，则可以选用如下方案之一：
在虚拟网元(即VNF实例)管理对象(VNFInfo)中：增加表示其是否有备份网元的属性、及备份网元的标识的属性；或者
在虚拟网元(即VNF实例)管理对象(VNFInfo)中：只增加备份网元的标识的属性，当这个属性值为空时表示没有备份，非空时表示有备份网元。
对于是1对多的备份策略，则可以选用如下方案之一：
在虚拟网元(即VNF实例)管理对象(VNFInfo)中：增加表示其是否有备份网元的属性、及备份网元组列表属性，其中备份网元组列表中包含所有可以备份的网元的标识；或者
在虚拟网元(即VNF实例)管理对象(VNFInfo)中：只增加备份网元组列表属性，这个备份网元组列表中包含所有可以备份的网元的标识，当这个属性值为空时表示没有备份，非空时表示有备份网元。
采用本实施例的方法，目的是为了克服现有技术中在网络功能虚拟化环境下，网络的自愈功能如何实现还没有成熟的方案的问题。通过提出一种用于在虚拟化环境下实现虚拟网元(虚拟化网络功能)自愈的、基于虚拟网元(虚拟化网络功能)的备份策略的网元自愈方法，为解决上述虚拟化网络环境下还没有成熟的网元自愈方案的问题提供一种高效、可行的解决方案。
本实施例还包括以下多个具体实施例，用于对本实施例进行详细说明：
具体实施例1：
一种虚拟网元(虚拟化网络功能)自愈方法，具体步骤如下：
制定用于自愈的备份切换策略，即为每个需要支持自愈的虚拟网元分配一个或多个用于备份的虚拟网元。
当一个需要支持自愈的虚拟网元出现故障时，根据预定的备份切换策 略确定一个用于备份的网元；
执行备份切换，包括但不限于将故障网元承担的业务切换到备份网元等操作；
可选的，对故障网元进行后续处理，包括但不限于如下之一：删除、重启；
具体实施例2：
一种虚拟网元(虚拟化网络功能)自愈方法(1对1)，具体步骤如下：
制定用于自愈的备份切换策略，即为每个需要支持自愈的虚拟网元分配一个用于备份的虚拟网元；
当一个需要支持自愈的虚拟网元A出现故障时，根据预定的备份切换策略确定一个用于备份的网元B；
执行备份切换操作，包括但不限于将故障网元A承担的业务切换到备份网元B；
可选的，对故障网元A进行后续处理，具体操作包括但不限于如下之一：重启故障网元、删除故障网元、重建故障网元；
具体实施例3：
一种虚拟网元(虚拟化网络功能)自愈方法(1对多)，具体步骤如下：
制定用于自愈的备份切换策略，即为每个需要支持自愈的虚拟网元分配1个或多个用于备份的虚拟网元，即创建一个备份网元组；
当一个需要支持自愈的虚拟网元A出现故障时，根据预定的备份切换策略从预定的备份网元组中选出一个用于备份的网元B，备份网元的选择策略包括但不限于如下方式的一个或多个的组合：
选中的网元是备份网元组中的所有网元中当前业务量最少的；
选中的网元是备份网元组中的所有网元中离故障网元A距离最近的；
执行备份切换操作，包括但不限于将故障网元A承担的业务切换到备 份网元B；
可选的，对故障网元A进行后续处理，具体操作包括但不限于如下之一：重启故障网元、删除故障网元、重建故障网元；
具体实施例4：
一种虚拟网元(虚拟化网络功能)自愈方法(1对1)，具体步骤如下：
创建一个备份切换关系策略列表，用于存放自愈的备份切换策略，列表中的每个元素包括：需要备份的网元的标识、用于备份的网元的标识；即为每个需要支持自愈的虚拟网元分配一个用于备份的虚拟网元；
当一个需要支持自愈的虚拟网元A出现故障时，搜索备份切换关系策略列表，若能搜到网元A的标识与列表的某个元素的需要备份的网元的标识相匹配，则说明网元A有备份网元，则确定这个用于备份的网元B；
执行备份切换操作，包括但不限于将故障网元A承担的业务切换到备份网元B；
可选的，对故障网元A进行后续处理，具体操作包括但不限于如下之一：重启故障网元、删除故障网元、重建故障网元；
具体实施例5：
一种虚拟网元(虚拟化网络功能)自愈方法(1对多)，具体步骤如下：
制定用于自愈的备份切换策略，即建立一个备份关系列表backupPolicyList，列表中的每个元素包括：一个列表onePolicy，列表中包含需要备份的网元的标识、及所有可用于备份的网元的标识，也即是说这个列表onePolicy中的网元可以相互备份；
当一个需要支持自愈的虚拟网元A出现故障时，根据预定的备份切换策略从预定的备份网元组中选出一个或多个用于备份的网元，备份网元的选择策略包括但不限于如下方式的一个或多个的组合：
选中的网元是备份网元组中的所有网元中当前业务量最少的；
选中的网元是备份网元组中的所有网元中离故障网元A距离最近的；
执行备份切换操作，包括但不限于将故障网元A承担的业务切换到备份网元；
可选的，对故障网元A进行后续处理，具体操作包括但不限于如下之一：重启故障网元、删除故障网元、重建故障网元；
具体实施例6：
一种虚拟网元(虚拟化网络功能)自愈方法(1对1,自愈模块在NMS(OSS))，具体步骤如下：
NMS创建一个备份切换关系策略列表，用于存放自愈的备份切换策略，列表中的每个元素包括：需要备份的网元的标识、用于备份的网元的标识；即为每个需要支持自愈的虚拟网元分配一个用于备份的虚拟网元；
当NMS监测到一个虚拟网元A出现故障时，NMS搜索备份切换关系策略列表，若能搜到网元A的标识与列表的某个元素记录的一个网元B的标识相匹配，则说明网元A有备份网元B；
NMS执行备份切换操作，具体地，执行的操作包括但不限于：
通过NMS(OSS)和NFVO的接口(Os-Ma-Nfvo)调用治愈网络服务(heal Network Service)操作，并在输入参数healNSData或healVNFData中给出用网元B来接替网元A的操作指示。具体的指示包括但不限于：
将故障网元A承担的业务切换到备份网元B；
可选的，对故障网元A进行后续处理，具体操作包括但不限于如下之一：重启故障网元、删除故障网元、重建故障网元；
具体实施例7：
一种虚拟网元(虚拟化网络功能)自愈方法(1对多，自愈模块在NMS(OSS))，具体步骤如下：
NMS制定用于自愈的备份切换策略，即建立一个备份关系列表backupPolicyList，列表中的每个元素包括：一个列表onePolicy，列表中包含需要备份的网元的标识、及所有可用于备份的网元的标识，也即是说这 个列表onePolicy中的网元可以相互备份；
当NMS监测到一个虚拟网元A出现故障时，NMS搜索备份切换关系策略列表backupPolicyList中的每一个元素onePolicy，若能搜到网元A的标识与某一个onePolicy列表(onePolicyX)的某个元素记录的一个网元标识相匹配，则说明网元A有备份网元组onePolicyX；根据预定的备份切换策略从备份网元组onePolicyX中选出一个用于备份的网元B，备份网元的选择策略包括但不限于如下方式的一个或多个的组合：
选中的网元是备份网元组中的所有网元中当前业务量最少的；
选中的网元是备份网元组中的所有网元中离故障网元A距离最近的；
NMS执行备份切换操作，具体操作包括但不限于：
通过NMS(OSS)和NFVO的接口(Os-Ma-Nfvo)调用网络服务伸缩(Scale Network Service)操作进行扩容，备份网元B加入到网元A所在的网络服务，将故障网元A承担的业务切换到备份网元B；
可选的，通过NMS(OSS)和NFVO的接口(Os-Ma-Nfvo)调用网络服务伸缩(Scale Network Service)操作进行缩容，将故障网元A移出其本来所在的网络服务；
具体实施例8：
一种虚拟网元(虚拟化网络功能)自愈方法(1对1,自愈模块在EMS)，具体步骤如下：
NMS通过北向接口在EMS创建一个备份切换关系策略，主要是通过在虚拟网元对于的管理对象中增加备份网元实例标识的属性(BackupNE)(若该属性值为空，则表示没有备用网元，若非空，则其值就是备份网元实例标识)；
当EMS监测到一个虚拟网元A出现故障时，EMS检查网元A的管理对象中的BackupNE属性的值，若其值非空，则说明BackupNE属性值对应的网元B就是故障网元A的备份网元；
EMS执行备份切换操作，具体地，执行的操作包括但不限于：
通过EMS和NFVO的接口(或者EMS通过NMS)调用治愈网络服务(heal Network Service)操作，并在输入参数healNSData或healVNFData中给出用网元B来接替网元A的操作指示。具体的指示包括但不限于：
将故障网元A承担的业务切换到备份网元B；
可选的，对故障网元A进行后续处理，具体操作包括但不限于如下之一：重启故障网元、删除故障网元、重建故障网元；
具体实施例9：
一种虚拟网元(虚拟化网络功能)自愈方法(1对多，自愈模块在VNFM)，具体步骤如下：
NMS通过EMS在VNFM制定用于自愈的备份切换策略，在记录虚拟网元对应的VNF实例信息的管理对象VNFInfo中增加一个备份关系列表backupPolicyList，列表中包含所有可用于备份的网元对应的VNF实例的标识，也即是说这个列表中的VNF实例都可以作为所述VNF实例的备份；若该列表为空，则说明所述VNF实例没有备份；
当VNFM监测到一个VNF实例A出现故障时，VNFM搜索故障VNF实例对应的管理对象VNFInfo中的备份切换关系策略列表backupPolicyList，若该列表不为空，则说明故障VNF实例A有备份，则根据预定的备份切换策略从备份网元组backupPolicyList中选出一个用于备份的网元B，备份网元的选择策略包括但不限于如下方式的一个或多个的组合：
选中的网元是备份网元组中的所有网元中当前业务量最少的；
选中的网元是备份网元组中的所有网元中离故障网元A距离最近的；
VNFM执行备份切换操作，具体操作包括但不限于：
通过VNFM和NFVO的接口调用网络服务伸缩(Scale Network Service)操作进行扩容，将备份网元B加入到网元A所在的网络服务，将故障网 元A承担的业务切换到备份网元B；
可选的，通过VNFM和NFVO的接口调用网络服务伸缩(Scale Network Service)操作进行缩容，将故障网元A移出其本来所在的网络服务；
具体实施例10：
一种虚拟网元(虚拟化网络功能)自愈方法(1对多，自愈模块在NFVO)，具体步骤如下：
在NFVO制定用于自愈的备份切换策略，在记录虚拟网元对应的VNF实例信息的管理对象VNFInfo中增加一个备份关系列表backupPolicyList，列表中包含所有可用于备份的网元对应的VNF实例的标识，也即是说这个列表中的VNF实例都可以作为所述VNF实例的备份；若该列表为空，则说明所述VNF实例没有备份；
当NFVO监测到一个VNF实例A出现故障时，NFVO搜索故障VNF实例对应的管理对象VNFInfo中的备份切换关系策略列表backupPolicyList，若该列表不为空，则说明故障VNF实例A有备份，则根据预定的备份切换策略从备份网元组backupPolicyList中选出一个用于备份的网元B，备份网元的选择策略包括但不限于如下方式的一个或多个的组合：
选中的网元是备份网元组中的所有网元中当前业务量最少的；
选中的网元是备份网元组中的所有网元中离故障网元A距离最近的；
NFVO执行备份切换操作，具体操作包括但不限于：
通过网络服务伸缩(Scale Network Service)操作进行扩容，将备份网元B加入到网元A所在的网络服务，将故障网元A承担的业务切换到备份网元B；
可选的，通过网络服务伸缩(Scale Network Service)操作进行缩容，将故障网元A移出其本来所在的网络服务；
实施例4
本发明的实施例还提供了一种存储介质。可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的程序代码：
S1，确定虚拟网元出现故障，其中，虚拟网元通过网络功能虚拟化NFV技术实现；
S2，根据预设策略将虚拟网元承担的业务切换到备份网元。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行确定虚拟网元出现故障，其中，虚拟网元通过网络功能虚拟化NFV技术实现；
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行根据预设策略将虚拟网元承担的业务切换到备份网元。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精 神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
如上所述，本实施例提供的一种虚拟网元的管理方法及装置，具有以下有益效果：通过将虚拟网元承担的业务转移到备份网元，可以解决相关技术中不能对虚拟网元进行切换的技术问题，提高了虚拟网元的自愈能力。

Claims (15)

  1. 一种虚拟网元的管理方法，包括：
    确定虚拟网元出现故障，其中，所述虚拟网元通过网络功能虚拟化NFV技术实现；
    根据预设策略将所述虚拟网元承担的业务切换到备份网元。
  2. 根据权利要求1所述的方法，其中，根据预设策略将所述虚拟网元承担的业务切换到备份网元包括以下之一：
    确定与所述虚拟网元对应的一个备份网元，并将所述虚拟网元承担的业务切换到所述备份网元；
    从与所述虚拟网元对应的备份网元组中确定一个备份网元，并将所述虚拟网元承担的业务切换到所述备份网元；
    确定与所述虚拟网元对应的多个备份网元，将所述虚拟网元承担的业务切换到所述多个备份网元。
  3. 根据权利要求1所述的方法，其中，在根据预设策略将所述虚拟网元承担的业务切换到备份网元之后，所述方法还包括以下之一：重启所述虚拟网元、删除所述虚拟网元、重建所述虚拟网元。
  4. 根据权利要求1所述的方法，其中，在根据预设策略将所述虚拟网元承担的业务切换到备份网元之前，所述方法还包括：
    在所述虚拟网元的虚拟网络功能描述符VNFD和/或网络服务描述符NSD中添加用于指示所述虚拟网元是否需要备份的指定策略；
    在所述虚拟网元的实例化过程中，根据所述指定策略配置所述预设策略的相关数据。
  5. 根据权利要求2所述的方法，其中，从与所述虚拟网元对应的备份网元组中确定一个备份网元包括以下之一：
    将所述备份网元组的所有网元中当前业务量最少的网元确定为所述备份网元；
    将所述备份网元组的所有网元中距离所述虚拟网元最近的网元确定为所述备份网元。
  6. 根据权利要求1所述的方法，其中，在根据预设策略将所述虚拟网元承担的业务切换到备份网元之前，所述方法还包括：
    为所述虚拟网元建立备份关系表，所述备份关系表用于描述所述虚拟网元与所述备份网元的对应关系；或者，
    在所述虚拟网元的管理对象中添加所述备份网元的信息。
  7. 根据权利要求6所述的方法，其中，所述备份关系表包括：所述虚拟网元的标识、所述备份网元的标识、所述虚拟网元与所述备份网元的对应关系。
  8. 根据权利要求6所述的方法，其中，
    在所述虚拟网元对应一个备份网元时，所述备份网元的信息包括：所述虚拟网元的备份网元的标识信息；或，
    在所述虚拟网元对应备份网元组时，所述备份网元的信息包括：所述虚拟网元的备份网元组中各个备份网元的标识信息。
  9. 根据权利要求8所述的方法，其中，所述备份网元的信息还包括：用于表征所述虚拟网元是否存在备份网元的属性信息。
  10. 一种虚拟网元的管理装置，包括：
    确定模块，设置为确定虚拟网元出现故障，其中，所述虚拟网元通过网络功能虚拟化NFV技术实现；
    切换模块，设置为根据预设策略将所述虚拟网元承担的业务切换 到备份网元。
  11. 根据权利要求10所述的装置，其中，所述切换模块包括以下之一：
    第一切换单元，设置为确定与所述虚拟网元对应的一个备份网元，并将所述虚拟网元承担的业务切换到所述备份网元；
    第二切换单元，设置为从与所述虚拟网元对应的备份网元组中确定一个备份网元，并将所述虚拟网元承担的业务切换到所述备份网元；
    第三切换单元，设置为确定与所述虚拟网元对应的多个备份网元，将所述虚拟网元承担的业务切换到所述多个备份网元。
  12. 根据权利要求10所述的装置，其中，所述装置还包括：
    处理模块，设置为在所述切换模块根据预设策略将所述虚拟网元承担的业务切换到备份网元之后，执行以下操作之一：重启所述虚拟网元、删除所述虚拟网元、重建所述虚拟网元。
  13. 根据权利要求10所述的装置，其中，所述装置还包括：
    第一添加模块，设置为在所述切换模块根据预设策略将所述虚拟网元承担的业务切换到备份网元之前，在所述虚拟网元的虚拟网络功能描述符VNFD和/或网络服务描述符NSD中添加用于指示所述虚拟网元是否需要备份的指定策略；
    配置模块，设置为在所述虚拟网元的实例化过程中，根据所述指定策略配置所述预设策略的相关数据。
  14. 根据权利要求11所述的装置，其中，所述第二切换单元还设置为：
    将所述备份网元组的所有网元中当前业务量最少的网元确定为所述备份网元；或，
    将所述备份网元组的所有网元中距离所述虚拟网元最近的网元确定为所述备份网元。
  15. 根据权利要求10所述的装置，其中，所述装置还包括：
    建立模块，设置为在根据预设策略将所述虚拟网元承担的业务切换到备份网元之前，为所述虚拟网元建立备份关系表，所述备份关系表用于描述所述虚拟网元与所述备份网元的对应关系；或者，
    第二添加模块，设置为在所述虚拟网元的管理对象中添加所述备份网元的信息。
PCT/CN2017/095517 2016-08-04 2017-08-01 虚拟网元的管理方法及装置 WO2018024204A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610635077.5A CN107689879A (zh) 2016-08-04 2016-08-04 虚拟网元的管理方法及装置
CN201610635077.5 2016-08-04

Publications (1)

Publication Number Publication Date
WO2018024204A1 true WO2018024204A1 (zh) 2018-02-08

Family

ID=61072688

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/095517 WO2018024204A1 (zh) 2016-08-04 2017-08-01 虚拟网元的管理方法及装置

Country Status (2)

Country Link
CN (1) CN107689879A (zh)
WO (1) WO2018024204A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111542064A (zh) * 2020-04-22 2020-08-14 中国科学院计算技术研究所 一种用于无线接入网的容器编排管理系统及编排方法
US10880370B2 (en) 2018-11-27 2020-12-29 At&T Intellectual Property I, L.P. Virtual network manager system

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108616394B (zh) * 2018-04-25 2021-03-02 电子科技大学 一种虚拟网络功能备份和部署方法
CN111352690B (zh) * 2018-12-21 2023-05-02 中国电信股份有限公司 虚拟网元的管理方法、装置及计算机可读存储介质
CN112749041B (zh) * 2019-10-29 2023-12-26 中国移动通信集团浙江有限公司 虚拟化网络功能备份策略自决策方法、装置及计算设备
CN112187533B (zh) * 2020-09-18 2023-04-18 北京浪潮数据技术有限公司 一种虚拟网络设备防御方法、装置、电子设备和介质
CN115396930B (zh) * 2022-08-19 2024-05-03 中国联合网络通信集团有限公司 容灾处理方法、装置及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101426306A (zh) * 2008-10-24 2009-05-06 中国移动通信集团山东有限公司 一种容灾切换方法、系统及装置
CN104980297A (zh) * 2014-04-14 2015-10-14 中兴通讯股份有限公司 虚拟机资源的变更方法、装置及虚拟网络功能设备
CN105591801A (zh) * 2015-08-11 2016-05-18 杭州华三通信技术有限公司 一种虚拟网络功能vnf故障处理方法及vnf管理设备
CN106254100A (zh) * 2016-07-27 2016-12-21 腾讯科技（深圳）有限公司 一种数据容灾方法、装置和系统

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100444534C (zh) * 2004-09-06 2008-12-17 中兴通讯股份有限公司 通讯系统中多数据区的冗余备份方法及装置
CN101052208B (zh) * 2006-04-06 2010-10-20 华为技术有限公司 一种切换方法及切换网络
CN101635638B (zh) * 2008-07-25 2012-10-17 中兴通讯股份有限公司 一种容灾系统及其容灾方法
CN104735101B (zh) * 2013-12-19 2019-11-26 中兴通讯股份有限公司 网络资源的共享处理、共享方法及装置、系统
CN104866395B (zh) * 2014-02-24 2017-11-21 中国移动通信集团福建有限公司 数据备份方法及系统、主备切换方法及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101426306A (zh) * 2008-10-24 2009-05-06 中国移动通信集团山东有限公司 一种容灾切换方法、系统及装置
CN104980297A (zh) * 2014-04-14 2015-10-14 中兴通讯股份有限公司 虚拟机资源的变更方法、装置及虚拟网络功能设备
CN105591801A (zh) * 2015-08-11 2016-05-18 杭州华三通信技术有限公司 一种虚拟网络功能vnf故障处理方法及vnf管理设备
CN106254100A (zh) * 2016-07-27 2016-12-21 腾讯科技（深圳）有限公司 一种数据容灾方法、装置和系统

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10880370B2 (en) 2018-11-27 2020-12-29 At&T Intellectual Property I, L.P. Virtual network manager system
US11451624B2 (en) 2018-11-27 2022-09-20 At&T Intellectual Property I, L.P. Virtual network manager system
CN111542064A (zh) * 2020-04-22 2020-08-14 中国科学院计算技术研究所 一种用于无线接入网的容器编排管理系统及编排方法
CN111542064B (zh) * 2020-04-22 2023-03-21 中国科学院计算技术研究所 一种用于无线接入网的容器编排管理系统及编排方法

Also Published As

Publication number Publication date
CN107689879A (zh) 2018-02-13

Similar Documents

Publication Publication Date Title
WO2018024204A1 (zh) 虚拟网元的管理方法及装置
US20210326167A1 (en) Vnf service instantiation method and apparatus
EP3291499B1 (en) Method and apparatus for network service capacity expansion
US11163607B2 (en) Method for associating NS with VNF, apparatus, and system
EP3800926B1 (en) Alarm method and device
CN107209710B (zh) 节点系统、服务器设备、缩放控制方法和程序
US10326653B2 (en) Method for upgrading network functions virtualization application, service forwarding method, and apparatus
CN106301876B (zh) 物理机升级方法、业务迁移方法及装置
US20190230004A1 (en) Network slice management method and management unit
US20180067830A1 (en) Healing cloud services during upgrades
JP2021508997A (ja) ネットワーク・スライスの展開方法および装置
US10965552B2 (en) Method and apparatus for managing virtualized network function
CN108011846B (zh) 网络功能虚拟化架构中管理业务的方法及装置
CN106664216A (zh) 一种切换vnf的方法和装置
WO2017121153A1 (zh) 软件升级方法及装置
CN110262893A (zh) 配置镜像内存的方法、装置及计算机存储介质
CN112218342A (zh) 一种实现核心网子切片容灾的方法、装置和系统
CN108319492B (zh) 复位物理机的方法、装置与系统
CN104468759A (zh) PaaS平台中实现应用迁移的方法和装置
CN112015515B (zh) 一种虚拟网络功能的实例化方法及装置
US20180069768A1 (en) Method and apparatus for establishing interface between vnfms, and system
CN106792843B (zh) 一种设备管理方法及装置
CN116414915A (zh) 分布式数据库集群的管控方法、装置和数据库管控平台
WO2017080499A1 (zh) 管理指示发送、vnf自动伸缩功能的管理方法及装置
WO2019011180A1 (zh) 一种License的发送方法和装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17836386

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17836386

Country of ref document: EP

Kind code of ref document: A1