WO2016161605A1 - 基于网络功能虚拟化的故障处理方法和装置 - Google Patents

基于网络功能虚拟化的故障处理方法和装置 Download PDF

Info

Publication number
WO2016161605A1
WO2016161605A1 PCT/CN2015/076183 CN2015076183W WO2016161605A1 WO 2016161605 A1 WO2016161605 A1 WO 2016161605A1 CN 2015076183 W CN2015076183 W CN 2015076183W WO 2016161605 A1 WO2016161605 A1 WO 2016161605A1
Authority
WO
WIPO (PCT)
Prior art keywords
self
healing
information
nfvi
fault
Prior art date
Application number
PCT/CN2015/076183
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 华为技术有限公司
Priority to RU2017134942A priority Critical patent/RU2681358C1/ru
Priority to PCT/CN2015/076183 priority patent/WO2016161605A1/zh
Priority to KR1020177030272A priority patent/KR102010942B1/ko
Priority to EP15888162.3A priority patent/EP3282640B1/en
Priority to CN201580030586.9A priority patent/CN106464533B/zh
Publication of WO2016161605A1 publication Critical patent/WO2016161605A1/zh
Priority to US15/722,347 priority patent/US10608871B2/en

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/0659—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities
    • H04L41/0661—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities by reconfiguring faulty entities
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/30—Arrangements for executing machine instructions, e.g. instruction decode
    • G06F9/34—Addressing or accessing the instruction operand or the result ; Formation of operand address; Addressing modes
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/24—Testing correct operation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus 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/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
    • 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/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
    • H04L41/083—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability for increasing network speed
    • 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/0803—Configuration setting
    • H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
    • H04L41/0836—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability to enhance reliability, e.g. reduce downtime
    • 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
    • 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/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H04L41/0897—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or 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/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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • 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/0866—Checking the configuration
    • H04L41/0869—Validating the configuration within one network element
    • 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/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities

