RU2672184C1 - Method, device and management system for processing failures - Google Patents

Abstract

FIELD: information technology.SUBSTANCE: invention provides a fault management method that can implement fault reporting and processing in the virtualization environment of network functions NFV. Method comprises the steps of: obtaining the first failure information containing the identifier of the failed device and the type of failure for the network function virtualization infrastructure object (NFVI), wherein the first failure information is used to indicate that the failure occurred in the first NFVI entity having the identifier of the failed entity; form the first comprehensive failure information corresponding to the first failure information, the first comprehensive failure information contains the first failure information and the correlated failure information of the first failure information; and performing fault recovery or reporting processing in accordance with the first comprehensive failure information.EFFECT: technical result of the invention consists in the possibility of obtaining information about failures for a hardware and / or software object to perform comprehensive processing of correlated fragments of information about failures, which can implement fault reporting and processing in the NFV environment.24 cl, 17 dwg, 4 tbl

Description

FIELD OF THE INVENTION

The present invention relates to the field of communication and, in particular, to a method, device and control system for failover.

BACKGROUND

VIRTUALIZATION OF NETWORK FUNCTIONS (NETWORK FUNCTION VIRTUALIZATION, NFV) IS INTENDED FOR IMPLEMENTATION OF THE SOFTWARE OF SOME NETWORK FUNDS. Compared with baseline, the regular virtual environment in a through ARCHITECTURE (END TO END, E2E) NFV ADDED numerous facilities software and controls devices such as object / device virtualized network FUNCTIONS (VIRTUAL NETWORK FUNCTION, VNF), device administrators virtualized infrastructure (SYSTEM VIRTUALIZATION MANAGEMENT (VIRTUALIZATION MANAGEMENT SYSTEM, VIM) AND VNF ADMINISTRATOR DEVICE, AS THE NFV ENVIRONMENT IS MORE COMPLEX THAN THE USUAL VIRTUAL ENVIRONMENT. THE METHOD FOR REPORTING AND FAILURE PROCESSING IN A USUAL VIRTUAL ENVIRONMENT CANNOT BE APPLIED TO THE NFV ENVIRONMENT. THEREFORE, IT IS NECESSARY TO CONSIDER HOW THE FAILURE MESSAGE IS CARRY OUT AND THEIR FAILURE PROCESSING IN THE COMPLEX NFV ENVIRONMENT.

Disclosure of invention

Embodiments of the present invention provide a fault management method that can implement fault reporting and processing in an NFV environment.

In accordance with the first embodiment, a failure management method is provided, comprising the steps of: obtaining through the administrator of the virtualized VIM infrastructure first failure information containing the identifier of the failed device and the type of failure for the network function virtualization infrastructure device (NFVI), where the first information about faults is used to indicate that a failure has occurred in the first NFVI device having a fault device identifier; form by means of VIM the first comprehensive failure information corresponding to the first failure information, where the first comprehensive failure information contains the first failure information and the correlated failure information of the first failure information; and perform VIM troubleshooting or message processing in accordance with the first comprehensive failure information.

With reference to the first embodiment, in the first embodiment of the first embodiment, the first NFVI device failure information containing the identifier of the failed device and the type of failure is obtained by VIM; receive the first failure information transmitted by the first NFVI device, or determine that a failure has occurred in the first NFVI device, and generate the first failure information in accordance with the failure of the first NFVI device.

With reference to the first embodiment and the method of implementing the first embodiment described above, in the second method of implementing the first embodiment, the first NFVI device is any hardware HW, host operating system (Host OS), virtual machine administrator or virtual machine device (VM) in the NFVI device, and the formation by VIM of the first comprehensive failure information in accordance with the first failure information comprises the step of: determining that the failure information transmitted by the NFVI device is elirovannym with the first device NFVI, the correlated information is the first failure information about failure; and form the first comprehensive failure information containing the first failure information and correlated failure information.

With reference to the first embodiment and the above-described methods for implementing the first embodiment, in the third method for implementing the first embodiment, performing fault elimination by VIM and processing messages corresponding to the first comprehensive failure information comprises the steps of: determining according to the type of failure in the first information about failures in the first comprehensive failure information or type of failure in the correlated failure information in the first comprehensive failure information, does VIM contain a policy failure Ia, which corresponds to the type of failure in the first information about the failure or refusal of the type correlated information about failures; and in accordance with the failure elimination policy, eliminate the failure in the first NFVI device and / or the failure of the NFVI device correlated with the first NFVI device when the VIM contains a failure elimination policy corresponding to the type of failure in the first failure information or the type of failure in the correlated failure information; either transmit the first comprehensive failure information to the VNFM or transmit the first comprehensive failure information to the orchestra when VIM does not contain a failure elimination policy corresponding to the type of failure in the first failure information or the type of failure in the correlated failure information.

With reference to the first option and the above-described methods for implementing the first option, in the fourth method for implementing the first option, in accordance with the type of failure in the first failure information in the first comprehensive failure information or the type of failure in the correlated failure information in the first comprehensive failure information whether the VIM contains a failover policy that corresponds to the type of failure in the first failure information or the type of failure in the correlated failure information, the determination contains the steps which: determine the NFVI device having the highest priority among the first NFVI device and the NFVI device correlated with the first NFVI device, where HW priority is higher than Host OS priority, Host OS priority is higher than virtual machine administrator priority and virtual machine administrator priority is higher than VM priority; determining, according to the failure type of the NFVI device having the highest priority, whether the VIM contains an appropriate failover policy; and when the VIM contains a failover policy corresponding to the failure type of the NFVI device having the highest priority, in accordance with the failover policy, the failure of the NFVI device having the highest priority is eliminated.

With reference to the first embodiment and the above-described methods for implementing the first embodiment, in the fifth method for implementing the first embodiment, after resolving in accordance with the failure elimination policy of the first NFVI device and / or the failure of the NFVI device correlated with the first NFVI device, the method further comprises the step of which: when the elimination of failure was successful, transmit a message indicating success to the orchestrator, or, when the elimination of failure was unsuccessful, transmit the first comprehensive information about Kazakh to VNFM or transmit the first comprehensive information about failures.

With reference to the first embodiment and the above-described methods for implementing the first embodiment, in the sixth method for implementing the first embodiment, after transmitting the first comprehensive failure information to the VNFM, the method further comprises the steps of: receiving an indication message transmitted by the VNFM and using it to indicate that the VNFM is unable to process the first comprehensive failure information; and transmit the first comprehensive failure information to the orchestra.

With reference to the first option and the above-described methods for implementing the first option, in the seventh method for implementing the first option, before transmitting the first comprehensive failure information to the orchestrator, the method further comprises the steps of: requesting VNFM information about the failures of the VNF device correlated with the first NFVI device ; and add fault information of the VNF device correlated with the first NFVI device to the first comprehensive fault information.

With reference to the first embodiment and the above-described methods of implementing the first embodiment, in the eighth method of implementing the first embodiment, the method further comprises the steps of: receiving the request information transmitted by the VNFM, where the request information is used to request information from the VIM about the faults of the NFVI device correlated with a faulty VNF device; and transmit the failure information of the NFVI device correlated with the faulty VNF device to the VNFM.

With reference to the first embodiment and the above-described methods for implementing the first embodiment, in the ninth method for implementing the first embodiment, after the first comprehensive failure information is generated by VIM in accordance with the first failure information, the method further comprises the steps of: detecting in accordance with the first comprehensive failure information, does VIM contain comprehensive failure information that is the same as the first comprehensive failure information; and when the VIM contains comprehensive failure information, which is the same as the first comprehensive failure information, the first comprehensive failure information is deleted.

With reference to the first embodiment and the above-described methods for implementing the first embodiment, in the tenth method for implementing the first embodiment, the first failure information is additionally communicated to the operations and business support system (OSS / BSS) so that OSS / BSS monitors and presents the first information about failures.

With reference to the first embodiment and the methods of the first embodiment described above, in the eleventh method of implementing the first embodiment, the first failure information comprises at least an operational state or time of failure; and the first comprehensive failure information additionally contains information about the failure state and the failure state contains at least one state such as: not yet processed, being processed, the failure has been eliminated, or the failure has not yet been eliminated.

According to a second embodiment, a failure management method is provided, comprising the steps of: obtaining, by the VNFM administrator of the virtualized network functions, the second failure information containing the identifier of the failed device and the type of failure for the virtualized device VNF network functions (VNF), where the second information Failures are used to indicate that a failure has occurred in the first VNF device having the identifier of the failed device; generating, by VNFM, a second comprehensive failure information corresponding to the second failure information; and performing VNFM troubleshooting or message processing in accordance with the second comprehensive failure information.

With reference to the second embodiment, in the first embodiment of the second embodiment, the second fault information containing the identifier of the failed device and the type of failure for the VNF device is obtained by VNFM, which comprises: receiving the second fault information transmitted by the first VNF device; or determining that a failure has occurred in the first VNF device and generating second failure information in accordance with the failure of the first VNF device.

With reference to the second embodiment and the above-described method of implementing the second embodiment, in the second method of implementing the second embodiment, the formation by the VNFM of the second comprehensive failure information in accordance with the second failure information comprises the steps of: determining that the failure information transmitted by the VNF device correlated with the first VNF device, is correlated failure information of the second failure information; and generating second comprehensive failure information containing second failure information and correlated failure information.

With reference to the second embodiment and the above-described methods for implementing the second embodiment, in the third embodiment of the second embodiment, the execution by VNFM of the elimination of failures or the reporting of a process in accordance with the second comprehensive information about the failures comprises the steps of: determining according to the type of failure in the second failure information in the second comprehensive failure information or the type of failure in the correlated failure information in the second comprehensive failure information, does the VNFM contain a policy troubleshooting that corresponds to the type of failure in the second failure information or the type of failure in the correlated failure information, in accordance with the troubleshooting policy, eliminate the failure of the first VNF device and / or the failure of the VNF device correlated with the first NFVI device; or transmit second comprehensive failure information to the orchestrator when the VNFM does not contain a failure elimination policy in the second failure information or the type of failure in the correlated failure information.

With reference to the second embodiment and the above-described methods for implementing the second embodiment, in the fourth method for implementing the second embodiment, after resolving the failure of the first VNF device and / or the failure of the VNF device correlated with the first VNF device, in accordance with the failure elimination policy, the method further comprises the step of on which: when the failure elimination was successful, a message indicating success is transmitted to the orchestrator, or when the failure elimination is unsuccessful, the second comprehensive information about failures.

With reference to the second option and the methods described above for implementing the second option, in the fifth method for implementing the second option, before transmitting the second comprehensive failure information to the orchestrator, the method further comprises the steps of: requesting information from the VIM administrator of the virtualized infrastructure about the failures of the NFVI device correlated with the first VNF device, where the NFVI device is any hardware HW, the host Host OS, the administrator of the virtual machine, or the device tual machine VM in NFVI; and add fault information of the NFVI device correlated with the first VNF device to the second comprehensive fault information.

With reference to the second embodiment and the above-described methods for implementing the second embodiment, in the sixth method for implementing the second embodiment, the method further comprises the steps of: receiving the first comprehensive failure information transmitted by VIM, where the first comprehensive failure information contains the first failure information and correlated failure information of the first failure information and the first failure information is used to indicate that a failure has occurred in the first NFVI device; determining whether the VNFM contains a failure elimination policy corresponding to the type of failure in the first failure information in the first comprehensive failure information or the type of failure in the correlated failure information in the first comprehensive failure information; and when the VNFM contains a failover policy corresponding to the type of failure in the first failure information or the type of failure in the correlated failure information, report in accordance with the failover policy of the failures of the first NFVI device and / or the failures of the NFVI device correlated with the first device NFVI; or, when the VNFM does not contain a failover policy corresponding to the type of failure in the first failure information or the type of failure in the correlated failure information, transmit the first comprehensive failure information to the orchestrator or transmit an indication message used to indicate to VIM that the VNFM is unable to process the first comprehensive failure information, so that VIM transmits the first comprehensive failure information to the orchestra.

With reference to the second embodiment and the above-described methods for implementing the second embodiment, in the seventh method for implementing the second embodiment, after receiving the first comprehensive failure information transmitted by VIM, the method further comprises the steps of: determining, according to the first comprehensive failure information, information about failures of the first VNF device correlated with the first NFVI device and / or correlated with the NFVI device correlated with the first NFVI device; and add fault information of the first VNF device to the first comprehensive fault information so that the VNFM performs a fault resolution or reporting process for the first comprehensive fault information.

With reference to the second embodiment and the above-described methods for implementing the second embodiment, in the eighth method for implementing the second embodiment, after performing fault elimination or process reporting by the VNFM according to the second comprehensive failure information, the method further comprises the steps of: detecting in accordance with the second comprehensive failure information, does the VNFM contain comprehensive failure information that is the same as the first comprehensive failure information; and when the VNFM contains comprehensive failure information, which is the same as the second comprehensive failure information, the second comprehensive failure information is deleted.

With reference to the second embodiment and the above-described methods for implementing the second embodiment, in the ninth embodiment of the second embodiment, the method further comprises receiving: the request information transmitted by VIM, where the request information is used to request information from the VNFM on the failure of the VNF correlated with a faulty NFVI device; and transmit to VIM the failure information of the VNF device correlated with the failed NFVI device.

With reference to the second embodiment and the above-described methods for implementing the second embodiment, in the tenth method for implementing the second embodiment, the second failure information is further reported to the OSS / BSS support system so that the OSS / BSS monitors and presents the second information about failures.

With reference to the second embodiment and the methods of the second embodiment described above, in the eleventh embodiment of the second embodiment, the second failure information further comprises at least an operational state or a failure time; and the second comprehensive information about the failures additionally contains information about the state of the failure and the state of the failure contains at least one state such as: not yet processed, being processed, the failure has been eliminated or the failure has not yet been eliminated.

In accordance with a third embodiment, a failure management method is provided, comprising the steps of: receiving through an orchestrator the first comprehensive failure information transmitted by the administrator of the virtualized VIM infrastructure, where the first comprehensive failure information contains the first failure information, the first failure information contains the identifier of the failed device and the type of failure and the first information about the failures is used to indicate that the failure occurred in the first device in Virtualization infrastructure of NFVI network functions with a failed device identifier and perform, through the orchestrator, the elimination of failures or the reporting of the process according to the first comprehensive information about the failures.

With reference to the third embodiment, in the first embodiment of the third embodiment, the first comprehensive failure information further comprises: failure information of the NFVI device correlated with the first NFVI device and / or information of the virtualized network function device VNF correlated with the first NFVI device.

With reference to the third embodiment and the above-described methods for implementing the third embodiment, in the second embodiment of the third embodiment, the implementation by the orchestrator of the elimination of failures or reporting the process according to the first comprehensive information about the failures, comprises the steps in which: they are determined according to the type of failure in the first comprehensive failure information, does the orchestrator contain a failure-removal policy appropriate to the type of failure; and when the orchestrator contains a failure-correcting policy appropriate to the type of failure, eliminate the failure in accordance with the failure-correcting policy for the first NFVI device and / or the failure of the NFVI device correlated with the first NFVI device; or, when the orchestrator does not contain a failover policy appropriate to the type of failure, transmit the first comprehensive failure information to the OSS / BSS operations and business support system.

With reference to the third embodiment and the above-described methods for implementing the third embodiment, in the third embodiment of the third embodiment, the execution by the orchestrator of the elimination of failures or the reporting of the process according to the first comprehensive information about the failures comprises the steps in which: they are determined according to the type of failure in the first comprehensive failure information, does the orchestrator contain a failure-removal policy appropriate to the type of failure; and when the orchestrator contains a failure-correcting policy corresponding to the type of failure, the failure is eliminated in accordance with the failure-correcting policy for the failure of the first NFVI device, the failure of the NFVI device correlated with the first NFVI device, and the failure of the VNF device correlated with the first NFVI device; or when the orchestrator does not contain a failover policy appropriate to the type of failure, transmit the first comprehensive failure information to the OSS / BSS system.

With reference to the third embodiment and the above-described methods for implementing the third embodiment, in the fourth embodiment of the third embodiment, before performing the fault elimination or the process message according to the first comprehensive failure information by the orchestrator, the method further comprises the steps of: detecting in accordance with the first comprehensive failure information, whether the orchestrator contains comprehensive failure information that is the same as the first comprehensive failure information; and when the orchestrator contains comprehensive failure information, which is the same as the first comprehensive failure information, the first comprehensive failure information is deleted.

With reference to the third embodiment and the methods of the third embodiment described above, in the fifth embodiment of the third embodiment, the first failure information comprises at least an operational state or a failure time; and the first comprehensive failure information additionally contains information about the failure state, and the failure state contains at least one state from such states as: not yet processed, being processed, the failure has been eliminated, or the failure has not yet been eliminated.

According to a fourth embodiment, a failure management method is provided, comprising the steps of: receiving, via an orchestrator, the second comprehensive failure information transmitted by the administrator of the virtualized network functions of VNFM, where the second comprehensive failure information contains the second failure information, the second failure information contains the identifier of the failed device and the type of failure and the second failure information is used to indicate that a failure has occurred in the first device infrastructure virtualized network functions VNF, having failed device identifier; and perform, through the orchestrator, the elimination of failures or the reporting of the process according to the second comprehensive failure information.

With reference to the fourth embodiment, in the first embodiment of the fourth embodiment, the second comprehensive failure information further comprises: failure information of the VNF device correlated with the first VNF device and / or failure information of the NFVI virtualized infrastructure manager device correlated with the first VNF device.

With reference to the fourth embodiment and the above-described method of implementing the fourth embodiment, in the second method of implementing the fourth embodiment, the execution by the orchestrator of the failure elimination or the process message according to the second comprehensive information about the failures, comprises the steps of: determining according to the type of failure in the second comprehensive failure information, does the orchestrator contain a failure-removal policy appropriate to the type of failure; and when the orchestrator contains a failure-correcting policy corresponding to the type of failure, the failure is eliminated in accordance with the failure-correcting policy for the first VNF device and / or the failure of the VNF device correlated with the first VNF device; or, when the orchestrator does not contain a failure-correcting policy appropriate to the type of failure, transmit second comprehensive failure information to the OSS / BSS operations and business support system.

With reference to the fourth embodiment and the above-described methods for implementing the fourth embodiment, in the third method for implementing the fourth embodiment, performing, by the orchestrator, the elimination of failures or reporting the process according to the second comprehensive failure information, comprises the steps of: determining according to the type of failure in the second comprehensive failure information, does the orchestrator contain a failure-removal policy appropriate to the type of failure; and when the orchestrator contains a failure-correcting policy appropriate to the type of failure, the failure is eliminated in accordance with the failure-correcting policy for the failure of the first VNF device, the failure of the VNF device correlated with the first VNF device, and the failure of the NFVI device correlated with the first VNF device; or, when the orchestrator does not contain a failover policy appropriate to the type of failure, transmit second comprehensive failure information to the OSS / BSS system.

With reference to the fourth embodiment and the above-described methods for implementing the fourth embodiment, in the fourth method for implementing the fourth embodiment, before performing the fault elimination or the process message according to the second comprehensive failure information by the orchestrator, the method further comprises the steps of: detecting in accordance with the second comprehensive failure information, whether the orchestrator contains comprehensive failure information, which is the same as the second comprehensive failure information Kazakh; and when the orchestrator contains comprehensive failure information, which is the same as the second comprehensive failure information, the second comprehensive failure information is deleted.

With reference to the fourth embodiment and the methods of the fourth embodiment described above, in the fifth embodiment of the fourth embodiment, the second failure information further comprises at least an operational state or a failure time; and the second comprehensive information about the failures additionally contains information about the state of the failure and the state of the failure contains at least one state such as: not yet processed, being processed, the failure has been eliminated or the failure has not yet been eliminated.

According to a fifth embodiment, a virtualized infrastructure manager is provided, comprising: a receiving unit configured to receive first failure information containing a failed device identifier and a failure type for a network function virtualization infrastructure (NFVI) device, where the first failure information is used to indicate that a failure has occurred in the first NFVI device having a failure device identifier; a generating unit configured to generate first comprehensive failure information corresponding to the first failure information, where the first comprehensive failure information contains first failure information and correlated failure information of the first failure information; and a processing unit configured to perform, via VIM, the elimination of failures or process messages according to the first comprehensive failure information.

With reference to the fifth embodiment, in the first embodiment of the fifth embodiment, the administrator further comprises a determination unit and a receiving unit, and the data receiving unit is specifically configured to receive, using the receiving unit, the first failure information transmitted by the first NFVI device; or determining, using the determining unit, that a failure has occurred in the first NFVI device, and generating the first failure information in accordance with the failure of the first NFVI device.

With reference to the fifth embodiment and the above described embodiment of the fifth embodiment, in the second embodiment of the fifth embodiment, the first NFVI device is any hardware HW, host operating system (Host OS), virtual machine administrator or virtual machine device (VM) in the NFVI device and the unit the formation is specifically configured to determine, using the determination unit, the failure information transmitted by the NFVI device correlated with the first NFVI device, which is the correlated information to her about failures of the first information about failures; and generating first comprehensive failure information containing first failure information and correlated failure information.

With reference to the fifth embodiment and the above-described methods for implementing the fifth embodiment, in the third embodiment of the fifth embodiment, the processing unit comprises a transmitting unit and the processing unit is specifically configured to determine using the determination unit and in accordance with the type of failure in the first failure information in the first comprehensive failure information or the type of failure in the correlated failure information in the first comprehensive failure information, does VIM contain a failure management policy that matches the type of refusal in the first information about the refusals or the type of refusal in the correlated information about the refusals; and when the VIM contains a failover policy corresponding to the type of failure in the first failure information or the type of failure in the correlated failure information, in accordance with the failover policy, eliminate the failure in the first NFVI device and / or the failure in the NFVI device correlated with the first device NFVI; or, when VIM does not contain a failover policy that matches the type of failure in the first failure information or the type of failure in the correlated failure information, transmit the first comprehensive failure information to the VNFM or transmit the first comprehensive failure information to the orchestra.

With reference to the fifth embodiment and the above-described methods for implementing the fifth embodiment, in the fourth embodiment of the fifth embodiment, the processing unit is specifically configured to determine, using the determination unit, an NFVI device having the highest priority among the first NFVI device and the NFVI device correlated with the first device NFVI, where HW priority is higher than Host OS priority, Host OS priority is higher than virtual machine administrator priority and virtual machine administrator priority is higher than VM priority; determining, using the determination unit and in accordance with the type of failure of the NFVI device having the highest priority, whether the VIM contains an appropriate failover policy; and when the VIM contains a failover policy corresponding to the failure type of the NFVI device having the highest priority, in accordance with the failover policy, the failure of the NFVI device having the highest priority is eliminated.

With reference to the fifth embodiment and the above-described methods for implementing the fifth embodiment, in the fifth embodiment of the fifth embodiment, the transmitting unit is specifically configured to transmit to the orchestrator, when the failure was successful, messages indicating success, or when the failure was unsuccessful, transmission to VNFM the first comprehensive information about failures or the transfer to the orchestrator of the first comprehensive information about failures.

With reference to the fifth embodiment and the above-described methods for implementing the fifth embodiment, in the sixth embodiment of the fifth embodiment, the receiving unit is further configured to receive an indication message that is transmitted by the VNFM and used to indicate that the VNFM is unable to process the first comprehensive failure information; and the transmitting unit is further configured to transmit to the orchestra the first comprehensive information about the failures.

With reference to the fifth embodiment and the above-described methods for implementing the fifth embodiment, in the seventh embodiment of the fifth embodiment, the processing unit is further configured to query the VNFM for fault information of the VNF device correlated with the first NFVI device, and add fault information of the VNF correlated to NFVI's first device, the first comprehensive failure information.

With reference to the fifth embodiment and the above-described methods for implementing the fifth embodiment, in the eighth embodiment of the fifth embodiment, the receiving unit is further adapted to receive request information transmitted by VNFM, where the request information is used to request information from the VIM about the failure of the NFVI device correlated with the failed VNF device and the transmitting unit is further configured to transmit failure information of the NFVI device correlated with the failed VNF device.

With reference to the fifth embodiment and the above-described methods for implementing the fifth embodiment, in the ninth embodiment of the fifth embodiment, the administrator further comprises a detection unit and a deletion unit, where the detection unit is specifically configured to detect, according to the first failure information, whether the VIM contains comprehensive information about failures, which is the same as the first comprehensive failure information; and the deletion unit is specifically configured to delete the first comprehensive failure information when the VIM contains comprehensive failure information, which is the same as the first comprehensive failure information.

According to a sixth embodiment, a virtualized network functions manager is provided, comprising: a receiving unit configured to receive second failure information containing a failed device identifier and a failure type for the virtualized network function device VNF, where the second failure information is used to indicate that the failure occurred in the first VNF device having the identifier of the failed device; a generating unit configured to generate second comprehensive failure information corresponding to the second failure information; and a processing unit configured to eliminate the failures or process messages according to the second comprehensive failure information.

With reference to the sixth embodiment, in the first embodiment of the sixth embodiment, the administrator further comprises a determination unit and a receiving unit, and the receiving unit is specifically configured to receive, using the receiving unit, second fault information transmitted by the first VNF; or determining, using the determining unit, that a failure has occurred in the first VNF device, and generating, using the generating unit, the second failure information in accordance with the failure of the first VNF device.

With reference to the sixth embodiment and the above-described method for implementing the sixth embodiment, in the second embodiment of the sixth embodiment, the generating unit is specifically configured to determine, using the determining unit, that the failure information transmitted by the VNF correlated with the first VNF is correlated failures of the second failure information; and generating second comprehensive failure information containing second failure information and correlated failure information.

With reference to the sixth embodiment and the above-described methods for implementing the sixth embodiment, in the third embodiment of the sixth embodiment, the processing unit comprises a transmitting unit and the processing unit is specifically adapted to be detected using the determination unit and in accordance with the type of failure in the second failure information in the second comprehensive failure information or the type of failure in the correlated failure information in the second comprehensive failure information, does the VNFM contain a failure management policy that complies with it is the type of refusal in the second information about the refusals or the type of refusal in the correlated information about the refusals; and when the VNFM contains a failover policy corresponding to the type of failure in the second failure information or the type of failure in the correlated failure information, in accordance with the failover policy, the failure of the first VNF device and / or the failure of the VNF device correlated with the first VNF device is eliminated; or, when the VNFM does not contain a failure elimination policy corresponding to the type of failure in the second failure information or the type of failure in the correlated failure information, the second comprehensive failure information is transmitted to the orchestrator using the transmitting unit.

With reference to the sixth embodiment and the above-described methods for implementing the sixth embodiment, in the fourth embodiment of the sixth embodiment, the transmitting unit is specifically configured to transmit to the orchestrator a message indicating success when the failure was successful, or when the failure was unsuccessful, to transfer the second comprehensive failure information.

With reference to the sixth embodiment and the above-described methods for implementing the sixth embodiment, in the fifth embodiment of the sixth embodiment, the processing unit is further configured to request the administrator of the virtualized VIM infrastructure information about the failures of the NFVI device correlated with the first VNF device, where the NFVI device is any hardware HW , Host Host OS, virtual machine administrator, or VM virtual machine device in NFVI; and adding fault information of the NFVI device correlated with the first VNF device to the second comprehensive fault information.

With reference to the sixth embodiment and the above-described methods for implementing the sixth embodiment, in the sixth embodiment of the sixth embodiment, the processing unit is specially adapted to receive first comprehensive failure information transmitted by VIM, where the first comprehensive failure information contains first failure information and correlated information about failures of the first failure information and the first failure information is used to indicate that a failure has occurred in the first NFVI device; determining whether the VNFM has a failure management policy appropriate for the type of failure in the first failure information in the first comprehensive failure information or the type of failure in the correlated failure information in the first comprehensive failure information; and when the VNFM contains a failover policy corresponding to the type of failure in the first failure information or the type of failure in the correlated failure information, the failure of the first NFVI device and / or the failure of the NFVI device correlated with the first NFVI device is eliminated in accordance with the failure management policy; or, when the VNFM does not contain a failover policy corresponding to the type of failure in the first failure information or the type of failure in the correlated failure information, transmit the first comprehensive failure information to the orchestrator or transmit the VIM indication message used to indicate that the VNFM is unable to process the first comprehensive failure information, so that VIM transmits the first comprehensive failure information to the orchestra.

With reference to the sixth embodiment and the above-described methods for implementing the sixth embodiment, in the seventh embodiment of the sixth embodiment, the processing unit is specifically configured to determine, according to the first comprehensive failure information, the failure information of the first VNF device correlated with the first NFVI device and / or correlated with an NFVI device correlated with the first NFVI device; and adding the fault information of the first VNF device to the first comprehensive fault information so that the VNFM performs a fault resolution or reporting process for the first comprehensive fault information.

With reference to the sixth embodiment and the above-described methods for implementing the sixth embodiment, in the eighth embodiment of the sixth embodiment, the administrator further comprises a detection unit and a deletion unit, where the detection unit is specifically configured to detect, according to the second comprehensive information, whether the VNFM contains comprehensive failure information , which is the same as the second comprehensive failure information; and the deletion unit is specifically configured to delete second comprehensive failure information when the VNFM contains comprehensive failure information, which is the same as the second comprehensive failure information.

With reference to the sixth embodiment and the above-described methods for implementing the sixth embodiment, in the ninth embodiment of the sixth embodiment, the receiving unit is further configured to receive request information transmitted by VIM, where the request information is used to request from the VNFM fault information of the VNF correlated with the faulty NFVI device and the transmitting unit is further configured to transmit VIM information about the failures of the VNF device correlated with the faulty NFVI device.

In accordance with a seventh embodiment, an orchestrator is provided comprising: a receiving unit configured to receive first comprehensive failure information transmitted by a VIM administrator of a virtualized infrastructure, where the first comprehensive failure information contains first failure information, the first failure information contains the identifier of the failed device and the type of failure and the first failure information is used to indicate that a failure has occurred in the first virtualization infrastructure NFVI device network function having the identifier of the failed device; and a processing unit configured to troubleshoot faults or process messages according to the first comprehensive fault information.

With reference to the seventh embodiment, in the first embodiment of the seventh embodiment, the first comprehensive failure information further comprises: failure information of the NFVI device correlated with the first NFVI device and / or information of the virtualized VNF network function device correlated with the first NFVI device.

With reference to the seventh embodiment and the method of implementing the seventh embodiment described above, in the second method of implementing the seventh embodiment, the processing unit is specifically configured to determine, according to the type of failure, in the first comprehensive failure information, whether the orchestrator contains a failure elimination policy corresponding to the type of failure; and when the orchestrator contains a failure-correcting policy appropriate to the type of failure, the failure of the first NFVI device is resolved in accordance with the failure-correcting policy and / or failure of the NFVI device correlated with the first NFVI device; or, when the orchestrator does not contain a failover policy appropriate to the type of failure, transmit the first comprehensive failure information to the OSS / BSS operations and business support system.

With reference to the seventh embodiment and the above-described methods for implementing the seventh embodiment, in the third method for implementing the seventh embodiment, the processing unit is specifically configured to determine, according to the type of failure, in the first comprehensive failure information, whether the orchestrator contains a failure elimination policy corresponding to the type of failure; and when the orchestrator contains a failure-correcting policy appropriate to the type of failure, in accordance with the failure-correcting policy, the failure of the first NFVI device, the failure of the NFVI device correlated with the first NFVI device, and the failure of the VNF device correlated with the first NFVI device are eliminated; or when the orchestrator does not contain a failover policy appropriate to the type of failure, transmit the first comprehensive failure information to the OSS / BSS system.

With reference to the seventh embodiment and the above-described methods for implementing the seventh embodiment, in the fourth embodiment of the seventh embodiment, the administrator further comprises a detection unit and a deletion unit, where the detection unit is specifically configured to detect, according to the first failure information, whether the orchestrator contains comprehensive information about failures, which is the same as the first comprehensive failure information; and the deletion unit is specifically configured to delete the first comprehensive failure information when the orchestrator contains comprehensive failure information, which is the same as the first comprehensive failure information.

According to the eighth embodiment, an orchestrator is provided, comprising: a receiving unit configured to receive second comprehensive failure information transmitted by the administrator of the virtualized network functions of VNFM, where the second comprehensive failure information contains second failure information, the second failure information contains the identifier of the failed devices and the type of failure and the second failure information is used to indicate that a failure has occurred in the first device of the virtualized network fu ktsy VNF, having failed device identifier; and a processing unit configured to eliminate the failures or process messages according to the second comprehensive failure information.

With reference to the eighth embodiment, in the first embodiment of the eighth embodiment, the second comprehensive failure information further comprises: failure information of the VNF device correlated with the first VNF device and / or failure information of the virtualized NFVI infrastructure manager device correlated with the first VNF device.

With reference to the eighth embodiment and the above-described method for implementing the eighth embodiment, in the second method for implementing the eighth embodiment, the processing unit is specifically configured to determine, according to the type of failure, in the second comprehensive failure information, whether the orchestrator contains a failure elimination policy corresponding to the type of failure; and when the orchestrator contains a failover policy appropriate to the type of failure, in accordance with the failover policy, eliminate the failure of the first VNF device and / or the failure of the VNF device correlated with the first VNF device; or, when the orchestrator does not contain a failure-correcting policy appropriate to the type of failure, transmit second comprehensive failure information to the OSS / BSS operations and business support system.

With reference to the eighth embodiment and the above-described methods for implementing the eighth embodiment, in the third method for implementing the eighth embodiment, the processing unit is specifically configured to determine, according to the type of failure, in the second comprehensive failure information, whether the orchestrator contains a failure elimination policy corresponding to the type of failure; and when the orchestrator contains a failure-correcting policy appropriate to the type of failure, the failure is eliminated in accordance with the failure-correcting policy for the failure of the first VNF device, the failure of the VNF device correlated with the first VNF device, and the failure of the NFVI device correlated with the first VNF device; or, when the orchestrator does not contain a failover policy appropriate to the type of failure, transmit second comprehensive failure information to the OSS / BSS system.

With reference to the eighth embodiment and the above-described methods for implementing the eighth embodiment, in the fourth embodiment of the eighth embodiment, the orchestrator further comprises a detection unit and a deletion unit, where the detection unit is configured to detect, in accordance with the second comprehensive failure information, whether the orchestrator contains comprehensive information about failures, which is the same as the second comprehensive failure information; and the deletion unit is specifically configured to delete second comprehensive failure information when the orchestrator contains comprehensive failure information, which is the same as the second comprehensive failure information.

In accordance with the failure processing control method provided in the embodiments of the present invention, VIM and VNFM obtain hardware and / or software failure information to comprehensively process correlated pieces of failure information that can implement the failure message and processing in the medium NFV.

BRIEF DESCRIPTION OF THE DRAWINGS

To more clearly describe the technical solutions in the embodiments of the present invention, the accompanying drawings required to describe the embodiments of the present invention are briefly presented below. Obviously, the accompanying drawings in the following description merely show some embodiments of the present invention, and those of ordinary skill in the art, without creative efforts, may additionally create other drawings from these accompanying drawings.

FIG. 1 is a schematic diagram of a system architecture for NFV network function virtualization according to an embodiment of the present invention;

FIG. 2 is a flowchart of a method for controlling a failure processing in accordance with an embodiment of the present invention;

FIG. 3 is a flowchart of a failure control method in accordance with an embodiment of the present invention;

FIG. 4 is a flowchart of a failure control method in accordance with an embodiment of the present invention;

FIG. 5 is a flowchart of a method for controlling a failure processing in accordance with an embodiment of the present invention;

FIG. 6a is an interaction diagram of a failure processing control method in accordance with an embodiment of the present invention;

FIG. 6b is a schematic diagram of the correlation between devices in accordance with an embodiment of the present invention;

FIG. 7 is an interaction diagram of a failure management method in accordance with an embodiment of the present invention;

FIG. 8 is an interaction diagram of a failure processing control method in accordance with an embodiment of the present invention;

FIG. 9 is an interaction diagram of a failure management method in accordance with an embodiment of the present invention;

FIG. 10 is an interaction diagram of a failure processing control method in accordance with an embodiment of the present invention;

FIG. 11 is a block diagram of a VIM virtualized infrastructure administrator device in accordance with an embodiment of the present invention;

FIG. 12 is a block diagram of a VNFM virtualized network functions manager device in accordance with an embodiment of the present invention;

FIG. 13 is a block diagram of an orchestrator device according to an embodiment of the present invention;

FIG. 14 is a block diagram of a VIM device according to another embodiment of the present invention;

FIG. 15 is a block diagram of a VNFM device according to another embodiment of the present invention; and

FIG. 16 is a block diagram of an orchestrator device according to another embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

The technical solutions in the embodiments of the present invention are clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are some, but not all, embodiments of the present invention. All other embodiments obtained by those skilled in the art, based on the embodiments of the present invention without creative efforts, will fall within the protection scope of the present invention.

In FIG. 1 is a schematic diagram of a system architecture for NFV network function virtualization according to an embodiment of the present invention.

In the End to End (E2E) Network Function Virtualization (NFV) architecture, the Network Function Virtualization Infrastructure (NFVI) contains a low-level hardware resource (Hardware, HW) that can be specifically classified as computer hardware, data storage hardware, network hardware, etc. The virtualization level is at the hardware level and contains the host operating system (Host Operating System, Host OS) and programs superupravleniya / virtual machine manager (hypervisor, Hypervisor) and multiple virtual machines (Virtual Machine, VM), running on the virtualization layer. HW and Hypervisor connect to the Operation and Business Support System (OSS / BSS) using the Element Management System (EMS). Numerous individual virtual network functions (VNFs) on the NFVI are connected to the OSS / BSS system using vEMS.

NFVI connects to the Virtualization Infrastructure Manager (VIM) administrator using the Nf-Vi interface, VNF connects to the VNF administrator (VNFM) using the Ve-Vnfm interface, and VIM connects to VNFM using the Vi-Vnfm interface. NFVI connects to the orchestra using Or-Vi, VNFM connects to the orchestra using Or-Vnfm and the orchestra connects to OSS / BSS using the Os-Ma interface.

The OSS / BSS system is configured to initiate a service request submitted to the orchestrator, the orchestrator is responsible for the resources of the orchestration and management in accordance with the OSS / BSS service request, the implementation of the NFV service and the discovery of real-time information about the resources and operational status of the VNF and NFVI. VNFM is responsible for managing a VNF life cycle, such as startup, lifetime, detection and collection of VNF operational status information. VIM is responsible for managing and distributing NFVI resources and for discovering and collecting NFVI operational status information.

In FIG. 2 is a flowchart of a failure control method in accordance with an embodiment of the present invention. The method shown in FIG. 2 is performed by VIM.

201: The VIM virtualized infrastructure administrator receives the first failure information containing the identifier of the failed device and the type of failure, the NFVI Network Function Virtualization Infrastructure device, where the first failure information is used to indicate that the failure occurred in the first NFVI device with the failed device identifier.

202: VIM generates the first comprehensive failure information in accordance with the first failure information, where the first comprehensive failure information contains the first failure information and correlated failure information of the first failure information.

203: VIM troubleshoots or reports the process in accordance with the first comprehensive fault information.

In accordance with the fault handling management method provided in this embodiment of the present invention, VIM obtains fault information of the hardware device and / or software to comprehensively process the correlated pieces of fault information, which can implement fault reporting and processing in the medium NFV.

Alternatively, in an embodiment, step 201 comprises actions in which: they receive the first failure information transmitted by the first NFVI device, or determine that a failure has occurred in the first NFVI device, and generate the first failure information in accordance with the failure of the first NFVI device. That is, VIM can passively receive information about failures of a failed device, or after detecting a failure, it can actively generate information about failures.

Alternatively, in an embodiment, the first NFVI device is any hardware HW device, host Host OS, virtual machine administrator, VM virtual machine in the NFVI device, and step 202 comprises actions in which: it is determined that the failure information transmitted by the device NFVI correlated with the first NFVI device is correlated failure information of the first failure information; and form the first comprehensive failure information containing the first failure information and correlated failure information. Since there is a correlation between some HW, Host OS, Hypervisor, and VM devices when a failure occurs in the first NFVI device, a failure may occur in another NFVI device correlated with the first NFVI device. VIM can collect all related failure information so that it can perform uniform and comprehensive processing.

Alternatively, in an embodiment, step 203 comprises actions in which: according to the type of failure in the first failure information in the first comprehensive failure information, or the type of failure in the correlated failure information in the first comprehensive failure information, determine whether the VIM policy elimination of failures, which corresponds to the type of failure in the first information about the failures or the type of failure in the correlated information about the failures; and when the VIM contains a failover policy corresponding to the type of failure in the first failure information or the type of failure in the correlated failure information, in accordance with the failover policy, eliminate the failure of the first NFVI device and / or the failure of the NFVI device correlated with the first NFVI device ; or, when VIM does not contain a failover policy that matches the type of failure in the first failure information or the type of failure in the correlated failure information, transmit the first comprehensive failure information to the VNFM or transmit the first comprehensive failure information to the orchestra.

Specifically, after generating comprehensive failure information, VIM first needs to determine if VIM is capable of processing locally comprehensive failure information; and if VIM is capable of handling comprehensive failure information, then VIM eliminates the failure of one NFVI device contained in the comprehensive failure information; or if VIM is unable to process comprehensive fault information, or if the troubleshooting fails, VIM runs a process message.

Alternatively, in the first embodiment, determining according to the type of failure in the first failure information in the first comprehensive failure information or the type of failure in the correlated failure information in the first comprehensive failure information, does VIM contain a failure management policy that matches the type of failure in the first failure information or type of failure in the correlated failure information, it comprises the steps of: determining the NFVI device having the highest priority from among the first device N FVI and NFVI devices correlated with the first NFVI device, where HW priority is higher than Host OS priority, Host OS priority is higher than virtual machine administrator priority and virtual machine administrator priority is higher than VM priority; determining, according to the failure type of the NFVI device having the highest priority, whether the VIM contains an appropriate failover policy; and when the VIM contains a failover policy corresponding to the failure type of the NFVI device having the highest priority, according to the failover policy, the failure of the NFVI device having the highest priority is eliminated.

Alternatively, in the embodiment, in accordance with the failure-correcting policy after resolving the failure of the first NFVI device and / or the failure of the NFVI device correlated with the first NFVI device, the method may further comprise the steps of: when the failure is successful, send a message to the orchestrator indication of success; or, when the failure repair failed, transmit the first comprehensive failure information to the VNFM or transmit the first comprehensive failure information to the orchestrator, where the success message may be failure information in which the operating state is set to “Normal”, or may be a message in another form and used to indicate that the failure has been successfully resolved, which is not limited in the present invention.

Alternatively, in an embodiment, after transmitting the first comprehensive fault information to the VNFM, the method further comprises the step of: receiving an indication message transmitted by the VNFM and using it to indicate that the VNFM is unable to process the first comprehensive fault information and transmitting the first comprehensive information about failures to the orchestra. In the event that VIM is unable to process the first comprehensive failure information and report the first comprehensive failure information to the VNFM, if VNFM is also unable to process the first comprehensive failure information, VNFM additionally reports the first comprehensive information to the orchestrator.

Alternatively, in the embodiment, before transmitting the first comprehensive failure information to the orchestrator, the method further comprises the steps of: requesting information from the VNFM about the failures of the VNF device correlated with the first NFVI device; and add fault information of the VNF device correlated with the first NFVI device to the first comprehensive fault information. When VIM is unable to process the first comprehensive fault information, or the failure repair failed, VIM can initiate a request to the VNFM, receive fault information of the VNF device correlated with the failed NFVI device, and run a comprehensive report so that the higher-level control device can perform comprehensive processing.

Alternatively, in an embodiment, the method further comprises the steps of: receiving the request information transmitted by the VNFM, where the request information is used to request from the VIM the failure information of the NFVI device correlated with the faulty VNF device; and transmit the failure information of the NFVI device correlated with the faulty VNF device to the VNFM. Specifically, when the VNFM is unable to process comprehensive fault information of the VNF device, the VNFM may also request the VIM information about the faults of the corresponding NFVI and perform a comprehensive report so that the higher-level control device can perform comprehensive processing.

Alternatively, in the embodiment, after generating the VIM first comprehensive failure information in accordance with the first failure information, the method further comprises the steps of: detecting, in accordance with the first comprehensive failure information, whether the VIM contains comprehensive failure information, which is same as the first comprehensive failure information; and when the VIM contains comprehensive failure information, which is the same as the first comprehensive failure information, the first comprehensive failure information is deleted.

Specifically, since correlated faults occur in multiple correlated NFVI devices, VIM can receive multiple pieces of the same comprehensive fault information, where the same comprehensive fault information is referred to here with the content of the fault information in the comprehensive fault information failures is the same. In this case, VIM may perform detection of a repeating alarm. VIM continues to process that comprehensive fault information that is being processed and deletes the same comprehensive fault information that has not yet been processed.

Alternatively, in an embodiment, the first failure information is further communicated to the operations and business support system (OSS / BSS) so that the OSS / BSS system monitors and presents the first failure information.

Alternatively, in an embodiment, the first failure information further comprises at least an operational state or time of failure, the first comprehensive failure information further comprises information about the failure state, and the failure state contains at least one of the following: not yet processed, being processed, the failure has been resolved or the failure has not yet been resolved.

In accordance with the fault handling management method provided in this embodiment of the present invention, VIM obtains fault information of the hardware device and / or software to comprehensively process the correlated pieces of fault information, which can implement fault reporting and processing in the medium NFV. In addition, since comprehensive processing is performed on correlated pieces of fault information and the same comprehensive fault information is deleted by detecting a repeating alarm, the efficiency and accuracy of the fault processing are improved.

In FIG. 3 is a flowchart of a failure control method in accordance with an embodiment of the present invention. The method shown in FIG. 3 is performed by VNFM.

301: The VNFM virtualized network functions administrator receives the second fault information containing the identifier of the failed device and the type of fault, the VNF virtualized network functions device, where the second fault information is used to indicate that a failure has occurred in the first VNF NFVI device having the identifier of the failed device.

302: VNFM generates second comprehensive failure information in accordance with the second failure information.

303: The VNFM performs a fault recovery or reports a process in accordance with the first comprehensive fault information.

In accordance with the fault handling management method provided in this embodiment of the present invention, the VNFM obtains fault information of the hardware device and / or software to perform comprehensive processing of the correlated pieces of fault information, which can implement fault reporting and processing in the medium NFV.

Alternatively, in an embodiment, step 301 comprises actions in which: receive the second fault information transmitted by the first VNF; or determining that a failure has occurred in the first VNF device and generating second failure information in accordance with the failure of the first VNF device. That is, VNFM can passively receive information about failures of a failed device or, after detecting a failure, can actively generate information about failures.

Alternatively, in an embodiment, step 302 comprises actions in which: it is determined that the failure information transmitted by the VNF device correlated with the first VNF device is correlated failure information of the second failure information; and generating second comprehensive failure information containing second failure information and correlated failure information. Since there is a correlation between VNF HW devices, when a failure occurs in the first VNF device, a failure can also occur in another VNF device correlated with the first VNF device. VNFM can collect all related failure information so that it can perform uniform and comprehensive processing.

Alternatively, in an embodiment, step 303 comprises actions in which: according to the type of failure in the second failure information in the second comprehensive failure information, or the type of failure in the correlated failure information in the second comprehensive failure information, determine whether the VNFM contains a policy elimination of failures that corresponds to the type of failure in the second failure information or the type of failure in the correlated failure information; and when the VNFM contains a failover policy corresponding to the type of failure in the second failure information or the type of failure in the correlated failure information, the failure of the first VNF device and / or the failure of the VNF device correlated with the first VNF device is eliminated in accordance with the failure policy; or, when the VNFM does not contain a failover policy that matches the type of failure in the second failure information or the type of failure in the correlated failure information, the second comprehensive failure information is transmitted to the orchestra.

Specifically, after generating comprehensive failure information, VNFM first needs to determine if VIM is capable of processing locally comprehensive failure information; and if the VNFM is capable of processing comprehensive failure information, then the VNFM eliminates the failure of one VNF device contained in the comprehensive failure information; or if the VNFM is unable to process comprehensive fault information or if the failover fails, the VNFM executes the process message.

Alternatively, in the embodiment, in accordance with the fault elimination policy after eliminating the fault of the first VNF device and / or the fault of the VNF device correlated with the first VNF device, the method further comprises the steps of: when the fault elimination is successful, a message indicating success; or, when the failure repair failed, transmit the first comprehensive failure information to the VNFM or transmit the second comprehensive failure information to the orchestrator, where the success message may be failure information in which the operating state is set to “Normal”, or may be a message in another form and used to indicate that the failure has been successfully resolved, which is not limited in the present invention.

Alternatively, in the embodiment, before transmitting the second comprehensive failure information to the orchestrator, the method further comprises the step of: requesting the administrator of the virtualized infrastructure VIM the failure information of the NFVI device correlated with the first VNF device, where the NFVI device is any hardware HW leading Host OS, virtual machine administrator, or VM virtual machine device in NFVI; and add fault information of the NFVI device correlated with the first VNF device to the second comprehensive fault information. When the VNFM is unable to process the second comprehensive fault information, or the failure repair failed, the VNFM can initiate a request to the VIM, receive the fault information of the NFVI device correlated with the failed VNF device, and execute a comprehensive report so that the higher-level control device can perform comprehensive processing.

Alternatively, in an embodiment, the method further comprises the steps of: receiving first comprehensive failure information transmitted by VIM, where the first comprehensive failure information contains first failure information and correlated failure information of the first failure information and the first failure information is used to indicate that a failure has occurred in the first NFVI device; determining whether the VNFM contains a failure elimination policy corresponding to the type of failure in the first failure information in the first comprehensive failure information or the type of failure in the correlated failure information in the first comprehensive failure information; and when the VNFM contains a failover policy corresponding to the type of failure in the first failure information or the type of failure in the correlated failure information, in accordance with the failover policy of the first NFVI device and / or the failure of the NFVI device correlated with the first NFVI device; or, when the VNFM does not contain a failover policy corresponding to the type of failure in the first failure information or the type of failure in the correlated failure information, transmit the first comprehensive failure information to the orchestrator or transmit an indication message used to indicate to VIM that the VNFM is unable to process the first comprehensive failure information so that VIM transmits the first comprehensive failure information to the orchestra. When VIM is unable to process the first comprehensive fault information of the NFVI device, or that the failover fails, VIM reports the first comprehensive fault information to VNFM. If the VNFM is also unable to process the first comprehensive failure information, or if the failover fails, VNFM notifies VIM that VIM reports the first comprehensive failure information to the orchestrator.

Alternatively, in the embodiment, after receiving the first comprehensive failure information transmitted by the VIM, the method further comprises the steps of: determining, according to the first comprehensive failure information, the failure information of the first VNF device correlated with the first NFVI device and / or correlated with an NFVI device correlated with the first NFVI device; and add the fault information of the first VNF device to the first comprehensive fault information so that the VNFM performs a fault repair or process message for the first comprehensive fault information.

Alternatively, in the embodiment, after performing fault elimination or process reporting by the VNFM in accordance with the second comprehensive fault information, the method further comprises the steps of: detecting, in accordance with the second comprehensive fault information, whether the VNFM contains comprehensive fault information , which is the same as the first comprehensive failure information; and when the VNFM contains comprehensive failure information, which is the same as the second comprehensive failure information, the second comprehensive failure information is deleted.

Specifically, since when correlated failures occur in multiple correlated VNF devices, VNFM can receive multiple pieces of the same comprehensive failure information, where the same comprehensive failure information is here as a reference to the content of the failure information in a comprehensive failure information is the same. In this case, the VNFM may perform detection of a repeating alarm. VNFM continues to process that comprehensive error information that is being processed and deletes the same comprehensive error information that has not yet been processed.

Alternatively, in an embodiment, the method further comprises the steps of: receiving the request information transmitted by VIM, where the request information is used to request information from the VNFM about the failure of the VNF device correlated with the failed NFVI device; and transmit to VIM the failure information of the VNF device correlated with the failed NFVI device.

Alternatively, in an embodiment, the second failure information is additionally communicated to the operations and business support system (OSS / BSS), so that the OSS / BSS system monitors and presents the second failure information.

Alternatively, in the embodiment, the second failure information further comprises at least an operational state or time of failure, the second comprehensive failure information further comprises information about the failure state, and the failure state contains at least one state such as: not yet processed, handled, failure resolved or failure not yet resolved.

In accordance with the fault handling management method provided in this embodiment of the present invention, the VNFM obtains fault information of the hardware device and / or software to perform comprehensive processing of the correlated pieces of fault information, which can implement fault reporting and processing in the medium NFV. In addition, since comprehensive processing is performed on correlated pieces of fault information and the same comprehensive fault information is deleted by detecting a repeating alarm, the efficiency and accuracy of the fault processing are improved.

In FIG. 4 is a flowchart of a method for controlling a failure processing in accordance with an embodiment of the present invention. The method shown in FIG. 4 is performed by an orchestra.

401: The orchestrator receives the first comprehensive failure information sent by the VIM virtualized infrastructure administrator, where the first comprehensive failure information contains the first failure information, the first failure information contains the identifier of the failed device and the type of failure, and the first failure information is used to indicate that the failure occurred on the first NFVI Network Functions Virtualization Infrastructure Infrastructure device, which has a failed device identifier

402: The orchestra performs troubleshooting or reports the process in accordance with the first comprehensive failure information.

In accordance with the failure handling control method provided in this embodiment of the present invention, the orchestrator obtains information about the failures of the hardware device and / or software in order to comprehensively process the correlated pieces of failure information, which can implement the failure message and the processing in the medium. NFV.

Alternatively, in the embodiment, the first comprehensive fault information further comprises fault information of the NFVI device correlated with the first NFVI device and / or information of the virtualized network function device VNF correlated with the first NFVI device. That is, the comprehensive failure information received by the orchestra from VIM may contain information about the failures of the NFVI device or may contain information about the failures of the NFVI device and the associated VNF device.

Alternatively, in an embodiment, step 402 comprises actions in which: determine, in accordance with the type of failure, in the first comprehensive failure information, whether the orchestrator contains a failure elimination policy corresponding to the type of failure; and when the orchestrator contains a failure-correcting policy appropriate to the type of failure, the failure of the first NFVI device and / or the failure of the NFVI device correlated with the first NFVI device are eliminated; or, when the orchestrator does not contain a failover policy appropriate to the type of failure, transmit the first comprehensive failure information to the OSS / BSS operations and business support system.

Alternatively, in an embodiment, step 402 comprises actions in which: determine, in accordance with the type of failure, in the first comprehensive failure information, whether the orchestrator contains a failure elimination policy corresponding to the type of failure; and when the orchestrator contains a failure-correcting policy corresponding to the type of failure, the failure of the first NFVI device, the failure of the NFVI device correlated with the first NFVI device, and the failure of the VNF device correlated with the first NFVI device are eliminated; or when the orchestrator does not contain a failover policy appropriate to the type of failure, transmit the first comprehensive failure information to the OSS / BSS system.

Alternatively, in the embodiment, before step 402, the method further comprises the steps of: finding, in accordance with the first comprehensive failure information, whether the orchestrator contains comprehensive failure information that is the same as the first comprehensive failure information; and when the orchestrator contains comprehensive failure information, which is the same as the first comprehensive failure information, the first comprehensive failure information is deleted. In a nutshell, since correlated failures occur in multiple correlated NFVI devices or VIM devices, the orchestrator can receive multiple pieces of the same comprehensive failure information, where the same comprehensive failure information is here referred to as the content of the information about denials of comprehensive denial information is the same. In this case, the orchestrator can perform the detection of a repeating alarm. The orchestra continues to process that comprehensive error information that is being processed, and deletes the same comprehensive error information that has not yet been processed.

Alternatively, in the embodiment, the first failure information further comprises at least an operational state or time of failure, the first comprehensive failure information further comprises information about the failure state, and the failure state comprises at least one of the following: not yet processed, handled, failure resolved or failure not yet resolved.

In accordance with the failure handling control method provided in this embodiment of the present invention, the orchestrator receives comprehensive failure information reported by VIM to perform comprehensive processing of the correlated pieces of failure information that can implement the failure message and processing in the NFV environment. In addition, since comprehensive processing is performed on correlated pieces of fault information and the same comprehensive fault information is deleted by detecting a repeating alarm, the efficiency and accuracy of the fault processing are improved.

In FIG. 5 is a flowchart of a method for controlling a failure processing in accordance with an embodiment of the present invention. The method shown in FIG. 5 is performed by an orchestra.

501: The orchestrator receives the second comprehensive failure information sent by the virtualized network function manager VNFM, where the second comprehensive failure information contains the second failure information, the second failure information contains the identifier of the failed device and the type of failure, and the second failure information is used to indicate that the failure occurred in the first VNF network function virtualization device having the identifier of the failed device.

502: The orchestrator performs troubleshooting or reports the process in accordance with the second comprehensive failure information.

In accordance with the failure handling control method provided in this embodiment of the present invention, the orchestrator obtains information about the failures of the hardware device and / or software in order to comprehensively process the correlated pieces of failure information, which can implement the failure message and the processing in the medium. NFV.

Alternatively, in the embodiment, the second comprehensive failure information further comprises failure information of the VNF device correlated with the first VNF device and / or information of the administrator device of the virtualized NFVI infrastructure correlated with the first VNF device. That is, comprehensive failure information received by the orchestrator from the VNFM may contain information about the failures of the NFVI device or may contain information about the failures of the VNF device or may contain information about the failures of the NFVI device and the associated VNF device.

Alternatively, in an embodiment, step 502 comprises actions in which: according to the type of failure, the second comprehensive failure information is determined according to whether the orchestrator contains a failure elimination policy corresponding to the type of failure; and when the orchestrator contains a failure-correcting policy corresponding to the type of failure, the failure of the first VNF device and / or the failure of the VNF device correlated with the first VNF device is eliminated; or, when the orchestrator does not contain a failure-correcting policy appropriate to the type of failure, transmit second comprehensive failure information to the OSS / BSS operations and business support system.

Alternatively, in an embodiment, step 502 comprises actions in which: according to the type of failure, the second comprehensive failure information is determined according to whether the orchestrator contains a failure elimination policy corresponding to the type of failure; and when the orchestrator contains a failure-correcting policy corresponding to the type of failure, the failure of the first VNF device, the failure of the VNF device correlated with the first VNF device, and the failure of the NFVI device correlated with the first VNF device are eliminated; or, when the orchestrator does not contain a failover policy appropriate to the type of failure, transmit second comprehensive failure information to the OSS / BSS system.

Alternatively, in the embodiment, prior to step 502, the method further comprises the steps of: detecting, in accordance with the second comprehensive failure information, whether the orchestrator contains comprehensive failure information that is the same as the second comprehensive failure information; and when the orchestrator contains comprehensive failure information, which is the same as the second comprehensive failure information, the second comprehensive failure information is deleted. Specifically, since correlated failures occur in multiple correlated NFVI devices or VIM devices, the orchestrator can receive multiple pieces of the same comprehensive failure information, where the same comprehensive failure information is referred to herein with reference to denials of comprehensive denial information is the same. In this case, the orchestrator can perform the detection of a repeating alarm. The orchestra continues to process that comprehensive error information that is being processed, and deletes the same comprehensive error information that has not yet been processed.

Alternatively, in the embodiment, the second failure information further comprises at least an operational state or time of failure, the second comprehensive failure information further comprises information about the failure state, and the failure state contains at least one of the following: not yet processed, being processed, Failure resolved or failure not resolved yet.

In accordance with the failure processing control method provided in this embodiment of the present invention, the orchestrator receives comprehensive failure information communicated by the VNFM to perform comprehensive processing of the correlated pieces of failure information, which can carry out failure reporting and processing in the NFV environment. In addition, since comprehensive processing is performed on correlated pieces of fault information and the same comprehensive fault information is deleted by detecting repeated alarms, the efficiency and accuracy of fault processing is improved.

In FIG. 6a shows an interaction diagram of a failure processing control method in accordance with an embodiment of the present invention; The method shown in FIG. 6a may be performed by the NFV system shown in FIG. one.

601: VIM receives failure information.

When VIM detects that a failure has occurred somewhere in the HW, Host OS, Hypervisor or VM in the NFVI, VIM receives information about the failures of the failed NFVI device. Specifically, the received failure information may be generated to be reported to the VIM by the failed NFVI device, or may be generated in accordance with the detected failure.

VIM can detect, using the following methods, that a failure has occurred in the NFVI device.

For convenience of description, the following is described using an example in which a failure occurs in the first NFVI device, where the first NFVI device can be any of the following: HW, Host OS, Hypervisor or VM in NFVI, and the device may comprise a hardware device or a software device.

Method 1

When a failure occurs in the first NFVI device, the first NFVI device generates fault information, where the failure information contains at least the identifier of the failed device, which is used to uniquely identify the first NFVI device, and the actual position of the failed first NFVI device or position The failed first NFVI device in a topological relation can be uniquely determined using the identifier. The failure information further comprises a failure identifier used to uniquely identify the failure information. Failure information additionally contains the type of failure used to represent the cause of the failure, such as overload, power outage, memory leak, port error, or failure. In addition, the failure information may further include an operating state and a failure time, where the operating state is used to indicate whether the first NFVI device is currently operating normally and the failure time can be used to record the time when the failure occurs. As an example, the format of the failure information can be shown in table 1.

Table 1

Failure Information

Failure ID ID of failed device Type of failure Working condition Failure time Other Uniquely Identified Failure Information NFVI Device ID Overload / Power Outage / No Failure Normal / failure Time

After generating the failure information in the above format, the first NFVI can transmit the failure information to VIM using the Nf-Vi interface, and, alternatively, the first NFVI device can also, using EMS, transmit the failure information to the OSS / BSS system for control, registration and submission.

Method 2

VIM may transmit an indication message to the first NFVI device periodically or, when required, to instruct the first NFVI device to perform fault detection. If the first NFVI device detects a failure, the first NFVI device can send back failure information similar to the information shown in Table 1; or, if the first NFVI device has no failure, the first NFVI device may not send back any messages, or it may send back a failure message that indicates “No fault” for the type of failure and the operating state is “Normal” ("Normal"), see table 1.

Method 3

The first NFVI device may periodically send a VIM message indicating that I am alive, indicating that the first NFVI device is operating normally. VIM periodically receives “I'm Alive” messages from the first NFVI device and realizes that the first NFVI device is working properly. When I am alive from the first NFVI device is interrupted, VIM determines that a failure has occurred in the first NFVI device and that VIM can generate failure information for the first NFVI. The specific format of the failure information is similar to the failure information shown in Table 1, and no further details are again described here.

When an NFVI device cannot report failure information due to an unexpected event, such as a power outage, VIM can still understand that a failure has just occurred in the first NFVI device.

Method 4

VIM can perform failure detection on the NFVI periodically or as needed, and then VIM generates failure information of the first NFVI in accordance with the result of the failure detection. The specific format of the failure information is similar to the failure information shown in Table 1, and no further details are again described here.

In conclusion, VIM can detect the failure of the NFVI device using any of the methods listed above, and, obviously, can perform the detection by combining multiple methods, for example, combining method 1 and method 3. The NFVI device sends VIM messages “I am alive” periodically and, when a failure occurs, sends failure information to VIM. If the NFVI device cannot report failure information due to a catastrophic failure, VIM may, due to the termination of the "I'm alive" messages, understand that a failure has occurred in the NFVI device.

602: VIM generates comprehensive failure information.

After the VIM receives the fault information transmitted by the first NFVI device, or when the VIM generates the fault information according to the failure of the first NFVI device, the VIM needs to collect the failure information of the other NFVI device correlated with the first NFVI device to generate comprehensive information about failures, so as to perform comprehensive processing.

Specifically, since there is a correlation between the HW, Host OS, Hypervisor, and VM devices when a failure occurs in the first NFVI device, failures may occur in some devices correlated with the first NFVI device. In FIG. 6b shows, for example, the correlation between HW, Host OS, Hypervisor, and VM devices. For example, Host OS1, Hypervisor1, VM1, and VM2 are correlated with HW1. This means that when a failure occurs in HW1, failures can also occur in virtualized devices installed on HW1: Host OS1, Hypervisor1, VM1, and VM2. In this case, VIM can collect failure information reported from Host OS1, Hypervisor1, VM1, and VM2, and generate comprehensive failure information with reference to the failure information of HW1. Specifically, the comprehensive failure information shown in Tables 2 can be generated as follows:

table 2

Comprehensive Failure Information

Comprehensive Failure Information Identifier Failure Information
Hw Failure Information
Host OS Hypervisor Failure Information Failure Information
VM Failure status Other Uniquely Identified Comprehensive Failure Information Hw1 Host OS1 Hypervisior1 VM1, VM2 Not yet processed / being processed / eliminated / not yet eliminated

The failure information format for HW, Host OS, Hypervisor, and VM devices is similar to the format shown in Table 1. The comprehensive fault information identifier is used to uniquely identify comprehensive fault information. It should be understood that the comprehensive failure information shown in Table 2 is a specific example, and device failure information, which is specifically included in the comprehensive failure information, is determined in accordance with the correlation. When comprehensive failure information is only being generated, the failure status can be set to “Not processed yet.”

603: Perform detection of a repeating alarm.

After generating comprehensive failure information, VIM can locally locate the generated comprehensive failure information to determine if it is the same information. Specifically, since after a failure occurs in the NFVI device, all correlated faulty NFVI devices can report failure information, VIM can generate multiple fragments of the same comprehensive failure information for the same failure. For example, if a failure occurs in HW1, failures also occur in Host OS1, Hypervisor1, VM1, and VM2 correlated with HW1, and Host OS1, Hypervisor1, VM1, and VM2 correlated with HW1 perform the same operation as HW1. VIM can generate multiple pieces of the same comprehensive failure information after collecting correlated failure information, in which case, VIM can only process one piece of comprehensive failure information and discard the other same comprehensive failure information. It should be understood that the same failure information refers to failure information of the HW, Host OS, Hypervisor, and VM, which are partially the same, but the failure identifiers and failure conditions may be different.

Specifically, comprehensive failure information can be backed up or discarded in accordance with the failure state of the comprehensive failure information, for example, the failure state of the comprehensive failure information that has just been generated is “Not processed yet”, Repeated alarm detection is performed for comprehensive failure information and if the same comprehensive failure information is detected in which the failure state is “Being processed”, in sister information about failures that has not yet been processed is discarded and comprehensive information about failures in which the failure state is “Being processed” is backed up and processed.

604: VIM performs a self-healing determination.

When VIM generates comprehensive failure information, VIM can first determine if the type of failure in the comprehensive failure information is the type of failure that VIM can handle.

Specifically, VIM has a failover policy, where the failover policy contains the mapping between the identifier of the failed device, the type of failure, and the method of troubleshooting. Whether processing can be performed can be determined by determining if the type of failure in comprehensive failure information exists in the failover policy. For example, the type of failure HW1 is “low performance” and the corresponding method of resolving the failure is “restart”.

In addition, when comprehensive failure information contains information about the failures of multiple correlated NFVI devices, VIM may, in accordance with the priorities of the NFVI devices, decide to perform a self-healing determination determined by the file type in the NFVI device failure information. The priorities are: HW> Host OS> Hypervisor> VM. For example, as shown in Table 2, when comprehensive failure information contains failure information HW1, Host OS1, Hypervisor1, VM1, and VM2, VIM can preferably handle the failure HW1, that is, determine according to the type of failure in the failure information HW1, such information as “low performance”, and a way to eliminate which failure is to “restart”.

Specifically, a method of eliminating a failure may include, in particular, one of the following methods. restarting the hardware device, rebooting the software (Host OS, Hypervisor, etc.), migrating the VM, rebooting the VNF of the VNF installation software, re-initiating the VNF, adding the VNF example, migrating the VNF (i.e., reallocating resources for VNF), and re-initiating the VNF Forwarding Graph.

605a: VIM can perform a self-healing process.

If VIM determines that processing can be performed, VIM performs NFVI device failover in accordance with the failover method. If the failure repair is successful and the correlations of the correlated NFVI devices are resolved, the orchestrator is informed that the failure repair is successful and the process for resolving the failure ends.

If comprehensive fault information contains multiple NFVI devices and the NFVI device failure, which is preferably handled, is resolved successfully, but the failures of other correlated NFVI devices continue to exist, step 604 is repeated to determine and eliminate the failure of the NFVI device that has the highest priority among the remaining failed devices NFVI until the failures of all NFVI devices in comprehensive fault information are resolved. The orchestrator is then notified that the troubleshooting has completed successfully and the processing process for troubleshooting has ended.

Specifically, for comprehensive failure information that can be processed, VIM can set the troubleshooting state to “Being processed” so as to avoid reprocessing the same comprehensive failure information that is generated sequentially and for which The status is indicated as Not processed yet.

An NFVI device for which a fault has been successfully resolved can notify VIM by reporting fault information in which the operating state is indicated as “Normal” and which is similar to the fault information shown in Table 1, that is, troubleshooting was successful. When the failures of all correlated NFVI devices in the comprehensive failure information are resolved, VIM can set the failure status of the comprehensive failure information to “Repaired” and report the comprehensive failure information to the orchestrator using the Or-Vi interface. It should be understood that the success of troubleshooting can also be reported using a predetermined alarm, which is not limited in the present invention.

In addition, the NFVI device for which the failure is eliminated can be isolated to avoid the additional propagation of failures caused by the interaction between the failed device and another neighboring device.

605b: VIM cannot complete the self-healing process.

If VIM's failover policy does not contain the type of failure of the NFVI device for which the failover is to be addressed, then VIM can set the failure state in the comprehensive failure information to be "Not repaired yet" and report comprehensive failure information to the orchestrator using the Or-Vi interface.

606: The orchestra performs a self-healing determination.

When the orchestrator receives comprehensive failure information transmitted via VIM, the orchestrator detects whether the self-healing process can be performed, which is similar to the self-healing definition for VIM. The orchestrator requests a local fault resolution policy, and if the processing can be completed and the fault removal is successful, the orchestrator sets the failure state in the comprehensive failure information as “Repaired” and reports the comprehensive failure information to the OSS / BSS system; or if the orchestrator cannot complete the troubleshooting process or can perform the troubleshooting process, but the failure repair fails, the orchestrator sets the failure status of the comprehensive NFVI device failure information as “Not repaired yet” and reports the comprehensive fault information to the OSS / BSS system. It should be understood that since the orchestrator is responsible for the resources of the orchestration and management and for the implementation of the NFV service, the orchestra has relatively high processing capabilities and administrative permissions and can eliminate most failures. The OSS / BSS system is only informed of a very small number of failures that cannot be handled or whose resolution fails.

Specifically, the method of resolving the failure may include, in particular, one of the following methods: restarting the hardware device, rebooting the software (Host OS, Hypervisor, etc.), migrating the VM, rebooting the VNF of the VNF installation software, re-initiating the VNF , adding a VNF example, migrating a VNF (that is, reallocating resources to a VNF), and re-initiating a VNF Forwarding Graph.

607: The OSS / BSS system performs troubleshooting.

The OSS / BSS system sets the failure state in the received comprehensive failure information as “Being processed”. The OSS / BSS system then performs the failover in accordance with the failover policy method. After the fault has been resolved, the OSS / BSS system may receive the fault rectification message sent by the NFVI and then the OSS / BSS system changes the fault state in the comprehensive fault information to “Repaired”. The OSS / BSS Failover Policy contains default methods for handling all types of failures.

In accordance with the fault handling management method provided in this embodiment of the present invention, VIM obtains fault information of the hardware device and / or software to comprehensively process the correlated pieces of fault information, which can implement fault reporting and processing in the medium NFV. In addition, since comprehensive processing is performed on the correlated pieces of fault information, the same comprehensive fault information is deleted by detecting repeated alarms and the efficiency and accuracy of the fault processing are improved.

In FIG. 7 is an interaction diagram of a failure processing control method according to an embodiment of the present invention; The method shown in FIG. 7 may be performed by the NFV system shown in FIG. one.

701: VNFM receives failure information.

When the VNFM detects that a failure has occurred in any VNF device in the VNF, the VNFM receives the failure information of the failed VNF device. Specifically, the received failure information may be generated by the VNFM by the failed VIM device, or may be generated locally by the VNFM in accordance with the detected failure.

VNFM, using the following methods, can detect that a failure has occurred in the VNF device:

For convenience of description, the following is described using an example in which a failure occurs in the first VNF device, where the first VNF device may be a VNF device in the VNF and the device may be a hardware device, a software device, or any specific example.

Method 1

When a failure occurs in the first VNF device, the first VNF device generates fault information, where the failure information contains at least the identifier of the failed device, which is used to uniquely identify the first VNF device, and the actual position of the failed first VNF device or position The failed first VNF device in a topological relation can be uniquely determined using the identifier. Failure identifier is used to uniquely identify failure information. Failure information additionally contains the type of failure used to represent the cause of the failure, such as overload, power outage, memory leak, port error, or failure. In addition, the failure information may further include an operating state and a failure time, where the operating state is used to indicate whether the first VNF is currently operating normally and the failure time can be used to record the time when the failure occurs. As an example, the format of the failure information can be shown in table 3.

Table 3

Failure Information

Failure ID ID of failed device Type of failure Working condition Failure time Other Uniquely identifiable information about
Failure VNF Device ID Overload / Power Outage / No Failure Normal / failure Time

After generating the failure information in the above format, the first VNF device can transmit the failure information to the VNFM using the Ve-Vnfm interface, and, alternatively, the first NFVI device can also use the vEMS to transmit the failure information to the OSS / BSS system for control registration and submission.

Method 2

The VNFM may transmit an indication message to the first VNF device periodically or as necessary to instruct the first VNF device to perform fault detection. If the first VNF device detects a failure, the first VNF device can transmit back to the VNFM failure information similar to the information shown in Table 3; or, if the first VNF device does not have a failure, the first VNF device may not send back any messages or it may send a failure message back indicating "No fault" for the type of failure and the operating state is "Normal" ("Normal"), see table 3.

Method 3

The first VNF device may periodically transmit a message with the indication "I'm alive" indicating to the VNFM that the first VNF device is operating normally. VNFM periodically receives “I'm Alive” messages from the first VNF device and realizes that the first VNF device is working properly. When the “I'm alive” messages from the first VNF device are interrupted, the VNFM determines that a failure has occurred in the first VNF device and the VNFM can generate failure information of the first VNF device. The specific format of the failure information is similar to the failure information shown in Table 3, and no further details are again described here.

When the VNF cannot communicate failure information due to an unexpected event, the VNFM can still understand that a failure has occurred in the first VNF.

Method 4

The VNFM may perform failure detection on the VNF periodically or as needed, and then the VNFM generates failure information of the first VNF in accordance with the result of the failure detection. The specific format of the failure information is similar to the failure information shown in Table 3, and no further details are again described here.

In conclusion, the VNFM can detect the failure of the VNF device using any of the above methods, and, obviously, can perform the detection by combining multiple methods, for example, combining the method 1 and method 3. The VNF device transmits to the VNFM messages "I am alive" periodically and, when a failure occurs, transmits failure information to the VNFM. If the VNF device cannot report failure information due to a catastrophic failure, the VNFM may, due to the termination of the "I'm alive" messages, understand that a failure has occurred in the VNF device.

702: VNFM generates comprehensive failure information.

After the VNFM receives the failure information transmitted by the first VNF, or the VNFM generates the failure information corresponding to the failure of the first VNF, the VNFM can generate comprehensive failure information in accordance with the failure information of the first VNF. Alternatively, the VNFM may collect failure information of other VNF devices correlated with the first VNF device to generate comprehensive failure information so as to perform comprehensive processing.

Since there is a correlation between VNF devices when a failure occurs in the first VNF device, a failure can also occur in another VNF device correlated with the first VNF device. In FIG. 6b schematically shows the correlation between VNF devices. For example, VNF1 and VNF2 are both based on VM1, that is, there is a correlation between VNF1 and VNF2. When a failure occurs in VNF1, a failure can also occur in VNF2.

In this case, the VNFM can collect the failure information reported by VNF1 and generate comprehensive failure information with reference to the VNF2 failure information. Specifically, the comprehensive failure information shown in Table 4 can be generated as follows:

Table 4

Comprehensive Failure Information

Comprehensive Information Identifier
about refusal Information about
VNF state Failure status Other Uniquely Identified Comprehensive Information
about refusal VNF1, VNF2 Not processed yet /
processed / eliminated / not yet eliminated

The fault information formats VNF1 and VNF2 are similar to the formats of table 3.

It should be understood that the comprehensive failure information shown in Table 4 is a specific example and the device failure information that is specifically included in the comprehensive failure information is determined in accordance with the correlation. When comprehensive failure information is only being generated, the failure status can be set to “Not processed yet.”

703: Perform detection of a repeating alarm.

After VNFM generates comprehensive failure information, VNFM can locally locate the generated comprehensive failure information to determine if it is the same information. Specifically, since after a failure occurs in the VNF device, all correlated faulty VNF devices can report failure information, the VNFM can generate multiple fragments of the same comprehensive failure information for the same failure. For example, if a failure occurs in VNF1, a failure also occurs in VNF2 correlated with VNF1, and VNF2 performs the same operation as VNF1. VNFM can generate multiple fragments of the same comprehensive failure information after collecting correlated failure information, in which case VNFM can only process one piece of comprehensive failure information and discard another same comprehensive failure information. It should be understood that the same failure information refers to VNF state information, which is partially the same, and failure states may be different.

Specifically, the comprehensive failure information may be backed up or discarded in accordance with the failure status of the comprehensive failure information, for example, the failure state of the comprehensive failure information that has just been generated is “Not processed yet”, repeating alarm detection is performed for comprehensive failure information and if the same comprehensive failure information is found in which the failure state is “Being processed”, all Third-party failure information that has not yet been processed is discarded.

704: VNFM performs self-healing determination.

When the VNFM generates comprehensive failure information, the VNFM can first determine if the type of failure in the comprehensive failure information is the type of failure that the VNFM can handle.

Specifically, VNFM has a failover policy, where the failover policy contains the mapping between the identifier of the failed device, the type of failure, and the method of troubleshooting. Whether processing can be performed can be decided by determining if the type of failure in comprehensive failure information exists in the failover policy. For example, the type of failure of VNF1 is “low performance” and the corresponding method of resolving the failure is “adding a VNF instance”.

Specifically, the method of resolving the failure may include, in particular, one of the following methods: restarting the hardware device, rebooting the software (Host OS, Hypervisor, etc.), migrating the VM, rebooting the VNF of the VNF installation software, re-initiating the VNF , adding a VNF example, migrating a VNF (that is, reallocating resources to a VNF), and re-initiating a VNF Forwarding Graph.

705a VNFM may perform a self-healing process.

If the VNFM determines that processing can be performed, the VNFM performs VNF device failover in accordance with the failover method. If the failover is successful and the correlations of the correlated VNF devices are resolved, the orchestrator is notified that the failover is successful and the process for resolving the failure ends.

If comprehensive fault information contains multiple VNF devices and the failure of the VNF device, which is preferably handled, is resolved successfully, but the failures of other correlated VNF devices continue to exist, step 704 is repeated to determine and eliminate the failure of the VNF device until it is resolved Failures of all VNF devices in comprehensive failure information. The orchestrator is then notified that the troubleshooting has completed successfully and the processing process for troubleshooting has ended.

Specifically, for comprehensive failure information that can be processed, VNFM can set the troubleshooting state to be Being processed so as to avoid reprocessing the same comprehensive failure information that is generated sequentially and in which The status is indicated as Not processed yet.

A VNF device that has successfully resolved the failure can notify the VNFM that the troubleshooting was successful by reporting the failure information, in which the operating state is indicated as “Normal” and which is similar to the failure information shown in Table 3 When the failures of all correlated VNF devices in the comprehensive failure information are resolved, VNFM can set the failure status of the comprehensive failure information to be “Repaired” and report comprehensive information about the failures of the orchestra from using the Or-Vnfm interface. It should be understood that the success of troubleshooting can also be reported using a predetermined alarm, which is not limited in the present invention.

In addition, the VNF device for which the failure is eliminated can be isolated to avoid the additional propagation of failures that is caused by the interaction between the failed device and another neighboring device.

705b: VNFM may perform a self-healing process.

If the VNFM failover policy does not contain the type of failure of the VNF device for which the fault should be resolved, then VNFM can set the failure state in the comprehensive failure information as "Not repaired yet" and report comprehensive failure information to the orchestrator using the Or-Vnfm interface.

706: The orchestra performs a self-healing determination.

When the orchestrator receives comprehensive failure information transmitted through the VNFM, the orchestrator detects whether a self-healing process can be performed that is similar to the self-healing definition for VNFM. The orchestrator requests a local fault resolution policy, and if the processing can be completed and the fault removal is successful, the orchestrator sets the failure state in the comprehensive failure information as “Repaired” and reports the comprehensive failure information to the OSS / BSS system; or if the orchestrator cannot complete the troubleshooting process or can perform the troubleshooting process, but the failure repair fails, the orchestrator sets the failure status of the comprehensive NFVI device failure information as “Not repaired yet” and reports the comprehensive fault information to the OSS / BSS system. It should be understood that since the orchestrator is responsible for the resources of the orchestration and management and for the implementation of the NFV service, the orchestra has relatively high processing capabilities and administrative permissions and can eliminate most failures. The OSS / BSS system is only informed of a very small number of failures that cannot be handled or whose resolution fails.

707: The OSS / BSS system performs troubleshooting.

The OSS / BSS system sets the failure state in the received comprehensive failure information as “Being processed”. The OSS / BSS system then performs the failover in accordance with the failover policy method. After the failure has been resolved, the OSS / BSS system may receive the failure correction notification sent by the VNF and then the OSS / BSS system changes the failure status of the comprehensive failure information to “Repaired”. The OSS / BSS Failover Policy contains default methods for handling all types of failures.

Specifically, the method of resolving the failure may include, in particular, one of the following methods: restarting the hardware device, rebooting the software (Host OS, Hypervisor, etc.), migrating the VM, rebooting the VNF of the VNF installation software, re-initiating the VNF , adding a VNF example, migrating a VNF (that is, reallocating resources to a VNF), and re-initiating a VNF Forwarding Graph.

In accordance with the fault handling management method provided in this embodiment of the present invention, VIM obtains fault information of the hardware device and / or software to comprehensively process the correlated pieces of fault information, which can implement fault reporting and processing in the medium NFV. In addition, since comprehensive processing is performed on the correlated pieces of fault information, the same comprehensive fault information is deleted by detecting repeated alarms and the efficiency and accuracy of the fault processing are improved.

In FIG. 8 is an interaction diagram of a failure processing control method according to an embodiment of the present invention. The method shown in FIG. 8 may be performed by the NFV system shown in FIG. one.

801: VIM receives failure information.

When VIM detects that a failure has occurred somewhere in the HW, Host OS, Hypervisor or VM in the NFVI, VIM receives information about the failures of the failed NFVI device. Specifically, the received failure information may be generated to be reported to the VIM by the failed NFVI device, or may be generated in accordance with the detected failure. Specifically, the method for detecting by VIM that a failure has occurred in the NFVI device is similar to the method described in step 601 of FIG. 6 and no further details are repeatedly described here.

802: VIM generates comprehensive failure information.

After the VIM receives the failure information transmitted by the first NFVI device, or when the VIM generates the failure information according to the failure of the first NFVI device, the VIM needs to collect the failure information of another NFVI device correlated with the first NFVI device to form a comprehensive processing that is substantially similar to the method described in block 602 of FIG. 6, and no further details are repeatedly described here.

803: Perform detection of a repeating alarm.

After generating comprehensive failure information, VIM can locally locate the generated comprehensive failure information to determine if it is the same information. The specific detection method is similar to the method described in step 603 of FIG. 6, and no further details are repeated here.

804: VIM performs a self-healing determination.

When VIM generates comprehensive failure information, VIM can first determine if the type of failure in the comprehensive failure information is the type of failure that VIM can handle. The specific detection method is similar to the method described in step 604 of FIG. 6, and no further details are repeated here.

805a: VIM can perform a self-healing process.

If VIM determines that processing can be performed, VIM performs NFVI device failover in accordance with the failover method. If the failure repair is successful and the correlations of the correlated NFVI devices are resolved, the orchestrator is informed that the failure repair is successful and the process for resolving the failure ends.

If comprehensive failure information contains multiple NFVI devices and the NFVI device failure, which is preferably handled, is resolved successfully, but the failures of other correlated NFVI devices continue to exist, step 804 is repeated to determine and eliminate the failure of the NFVI device, which has the highest priority among the remaining failed devices NFVI until the failures of all NFVI devices in comprehensive fault information are resolved. The orchestrator is then notified that the troubleshooting has completed successfully and the processing process for troubleshooting has ended. The specific detection method is similar to the method described in step 605a of FIG. 6, and no further details are repeated here.

In addition, the NFVI device for which the failure is eliminated can be isolated to avoid the additional propagation of failures caused by the interaction between the failed device and another neighboring device.

805b: If VIM cannot complete the self-healing process, VIM submits a message to VNFM.

If VIM's failover policy does not contain the type of failure of the NFVI device for which the failover is to be addressed, then VIM can set the failure state in the comprehensive failure information to be "Not repaired yet" and report comprehensive failure information VNFM using the Vi-Vnfm interface.

When the VNFM receives comprehensive fault information transmitted via VIM, the VNFM detects whether the self-healing process can be performed, which is similar to the self-healing definition for VIM. VNFM asks for a local failover policy, and if processing can be completed and the failover is successful, VNFM sets the failure status in the comprehensive failure information to “Repaired” and reports the comprehensive failure information to the orchestrator; or, if VNFM cannot complete the troubleshooting process, or can perform the troubleshooting process, but the troubleshooting fails, VNFM sets the failure status in the comprehensive NFVI device failure information to "Not repaired yet" and reports the comprehensive information about failures to the orchestra.

806: The orchestra performs a self-healing determination.

When the orchestrator receives comprehensive NFVI failure information transmitted through the VNFM, the orchestrator detects whether a self-healing process can be performed that is similar to the self-healing definition for VIM. The orchestrator requests a local fault resolution policy, and if the processing can be completed and the fault removal is successful, the orchestrator sets the failure state in the comprehensive failure information as “Repaired” and reports the comprehensive failure information to the OSS / BSS system; or if the orchestrator cannot complete the troubleshooting process or can perform the troubleshooting process, but the failure repair fails, the orchestrator sets the failure status of the comprehensive NFVI device failure information as “Not repaired yet” and reports the comprehensive fault information to the OSS / BSS system. It should be understood that since the orchestrator is responsible for the resources of the orchestration and management and for the implementation of the NFV service, the orchestra has relatively high processing capabilities and administrative permissions and can eliminate most failures. The OSS / BSS system is only informed of a very small number of failures that cannot be handled or whose resolution fails.

807: The OSS / BSS system performs troubleshooting.

The OSS / BSS system sets the failure state in the received comprehensive failure information as “Being processed”. The OSS / BSS system then performs the failover in accordance with the failover policy method. After the fault has been resolved, the OSS / BSS system may receive the fault rectification message sent by the NFVI and then the OSS / BSS system changes the fault state in the comprehensive fault information to “Repaired”. The OSS / BSS Failover Policy contains default methods for handling all types of failures.

Specifically, a method of eliminating a failure may include, in particular, one of the following methods. restarting the hardware device, rebooting the software (Host OS, Hypervisor, etc.), migrating the VM, rebooting the VNF of the VNF installation software, re-initiating the VNF, adding the VNF example, migrating the VNF (i.e., reallocating resources for VNF), and re-initiating the VNF Forwarding Graph.

In accordance with the fault handling management method provided in this embodiment of the present invention, VIM obtains fault information of the hardware device and / or software to comprehensively process the correlated pieces of fault information, which can implement fault reporting and processing in the medium NFV. In addition, since comprehensive processing is performed on the correlated pieces of fault information, the same comprehensive fault information is deleted by detecting repeated alarms and the efficiency and accuracy of the fault processing are improved.

In FIG. 9 is an interaction diagram of a failure processing control method according to an embodiment of the present invention. The method shown in FIG. 9 can be performed by the NFV system shown in FIG. one.

901: VIM receives failure information.

When VIM detects that a failure has occurred somewhere in the HW, Host OS, Hypervisor or VM in the NFVI, VIM receives information about the failures of the failed NFVI device. Specifically, the received failure information may be generated and reported by the VIM to the failed NFVI device, or may be generated in accordance with the detected failure. Specifically, the method for detecting by VIM that a failure has occurred in the NFVI device is similar to the method described in step 601 of FIG. 6 and no further details are not described here again.

902: VIM generates comprehensive failure information.

After the VIM receives the failure information transmitted by the first NFVI device, or when the VIM generates the failure information according to the failure of the first NFVI device, the VIM needs to collect the failure information of another NFVI device correlated with the first NFVI device to form a comprehensive processing that is substantially similar to the method described in block 602 of FIG. 6, and no further details are repeatedly described here.

903: Perform detection of a repeating alarm.

After generating comprehensive failure information, VIM can locally locate the generated comprehensive failure information to determine if it is the same information. The specific detection method is similar to the method described in step 603 of FIG. 6, and no further details are repeated here.

904: VIM performs a self-healing determination.

When VIM generates comprehensive failure information, VIM can first determine if the type of failure in the comprehensive failure information is the type of failure that VIM can handle. The specific detection method is similar to the method described in step 604 of FIG. 6, and no further details are repeated here.

905a: VIM can perform a self-healing process.

If VIM determines that processing can be performed, VIM performs NFVI device failover in accordance with the failover method. If the failure repair is successful and the correlations of the correlated NFVI devices are resolved, the orchestrator is informed that the failure repair is successful and the process for resolving the failure ends.

If comprehensive fault information contains multiple NFVI devices and the NFVI device failure, which is preferably handled, is resolved successfully, but the failures of other correlated NFVI devices continue to exist, step 904 is repeated to determine and eliminate the failure of the NFVI device, which has the highest priority among the remaining failed devices NFVI until the failures of all NFVI devices in comprehensive fault information are resolved. The orchestrator is then notified that the troubleshooting has completed successfully and the processing process for troubleshooting has ended. The specific detection method is similar to the method described in step 605a of FIG. 6, and no further details are repeated here.

In addition, the NFVI device for which the failure is eliminated can be isolated to avoid the additional propagation of failures caused by the interaction between the failed device and another neighboring device.

905b: If VIM cannot complete the self-healing process, VIM submits a VNFM message.

If VIM's failover policy does not contain the type of failure of the NFVI device for which the failover is to be addressed, then VIM can set the failure state in the comprehensive failure information to be "Not repaired yet" and report comprehensive failure information VNFM using the Vi-Vnfm interface.

When the VNFM receives comprehensive fault information transmitted via VIM, the VNFM detects whether the self-healing process can be performed, which is similar to the self-healing definition for VIM. VNFM asks for a local failover policy, and if processing can be completed and the failover is successful, VNFM sets the failure status in the comprehensive failure information to “Repaired” and reports the comprehensive failure information to the orchestrator; or, if VNFM cannot complete the troubleshooting process, or can perform the troubleshooting process, but the troubleshooting fails, VNFM sets the failure status in the comprehensive NFVI device failure information to "Not repaired yet" and reports the comprehensive VIM failure information.

906: The orchestra performs a self-healing determination.

VIM then reports comprehensive NFVI failure information to the orchestrator using the Or-Vi interface, and the orchestrator detects whether a self-healing process can be performed that is similar to the self-healing definition for VIM. The orchestrator requests a local fault resolution policy, and if the processing can be completed and the fault removal is successful, the orchestrator sets the failure state in the comprehensive failure information as “Repaired” and reports the comprehensive failure information to the OSS / BSS system; or, if the orchestrator cannot complete the troubleshooting process, or can perform the troubleshooting process, but the troubleshooting fails, the orchestrator sets the failure status in the comprehensive failure information as "Not repaired yet" and reports comprehensive information about failures of the OSS / BSS system. It should be understood that since the orchestrator is responsible for the resources of the orchestration and management and for the implementation of the NFV service, the orchestra has relatively high processing capabilities and administrative permissions and can eliminate most failures. The OSS / BSS system is only informed of a very small number of failures that cannot be handled or whose resolution fails.

907: The OSS / BSS system performs troubleshooting.

The OSS / BSS system sets the failure state in the received comprehensive failure information as “Being processed”. The OSS / BSS system then performs the failover in accordance with the failover policy method. After the fault has been resolved, the OSS / BSS system may receive the fault rectification message sent by the NFVI and then the OSS / BSS system changes the fault state in the comprehensive fault information to “Repaired”. The OSS / BSS Failover Policy contains default methods for handling all types of failures.

Specifically, the method of resolving the failure may include, in particular, one of the following methods: restarting the hardware device, rebooting the software (Host OS, Hypervisor, etc.), migrating the VM, rebooting the VNF of the VNF installation software, re-initiating the VNF , adding a VNF example, migrating a VNF (that is, reallocating resources to a VNF), and re-initiating a VNF Forwarding Graph.

It should be understood that in FIG. 6, FIG. 8 and FIG. 9 illustrates the processes for troubleshooting and controlling the failure handling of an NFVI device by a VIM device, and FIG. 7 illustrates the process of troubleshooting and managing the failure of a VNF device by a VNFM device. Failover processing and control of the NFVI device via the VIM device and the process of troubleshooting and control of the VNF device through the VNFM device may be two relatively separate processes or may also be two simultaneous processes, which is not limited in the present invention.

In accordance with the fault handling management method provided in this embodiment of the present invention, VIM obtains fault information of the hardware device and / or software to comprehensively process the correlated pieces of fault information, which can implement fault reporting and processing in the medium NFV. In addition, since comprehensive processing is performed on the correlated pieces of fault information, the same comprehensive fault information is deleted by detecting repeated alarms and the efficiency and accuracy of the fault processing are improved.

In FIG. 10 is an interaction diagram of a failure processing control method according to an embodiment of the present invention; The method shown in FIG. 10 may be performed by the NFV system shown in FIG. one.

1001a: VIM receives failure information.

When VIM detects that a failure has occurred somewhere in the HW, Host OS, Hypervisor or VM in the NFVI, VIM receives information about the failures of the failed NFVI device. Specifically, the received failure information may be generated to be reported to the VIM by the failed NFVI device, or may be generated in accordance with the detected failure.

Using the following methods, VIM can detect that a failure has occurred in the NFVI device.

For convenience, the following is described using an example in which the failure occurs in the first NFVI device, where the first NFVI device can be any of the following: HW, Host OS, Hypervisor or VM in NFVI, and the device may comprise a hardware device or a software device.

Method 1

When a failure occurs in the first NFVI device, the first NFVI device generates fault information, where the failure information contains at least the identifier of the failed device, which is used to uniquely identify the first NFVI device, and the actual position of the failed first NFVI device or position The failed first NFVI device in a topological relation can be uniquely determined using the identifier. The failure information further comprises a failure identifier used to uniquely identify the failure information. Failure information additionally contains the type of failure used to represent the cause of the failure, for example, a power outage, overload, or no failure. In addition, the failure information may further include an operating state and a failure time, where the operating state is used to indicate whether the first NFVI device is currently operating normally and the failure time can be used to record the time when the failure occurs. As an example, the format of the failure information can be shown in table 1.

After generating the failure information in the above format, the first NFVI can transmit the failure information to VIM using the Nf-Vi interface, and, alternatively, the first NFVI device can also, using EMS, transmit the failure information to the OSS / BSS system for control, registration and submission.

Method 2

VIM may transmit an indication message to the first NFVI device periodically or, when required, to instruct the first NFVI device to perform fault detection. If the first NFVI device detects a failure, the first NFVI device can transmit back to VIM the failure information similar to the information shown in Table 1; or, if the first NFVI device has no failure, the first NFVI device may not send back any messages, or it may send back a failure message that indicates “No fault” for the type of failure and the operating state is “Normal” ("Normal"), see table 1.

Method 3

The first NFVI device may periodically send a message with the indication "I'm alive" indicating to VIM that the first NFVI device is operating normally. VIM periodically receives “I'm Alive” messages from the first NFVI device and realizes that the first NFVI device is working properly. When I am alive from the first NFVI device is interrupted, VIM determines that a failure has occurred in the first NFVI device and that VIM can generate failure information for the first NFVI. The specific format of the failure information is similar to the failure information shown in Table 1, and no further details are again described here.

When an NFVI device cannot report failure information due to an unexpected event, such as a power outage, VIM can still understand that a failure has just occurred in the first NFVI device.

Method 4

VIM can perform failure detection on the NFVI periodically or as needed, and then VIM generates failure information of the first NFVI in accordance with the result of the failure detection. The specific format of the failure information is similar to the failure information shown in Table 1, and no further details are again described here.

In conclusion, VIM can detect the failure of the NFVI device using any of the methods listed above, and, obviously, can perform the detection by combining multiple methods, for example, combining method 1 and method 3. The NFVI device sends VIM messages “I am alive” periodically and, when a failure occurs, passes the failure information to VIM. If the NFVI device cannot report failure information due to a catastrophic failure, VIM may, due to the termination of the "I'm alive" messages, understand that a failure has occurred in the NFVI device.

1001b: VNFM receives failure information.

When the VNFM detects that a failure has occurred in any VNF device in the VNF, the VNFM receives the failure information of the failed VNF device. Specifically, the received failure information may be generated by the VNFM by the failed VIM device, or may be generated locally by the VNFM in accordance with the detected failure.

VNFM, using the following methods, can detect that a failure has occurred in the VNF device.

For convenience of description, the following is described using an example in which a failure occurs in the first VNF device, where the first VNF device may be a VNF device in the VNF and the device may be a hardware device, a software device, or any specific example.

Method 1

When a failure occurs in the first VNF device, the first VNF device generates fault information, where the failure information contains at least the identifier of the failed device, which is used to uniquely identify the first VNF device, and the actual position of the failed first VNF device or position The failed first VNF device in a topological relation can be uniquely determined using the identifier. The failure information further comprises a type of failure used to represent the cause or result of the failure. In addition, the failure information may further include an operating state and a failure time, where the operating state is used to indicate whether the first VNF is currently operating normally and the failure time can be used to record the time when the failure occurs. As an example, the format of the failure information can be shown in table 3.

After generating the failure information in the above format, the first VNF device can transmit the failure information to the VNFM using the Ve-Vnfm interface, and, alternatively, the first NFVI device can also use the vEMS to transmit the failure information to the OSS / BSS system for control registration and submission.

Method 2

The VNFM may transmit an indication message to the first VNF device periodically or as necessary to instruct the first VNF device to perform fault detection. If the first VNF device detects a failure, the first VNF device can transmit back to the VNFM failure information similar to the information shown in Table 3; or, if the first VNF device does not have a failure, the first VNF device may not send back any messages or it may send a failure message back indicating "No fault" for the type of failure and the operating state is "Normal" ("Normal"), see table 3.

Method 3

The first VNF device may periodically transmit a message with the indication "I'm alive" indicating to the VNFM that the first VNF device is operating normally. VNFM periodically receives “I'm Alive” messages from the first VNF device and realizes that the first VNF device is working properly. When the “I'm alive” messages from the first VNF device are interrupted, the VNFM determines that a failure has occurred in the first VNF device and the VNFM can generate failure information of the first VNF device. The specific format of the failure information is similar to the failure information shown in Table 3, and no further details are again described here.

When the VNF cannot communicate failure information due to an unexpected event, the VNFM can still understand that a failure has occurred in the first VNF.

Method 4

The VNFM may perform failure detection on the VNF periodically or as needed, and then the VNFM generates failure information of the first VNF in accordance with the result of the failure detection. The specific format of the failure information is similar to the failure information shown in Table 3, and no further details are again described here.

In conclusion, the VNFM can detect the failure of the VNF device using any of the above methods, and, obviously, can perform the detection by combining multiple methods, for example, combining the method 1 and method 3. The VNF device transmits to the VNFM messages "I am alive" periodically and, when a failure occurs, transmits failure information to the VNFM. If the VNF device cannot report failure information due to a catastrophic failure, the VNFM may, due to the termination of the "I'm alive" messages, understand that a failure has occurred in the VNF device.

It should be understood that steps 1001a and 1001b may be relatively separate processes or may be two related processes. In this embodiment of the present invention, two steps can be considered as two simultaneous processes, that is, this embodiment of the present invention specifically describes fault management and fault elimination in the event that correlated faults occur in the NFVI device and the VNF device.

1002a: VIM generates comprehensive failure information.

After the VIM receives the failure information transmitted by the first NFVI device, or when the VIM generates the failure information according to the failure of the first NFVI device, the VIM needs to collect the failure information of another NFVI device correlated with the first NFVI device to form a comprehensive failure information, so as to perform comprehensive processing.

Specifically, since there is a correlation between the HW, Host OS, Hypervisor, and VM devices when a failure occurs in the first NFVI device, a failure can occur in the device correlated with the first NFVI device.

In FIG. 6b shows, for example, the correlation between HW, Host OS, Hypervisor, and VM devices. For example, Host OS1, Hypervisor1, VM1, and VM2 are correlated with HW1. This means that when a failure occurs in HW1, failures can also occur in virtualized devices installed on HW1: Host OS1, Hypervisor1, VM1, and VM2.

In this case, VIM can collect the failure information reported from Host OS1, Hypervisor1, VM1 and VM2, and generate comprehensive failure information with reference to the failure information HW1. Specifically, comprehensive failure information can be generated, shown in Table 2, where the failure information format of the HW, Host OS, Hypervisor, and VM devices is similar to the format shown in Table 1.

It should be understood that the comprehensive failure information shown in Table 2 is a specific example and the device failure information that is specifically included in the comprehensive failure information is determined in accordance with the correlation. When comprehensive failure information is only being generated, the failure status can be set to “Not processed yet.”

1002b: VNFM generates comprehensive failure information.

After the VNFM receives the failure information transmitted by the first VNF device, or the VNFM generates failure information corresponding to the failure of the first VNF device, that is, after step 1001b, the VNFM can generate comprehensive failure information in accordance with the failure information of the first VNF . Alternatively, the VNFM may collect failure information of other VNF devices correlated with the first VNF device to generate comprehensive failure information so as to perform comprehensive processing.

Since there is a correlation between VNF devices when a failure occurs in the first VNF device, a failure can also occur in another VNF device correlated with the first VNF device. In FIG. 7b shows, by way of example, the correlation between VNF devices. For example, VNF1 and VNF2 are both based on VM1, that is, there is a correlation between VNF1 and VNF2. When a failure occurs in VNF1, a failure can also occur in VNF2.

In this case, the VNFM can collect the failure information reported by VNF1 and generate comprehensive failure information with reference to the VNF2 failure information. Specifically, the comprehensive failure information shown in Table 4 can be generated as follows:

The failure information formats VNF1 and VNF2 are similar to the formats of Table 3. It should be understood that the comprehensive failure information shown in Table 4 is a specific example and the device failure information that is specifically included in the comprehensive failure information is determined according to the correlation. When comprehensive failure information is only being generated, the failure status can be set to “Not processed yet.”

Similarly, steps 1002a and 1001b may be relatively separate processes or may be two related processes. In the present embodiment of the present invention, two steps can be considered as two simultaneous processes.

1003a: VIM performs detection of a repeating alarm.

After generating comprehensive failure information, VIM can locally locate the generated comprehensive failure information to determine if it is the same information. Specifically, since after a failure occurs in the NFVI device, all correlated faulty NFVI devices can report the failure information, VIM can generate multiple fragments of the same comprehensive failure information for the same failure. For example, if a failure occurs in HW1, failures also occur in Host OS1, Hypervisor1, VM1, and VM2 correlated with HW1, and Host OS1, Hypervisor1, VM1, and VM2 correlated with HW1 perform the same operation as HW1. VIM can generate multiple pieces of the same comprehensive failure information after collecting correlated failure information, in which case, VIM can only process one piece of comprehensive failure information and discard the other same comprehensive failure information. It should be understood that the same failure information refers to failure information of HW, Host OS, Hypervisor, and VM, which are partially the same, but failure conditions may be different.

Specifically, the comprehensive failure information may be backed up or discarded in accordance with the failure status of the comprehensive failure information, for example, the failure state of the comprehensive failure information that has just been generated is “Not processed yet”, repeating alarm detection is performed for comprehensive failure information and if the same comprehensive failure information is detected in which the failure state is “Being processed”, fully External failure information that has not yet been processed is discarded and comprehensive failure information in which the failure state is “Being processed” is backed up and processed.

1003b: VNFM performs a repeating alarm detection.

After generating comprehensive failure information, VNFM can locally locate the generated comprehensive failure information to determine if it is the same information. Specifically, since after a failure occurs in the VNF device, all correlated faulty VNF devices can report failure information, the VNFM can generate multiple fragments of the same comprehensive failure information for the same failure. For example, if a failure occurs in VNF1, a failure also occurs in VNF2 correlated with VNF1, and VNF2 performs the same operation as VNF1. VNFM can generate multiple fragments of the same comprehensive failure information after collecting correlated failure information, in which case VNFM can only process one piece of comprehensive failure information and discard another same comprehensive failure information. It should be understood that the same failure information refers to VNF state information, which is partially the same, and failure states may be different.

Specifically, the comprehensive failure information may be backed up or discarded in accordance with the failure status of the comprehensive failure information, for example, the failure state of the comprehensive failure information that has just been generated is “Not processed yet”, repeating alarm detection is performed for comprehensive failure information and if the same comprehensive failure information is detected in which the failure state is “Being processed”, fully External failure information that has not yet been processed is discarded and comprehensive failure information in which the failure state is “Being processed” is backed up and processed.

1004a: VIM performs a self-healing determination.

When VIM generates comprehensive failure information, VIM can first determine if the type of failure in the comprehensive failure information is the type of failure that VIM can handle.

Specifically, VIM has a failover policy, where the failover policy contains the mapping between the identifier of the failed device, the type of failure, and the method of troubleshooting. Whether processing can be performed can be decided by determining if the type of failure in comprehensive failure information exists in the failover policy. For example, the type of failure HW1 is “low performance” and the corresponding method of resolving the failure is “restart”.

In addition, when comprehensive failure information contains failure information of multiple correlated NFVI devices, VIM may, in accordance with the priorities of the NFVI devices, decide to perform a self-healing determination determined by the file type in the NFVI device failure information. The priorities are: HW> Host OS> Hypervisor> VM. For example, as shown in Table 2, when comprehensive failure information contains the failure information HW1, Host OS1, Hypervisor1, VM1 and VM2, VIM can preferably handle the failure HW1, that is, determine according to the type of failure in the failure information HW1, information such as "low performance", which can be resolved by "restart".

1004b: VNFM performs self-healing determination.

When the VNFM generates comprehensive failure information, the VNFM can first determine if the type of failure in the comprehensive failure information is the type of failure that the VNFM can handle.

Specifically, VNFM has a failover policy, where the failover policy contains the mapping between the identifier of the failed device, the type of failure, and the method of troubleshooting. Whether processing can be performed can be decided by determining if a failure type exists in the failure elimination policy corresponding to the failure to provide comprehensive failure information. For example, if VNF1 is a failure type of "low performance", then the appropriate way to eliminate the failure is to "add a VNF instance".

Specifically, the method of resolving the failure may include, in particular, one of the following methods: restarting the hardware device, rebooting the software (Host OS, Hypervisor, etc.), migrating the VM, rebooting the VNF of the VNF installation software, re-initiating the VNF , adding a VNF example, migrating a VNF (that is, reallocating resources to a VNF), and re-initiating a VNF Forwarding Graph.

1005a: VIM can perform a self-healing process.

If VIM determines that processing can be performed, VIM performs NFVI device failover in accordance with the failover method. If the failure repair is successful and the correlations of the correlated NFVI devices are resolved, the orchestrator is informed that the failure repair is successful and the process for resolving the failure ends.

If comprehensive fault information contains multiple NFVI devices and the NFVI device failure, which is preferably handled, is resolved successfully, but the failures of other correlated NFVI devices continue to exist, step 1004a is repeated to determine and eliminate the failure of the NFVI device having the highest priority among the remaining failed devices NFVI until all the NFVI devices in the comprehensive failure information are resolved. The orchestrator is then notified that the troubleshooting has completed successfully and the processing process for troubleshooting has ended.

Specifically, for comprehensive failure information that can be processed, VIM can set the troubleshooting state to “Being processed” in order to avoid reprocessing the same comprehensive failure information that is generated sequentially and in which The status is indicated as Not processed yet.

An NFVI device for which a fault has been successfully resolved can notify VIM by reporting fault information in which the operating state is indicated as “Normal” and which is similar to the fault information shown in Table 1 that the fault elimination was successful. When the failures of all correlated NFVI devices in the comprehensive failure information are resolved, VIM can set the failure status of the comprehensive failure information to “Repaired” and report the comprehensive failure information to the orchestrator using the Or-Vi interface. It should be understood that the success of troubleshooting can also be reported using a predetermined alarm, which is not limited in the present invention.

In addition, the NFVI device for which the failure is eliminated can be isolated to avoid the additional propagation of failures caused by the interaction between the failed device and another neighboring device.

1005b: VNFM can perform a self-healing process.

If the VNFM determines that processing can be performed, the VNFM performs VNF device failover in accordance with the failover method. If the failover is successful and the correlations of the correlated VNF devices are resolved, the orchestrator is notified that the failover is successful and the process for resolving the failure ends.

If comprehensive fault information contains multiple VNF devices and the failure of the VNF device, which is preferably handled, is resolved successfully, but the failures of other correlated VNF devices continue to exist, step 1004b is repeated to determine and eliminate the failures of the remaining VNF devices until they fail Failures of all VNF devices in comprehensive fault information have been resolved. The orchestrator is then notified that the troubleshooting has completed successfully and the processing process for troubleshooting has ended.

Specifically, for comprehensive failure information that can be processed, VNFM can set the troubleshooting state to be Being processed so as to avoid reprocessing the same comprehensive failure information that is generated sequentially and in which The status is indicated as Not processed yet.

A VNF device that has successfully resolved the failure can notify the VNFM that the troubleshooting was successful by reporting the failure information, in which the operating state is indicated as “Normal” and which is similar to the failure information shown in Table 3 When the failures of all correlated VNF devices in the comprehensive failure information are resolved, VNFM can set the failure status of the comprehensive failure information to be “Repaired” and report comprehensive information about the failures of the orchestra from using the Or-Vnfm interface. It should be understood that the success of troubleshooting can also be reported using a predetermined alarm, which is not limited in the present invention.

In addition, the VNF device for which the failure is eliminated can be isolated to avoid the additional propagation of failures that is caused by the interaction between the failed device and another neighboring device.

1005c: VIM cannot complete the self-healing process.

After determining in step 1005a, if the VIM failover policy does not contain the type of failure of the NFVI device for which the fault should be resolved, the VIM device requests the VNFM device information about the failure of the VNF device correlated with the first VNFI device. VIM then receives the VNF device failure information transmitted by the VNFM correlated with the first VNFI device, adds the received failure information to the original comprehensive NFVI failure information, and then reports the combined comprehensive failure information to the orchestrator using the Or-Vi interface. For example, with the correlation shown in FIG. 6a, NFVI devices correlated with HW1 are Host OS1, Hypervisor1, VM1 and VM2, and HW1 is further correlated with VNF, where VNF1 and VNF2 are also correlated with HW1. If a failure occurs in VNF1, that is, VNFM has VNF1 failure information, VNFM transmits VNF1 failure information to VIM using the Vi-Vnfm interface, so that VIM performs comprehensive processing and reporting.

1005d: VNFM can perform a self-healing process.

After determining in step 1005b, if the VNFM failover policy does not contain the type of failure of the VNF device for which the failure should be resolved, the VNFM device requests the VIM device information about the failure of the NFVI device correlated with the first VNF device. The VNFM then receives the failure information transmitted by VIM of the NFVI device correlated with the first VNF device, adds the received failure information to the original comprehensive VNF failure information, and then reports the combined comprehensive failure information to the orchestrator using the Or-Vnfm interface. For example, with the correlation shown in FIG. 6a, NFVI devices correlated with VNF1 are VM1, Host OS1, Hypervisor1, HW1, and HW2. If faults also occur in VM1, the Host OS1, the Hypervisor1 and HW1, VIM passes the fault information of VM1, Host OS1, Hypervisor1 and HW1 to the VNFM using the Vi-Vnfm interface so that VNFM performs comprehensive processing and reporting.

1006: The orchestra performs a self-healing determination.

When an orchestrator receives comprehensive failure information that is communicated through VNFM or VIM and for which comprehensive processing has been performed (1005c or 1005d), the orchestrator detects whether a self-healing process can be performed for comprehensive failure information, which is similar to the self-healing definition for VIM. The orchestrator requests a local fault resolution policy, and if the processing can be completed and the fault removal is successful, the orchestrator sets the failure state in the comprehensive failure information as “Repaired” and reports the comprehensive failure information to the OSS / BSS system; or, if the orchestrator cannot complete the troubleshooting process, or can perform the troubleshooting process, but the troubleshooting fails, the orchestrator sets the failure status in the comprehensive failure information as "Not repaired yet" and reports comprehensive information about failures of the OSS / BSS system. It should be understood that since the orchestrator is responsible for the resources of the orchestration and management and for the implementation of the NFV service, the orchestra has relatively high processing capabilities and administrative permissions and can eliminate most failures. The OSS / BSS system is only informed of a very small number of failures that cannot be handled or whose resolution fails.

1007: The OSS / BSS system performs troubleshooting.

The OSS / BSS system sets the failure state in the received comprehensive failure information as “Being processed”. The OSS / BSS system then performs the failover in accordance with the failover policy method. After the fault has been resolved, the OSS / BSS system may receive the fault rectification message sent by the NFVI and then the OSS / BSS system changes the fault state in the comprehensive fault information to “Repaired”. The OSS / BSS Failover Policy contains default methods for handling all types of failures.

In accordance with the fault handling management method provided in this embodiment of the present invention, VIM obtains fault information of the hardware device and / or software to comprehensively process the correlated pieces of fault information, which can implement fault reporting and processing in the medium NFV. In addition, since comprehensive processing is performed on the correlated pieces of fault information, the same comprehensive fault information is deleted by detecting repeated alarms and the efficiency and accuracy of the fault processing are improved.

In FIG. 11 is a block diagram of a virtualized VIM infrastructure administrator device in accordance with an embodiment of the present invention. The VIM device 1100 shown in FIG. 11, comprises a receiving unit 1101, a forming unit 1102, and a processing unit 1103.

The receiving unit 1101 obtains the first failure information containing the identifier of the failed device and the type of failure for the NFVI Network Function Virtualization Infrastructure device, where the first failure information is used to indicate that a failure has occurred in the first NFVI device having the identifier of the failed device.

The generating unit 1102 is configured to generate the first comprehensive failure information in accordance with the first failure information received by the receiving unit 1101, where the first comprehensive failure information contains first failure information and correlated failure information of the first failure information.

The processing unit 1103 is configured to eliminate the failure or process message according to the first comprehensive failure information generated by the generating unit 1102.

The VIM device 1100 provided in the present embodiment of the present invention obtains fault information of the hardware and / or software device in order to comprehensively process the correlated pieces of fault information, which can carry out fault reporting and processing in the NFV environment.

Alternatively, in an embodiment, the VIM device 1100 further comprises a determination unit and a receiving unit, and the receiving unit is specifically configured to receive, using the receiving unit, the first failure information transmitted by the first NFVI device; or determining, using the determining unit, that a failure has occurred in the first NFVI device, and generating the first failure information in accordance with the failure of the first NFVI device.

Alternatively, in the embodiment, the first NFVI device is any hardware HW hosted by the Host OS, the VM virtual machine administrator device in the NFVI device, and the generating unit 1102 is specifically configured to determine that the failure information transmitted by the NFVI device correlated with the first NFVI device, is correlated failure information of the first failure information, and the formation of the first comprehensive failure information, which contains the first information about failures and correlated failure information.

Alternatively, in an embodiment, the processing unit 1103 comprises a transmitting unit and the processing unit 1103 is specifically designed to be determined using the determination unit, and in accordance with the type of failure in the first failure information in the first comprehensive failure information or the type of failure in the correlated failure information in the first comprehensive failure information, does the VIM device 1100 contain a failure management policy that matches the type of failure in the first failure information or the type of failure in the correlated information and fault; and when the VIM contains a failover policy corresponding to the type of failure in the first failure information or the type of failure in the correlated failure information, in accordance with the failover policy, eliminate the failure in the first NFVI device and / or the failure in the NFVI device correlated with the first device NFVI; or, when the VIM device 1100 does not contain a failure elimination policy corresponding to the type of failure in the first failure information or the type of failure in the correlated failure information, transmit, using the transmitting unit, the first comprehensive failure information to the VNFM or transmit the first comprehensive failure information to the orchestra .

Alternatively, in the embodiment, the processing unit 1103 is specifically configured to determine, using the determining unit, an NFVI device having the highest priority among the first NFVI device and an NFVI device correlated with the first NFVI device, where the HW priority is higher than the Host OS priority, Host OS priority is higher than virtual machine administrator priority and virtual machine administrator priority is higher than VM priority; determining, using the determination unit and in accordance with the type of failure of the NFVI device having the highest priority, whether the VIM device 1100 contains an appropriate failover policy; and, when the VIM device 1100 contains a failover policy corresponding to the failure type of the NFVI device having the highest priority, in accordance with the failover policy, the failure of the NFVI device having the highest priority is eliminated.

Alternatively, in an embodiment, the transmitting processing unit is specifically configured to transmit, when the failure was successful, to the orchestrator of a message indicating success, or when the failure was unsuccessful, to transmit the first comprehensive failure information to the VNFM or to transmit the first comprehensive failure information to the orchestra.

Alternatively, in an embodiment, the receiving unit is further configured to receive an indication message transmitted by the VNFM, and is used to indicate that the VNFM is unable to process the first comprehensive failure information, and the transmitting unit is further configured to transmit the first comprehensive failure information to the orchestra.

Alternatively, in the embodiment, the processing unit 1103 is further configured to query the VNFM for failure information of the VNF device correlated with the first NFVI device; and adding fault information of the VNF device correlated with the first NFVI device to the first comprehensive fault information.

Alternatively, in the embodiment, the receiving unit is further configured to receive request information transmitted by the VNFM, where the request information is used to request from the VIM 1100 device failure information of the NFVI device correlated with the faulty VNF device; and the transmitting unit is further configured to transmit failure information of the NFVI device correlated with the faulty VNF device to the VNFM device.

Alternatively, in an embodiment, the VIM device 1100 further comprises a detection unit and a deletion unit, where the detection unit is specifically configured to detect, according to the first failure information, whether the VIM device 1100 contains comprehensive failure information that is the same as the first comprehensive failure information; and the deletion unit is specifically configured to: delete the first comprehensive failure information when the VIM device 1100 contains comprehensive failure information, which is the same as the first comprehensive failure information.

The VIM device 1100 provided in this embodiment of the present invention obtains fault information of the hardware and / or software device to perform comprehensive processing of the correlated pieces of fault information, which can implement fault reporting and processing in the NFV environment. In addition, since comprehensive processing is performed on the correlated pieces of fault information and the same comprehensive fault information is removed by detecting a repeating alarm, the efficiency and accuracy of the fault processing are improved.

In FIG. 12 is a block diagram of a VNFM device of a virtualized network function manager device according to an embodiment of the present invention. The VNFM 1200 device shown in FIG. 12 comprises a receiving unit 1201, a generating unit 1202, and a processing unit 1203.

Block 1201 receives the second failure information containing the identifier of the failed device and the type of failure for the VNF virtualized network functions, where the second information about the failures is used to indicate that the failure occurred in the first VNF device with the identifier of the failed device. Block 1202 generates a second comprehensive failure information corresponding to the second failure information. The processing unit 1203 performs the troubleshooting or reports the process in accordance with the second comprehensive failure information.

The VNFM device 1200 provided in this embodiment of the present invention obtains fault information of the hardware and / or software device in order to comprehensively process the correlated pieces of fault information, which can carry out fault reporting and processing in the NFV environment.

Alternatively, in an embodiment, the VNFM device 1200 further comprises a determining unit and a receiving unit, and the receiving unit is specially configured to receive, using the receiving unit, second fault information transmitted by the first VNF device; or determining, using the determining unit, that a failure has occurred in the first VNF device, and generating, using the generating unit, the second failure information in accordance with the failure of the first VNF device.

Alternatively, in an embodiment, the generating unit 1202 is specifically configured to determine, using the determining unit, that the failure information transmitted by the VNF device correlated with the first VNF device is the correlated failure information of the second failure information; and generating second comprehensive failure information containing second failure information and correlated failure information.

Alternatively, in an embodiment, the processing unit 1203 comprises a transmitting unit and the processing unit is specifically adapted to be detected using the determination unit and in accordance with the type of failure in the second failure information in the second comprehensive failure information or the type of failure in the correlated failure information in second comprehensive failure information, does the 1200 VNFM device contain a failover policy that matches the type of failure in the second failure information or the type of failure in correlated No information about failures; and, when the VNFM device 1200 contains a failure management policy corresponding to the type of failure in the second failure information or the type of failure in the correlated failure information, according to the failure management policy, the failure in the first VNF device and / or the failure in the VNF device correlated with the first NFVI device; or, when the VNFM device 1200 does not contain a failure elimination policy corresponding to the type of failure in the second failure information or the type of failure in the correlated failure information, transmit, using the transmitting unit, the second comprehensive failure information to the orchestrator.

Alternatively, in an embodiment, the transmitting unit is specifically configured to transmit to the orchestrator a message indicating success when the failure was successful, or when the failure was unsuccessful, to transmit the second comprehensive failure information to the orchestra.

Alternatively, in an embodiment, the processing unit 1203 is further configured to request information from the administrator of the virtualized VIM infrastructure about the failures of the NFVI device correlated with the first VNF device, where the NFVI device is any hardware HW hosted by the Host OS, the administrator of the virtual machine, or the device VM virtual machine in NFVI; and adding fault information of the NFVI device correlated with the first VNF device to the second comprehensive fault information.

Alternatively, in an embodiment, processing unit 1203 is further configured to receive first comprehensive failure information transmitted by VIM, where the first comprehensive failure information contains first failure information and correlated failure information of the first failure information and the first failure information is used to indications that a failure has occurred in the first NFVI device; determining whether the 1200 VNFM device contains a failover policy corresponding to the type of failure in the first failure information in the first comprehensive failure information or the type of failure in the correlated failure information in the first comprehensive failure information; and, when the VNFM device 1200 contains a failover policy corresponding to the type of failure in the first failure information or the type of failure in the correlated failure information, in accordance with the failover policy, the failure of the first NFVI device and / or the failure of the NFVI device correlated with the first device NFVI; or, when the 1200 VNFM device does not contain a failover policy corresponding to the type of failure in the first failure information or the type of failure in the correlated failure information, transmit the first comprehensive failure information to the orchestrator or transmit a VIM indication message used to indicate that the 1200 VNFM device unable to process the first comprehensive failure information so that VIM transmits the first comprehensive failure information to the orchestra.

Alternatively, in the embodiment, the processing unit 1203 is further configured to determine, in accordance with the first comprehensive failure information, the failure information of the first VNF device correlated with the first NFVI device and / or correlated with the NFVI device correlated with the first NFVI device; and adding the failure information of the first VNF device to the first comprehensive failure information so that the VNFM 1200 performs the troubleshooting or reports the process for the first comprehensive failure information.

Alternatively, in an embodiment, the VNFM device 1200 further comprises a detection unit and a deletion unit, where the detection unit is specifically configured to detect in accordance with the second failure information, whether the VNFM device 1200 contains comprehensive failure information that is the same as the second comprehensive failure information; and the deletion unit is specifically configured to delete second comprehensive failure information when the VNFM 1200 contains comprehensive failure information, which is the same as the second comprehensive failure information.

Alternatively, in the embodiment, the receiving unit is further configured to receive request information transmitted by VIM, where the request information is used to request from the VNFM device 1200 information about the failures of the VNF device correlated with the faulty NFVI device; and the transmitting unit is further configured to transmit VIM information about the failures of the VNF device correlated with the faulty NFVI device.

The VNFM device 1200 provided in this embodiment of the present invention obtains fault information of the hardware and / or software device in order to comprehensively process the correlated pieces of fault information, which can carry out fault reporting and processing in the NFV environment. In addition, since comprehensive processing is performed on the correlated pieces of fault information and the same comprehensive fault information is removed by detecting a repeating alarm, the efficiency and accuracy of the fault processing are improved.

In FIG. 13 is a block diagram of an apparatus of an Orchestrator orchestrator device according to an embodiment of the present invention. The orchestrator device 1300 shown in FIG. 12 comprises a receiving unit 1301 and a processing unit 1302.

The receiving unit 1301 receives the first comprehensive failure information transmitted by the administrator of the virtualized VIM infrastructure, where the first comprehensive failure information contains the first failure information, the first failure information contains the identifier of the failed device and the type of failure, and the first failure information is used to indicate that the failure occurred in the first device of the NFVI Network Functions Virtualization Infrastructure having a failed device identifier; and the processing unit 1302 performs troubleshooting or reports the process according to the first comprehensive failure information;

or

the receiving unit receives the second comprehensive failure information transmitted by the virtualized network function manager VNFM, where the second comprehensive failure information contains the second failure information, the second failure information contains the identifier of the failed device and the type of failure, and the second failure information is used to indicate that the failure occurred in the first VNF virtualized network function device having a failed device identifier; and the processing unit 1302 performs the troubleshooting or reports the process according to the second comprehensive failure information.

The orchestrator device 1300 provided in this embodiment of the present invention receives fault information of the hardware and / or software device from the VNFM or VIM in order to comprehensively process the correlated pieces of fault information, which can implement fault reporting and processing in the NFV environment .

Alternatively, in the embodiment, the first comprehensive fault information further comprises fault information of the NFVI device correlated with the first NFVI device and / or information of the virtualized network function device VNF correlated with the first NFVI device.

Alternatively, in the embodiment, the second comprehensive failure information further comprises failure information of the VNF device correlated with the first VNF device and / or information of the administrator device of the virtualized NFVI infrastructure correlated with the first VNF device.

Alternatively, in the embodiment, the processing unit 1302 is specifically configured to determine, according to the type of failure, in the first comprehensive failure information, whether the orchestrator device 1300 contains a failure elimination policy corresponding to the type of failure; and when the orchestrator device 1300 contains a failure-correcting policy corresponding to the type of failure, the failure of the first NFVI device and / or the failure of the NFVI device correlated with the first NFVI device is eliminated; or, when the orchestrator device 1300 does not contain a failover policy appropriate to the type of failure, the first comprehensive failure information is transmitted to the OSS / BSS operations and business support system.

Alternatively, in an embodiment, the processing unit 1302 is specifically configured to determine, according to the type of failure, in the second comprehensive failure information, whether the orchestrator device 1300 contains a failure elimination policy corresponding to the type of failure; and when the orchestrator device 1300 contains a failure-correcting policy corresponding to the type of failure, the failure of the first VNF device and / or the failure of the VNF device correlated with the first VNF device is eliminated; or, when the orchestrator device 1300 does not contain a failure-correcting policy appropriate to the type of failure, transmit second comprehensive failure information to the OSS / BSS operations and business support system.

Alternatively, in the embodiment, the processing unit 1302 is specifically configured to determine, according to the type of failure, in the first comprehensive failure information, whether the orchestrator contains a failure elimination policy corresponding to the type of failure; and, when the orchestrator device 1300 contains a failure-correcting policy corresponding to the type of failure, the failure of the first NFVI device, the failure of the NFVI device correlated with the first NFVI device, and the failure of the VNF device correlated with the first NFVI device are eliminated; or, when the orchestrator device 1300 does not contain a failure elimination policy appropriate to the type of failure, the first comprehensive failure information is transmitted to the OSS / BSS system.

Alternatively, in an embodiment, the processing unit 1302 is specifically configured to determine, according to the type of failure, in the second comprehensive failure information, whether the orchestrator device 1300 contains a failure elimination policy corresponding to the type of failure; and when the orchestrator device 1300 contains a failure-correcting policy corresponding to the type of failure, the failure of the first VNF device, the failure of the VNF device correlated with the first VNF device, and the failure of the NFVI device correlated with the first VNF device are eliminated; or, when the orchestrator device 1300 does not contain a failover policy appropriate to the type of failure, the second comprehensive failure information is transmitted to the OSS / BSS system.

Alternatively, in an embodiment, the VIM device 1300 further comprises a detection unit and a deletion unit, where the detection unit is configured to detect, in accordance with the first / second failure information, whether the orchestrator device 1300 contains comprehensive failure information that is the same as first / second comprehensive failure information; and the deletion unit is configured to delete the first / second comprehensive failure information when the orchestrator device 1300 contains comprehensive failure information, which is the same as the first / second comprehensive failure information.

The orchestrator device 1300 provided in this embodiment of the present invention receives fault information of the hardware and / or software device from the VNFM or VIM in order to comprehensively process the correlated pieces of fault information, which can implement fault reporting and processing in the NFV environment . In addition, since comprehensive processing is performed on correlated pieces of fault information and the same comprehensive fault information is deleted by detecting a repeating alarm, the efficiency and accuracy of the fault processing are improved.

In FIG. 14 is a block diagram of a VIM device according to another embodiment of the present invention; The VIM device 1400 shown in FIG. 14 comprises a processor 1401 and a memory 1402. A processor 1401 is coupled to the memory 1402 using a bus system 1403.

The memory 1402 is configured to store a command allowing the processor 1401 to perform the following operations: obtain the NFVI device first failure information of the NFVI device containing the identifier of the failed device and the type of failure, where the first failure information is used to indicate that the failure occurred in the first NFVI device, having a device failure identifier; generating the first comprehensive failure information corresponding to the first failure information, where the first comprehensive failure information contains the first failure information and the correlated failure information of the first failure information; and performing a failover or reporting the process in accordance with the first comprehensive failure information.

The VIM device 1400 provided in this embodiment of the present invention obtains fault information of a hardware and / or software device to comprehensively process correlated pieces of fault information, which can implement fault reporting and processing in an NFV environment.

In addition, the VIM device 1400 may further comprise a transmitter circuit 1404 and a receiver circuit 1405. The processor 1401 controls the operation of the VIM device 1400, and the processor 1401 can also be considered as a central processing unit (Central Processing Unit). Memory 1402 may comprise read-only memory and random access memory and provide instructions and data to processor 1401. Part of memory 1402 may further comprise non-volatile random access memory (NVRAM). The components of the VIM device 1400 are interconnected using a bus system 1403, where, in addition to the data bus, the bus system 1403 includes a power bus, a control bus, and a status signal bus. However, for clarity of description, the various tire types in the drawing are referred to as system 1403.

The method disclosed in embodiments of the present invention may be applied to a processor 1401 or implemented by a processor 1401. The processor 1401 may be an integrated circuit chip and has signal processing capability. In the implementation process, the steps of the above method can be carried out by integrated logic of hardware of the processor 1401 or in the form of software instructions. The aforementioned processor 1401 may be a universal processor, a digital signal processor (DSP), a special application integrated circuit (ASIC), a programmable logic integrated circuit (FPGA), or another programmable logic device, discrete logic or transistor logic device or discrete hardware component. The processor 1401 may implement or execute the methods, steps, and logic flow diagrams disclosed in embodiments of the present invention. A general purpose processor may be a microprocessor or any conventional processor, etc. The process steps disclosed with reference to embodiments of the present invention may be directly executed and performed by a hardware decoding processor, or may be performed and performed using a combination of hardware and software modules in decoding processor. Software modules may be present in a prevailing storage medium in a field such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory or a register. The storage medium is located in the memory 1402 and the processor 1401 reads the information in the memory 1402 and performs the steps of the above methods in combination with the hardware of the processor.

The VIM device 1400 provided in this embodiment of the present invention obtains fault information of a hardware and / or software device to comprehensively process correlated pieces of fault information, which can implement fault reporting and processing in an NFV environment. In addition, since comprehensive processing is performed on correlated pieces of fault information and the same comprehensive fault information is deleted by detecting a repeating alarm, the efficiency and accuracy of the fault processing are improved.

In FIG. 15 is a block diagram of a VNFM device according to another embodiment of the present invention; The VNFM device 1500 shown in FIG. 15 comprises a processor 1501 and a memory 1502. A processor 1501 is coupled to a memory 1502 using a bus system 1503.

Memory 1502 is configured to store a command enabling processor 1501 to perform the following operations: obtain second failure information containing the identifier of the failed device and the type of failure of the VNF device of virtualized network functions, where the second failure information is used to indicate that a failure has occurred in the first VNF device having the identifier of the failed device; generation of the second comprehensive failure information corresponding to the second failure information; and performing a failover or processing message in accordance with the second comprehensive failure information.

The VNFM device 1500 provided in this embodiment of the present invention obtains fault information of the hardware and / or software device in order to comprehensively process the correlated pieces of fault information, which can implement fault reporting and processing in the NFV environment.

In addition, the VNFM device 1500 may further comprise a transmitter circuit 1504 and a receiver circuit 1505. A processor 1501 controls the operation of the VNFM device 1500, and the processor 1501 can also be considered as a central processing unit (Central Processing Unit). Memory 1502 may include read only memory and random access memory and provide instructions and data for processor 1501. Part of memory 1502 may further comprise non-volatile random access memory (NVRAM). The components of the VNFM 1500 are interconnected using a bus system 1503, where, in addition to the data bus, the bus system 1503 includes a power bus, a control bus, and a status bus. However, for clarity of description, the various tire types in the drawing are referred to as tire system 1503.

The method disclosed in embodiments of the present invention may be applied to a processor 1501 or implemented by a processor 1501. The processor 1501 may be an integrated circuit chip and has signal processing capability. In the implementation process, the steps of the above method can be implemented through integrated logic circuits for hardware of the processor 1501 or in the form of software instructions. The aforementioned processor 1501 may be a universal processor, a digital signal processor (DSP), a special application integrated circuit (ASIC), a programmable logic integrated circuit (FPGA), or another programmable logic device, discrete logic or transistor logic device or discrete hardware component. Processor 802 may implement or execute the methods, steps, and logic flow diagrams disclosed in embodiments of the present invention. A general purpose processor may be a microprocessor or any conventional processor, etc. The process steps disclosed with reference to embodiments of the present invention may be directly executed and performed by a hardware decoding processor, or may be performed and performed using a combination of hardware and software modules in decoding processor. Software modules may be present in a prevailing storage medium in a field such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory or a register. The storage medium is located in the memory 1502 and the processor 1501 reads the information in the memory 1502 and performs the steps of the above methods in combination with the hardware of the processor.

The VNFM device 1500 provided in this embodiment of the present invention obtains fault information of the hardware and / or software device in order to comprehensively process the correlated pieces of fault information, which can perform fault reporting and processing in the NFV environment. In addition, since comprehensive processing is performed on correlated pieces of fault information and the same comprehensive fault information is deleted by detecting a repeating alarm, the efficiency and accuracy of the fault processing are improved.

In FIG. 16 is a block diagram of an orchestrator device according to another embodiment of the present invention. The orchestra device 1600 in FIG. 16 comprises a processor 1601 and a memory 1602. A processor 1601 is coupled to the memory 1602 using a bus system 1603.

The memory 1602 is configured to store a command allowing the processor 1601 to perform the following operations: receive the first comprehensive failure information transmitted by the administrator of the virtualized VIM infrastructure, where the first comprehensive failure information contains the first failure information, the first failure information contains the identifier of the failed device and type failure and the first failure information is used to indicate that a failure occurred in the first device of the network virtualization infrastructure An NFVI function with a failed device identifier and carry out the troubleshooting or reporting process according to the first comprehensive failure information; or receive, via an orchestrator, a second comprehensive failure information transmitted by the VNFM virtualized network function manager, where the second comprehensive failure information contains the second failure information, the second failure information contains the identifier of the failed device and the type of failure, and the second failure information is used to indicate that the failure occurred in the first VNF virtualized network functions infrastructure device having the identifier of the failed device; and carry out the troubleshooting or reporting process according to the second comprehensive failure information.

The orchestrator device 1600 provided in this embodiment of the present invention obtains failure information of the hardware and / or software device in order to comprehensively process the correlated pieces of failure information, which can carry out failure reporting and processing in the NFV environment.

In addition, the orchestrator device 1600 may further comprise a transmitter circuit 1604 and a receiver circuit 1605. A processor 1601 controls the operation of the orchestrator device 1600, and the processor 1601 may also be considered as a central processing unit (Central Processing Unit). The memory 1602 may comprise read-only memory and random access memory and provide instructions and data for processor 1601. Part of the memory 1602 may further comprise non-volatile random access memory (NVRAM). The components of the orchestrator device 1600 are interconnected using a bus system 1603, where, in addition to the data bus, the bus system 1603 includes a power bus, a control bus, and a status signal bus. However, for clarity of description, the various tire types in the drawing are referred to as tire system 1603.

The method disclosed in embodiments of the present invention may be applied to a processor 1601 or implemented by a processor 1601. The processor 1601 may be an integrated circuit chip and has signal processing capability. In the implementation process, the steps of the above method can be implemented through integrated logic circuits for hardware of the processor 1601 or in the form of software instructions. The aforementioned processor 1601 may be a universal processor, a digital signal processor (DSP), a special application integrated circuit (ASIC), a programmable logic integrated circuit (FPGA), or another programmable logic device, discrete logic or transistor logic device or discrete hardware component. The processor 1601 may implement or execute the methods, steps, and logic flow diagrams disclosed in embodiments of the present invention. A general purpose processor may be a microprocessor or any conventional processor, etc. The process steps disclosed with reference to embodiments of the present invention may be directly executed and performed by a hardware decoding processor, or may be performed and performed using a combination of hardware and software modules in decoding processor. Software modules may be present in a prevailing storage medium in a field such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory or a register. The storage medium is located in the memory 1602 and the processor 1601 reads the information in the memory 1602 and performs the steps of the above methods in combination with the hardware of the processor.

The orchestrator device 1600 provided in this embodiment of the present invention obtains failure information of the hardware and / or software device in order to comprehensively process the correlated pieces of failure information, which can carry out failure reporting and processing in the NFV environment. In addition, since comprehensive processing is performed on correlated pieces of fault information and the same comprehensive fault information is deleted by detecting a repeating alarm, the efficiency and accuracy of the fault processing are improved.

One skilled in the art may be aware that in combination with the examples described in the embodiments disclosed in this description, the steps of the methods and units may be implemented by electronic hardware, computer software, or a combination thereof. In order to clearly describe the interchangeability between hardware and software, the above generally described the steps and compositions of each embodiment in accordance with the functions. Whether these functions are performed through hardware or software depends on the specific applications and design limitations of the technical solutions. Specialists in the art can use various methods for implementing the described functions for each specific application, but should not assume that such implementations are beyond the scope of the present invention.

The methods or steps described in the embodiments disclosed herein may be implemented by hardware, a software program executed by a processor, or a combination thereof. The software program may be permanently present in random access memory (RAM), in memory, in read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, register, hard disk, removable disk, CD-ROM, or other form of media for storing data known in the art.

The present invention is described in detail with reference to the accompanying drawings and in combination with exemplary embodiments, but the present invention is not limited to this. Various equivalent changes or substitutions may be made by those skilled in the art in embodiments of the present invention without departing from the spirit and essence of the present invention, and modifications or substitutions should fall within the scope of the present invention.

Claims (75)

1. A method for controlling failure processing, comprising the steps of: receive through the virtualized infrastructure administrator (VIM) the first failure information containing the identifier of the failed object and the type of failure, the network function virtualization infrastructure object (NFVI), the first failure information being used to indicate that the failure occurs in the first NFVI object with the failed identifier object; form by means of VIM the first comprehensive failure information in accordance with the first failure information, the first comprehensive failure information containing the first failure information and the correlated failure information of the first failure information; and perform fault elimination through VIM or report processing in accordance with the first comprehensive failure information. 2. The method according to p. 1, in which at the stage of receiving through VIM the first information about the failures of the NFVI object containing the identifier of the failed device and the type of failure: receiving through VIM the first failure information transmitted by the first NFVI; or it is determined by VIM that the failure occurs in the first NFVI, and the first failure information is generated in accordance with the failure of the first NFVI. 3. The method of claim 1, wherein the first NFVI object is any hardware device (HW), a host operating system (Host OS), a virtual machine administrator, or a virtual machine object (VM) in an NFVI object, and during generation through VIM first comprehensive failure information in accordance with the first failure information: determining by VIM that the failure information transmitted by the NFVI correlated with the first NFVI is the correlated failure information of the first failure information; and form through VIM the first comprehensive failure information containing the first failure information and correlated failure information. 4. The method according to claim 1, in which at the execution stage by means of VIM the elimination of failures or processing messages in accordance with the first comprehensive information about the failures: determine, by VIM, in accordance with the type of failure in the first failure information in the first comprehensive failure information or the type of failure in the correlated failure information in the first comprehensive failure information, does VIM contain a failure management policy that matches the type of failure in the first failure information or type of denial of correlated denial information, and when the VIM contains a failover policy corresponding to the type of failure in the first failure information or the type of failure in the correlated failure information, eliminate through the VIM the failure of the first NFVI and / or the failure of the NFVI correlated to the first NFVI in accordance with the failover policy ; or when VIM does not contain a failure elimination policy corresponding to the type of failure in the first failure information or the type of failure in the correlated failure information, transmit the first comprehensive failure information to VNFM via VIM or transmit the first comprehensive failure information to the orchestrator. 5. The method according to p. 4, in which: at the stage of determining by VIM according to the type of failure in the first failure information in the first comprehensive failure information or the type of failure in the correlated failure information in the first comprehensive failure information, does VIM contain a failure management policy that matches the type of failure in the first information about failures or the type of failure in the correlated failure information: determine by VIM the NFVI object having the highest priority from the first NFVI object and the NFVI object correlated with the first NFVI object, wherein the HW priority is higher than the Host OS priority, the Host OS priority is higher than the virtual machine administrator priority, and the virtual machine administrator priority is higher than VM priority; determining by VIM, in accordance with the type of failure of the NFVI object having the highest priority, whether VIM contains an appropriate failover policy; and when the VIM contains a failure-correcting policy corresponding to the failure type of the NFVI object having the highest priority, VIM eliminates the failure of the NFVI-object having the highest priority in accordance with the failover policy. 6. The method according to claim 4, in which, after the step of eliminating by means of VIM the failure of the first NFVI object and / or the failure of the NFVI object correlated with the first NFVI object, in accordance with the troubleshooting policy of the first NFVI device, the method further comprises the steps of: when the failure repair is successful, transmit via VIM a message indicating success to the orchestra; or when the failover fails, transmit the first comprehensive failure information to the VNFM via VIM or transmit the first comprehensive failure information to the orchestrator. 7. The method according to claim 6, in which, after the step of transmitting to the VNFM by VIM the first comprehensive failure information, the method further comprises the steps of: receive, by VIM, an indication message transmitted by the VNFM and used to indicate that the VNFM is unable to process the first comprehensive failure information; and transmit through VIM the first comprehensive failure information to the orchestra. 8. The method according to claim 6, in which before the step of transmitting via VIM the first comprehensive information about the failures to the orchestra, the method further comprises the steps of: requesting via VIM to the VNFM the failure information of the VNF correlated with the first NFVI; and add, via VIM, the failure information of the VNF correlated with the first NFVI to the first comprehensive failure information. 9. The method according to p. 1, further comprising stages in which: receive, via VIM, the request information transmitted by the VNFM, the request information being used to request from the VIM the failure information of the NFVI correlated with the failed VNF; and transmit via VIM to the VNFM the failure information of the NFVI correlated with the failed VNF. 10. The method according to p. 1, in which, after the stage of generating by VIM the first comprehensive information about the failures in accordance with the first information about the failures, the method further comprises the steps of: detecting by VIM, in accordance with the first comprehensive failure information, whether the VIM contains comprehensive failure information matching the first comprehensive failure information; and when the VIM contains comprehensive failure information matching the first comprehensive failure information, the first comprehensive failure information is deleted by VIM. 11. The method of claim 1, wherein the first failure information is further communicated to the operations and business support system (OSS / BSS) so that the OSS / BSS monitors and provides the first failure information. 12. The method according to p. 1, in which: the first failure information contains at least the execution status or time of failure; and the first comprehensive failure information additionally contains information about the failure state, and the failure state contains at least one of the following states: not yet processed, is being processed, the failures have been resolved and the failures have not yet been resolved. 13. The administrator of the virtualized infrastructure (VIM), containing: a receiving unit configured to receive first failure information containing the identifier of the failed object and the type of failure for the network function virtualization infrastructure object (NFVI), the first failure information being used to indicate that the failure occurs in the first NFVI object having the identifier of the failed object ; a generating unit configured to generate first comprehensive failure information in accordance with the first failure information, the first comprehensive failure information containing first failure information and correlated failure information of the first failure information; and a processing unit configured to perform fault elimination or processing messages in accordance with the first comprehensive failure information. 14. VIM according to claim 13, further comprising: a receiving unit, made in particular with the possibility of receiving by the receiving unit the first failure information transmitted by the first NFVI object; or a determination unit, configured to determine that the failure occurs in the first NFVI object, and generate the first information about the failures in accordance with the failure of the first NFVI object. 15. The VIM of claim 13, wherein the first NFVI is any hardware (HW), host operating system (Host OS), virtual machine administrator, or virtual machine (VM) object in the NFVI, wherein the determination unit is made, in particular, with the possibility of determining that the failure information transmitted by the NFVI object correlated with the first NFVI object is the correlated failure information of the first failure information; but the forming unit is made, in particular, with the possibility of generating the first comprehensive information about the failures containing the first information about the failures and correlated information about the failures. 16. The VIM according to claim 13, wherein the processing unit comprises a transmitting unit, wherein the processing unit, in particular, is configured to: determining, by the determination unit and in accordance with the type of failure in the first failure information in the first comprehensive failure information or the type of failure in the correlated failure information in the first comprehensive failure information, does VIM contain a failure management policy that matches the type of failure in the first information failures or the type of failure in the correlated failure information; and eliminating, in accordance with the failure elimination policy, the failure of the first NFVI and / or the failure of the NFVI correlated with the first NFVI when the VIM contains a failure elimination policy corresponding to the type of failure in the first failure information or the type of failure in the correlated failure information; or transmitting, by the transmitting unit, the first comprehensive failure information to the VNFM, or transmitting the first comprehensive failure information to the orchestra when VIM does not contain a failure elimination policy corresponding to the type of failure in the first failure information or the type of failure in the correlated failure information. 17. VIM according to claim 16, in which the processing unit, in particular, is configured to: determining by means of a determination block of an NFVI object having the highest priority from the first NFVI object and the NFVI object correlated with the first NFVI object, wherein the HW priority is higher than the Host OS priority, the Host OS priority is higher than the virtual machine administrator priority, and the virtual machine administrator priority higher than VM priority; determining, by the determination unit and in accordance with the type of failure of the NFVI object having the highest priority, whether the VIM contains an appropriate failover policy; and in accordance with the NFVI failover mitigation policy of the highest priority, when VIM contains the failover policy corresponding to the failure type of the NFVI highest priority. 18. VIM according to claim 16, in which the transmitting unit, in particular, is configured to: transmitting a success message to the orchestrator when the failure repair was successful; or transmitting the first comprehensive failure information to the VNFM or transmitting the first comprehensive failure information to the orchestrator when the failure elimination fails. 19. VIM according to claim 18, in which the receiving unit, in particular, is configured to: receiving an indication message transmitted by the VNFM and used to indicate that the VNFM is unable to process the first comprehensive failure information; however, the transmitting unit is additionally configured to transmit the first comprehensive information about the failures to the orchestra. 20. VIM according to claim 18, in which the processing unit is further configured to: request from the VNFM information about the failures of the VNF object correlated with the first NFVI object; and adding failure information of the VNF correlated with the first NFVI to the first comprehensive failure information. 21. VIM according to claim 13, in which the receiving unit, in particular, is configured to: receiving request information transmitted by the VNFM, the request information being used to request information from the VIM about the failures of the NFVI object correlated with the failed VNF object; but the transmitting unit is further configured to transmit to the VNFM information about the failures of the NFVI object correlated with the failed VNF object. 22. VIM according to claim 13, in which the administrator further comprises a determination unit and a deletion unit, wherein the determination unit, in particular, is configured to: detecting, in accordance with the first comprehensive failure information, whether VIM contains comprehensive failure information that matches the first comprehensive failure information; but the deletion unit, in particular, is configured to delete the first comprehensive failure information when the VIM contains comprehensive failure information matching the first comprehensive failure information. 23. VIM according to claim 13, in which the first failure information contains at least the execution status or time of failure; and the first comprehensive failure information additionally contains information about the failure state, and the failure state contains at least one of the following states: not yet processed, is being processed, the failures have been resolved and the failures have not yet been resolved. 24. A computer-readable medium for storing data containing a program recorded thereon, causing the computer to execute the method according to any one of paragraphs. 1-12.

Images