WO2017000260A1 - 一种切换vnf的方法和装置 - Google Patents

一种切换vnf的方法和装置 Download PDF

Info

Publication number
WO2017000260A1
WO2017000260A1 PCT/CN2015/082997 CN2015082997W WO2017000260A1 WO 2017000260 A1 WO2017000260 A1 WO 2017000260A1 CN 2015082997 W CN2015082997 W CN 2015082997W WO 2017000260 A1 WO2017000260 A1 WO 2017000260A1
Authority
WO
WIPO (PCT)
Prior art keywords
vnf
affinity group
backup
primary
affinity
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.)
Ceased
Application number
PCT/CN2015/082997
Other languages
English (en)
French (fr)
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.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP15896791.9A priority Critical patent/EP3300298B1/en
Priority to CN201580032742.5A priority patent/CN106664216B/zh
Priority to PCT/CN2015/082997 priority patent/WO2017000260A1/zh
Priority to JP2017565253A priority patent/JP6466003B2/ja
Publication of WO2017000260A1 publication Critical patent/WO2017000260A1/zh
Priority to US15/853,958 priority patent/US10644952B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
    • 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/0894—Policy-based network configuration management
    • 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/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow 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/40—Arrangements 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
    • 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/04—Network management architectures or arrangements
    • H04L41/046—Network management architectures or arrangements comprising network management agents or mobile agents therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method and apparatus for switching a virtualized network function (English: Virtualised Network Function, VNF for short).
  • a virtualized network function English: Virtualised Network Function, VNF for short.
  • NFV Network Function Virtualization
  • affinity policies English: Affinity
  • anti-affinity strategies English: Anti-affinity
  • affinity policy is used to ensure that the VNF is deployed to one of the specified host sets
  • anti-affinity policy is used to ensure that different VNFs in the same VNF set are deployed to different hosts.
  • a high availability (High Availability, HA for short) clustering mechanism is needed to ensure the continuity of VNF services on a host failure.
  • the affinity policy limits that a VNF can only be deployed on a specified host. Once the host fails, the VNF on the host cannot be switched to the backup. On the host. Therefore, there is a need for a solution that is incompatible with the HA mechanism in the NFV scenario.
  • the embodiment of the invention provides a method and a device for switching a VNF, which are used to solve the problem that the affinity policy is incompatible with the HA mechanism in the NFV scenario.
  • an embodiment of the present invention provides a method for switching a VNF, including:
  • the MANO receives a fault message, and the fault message is used to indicate that the first VNF is faulty;
  • the MANO determines a primary affinity group to which the first VNF belongs, and a backup affinity group of the primary affinity group; a VNF in the backup affinity group and the primary affinity group VNF in One-to-one correspondence, the affinity group represents a set of VNFs using an affinity strategy;
  • the MANO causes the VNF in the backup affinity group to continue processing the traffic of the VNF in the primary affinity group.
  • the MANO comprises NFVO and VNFM;
  • the MANO receives the fault message, including:
  • the MANO determines a primary affinity group to which the first VNF belongs and a backup affinity group of the primary affinity group, including:
  • the NFVO determines a primary affinity group to which the first VNF belongs and a backup affinity group of the primary affinity group.
  • the NFVO determines a primary affinity group to which the first VNF belongs, and the primary affinity After the backup affinity group of the sex group, the method further includes:
  • the NFVO changes an attribute of the backup affinity group and the VNF in the backup affinity group to a primary attribute.
  • the fault message is detected by a proxy of the backup affinity group by a heartbeat mechanism Reporting to the VNFM after the first VNF failure;
  • the fault message is reported by the NFVI to the virtualized infrastructure management VIM after detecting the fault in the NFVI that will affect the operation of the first VNF, and then reported by the VIM to the VNFM; or
  • the fault message is notified by the NFVI to the first VNF after detecting a fault in the NFVI that will affect the operation of the first VNF, and then reported by the first VNF to the VNFM.
  • the VNF distribution in the affinity group On one host, or on multiple hosts.
  • an embodiment of the present invention provides an apparatus for switching a VNF, including:
  • a receiving unit configured to receive a fault message, where the fault message is used to indicate a first VNF that fails;
  • a determining unit configured to determine a primary affinity group to which the first VNF belongs, and a backup affinity group of the primary affinity group; and a VNF in the backup affinity group and the primary affinity
  • the VNFs in the sexual group correspond one-to-one, and the affinity group represents a collection of VNFs using an affinity strategy;
  • a switching unit configured to enable the VNF in the backup affinity group to continue processing the service of the VNF in the primary affinity group.
  • the receiving unit is specifically configured to:
  • the device further includes:
  • an update unit configured to change an attribute of the backup affinity group and the VNF in the backup affinity group to a primary attribute.
  • the fault message is detected by a proxy of the backup affinity group by a heartbeat mechanism Reporting to the VNFM after the first VNF failure;
  • the fault message is reported by the NFVI to the virtualized infrastructure management VIM after detecting the fault in the NFVI that will affect the operation of the first VNF, and then reported by the VIM to the VNFM; or
  • the fault message is notified by the NFVI to the first VNF after detecting a fault in the NFVI that will affect the operation of the first VNF, and then reported by the first VNF to the VNFM.
  • the VNF distribution in the affinity group On one host, or on multiple hosts.
  • the affinity policy and the NFV scenario can be solved.
  • the HA mechanism is not compatible, and the management of the affinity policy and the active/standby switchover is centralized to MANO, which avoids the decentralization of control capabilities.
  • FIG. 1 is a schematic structural diagram of a system of an NFV system according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of deployment of an active and standby node according to an embodiment of the present invention
  • FIG. 3 is a flowchart of a method for switching a VNF according to an embodiment of the present invention
  • FIG. 4 is a schematic diagram of a VNF in an affinity group distributed on a host according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of VNFs in an affinity group on different hosts according to an embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of an apparatus for switching a VNF according to an embodiment of the present invention.
  • Embodiments of the present invention provide a method and apparatus for switching a VNF.
  • the NFV Management and Orchestration System (English: NFV Management and Orchestration System, abbreviated :NFV-MANO) triggers the switching of all VNFs in this affinity group.
  • the method and the device are based on the same inventive concept. Since the principles of the method and the device for solving the problem are similar, the implementation of the device and the method can be referred to each other, and the repeated description is not repeated.
  • an embodiment of the present invention provides a system architecture diagram of an NFV system, where the NFV system can be implemented through multiple networks, such as a data center network, a service provider network, or a local area network (English: Local Area) Network, referred to as: LAN).
  • networks such as a data center network, a service provider network, or a local area network (English: Local Area) Network, referred to as: LAN).
  • the NFV system can include NFV-MANO101, NFV infrastructure (English: NFV Infrastructure, referred to as: NFVI) 102, multiple VNFs 103, multiple element management systems (English: element management system, EMS) 104, service, VNF and infrastructure description (English: Service VNF and Infrastructure Description) system 105, And one or more operational support systems/business support systems (English: Operation Support System/Business Support System, OSS/BSS) 106.
  • NFV-MANO101 NFV infrastructure
  • NFVI NFV Infrastructure
  • EMS element management system
  • service VNF and infrastructure description
  • service Service VNF and Infrastructure Description
  • operational support systems/business support systems English: Operation Support System/Business Support System, OSS/BSS
  • the NFV-MANO 101 may include a Network Function Virtualization Orchestrator (NFVO) 107, one or more virtualized network function management (English: Virtualised Network Function Manager, VNFM) 108, And one or more Virtualized Infrastructure Manager (VIM) 109; the NFVI 102 can include a computing hardware 110, a storage hardware 111, a hardware resource layer composed of network hardware 112, a virtualization layer, and a virtual A virtual resource layer composed of 113 (e.g., virtual machine), virtual storage 114, and virtual network 115 is calculated.
  • NFVO Network Function Virtualization Orchestrator
  • VNFM Virtualised Network Function Manager
  • VIP Virtualized Infrastructure Manager
  • the computing hardware 110 in the hardware resource layer can be a dedicated processor or a general purpose processor for providing processing and computing functions; the storage hardware 111 can be used to provide storage capabilities, which can be provided by the storage hardware 111 itself (eg The local memory of a server can also be provided through a network (for example, a server connects to a network storage device through a network); the network hardware 112 can be a switch, a router, and/or other network device, and the network hardware 112 is used to implement multiple devices. Communication between multiple devices via wireless or wired connection.
  • the virtualization layer in NFVI 102 is used to abstract the hardware resources of the hardware resource layer, decouple the VNF 103 from the physical layer to which the hardware resources belong, and provide virtual resources to the VNF 103.
  • the virtual resource layer may include virtual computing 113, virtual storage 114, and virtual network 115.
  • the virtual computing 113, the virtual storage 114 may be provided to the VNF 103 in the form of a virtual machine or other virtual container, for example, one or more VNFs 103 may be deployed on a virtual machine.
  • the virtualization layer forms a virtual network 115 through abstract network hardware 112.
  • a virtual network 115 such as a virtual switch (English: Vswitches), is used to implement communication between multiple virtual machines, or between other types of virtual containers hosting VNFs.
  • Virtualization of network hardware can be through virtual LAN (English: Vritual LAN, referred to as: VLAN), virtual private LAN service (English: Virtual Private LAN Service, Jane It is called VPLS, virtual eXtensible Local Area Network (VxLAN) or Nerwork Virtualization using Generic Routing Encapsulation (NVGRE).
  • VLAN Virtual Local Area Network
  • NVGRE Generic Routing Encapsulation
  • OSS/BSS106 is mainly for telecom service operators, providing comprehensive network management and service operation functions, including network management (such as fault monitoring, network information collection, etc.), billing management, and customer service management.
  • network management such as fault monitoring, network information collection, etc.
  • billing management billing management
  • customer service management customer service management.
  • the service, VNF, and infrastructure description system 105 is described in detail in the ETSI GS NFV 002 v1.1.1 standard, and details are not described herein again.
  • the NFV-MANO101 can be used to monitor and manage VNF103 and NFVI102.
  • the NFVO 107 can communicate with one or more VNFMs 108 to implement resource related requests, send configuration information to the VNFM 108, and collect status information for the VNF 103.
  • the NFVO 107 can also communicate with the VIM 109 to enable resource allocation, and/or to implement configuration and status information reservation and exchange of virtualized hardware resources.
  • the VNFM 108 can communicate with the VNF 103 and the EMS 104 under the direction of the NFVO 107 to perform VNF 103 lifecycle management and implement the exchange of configuration/status information, ie, responsible for the creation, deletion, start, stop, etc. of the VNF 103.
  • the VIM 109 can be used to control and manage the interaction of the VNF 103 with the computing hardware 110, the storage hardware 111, the network hardware 112, the virtual computing 113, the virtual storage 114, and the virtual network 115.
  • VIM 109 can be used to perform resource allocation operations to VNF 103.
  • the VNFM 108 and VIM 109 can communicate with one another to exchange virtualized hardware resource configuration and status information.
  • the NFVI 102 includes both hardware and software that together create a virtualized environment to deploy, manage, and execute the VNF 103.
  • the hardware resource layer and the virtual resource layer are used to provide virtual resources, such as virtual machines and/or other forms of virtual containers, to the various VNFs 103.
  • the VNF 103 is a virtualization of at least one network function that was previously provided by a physical network device.
  • the VNF 103 may be a virtualized Mobility Management Entity (MME) node for providing all network functions provided by a typical non-virtualized MME device.
  • MME Mobility Management Entity
  • the VNF 103 can be used to implement the functionality of some of the components provided on the non-virtualized MME device.
  • One or more VNFs 103 can be deployed on a virtual machine (or other form of virtual container).
  • EMS104 Can be used to manage one or more VNF103.
  • a set of VNFs having a certain relationship is called an affinity group.
  • affinity strategy or anti-affinity strategy
  • a set of VNFs having a certain relationship is called an affinity group.
  • the management of the affinity policy is controlled by NFVO107, which is only responsible for executing the instructions issued by NFVO107.
  • the embodiment of the present invention also uses the HA mechanism.
  • the active and standby nodes are deployed in units of affinity groups, and each affinity group includes Several VNFs, the primary affinity group and the backup affinity group need to be deployed on different hosts, and any VNF in the primary affinity group has a VNF corresponding to it in the backup affinity group, as shown in FIG. 2 VNF1 in the middle affinity group corresponds to VNF1' in the backup affinity group, and VNFn corresponds to VNFn'.
  • the VNF in each affinity group can be monitored by the agent (English: Agent), and the agent of the backup affinity group detects whether the VNF in the primary affinity group is faulty through the heartbeat mechanism; or, each affinity VNF in the sexual group can also be monitored by the NFVI detection mechanism of the upper layer of NFVI.
  • Agent International: Agent
  • each affinity VNF in the sexual group can also be monitored by the NFVI detection mechanism of the upper layer of NFVI.
  • the primary and backup relationships of the VNF 103 are managed by the NFVO 107, which is not perceived by the VIM 109.
  • An embodiment of the present invention provides a method for switching a VNF. As shown in FIG. 3, the implementation process of the method is as follows:
  • Step 301 The MANO receives a fault message, and the fault message is used to indicate the first VNF that has failed.
  • Step 302 The MANO determines a primary affinity group to which the first VNF belongs, and a backup affinity group of the primary affinity group; and the VNF in the backup affinity group and the primary parent
  • the VNFs in the sex group correspond one-to-one, and the affinity group represents a collection of VNFs using an affinity strategy.
  • Step 303 The MANO causes the VNF in the backup affinity group to continue processing the service of the VNF in the primary affinity group.
  • the MANO can be split into two functional modules: NFVO and VNFM.
  • the specific implementation process of steps 301-303 is as follows:
  • the NFVO receives the fault message reported by the VNFM, and then the NFVO determines a primary affinity group to which the first VNF belongs, and a backup affinity group of the primary affinity group, and finally the NFVO order The VNF in the backup affinity group continues to process the traffic of the VNF in the primary affinity group.
  • the fault message may be reported to the VNFM in the following three manners:
  • the fault message may be reported to the VNFM by the agent of the backup affinity group after detecting the first VNF fault by using a heartbeat mechanism.
  • the fault message may be reported by the NFVI to the VIM after detecting the fault in the NFVI that will affect the operation of the first VNF, and then reported by the VIM to the VNFM.
  • the fault message may be notified by the NFVI to the first VNF after detecting a fault in the NFVI that will affect the operation of the first VNF, and then reported by the first VNF to the VNFM.
  • the NFVI detects that the resource in the NFVI has failed by its own detection mechanism, and the fault may cause the first VNF to fail to run or degrade after a certain time.
  • the heartbeat mechanism between the active and standby affinity groups has not detected the fault at the current time. Therefore, the fault message can be reported through NFVI ⁇ VIM ⁇ VNFM or NFVI ⁇ VNF ⁇ VNFM related to the fault.
  • the embodiment of the present invention selects an overall handover of all VNFs in the primary affinity group.
  • the VNF in the backup affinity group is taken over by the VNF in the primary affinity group, and the handover process may be implemented by updating the forwarding path, that is, the NFVO notifies the VIM (or software definition).
  • the network controller deletes a forwarding path between each VNF in the primary affinity and the respective service object, and establishes a new forwarding path between the corresponding VNFs of the service objects and the backup affinity; or Virtual Internet Protocol (English: Internet Protocol, Abbreviation: IP) is implemented by switching the virtual IP of each VNF in the primary affinity group to the corresponding VNF in the backup affinity.
  • Virtual Internet Protocol English: Internet Protocol, Abbreviation: IP
  • the NFVO may further use the backup affinity group in a database.
  • the attribute of the VNF in the backup affinity group is changed to a primary attribute.
  • the VNFs in the affinity group may be distributed on one host, for example, as shown in FIG. 4, affinity group 1 and affinity. All VNFs in group 2 are deployed on host 1, and all VNFs in backup affinity group 1 and backup affinity group 2 are deployed on host 2.
  • the VNFs in the affinity group may also be distributed on multiple hosts. For example, as shown in FIG. 5, the VNFs in the affinity group 1 are distributed on the host 1 and the host 2, and the backup affinity group is The VNFs within 1 are distributed on the host 3 and the host 4.
  • an embodiment of the present invention provides a device for switching a VNF, which is used to implement the method for switching a VNF shown in FIG. 3 of the present invention.
  • the device may be located in a MANO, and the device includes:
  • the receiving unit 601 is configured to receive a fault message, where the fault message is used to indicate the first VNF that fails.
  • a determining unit 602 configured to determine a primary affinity group to which the first VNF belongs, and a backup affinity group of the primary affinity group; and the VNF in the backup affinity group and the primary parent
  • the VNFs in the sex group correspond one-to-one, and the affinity group represents a collection of VNFs using an affinity strategy.
  • the switching unit 603 is configured to enable the VNF in the backup affinity group to continue processing the service of the VNF in the primary affinity group.
  • the receiving unit 601 is specifically configured to receive a fault message reported by the VNFM.
  • the device further includes:
  • the updating unit 604 is configured to change an attribute of the backup affinity group and the VNF in the backup affinity group to a primary attribute.
  • the fault message may be reported to the VNFM by the agent of the backup affinity group after detecting the first VNF fault by using a heartbeat mechanism; or the fault message may be The NFVI is reported to the virtualized infrastructure management VIM after the failure of the NFVI to affect the operation of the first VNF, and is reported to the VNFM by the VIM; or the failure message may be The NFVI notifies the first VNF after detecting a fault in the NFVI that will affect the operation of the first VNF, and then reports the first VNF to the VNFM.
  • the VNFs in the affinity group are distributed on one host or distributed on multiple hosts.
  • the technical solution provided by the embodiment of the present invention when the MANO receives the fault message related to a certain VNF in the affinity group, triggers the switching of all the VNFs in the affinity group at the first time, thereby
  • the problem that the affinity policy is incompatible with the HA mechanism in the NFV scenario is solved, and the management of the affinity policy and the active/standby switchover is centralized to MANO, which avoids the decentralization of control capabilities.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the device is implemented in a flow chart or Multiple processes and/or block diagrams The functions specified in one or more boxes.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

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

Abstract

本发明公开了一种切换虚拟化网络功能VNF的方法和装置，用于解决在NFV场景下，亲和性策略与HA机制不能兼容的问题。该方法为：MANO接收故障消息，所述故障消息用于指示发生故障的第一VNF；所述MANO确定所述第一VNF所属的主亲和性组，以及所述主亲和性组的备份亲和性组；所述备份亲和性组中的VNF与所述主亲和性组中的VNF一一对应，所述亲和性组表示采用亲和性策略的VNF的集合；所述MANO令所述备份亲和性组中的VNF继续处理所述主亲和性组中的VNF的业务。

Description

一种切换VNF的方法和装置 技术领域
本发明涉及通信技术领域，尤其涉及一种切换虚拟化网络功能(英文：Virtualised Network Function，简称：VNF)的方法和装置。
背景技术
在网络功能虚拟化(英文：Network Functions Virtualization，简称：NFV)技术中，允许用户显式地为VNF的集合指定策略，包括亲和性策略(英文：Affinity)和反亲和性策略(英文：Anti-affinity)，其中，亲和性策略用于保证VNF被部署到指定主机集合中的一台，反亲和性策略用于保证同一个VNF集合中的不同VNF被部署到不同的主机上。
而考虑到电信级业务的高可用与连续性要求，需要使用高可用性(英文：High Available，简称：HA)群集机制来确保在某一主机故障的情况下其上的VNF业务的连续性。
但是在指定了亲和性策略的NFV场景下，由于亲和性策略限制了一个VNF只能部署在一个指定的主机上，而一旦该主机发生故障，那么该主机上的VNF将无法切换到备份主机上。因此，需要一种在NFV场景下能够解决亲和性策略与HA机制不兼容的方案。
发明内容
本发明实施例提供了一种切换VNF的方法和装置，用以解决在NFV场景下亲和性策略与HA机制不兼容的问题。
第一方面，本发明实施例提供了一种切换VNF的方法，包括：
MANO接收故障消息，所述故障消息用于指示发生故障的第一VNF；
所述MANO确定所述第一VNF所属的主亲和性组，以及所述主亲和性组的备份亲和性组；所述备份亲和性组中的VNF与所述主亲和性组中的VNF 一一对应，所述亲和性组表示采用亲和性策略的VNF的集合；
所述MANO令所述备份亲和性组中的VNF继续处理所述主亲和性组中的VNF的业务。
结合第一方面，在第一方面的第一种可能的实现方式中，所述MANO包括NFVO和VNFM；
所述MANO接收故障消息，包括：
所述NFVO接收所述VNFM上报的故障消息；
所述MANO确定所述第一VNF所属的主亲和性组以及所述主亲和性组的备份亲和性组，包括：
所述NFVO确定所述第一VNF所属的主亲和性组以及所述主亲和性组的备份亲和性组。
结合第一方面的第一种可能的实现方式，在第一方面的第二种可能的实现方式中，所述NFVO确定所述第一VNF所属的主亲和性组，以及所述主亲和性组的备份亲和性组之后，所述方法还包括：
所述NFVO将所述备份亲和性组及所述备份亲和性组中的VNF的属性更改为主属性。
结合第一方面的第一种或第二种可能的实现方式，在第一方面的第三种可能的实现方式中，所述故障消息由所述备份亲和性组的代理在通过心跳机制检测到所述第一VNF故障后上报给所述VNFM；或者，
所述故障消息由NFVI在检测到所述NFVI内将影响所述第一VNF运行的故障后上报给虚拟化的基础设施管理VIM，再由所述VIM上报给所述VNFM；或者，
所述故障消息由所述NFVI在检测到所述NFVI内将影响所述第一VNF运行的故障后通知所述第一VNF，再由所述第一VNF上报给所述VNFM。
结合第一方面和第一方面的第一种至第三种可能的实现方式中的任意一种，在第一方面的第四种可能的实现方式中，所述亲和性组中的VNF分布在一个主机上，或者分布在多个主机上。
第二方面，本发明实施例提供了一种切换VNF的装置，包括：
接收单元，用于接收故障消息，所述故障消息用于指示发生故障的第一VNF；
确定单元，用于确定所述第一VNF所属的主亲和性组，以及所述主亲和性组的备份亲和性组；所述备份亲和性组中的VNF与所述主亲和性组中的VNF一一对应，所述亲和性组表示采用亲和性策略的VNF的集合；
切换单元，用于令所述备份亲和性组中的VNF继续处理所述主亲和性组中的VNF的业务。
结合第二方面，在第二方面的第一种可能的实现方式中，所述接收单元具体用于：
接收VNFM上报的故障消息。
结合第二方面的第一种可能的实现方式，在第二方面的第二种可能的实现方式中，所述装置还包括：
更新单元，用于将所述备份亲和性组及所述备份亲和性组中的VNF的属性更改为主属性。
结合第二方面的第一种或第二种可能的实现方式，在第二方面的第三种可能的实现方式中，所述故障消息由所述备份亲和性组的代理在通过心跳机制检测到所述第一VNF故障后上报给所述VNFM；或者，
所述故障消息由NFVI在检测到所述NFVI内将影响所述第一VNF运行的故障后上报给虚拟化的基础设施管理VIM，再由所述VIM上报给所述VNFM；或者，
所述故障消息由所述NFVI在检测到所述NFVI内将影响所述第一VNF运行的故障后通知所述第一VNF，再由所述第一VNF上报给所述VNFM。
结合第二方面和第二方面的第一种至第三种可能的实现方式中的任意一种，在第二方面的第四种可能的实现方式中，所述亲和性组中的VNF分布在一个主机上，或者分布在多个主机上。
利用本发明实施例提供的方案，可以解决在NFV场景下，亲和性策略与 HA机制不能兼容的问题，并且将对亲和性策略和主备切换的管理集中到了MANO，避免了控制能力的下放。
附图说明
图1为本发明实施例提供的NFV系统的系统架构示意图；
图2为本发明实施例提供的主备节点的部署示意图；
图3为本发明实施例提供的一种切换VNF的方法的流程图；
图4为本发明实施例中亲和性组中的VNF分布在一个主机上的示意图；
图5为本发明实施例中亲和性组中的VNF分别在不同主机上的示意图；
图6为本发明实施例提供的一种切换VNF的装置的结构示意图。
具体实施方式
为了使本发明的目的、技术方案和优点更加清楚，下面将结合附图对本发明作进一步地详细描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例，都属于本发明保护的范围。
本发明实施例提供了一种切换VNF的方法和装置，当接收到与亲和性组中的某个VNF相关的故障消息时，由NFV管理和编制系统(英文：NFV Management and Orchestration System，简称：NFV-MANO)触发该亲和性组中所有VNF的切换。其中，方法和装置是基于同一发明构思的，由于方法及装置解决问题的原理相似，因此装置与方法的实施可以相互参见，重复之处不再赘述。
参阅图1所示，本发明实施例提供了一种NFV系统的系统架构示意图，其中，该NFV系统可以通过多种网络实现，例如数据中心网络、服务提供者网络、或者局域网(英文：Local Area Network，简称：LAN)。如图1所示，该NFV系统可以包括NFV-MANO101，NFV基础设施(英文：NFV  Infrastructure，简称：NFVI)102，多个VNF103，多个网元管理系统(英文：element management system，简称：EMS)104，服务、VNF和基础设施描述(英文：Service VNF and Infrastructure Description)系统105，以及一个或多个运营支撑系统/业务支撑系统(英文：Operation Support System/Business Support System，简称：OSS/BSS)106。
NFV-MANO 101可以包括网络功能虚拟化编排器(英文：Network Function Virtualization Orchestrator，简称：NFVO)107、一个或多个虚拟化的网络功能管理(英文：Virtualised Network Function Manager，简称：VNFM)108，以及一个或多个虚拟化基础设施管理器(英文：Virtualized Infrastructure Manager，简称VIM)109；NFVI 102可以包括计算硬件110、存储硬件111、网络硬件112组成的硬件资源层、虚拟化层、以及虚拟计算113(例如虚拟机)、虚拟存储114和虚拟网络115组成的虚拟资源层。
硬件资源层中的计算硬件110可以为专用的处理器或通用的用于提供处理和计算功能的处理器；存储硬件111用于提供存储能力，该存储能力可以是存储硬件111本身提供的(例如一台服务器的本地内存)，也可以通过网络提供(例如服务器通过网络连接一个网络存储设备)；网络硬件112可以是交换机、路由器和/或其他网络设备，网络硬件112用于实现多个设备之间的通信，多个设备之间通过无线或有线连接。
NFVI 102中的虚拟化层用于抽象硬件资源层的硬件资源，将VNF 103和硬件资源所属的物理层解耦，向VNF 103提供虚拟资源。
虚拟资源层可以包括虚拟计算113、虚拟存储114和虚拟网络115。虚拟计算113、虚拟存储114可以以虚拟机或其他虚拟容器的形式向VNF 103提供，例如一个或多个VNF 103可以部署在一台虚拟机上。虚拟化层通过抽象网络硬件112形成虚拟网络115。虚拟网络115，例如虚拟交换机(英文：Vswitches)，用于实现多个虚拟机之间，或多个承载VNF的其他类型的虚拟容器之间的通信。网络硬件的虚拟化可以通过虚拟LAN(英文：Vritual LAN，简称：VLAN)、虚拟专用局域网业务(英文：Virtual Private LAN Service，简 称：VPLS)、虚拟可扩展局域网(英文：Virtual eXtensible Local Area Network，简称：VxLAN)或通用路由封装网络虚拟化(英文：Nerwork Virtualization using Generic Routing Encapsulation，简称：NVGRE)等技术实现。
OSS/BSS106主要面向电信服务运营商，提供综合的网络管理和业务运营功能，包括网络管理(例如故障监控、网络信息收集等)、计费管理以及客户服务管理等。服务、VNF和基础设施描述系统105在ETSI GS NFV 002v1.1.1标准中有详细介绍，本发明实施例在此不再赘述。
NFV-MANO101可以用于实现VNF103和NFVI102的监控和管理。NFVO107可以与一个或多个VNFM108进行通信以实现与资源相关的请求、发送配置信息给VNFM108、以及收集VNF103的状态信息。另外，NFVO107还可以与VIM 109进行通信以实现资源分配，和/或，实现虚拟化硬件资源的配置信息和状态信息的预留和交换。VNFM108可以在NFVO107的指挥下与VNF103和EMS104通信以执行VNF 103生命周期管理和实现配置/状态信息的交换，即负责VNF 103的创建、删除、启动、停止等。VIM109可以用于控制和管理VNF 103和计算硬件110、存储硬件111、网络硬件112、虚拟计算113、虚拟存储114、虚拟网络115的交互。例如，VIM109可以用于执行资源向VNF103的分配操作。VNFM108和VIM109可以互相通信以交换虚拟化硬件资源配置和状态信息。
NFVI102包含硬件和软件，二者共同建立虚拟化环境以部署、管理和执行VNF 103。换句话说，硬件资源层和虚拟资源层用于向各个VNF103提供虚拟资源，例如虚拟机和/或其他形式的虚拟容器。
VNF103是至少一个网络功能的虚拟化，该网络功能之前是由物理网络设备提供的。在一种实现方式下，VNF103可以是一个虚拟化的移动管理实体(英文：Mobility Management Entity，简称：MME)节点，用于提供典型的非虚拟化的MME设备提供的所有网络功能。在另一种实现方式下，VNF103可以用于实现非虚拟化的MME设备上提供的全部组件中的部分组件的功能。一个虚拟机(或其他形式的虚拟容器)上可以部署有一个或多个VNF103。EMS104 可以用于管理一个或多个VNF103。
本发明实施例将同一个策略(亲和性策略或反亲和性策略)下，存在一定关系的VNF的集合称为亲和性组。需要说明的是，本发明实施例中只关注VNF被实施了亲和性策略的这种情况。在图1中，亲和性策略的管理由NFVO107控制，VIM109只负责执行NFVO107下发的指令。
同时为了满足电信级业务的可用性和连续性要求，本发明实施例还使用了HA机制，如图2所示，主备节点以亲和性组为单位进行部署，每个亲和性组内包括若干VNF，主亲和性组和备份亲和性组需要部署在不同的主机上，主亲和性组中的任一VNF在备份亲和性组中均有一VNF与之相对应，如图2中主亲和性组中的VNF1对应于备份亲和性组中的VNF1’，VNFn对应于VNFn’。每个亲和性组内的VNF可以由代理(英文：Agent)负责监测，备份亲和性组的代理通过心跳机制来检测主亲和性组中的VNF是否发生故障；或者，每个亲和性组内的VNF也可以由上层的NFVI通过NFVI的检测机制进行监测。当主亲和性组中的任一VNF发生故障时，主亲和性组中的所有VNF当前正在处理的业务将分别交由备份亲和性组中对应的VNF继续处理。在图1中，VNF 103的主备关系由NFVO 107管理，VIM 109并不感知。
本发明实施例提供了一种切换VNF的方法，如图3所示，该方法的实施流程如下：
步骤301：MANO接收故障消息，所述故障消息用于指示发生故障的第一VNF。
步骤302：所述MANO确定所述第一VNF所属的主亲和性组，以及所述主亲和性组的备份亲和性组；所述备份亲和性组中的VNF与所述主亲和性组中的VNF一一对应，所述亲和性组表示采用亲和性策略的VNF的集合。
步骤303：所述MANO令所述备份亲和性组中的VNF继续处理所述主亲和性组中的VNF的业务。
可选的，所述MANO可以拆分为两个功能模块：NFVO和VNFM。步骤301-303的具体实现过程如下：
所述NFVO接收所述VNFM上报的故障消息，然后所述NFVO确定所述第一VNF所属的主亲和性组，以及所述主亲和性组的备份亲和性组，最后所述NFVO令所述备份亲和性组中的VNF继续处理所述主亲和性组中的VNF的业务。
可选的，所述故障消息可以通过以下三种方式上报给所述VNFM：
第一种实现方式：
所述故障消息可以由所述备份亲和性组的代理在通过心跳机制检测到所述第一VNF故障后上报给所述VNFM。
第二种实现方式：
所述故障消息可以由NFVI在检测到所述NFVI内将影响所述第一VNF运行的故障后上报给VIM，再由所述VIM上报给所述VNFM。
第三种实现方式：
所述故障消息可以由所述NFVI在检测到所述NFVI内将影响所述第一VNF运行的故障后通知所述第一VNF，再由所述第一VNF上报给所述VNFM。
在第二种和第三种实现方式下，所述NFVI通过自身的检测机制检测到了所述NFVI中的资源发生了故障，该故障可能导致一定时间后所述第一VNF无法运行或降级运行，但在当前时刻主备亲和性组之间的心跳机制还未检测到该故障，因此可以通过NFVI→VIM→VNFM或NFVI→与故障相关的VNF→VNFM两种途径上报故障消息。
考虑到只对主亲和性组内单个的VNF进行主备切换将违反亲和性策略对主机的限制，因此，本发明实施例选择对主亲和性组内的所有VNF作一个整体的切换，令所述备份亲和性组中的每个VNF分别接管所述主亲和性组中对应VNF的业务，切换过程具体可以通过更新转发路径的方式实现，即由NFVO通知VIM(或软件定义网络控制器)删除主亲和性中每个VNF与各自的业务对象之间的转发路径，以及在各业务对象和备份亲和性中对应的VNF之间建立新的转发路径；或者也可以通过虚拟互联网协议(英文：Internet Protocol， 简称：IP)的方式实现，即将主亲和性组中每个VNF的虚拟IP切换到备份亲和性中对应的VNF上。
可选的，在确定所述第一VNF所属的主亲和性组以及所述主亲和性组的备份亲和性组之后，所述NFVO还可以在数据库中将所述备份亲和性组及所述备份亲和性组中的VNF的属性更改为主属性。
可选的，所述亲和性组(主亲和性组或备份亲和性组)中的VNF可以分布在一个主机上，例如，如图4所示，亲和性组1以及亲和性组2内的所有VNF均部署在主机1上，备份亲和性组1以及备份亲和性组2内的所有VNF均部署在主机2上。或者，所述亲和性组中的VNF也可以分布在多个主机上，例如，如图5所示，亲和性组1内的VNF分布在主机1和主机2上，备份亲和性组1内的VNF分布在主机3和主机4上。
参阅图6所示，本发明实施例提供了一种切换VNF的装置，用于实现本发明图3所示的切换VNF的方法，所述装置可以位于MANO内，所述装置包括：
接收单元601，用于接收故障消息，所述故障消息用于指示发生故障的第一VNF。
确定单元602，用于确定所述第一VNF所属的主亲和性组，以及所述主亲和性组的备份亲和性组；所述备份亲和性组中的VNF与所述主亲和性组中的VNF一一对应，所述亲和性组表示采用亲和性策略的VNF的集合。
切换单元603，用于令所述备份亲和性组中的VNF继续处理所述主亲和性组中的VNF的业务。
可选的，所述接收单元601具体用于，接收VNFM上报的故障消息。
可选的，所述装置还包括：
更新单元604，用于将所述备份亲和性组及所述备份亲和性组中的VNF的属性更改为主属性。
可选的，所述故障消息可以由所述备份亲和性组的代理在通过心跳机制检测到所述第一VNF故障后上报给所述VNFM；或者，所述故障消息可以由 NFVI在检测到所述NFVI内将影响所述第一VNF运行的故障后上报给虚拟化的基础设施管理VIM，再由所述VIM上报给所述VNFM；或者，所述故障消息可以由所述NFVI在检测到所述NFVI内将影响所述第一VNF运行的故障后通知所述第一VNF，再由所述第一VNF上报给所述VNFM。
可选的，所述亲和性组中的VNF分布在一个主机上，或者分布在多个主机上。
综上所述，本发明实施例提供的技术方案，当MANO接收到与亲和性组中的某个VNF相关的故障消息时，第一时间触发该亲和性组中所有VNF的切换，从而解决了在NFV场景下，亲和性策略与HA机制不能兼容的问题，并且将对亲和性策略和主备切换的管理集中到了MANO，避免了控制能力的下放。
本领域内的技术人员应明白，本发明的实施例可提供为方法、系统、或计算机程序产品。因此，本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或 多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本发明的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例做出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本发明范围的所有变更和修改。
显然，本领域的技术人员可以对本发明实施例进行各种改动和变型而不脱离本发明实施例的精神和范围。这样，倘若本发明实施例的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。

Claims (10)

  1. 一种切换虚拟化网络功能VNF的方法，其特征在于，包括：
    管理与编排系统MANO接收故障消息，所述故障消息用于指示发生故障的第一VNF；
    所述MANO确定所述第一VNF所属的主亲和性组，以及所述主亲和性组的备份亲和性组；所述备份亲和性组中的VNF与所述主亲和性组中的VNF一一对应，所述亲和性组表示采用亲和性策略的VNF的集合；
    所述MANO令所述备份亲和性组中的VNF继续处理所述主亲和性组中的VNF的业务。
  2. 如权利要求1所述的方法，其特征在于，所述MANO包括网络功能虚拟化编排器NFVO和虚拟化的网络功能管理VNFM；
    所述MANO接收故障消息，包括：
    所述NFVO接收所述VNFM上报的故障消息；
    所述MANO确定所述第一VNF所属的主亲和性组以及所述主亲和性组的备份亲和性组，包括：
    所述NFVO确定所述第一VNF所属的主亲和性组以及所述主亲和性组的备份亲和性组。
  3. 如权利要求2所述的方法，其特征在于，所述NFVO确定所述第一VNF所属的主亲和性组以及所述主亲和性组的备份亲和性组之后，所述方法还包括：
    所述NFVO将所述备份亲和性组及所述备份亲和性组中的VNF的属性更改为主属性。
  4. 如权利要求2或3所述的方法，其特征在于，所述故障消息由所述备份亲和性组的代理在通过心跳机制检测到所述第一VNF故障后上报给所述VNFM；或者，
    所述故障消息由网络功能虚拟化基础设施NFVI在检测到所述NFVI内将 影响所述第一VNF运行的故障后上报给虚拟化的基础设施管理VIM，再由所述VIM上报给所述VNFM；或者，
    所述故障消息由所述NFVI在检测到所述NFVI内将影响所述第一VNF运行的故障后通知所述第一VNF，再由所述第一VNF上报给所述VNFM。
  5. 如权利要求1-4中任一项所述的方法，其特征在于，所述亲和性组中的VNF分布在一个主机上，或者分布在多个主机上。
  6. 一种切换虚拟化网络功能VNF的装置，其特征在于，包括：
    接收单元，用于接收故障消息，所述故障消息用于指示发生故障的第一VNF；
    确定单元，用于确定所述第一VNF所属的主亲和性组，以及所述主亲和性组的备份亲和性组；所述备份亲和性组中的VNF与所述主亲和性组中的VNF一一对应，所述亲和性组表示采用亲和性策略的VNF的集合；
    切换单元，用于令所述备份亲和性组中的VNF继续处理所述主亲和性组中的VNF的业务。
  7. 如权利要求6所述的装置，其特征在于，所述接收单元具体用于：
    接收虚拟化的网络功能管理VNFM上报的故障消息。
  8. 如权利要求7所述的装置，其特征在于，所述装置还包括：
    更新单元，用于将所述备份亲和性组及所述备份亲和性组中的VNF的属性更改为主属性。
  9. 如权利要求7或8所述的装置，其特征在于，所述故障消息由所述备份亲和性组的代理在通过心跳机制检测到所述第一VNF故障后上报给所述VNFM；或者，
    所述故障消息由网络功能虚拟化基础设施NFVI在检测到所述NFVI内将影响所述第一VNF运行的故障后上报给虚拟化的基础设施管理VIM，再由所述VIM上报给所述VNFM；或者，
    所述故障消息由所述NFVI在检测到所述NFVI内将影响所述第一VNF运行的故障后通知所述第一VNF，再由所述第一VNF上报给所述VNFM。
  10. 如权利要求6-9中任一项所述的装置，其特征在于，所述亲和性组中的VNF分布在一个主机上，或者分布在多个主机上。
PCT/CN2015/082997 2015-06-30 2015-06-30 一种切换vnf的方法和装置 Ceased WO2017000260A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP15896791.9A EP3300298B1 (en) 2015-06-30 2015-06-30 Method and apparatus for switching vnf
CN201580032742.5A CN106664216B (zh) 2015-06-30 2015-06-30 一种切换vnf的方法和装置
PCT/CN2015/082997 WO2017000260A1 (zh) 2015-06-30 2015-06-30 一种切换vnf的方法和装置
JP2017565253A JP6466003B2 (ja) 2015-06-30 2015-06-30 Ｖｎｆフェイルオーバの方法及び装置
US15/853,958 US10644952B2 (en) 2015-06-30 2017-12-25 VNF failover method and apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/082997 WO2017000260A1 (zh) 2015-06-30 2015-06-30 一种切换vnf的方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/853,958 Continuation US10644952B2 (en) 2015-06-30 2017-12-25 VNF failover method and apparatus

Publications (1)

Publication Number Publication Date
WO2017000260A1 true WO2017000260A1 (zh) 2017-01-05

Family

ID=57607424

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/082997 Ceased WO2017000260A1 (zh) 2015-06-30 2015-06-30 一种切换vnf的方法和装置

Country Status (5)

Country Link
US (1) US10644952B2 (zh)
EP (1) EP3300298B1 (zh)
JP (1) JP6466003B2 (zh)
CN (1) CN106664216B (zh)
WO (1) WO2017000260A1 (zh)

Families Citing this family (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106452925B (zh) * 2016-12-02 2021-01-05 华为技术有限公司 在nfv系统中检测故障的方法、装置和系统
US10728132B2 (en) * 2017-06-01 2020-07-28 Hewlett Packard Enterprise Development Lp Network affinity index increase
US10735275B2 (en) 2017-06-16 2020-08-04 Cisco Technology, Inc. Releasing and retaining resources for use in a NFV environment
US11003516B2 (en) * 2017-07-24 2021-05-11 At&T Intellectual Property I, L.P. Geographical redundancy and dynamic scaling for virtual network functions
US11048536B2 (en) * 2017-11-28 2021-06-29 Microsoft Technology Licensing, Llc High availability cloud service provision
US10778506B1 (en) 2017-11-30 2020-09-15 Open Invention Network Llc Coordinated switch of activity in virtual network function components
US10764115B1 (en) 2018-01-05 2020-09-01 Open Invention Network Llc EMS handling of faults in virtual network function components
CN110048872A (zh) * 2018-01-16 2019-07-23 中兴通讯股份有限公司 一种网络告警方法、装置、系统及终端
FR3081582A1 (fr) * 2018-06-18 2019-11-29 Orange Procede d'installation d'une fonction reseau virtualisee
CN116669083A (zh) 2018-09-27 2023-08-29 中兴通讯股份有限公司 一种ue迁移方法、装置、系统及存储介质
DE112018008114B4 (de) * 2018-11-01 2024-06-13 Hewlett Packard Enterprise Development Lp Reaktion einer virtuellen netzwerkfunktion auf eine dienstunterbrechung
US10880370B2 (en) 2018-11-27 2020-12-29 At&T Intellectual Property I, L.P. Virtual network manager system
US11323310B2 (en) * 2019-06-24 2022-05-03 Allot Ltd. Method, device, and system for providing hot reservation for in-line deployed network functions with multiple network interfaces
WO2021033255A1 (ja) * 2019-08-20 2021-02-25 日本電信電話株式会社 処理装置、処理システム、処理方法、および処理プログラム
EP3862880B1 (en) * 2020-02-04 2024-09-11 Adtran Networks SE Computer-implemented method for reducing service disruption times for a universal customer premise equipment, ucpe, device with resource constraint in a network functions virtualization, nfv, network infrastructure
CN113573329B (zh) * 2020-04-28 2024-11-29 华为技术有限公司 节点控制的方法、系统以及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104170323A (zh) * 2014-04-09 2014-11-26 华为技术有限公司 基于网络功能虚拟化的故障处理方法及装置、系统
CN104320274A (zh) * 2014-10-24 2015-01-28 华为技术有限公司 一种容灾方法及装置
CN104468688A (zh) * 2013-09-13 2015-03-25 株式会社Ntt都科摩 用于网络虚拟化的方法和设备
WO2015091964A1 (en) * 2013-12-19 2015-06-25 Amdocs Software Systems Limited System, method, and computer program for inter-module communication in a network based on network function virtualization (nfv)

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8918490B1 (en) * 2007-07-12 2014-12-23 Oracle America Inc. Locality and time based dependency relationships in clusters
US8510590B2 (en) * 2010-03-17 2013-08-13 Vmware, Inc. Method and system for cluster resource management in a virtualized computing environment
TWI537828B (zh) * 2010-12-21 2016-06-11 萬國商業機器公司 虛擬機管理的方法及其電腦系統之裝置和電腦程式
US9292376B2 (en) * 2012-08-24 2016-03-22 Vmware, Inc. Proactive resource reservation for protecting virtual machines
CN105247826B (zh) * 2013-01-11 2018-07-13 华为技术有限公司 网络设备的网络功能虚拟化
CN104685830B (zh) 2013-09-30 2018-03-06 华为技术有限公司 故障管理的方法、实体和系统
WO2015157897A1 (zh) * 2014-04-14 2015-10-22 华为技术有限公司 一种云计算架构下的容灾数据中心配置方法及装置
CN104253866B (zh) 2014-09-20 2018-03-27 华为技术有限公司 虚拟网络功能网元的软件部署方法、系统及相关设备
US10931742B2 (en) * 2014-09-29 2021-02-23 Koninklijke Kpn N.V. State replication of virtual network function instances
US9594649B2 (en) * 2014-10-13 2017-03-14 At&T Intellectual Property I, L.P. Network virtualization policy management system
WO2016093861A1 (en) * 2014-12-12 2016-06-16 Nokia Solutions And Networks Oy Alarm correlation in network function virtualization environment
CN104636184B (zh) * 2014-12-29 2018-05-01 上海华为技术有限公司 虚拟机实例的部署方法和装置及设备
KR20170109603A (ko) * 2015-01-28 2017-09-29 닛본 덴끼 가부시끼가이샤 가상 네트워크 기능 관리 장치, 시스템, 힐링 방법 및 프로그램

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104468688A (zh) * 2013-09-13 2015-03-25 株式会社Ntt都科摩 用于网络虚拟化的方法和设备
WO2015091964A1 (en) * 2013-12-19 2015-06-25 Amdocs Software Systems Limited System, method, and computer program for inter-module communication in a network based on network function virtualization (nfv)
CN104170323A (zh) * 2014-04-09 2014-11-26 华为技术有限公司 基于网络功能虚拟化的故障处理方法及装置、系统
CN104320274A (zh) * 2014-10-24 2015-01-28 华为技术有限公司 一种容灾方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3300298A4 *

Also Published As

Publication number Publication date
EP3300298A4 (en) 2018-05-02
CN106664216A (zh) 2017-05-10
US20180123870A1 (en) 2018-05-03
JP2018519736A (ja) 2018-07-19
EP3300298B1 (en) 2020-11-25
CN106664216B (zh) 2019-12-06
US10644952B2 (en) 2020-05-05
EP3300298A1 (en) 2018-03-28
JP6466003B2 (ja) 2019-02-06

Similar Documents

Publication Publication Date Title
CN106664216B (zh) 一种切换vnf的方法和装置
CN108632067B (zh) 容灾部署方法、装置及系统
JP6026705B2 (ja) 更新管理システムおよび更新管理方法
EP3216194B1 (en) Network function virtualization service chaining
Houidi et al. Adaptive virtual network provisioning
JP6432955B2 (ja) 仮想ネットワーク機能インスタンスをマイグレーションさせるための方法、装置およびシステム
WO2017181876A1 (zh) 一种设备状态及资源信息监测方法、相关设备及系统
WO2013044828A1 (zh) 虚拟化集群系统及其处理方法和设备
CN110661641B (zh) 一种虚拟网络功能vnf部署方法及装置
CN108347339B (zh) 一种业务恢复方法及装置
JP2018515978A (ja) サービス可用性管理のための方法およびエンティティ
WO2016206456A1 (zh) 物理机升级方法、业务迁移方法及装置
CN105515812A (zh) 资源的故障处理方法及装置
CN104158707A (zh) 一种检测并处理集群脑裂的方法和装置
WO2016054922A1 (zh) 决策协调方法、执行装置和决策协调器
CN113709220B (zh) 虚拟负载均衡器的高可用实现方法、系统及电子设备
JP2015191246A (ja) 通信システムおよび管理方法
CN116455731A (zh) 云安全资源池的高可用实现方法、系统、设备及存储介质
CN108345490B (zh) 一种nfv中部署虚拟机的方法和系统
CN110545193B (zh) 一种虚拟资源的管理方法、虚拟资源管理设备及服务器
US11281451B2 (en) Distributed backup and restoration in virtualized computing environments
EP4706277A1 (en) Shared open-ran radio unit resiliency
CN113535359A (zh) 一种多租户云中服务请求调度方法和装置
NFV ETSI GS NFV-REL 001 V1. 1.1 (2015-01)

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: 15896791

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2017565253

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2015896791

Country of ref document: EP