Definitions

  • the present invention relates to the field of communication technologies, and, more particularly, to a fault processing method and apparatus based on network function virtualization.
  • NFV Network Function Virtualization
  • NFV ISG The purpose of the operator's NFV ISG is to define the requirements for carrier network function virtualization and related technical reports, and hope to implement some network functions in general-purpose high-performance servers, switches and storage. This requires network functions to be implemented in software and run on common server hardware, which can be migrated, instantiated, deployed in different locations on the network as needed, and does not require new equipment to be installed.
  • Various types of network devices such as servers, routers, storage devices, and switches, can be separated from hardware and software through NFV technology.
  • NFV failures may occur at different levels of the network. For example, infrastructure failures in the Network Function Virtualization Infrastructure (NFVI) layer, Virtualized Network Function (VNF) software failures, and network failures.
  • infrastructure failures may include hardware failures (such as hard disk input and output failures, server power failures, port failures, etc.) and virtual machine (VM) failures.
  • hardware failures such as hard disk input and output failures, server power failures, port failures, etc.
  • VM virtual machine
  • the fault of the existing NFV needs to be reported to the fault association entity and the fault decision entity first.
  • the fault correlation entity first analyzes the fault root cause, and then the fault decision entity makes a fault diagnosis decision before the fault repair is performed. Therefore, NFV failures have an analysis and processing delay from discovery to failure repair so that the fault decision entity can make the right decision.
  • NFVI infrastructure failures are different from VNF failures, which can be caused by other failures, and infrastructure failures themselves are root cause failures that do not require root cause analysis and decision making. Therefore, the existing infrastructure is faulty
  • the processing method has a higher processing delay.
  • Embodiments of the present invention provide a fault processing method and apparatus based on network function virtualization, which can reduce processing delay of infrastructure faults.
  • the first aspect provides a fault processing method based on network function virtualization, including: determining a network function virtualization infrastructure NFVI fault; acquiring self-healing policy information, where the self-healing policy information is used to indicate whether the NFVI fault is performed. Self-healing operation; when the self-healing policy information indicates that the NFVI fault is self-healing, the NFVI fault is self-healing.
  • the self-healing policy information includes updated self-healing policy information.
  • the method further includes: sending self-healing startup information, the self-healing startup information is used to indicate that the self-healing operation of the NFVI failure has been initiated.
  • the method further includes: sending self-healing completion information, the self-healing completion information Used to indicate that the self-healing operation for the NFVI failure has been completed.
  • the method further includes: when The self-healing policy information indicates that the fault information of the NFVI fault is sent when the self-healing operation of the NFVI fault is prohibited.
  • the self-healing policy information When the self-healing operation is performed on the NFVI fault, the self-healing operation is performed, including: selecting a new server to deploy the virtual machine that is affected by the NFVI failure; and creating a new virtual machine.
  • the self-healing policy information includes The virtual machine identifier, the fault type information, and the self-healing behavior information, or the self-healing policy information includes a virtual machine identifier, a virtual link identifier, a fault type information, and a self-healing behavior information, where the self-healing behavior information includes starting self-healing information and / or prohibit self-healing information.
  • the second aspect provides a fault processing method based on network function virtualization, including: determining self-healing policy information, the self-healing policy information is used to indicate whether the NFVI fault is self-healing operation; and the self-healing policy information is sent.
  • the self-healing policy information indicates that the determined network function virtualization infrastructure NFVI fault is self-healing.
  • the determining the self-healing strategy information includes: determining a pre-stored self-healing strategy, where the pre-stored self-healing strategy includes a network function virtualization VNF self-healing strategy And/or a network service NS self-healing strategy; mapping or transforming the pre-stored self-healing policy to determine the self-healing policy information.
  • the method further includes: updating the pre-stored self-healing policy.
  • the VNF self-healing policy includes a VNF identifier and/or a network function virtual Component identification, as well as fault type information and self-healing behavior information.
  • the NS self-healing policy includes the VNF A virtual link self-healing policy between the self-healing policy and the plurality of VNFs, wherein the virtual link self-healing policy includes virtual link identification and self-healing behavior information.
  • the method further includes: receiving self-healing
  • the startup information is used to indicate that the self-healing operation for the NFVI failure has been initiated; and according to the self-healing startup information, the repeated activation of the self-healing operation is prohibited.
  • the method further includes: receiving self-healing completion information, the self-healing completion information Used to indicate that the self-healing operation for the NFVI failure has been completed.
  • the self-healing policy information includes The virtual machine identifier, the fault type information, and the self-healing behavior information, or the self-healing policy information includes a virtual machine identifier, a virtual link identifier, a fault type information, and a self-healing behavior information, where the self-healing behavior information includes starting self-healing information and / or prohibit self-healing information.
  • a fault processing method based on network function virtualization comprising: performing a self-healing operation on a determined network function virtualization infrastructure NFVI fault; sending the NFVI Status information of the barrier, the status information is used to indicate that the self-healing operation is repeatedly initiated.
  • the status information includes self-healing startup information, where the self-healing startup information is used to indicate that the self-healing operation of the NFVI fault has been initiated.
  • the method further includes: sending the self-healing completion information
  • the self-healing completion information is used to indicate that the self-healing operation on the NFVI failure has been completed.
  • the determined network function Virtualization infrastructure NFVI failures are self-healing operations, including: selecting a new server to deploy the virtual machine that is subject to the NFVI failure; creating a new virtual machine.
  • a fourth aspect provides a fault processing method based on network function virtualization, comprising: acquiring state information of a network function virtualization infrastructure NFVI fault, wherein the state information is used to indicate that the restarting self-healing operation is prohibited; and the state information is prohibited according to the state information. It is forbidden to start the self-healing operation repeatedly.
  • the status information includes self-healing startup information, where the self-healing startup information is used to indicate that the self-healing operation of the NFVI fault has been initiated.
  • the method further includes: acquiring The self-healing completion information is used to indicate that the self-healing operation for the NFVI failure has been completed.
  • an apparatus including: a determining unit, configured to determine a network function virtualization infrastructure NFVI fault; and an obtaining unit, configured to obtain self-healing policy information, where the self-healing policy information is used to indicate whether the NFVI is The fault performs a self-healing operation; the self-healing unit is configured to perform a self-healing operation on the NFVI fault when the self-healing policy information indicates that the NFVI fault is self-healing.
  • the self-healing policy information includes updated self-healing policy information.
  • the second possible implementation manner of the fifth aspect further includes: a sending unit, configured to send self-healing startup information, the self-healing startup information Used to indicate that the self-healing operation for the NFVI failure has been initiated.
  • the sending unit is further configured to send self-healing completion information, where the self-healing completion information is used to indicate that the Self-healing operation for this NFVI failure.
  • the sending unit is further configured to: when the self-healing policy information indicates that the NFVI fault is prohibited When the self-healing operation is performed, the fault information of the NFVI fault is sent.
  • the self-healing unit is specific Used to select a new server to deploy a virtual machine that is subject to the NFVI failure; create a new virtual machine.
  • the self-healing policy information includes The virtual machine identifier, the fault type information, and the self-healing behavior information, or the self-healing policy information includes a virtual machine identifier, a virtual link identifier, a fault type information, and a self-healing behavior information, where the self-healing behavior information includes starting self-healing information and / or prohibit self-healing information.
  • an apparatus including: a determining unit, configured to determine self-healing policy information, the self-healing policy information is used to indicate whether the NFVI fault is self-healing operation; and a sending unit is configured to send the self-healing
  • the policy information is such that when the self-healing policy information indicates that the determined network function virtualization infrastructure NFVI fault is self-healing, the NFVI fault is self-healing.
  • the determining unit is specifically configured to determine a pre-stored self-healing policy, where the pre-stored self-healing strategy includes a network function virtualization VNF self-healing strategy and/or Or a network service NS self-healing strategy; mapping or transforming the pre-stored self-healing policy to determine the self-healing policy information.
  • the pre-stored self-healing strategy includes a network function virtualization VNF self-healing strategy and/or Or a network service NS self-healing strategy; mapping or transforming the pre-stored self-healing policy to determine the self-healing policy information.
  • the method further includes: an update unit, configured to update the pre-stored self-healing policy.
  • the VNF self-healing strategy includes VNF identification and/or network function virtualization component identification, as well as fault type information and self-healing behavior information.
  • the NS self-healing strategy includes the VNF A virtual link self-healing strategy between the self-healing policy and the plurality of VNFs, wherein the virtual link self-healing policy includes virtual link identification and self-healing behavior information.
  • the receiving unit is configured to receive Self-healing startup information, the self-healing startup information is used to indicate that the self-healing operation of the NFVI failure has been initiated; and the prohibiting unit is configured to prohibit repeated activation of the self-healing operation according to the self-healing startup information.
  • the receiving unit is further configured to receive and receive self-healing completion information, where the self-healing completion information is used to indicate that Complete the self-healing operation of the NFVI fault.
  • the self-healing policy information includes The virtual machine identifier, the fault type information, and the self-healing behavior information, or the self-healing policy information includes a virtual machine identifier, a virtual link identifier, a fault type information, and a self-healing behavior information, where the self-healing behavior information includes starting self-healing information and / or prohibit self-healing information.
  • a seventh aspect provides an apparatus, including: a self-healing unit, configured to perform a self-healing operation on a determined network function virtualization infrastructure NFVI fault; and a sending unit, configured to send status information of the NFVI fault, the status information Used to indicate that repeated self-healing operations are prohibited.
  • the status information includes self-healing startup information, where the self-healing startup information is used to indicate that the self-healing operation of the NFVI fault has been initiated.
  • the sending unit is further configured to send self-healing completion information, where the self-healing completion information is used Indicates that the self-healing operation for the NFVI failure has been completed.
  • the self-healing unit specifically Used to select a new server to deploy a virtual machine that is subject to the NFVI failure; create a new virtual machine.
  • the eighth aspect provides an apparatus, including: an acquiring unit, configured to acquire state information of a network function virtualization infrastructure NFVI fault, where the state information is used to indicate that the self-healing operation is prohibited from being repeatedly initiated; and the prohibiting unit is configured to Status information, it is forbidden to start the self-healing operation repeatedly.
  • the status information packet The self-healing startup information is used to indicate that the self-healing operation for the NFVI failure has been initiated.
  • the acquiring unit is further configured to obtain self-healing completion information, where the self-healing completion information is used Indicates that the self-healing operation for the NFVI failure has been completed.
  • the infrastructure failure since the infrastructure failure itself is a root cause failure, failure analysis is not required. Therefore, after determining the network function virtualization infrastructure failure, the self-healing policy information of the self-healing operation of the network function virtualization infrastructure failure may be determined according to the obtained indication. When the self-healing policy information indicates that the self-healing operation is performed, the determined fault can be self-healing in time. Therefore, the infrastructure failure in the embodiment of the present invention can avoid reporting time and failure analysis time, repair and process the infrastructure failure as soon as possible, reduce the fault processing delay, and improve system performance.
  • FIG. 1 is a fault processing method based on network function virtualization according to an embodiment of the present invention.
  • FIG. 2 is a schematic flowchart of a process for acquiring self-healing policy information according to an embodiment of the present invention.
  • FIG. 3 is a schematic flowchart of a process for acquiring self-healing policy information according to an embodiment of the present invention.
  • FIG. 4 is a schematic flowchart of a process for acquiring self-healing policy information according to another embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of a process for acquiring self-healing policy information according to another embodiment of the present invention.
  • FIG. 6 is a schematic flowchart of a process for acquiring self-healing policy information according to another embodiment of the present invention.
  • FIG. 7 is a schematic flowchart of a process of acquiring self-healing policy information according to another embodiment of the present invention.
  • FIG. 8 is a schematic flowchart of a fault processing method based on network function virtualization according to another embodiment of the present invention.
  • FIG. 9 is a schematic flowchart of a fault processing method based on network function virtualization according to another embodiment of the present invention.
  • FIG. 10 is a schematic flowchart of a fault processing method based on network function virtualization according to another embodiment of the present invention.
  • FIG. 11 is a flowchart of a fault processing method based on network function virtualization according to another embodiment of the present invention.
  • FIG. 12 is a schematic flowchart of a fault handling process based on network function virtualization according to an embodiment of the present invention.
  • Figure 13 is a schematic block diagram of an apparatus in accordance with one embodiment of the present invention.
  • Figure 14 is a schematic block diagram of an apparatus in accordance with another embodiment of the present invention.
  • Figure 15 is a schematic block diagram of an apparatus in accordance with another embodiment of the present invention.
  • Figure 16 is a schematic block diagram of an apparatus in accordance with another embodiment of the present invention.
  • Figure 17 is a schematic block diagram of an apparatus in accordance with another embodiment of the present invention.
  • Figure 18 is a schematic block diagram of an apparatus in accordance with another embodiment of the present invention.
  • Figure 19 is a schematic block diagram of an apparatus in accordance with another embodiment of the present invention.
  • Figure 20 is a schematic block diagram of an apparatus in accordance with another embodiment of the present invention.
  • NFV includes three key features: first, the software that defines the network functions is completely separated from the general high-performance hardware servers, storage, and network switches; second, the independent modularity of software and hardware components. Third, automated orchestration, which is the complete automated installation and management of software devices based on common hardware.
  • NFVO Network Function Virtualization Orchestrator
  • NSD Network Service Descriptor
  • VNFFG Virtualized Network Function Forwarding Graph
  • VNFM Virtualized Network Function Manager
  • the VNFM implements the lifecycle management of the virtualized network element VNF, including the management and processing of the virtualized network function descriptor (VNFD), the initialization of the VNF instance, the expansion/reduction of the VNF, and the termination of the VNF instance.
  • VNFD virtualized network function descriptor
  • Virtualized Infrastructure Manager is responsible for infrastructure layer hardware resources, virtualization resource management, monitoring and fault reporting, and facing the upper layer.
  • the application provides a pool of virtualized resources.
  • NFVI consists of hardware resources and virtual resources as well as virtual layers. From a VNF perspective, virtual layers and hardware resources are entities that provide the required virtual resources.
  • the process of NFVI failure can be as follows:
  • VIM After the NFVI fault occurs, VIM reports the fault to VNFM/NFVO;
  • VNFM/NFVO sends a fault repair indication to the VIM
  • VIM performs fault repair or fault self-healing according to the fault repair indication, for example, including
  • the NFV failure has an analysis and processing delay from discovery to failure repair so that the fault decision entity can make the right decision.
  • NFVI infrastructure failures are different from VNF failures, which can be caused by other failures, and infrastructure failures themselves are root cause failures that do not require root cause analysis and decision making. Therefore, the processing delay of the existing infrastructure failure processing method is high.
  • VNFM Virtualised Network Function Manager
  • NFVO Network Function Virtualization Orchestrator
  • FIG. 1 is a fault processing method based on network function virtualization according to an embodiment of the present invention.
  • the method 100 shown in Figure 1 can be performed by a virtualized infrastructure manager VIM.
  • the method 100 includes:
  • the self-healing policy information indicates that the NFVI fault is self-healing, the NFVI fault is self-healing.
  • the infrastructure failure since the infrastructure failure itself is a root cause failure, failure analysis is not required. Therefore, after determining the network function virtualization infrastructure failure, the self-healing policy information of the self-healing operation of the network function virtualization infrastructure failure may be judged according to the obtained indication. Broken. When the self-healing policy information indicates that the self-healing operation is performed, the determined fault can be self-healing in time. Therefore, the infrastructure failure in the embodiment of the present invention can avoid reporting time and failure analysis time, repair and process the infrastructure failure as soon as possible, reduce the fault processing delay, and improve system performance.
  • NFV failures may include NFVI failures, VNF failures, and network failures.
  • NFVI failures may include hardware failures (such as hard disk input and output failures, server power failures, port failures, etc.) and VM failures.
  • a VNF failure can be a VNF software failure, and an NFVI failure can be passed to the VNF, causing a VNF failure.
  • VIM can perform health checks on NFVI to facilitate timely detection and determination of NFVI failures.
  • the health check can be implemented by a prior art method such as a heartbeat packet or a watchdog.
  • the embodiment of the present invention does not limit the manner in which the VIM determines the NFVI fault.
  • the acquired self-healing policy information can be used to indicate whether the VIM is self-healing for the detected NFVI failure. That is, the self-healing policy information may indicate that the VIM initiates a self-healing operation, and may also instruct the VIM to prohibit the self-healing operation.
  • the self-healing policy information may be obtained by mapping or transforming the pre-stored self-healing strategy.
  • the pre-stored self-healing strategy can be statically pre-existing in the VNFD or in the NSD; the network operator can also define the self-healing strategy in the NFVO.
  • the self-healing policy information that the VIM can recognize is obtained, and then sent by the NFVO or the VNFM to the corresponding VIM when the VNF is instantiated. In this way, when the VIM detects an NFVI failure, the self-healing operation for the NFVI failure can be automatically triggered according to the self-healing policy information.
  • VNFM and NFVO can identify the VNF and deploy the VM corresponding to the VNF.
  • VIM can only identify VMs and cannot determine which VNF the VM specifically corresponds to. Therefore, the VNFM and/or the NFVO need to map or convert the self-healing policy into self-healing policy information, wherein the self-healing policy information includes the VM self-healing policy information corresponding to the VNF instance and the internal VL self-healing policy information between the VMs.
  • the self-healing strategy defined in the VNFD may include a VNF self-healing strategy, that is, a self-healing strategy for a certain type or a certain type of VNF;
  • the self-healing strategy defined in the NSD may include an NS self-healing strategy, that is, for a certain or some Self-healing strategy for class NS.
  • the self-healing strategy of the NS may include a self-healing strategy of multiple VNFs constituting the NS and a self-healing strategy of the external virtual link (VL) between the VNFs.
  • the self-healing policy defined in the NSD may include a self-healing policy of a VNF constituting a network service (NS) and a self-healing strategy of a VNFFG or a virtual link (VL) constituting the NS.
  • NS network service
  • VL virtual link
  • the self-healing strategy of the VNF defined in the VNFD may include a plurality of different self-healing strategies of the VNFC and a self-healing strategy of the VL between the VNFCs;
  • the self-healing strategy of the VNF may include only the self-healing strategy of the VNFC.
  • the VIM When the self-healing policy information obtained after mapping or transformation indicates that the VIM performs a self-healing operation on the NFVI failure, the VIM performs a self-healing operation. It should be understood that the self-healing operation can be the same as the existing self-healing process.
  • the embodiment of the present invention does not limit how the VIM can self-heal the detected NFVI fault.
  • the self-healing policy information may include updated self-healing policy information.
  • NFVO or VNFM can update the self-healing strategy as needed.
  • mapping or converting the updated self-healing strategy can result in updated self-healing strategy information.
  • FIG. 2 is a schematic flowchart of a process for acquiring self-healing policy information according to an embodiment of the present invention.
  • the process 200 includes:
  • NFVO maps or transforms the VNF self-healing strategy.
  • the NFVO maps or converts the VNF self-healing policy into self-healing policy information
  • the self-healing policy information may include VM self-healing policy information corresponding to the VNF instance and internal virtual link VL self-healing policy information between the VMs.
  • VNFM and NFVO can identify the VNF and deploy the VM corresponding to the VNF.
  • VIM can only identify VMs and cannot determine which VNF the VM specifically corresponds to. Therefore, before the VNFM and/or the NFVO send the self-healing policy information to the VIM, the VNF self-healing policy needs to be mapped or converted into the VM self-healing policy information corresponding to the VNF instance and the internal VL self-healing policy information between the VMs.
  • the VNF self-healing strategy can be mapped or translated into self-healing policy information of one or more VMs.
  • the VNF self-healing policy can be mapped or converted into a VM self-healing policy information; when the VNF is deployed in multiple On a VM, the VNF self-healing strategy can be mapped or translated into multiple VM self-healing policy information and self-healing policy information of the internal VL between the VMs.
  • the NFVO sends the mapped or transformed self-healing policy information to the VIM.
  • the VNF self-healing strategy can be defined by the operator in NFVO, or the default VNF self-healing strategy can be stored in the VNFD.
  • the operator may define a VNF self-healing policy in the NFVO.
  • the NFVO maps or transforms the VNF self-healing policy, and then the NFVO maps or converts the self-healing policy. The more policy information is sent directly to VIM.
  • the VNFD may have a default VNF self-healing strategy. After the VNF instantiation is completed, the NFVO maps or transforms the VNF self-healing strategy, and then the NFVO maps or converts the self-healing strategy. The more policy information is sent directly to VIM.
  • FIG. 3 is a schematic flowchart of a process for acquiring self-healing policy information according to an embodiment of the present invention.
  • the self-healing policy information can be obtained by the VIM.
  • the process 300 includes:
  • NFVO sends a VNF self-healing strategy to VNFM.
  • the VNF self-healing policy is mapped or converted into self-healing policy information, where the self-healing policy information includes VM self-healing policy information corresponding to the VNF instance and internal virtual link VL self-healing policy information between the VMs.
  • the VNF self-healing strategy can be mapped or translated into self-healing policy information of one or more VMs.
  • the VNF self-healing policy can be mapped or converted into a VM self-healing policy information; when the VNF is deployed in multiple On a VM, the VNF self-healing strategy can be mapped or converted into multiple VM self-healing policy information and VL self-healing policy information between VMs.
  • mapping or conversion process may be performed by the VNFM or by the NFVO, and the embodiment of the present invention is not limited thereto.
  • the VNFM sends the VM self-healing policy information and the internal virtual link VL self-healing policy information to the VIM.
  • the VNF self-healing policy may be defined by the operator in the NFVO, or the default VNF self-healing policy may be stored in the VNFD.
  • an operator may define a VNF self-healing policy in the NFVO.
  • the NFVO sends the VNF self-healing policy to the VNFM, and the VNF instance is sent.
  • the VNFM maps or transforms the received VNF self-healing policy, and then the VNFM sends the mapped or transformed self-healing policy information to the VIM.
  • the operator may define a VNF self-healing policy in the NFVO.
  • the NFVO maps or transforms the VNF self-healing policy, and then the NFVO maps or transforms the VNF.
  • the self-healing policy information is sent to the VNFM, and the mapped or converted self-healing policy information is sent to the VIM by the VNFM.
  • a default VNF self-healing strategy may be included in the VNFD, and the VNF self-healing strategy in the VNFD is obtained by the NFVO, and the VNF is instantiated or instantiated after the instantiation is completed.
  • the NFVO sends the VNF self-healing policy to the VNFM.
  • the VNFM maps or transforms the received VNF self-healing policy, and the VNFM sends the mapped or transformed self-healing policy information to the VIM.
  • the VNFD may have a default VNF self-healing strategy, and the VNF self-healing strategy in the VNFD is obtained by the NFVO.
  • the NFVO maps the VNF self-healing strategy or After conversion, the NFVO sends the mapped or transformed self-healing policy information to the VNFM, and the VNFM sends the mapped or transformed self-healing policy information to the VIM.
  • FIG. 4 is a schematic flowchart of a process for acquiring self-healing policy information according to another embodiment of the present invention.
  • the self-healing policy information can be obtained by the VIM.
  • the process 400 includes:
  • VNFM sends a VNF self-healing strategy to NFVO.
  • the self-healing policy information includes the VM self-healing policy information corresponding to the VNF instance and the internal virtual link VL self-healing policy information between the VMs.
  • the VNF self-healing strategy can be mapped or translated into self-healing policy information of one or more VMs.
  • the VNF self-healing policy can be mapped or converted into a VM self-healing policy information; when the VNF is deployed in multiple On a VM, the VNF self-healing strategy can be mapped or converted into multiple VM self-healing policy information and VL self-healing policy information between VMs.
  • mapping or conversion process may be performed by the VNFM or by the NFVO, and the embodiment of the present invention is not limited thereto.
  • the VNF self-healing strategy can be defined by the operator in the VNFM, or the default VNF self-healing policy can be stored in the VNFD.
  • the transmission process in 403 may be sent by NFVO or by VNFM.
  • an operator may define a VNF self-healing policy in the VNFM.
  • the VNFM sends the VNF self-healing policy to the NFVO, and the VNF instance is sent.
  • the NFVO maps or converts the received VNF self-healing policy, and then the VNFM sends the mapped or transformed self-healing policy information to the VIM.
  • the operator may define a VNF self-healing policy in the VNFM.
  • the VNFM maps or transforms the VNF self-healing policy, and then the VNFM maps or transforms the VNF.
  • the self-healing policy information is sent to the NFVO, and the mapped or transformed self-healing policy information is sent to the VIM by the NFVO.
  • a default VNF self-healing strategy may be included in the VNFD, and the VNF self-healing strategy in the VNFD is obtained by the VNFM, and when the VNF is instantiated or instantiated, The VNFM sends the VNF self-healing strategy to the NFVO.
  • the NFVO maps or transforms the received VNF self-healing policy, and the NFVO sends the mapped or transformed self-healing policy information to the VIM.
  • the VNFD may have a default VNF self-healing strategy, and the VNFM obtains the VNF self-healing strategy in the VNFD.
  • the VNFM maps the VNF self-healing policy or After the conversion, the VNFM sends the mapped or transformed self-healing policy information to the NFVO, and the NFVO sends the mapped or transformed self-healing policy information to the VIM.
  • VNFM in the embodiment of the present invention may also directly send the mapped or transformed self-healing policy information to the VIM without using NFVO. details as follows:
  • the operator may define a VNF self-healing policy in the VNFM.
  • the VNFM maps or transforms the VNF self-healing policy, and then the VNFM maps or converts the VNF.
  • Self-healing policy information is sent directly to VIM.
  • the VNFD may have a default VNF self-healing strategy. After the VNF is instantiated, the VNFM maps or transforms the VNF self-healing policy, and then the VNFM maps or converts the self-healing policy. The more policy information is sent directly to VIM.
  • FIG. 5 is a schematic flowchart of a process for acquiring self-healing policy information according to another embodiment of the present invention.
  • the self-healing policy information can be obtained by the VIM.
  • the process 500 includes:
  • NFVO determines the NS self-healing strategy.
  • the NFVO may obtain the NS self-healing strategy from the NSD, or the operator may predefine the NS self-healing strategy in the NFVO.
  • the NS self-healing strategy may include a self-healing strategy of a plurality of VNFs constituting the NS and an external virtual link (VL) self-healing strategy between the VNFs.
  • VL virtual link
  • the NFVO maps or transforms the self-healing strategy of the VNFs that constitute the NS included in the NS self-healing strategy.
  • the NFVO maps or converts the self-healing policy of the VNF in the NS self-healing policy into the VM self-healing policy information corresponding to the VNF instance and the internal virtual link VL self-healing policy information between the VMs.
  • the VNF self-healing strategy can be mapped or translated into self-healing policy information of one or more VMs.
  • the VNF self-healing policy can be mapped or converted into a VM self-healing policy information; when the VNF is deployed in multiple On a VM, the VNF self-healing strategy can be mapped or translated into multiple VM self-healing policy information and self-healing policy information of the internal VL between the VMs.
  • the NFVO may map or convert the external VL self-healing policy information constituting the NS included in the acquired NS self-healing policy to the VM corresponding to the multiple VNF instances constituting the NS.
  • VL self-healing strategy information may be converted to the external VL self-healing policy information constituting the NS included in the acquired NS self-healing policy to the VM corresponding to the multiple VNF instances constituting the NS.
  • the NFVO sends the mapped and transformed self-healing policy information to the VIM.
  • the process shown in Figure 5 can include the following embodiments:
  • the NSD may have a default self-healing strategy. After the NFVO obtains the self-healing policy in the NSD, after the NS instantiation is completed, the NSD obtained by the NFVO pair is obtained. The NS self-healing strategy is mapped or transformed, and then the NFVO directly transmits the mapped or transformed self-healing policy information to the VIM.
  • the operator may pre-define the NS self-healing policy in the NFVO.
  • the NFVO maps or transforms the acquired NS self-healing policy in the NSD, and then the NFVO. Send the mapped or converted self-healing policy information directly to VIM.
  • FIG. 6 is a schematic flowchart of a process for acquiring self-healing policy information according to another embodiment of the present invention.
  • the self-healing policy information can be obtained by the VIM.
  • the process 600 includes:
  • NFVO determines the NS self-healing strategy.
  • the NFVO may obtain the NS self-healing strategy from the NSD, or the operator may predefine the NS self-healing strategy in the NFVO.
  • the NS self-healing strategy may include a self-healing strategy of a plurality of VNFs constituting the NS and an external virtual link (VL) self-healing strategy between the VNFs.
  • VL virtual link
  • the NFVO maps or converts the VNF self-healing strategy that constitutes the NS included in the NS self-healing strategy.
  • the NFVO maps or converts the VNF self-healing policy in the NS self-healing policy into VM self-healing policy information corresponding to the VNF instance and internal virtual link VL self-healing policy information between the VMs.
  • the VNF self-healing strategy can be mapped or translated into self-healing policy information of one or more VMs.
  • the VNF self-healing policy can be mapped or converted into a VM self-healing policy information; when the VNF is deployed in multiple On a VM, the VNF self-healing strategy can be mapped or converted into multiple VM self-healing policy information and VL self-healing policy information between VMs.
  • the NFVO may map or convert the external VL self-healing policy constituting the NS included in the acquired NS self-healing policy to the VM corresponding to the multiple VNF instances constituting the NS.
  • VL self-healing strategy information may be used to map or convert the external VL self-healing policy constituting the NS included in the acquired NS self-healing policy to the VM corresponding to the multiple VNF instances constituting the NS.
  • the NFVO sends the mapped or converted multiple VM self-healing policy information and the VL self-healing policy information between the VMs to the VNFM, and the VNFM sends the mapped or converted multiple VM self-healing policy information and the VM to the VIM.
  • Self-healing strategy information between VL is not limited to VL.
  • the NFVO sends the virtual link self-healing policy information between the VMs corresponding to the multiple VNF instances that are mapped or converted to the VIM.
  • sequence of 603 and 604 is not limited in the embodiment of the present invention.
  • FIG. 7 is a schematic flowchart of a process of acquiring self-healing policy information according to another embodiment of the present invention.
  • the self-healing policy information can be obtained by the VIM.
  • the process 700 includes:
  • NFVO determines the NS self-healing strategy.
  • the NFVO may obtain the NS self-healing strategy from the NSD, or the operator may predefine the NS self-healing strategy in the NFVO.
  • the NS self-healing strategy may include multiple VNF self-healing policies that make up the NS and an external virtual link (VL) self-healing strategy between the VNFs.
  • VL virtual link
  • the NFVO sends the VNF self-healing strategy constituting the NS included in the NS self-healing strategy to the VNFM.
  • the VNFM maps or converts the received VNF self-healing policy.
  • the VNFM maps or converts the received VNF self-healing policy into VM self-healing policy information corresponding to the VNF instance and internal virtual link VL self-healing policy information between the VMs.
  • the VNF self-healing strategy can be mapped or translated into self-healing policy information of one or more VMs.
  • the VNF self-healing policy can be mapped or converted into a VM self-healing policy information; when the VNF is deployed in multiple On a VM, the VNF self-healing strategy can be mapped or converted into multiple VM self-healing policy information and VL self-healing policy information between VMs.
  • the VNFM sends the mapped and transformed self-healing policy information to the VIM.
  • NFVO maps or converts the VL self-healing strategy composed of NS included in the NS self-healing strategy
  • the virtual link self-healing policy information between VMs corresponding to multiple VNF instances constituting the NS is replaced.
  • the NFVO sends the virtual link self-healing policy information between the VMs corresponding to the multiple VNF instances that form the NS to the VIM.
  • the VNF self-healing policy may include a virtual network function VNF identifier, and fault type information and self-healing behavior information, and the self-healing behavior information may include starting self-healing information and/or prohibiting self-healing information.
  • the self-healing strategy of the VNF defined in the VNFD may include a plurality of different self-healing strategies of the VNFC, and a self-healing strategy of the VL between the VNFCs;
  • the self-healing strategy of the VNF may include only the self-healing strategy of the VNFC.
  • the VNF identifier in the VNF self-healing policy defined in the VNFD may be the identification information (ID) of the VNF vendor to the VNF.
  • ID the identification information
  • the VNF identifier defined by the operator may be a unique identifier of the VNF in the operator management domain, or may be specified.
  • a type of VNF such as MME
  • failure type information may include hardware failures (such as hard disk input and output failures), server power outages, host operating system failures, port failures, and the like.
  • the self-healing behavior information may include initiating self-healing information and/or prohibiting self-healing information, wherein initiating self-healing information may instruct the VIM to automatically trigger a self-healing operation, and prohibiting the self-healing information may instruct the VIM to prohibit automatic triggering of the self-healing operation.
  • VNF self-healing strategy defined by the operator or the VNF self-healing strategy defined in the VNFD can be as shown in Table 1.
  • VNF ID 1 is a certain VNF identifier
  • the type of failure occurs is a hardware failure
  • the corresponding self-healing behavior is startup, that is, when VNF ID 1 fails, and the fault type is hardware failure.
  • VIM can initiate self-healing operations. It should be understood that Table 1 only shows a self-healing strategy including a partial VNF, and the self-healing strategy may also include other VNFs, which are not enumerated in the embodiments of the present invention. It should also be understood that the VIM can detect multiple faults at the same time, and then compare the identifiers in Table 1 to find out the fault handling method corresponding to the fault identifier, that is, the fault behavior information.
  • the method for defining the self-healing policy is not limited in the embodiment of the present invention, and only the self-healing policy is required to indicate whether the NVFI fault is self-healing.
  • the NS self-healing strategy may include a VNF self-healing strategy and a VL self-healing strategy between the plurality of VNFs that form the NS, where
  • the VL (including VNF internal or external VL) self-healing strategy may include a virtual link VL identification, and self-healing behavior information, as shown in Table 2.
  • Self-healing behavior information may include initiating self-healing information and/or prohibiting self-healing information.
  • the VL identifier can identify the VL between the specific two VNFCs in the specific VNF; for the external VL between the VNFs, the VL identifier can identify the VL between the specific two VNFs.
  • the NS self-healing policy defined in the NSD may include an NS identifier and self-healing behavior information, where the self-healing behavior information may include starting self-healing information and/or prohibiting self-healing information, as shown in the following table. 3 is shown.
  • the NS self-healing strategy may include VNF self-healing.
  • Strategy when the NS self-healing strategy includes multiple VNFs, the NS self-healing strategy includes the multiple VNF self-healing strategies and an external VL self-healing strategy between the VNFs
  • the self-healing policy information may include a virtual machine identifier, fault type information, and self-healing behavior information, or the self-healing policy information includes a virtual machine identifier, a virtual link identifier, a fault type information, and a self-healing policy.
  • the more behavioral information, the self-healing behavior information includes the initiation of self-healing information and/or the prohibition of self-healing information.
  • the VNF self-healing policy and/or the NS self-healing policy mapping and the converted self-healing policy information may include: a virtual machine VM identifier, and fault type information and self-healing behavior information, as follows Table 4 shows.
  • Self-healing behavior information may include initiating self-healing information and/or prohibiting self-healing information.
  • the VL (VNF internal or external VL) self-healing policy mapping or the transformed self-healing policy information may include: a VL identifier and self-healing behavior information.
  • the self-healing behavior information may include initiating self-healing information and/or prohibiting self-healing information.
  • the VL flag can identify the VL between the specific two VMs.
  • FIG. 8 is a schematic flowchart of a fault processing method based on network function virtualization according to another embodiment of the present invention.
  • the method 100 may further include:
  • the infrastructure failure since the infrastructure failure itself is a root cause failure, failure analysis is not required. Therefore, after determining the network function virtualization infrastructure failure, the self-healing policy information of the self-healing operation for the NFVI failure may be determined according to the obtained indication. When the self-healing policy information indicates that the self-healing operation is performed, the determined fault can be self-healing in time. Therefore, the infrastructure failure in the embodiment of the present invention can avoid reporting time and failure analysis time, repair and process the infrastructure failure as soon as possible, reduce the fault processing delay, and improve system performance.
  • the self-healing startup information sent in the embodiment of the present invention can indicate that the self-healing operation for the NFVI failure has been initiated. In this way, the receiving party does not repeatedly initiate the self-healing operation after receiving the self-healing startup information, thereby avoiding the conflict that may be caused by repeated activation of the self-healing operation.
  • the recipient of the self-healing activation information may be VNFM and/or NFVO.
  • the VIM may send self-healing startup information to the NFVO and/or VNFM.
  • the VIM when the VIM can send the self-healing startup information to the NFVO and/or the VNFM, the fault information of the NFVI fault can also be sent to the NFVO and/or the VNFM.
  • the method 100 may further include:
  • Send self-healing completion information, and the self-healing completion information is used to indicate that the self-healing operation for the NFVI failure has been completed.
  • the VIM may send self-healing completion information to the NFVO and/or VNFM after completing the self-healing operation, such that the NFVO and/or VNFM may trigger the repaired VM or VNF after receiving the self-healing completion information.
  • Reconfigure It should be understood that the self-healing start information in 140 is used as an indication to inform the NFVO and/or VNFM that the self-healing operation for the NFVI failure by the VIM is in progress, and the VNF failure caused by the NVFI failure prohibits the self-healing operation.
  • the self-healing startup information may not be sent, and only the self-healing completion information may be sent; or the self-healing completion information may be sent after the self-healing startup information is sent.
  • the NFVO and/or VNFM receives the self-healing completion information, it can trigger reconfiguration of the repaired VM or VNF.
  • the VIM may report the fault information of the NFVI fault to the NFVO and/or the VNFM. At this time, the subsequent operations may be the same as the operations after the existing VIM reports the fault information.
  • the embodiment of the present invention does not limit the process after the VIM reports the fault information.
  • the VIM may perform a health check on the NFVI to detect the NFVI fault and determine the virtual impact of the NFVI fault before determining whether to perform the self-healing operation on the NFVI fault according to the self-healing policy information. machine.
  • VIM can also view self-healing strategy information.
  • the self-healing operation may be performed, and the self-healing operation may include:
  • VIM creates a new virtual machine
  • the newly created virtual machine can continue to use the previous storage resources and network resources.
  • VIM completes the self-healing operation when VIM creates a new virtual machine.
  • the VIM can send self-healing completion information to the NFVO and/or VNFM, and the VNFM and/or the Element Management System (EMS) can perform service-related configuration on the new VM.
  • EMS Element Management System
  • FIG. 9 is a schematic flowchart of a fault processing method based on network function virtualization according to another embodiment of the present invention.
  • the method shown in Figure 9 can be performed by NFVO and/or VNFM.
  • the method includes:
  • the infrastructure failure since the infrastructure failure itself is a root cause failure, failure analysis is not required. Therefore, after determining the network function virtualization infrastructure failure, the self-healing policy information of the self-healing operation for the NFVI failure may be determined according to the obtained indication. When the self-healing policy information indicates that the self-healing operation is performed, the determined fault can be self-healing in time. Therefore, the infrastructure failure in the embodiment of the present invention can avoid reporting time and failure analysis time, repair and process the infrastructure failure as soon as possible, reduce the fault processing delay, and improve system performance.
  • the recipient of the self-healing policy information may be a VIM.
  • NFV failures may include NFVI failures, VNF failures, and network failures.
  • NFVI failures may include hardware failures (such as hard disk input and output failures, server power failures, port failures, etc.) and VM failures.
  • a VNF failure can be a VNF software failure, and an NFVI failure can be passed to the VNF, causing a VNF failure.
  • VIM can perform health checks on NFVI to facilitate timely detection and determination of NFVI failures.
  • the health check can be implemented by a prior art method such as a heartbeat packet or a watchdog.
  • the embodiment of the present invention does not limit the manner in which the VIM determines the NFVI fault.
  • the embodiment of the present invention does not limit the form and specific content of the self-healing policy information, and only needs the self-healing policy information to indicate whether the NFVI fault is self-healing.
  • the process of determining self-healing policy information may include:
  • the pre-stored self-healing strategy is determined, and the pre-stored self-healing strategy includes a network function virtualization VNF self-healing strategy and/or a network service NS self-healing strategy; mapping or transforming the pre-stored self-healing strategy to determine the self-healing strategy information.
  • the pre-stored self-healing strategy may include a VNF self-healing strategy and/or an NS self-healing strategy.
  • the self-healing strategy can be statically pre-existing in the VNFD or in the NSD; the network operator can also define the self-healing strategy in NFVO.
  • the self-healing policy information that the VIM can recognize is obtained, and then sent by the NFVO or the VNFM to the corresponding VIM when the VNF is instantiated. In this way, when the VIM detects an NFVI failure, the self-healing operation for the NFVI failure can be automatically triggered according to the self-healing policy information.
  • VNFM and NFVO can identify the VNF and deploy the VM corresponding to the VNF.
  • VIM can only identify VMs and cannot determine which VNF the VM specifically corresponds to. Therefore, the VNFM and/or the NFVO need to map or convert the self-healing policy into self-healing policy information, wherein the self-healing policy information includes the VM self-healing policy information corresponding to the VNF instance and the internal VL self-healing policy information between the VMs.
  • the VNF self-healing policy may include a VNF identifier and/or a network function virtualization component identifier, and fault type information and self-healing behavior information.
  • the self-healing strategy defined in the VNFD may include a VNF self-healing strategy, that is, a self-healing strategy for a certain type or a certain type of VNF.
  • the content of the VNF self-healing policy may be as shown in Table 1 above, in order to avoid duplication. It will not be described in detail here.
  • the self-healing strategy of the VNF defined in the VNFD may include a plurality of different self-healing strategies of the VNFC and a self-healing strategy of the VL between the VNFCs;
  • the self-healing strategy of the VNF may include only the self-healing strategy of the VNFC.
  • the VNF identifier in the VNF self-healing policy defined in the VNFD may be the identification information (ID) of the VNF vendor to the VNF.
  • ID the identification information
  • the VNF identifier defined by the operator may be a unique identifier of the VNF in the operator management domain, or may be specified.
  • a type of VNF such as MME
  • fault type Information can include hardware failures (such as hard drive input and output failures), server power outages, host operating system failures, port failures, and more.
  • the self-healing behavior information may include initiating self-healing information and/or prohibiting self-healing information, wherein initiating self-healing information may instruct the VIM to automatically trigger a self-healing operation, and prohibiting the self-healing information may instruct the VIM to prohibit automatic triggering of the self-healing operation.
  • initiating self-healing information may instruct the VIM to automatically trigger a self-healing operation
  • prohibiting the self-healing information may instruct the VIM to prohibit automatic triggering of the self-healing operation.
  • the NS self-healing policy may include a VNF self-healing policy and a virtual link self-healing policy between multiple VNFs, where the virtual link self-healing policy includes virtual link identification and self-healing Behavioral information.
  • the VL (including VNF internal or external VL) self-healing strategy may include a virtual link VL identity, as well as self-healing behavior information, as shown in Table 2 described above.
  • Self-healing behavior information may include initiating self-healing information and/or prohibiting self-healing information.
  • the VL identifier can identify the VL between the specific two VNFCs in the specific VNF; for the external VL between the VNFs, the VL identifier can identify the VL between the specific two VNFs.
  • the NS self-healing policy defined in the NSD may include an NS identifier and self-healing behavior information, wherein the self-healing behavior information may include starting self-healing information and/or prohibiting self-healing information, and the NS self-healing policy may be as shown in Table 3 above. Show. Specifically, the NS self-healing strategy may be as shown in Table 3 described above, and is not described in detail herein to avoid repetition.
  • the self-healing strategy defined in the NSD may include an NS self-healing strategy, that is, a self-healing strategy for a certain or a certain type of NS.
  • the self-healing strategy of the NS may include a self-healing strategy of multiple VNFs constituting the NS and a self-healing strategy of the external virtual link (VL) between the VNFs.
  • the NS self-healing policy defined in the NSD may include a self-healing policy of a VNF constituting a network service (NS) and a self-healing strategy of a VNFFG or a virtual link (VL) constituting the NS.
  • the VIM When the self-healing policy information obtained after mapping or transformation indicates that the VIM performs a self-healing operation on the NFVI failure, the VIM performs a self-healing operation. It should be understood that the self-healing operation can be the same as the existing self-healing process.
  • the embodiment of the present invention does not limit how the VIM can self-heal the detected NFVI fault.
  • the self-healing policy information may include a virtual machine identifier and/or a virtual link identifier, and fault type information and self-healing behavior information, including self-healing information and/or prohibition. Self-healing information.
  • the self-healing policy information can be obtained by mapping and converting the VNF self-healing policy and/or the NS self-healing policy, and the self-healing policy information may include: a virtual machine VM identifier, or, The virtual machine identification and virtual link identification, as well as the failure type information and self-healing behavior information, are shown in Table 4 of the description above.
  • Self-healing behavior information may include initiating self-healing information and/or prohibiting self-healing information.
  • the NS self-healing policy mapping or the transformed self-healing policy information may include: a virtual machine identifier, a fault type information, and a self-healing behavior information; when the NS self-healing policy includes multiple VNFs
  • the NS self-healing strategy includes the plurality of VNF self-healing policies and an external VL self-healing strategy between the VNFs, and the external VL self-healing policies may be mapped or converted into VL self-healing policy information between the VMs.
  • the VL self-healing strategy information may include VL identification and self-healing behavior information. Therefore, the NS self-healing policy mapping or the transformed self-healing policy information may include: a virtual machine identifier, a virtual link identifier, fault type information, and self-healing behavior information.
  • the VL (VNF internal or external VL) self-healing policy mapping or the transformed self-healing policy information may include: a VL identifier and self-healing behavior information.
  • the self-healing behavior information may include initiating self-healing information and/or prohibiting self-healing information.
  • the VL flag can identify the VL between the specific two VMs.
  • the method may further include:
  • the VIM in the embodiment of the present invention sends self-healing start information capable of instructing the self-healing operation of the VIM to the NFVI failure to the NFVO and/or VNFM.
  • NFVO and/or VNFM will not initiate the self-healing operation of VNF/VM after receiving the self-healing startup information, thereby avoiding the conflict that may be caused by the self-healing operation triggered by NFVO or VNFM and the self-healing operation triggered by VIM.
  • the method may further include:
  • Receive self-healing completion information, and the self-healing completion information is used to indicate that the self-healing operation on the NFVI fault has been completed.
  • the NFVO and/or VNFM may initiate the virtual network function VNF to perform the self-healing operation after receiving the self-healing completion information. If the new VM is created and the NFVO and/or VNFM receives the self-healing completion information, the VNFM and/or EMS can perform service-related configuration on the new VM.
  • the method shown in FIG. 9 may further include:
  • NFVO or VNFM can update the self-healing strategy as needed.
  • mapping or converting the updated self-healing strategy can result in updated self-healing strategy information.
  • FIG. 10 is a schematic flowchart of a fault processing method based on network function virtualization according to another embodiment of the present invention.
  • the method shown in Figure 10 can be performed by VIM.
  • the method can include:
  • status information is sent to the NFVO and/or the VNFM, and the status information is used to indicate that the virtual network function VNF is prohibited from performing the self-healing operation.
  • the receiving party does not repeatedly initiate the self-healing operation after receiving the self-healing startup information, thereby avoiding the conflict that may be caused by repeated activation of the self-healing operation.
  • the recipient of the status information for the NFVI failure may be VNFM and/or NFVO.
  • this status information can be used to indicate the status of the NFVI failure, that is, the status information can represent the processing stage of the NFVI failure. For example, whether the NFVI failure has initiated a self-healing operation.
  • the status information may include self-healing startup information, where the self-healing startup information is used to indicate that the self-healing operation for the NFVI failure has been initiated, so that the NFVO and/or the VNFM prohibit the repetition according to the self-healing startup information. Start the VNF self-healing operation.
  • the self-healing start information is used as an indication to inform the NFVO and/or VNFM that the self-healing operation for the NFVI failure by the VIM is in progress, and the VNF failure caused by the NVFI failure prohibits the self-healing operation.
  • the VNF fault triggered by the NFVI fault does not need to be self-healing again.
  • the VIM may also send the fault information of the NFVI fault to the NFVO and/or the VNFM while transmitting the self-healing start information to the NFVO and/or the VNFM.
  • the VIM may send self-healing completion information to the NFVO and/or VNFM after completing the self-healing operation, such that the NFVO and/or VNFM may trigger a re-repair of the repaired VM or VNF after receiving the self-healing completion information.
  • the self-healing start information can be used as an indication to inform the NFVO and/or VNFM that the self-healing operation for the NFVI fault by the VIM is in progress, and the VNF fault prohibition caused by the NVFI fault is prohibited. Perform self-healing operations.
  • the method shown in FIG. 10 may further include:
  • the self-healing startup information may not be sent, and only the self-healing completion information may be sent; or the self-healing completion information may be sent after the self-healing startup information is sent.
  • the NFVO and/or VNFM receives the self-healing completion information, it can trigger reconfiguration of the repaired VM or VNF.
  • the VIM may send the fault information of the NFVI fault to the NFVO and/or the VNFM.
  • the subsequent operations can be the same as the operations after the existing VIM reports the fault information.
  • the embodiment of the present invention does not limit the process after the VIM reports the fault information.
  • the VIM may perform a health check on the NFVI to detect the NFVI fault and determine the virtual impact of the NFVI fault before determining whether to perform the self-healing operation on the NFVI fault according to the self-healing policy information. machine.
  • VIM can also view self-healing strategy information.
  • performing self-healing operations on the determined network function virtualization infrastructure NFVI fault may include:
  • VIM creates a new virtual machine
  • the newly created virtual machine can continue to use the previous storage resources and network resources.
  • VIM completes the self-healing operation when VIM creates a new virtual machine.
  • the VIM can send self-healing completion information to the NFVO and/or VNFM, and the VNFM and/or the Element Management System (EMS) can perform service-related configuration on the new VM.
  • EMS Element Management System
  • FIG. 11 is a flowchart of a fault processing method based on network function virtualization according to another embodiment of the present invention.
  • the method shown in Figure 11 can be performed by NFVO and/or VNFM.
  • the method can include:
  • the status information is sent, and the status information is used to indicate that the virtual network function VNF self-healing operation is prohibited from being repeatedly started.
  • the receiving party does not repeatedly initiate the self-healing operation after receiving the self-healing startup information, thereby avoiding the conflict that may be caused by repeated activation of the self-healing operation.
  • NFVO and/or VNFM may obtain status information for the NFVI fault from the VIM.
  • this status information can be used to indicate the status of the NFVI failure, that is, the status information can represent the processing stage of the NFVI failure. For example, whether the NFVI failure has initiated a self-healing operation.
  • the status information may include self-healing startup information, and the self-healing startup information is used to indicate that the VIM has initiated a self-healing operation on the NFVI failure.
  • the VNF fault triggered by the NFVI fault does not need to be self-healing again.
  • the VIM may also send the fault information of the NFVI fault to the NFVO and/or the VNFM while transmitting the self-healing start information to the NFVO and/or the VNFM.
  • the VIM may send self-healing completion information to the NFVO and/or VNFM after completing the self-healing operation, such that the NFVO and/or VNFM may trigger a re-repair of the repaired VM or VNF after receiving the self-healing completion information.
  • the self-healing start information may be used as an indication to inform the NFVO and/or VNFM that the self-healing operation for the NFVI failure by the VIM is in progress, and the VNF failure caused by the NVFI failure prohibits the self-healing operation.
  • the method shown in FIG. 11 may further include:
  • Acquire self-healing completion information, and the self-healing completion information is used to indicate that the self-healing operation on the NFVI fault has been completed.
  • the self-healing startup information may not be acquired, and only the self-healing completion information may be acquired; or the self-healing completion information may be acquired after acquiring the self-healing startup information.
  • the NFVO and/or VNFM may trigger reconfiguration of the repaired VM or VNF.
  • FIG. 12 is a schematic flowchart of a fault handling process based on network function virtualization according to an embodiment of the present invention.
  • the process can include:
  • VIM performs a health check on NFVI.
  • VIM performs a health check on NFVI for timely detection of NFVI failures.
  • the embodiment of the present invention may implement a health check using a technique such as a heartbeat packet or a watchdog. It should be understood that the manner of the health check is not limited in the embodiment of the present invention.
  • VIM When the VIM detects an NFVI failure, determine a virtual machine that is affected by the NFVI failure.
  • the self-healing policy information obtained indicates that the self-healing operation is prohibited, the self-healing operation of the NFVI fault is prohibited and the NFVI fault is reported.
  • 1203 and 1204 can be a side-by-side step. Specifically, if the self-healing policy information indicates that the self-healing operation is initiated, the VIM performs a self-healing operation on the NFVI, and reports the NFVI fault to the NFVO or the VNFM; if the self-healing policy information indicates that the self-healing operation is prohibited, the VIM Report the NFVI fault to NFVO or VNFM and wait for a fault handling request or indication.
  • the subsequent operations may be the same as the operations after the existing VIM reports the fault information.
  • the embodiment of the present invention does not limit the process after the VIM reports the fault information of the NFVI fault.
  • 1205 and 1206 may be performed; in 1204, if the self-healing operation is prohibited, the operation after 1205 is not performed, and the fault information is directly reported and the indication is awaited.
  • VIM selects a new server to deploy virtual machines affected by NFVI failures.
  • the VIM sends fault alarm information and self-healing startup information to the NFVO and/or the VNFM.
  • the self-healing startup information is used to indicate that the VIM has initiated a self-healing operation on the NFVI failure.
  • the self-healing start information is used as an indication to inform the NFVO and/or VNFM that the self-healing operation for the NFVI failure by the VIM is in progress, and the VNF failure caused by the NVFI failure prohibits the self-healing operation.
  • the VNFM may also send fault alarm information and self-healing startup information to the EMS.
  • VIM creates a new virtual machine.
  • VIM creates a new virtual machine, if it is not a storage resource failure and a network failure, the newly created virtual machine can continue to use the previous storage resources and network resources.
  • the VIM sends a self-healing completion message to the NFVO or VNFM.
  • the self-healing completion information is used to indicate that the VIM has completed the self-healing operation on the NFVI failure.
  • the VNFM may also send the self-healing completion information to the EMS.
  • VNFM Voice Network Management
  • EMS perform service related configuration on the new virtual machine.
  • VIM completes the self-healing operation when VIM creates a new virtual machine.
  • the VIM can send self-healing completion information to the NFVO and/or VNFM, and the VNFM and/or the Element Management System (EMS) can perform service-related configuration on the new VM.
  • EMS Element Management System
  • the virtualized infrastructure manager VIM can determine based on the pre-defined self-healing policy information indicating whether the virtualized infrastructure manager performs the self-healing operation.
  • the self-healing policy information indicates that the self-healing operation is performed, the VIM can self-heal the determined fault in time. Therefore, the infrastructure failure in the embodiment of the present invention can avoid reporting time and failure analysis time, repair and process the infrastructure failure as soon as possible, reduce the fault processing delay, and improve system performance.
  • FIG. 13 is a schematic block diagram of an apparatus in accordance with one embodiment of the present invention.
  • the apparatus 1300 shown in FIG. 13 may include:
  • the determining unit 1301 determines that the network function virtualization infrastructure NFVI is faulty
  • the obtaining unit 1302 obtains self-healing policy information, and the self-healing policy information is used to indicate whether the NFVI fault is self-healing.
  • the self-healing unit 1303 performs a self-healing operation on the NFVI failure when the self-healing policy information indicates that the NFVI failure is self-healing.
  • the infrastructure failure since the infrastructure failure itself is a root cause failure, failure analysis is not required. Therefore, after determining the network function virtualization infrastructure failure, the self-healing policy information of the self-healing operation of the network function virtualization infrastructure failure may be determined according to the obtained indication. When the self-healing policy information indicates that the self-healing operation is performed, the determined fault can be self-healing in time. Therefore, the infrastructure failure in the embodiment of the present invention can avoid reporting time and failure analysis time, repair and process the infrastructure failure as soon as possible, reduce the fault processing delay, and improve system performance.
  • FIG. 13 can implement the method shown in FIG. 1 or the process shown in FIG. 12, and the repetition is not avoided, and will not be described in detail herein.
  • the self-healing policy information may include updated self-healing policy information.
  • the apparatus 1300 may further include:
  • the sending unit 1304 sends a self-healing start message, and the self-healing start information is used to indicate that the self-healing operation for the NFVI failure has been initiated.
  • the sending unit 1304 may further send self-healing completion information, where the self-healing completion information is used to indicate that the self-healing operation on the NFVI fault has been completed.
  • the sending unit 1304 may further send the fault information of the NFVI fault when the self-healing policy information indicates that the self-healing operation for the NFVI fault is prohibited.
  • the self-healing unit 1303 may select a new server to deploy the virtual machine that is subject to the NFVI failure; create a new virtual machine.
  • the self-healing policy information includes a virtual machine identifier, fault type information, and self-healing behavior information, or the self-healing policy information includes a virtual machine identifier, a virtual link identifier, a fault type information, and a self-healing Behavioral information, self-healing behavior information includes initiation of self-healing information and/or prohibition of self-healing information.
  • Figure 14 is a schematic block diagram of an apparatus in accordance with another embodiment of the present invention.
  • the apparatus 1400 shown in Figure 14 can include:
  • the determining unit 1401 determines self-healing policy information, and the self-healing policy information is used to indicate whether the NFVI fault is self-healing;
  • the sending unit 1402 sends the self-healing policy information to facilitate the self-healing operation of the NFVI fault when the self-healing policy information indicates that the determined network function virtualization infrastructure NFVI fault is self-healing.
  • the infrastructure failure since the infrastructure failure itself is a root cause failure, failure analysis is not required. Therefore, after determining the network function virtualization infrastructure failure, the self-healing policy information of the self-healing operation of the network function virtualization infrastructure failure may be determined according to the obtained indication. When the self-healing policy information indicates that the self-healing operation is performed, the determined fault can be self-healing in time. Therefore, the infrastructure failure in the embodiment of the present invention can avoid reporting time and failure analysis time, repair and process the infrastructure failure as soon as possible, reduce the fault processing delay, and improve system performance.
  • FIG. 14 can implement the method shown in FIG. 9 or the process shown in FIG. 12, and the repetition is not avoided, and will not be described in detail herein.
  • the determining unit 1401 may determine a pre-stored self-healing strategy, where the pre-stored self-healing strategy includes a network function virtualization VNF self-healing policy and/or a network service NS self-healing strategy;
  • the strategy maps or transforms to determine the self-healing strategy information.
  • the apparatus 1400 may further include:
  • the receiving unit 1403 receives the self-healing startup information, and the self-healing startup information is used to indicate that the self-healing operation for the NFVI failure has been initiated;
  • the prohibition unit 1404 prohibits the repeated activation of the self-healing operation based on the self-healing start information.
  • the receiving unit 1403 may further receive the self-healing completion information, where the self-healing completion information is used to indicate that the self-healing operation for the NFVI fault has been completed.
  • the apparatus 1400 may further include:
  • the update unit 1405 updates the pre-stored self-healing policy.
  • the VNF self-healing policy may include a VNF identifier and/or a network function virtualization component identifier, and fault type information and self-healing behavior information.
  • the NS self-healing policy may include a VNF self-healing policy and a virtual link self-healing policy between multiple VNFs, where the virtual link self-healing policy includes virtual link identification and self-healing Behavioral information.
  • the self-healing policy information may include a virtual machine identifier, fault type information, and self-healing behavior information, or the self-healing policy information includes a virtual machine identifier, a virtual link identifier, a fault type information, and a self-healing policy.
  • the more behavioral information, the self-healing behavior information includes the initiation of self-healing information and/or the prohibition of self-healing information.
  • FIG. 15 is a schematic block diagram of an apparatus in accordance with another embodiment of the present invention.
  • the apparatus 1500 shown in FIG. 15 may include:
  • the self-healing unit 1501 performs a self-healing operation on the determined network function virtualization infrastructure NFVI failure;
  • the sending unit 1502 sends status information of the NFVI fault, and the status information is used to indicate that the self-healing operation of the repeated start is prohibited.
  • the sending status information is used to indicate that the virtual network function VNF self-healing operation is prohibited from being repeatedly started.
  • the receiving party does not repeatedly initiate the self-healing operation after receiving the self-healing startup information, thereby avoiding the conflict that may be caused by repeated activation of the self-healing operation.
  • apparatus 1500 can implement the above method of FIG. 10 or the process of FIG. 12, and to avoid repetition, it will not be described in detail herein.
  • the status information includes self-healing startup information, and the self-healing startup information is used to indicate that the self-healing operation for the NFVI failure has been initiated.
  • the sending unit 1502 may further send self-healing completion information, where the self-healing completion information is used to indicate that the self-healing operation for the NFVI fault has been completed.
  • the self-healing unit 1501 may select a new server to deploy the virtual machine that is subject to the NFVI failure; create a new virtual machine.
  • Figure 16 is a schematic block diagram of an apparatus in accordance with another embodiment of the present invention.
  • the apparatus 1600 shown in Figure 16 can include:
  • the obtaining unit 1601 acquires state information of the network function virtualization infrastructure NFVI fault, and the state information is used to indicate that the restarting self-healing operation is prohibited;
  • the prohibition unit 1602 prohibits the repeated activation of the self-healing operation based on the status information.
  • status information may be sent, where the status information is used to indicate that the virtual network function VNF self-healing operation is prohibited from being repeatedly started.
  • the receiving party does not repeatedly initiate the self-healing operation after receiving the self-healing startup information, thereby avoiding the conflict that may be caused by repeated activation of the self-healing operation.
  • apparatus 1600 can implement the method of FIG. 11 or the process of FIG. 12 described above, and to avoid repetition, it will not be described in detail herein.
  • the status information includes self-healing startup information, and the self-healing startup information is used to indicate that the self-healing operation for the NFVI failure has been initiated.
  • the obtaining unit 1601 may further obtain self-healing completion information, where the self-healing completion information is used to indicate that the self-healing operation on the NFVI fault has been completed.
  • FIG. 17 is a schematic block diagram of an apparatus in accordance with another embodiment of the present invention.
  • the apparatus 1700 of FIG. 17 can be used to implement the steps and methods of the above method embodiments.
  • the apparatus of FIG. 17 includes a processor 1701 and a memory 1702.
  • the processor 1701 and the memory 1702 are connected by a bus system 1709.
  • the processor 1701 controls the operation of the device 1700.
  • the memory 1702 can include read only memory and random access memory and provides instructions and data to the processor 1701.
  • a portion of the memory 1702 may also include non-volatile line random access memory (NVRAM).
  • NVRAM non-volatile line random access memory
  • the various components of device 1700 are coupled together by a bus system 1709, which in addition to the data bus includes a power bus, a control bus, and a status signal bus. However, for clarity of description, various buses are labeled as bus system 1709 in the figure.
  • the processor 1701 may be an integrated circuit chip with signal processing capabilities.
  • the processor 1701 described above may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or discrete hardware. Component.
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or carried out.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the processor 1701 reads the information in the memory 1702 in conjunction with the various components of its hardware control device 1700.
  • the device 1700 performs the following operations:
  • the self-healing policy information is used to indicate whether the NFVI fault is self-healing
  • the self-healing policy information indicates that the NFVI fault is self-healing
  • the NFVI fault is self-healing.
  • the virtualized infrastructure manager VIM can determine based on the pre-defined self-healing policy information indicating whether the virtualized infrastructure manager performs the self-healing operation.
  • the self-healing policy information indicates that the self-healing operation is performed, the VIM can self-heal the determined fault in time. Therefore, the infrastructure failure in the embodiment of the present invention can avoid reporting time and failure analysis time, repair and process the infrastructure failure as soon as possible, reduce the fault processing delay, and improve system performance.
  • the self-healing policy information may include updated self-healing policy information.
  • the processor 1701 may further send self-healing startup information, where the self-healing startup information is used to indicate that the self-healing operation for the NFVI failure has been initiated.
  • the processor 1701 may further send self-healing completion information, where the self-healing completion information is used to indicate that the self-healing operation for the NFVI failure has been completed.
  • the processor 1701 may send the fault information of the NFVI fault.
  • the processor 1701 may select a new server to deploy the virtual machine that is faulty with the NFVI; create a new Virtual machine.
  • the self-healing policy information includes a virtual machine identifier, fault type information, and self-healing behavior information, or the self-healing policy information includes a virtual machine identifier, a virtual link identifier, a fault type information, and a self-healing Behavioral information, self-healing behavior information includes initiation of self-healing information and/or prohibition of self-healing information.
  • Figure 18 is a schematic block diagram of an apparatus in accordance with another embodiment of the present invention.
  • the apparatus 1800 of FIG. 18 can be used to implement the steps and methods of the above method embodiments.
  • the device of Figure 18 includes a processor 1801 and a memory Reservoir 1802.
  • the processor 1801 and the memory 1802 are connected by a bus system 1809.
  • the processor 1801 controls the operation of the device 1800.
  • the memory 1802 can include read only memory and random access memory and provides instructions and data to the processor 1801.
  • a portion of the memory 1802 may also include non-volatile line random access memory (NVRAM).
  • NVRAM non-volatile line random access memory
  • the various components of device 1800 are coupled together by a bus system 1809 that includes, in addition to the data bus, a power bus, a control bus, and a status signal bus. However, for clarity of description, various buses are labeled as bus system 1809 in the figure.
  • the processor 1801 may be an integrated circuit chip with signal processing capabilities.
  • the processor 1801 described above may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or discrete hardware. Component.
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or carried out.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the processor 1801 reads the information in the memory 1802 in conjunction with the various components of its hardware control device 1800.
  • the device 1800 performs the following operations:
  • the self-healing policy information is used to indicate whether the NFVI fault is self-healing
  • the self-healing policy information is sent to facilitate self-healing of the NFVI fault when the self-healing policy information indicates that the determined network function virtualization infrastructure NFVI fault is self-healing.
  • the virtualized infrastructure manager VIM can determine based on the pre-defined self-healing policy information indicating whether the virtualized infrastructure manager performs the self-healing operation.
  • the self-healing policy information indicates that the self-healing operation is performed, the VIM can self-heal the determined fault in time. Therefore, the infrastructure failure in the embodiment of the present invention can avoid reporting time and failure analysis time, repair and process the infrastructure failure as soon as possible, reduce the fault processing delay, and improve system performance.
  • the processor 1801 may receive the self-healing startup information sent by the VIM, and the self-healing startup information, after the self-healing operation is performed, when the self-healing policy information indicates that the VIM performs a self-healing operation on the NFVI failure. Used to indicate that VIM has initiated self-healing operations on NFVI failures; According to the self-healing startup information, it is forbidden to repeatedly start the virtual network function VNF self-healing operation.
  • the processor 1801 may determine a pre-stored self-healing strategy, where the pre-stored self-healing strategy includes a network function virtualization VNF self-healing policy and/or a network service NS self-healing strategy;
  • the strategy maps or transforms to determine the self-healing strategy information.
  • the processor 1801 may receive self-healing startup information, where the self-healing startup information is used to indicate that the self-healing operation for the NFVI failure has been initiated; and the self-healing operation is prohibited from being repeatedly initiated according to the self-healing startup information.
  • the processor 1801 may receive self-healing completion information, where the self-healing completion information is used to indicate that the self-healing operation for the NFVI failure has been completed.
  • the processor 1801 may further update the pre-stored self-healing policy.
  • the VNF self-healing policy includes a VNF identifier and/or a network function virtualization component identifier, and fault type information and self-healing behavior information.
  • the NS self-healing policy includes a VNF self-healing policy and a virtual link self-healing policy between multiple VNFs, where the virtual link self-healing policy includes virtual link identification and self-healing behavior. information.
  • the self-healing policy information includes a virtual machine identifier, fault type information, and self-healing behavior information, or the self-healing policy information includes a virtual machine identifier, a virtual link identifier, a fault type information, and a self-healing Behavioral information, self-healing behavior information includes initiation of self-healing information and/or prohibition of self-healing information.
  • FIG. 19 is a schematic block diagram of an apparatus in accordance with another embodiment of the present invention.
  • the apparatus 1900 of FIG. 19 can be used to implement the steps and methods of the above method embodiments.
  • the apparatus of FIG. 19 includes a processor 1901 and a memory 1902.
  • the processor 1901 and the memory 1902 are connected by a bus system 1909.
  • the processor 1901 controls the operation of the device 1900.
  • Memory 1902 can include read only memory and random access memory and provides instructions and data to processor 1901.
  • a portion of memory 1902 may also include non-volatile line random access memory (NVRAM).
  • NVRAM non-volatile line random access memory
  • the various components of device 1900 are coupled together by a bus system 1909, which in addition to the data bus includes a power bus, a control bus, and a status signal bus. However, for clarity of description, various buses are labeled as bus system 1909 in the figure.
  • the processor 1901 may be an integrated circuit chip with signal processing capabilities.
  • the processor 1901 described above may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, and a discrete gate. Or transistor logic devices, discrete hardware components.
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or carried out.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the processor 1901 reads the information in the memory 1902 in conjunction with the various components of its hardware control device 1900.
  • the device 1900 performs the following operations:
  • the status information of the NFVI fault is sent, and the status information is used to indicate that the self-healing operation is prohibited from being repeated.
  • the VIM in the embodiment of the present invention sends status information to the NFVO and/or the VNFM, and the status information is used to indicate that the NFVO and/or the VNFM prohibits the repeated activation of the virtual network function VNF self-healing operation.
  • NFVO and/or VNFM will not initiate the self-healing operation of VNF/VM after receiving the self-healing startup information, thereby avoiding the conflict that may be caused by the self-healing operation triggered by NFVO or VNFM and the self-healing operation triggered by VIM.
  • the status information may include self-healing startup information, where the self-healing startup information is used to indicate that the self-healing operation for the NFVI failure has been initiated.
  • the processor 1901 may send self-healing completion information, where the self-healing completion information is used to indicate that the self-healing operation for the NFVI failure has been completed.
  • the processor 1901 may select a new server to deploy the virtual machine that is faulty with the NFVI;
  • Figure 20 is a schematic block diagram of an apparatus in accordance with another embodiment of the present invention.
  • the apparatus 2000 of FIG. 20 can be used to implement the steps and methods of the above method embodiments.
  • the apparatus of FIG. 20 includes a processor 2001 and a memory 2002.
  • the processor 2001 and the memory 2002 are connected by a bus system 2009.
  • the processor 2001 controls the operation of the device 2000.
  • the memory 2002 can include read only memory and random access memory and provides instructions and data to the processor 2001.
  • a portion of the memory 2002 may also include non-volatile line random access memory (NVRAM).
  • NVRAM non-volatile line random access memory
  • the various components of device 2000 are coupled together by a bus system 2009, which in addition to the data bus includes a power bus, a control bus, and a status signal bus. However, for clarity of description, various buses are labeled as the bus system 2009 in the figure.
  • the processor 2001 may be an integrated circuit chip with signal processing capabilities.
  • the processor 2001 can be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, discrete hardware component.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA off-the-shelf programmable gate array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or carried out.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the processor 2001 reads the information in the memory 1902 in conjunction with the various components of its hardware control device 2000.
  • the device 2000 performs the following operations:
  • the VIM in the embodiment of the present invention sends status information to the NFVO and/or the VNFM, and the status information is used to indicate that the NFVO and/or the VNFM prohibits the repeated activation of the virtual network function VNF self-healing operation.
  • NFVO and/or VNFM will not initiate the self-healing operation of VNF/VM after receiving the self-healing startup information, thereby avoiding the conflict that may be caused by the self-healing operation triggered by NFVO or VNFM and the self-healing operation triggered by VIM.
  • the status information may include self-healing startup information, and the self-healing startup information is used to indicate that the VIM has initiated a self-healing operation on the NFVI failure.
  • the processor 2001 may obtain the self-healing completion information and use the self-healing completion information. Indicates that the self-healing operation for the NFVI failure has been completed.
  • system and “network” are used interchangeably herein.
  • the word “and/or” is merely an association relationship describing the associated object, indicating that there may be three relationships, for example, A and/or B, which may indicate that A exists separately, A and B exist simultaneously, and B exists separately. three situations.
  • the character “/” in this article generally indicates that the contextual object is an "or" relationship.
  • B corresponding to A means that B is associated with A, and B can be determined according to A.
  • determining B from A does not mean that B is only determined based on A, and that B can also be determined based on A and/or other information.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, or an electrical, mechanical or other form of connection.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the embodiments of the present invention.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or software. The form of the functional unit is implemented.
  • Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a storage medium may be any available media that can be accessed by a computer.
  • computer readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage media or other magnetic storage device, or can be used for carrying or storing in the form of an instruction or data structure.
  • connection may suitably be a computer readable medium.
  • the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave
  • coaxial cable , fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, wireless, and microwave are included in the fixing of the associated media.
  • a disk and a disc include a compact disc (CD), a laser disc, a compact disc, a digital versatile disc (DVD), a floppy disk, and a Blu-ray disc, wherein the disc is usually magnetically copied, and the disc is The laser is used to optically replicate the data. Combinations of the above should also be included within the scope of the computer readable media.

Abstract

本发明实施例提供了一种基于网络功能虚拟化的故障处理方法，该方法包括：确定网络功能虚拟化基础设施NFVI故障；获取自愈策略信息，自愈策略信息用于指示是否对NFVI故障进行自愈操作；当自愈策略信息指示对NFVI故障进行自愈操作时，对NFVI故障进行自愈操作。本发明实施例中在确定网络功能虚拟化基础设施故障后，可以根据获取的指示是否对网络功能虚拟化基础设施故障进行自愈操作的自愈策略信息进行判断。当自愈策略信息指示进行自愈操作时，能够及时对确定的故障进行自愈。因此，本发明实施例中的基础设施故障可以避免上报以及故障分析的时间，将基础设施故障尽快修复处理，减少了故障处理时延，能够提高系统性能。

Description

基于网络功能虚拟化的故障处理方法和装置 技术领域
本发明涉及通信技术领域，并且更具体地，涉及基于网络功能虚拟化的故障处理方法和装置。
背景技术
目前，网络功能虚拟化(Network Function Virtualization，NFV)技术越来越得到重视。2012年10月23日13个运营商发布了NFV白皮书，宣布在欧洲电信标准化协会(European Telecommunication Standards Institute，ETSI)成立网络功能虚拟化标准工作组(Network Function Virtualization Industry Standard Group，NFV ISG)。
运营商成立NFV ISG的目的是定义运营商网络功能虚拟化的需求和相关的技术报告，希望在通用的高性能服务器、交换机和存储中实现部分网络功能。这需要网络功能以软件方式实现，并能在通用的服务器硬件上运行，可以根据需要进行迁移、实例化、部署在网络的不同位置，并且不需要安装新设备。各种类型的网络设备，如服务器、路由器、存储设备和交换机等，都可以通过NFV技术实现软硬件分离。
现有的NFV管理和编排(Management and Orchestration，MANO)系统中，由于NFV的分层体系架构，NFV的故障可能出现在网络的不同层次。例如，网络功能虚拟化基础设施(Network Function Virtualization Infrastructure，NFVI)层的基础设施故障、虚拟网络功能(Virtualized Network Function，VNF)软件故障和网络故障等。其中，基础设施故障可以包括硬件故障(例如硬盘输入输出故障、服务器断电、端口故障等)和虚拟机(Virtualized Machine，VM)故障等。
现有的NFV的故障需要先上报故障关联实体和故障决策实体，先由故障关联实体做出故障根因分析，再由故障决策实体做出故障处理决策后，才进行故障修复。因此，NFV的故障从发现到故障修复中间会有一段分析和处理时延，以便故障决策实体能够做出正确的决策。但是，NFVI的基础设施故障不同于VNF故障，VNF故障可能由其他故障引起，而基础设施故障本身就是根因故障，不需要进行根因分析和决策。因此，现有的基础设施故障 的处理方法的处理延迟较高。
发明内容
本发明实施例提供了一种基于网络功能虚拟化的故障处理方法和装置，能够减少基础设施故障的处理时延。
第一方面，提供了一种基于网络功能虚拟化的故障处理方法，包括：确定网络功能虚拟化基础设施NFVI故障；获取自愈策略信息，该自愈策略信息用于指示是否对该NFVI故障进行自愈操作；当该自愈策略信息指示对该NFVI故障进行自愈操作时，对该NFVI故障进行自愈操作。
结合第一方面，在第一方面的第一种可能的实现方式中，该自愈策略信息包括更新后的自愈策略信息。
结合第一方面或第一方面的第一种可能的实现方式，在第一方面的第二种可能的实现方式中，在该当该自愈策略信息指示对该NFVI故障进行自愈操作时，进行自愈操作之后，还包括：发送自愈启动信息，该自愈启动信息用于指示已经启动对该NFVI故障的自愈操作。
结合第一方面的第二种可能的实现方式，在第一方面的第三种可能的实现方式中，在该发送自愈启动信息之后，还包括：发送自愈完成信息，该自愈完成信息用于指示已经完成对该NFVI故障的自愈操作。
结合第一方面或第一方面的第一种至第三种可能的实现方式中的任一种可能的实现方式，在第一方面的第四种可能的实现方式中，该方法还包括：当该自愈策略信息指示禁止对该NFVI故障进行自愈操作时，发送该NFVI故障的故障信息。
结合第一方面或第一方面的第一种至第四种可能的实现方式中的任一种可能的实现方式，在第一方面的第五种可能的实现方式中，该当该自愈策略信息指示对该NFVI故障进行自愈操作时，进行自愈操作，包括：选择新的服务器对受到该NFVI故障的虚拟机进行部署；创建新的虚拟机。
结合第一方面或第一方面的第一种至第五种可能的实现方式中的任一种可能的实现方式，在第一方面的第六种可能的实现方式中，该自愈策略信息包括虚拟机标识、故障类型信息和自愈行为信息，或者，该自愈策略信息包括虚拟机标识、虚拟链路标识、故障类型信息和自愈行为信息，该自愈行为信息包括启动自愈信息和/或禁止自愈信息。
第二方面，提供了一种基于网络功能虚拟化的故障处理方法，包括：确定自愈策略信息，该自愈策略信息用于指示是否对该NFVI故障进行自愈操作；发送该自愈策略信息，以便于当该自愈策略信息指示对确定的网络功能虚拟化基础设施NFVI故障进行自愈操作时，对该NFVI故障进行自愈操作。
结合第二方面，在第二方面的第一种可能的实现方式中，该确定自愈策略信息，包括：确定预存的自愈策略，该预存的自愈策略包括网络功能虚拟化VNF自愈策略和/或网络服务NS自愈策略；对该预存的自愈策略进行映射或转化，确定该自愈策略信息。
结合第二方面的第一种可能的实现方式，在第二方面的第二种可能的实现方式中，还包括：更新所述预存的自愈策略。
结合第二方面的第一种或第二方面的第二种可能的实现方式，在第二方面的第三种可能的实现方式中，所述VNF自愈策略包括VNF标识和/或网络功能虚拟化组件标识，以及故障类型信息和自愈行为信息。
结合第二方面的第一种至第三种可能的实现方式中的任一种可能的实现方式，在第二方面的第四种可能的实现方式中，所述NS自愈策略包括所述VNF自愈策略和多个VNF之间的虚拟链路自愈策略，其中，所述虚拟链路自愈策略包括虚拟链路标识和自愈行为信息。
结合第二方面或第二方面的第一种至第四种可能的实现方式中的任一种可能的实现方式，在第二方面的第五种可能的实现方式中，还包括：接收自愈启动信息，所述自愈启动信息用于指示已经启动对所述NFVI故障的自愈操作；根据所述自愈启动信息，禁止重复启动自愈操作。
结合第二方面的第五种可能的实现方式，在第二方面的第六种可能的实现方式中，在该接收自愈启动信息之后，还包括：接收自愈完成信息，该自愈完成信息用于指示已经完成对该NFVI故障的自愈操作。
结合第二方面或第二方面的第一种至第六种可能的实现方式中的任一种可能的实现方式，在第二方面的第七种可能的实现方式中，该自愈策略信息包括虚拟机标识、故障类型信息和自愈行为信息，或者，该自愈策略信息包括虚拟机标识、虚拟链路标识、故障类型信息和自愈行为信息，该自愈行为信息包括启动自愈信息和/或禁止自愈信息。
第三方面，提供了一种基于网络功能虚拟化的故障处理方法，包括：对确定的网络功能虚拟化基础设施NFVI故障进行自愈操作；发送该NFVI故 障的状态信息，该状态信息用于指示禁止重复启动自愈操作。
结合第三方面，在第三方面的第一种可能的实现方式中，该状态信息包括自愈启动信息，该自愈启动信息用于指示已经启动对该NFVI故障的自愈操作。
结合第三方面或第三方面的第一种可能的实现方式，在第三方面的第二种可能的实现方式中，在该发送该NFVI故障的状态信息之后，还包括：发送自愈完成信息，该自愈完成信息用于指示已经完成对该NFVI故障的自愈操作。
结合第三方面或第三方面的第一种至第二种可能的实现方式中的任一种可能的实现方式，在第三方面的第三种可能的实现方式中，该对确定的网络功能虚拟化基础设施NFVI故障进行自愈操作，包括：选择新的服务器对受到该NFVI故障的虚拟机进行部署；创建新的虚拟机。
第四方面，提供了一种基于网络功能虚拟化的故障处理方法，包括：获取网络功能虚拟化基础设施NFVI故障的状态信息，该状态信息用于指示禁止重复启动自愈操作；根据该状态信息，禁止重复启动自愈操作。
结合第四方面，在第四方面的第一种可能的实现方式中，该状态信息包括自愈启动信息，该自愈启动信息用于指示已经启动对该NFVI故障的自愈操作。
结合第四方面或第四方面的第一种可能的实现方式，在第四方面的第二种可能的实现方式中，该获取网络功能虚拟化基础设施NFVI故障的状态信息之后，还包括：获取自愈完成信息，该自愈完成信息用于指示已经完成对该NFVI故障的自愈操作。
第五方面，提供了一种装置，包括：确定单元，用于确定网络功能虚拟化基础设施NFVI故障；获取单元，用于获取自愈策略信息，该自愈策略信息用于指示是否对该NFVI故障进行自愈操作；自愈单元，用于当该自愈策略信息指示对该NFVI故障进行自愈操作时，对该NFVI故障进行自愈操作。
结合第五方面，在第五方面的第一种可能的实现方式中，该自愈策略信息包括更新后的自愈策略信息。
结合第五方面或第五方面的第一种可能的实现方式，在第五方面的第二种可能的实现方式中，还包括：发送单元，用于发送自愈启动信息，该自愈启动信息用于指示已经启动对该NFVI故障的自愈操作。
结合第五方面的第二种可能的实现方式，在第五方面的第三种可能的实现方式中，该发送单元，还用于发送自愈完成信息，该自愈完成信息用于指示已经完成对该NFVI故障的自愈操作。
结合第五方面的第二种或第三种可能的实现方式，在第五方面的第四种可能的实现方式中，该发送单元，还用于当该自愈策略信息指示禁止对该NFVI故障进行自愈操作时，发送该NFVI故障的故障信息。
结合第五方面或第五方面的第一种至第四种可能的实现方式中的任一种可能的实现方式，在第五方面的第五种可能的实现方式中，该自愈单元，具体用于选择新的服务器对受到该NFVI故障的虚拟机进行部署；创建新的虚拟机。
结合第五方面或第五方面的第一种至第五种可能的实现方式中的任一种可能的实现方式，在第五方面的第六种可能的实现方式中，该自愈策略信息包括虚拟机标识、故障类型信息和自愈行为信息，或者，该自愈策略信息包括虚拟机标识、虚拟链路标识、故障类型信息和自愈行为信息，该自愈行为信息包括启动自愈信息和/或禁止自愈信息。
第六方面，提供了一种装置，包括：确定单元，用于确定自愈策略信息，该自愈策略信息用于指示是否对该NFVI故障进行自愈操作；发送单元，用于发送该自愈策略信息，以便于当该自愈策略信息指示对确定的网络功能虚拟化基础设施NFVI故障进行自愈操作时，对该NFVI故障进行自愈操作。
结合第六方面，在第六方面的第一种可能的实现方式中，该确定单元，具体用于确定预存的自愈策略，该预存的自愈策略包括网络功能虚拟化VNF自愈策略和/或网络服务NS自愈策略；对该预存的自愈策略进行映射或转化，确定该自愈策略信息。
结合第六方面的第一种可能的实现方式，在第六方面的第二种可能的实现方式中，还包括：更新单元，用于更新该预存的自愈策略。
结合第六方面的第一种或第六方面的第二种可能的实现方式中的任一种可能的实现方式，在第六方面的第三种可能的实现方式中，该VNF自愈策略包括VNF标识和/或网络功能虚拟化组件标识，以及故障类型信息和自愈行为信息。
结合第六方面的第一种至第三种可能的实现方式中的任一种可能的实现方式，在第六方面的第四种可能的实现方式中，该NS自愈策略包括该VNF 自愈策略和多个VNF之间的虚拟链路自愈策略，其中，该虚拟链路自愈策略包括虚拟链路标识和自愈行为信息。
结合第六方面或第六方面的第一种至第四种可能的实现方式中的任一种可能的实现方式，在第六方面的第五种可能的实现方式中，接收单元，用于接收自愈启动信息，该自愈启动信息用于指示已经启动对该NFVI故障的自愈操作；禁止单元，用于根据该自愈启动信息，禁止重复启动自愈操作。
结合第六方面的第五种可能的实现方式，在第六方面的第六种可能的实现方式中，该接收单元，还用于接收接收自愈完成信息，该自愈完成信息用于指示已经完成对该NFVI故障的自愈操作。
结合第六方面或第六方面的第一种至第六种可能的实现方式中的任一种可能的实现方式，在第六方面的第七种可能的实现方式中，该自愈策略信息包括虚拟机标识、故障类型信息和自愈行为信息，或者，该自愈策略信息包括虚拟机标识、虚拟链路标识、故障类型信息和自愈行为信息，该自愈行为信息包括启动自愈信息和/或禁止自愈信息。
第七方面，提供了一种装置，包括：自愈单元，用于对确定的网络功能虚拟化基础设施NFVI故障进行自愈操作；发送单元，用于发送该NFVI故障的状态信息，该状态信息用于指示禁止重复启动自愈操作。
结合第七方面，在第七方面的第一种可能的实现方式中，该状态信息包括自愈启动信息，该自愈启动信息用于指示已经启动对该NFVI故障的自愈操作。
结合第七方面或第七方面的第一种可能的实现方式，在第七方面的第二种可能的实现方式中，该发送单元还用于发送自愈完成信息，该自愈完成信息用于指示已经完成对该NFVI故障的自愈操作。
结合第七方面或第七方面的第一种至第二种可能的实现方式中的任一种可能的实现方式，在第七方面的第三种可能的实现方式中，该自愈单元，具体用于选择新的服务器对受到该NFVI故障的虚拟机进行部署；创建新的虚拟机。
第八方面，提供了一种装置，包括：获取单元，用于获取网络功能虚拟化基础设施NFVI故障的状态信息，该状态信息用于指示禁止重复启动自愈操作；禁止单元，用于根据该状态信息，禁止重复启动自愈操作。
结合第八方面，在第八方面的第一种可能的实现方式中，该状态信息包 括自愈启动信息，该自愈启动信息用于指示已经启动对该NFVI故障的自愈操作。
结合第八方面或第八方面的第一种可能的实现方式，在第八方面的第二种可能的实现方式中，该获取单元，还用于获取自愈完成信息，该自愈完成信息用于指示已经完成对该NFVI故障的自愈操作。
本发明实施例中由于基础设施故障本身就是根因故障，不需要进行故障分析。因而，在确定网络功能虚拟化基础设施故障后，可以根据获取的指示是否对网络功能虚拟化基础设施故障进行自愈操作的自愈策略信息进行判断。当自愈策略信息指示进行自愈操作时，能够及时对确定的故障进行自愈。因此，本发明实施例中的基础设施故障可以避免上报以及故障分析的时间，将基础设施故障尽快修复处理，减少了故障处理时延，能够提高系统性能。
附图说明
为了更清楚地说明本发明实施例的技术方案，下面将对本发明实施例中所需要使用的附图作简单地介绍，显而易见地，下面所描述的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本发明一个实施例的基于网络功能虚拟化的故障处理方法。
图2是本发明一个实施例的获取自愈策略信息的过程的示意性流程图。
图3是本发明一个实施例的获取自愈策略信息的过程的示意性流程图。
图4是本发明另一实施例的获取自愈策略信息的过程的示意性流程图。
图5是本发明另一实施例的获取自愈策略信息的过程的示意性流程图。
图6是本发明另一实施例的获取自愈策略信息的过程的示意性流程图。
图7是本发明另一实施例的获取自愈策略信息的过程的示意性流程图。
图8是本发明另一实施例的基于网络功能虚拟化的故障处理方法的示意性流程图。
图9是本发明另一实施例的基于网络功能虚拟化的故障处理方法的示意性流程图。
图10是本发明另一实施例的基于网络功能虚拟化的故障处理方法的示意性流程图。
图11是本发明另一实施例的基于网络功能虚拟化的故障处理方法。
图12是本发明一个实施例的基于网络功能虚拟化的故障处理过程的示意性流程图。
图13是本发明一个实施例的装置的示意框图。
图14是本发明另一实施例的装置的示意框图。
图15是本发明另一实施例的装置的示意框图。
图16是本发明另一实施例的装置的示意框图。
图17是本发明另一实施例的装置的示意框图。
图18是本发明另一实施例的装置的示意框图。
图19是本发明另一实施例的装置的示意框图。
图20是本发明另一实施例的装置的示意框图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明的一部分实施例，而不是全部实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动的前提下所获得的所有其他实施例，都应属于本发明保护的范围。
应理解，NFV包括三个关键特性：第一，将定义网络功能的软件从通用的高性能的硬件服务器、存储以及网络交换机中完全分离出来；第二，软件和硬件组件的独立的模块化特性；第三，自动化的编排，即基于通用硬件完全自动化地远程安装和管理软件设备。
网络功能虚拟化编排器(Network Function Virtualization Orchestrator，NFVO)实现网络服务描述符(Network Service Descriptor，NSD)、虚拟网络功能转发图(Virtualized Network Function Forwarding Graph，VNFFG)的管理及处理，网络服务生命周期的管理，与虚拟网络功能管理器(Virtualized Network Function Manager，VNFM)配合实现VNF的生命周期管理和资源的全局视图功能。
VNFM实现虚拟化网元VNF的生命周期管理，包括虚拟化网络功能描述符(Virtualized Network Function Descriptor，VNFD)的管理及处理，VNF实例的初始化，VNF的扩容/缩容，VNF实例的终止。
虚拟化基础设施管理器(Virtualized Infrastructure Manager，VIM)主要负责基础设施层硬件资源，虚拟化资源的管理，监控和故障上报，面向上层 应用提供虚拟化资源池。
NFVI由硬件资源和虚拟资源以及虚拟层组成。从VNF的角度来说，虚拟层和硬件资源是能够提供所需虚拟资源的实体。
NFVI故障的处理过程可以如下：
1)NFVI故障发生后，VIM将该故障报告给VNFM/NFVO；
2)VNFM/NFVO进行故障关联和故障处理决策；
3)VNFM/NFVO向VIM发送故障修复指示；
4)VIM根据该故障修复指示进行故障修复或故障自愈，例如包括
VM迁移或创建VM等。
NFV的故障从发现到故障修复中间会有一段分析和处理时延，以便故障决策实体能够做出正确的决策。但是，NFVI的基础设施故障不同于VNF故障，VNF故障可能由其他故障引起，而基础设施故障本身就是根因故障，不需要进行根因分析和决策。因此，现有的基础设施故障的处理方法的处理延迟较高。
而且，当基础设施发生故障(如硬件故障或虚拟机故障)时，虚拟化基础设施管理器(Virtualised Infrastructure Manager，VIM)能够自行触发一些对故障的自愈操作。但是，当硬件故障或虚拟机故障时，也会触发VNF故障，同时虚拟网络功能管理器(Virtualised Network Function Manager，VNFM)或网络功能虚拟化编排器(Network Function Virtualization Orchestrator，NFVO)会通过向VIM发送启动新VM的请求来触发VNF自愈操作。因此，NFVO或VNFM触发的自愈操作和VIM触发的自愈操作可能会造成冲突。
图1是本发明一个实施例的基于网络功能虚拟化的故障处理方法。图1所示的方法100可以由虚拟化基础设施管理器VIM执行。该方法100包括：
110，确定网络功能虚拟化基础设施NFVI故障；
120，获取自愈策略信息，自愈策略信息用于指示是否对NFVI故障进行自愈操作；
130，当自愈策略信息指示对NFVI故障进行自愈操作时，对NFVI故障进行自愈操作。
本发明实施例中由于基础设施故障本身就是根因故障，不需要进行故障分析。因而，在确定网络功能虚拟化基础设施故障后，可以根据获取的指示是否对网络功能虚拟化基础设施故障进行自愈操作的自愈策略信息进行判 断。当自愈策略信息指示进行自愈操作时，能够及时对确定的故障进行自愈。因此，本发明实施例中的基础设施故障可以避免上报以及故障分析的时间，将基础设施故障尽快修复处理，减少了故障处理时延，能够提高系统性能。
应理解，NFV的故障可以包括NFVI故障，VNF故障和网络故障等。其中，NFVI故障可以包括硬件故障(例如硬盘输入输出故障、服务器断电、端口故障等)和VM故障等。VNF故障可以为VNF软件故障，NFVI故障可以传递到VNF，从而引起VNF故障。
VIM可以对NFVI进行健康检查，以便于及时发现并确定NFVI故障。健康检查可以通过心跳包或者看门狗等现有技术手段实现，本发明实施例对VIM确定NFVI故障的方式不做限定。
获取的自愈策略信息可以用来指示VIM是否对检测到的NFVI故障进行自愈。即该自愈策略信息可以指示VIM启动自愈操作，也可以指示VIM禁止自愈操作。
可选地，作为另一实施例，自愈策略信息可以由预存的自愈策略经过映射或转化得到。该预存的自愈策略可以静态地预存在于VNFD中，也可以在NSD中描述；网络运营商也可以在NFVO定义自愈策略。自愈策略进行映射或转化后，得到VIM能够识别的自愈策略信息，再由NFVO或VNFM在VNF实例化完成时发送给对应的VIM。这样，当VIM检测到NFVI故障时，可以根据该自愈策略信息自动触发针对该NFVI故障的自愈操作。
应理解，VNFM和NFVO可以识别VNF以及部署VNF对应的VM。然而，VIM只能识别VM，并不能确定VM具体对应哪个VNF。因此，VNFM和/或NFVO需要将自愈策略映射或转化为自愈策略信息，其中，自愈策略信息包括VNF实例对应的VM自愈策略信息和VM之间的内部VL自愈策略信息。
具体地，VNFD中定义的自愈策略可以包括VNF自愈策略，即针对某个或某类VNF的自愈策略；NSD中定义的自愈策略可以包括NS自愈策略，即针对某个或某类NS的自愈策略。其中NS的自愈策略可以包括组成NS的多个VNF的自愈策略和VNF之间的外部虚拟链路(VL)的自愈策略。NSD中定义的自愈策略可以包括组成网络服务(Network Service，NS)的VNF的自愈策略以及组成NS的VNFFG或虚拟链路(Virtual Link，VL)的自愈策略。
其中，当VNF由多个VNF组件(VNF Component，VNFC)组成时，VNFD中定义的VNF的自愈策略可以包括多个不同的VNFC的自愈策略，以及VNFC之间的VL的自愈策略；当VNF只包括一个VNFC时，该VNF的自愈策略可以只包括该VNFC的自愈策略。
当映射或转化后所得的自愈策略信息指示VIM对NFVI故障进行自愈操作时，VIM进行自愈操作。应理解，该自愈操作可以与现有的自愈过程相同，本发明实施例对VIM如何对检测到的NFVI故障进行自愈的方法不做限定。
可选地，作为另一实施例，自愈策略信息可以包括更新后的自愈策略信息。
具体地，NFVO或VNFM可以根据需要，更新自愈策略。换句话说，将更新后的自愈策略进行映射或转化可以得到更新后的自愈策略信息。
下面结合图2至图4详细说明获取自愈策略信息的过程。
图2是本发明一个实施例的获取自愈策略信息的过程的示意性流程图。该过程200包括：
201，NFVO对VNF自愈策略进行映射或转化。
NFVO将VNF自愈策略映射或转化为自愈策略信息，该自愈策略信息可以包括VNF实例对应的VM自愈策略信息和VM之间的内部虚拟链路VL自愈策略信息。
应理解，VNFM和NFVO可以识别VNF以及部署VNF对应的VM。然而，VIM只能识别VM，并不能确定VM具体对应哪个VNF。因此，VNFM和/或NFVO在向VIM发送自愈策略信息之前，需要将VNF自愈策略映射或转化为VNF实例对应的VM自愈策略信息和VM之间的内部VL自愈策略信息。
VNF自愈策略可以映射或转化为一个或多个VM的自愈策略信息，当VNF部署在一个VM上时，VNF自愈策略可以映射或转化为一个VM自愈策略信息；当VNF部署在多个VM上时，VNF自愈策略可以映射或转化为多个VM自愈策略信息以及VM之间的内部VL的自愈策略信息。
202，NFVO将映射或转化后的自愈策略信息发送给VIM。
该VNF自愈策略可以由运营商在NFVO中定义，也可以在VNFD中存有默认的VNF自愈策略。
图2所示的过程可以包括以下两个实施例：
可选地，作为一个实施例，运营商可以在NFVO中定义VNF自愈策略，在VNF实例化完成后，由NFVO对VNF自愈策略进行映射或转化，再由NFVO将映射或转化后的自愈策略信息直接发送给VIM。
可选地，作为另一实施例，VNFD中可以有默认的VNF自愈策略，在VNF实例化完成后，由NFVO对VNF自愈策略进行映射或转化，再由NFVO将映射或转化后的自愈策略信息直接发送给VIM。
图3是本发明一个实施例的获取自愈策略信息的过程的示意性流程图。本发明实施例中可以由VIM获取自愈策略信息。该过程300包括：
301，NFVO向VNFM发送VNF自愈策略。
302，对VNF自愈策略映射或转化为自愈策略信息，该自愈策略信息包括VNF实例对应的VM自愈策略信息和VM之间的内部虚拟链路VL自愈策略信息。
VNF自愈策略可以映射或转化为一个或多个VM的自愈策略信息，当VNF部署在一个VM上时，VNF自愈策略可以映射或转化为一个VM自愈策略信息；当VNF部署在多个VM上时，VNF自愈策略可以映射或转化为多个VM自愈策略信息以及VM之间的VL的自愈策略信息。
可选地，该映射或转化过程可以由VNFM执行，也可以由NFVO执行，本发明实施例并不限于此。
303，VNFM向VIM发送VM自愈策略信息和内部虚拟链路VL自愈策略信息。
可选地，该VNF自愈策略可以由运营商在NFVO中定义，也可以在VNFD中存有默认的VNF自愈策略。
应理解，图3所示的过程可以包含以下四个实施例：
可选地，作为一个实施例，在图3中，运营商可以在NFVO中定义VNF自愈策略，在VNF实例化时或实例化完成后，由NFVO向VNFM发送该VNF自愈策略，VNF实例化完成后，由VNFM对接收到的VNF自愈策略进行映射或转化，再由VNFM将映射或转化后的自愈策略信息发送给VIM。
可选的，作为另一实施例，运营商可以在NFVO中定义VNF自愈策略，在VNF实例化完成后，由NFVO对VNF自愈策略进行映射或转化，再由NFVO将映射或转化后的自愈策略信息发送给VNFM，再由VNFM将映射或转化后的自愈策略信息发送给VIM。
可选地，作为另一实施例，在图3中，VNFD中可以有默认的VNF自愈策略，由NFVO获取到VNFD中的VNF自愈策略，在VNF实例化时或实例化完成后，由NFVO向VNFM发送该VNF自愈策略，VNF实例化完成后，由VNFM对接收到的VNF自愈策略进行映射或转化，再由VNFM将映射或转化后的自愈策略信息发送给VIM。
可选的，作为另一实施例，VNFD中可以有默认的VNF自愈策略，由NFVO获取到VNFD中的VNF自愈策略，在VNF实例化完成后，由NFVO对VNF自愈策略进行映射或转化，再由NFVO将映射或转化后的自愈策略信息发送给VNFM，再由VNFM将映射或转化后的自愈策略信息发送给VIM。
图4是本发明另一实施例的获取自愈策略信息的过程的示意性流程图。本发明实施例中可以由VIM获取自愈策略信息。该过程400包括：
401，VNFM向NFVO发送VNF自愈策略。
402，将VNF自愈策略映射或转化自愈策略信息，该自愈策略信息包括VNF实例对应的VM自愈策略信息和VM之间的内部虚拟链路VL自愈策略信息。
VNF自愈策略可以映射或转化为一个或多个VM的自愈策略信息，当VNF部署在一个VM上时，VNF自愈策略可以映射或转化为一个VM自愈策略信息；当VNF部署在多个VM上时，VNF自愈策略可以映射或转化为多个VM自愈策略信息以及VM之间的VL的自愈策略信息。
可选地，该映射或转化过程可以由VNFM执行，也可以由NFVO执行，本发明实施例并不限于此。
403，向VIM发送VM自愈策略信息和内部虚拟链路VL自愈策略信息。
该VNF自愈策略可以由运营商在VNFM中定义，也可以在VNFD中存有默认的VNF自愈策略。403中的发送过程可以由NFVO发送，也可以由VNFM发送。
应理解，图4所示的过程可以包含以下四个实施例：
可选地，作为一个实施例，在图4中，运营商可以在VNFM中定义VNF自愈策略，在VNF实例化时或实例化完成后，由VNFM向NFVO发送该VNF自愈策略，VNF实例化完成后，由NFVO对接收到的VNF自愈策略进行映射或转化，再由VNFM将映射或转化后的自愈策略信息发送给VIM。
可选的，作为另一实施例，运营商可以在VNFM中定义VNF自愈策略，在VNF实例化完成后，由VNFM对VNF自愈策略进行映射或转化，再由VNFM将映射或转化后的自愈策略信息发送给NFVO，再由NFVO将映射或转化后的自愈策略信息发送给VIM。
可选地，作为另一实施例，在图4中，VNFD中可以有默认的VNF自愈策略，由VNFM获取到VNFD中的VNF自愈策略，在VNF实例化时或实例化完成后，由VNFM向NFVO发送该VNF自愈策略，VNF实例化完成后，由NFVO对接收到的VNF自愈策略进行映射或转化，再由NFVO将映射或转化后的自愈策略信息发送给VIM。
可选的，作为另一实施例，VNFD中可以有默认的VNF自愈策略，由VNFM获取到VNFD中的VNF自愈策略，在VNF实例化完成后，由VNFM对VNF自愈策略进行映射或转化，再由VNFM将映射或转化后的自愈策略信息发送给NFVO，再由NFVO将映射或转化后的自愈策略信息发送给VIM。
应理解，本发明实施例中的VNFM还可以不通过NFVO，直接向VIM发送映射或转化后的自愈策略信息。具体如下：
可选地，作为另一实施例，运营商可以在VNFM中定义VNF自愈策略，在VNF实例化完成后，由VNFM对VNF自愈策略进行映射或转化，再由VNFM将映射或转化后的自愈策略信息直接发送给VIM。
可选地，作为另一实施例，VNFD中可以有默认的VNF自愈策略，在VNF实例化完成后，由VNFM对VNF自愈策略进行映射或转化，再由VNFM将映射或转化后的自愈策略信息直接发送给VIM。
图5是本发明另一实施例的获取自愈策略信息的过程的示意性流程图。本发明实施例中可以由VIM获取自愈策略信息。该过程500包括：
501，NFVO确定NS自愈策略。
具体地，NFVO可以从NSD中获取NS自愈策略，也可以由运营商在NFVO中预定义NS自愈策略。
NS自愈策略中可以包括组成NS的多个VNF的自愈策略以及VNF之间的外部虚拟链路(VL)自愈策略。
502，NFVO对NS自愈策略中包括的组成NS的VNF的自愈策略映射或转换。
具体地，NFVO将NS自愈策略中的VNF的自愈策略映射或转化为VNF实例对应的VM自愈策略信息和VM之间的内部虚拟链路VL自愈策略信息。
VNF自愈策略可以映射或转化为一个或多个VM的自愈策略信息，当VNF部署在一个VM上时，VNF自愈策略可以映射或转化为一个VM自愈策略信息；当VNF部署在多个VM上时，VNF自愈策略可以映射或转化为多个VM自愈策略信息以及VM之间的内部VL的自愈策略信息。
可选地，当NS由多个VNF构成时，NFVO可以将获取的NS自愈策略中包括的组成NS的外部VL自愈策略信息映射或转换为组成NS的多个VNF实例对应的VM之间的VL自愈策略信息。
503，NFVO向VIM发送映射和转化后的自愈策略信息。
图5所示的过程可以包括以下实施例：
可选地，作为一个实施例，在图5中，NSD中可以有默认的自愈策略，由NFVO获取到NSD中的自愈策略后，在NS实例化完成后，由NFVO对获取到的NSD中的NS自愈策略进行映射或转化，再由NFVO将映射或转化后的自愈策略信息直接发送给VIM。
可选地，作为另一实施例，运营商可以在NFVO预定义NS自愈策略，在NS实例化完成后，由NFVO对获取到的NSD中的NS自愈策略进行映射或转化，再由NFVO将映射或转化后的自愈策略信息直接发送给VIM。
图6是本发明另一实施例的获取自愈策略信息的过程的示意性流程图。本发明实施例中可以由VIM获取自愈策略信息。该过程600包括：
601，NFVO确定NS自愈策略。
具体地，NFVO可以从NSD中获取NS自愈策略，也可以由运营商在NFVO中预定义NS自愈策略。
NS自愈策略中可以包括组成NS的多个VNF的自愈策略以及VNF之间的外部虚拟链路(VL)自愈策略。
602，NFVO对NS自愈策略中包括的组成NS的VNF自愈策略映射或转换。
具体地，NFVO将NS自愈策略中的VNF自愈策略映射或转化为VNF实例对应的VM自愈策略信息和VM之间的内部虚拟链路VL自愈策略信息。
VNF自愈策略可以映射或转化为一个或多个VM的自愈策略信息，当VNF部署在一个VM上时，VNF自愈策略可以映射或转化为一个VM自愈策略信息；当VNF部署在多个VM上时，VNF自愈策略可以映射或转化为多个VM自愈策略信息以及VM之间的VL的自愈策略信息。
可选地，当NS由多个VNF构成时，NFVO可以将获取的NS自愈策略中包括的组成NS的外部VL自愈策略映射或转换为组成NS的多个VNF实例对应的VM之间的VL自愈策略信息。
603，NFVO将映射或转化后的多个VM自愈策略信息以及VM之间的VL自愈策略信息发送给VNFM，由VNFM向VIM发送映射或转化后的多个VM自愈策略信息以及VM之间的VL的自愈策略信息。
604，NFVO将映射或转化后的组成NS的多个VNF实例对应的VM之间的虚拟链路自愈策略信息发送给VIM。
应理解，本发明实施例对603和604的先后顺序不做限定。
图7是本发明另一实施例的获取自愈策略信息的过程的示意性流程图。本发明实施例中可以由VIM获取自愈策略信息。该过程700包括：
701，NFVO确定NS自愈策略。
具体地，NFVO可以从NSD中获取NS自愈策略，也可以由运营商在NFVO中预定义NS自愈策略。
NS自愈策略中可以包括组成NS的多个VNF自愈策略以及VNF之间的外部虚拟链路(VL)自愈策略。
702，NFVO将NS自愈策略中包括的组成NS的VNF自愈策略发送给VNFM。
703，VNFM对收到的VNF自愈策略进行映射或转换。
具体地，VNFM将收到的VNF自愈策略映射或转换为VNF实例对应的VM自愈策略信息和VM之间的内部虚拟链路VL自愈策略信息。
VNF自愈策略可以映射或转化为一个或多个VM的自愈策略信息，当VNF部署在一个VM上时，VNF自愈策略可以映射或转化为一个VM自愈策略信息；当VNF部署在多个VM上时，VNF自愈策略可以映射或转化为多个VM自愈策略信息以及VM之间的VL的自愈策略信息。
704，VNFM将映射和转化后的自愈策略信息发送给VIM。
705，NFVO将NS自愈策略中包括的组成NS的VL自愈策略映射或转 换为组成NS的多个VNF实例对应的VM之间的虚拟链路自愈策略信息。
706，NFVO将映射和转化后的组成NS的多个VNF实例对应的VM之间的虚拟链路自愈策略信息发送给VIM。
应理解，本发明实施例中702与(705和706)的先后顺序不做限定。
以上具体描述了如何获得自愈策略信息的过程，下面将详细描述自愈策略信息和自愈策略包括的具体内容。
可选地，作为另一实施例，VNF自愈策略可以包括虚拟网络功能VNF标识，以及故障类型信息和自愈行为信息，自愈行为信息可以包括启动自愈信息和/或禁止自愈信息。
当VNF由多个VNF组件(VNF Component，VNFC)组成时，VNFD中定义的VNF的自愈策略可以包括多个不同的VNFC的自愈策略，以及VNFC之间的VL的自愈策略；当VNF只包括一个VNFC时，该VNF的自愈策略可以只包括该VNFC的自愈策略。
具体地，VNFD中定义的VNF自愈策略中的VNF标识可以为VNF厂商对VNF的标识信息(ID)，运营商定义的VNF标识可以是运营商管理域内VNF的唯一标识，也可以是指定某一类型的VNF(如MME)；故障类型信息可以包括硬件故障(例如硬盘输入输出故障)、服务器断电、主机操作系统故障、端口故障等。自愈行为信息可以包括启动自愈信息和/或禁止自愈信息，其中启动自愈信息可以指示VIM自动触发自愈操作，禁止自愈信息可以指示VIM禁止自动触发自愈操作。
运营商定义的VNF自愈策略或VNFD中定义的VNF自愈策略可以如表1所示。
表1VNF自愈策略
VNF/VNFC ID 故障类型信息 自愈行为信息
VNF ID 1 硬件故障 启动
VNFC ID 1 服务器断电 启动
VNFC ID 2 端口故障 禁止
…… …… ……
由表1可知，例如，VNF ID 1为某个VNF标识，其发生的故障类型为硬件故障，对应的自愈行为为启动，即当VNF ID 1发生故障时，且其故障类型为硬件故障时，VIM可以启动自愈操作。应理解，表1仅仅示出了包含部分VNF的自愈策略，该自愈策略还可以包括其他VNF，本发明实施例不一一列举。还应理解，VIM可以同时检测出多个故障，然后对比表1中的标识，找出该故障的标识对应的故障处理方法，即故障行为信息。可选地，该自愈策略的定义方法本发明实施例并不作限定，只需要该自愈策略能够指示是否对NVFI故障进行自愈即可。
可选地，作为另一实施例，NS自愈策略可以包括VNF自愈策略以及组成NS的多个VNF之间的VL自愈策略，其中，
VL(包括VNF内部或外部VL)自愈策略可以包括虚拟链路VL标识，以及自愈行为信息，如表2所示。自愈行为信息可以包括启动自愈信息和/或禁止自愈信息。其中，对于VNF内部VL，VL标识能标识出具体的VNF内部具体的两个VNFC之间的VL；对于VNF之间的外部VL，VL标识能标识出具体的两个VNF之间的VL。
表2VL自愈策略
VL ID 自愈行为信息
VL ID 1 启动
VL ID 2 启动
VL ID 3 禁止
…… ……
可选地，作为另一实施例，NSD中定义的NS自愈策略可以包括NS标识和自愈行为信息，其中，自愈行为信息可以包括启动自愈信息和/或禁止自愈信息，如下表3所示。
应理解，当NS包括一个VNF时，该NS自愈策略可以包括VNF自愈 策略；当NS自愈策略包括多个VNF时，该NS自愈策略包括该多个VNF自愈策略以及VNF之间的外部VL自愈策略
表3NS自愈策略
NS ID 自愈行为信息
NS ID 1 启动
NS ID 2 启动
NS ID 3 禁止
…… ……
可选地，作为另一实施例，自愈策略信息可以包括虚拟机标识、故障类型信息和自愈行为信息，或者，自愈策略信息包括虚拟机标识、虚拟链路标识、故障类型信息和自愈行为信息，自愈行为信息包括启动自愈信息和/或禁止自愈信息。
可选地，作为另一实施例，由VNF自愈策略和/或NS自愈策略映射和转化后的自愈策略信息可以包括：虚拟机VM标识，以及故障类型信息和自愈行为信息，如下表4所示。自愈行为信息可以包括启动自愈信息和/或禁止自愈信息。
表4映射或转化后的自愈策略信息
VM ID 故障类型信息 自愈行为信息
VM ID 1 硬件故障 启动
VM ID 2 服务器断电 启动
VM ID 3 端口故障 禁止
…… …… ……
可选地，作为另一实施例，VL(VNF内部或外部VL)自愈策略映射或转化后的自愈策略信息可以包括：VL标识和自愈行为信息。该自愈行为信息可以包括启动自愈信息和/或禁止自愈信息。其中，VL标识能标识出具体的两个VM之间的VL。
图8是本发明另一实施例的基于网络功能虚拟化的故障处理方法的示意性流程图。当自愈策略信息指示对NFVI故障进行自愈操作时，VIM进行自愈操作之后，方法100还可以包括：
140，发送自愈启动信息，自愈启动信息用于指示已经启动对NFVI故障的自愈操作。
本发明实施例中由于基础设施故障本身就是根因故障，不需要进行故障分析。因而，在确定网络功能虚拟化基础设施故障后，可以根据获取的指示是否针对NFVI故障进行自愈操作的自愈策略信息进行判断。当自愈策略信息指示进行自愈操作时，能够及时对确定的故障进行自愈。因此，本发明实施例中的基础设施故障可以避免上报以及故障分析的时间，将基础设施故障尽快修复处理，减少了故障处理时延，能够提高系统性能。
另外，本发明实施例中发送的能够指示已经启动对NFVI故障的自愈操作的自愈启动信息。这样，接收方在收到自愈启动信息后不会重复启动自愈操作，从而避免了重复启动自愈操作可能造成的冲突。
应理解，自愈启动信息的接收方可以为VNFM和/或NFVO。
可选地，作为另一实施例，VIM可以向NFVO和/或VNFM发送自愈启动信息。
可选地，作为另一实施例，VIM可以向NFVO和/或VNFM发送自愈启动信息时，还可以向NFVO和/或VNFM发送该NFVI故障的故障信息。
可选地，作为另一实施例，在发送自愈启动信息之后，该方法100还可以包括：
150，发送自愈完成信息，自愈完成信息用于指示已经完成对NFVI故障的自愈操作。
具体地，VIM可以在完成自愈操作之后可以向NFVO和/或VNFM发送自愈完成信息，这样，NFVO和/或VNFM可以在收到该自愈完成信息之后触发对修复后的VM或VNF进行重新配置。应理解，140中的自愈启动信息作为指示信息告知NFVO和/或VNFM由VIM针对NFVI故障的自愈操作正在进行，NVFI故障引起的VNF故障禁止进行自愈操作。
可选地，作为另一实施例，本发明实施例中也可以不发送自愈启动信息，仅发送自愈完成信息；也可以在发送自愈启动信息之后再发送自愈完成信息。这样，当NFVO和/或VNFM收到自愈完成信息之后可以触发对修复后的VM或VNF进行重新配置。可选地，作为另一实施例，当自愈策略信息指示禁止对NFVI故障进行自愈操作时，VIM可以向NFVO和/或VNFM上报该NFVI故障的故障信息。此时，之后的操作可以与现有中VIM上报故障信息之后的操作相同。本发明实施例对VIM上报故障信息之后的过程并不做限定。
可选地，作为另一实施例，VIM在根据自愈策略信息判断是否对NFVI故障进行自愈操作之前，还可以对NFVI进行健康检查，来检测NFVI故障，并确定受到该NFVI故障影响的虚拟机。同时，VIM还可以查看自愈策略信息。
可选地，作为另一实施例，当自愈策略信息指示对NFVI故障进行自愈操作时，进行自愈操作，该自愈操作的过程可以包括：
选择新的服务器对受到NFVI故障的虚拟机进行部署；
创建新的虚拟机。
应理解，VIM创建新的虚拟机时，如果不是存储资源故障和网络故障，新创建的虚拟机可以继续使用之前的存储资源和网络资源。还应理解，VIM创建新的虚拟机完成时即为VIM完成自愈操作。VIM可以将自愈完成信息发送给NFVO和/或VNFM，VNFM和/或网元管理系统(Element Management System，EMS)可以对新的VM进行业务相关的配置。
图9是本发明另一实施例的基于网络功能虚拟化的故障处理方法的示意性流程图。图9所示的方法可以由NFVO和/或VNFM执行。该方法包括：
910，确定自愈策略信息，自愈策略信息用于指示是否对NFVI故障进行自愈操作；
920，发送自愈策略信息，以便于当自愈策略信息指示对确定的网络功能虚拟化基础设施NFVI故障进行自愈操作时，对NFVI故障进行自愈操作。
本发明实施例中由于基础设施故障本身就是根因故障，不需要进行故障分析。因而，在确定网络功能虚拟化基础设施故障后，可以根据获取的指示是否针对NFVI故障进行自愈操作的自愈策略信息进行判断。当自愈策略信息指示进行自愈操作时，能够及时对确定的故障进行自愈。因此，本发明实施例中的基础设施故障可以避免上报以及故障分析的时间，将基础设施故障尽快修复处理，减少了故障处理时延，能够提高系统性能。
应理解，自愈策略信息的接收方可以为VIM。
还应理解，NFV的故障可以包括NFVI故障，VNF故障和网络故障等。其中，NFVI故障可以包括硬件故障(例如硬盘输入输出故障、服务器断电、端口故障等)和VM故障等。VNF故障可以为VNF软件故障，NFVI故障可以传递到VNF，从而引起VNF故障。
VIM可以对NFVI进行健康检查，以便于及时发现并确定NFVI故障。 健康检查可以通过心跳包或者看门狗等现有技术手段实现，本发明实施例对VIM确定NFVI故障的方式不做限定。
应理解，本发明实施例对自愈策略信息的形式和具体内容不做限定，只需要该自愈策略信息能够指示是否对NFVI故障进行自愈操作即可。
可选地，作为另一实施例，确定自愈策略信息的过程可以包括：
确定预存的自愈策略，预存的自愈策略包括网络功能虚拟化VNF自愈策略和/或网络服务NS自愈策略；对预存的自愈策略进行映射或转化，确定自愈策略信息。
该预存的自愈策略可以包括VNF自愈策略和/或NS自愈策略。换句话说，自愈策略可以静态地预存在于VNFD中，也可以在NSD中描述；网络运营商也可以在NFVO定义自愈策略。自愈策略进行映射或转化后，得到VIM能够识别的自愈策略信息，再由NFVO或VNFM在VNF实例化完成时发送给对应的VIM。这样，当VIM检测到NFVI故障时，可以根据该自愈策略信息自动触发针对该NFVI故障的自愈操作。
应理解，VNFM和NFVO可以识别VNF以及部署VNF对应的VM。然而，VIM只能识别VM，并不能确定VM具体对应哪个VNF。因此，VNFM和/或NFVO需要将自愈策略映射或转化为自愈策略信息，其中，自愈策略信息包括VNF实例对应的VM自愈策略信息和VM之间的内部VL自愈策略信息。
可选地，作为另一实施例，VNF自愈策略可以包括VNF标识和/或网络功能虚拟化组件标识，以及故障类型信息和自愈行为信息。
具体地，VNFD中定义的自愈策略可以包括VNF自愈策略，即针对某个或某类VNF的自愈策略，VNF自愈策略的内容可以如上文描述的表1所示，为避免重复，此处不再详细描述。
其中，当VNF由多个VNF组件(VNF Component，VNFC)组成时，VNFD中定义的VNF的自愈策略可以包括多个不同的VNFC的自愈策略，以及VNFC之间的VL的自愈策略；当VNF只包括一个VNFC时，该VNF的自愈策略可以只包括该VNFC的自愈策略。
具体地，VNFD中定义的VNF自愈策略中的VNF标识可以为VNF厂商对VNF的标识信息(ID)，运营商定义的VNF标识可以是运营商管理域内VNF的唯一标识，也可以是指定某一类型的VNF(如MME)；故障类型 信息可以包括硬件故障(例如硬盘输入输出故障)、服务器断电、主机操作系统故障、端口故障等。自愈行为信息可以包括启动自愈信息和/或禁止自愈信息，其中启动自愈信息可以指示VIM自动触发自愈操作，禁止自愈信息可以指示VIM禁止自动触发自愈操作。应理解，运营商定义的VNF自愈策略或VNFD中定义的VNF自愈策略可以如上文中的表1所示，为避免重复，此处不再详细描述。
可选地，作为另一实施例，NS自愈策略可以包括VNF自愈策略和多个VNF之间的虚拟链路自愈策略，其中，虚拟链路自愈策略包括虚拟链路标识和自愈行为信息。
VL(包括VNF内部或外部VL)自愈策略可以包括虚拟链路VL标识，以及自愈行为信息，可以如上文描述的表2所示。自愈行为信息可以包括启动自愈信息和/或禁止自愈信息。其中，对于VNF内部VL，VL标识能标识出具体的VNF内部具体的两个VNFC之间的VL；对于VNF之间的外部VL，VL标识能标识出具体的两个VNF之间的VL。
NSD中定义的NS自愈策略可以包括NS标识和自愈行为信息，其中，自愈行为信息可以包括启动自愈信息和/或禁止自愈信息，NS自愈策略可以如上文描述的表3所示。具体地，NS自愈策略可以如上文描述的表3所示，为避免重复，此处不再详细描述。
NSD中定义的自愈策略可以包括NS自愈策略，即针对某个或某类NS的自愈策略。其中NS的自愈策略可以包括组成NS的多个VNF的自愈策略和VNF之间的外部虚拟链路(VL)的自愈策略。NSD中定义的NS自愈策略可以包括组成网络服务(Network Service，NS)的VNF的自愈策略以及组成NS的VNFFG或虚拟链路(Virtual Link，VL)的自愈策略。
当映射或转化后所得的自愈策略信息指示VIM对NFVI故障进行自愈操作时，VIM进行自愈操作。应理解，该自愈操作可以与现有的自愈过程相同，本发明实施例对VIM如何对检测到的NFVI故障进行自愈的方法不做限定。
可选地，作为另一实施例，自愈策略信息可以包括虚拟机标识和/或虚拟链路标识，以及故障类型信息和自愈行为信息，自愈行为信息包括启动自愈信息和/或禁止自愈信息。
由上文描述可知，自愈策略信息可以由VNF自愈策略和/或NS自愈策略映射和转化后得到，该自愈策略信息可以包括：虚拟机VM标识，或者， 虚拟机标识和虚拟链路标识，以及故障类型信息和自愈行为信息，如上文中的描述表4所示。自愈行为信息可以包括启动自愈信息和/或禁止自愈信息。
也就是说，当NS包括一个VNF时，该NS自愈策略映射或转化后的自愈策略信息可以包括：虚拟机标识，故障类型信息和自愈行为信息；当NS自愈策略包括多个VNF时，该NS自愈策略包括该多个VNF自愈策略以及VNF之间的外部VL自愈策略，该外部VL自愈策略可以映射或转化成VM之间的VL自愈策略信息。该VL自愈策略信息可以包括VL标识和自愈行为信息。因此，该NS自愈策略映射或转化后的自愈策略信息可以包括：虚拟机标识、虚拟链路标识、故障类型信息和自愈行为信息。
可选地，作为另一实施例，VL(VNF内部或外部VL)自愈策略映射或转化后的自愈策略信息可以包括：VL标识和自愈行为信息。该自愈行为信息可以包括启动自愈信息和/或禁止自愈信息。其中，VL标识能标识出具体的两个VM之间的VL。
可选地，作为另一实施例，当自愈策略信息指示VIM对NFVI故障进行自愈操作时，进行自愈操作之后，该方法还可以包括：
930，接收自愈启动信息，自愈启动信息用于指示已经启动对NFVI故障的自愈操作；
940，根据自愈启动信息，禁止重复启动自愈操作。
本发明实施例中的VIM向NFVO和/或VNFM发送能够指示启动VIM对NFVI故障的自愈操作的自愈启动信息。这样，NFVO和/或VNFM在收到自愈启动信息后不会启动VNF/VM的自愈操作，从而避免了NFVO或VNFM触发的自愈操作和VIM触发的自愈操作可能造成的冲突。
可选地，作为另一实施例，当接收自愈启动信息之后，该方法还可以包括：
950，接收自愈完成信息，自愈完成信息用于指示已经完成对NFVI故障的自愈操作。
应理解，若NFVI故障触发VNF/VM故障，NFVO和/或VNFM可以在接收到自愈完成信息后，启动虚拟网络功能VNF进行自愈操作。若新的VM创建完成且NFVO和/或VNFM接收到该自愈完成信息后，VNFM和/或EMS可以对新的VM进行业务相关的配置。
可选地，作为另一实施例，图9所示的方法还可以包括：
960，更新预存的自愈策略。
具体地，NFVO或VNFM可以根据需要，更新自愈策略。换句话说，将更新后的自愈策略进行映射或转化可以得到更新后的自愈策略信息。
图10是本发明另一实施例的基于网络功能虚拟化的故障处理方法的示意性流程图。图10所示的方法可以由VIM执行。该方法可以包括：
1010，对确定的网络功能虚拟化基础设施NFVI故障进行自愈操作；
1020，发送NFVI故障的状态信息，状态信息用于指示禁止重复启动自愈操作。
本发明实施例中向NFVO和/或VNFM发送状态信息，该状态信息用于指示禁止虚拟网络功能VNF进行自愈操作。这样，接收方在收到自愈启动信息后不会重复启动自愈操作，从而避免了重复启动自愈操作可能造成的冲突。
应理解，NFVI故障的状态信息的接收方可以为VNFM和/或NFVO。
还应理解，该状态信息可以用于表示NFVI故障的状态，也就是说，该状态信息可以表示NFVI故障的处理阶段。例如，NFVI故障是否已经启动自愈操作。
可选地，作为另一实施例，状态信息可以包括自愈启动信息，自愈启动信息用于指示已经启动对NFVI故障的自愈操作，以便于NFVO和/或VNFM根据自愈启动信息禁止重复启动VNF自愈操作。
应理解，自愈启动信息作为指示信息告知NFVO和/或VNFM由VIM针对NFVI故障的自愈操作正在进行，NVFI故障引起的VNF故障禁止进行自愈操作。
也就是说，若NFVI故障已经处理，该NFVI故障触发的VNF故障则不需要再次进行自愈操作。
VIM在向NFVO和/或VNFM发送自愈启动信息的同时，还可以向NFVO和/或VNFM发送该NFVI故障的故障信息。
具体地，VIM可以在完成自愈操作之后向NFVO和/或VNFM发送自愈完成信息，这样，NFVO和/或VNFM可以在收到该自愈完成信息之后触发对修复后的VM或VNF进行重新配置。
应理解，自愈启动信息可以作为指示信息告知NFVO和/或VNFM由VIM针对NFVI故障的自愈操作正在进行，NVFI故障引起的VNF故障禁止 进行自愈操作。
可选地，作为另一实施例，在发送状态信息之后，图10所示的方法还可以包括：
1030，发送自愈完成信息，自愈完成信息用于指示已经完成对NFVI故障的自愈操作。
可选地，作为另一实施例，本发明实施例中也可以不发送自愈启动信息，仅发送自愈完成信息；也可以在发送自愈启动信息之后再发送自愈完成信息。这样，当NFVO和/或VNFM收到自愈完成信息之后可以触发对修复后的VM或VNF进行重新配置。
可选地，作为另一实施例，当自愈策略信息指示禁止对NFVI故障进行自愈操作时，VIM可以向NFVO和/或VNFM发送该NFVI故障的故障信息。此时，之后的操作可以与现有的VIM上报故障信息之后的操作相同。本发明实施例对VIM上报故障信息之后的过程并不做限定。
可选地，作为另一实施例，VIM在根据自愈策略信息判断是否对NFVI故障进行自愈操作之前，还可以对NFVI进行健康检查，来检测NFVI故障，并确定受到该NFVI故障影响的虚拟机。同时，VIM还可以查看自愈策略信息。
可选地，作为另一实施例，对确定的网络功能虚拟化基础设施NFVI故障进行自愈操作可以包括：
选择新的服务器对受到NFVI故障的虚拟机进行部署；
创建新的虚拟机。
应理解，VIM创建新的虚拟机时，如果不是存储资源故障和网络故障，新创建的虚拟机可以继续使用之前的存储资源和网络资源。还应理解，VIM创建新的虚拟机完成时即为VIM完成自愈操作。VIM可以将自愈完成信息发送给NFVO和/或VNFM，VNFM和/或网元管理系统(Element Management System，EMS)可以对新的VM进行业务相关的配置。
图11是本发明另一实施例的基于网络功能虚拟化的故障处理方法。图11所示的方法可以由NFVO和/或VNFM执行。该方法可以包括：
1110，获取网络功能虚拟化基础设施NFVI故障的状态信息，状态信息用于指示禁止重复启动自愈操作；
1120，根据状态信息，禁止重复启动自愈操作。
本发明实施例中发送状态信息，该状态信息用于指示禁止重复启动虚拟网络功能VNF自愈操作。这样，接收方在收到自愈启动信息后不会重复启动自愈操作，从而避免了重复启动自愈操作可能造成的冲突。
应理解，NFVO和/或VNFM可以从VIM获取该NFVI故障的状态信息。
还应理解，该状态信息可以用于表示NFVI故障的状态，也就是说，该状态信息可以表示NFVI故障的处理阶段。例如，NFVI故障是否已经启动自愈操作。
可选地，作为另一实施例，状态信息可以包括自愈启动信息，自愈启动信息用于指示VIM已经启动对NFVI故障的自愈操作。
也就是说，若NFVI故障已经处理，侧该NFVI故障触发的VNF故障则不需要再次进行自愈操作。
VIM在向NFVO和/或VNFM发送自愈启动信息的同时，还可以向NFVO和/或VNFM发送该NFVI故障的故障信息。
具体地，VIM可以在完成自愈操作之后向NFVO和/或VNFM发送自愈完成信息，这样，NFVO和/或VNFM可以在收到该自愈完成信息之后触发对修复后的VM或VNF进行重新配置。
应理解，自愈启动信息可以作为指示信息告知NFVO和/或VNFM由VIM针对NFVI故障的自愈操作正在进行，NVFI故障引起的VNF故障禁止进行自愈操作。
可选地，作为另一实施例，在获取状态信息之后，图11所示的方法还可以包括：
1130，获取自愈完成信息，自愈完成信息用于指示已经完成对NFVI故障的自愈操作。
可选地，作为另一实施例，本发明实施例中也可以不获取自愈启动信息，仅获取自愈完成信息；也可以在获取自愈启动信息之后再获取自愈完成信息。这样，当NFVO和/或VNFM获取到自愈完成信息之后可以触发对修复后的VM或VNF进行重新配置。
图12是本发明一个实施例的基于网络功能虚拟化的故障处理过程的示意性流程图。该过程可以包括：
1201，VIM对NFVI进行健康检查。
VIM对NFVI进行健康检查，用于及时发现NFVI故障。
具体地，本发明实施例可以采用心跳包或者看门狗等技术实现健康检查。应理解，本发明实施例对健康检查的方式不做限定。
1202，当VIM检测到NFVI故障时，确定受到该NFVI故障影响的虚拟机。
1203，当获取的自愈策略信息指示启动自愈操作时，启动对NFVI故障的自愈操作。
1204，当获取的自愈策略信息指示禁止自愈操作时，禁止对NFVI故障的自愈操作并上报NFVI故障。
应理解，1203和1204可以为并列的步骤。具体地，若该自愈策略信息指示启动自愈操作，则VIM针对该NFVI进行自愈操作，并将该NFVI故障上报给NFVO或VNFM；若该自愈策略信息指示禁止自愈操作，则VIM将该NFVI故障上报给NFVO或VNFM，并等待故障处理请求或指示。
此时，之后的操作可以与现有中VIM上报故障信息之后的操作相同。本发明实施例对VIM上报NFVI故障的故障信息之后的过程并不做限定。
在1203中，若启动对NFVI故障的自愈操作之后，可以进行1205和1206；在1204中，若禁止自愈操作时，则不执行1205之后的操作，直接上报故障信息并等待指示。
1205，VIM选择新的服务器来部署受NFVI故障影响的虚拟机。
1206，VIM向NFVO和/或VNFM发送故障告警信息和自愈启动信息。
具体地，自愈启动信息用于指示VIM已经启动对NFVI故障的自愈操作。自愈启动信息作为指示信息告知NFVO和/或VNFM由VIM针对NFVI故障的自愈操作正在进行，NVFI故障引起的VNF故障禁止进行自愈操作。
可选地，作为另一实施例，VNFM还可以将故障告警信息和自愈启动信息发送到EMS。
1207，VIM创建新的虚拟机。
应理解，VIM创建新的虚拟机时，如果不是存储资源故障和网络故障，新创建的虚拟机可以继续使用之前的存储资源和网络资源。
1208，当新的虚拟机创建完成后，VIM向NFVO或VNFM发送自愈完成信息。
具体地，自愈完成信息用于指示VIM已经完成对NFVI故障的自愈操作。
可选地，作为另一实施例，VNFM还可以将自愈完成信息发送到EMS。
1209，VNFM和/或EMS对新的虚拟机进行业务相关的配置。
还应理解，VIM创建新的虚拟机完成时即为VIM完成自愈操作。VIM可以将自愈完成信息发送给NFVO和/或VNFM，VNFM和/或网元管理系统(Element Management System，EMS)可以对新的VM进行业务相关的配置。
本发明实施例中由于基础设施故障本身就是根因故障，不需要进行故障分析。因而，在确定网络功能虚拟化基础设施故障后，虚拟化基础设施管理器VIM可以根据预先定义的指示虚拟化基础设施管理器是否进行自愈操作的自愈策略信息进行判断。当自愈策略信息指示进行自愈操作时，VIM能够及时对确定的故障进行自愈。因此，本发明实施例中的基础设施故障可以避免上报以及故障分析的时间，将基础设施故障尽快修复处理，减少了故障处理时延，能够提高系统性能。
图13是本发明一个实施例的装置的示意框图。图13所示的装置1300可以包括：
确定单元1301确定网络功能虚拟化基础设施NFVI故障；
获取单元1302获取自愈策略信息，自愈策略信息用于指示是否对NFVI故障进行自愈操作；
自愈单元1303当自愈策略信息指示对NFVI故障进行自愈操作时，对NFVI故障进行自愈操作。
本发明实施例中由于基础设施故障本身就是根因故障，不需要进行故障分析。因而，在确定网络功能虚拟化基础设施故障后，可以根据获取的指示是否对网络功能虚拟化基础设施故障进行自愈操作的自愈策略信息进行判断。当自愈策略信息指示进行自愈操作时，能够及时对确定的故障进行自愈。因此，本发明实施例中的基础设施故障可以避免上报以及故障分析的时间，将基础设施故障尽快修复处理，减少了故障处理时延，能够提高系统性能。
应理解，图13所示的装置可以实现图1所示的方法或图12所示的过程，未避免重复，此处不再详细描述。
可选地，作为另一实施例，自愈策略信息可以包括更新后的自愈策略信息。
可选地，作为另一实施例，该装置1300还可以包括：
发送单元1304发送自愈启动信s息，自愈启动信息用于指示已经启动对NFVI故障的自愈操作。
可选地，作为另一实施例，发送单元1304还可以发送自愈完成信息，自愈完成信息用于指示已经完成对NFVI故障的自愈操作。
可选地，作为另一实施例，发送单元1304还可以当自愈策略信息指示禁止对NFVI故障进行自愈操作时，发送NFVI故障的故障信息。
可选地，作为另一实施例，自愈单元1303可以选择新的服务器对受到NFVI故障的虚拟机进行部署；创建新的虚拟机。
可选地，作为另一实施例，自愈策略信息包括虚拟机标识、故障类型信息和自愈行为信息，或者，自愈策略信息包括虚拟机标识、虚拟链路标识、故障类型信息和自愈行为信息，自愈行为信息包括启动自愈信息和/或禁止自愈信息。
图14是本发明另一实施例的装置的示意框图。图14所示的装置1400可以包括：
确定单元1401确定自愈策略信息，自愈策略信息用于指示是否对NFVI故障进行自愈操作；
发送单元1402发送自愈策略信息，以便于当自愈策略信息指示对确定的网络功能虚拟化基础设施NFVI故障进行自愈操作时，对NFVI故障进行自愈操作。
本发明实施例中由于基础设施故障本身就是根因故障，不需要进行故障分析。因而，在确定网络功能虚拟化基础设施故障后，可以根据获取的指示是否对网络功能虚拟化基础设施故障进行自愈操作的自愈策略信息进行判断。当自愈策略信息指示进行自愈操作时，能够及时对确定的故障进行自愈。因此，本发明实施例中的基础设施故障可以避免上报以及故障分析的时间，将基础设施故障尽快修复处理，减少了故障处理时延，能够提高系统性能。
应理解，图14所示的装置可以实现图9所示的方法或图12所示的过程，未避免重复，此处不再详细描述。
可选地，作为另一实施例，确定单元1401可以确定预存的自愈策略，预存的自愈策略包括网络功能虚拟化VNF自愈策略和/或网络服务NS自愈策略；对预存的自愈策略进行映射或转化，确定自愈策略信息。
可选地，作为另一实施例，该装置1400还可以包括：
接收单元1403接收自愈启动信息，自愈启动信息用于指示已经启动对NFVI故障的自愈操作；
禁止单元1404根据自愈启动信息，禁止重复启动自愈操作。
可选地，作为另一实施例，接收单元1403还可以接收接收自愈完成信息，自愈完成信息用于指示已经完成对NFVI故障的自愈操作。
可选地，作为另一实施例，该装置1400还可以包括：
更新单元1405更新预存的自愈策略。
可选地，作为另一实施例，VNF自愈策略可以包括VNF标识和/或网络功能虚拟化组件标识，以及故障类型信息和自愈行为信息。
可选地，作为另一实施例，NS自愈策略可以包括VNF自愈策略和多个VNF之间的虚拟链路自愈策略，其中，虚拟链路自愈策略包括虚拟链路标识和自愈行为信息。
可选地，作为另一实施例，自愈策略信息可以包括虚拟机标识、故障类型信息和自愈行为信息，或者，自愈策略信息包括虚拟机标识、虚拟链路标识、故障类型信息和自愈行为信息，自愈行为信息包括启动自愈信息和/或禁止自愈信息。
图15是本发明另一实施例的装置的示意框图。图15所示的装置1500可以包括：
自愈单元1501对确定的网络功能虚拟化基础设施NFVI故障进行自愈操作；
发送单元1502发送NFVI故障的状态信息，状态信息用于指示禁止重复启动自愈操作。
本发明实施例中的发送状态信息，该状态信息用于指示禁止重复启动虚拟网络功能VNF自愈操作。这样，接收方在收到自愈启动信息后不会重复启动自愈操作，从而避免了重复启动自愈操作可能造成的冲突。
应理解，该装置1500可以实现上述图10的方法或图12的过程，为避免重复，此处不再详细描述。
可选地，作为另一实施例，状态信息包括自愈启动信息，自愈启动信息用于指示已经启动对NFVI故障的自愈操作。
可选地，作为另一实施例，发送单元1502还可以发送自愈完成信息，自愈完成信息用于指示已经完成对NFVI故障的自愈操作。
可选地，作为另一实施例，自愈单元1501可以选择新的服务器对受到NFVI故障的虚拟机进行部署；创建新的虚拟机。
图16是本发明另一实施例的装置的示意框图。图16所示的装置1600可以包括：
获取单元1601获取网络功能虚拟化基础设施NFVI故障的状态信息，状态信息用于指示禁止重复启动自愈操作；
禁止单元1602根据状态信息，禁止重复启动自愈操作。
本发明实施例中可以发送状态信息，该状态信息用于指示禁止重复启动虚拟网络功能VNF自愈操作。这样，接收方在收到自愈启动信息后不会重复启动自愈操作，从而避免了重复启动自愈操作可能造成的冲突。
应理解，该装置1600可以实现上述图11的方法或图12的过程，为避免重复，此处不再详细描述。
可选地，作为另一实施例，状态信息包括自愈启动信息，自愈启动信息用于指示已经启动对NFVI故障的自愈操作。
可选地，作为另一实施例，获取单元1601还可以获取自愈完成信息，自愈完成信息用于指示已经完成对NFVI故障的自愈操作。
图17是本发明另一实施例的装置的示意框图。图17的装置1700可用于实现上述方法实施例中各步骤及方法。图17的装置包括处理器1701和存储器1702。处理器1701和存储器1702通过总线系统1709连接。
处理器1701控制装置1700的操作。存储器1702可以包括只读存储器和随机存取存储器，并向处理器1701提供指令和数据。存储器1702的一部分还可以包括非易失行随机存取存储器(NVRAM)。装置1700的各个组件通过总线系统1709耦合在一起，其中总线系统1709除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图中将各种总线都标为总线系统1709。
处理器1701可能是一种集成电路芯片，具有信号的处理能力。上述的处理器1701可以是通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本发明实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。处理器1701读取存储器1702中的信息，结合其硬件控制装置1700的各个部件。
图1的方法可以在图17的装置1700中实现，为避免重复，不再详细描 述。
具体地，在处理器1701的控制之下，装置1700完成以下操作：
确定网络功能虚拟化基础设施NFVI故障；
获取自愈策略信息，自愈策略信息用于指示是否对NFVI故障进行自愈操作；
当自愈策略信息指示对NFVI故障进行自愈操作时，对NFVI故障进行自愈操作。
本发明实施例中由于基础设施故障本身就是根因故障，不需要进行故障分析。因而，在确定网络功能虚拟化基础设施故障后，虚拟化基础设施管理器VIM可以根据预先定义的指示虚拟化基础设施管理器是否进行自愈操作的自愈策略信息进行判断。当自愈策略信息指示进行自愈操作时，VIM能够及时对确定的故障进行自愈。因此，本发明实施例中的基础设施故障可以避免上报以及故障分析的时间，将基础设施故障尽快修复处理，减少了故障处理时延，能够提高系统性能。
可选地，作为另一实施例，自愈策略信息可以包括更新后的自愈策略信息。
可选地，作为另一实施例，处理器1701还可以发送自愈启动信息，自愈启动信息用于指示已经启动对NFVI故障的自愈操作。
可选地，作为另一实施例，处理器1701还可以发送自愈完成信息，自愈完成信息用于指示已经完成对NFVI故障的自愈操作。
可选地，作为另一实施例，当自愈策略信息指示禁止对NFVI故障进行自愈操作时，处理器1701可以发送NFVI故障的故障信息。可选地，作为另一实施例，当自愈策略信息指示对NFVI故障进行自愈操作时，进行自愈操作，处理器1701可以选择新的服务器对受到NFVI故障的虚拟机进行部署；创建新的虚拟机。
可选地，作为另一实施例，自愈策略信息包括虚拟机标识、故障类型信息和自愈行为信息，或者，自愈策略信息包括虚拟机标识、虚拟链路标识、故障类型信息和自愈行为信息，自愈行为信息包括启动自愈信息和/或禁止自愈信息。
图18是本发明另一实施例的装置的示意框图。图18的装置1800可用于实现上述方法实施例中各步骤及方法。图18的装置包括处理器1801和存 储器1802。处理器1801和存储器1802通过总线系统1809连接。
处理器1801控制装置1800的操作。存储器1802可以包括只读存储器和随机存取存储器，并向处理器1801提供指令和数据。存储器1802的一部分还可以包括非易失行随机存取存储器(NVRAM)。装置1800的各个组件通过总线系统1809耦合在一起，其中总线系统1809除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图中将各种总线都标为总线系统1809。
处理器1801可能是一种集成电路芯片，具有信号的处理能力。上述的处理器1801可以是通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本发明实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。处理器1801读取存储器1802中的信息，结合其硬件控制装置1800的各个部件。
图9的方法可以在图18的装置1800中实现，为避免重复，不再详细描述。
具体地，在处理器1801的控制之下，装置1800完成以下操作：
确定自愈策略信息，自愈策略信息用于指示是否对NFVI故障进行自愈操作；
发送自愈策略信息，以便于当自愈策略信息指示对确定的网络功能虚拟化基础设施NFVI故障进行自愈操作时，对NFVI故障进行自愈操作。
本发明实施例中由于基础设施故障本身就是根因故障，不需要进行故障分析。因而，在确定网络功能虚拟化基础设施故障后，虚拟化基础设施管理器VIM可以根据预先定义的指示虚拟化基础设施管理器是否进行自愈操作的自愈策略信息进行判断。当自愈策略信息指示进行自愈操作时，VIM能够及时对确定的故障进行自愈。因此，本发明实施例中的基础设施故障可以避免上报以及故障分析的时间，将基础设施故障尽快修复处理，减少了故障处理时延，能够提高系统性能。
可选地，作为另一实施例，处理器1801可以在当自愈策略信息指示VIM对NFVI故障进行自愈操作时，进行自愈操作之后，接收VIM发送的自愈启动信息，自愈启动信息用于指示VIM已经启动对NFVI故障的自愈操作；根 据自愈启动信息，禁止重复启动虚拟网络功能VNF自愈操作。
可选地，作为另一实施例，处理器1801可以确定预存的自愈策略，预存的自愈策略包括网络功能虚拟化VNF自愈策略和/或网络服务NS自愈策略；对预存的自愈策略进行映射或转化，确定自愈策略信息。
可选地，作为另一实施例，处理器1801可以接收自愈启动信息，自愈启动信息用于指示已经启动对NFVI故障的自愈操作；根据自愈启动信息，禁止重复启动自愈操作。
可选地，作为另一实施例，处理器1801可以接收自愈完成信息，自愈完成信息用于指示已经完成对NFVI故障的自愈操作。
可选地，作为另一实施例，处理器1801还可以更新预存的自愈策略。
可选地，作为另一实施例，VNF自愈策略包括VNF标识和/或网络功能虚拟化组件标识，以及故障类型信息和自愈行为信息。
可选地，作为另一实施例，NS自愈策略包括VNF自愈策略和多个VNF之间的虚拟链路自愈策略，其中，虚拟链路自愈策略包括虚拟链路标识和自愈行为信息。
可选地，作为另一实施例，自愈策略信息包括虚拟机标识、故障类型信息和自愈行为信息，或者，自愈策略信息包括虚拟机标识、虚拟链路标识、故障类型信息和自愈行为信息，自愈行为信息包括启动自愈信息和/或禁止自愈信息。
图19是本发明另一实施例的装置的示意框图。图19的装置1900可用于实现上述方法实施例中各步骤及方法。图19的装置包括处理器1901和存储器1902。处理器1901和存储器1902通过总线系统1909连接。
处理器1901控制装置1900的操作。存储器1902可以包括只读存储器和随机存取存储器，并向处理器1901提供指令和数据。存储器1902的一部分还可以包括非易失行随机存取存储器(NVRAM)。装置1900的各个组件通过总线系统1909耦合在一起，其中总线系统1909除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图中将各种总线都标为总线系统1909。
处理器1901可能是一种集成电路芯片，具有信号的处理能力。上述的处理器1901可以是通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门 或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本发明实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。处理器1901读取存储器1902中的信息，结合其硬件控制装置1900的各个部件。
图10的方法可以在图19的装置1900中实现，为避免重复，不再详细描述。
具体地，在处理器1901的控制之下，装置1900完成以下操作：
对确定的网络功能虚拟化基础设施NFVI故障进行自愈操作；
发送NFVI故障的状态信息，状态信息用于指示禁止重复启动自愈操作。
本发明实施例中的VIM向NFVO和/或VNFM发送状态信息，该状态信息用于指示NFVO和/或VNFM禁止重复启动虚拟网络功能VNF自愈操作。这样，NFVO和/或VNFM在收到自愈启动信息后不会启动VNF/VM的自愈操作，从而避免了NFVO或VNFM触发的自愈操作和VIM触发的自愈操作可能造成的冲突。
可选地，作为另一实施例，状态信息可以包括自愈启动信息，自愈启动信息用于指示已经启动对NFVI故障的自愈操作。
可选地，作为另一实施例，处理器1901可以发送自愈完成信息，自愈完成信息用于指示已经完成对NFVI故障的自愈操作。
可选地，作为另一实施例，处理器1901可以选择新的服务器对受到NFVI故障的虚拟机进行部署；
创建新的虚拟机。
图20是本发明另一实施例的装置的示意框图。图20的装置2000可用于实现上述方法实施例中各步骤及方法。图20的装置包括处理器2001和存储器2002。处理器2001和存储器2002通过总线系统2009连接。
处理器2001控制装置2000的操作。存储器2002可以包括只读存储器和随机存取存储器，并向处理器2001提供指令和数据。存储器2002的一部分还可以包括非易失行随机存取存储器(NVRAM)。装置2000的各个组件通过总线系统2009耦合在一起，其中总线系统2009除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图中将各种总线都标为总线系统2009。
处理器2001可能是一种集成电路芯片，具有信号的处理能力。上述的 处理器2001可以是通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本发明实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。处理器2001读取存储器1902中的信息，结合其硬件控制装置2000的各个部件。
图11的方法可以在图20的装置2000中实现，为避免重复，不再详细描述。
具体地，在处理器2001的控制之下，装置2000完成以下操作：
获取网络功能虚拟化基础设施NFVI故障的状态信息，状态信息用于指示禁止重复启动自愈操作；
根据状态信息，禁止重复启动自愈操作。
本发明实施例中的VIM向NFVO和/或VNFM发送状态信息，该状态信息用于指示NFVO和/或VNFM禁止重复启动虚拟网络功能VNF自愈操作。这样，NFVO和/或VNFM在收到自愈启动信息后不会启动VNF/VM的自愈操作，从而避免了NFVO或VNFM触发的自愈操作和VIM触发的自愈操作可能造成的冲突。
可选地，作为另一实施例，状态信息可以包括自愈启动信息，自愈启动信息用于指示VIM已经启动对NFVI故障的自愈操作。
可选地，作为另一实施例，处理器2001可以从虚拟化基础设施管理器VIM获取VIM确定的网络功能虚拟化基础设施NFVI故障的状态信息之后，获取自愈完成信息，自愈完成信息用于指示已经完成对NFVI故障的自愈操作。
应理解，说明书通篇中提到的“一个实施例”或“一实施例”意味着与实施例有关的特定特征、结构或特性包括在本发明的至少一个实施例中。因此，在整个说明书各处出现的“在一个实施例中”或“在一实施例中”未必一定指相同的实施例。此外，这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。在本发明的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本发明实施例的实施过程构成任何限定。
另外，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术 语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本发明实施例中，“与A相应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口、装置或单元的间接耦合或通信连接，也可以是电的，机械的或其它的形式连接。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本发明实施例方案的目的。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以是两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件 功能单元的形式实现。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到本发明可以用硬件实现，或固件实现，或它们的组合方式来实现。当使用软件实现时，可以将上述功能存储在计算机可读介质中或作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是计算机能够存取的任何可用介质。以此为例但不限于：计算机可读介质可以包括RAM、ROM、EEPROM、CD-ROM或其他光盘存储、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质。此外。任何连接可以适当的成为计算机可读介质。例如，如果软件是使用同轴电缆、光纤光缆、双绞线、数字用户线(DSL)或者诸如红外线、无线电和微波之类的无线技术从网站、服务器或者其他远程源传输的，那么同轴电缆、光纤光缆、双绞线、DSL或者诸如红外线、无线和微波之类的无线技术包括在所属介质的定影中。如本发明所使用的，盘(Disk)和碟(disc)包括压缩光碟(CD)、激光碟、光碟、数字通用光碟(DVD)、软盘和蓝光光碟，其中盘通常磁性的复制数据，而碟则用激光来光学的复制数据。上面的组合也应当包括在计算机可读介质的保护范围之内。
总之，以上所述仅为本发明技术方案的较佳实施例而已，并非用于限定本发明的保护范围。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (44)

  1. 一种基于网络功能虚拟化的故障处理方法，其特征在于，包括：
    确定网络功能虚拟化基础设施NFVI故障；
    获取自愈策略信息，所述自愈策略信息用于指示是否对所述NFVI故障进行自愈操作；
    当所述自愈策略信息指示对所述NFVI故障进行自愈操作时，对所述NFVI故障进行自愈操作。
  2. 根据权利要求1所述的方法，其特征在于，所述自愈策略信息包括更新后的自愈策略信息。
  3. 根据权利要求1或2所述的方法，其特征在于，在所述当所述自愈策略信息指示对所述NFVI故障进行自愈操作时，进行自愈操作之后，还包括：
    发送自愈启动信息，所述自愈启动信息用于指示已经启动对所述NFVI故障的自愈操作。
  4. 根据权利要求3所述的方法，其特征在于，在所述发送自愈启动信息之后，还包括：
    发送自愈完成信息，所述自愈完成信息用于指示已经完成对所述NFVI故障的自愈操作。
  5. 根据权利要求1-4中任一项所述的方法，其特征在于，所述方法还包括：
    当所述自愈策略信息指示禁止对所述NFVI故障进行自愈操作时，发送所述NFVI故障的故障信息。
  6. 根据权利要求1-5中任一项所述的方法，其特征在于，所述当所述自愈策略信息指示对所述NFVI故障进行自愈操作时，进行自愈操作，包括：
    选择新的服务器对受到所述NFVI故障的虚拟机进行部署；
    创建新的虚拟机。
  7. 根据权利要求1-6中任一项所述的方法，其特征在于，所述自愈策略信息包括虚拟机标识、故障类型信息和自愈行为信息，或者，所述自愈策略信息包括虚拟机标识、虚拟链路标识、故障类型信息和自愈行为信息，所述自愈行为信息包括启动自愈信息和/或禁止自愈信息。
  8. 一种基于网络功能虚拟化的故障处理方法，其特征在于，包括：
    确定自愈策略信息，所述自愈策略信息用于指示是否对所述NFVI故障进行自愈操作；
    发送所述自愈策略信息，以便于当所述自愈策略信息指示对确定的网络功能虚拟化基础设施NFVI故障进行自愈操作时，对所述NFVI故障进行自愈操作。
  9. 根据权利要求8所述的方法，其特征在于，所述确定自愈策略信息，包括：
    确定预存的自愈策略，所述预存的自愈策略包括网络功能虚拟化VNF自愈策略和/或网络服务NS自愈策略；
    对所述预存的自愈策略进行映射或转化，确定所述自愈策略信息。
  10. 根据权利要求9所述的方法，其特征在于，还包括：
    更新所述预存的自愈策略。
  11. 根据权利要求9或10所述的方法，其特征在于，所述VNF自愈策略包括VNF标识和/或网络功能虚拟化组件标识，以及故障类型信息和自愈行为信息。
  12. 根据权利要求9-11中任一项所述的方法，其特征在于，所述NS自愈策略包括所述VNF自愈策略和多个VNF之间的虚拟链路自愈策略，其中，所述虚拟链路自愈策略包括虚拟链路标识和自愈行为信息。
  13. 根据权利要求8-12中任一项所述的方法，其特征在于，在所述发送所述自愈策略信息之后，还包括：
    接收自愈启动信息，所述自愈启动信息用于指示已经启动对所述NFVI故障的自愈操作；
    根据所述自愈启动信息，禁止重复启动自愈操作。
  14. 根据权利要求13所述的方法，其特征在于，在所述接收自愈启动信息之后，还包括：
    接收自愈完成信息，所述自愈完成信息用于指示已经完成对所述NFVI故障的自愈操作。
  15. 根据权利要求8-14中任一项所述的方法，其特征在于，所述自愈策略信息包括虚拟机标识、故障类型信息和自愈行为信息，或者，所述自愈策略信息包括虚拟机标识、虚拟链路标识、故障类型信息和自愈行为信息，所述自愈行为信息包括启动自愈信息和/或禁止自愈信息。
  16. 一种基于网络功能虚拟化的故障处理方法，其特征在于，包括：
    对确定的网络功能虚拟化基础设施NFVI故障进行自愈操作；
    发送所述NFVI故障的状态信息，所述状态信息用于指示禁止重复启动自愈操作。
  17. 根据权利要求16所述的方法，其特征在于，所述状态信息包括自愈启动信息，所述自愈启动信息用于指示已经启动对所述NFVI故障的自愈操作。
  18. 根据权利要求16或17所述的方法，其特征在于，在所述发送所述NFVI故障的状态信息之后，还包括：
    发送自愈完成信息，所述自愈完成信息用于指示已经完成对所述NFVI故障的自愈操作。
  19. 根据权利要求16-18中任一项所述的方法，其特征在于，所述对确定的网络功能虚拟化基础设施NFVI故障进行自愈操作，包括：
    选择新的服务器对受到所述NFVI故障的虚拟机进行部署；
    创建新的虚拟机。
  20. 一种基于网络功能虚拟化的故障处理方法，其特征在于，包括：
    获取网络功能虚拟化基础设施NFVI故障的状态信息，所述状态信息用于指示禁止重复启动自愈操作；
    根据所述状态信息，禁止重复启动自愈操作。
  21. 根据权利要求20所述的方法，其特征在于，所述状态信息包括自愈启动信息，所述自愈启动信息用于指示已经启动对所述NFVI故障的自愈操作。
  22. 根据权利要求20或21所述的方法，其特征在于，所述获取网络功能虚拟化基础设施NFVI故障的状态信息之后，还包括：
    获取自愈完成信息，所述自愈完成信息用于指示已经完成对所述NFVI故障的自愈操作。
  23. 一种装置，其特征在于，包括：
    确定单元，用于确定网络功能虚拟化基础设施NFVI故障；
    获取单元，用于获取自愈策略信息，所述自愈策略信息用于指示是否对所述NFVI故障进行自愈操作；
    自愈单元，用于当所述自愈策略信息指示对所述NFVI故障进行自愈操 作时，对所述NFVI故障进行自愈操作。
  24. 根据权利要求23所述的装置，其特征在于，所述自愈策略信息包括更新后的自愈策略信息。
  25. 根据权利要求23或24所述的装置，其特征在于，还包括：
    发送单元，用于发送自愈启动信息，所述自愈启动信息用于指示已经启动对所述NFVI故障的自愈操作。
  26. 根据权利要求25所述的装置，其特征在于，所述发送单元，还用于发送自愈完成信息，所述自愈完成信息用于指示已经完成对所述NFVI故障的自愈操作。
  27. 根据权利要求25或26所述的装置，其特征在于，所述发送单元，还用于当所述自愈策略信息指示禁止对所述NFVI故障进行自愈操作时，发送所述NFVI故障的故障信息。
  28. 根据权利要求23-27中任一项所述的装置，其特征在于，所述自愈单元，具体用于
    选择新的服务器对受到所述NFVI故障的虚拟机进行部署；
    创建新的虚拟机。
  29. 根据权利要求23-28中任一项所述的装置，其特征在于，所述自愈策略信息包括虚拟机标识、故障类型信息和自愈行为信息，或者，所述自愈策略信息包括虚拟机标识、虚拟链路标识、故障类型信息和自愈行为信息，所述自愈行为信息包括启动自愈信息和/或禁止自愈信息。
  30. 一种装置，其特征在于，包括：
    确定单元，用于确定自愈策略信息，所述自愈策略信息用于指示是否对所述NFVI故障进行自愈操作；
    发送单元，用于发送所述自愈策略信息，以便于当所述自愈策略信息指示对确定的网络功能虚拟化基础设施NFVI故障进行自愈操作时，对所述NFVI故障进行自愈操作。
  31. 根据权利要求30所述的装置，其特征在于，所述确定单元，具体用于
    确定预存的自愈策略，所述预存的自愈策略包括网络功能虚拟化VNF自愈策略和/或网络服务NS自愈策略；
    对所述预存的自愈策略进行映射或转化，确定所述自愈策略信息。
  32. 根据权利要求31所述的装置，其特征在于，还包括：
    更新单元，用于更新所述预存的自愈策略。
  33. 根据权利要求31或32所述的装置，其特征在于，所述VNF自愈策略包括VNF标识和/或网络功能虚拟化组件标识，以及故障类型信息和自愈行为信息。
  34. 根据权利要求31-33中任一项所述的装置，其特征在于，所述NS自愈策略包括所述VNF自愈策略和多个VNF之间的虚拟链路自愈策略，其中，所述虚拟链路自愈策略包括虚拟链路标识和自愈行为信息。
  35. 根据权利要求30-34中任一项所述的装置，其特征在于，还包括：
    接收单元，用于接收自愈启动信息，所述自愈启动信息用于指示已经启动对所述NFVI故障的自愈操作；
    禁止单元，用于根据所述自愈启动信息，禁止重复启动自愈操作。
  36. 根据权利要求35所述的装置，其特征在于，所述接收单元，还用于接收接收自愈完成信息，所述自愈完成信息用于指示已经完成对所述NFVI故障的自愈操作。
  37. 根据权利要求30-36中任一项所述的装置，其特征在于，所述自愈策略信息包括虚拟机标识、故障类型信息和自愈行为信息，或者，所述自愈策略信息包括虚拟机标识、虚拟链路标识、故障类型信息和自愈行为信息，所述自愈行为信息包括启动自愈信息和/或禁止自愈信息。
  38. 一种装置，其特征在于，包括：
    自愈单元，用于对确定的网络功能虚拟化基础设施NFVI故障进行自愈操作；
    发送单元，用于发送所述NFVI故障的状态信息，所述状态信息用于指示禁止重复启动自愈操作。
  39. 根据权利要求38所述的装置，其特征在于，所述状态信息包括自愈启动信息，所述自愈启动信息用于指示已经启动对所述NFVI故障的自愈操作。
  40. 根据权利要求38或39所述的装置，其特征在于，所述发送单元还用于发送自愈完成信息，所述自愈完成信息用于指示已经完成对所述NFVI故障的自愈操作。
  41. 根据权利要求38-40中任一项所述的装置，其特征在于，所述自愈 单元，具体用于
    选择新的服务器对受到所述NFVI故障的虚拟机进行部署；
    创建新的虚拟机。
  42. 一种装置，其特征在于，包括：
    获取单元，用于获取网络功能虚拟化基础设施NFVI故障的状态信息，所述状态信息用于指示禁止重复启动自愈操作；
    禁止单元，用于根据所述状态信息，禁止重复启动自愈操作。
  43. 根据权利要求42所述的装置，其特征在于，所述状态信息包括自愈启动信息，所述自愈启动信息用于指示已经启动对所述NFVI故障的自愈操作。
  44. 根据权利要求42或43所述的装置，其特征在于，所述获取单元，还用于获取自愈完成信息，所述自愈完成信息用于指示已经完成对所述NFVI故障的自愈操作。
PCT/CN2015/076183 2015-04-09 2015-04-09 基于网络功能虚拟化的故障处理方法和装置 WO2016161605A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
RU2017134942A RU2681358C1 (ru) 2015-04-09 2015-04-09 Способ и устройство для обработки ошибок на основе виртуализации сетевых функций
PCT/CN2015/076183 WO2016161605A1 (zh) 2015-04-09 2015-04-09 基于网络功能虚拟化的故障处理方法和装置
KR1020177030272A KR102010942B1 (ko) 2015-04-09 2015-04-09 네트워크 기능 가상화 기반 장애 처리 방법 및 장치
EP15888162.3A EP3282640B1 (en) 2015-04-09 2015-04-09 Network function virtualization-based failure processing method and device
CN201580030586.9A CN106464533B (zh) 2015-04-09 2015-04-09 基于网络功能虚拟化的故障处理方法和装置
US15/722,347 US10608871B2 (en) 2015-04-09 2017-10-02 Network functions virtualization based fault processing method and apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/076183 WO2016161605A1 (zh) 2015-04-09 2015-04-09 基于网络功能虚拟化的故障处理方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/722,347 Continuation US10608871B2 (en) 2015-04-09 2017-10-02 Network functions virtualization based fault processing method and apparatus

Publications (1)

Publication Number Publication Date
WO2016161605A1 true WO2016161605A1 (zh) 2016-10-13

Family

ID=57073046

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/076183 WO2016161605A1 (zh) 2015-04-09 2015-04-09 基于网络功能虚拟化的故障处理方法和装置

Country Status (6)

Country Link
US (1) US10608871B2 (zh)
EP (1) EP3282640B1 (zh)
KR (1) KR102010942B1 (zh)
CN (1) CN106464533B (zh)
RU (1) RU2681358C1 (zh)
WO (1) WO2016161605A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110061853A (zh) * 2018-01-17 2019-07-26 中兴通讯股份有限公司 策略处理方法及装置
CN110868309A (zh) * 2018-08-27 2020-03-06 中移(苏州)软件技术有限公司 Vnfm中资源处理的方法、装置及计算机存储介质
CN113434327A (zh) * 2021-07-13 2021-09-24 上海浦东发展银行股份有限公司 一种故障处理系统、方法、设备和存储介质
CN114928533A (zh) * 2022-06-13 2022-08-19 中国电信股份有限公司 虚拟网元故障处理方法、装置、电子设备及存储介质

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3472971B1 (en) * 2016-06-16 2022-09-14 Telefonaktiebolaget LM Ericsson (publ) Technique for resolving a link failure
US10666497B2 (en) 2018-06-22 2020-05-26 Intel Corporation Localized service resiliency
WO2020091776A1 (en) * 2018-11-01 2020-05-07 Hewlett Packard Enterprise Development Lp Virtual network function response to a service interruption
US11968240B2 (en) * 2019-03-04 2024-04-23 Cisco Technology, Inc. Network posture based suggestion of applications and services
KR20230033927A (ko) * 2021-09-02 2023-03-09 삼성전자주식회사 디바이스 결함 방지 강화 방법 및 장치
CN114567539B (zh) * 2022-03-22 2024-04-12 中国农业银行股份有限公司 一种网络系统异常处理方法、装置、设备及介质
DE102022203656A1 (de) * 2022-04-12 2023-10-12 Robert Bosch Gesellschaft mit beschränkter Haftung Verfahren und Vorrichtung zum Verarbeiten von Daten

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140241247A1 (en) * 2011-08-29 2014-08-28 Telefonaktiebolaget L M Ericsson (Publ) Implementing a 3g packet core in a cloud computer with openflow data and control planes
CN104115447A (zh) * 2014-04-14 2014-10-22 华为技术有限公司 一种云计算架构下的容灾方案配置方法及装置
CN104170323A (zh) * 2014-04-09 2014-11-26 华为技术有限公司 基于网络功能虚拟化的故障处理方法及装置、系统
CN104410672A (zh) * 2014-11-12 2015-03-11 华为技术有限公司 网络功能虚拟化应用升级的方法、转发业务的方法及装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7334076B2 (en) 2005-03-08 2008-02-19 Microsoft Corporation Method and system for a guest physical address virtualization in a virtual machine environment
US8811152B2 (en) 2009-10-29 2014-08-19 At&T Intellectual Property I, L.P. System and method to support secondary channel connection from residential gateway to service provider network
EP2936754B1 (en) * 2013-01-11 2020-12-02 Huawei Technologies Co., Ltd. Network function virtualization for a network device
US9973375B2 (en) * 2013-04-22 2018-05-15 Cisco Technology, Inc. App store portal providing point-and-click deployment of third-party virtualized network functions
CN108418711B (zh) * 2013-09-30 2021-05-18 华为技术有限公司 故障管理的存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140241247A1 (en) * 2011-08-29 2014-08-28 Telefonaktiebolaget L M Ericsson (Publ) Implementing a 3g packet core in a cloud computer with openflow data and control planes
CN104170323A (zh) * 2014-04-09 2014-11-26 华为技术有限公司 基于网络功能虚拟化的故障处理方法及装置、系统
CN104115447A (zh) * 2014-04-14 2014-10-22 华为技术有限公司 一种云计算架构下的容灾方案配置方法及装置
CN104410672A (zh) * 2014-11-12 2015-03-11 华为技术有限公司 网络功能虚拟化应用升级的方法、转发业务的方法及装置

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110061853A (zh) * 2018-01-17 2019-07-26 中兴通讯股份有限公司 策略处理方法及装置
CN110061853B (zh) * 2018-01-17 2023-03-14 中兴通讯股份有限公司 策略处理方法、装置及存储介质
CN110868309A (zh) * 2018-08-27 2020-03-06 中移(苏州)软件技术有限公司 Vnfm中资源处理的方法、装置及计算机存储介质
CN113434327A (zh) * 2021-07-13 2021-09-24 上海浦东发展银行股份有限公司 一种故障处理系统、方法、设备和存储介质
CN113434327B (zh) * 2021-07-13 2022-11-25 上海浦东发展银行股份有限公司 一种故障处理系统、方法、设备和存储介质
CN114928533A (zh) * 2022-06-13 2022-08-19 中国电信股份有限公司 虚拟网元故障处理方法、装置、电子设备及存储介质
CN114928533B (zh) * 2022-06-13 2024-02-23 中国电信股份有限公司 虚拟网元故障处理方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
EP3282640A1 (en) 2018-02-14
CN106464533A (zh) 2017-02-22
EP3282640A4 (en) 2018-04-11
US20180026832A1 (en) 2018-01-25
KR102010942B1 (ko) 2019-08-14
RU2681358C1 (ru) 2019-03-06
EP3282640B1 (en) 2020-01-15
CN106464533B (zh) 2020-03-10
US10608871B2 (en) 2020-03-31
KR20170129253A (ko) 2017-11-24

Similar Documents

Publication Publication Date Title
WO2016161605A1 (zh) 基于网络功能虚拟化的故障处理方法和装置
RU2640724C1 (ru) Способ устранения неисправностей, устройство и система, основанные на виртуализации сетевых функций
US10326653B2 (en) Method for upgrading network functions virtualization application, service forwarding method, and apparatus
KR102439559B1 (ko) 경보 방법 및 디바이스
EP3291499B1 (en) Method and apparatus for network service capacity expansion
CN107005426B (zh) 一种虚拟网络功能的生命周期管理方法及装置
JP6332774B2 (ja) ネットワーク機能仮想化ｎｆｖ障害管理の装置、デバイス、および方法
JP6466003B2 (ja) Ｖｎｆフェイルオーバの方法及び装置
US11310123B2 (en) Method for managing service in network function virtualization architecture, and apparatus
JP2006114040A (ja) コンピュータクラスタのノードのフェールオーバー範囲
JP2016533655A (ja) 障害管理方法、エンティティ、及びシステム
CN106031116A (zh) 一种ns与vnf的关联方法、装置及系统
WO2019242487A1 (zh) 一种故障管理方法和相关装置
CN108347339B (zh) 一种业务恢复方法及装置
WO2019153532A1 (zh) 监控系统的部署方法、装置、计算机设备及存储介质
WO2016112676A1 (zh) 告警处理方法及装置
JP2018029344A (ja) 障害管理方法、仮想化ネットワーク機能マネージャ（ｖｎｆｍ）、及びプログラム
US20170091252A1 (en) Reconciling sensor data in a database
US20160142264A1 (en) Device recognition and management
WO2016154860A1 (zh) 一种建立vnfm之间的接口的方法、装置及系统
WO2017070963A1 (zh) 一种虚拟资源的部署方法、装置及系统
US11442756B2 (en) Common service resource application method, related device, and system
CN110022220A (zh) 名片识别中的路由激活方法及系统
WO2018018459A1 (zh) 一种策略处理的方法和设备
JP2018116446A (ja) 試験装置、試験システム、試験方法およびプログラム

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2017134942

Country of ref document: RU

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20177030272

Country of ref document: KR

Kind code of ref document: A