CN107925585B - Network service fault processing method and device - Google Patents

Abstract

The invention discloses a method and a device for processing network service faults. The method comprises the following steps: a first network function virtualization orchestrator acquires first network service fault information of a first network domain; the first network service failure information is used for describing failure information of the network service deployed in the first network domain; the first network function virtualization orchestrator acquires second network service fault information sent by the second network function virtualization orchestrator; the second network service failure information is used for describing failure information of the network service deployed in the second network domain; and the first network function virtualization orchestrator determines a root fault unit of the network service according to the first network service fault information and the second network service fault information. By adopting the method or the system, the fault of the NS deployed in a cross-domain mode can be processed through information interaction between the NFVOs.

Description

Network service fault processing method and device

Technical Field

The present invention relates to the field of network communication technologies, and in particular, to a method and an apparatus for processing a fault of a network service.

Background

Network Function Virtualization (NFV) technology is initiated by 13 major telecommunication operators worldwide, with numerous equipment vendors, IT vendors participating. By adopting the NFV technology, various types of network devices, such as servers, routers, storage devices, switches, and other devices, can be separated by a network function virtualization technology. By using NFV technology, the above-described devices can be deployed in a data center, a network node, or a user's home.

Briefly, NFV technology is primarily directed to the integration of hardware resources of various data processing capable computers in a network so that the computers can perform the functions of devices (e.g., servers, routers, storage devices, switches, etc.) in a communication network. In NFV technology, a Function carried by an entity device after virtualization may be referred to as a Virtualized Network Function (VNF). One or more VNFs may be combined into a Network Service (NS) in a particular manner.

In an actual NFV system, a device that manages virtualized Network functions may be referred to as a Network Function Virtualization Orchestrator (NFVO).

The management domain of the NFVO and the operator network domain have a certain mapping relation. For example: for operators in medium and small countries, a virtualization function and resources managed by NFVO can cover the national network of the operator; for super-large countries such as china and the united states, the managed virtualization function and resources of an NFVO can cover the network of an provincial company.

The inventor has found through research that in some application scenarios, for example, when NFV technology is adopted in an enterprise network of a global enterprise, or when a VNF of an inactive zone is selected for a VNF of a tsunami earthquake active zone region for reliable disaster recovery backup (the active zone and the inactive zone usually span different countries or span different provinces), NS needs to be deployed in different NFVO management domains. In the existing NFV technology, one NFVO can only handle the failure of the NS in the management domain of the NFVO. When the NS is deployed in a different NFVO management domain, if the NS fails, failure processing cannot be performed.

Disclosure of Invention

In view of this, the present invention provides a method and an apparatus for handling a failure of a network service, which solve a handling method when an NS fails when the NS is deployed in different NFVO management domains through information interaction between NFVOs. The specific scheme is as follows:

according to a first possible implementation manner of the first aspect of the present application, the present application provides a method for handling a failure of a network service, where the network service is deployed in at least a first network domain and a second network domain, the first network domain is a network domain managed by a first network function virtualization orchestrator, and the second network domain is a network domain managed by a second network function virtualization orchestrator; the network service is composed of at least a first virtualized network function and a second virtualized network function; the first virtualized network function is deployed in the first network domain and the second virtualized network function is deployed in the second network domain;

the method comprises the following steps:

the first network function virtualization orchestrator acquires first network service fault information of a first network domain; the first network service failure information is used for describing failure information of the network service deployed in the first network domain;

the first network function virtualization orchestrator acquires second network service fault information sent by the second network function virtualization orchestrator; the second network service failure information is used for describing failure information of the network service deployed in the second network domain;

and the first network function virtualization orchestrator determines a root fault unit of the network service according to the first network service fault information and the second network service fault information.

With reference to the second possible implementation manner of the first aspect, after determining the root cause failure unit of the network service, the method further includes:

and determining a fault recovery strategy based on the root cause fault unit.

With reference to the third possible implementation manner of the first aspect, the determining a root cause failure unit of the network service specifically includes:

determining that the root cause failure unit is a first root cause failure unit in the first network domain.

With reference to a specific implementation manner of the third possible implementation manner of the first aspect, after determining that the root cause failure unit is a first root cause failure unit in the first network domain, the method further includes:

determining a failure recovery strategy based on the first root source failure unit;

and processing the fault of the first root source fault unit by adopting the fault recovery strategy.

With reference to the fourth possible implementation manner of the first aspect, the determining a root cause failure unit of the network service specifically includes:

determining the root cause failure unit is a second root cause failure unit in the second network domain.

With reference to a specific implementation manner of the fourth possible implementation manner of the first aspect, after determining that the root failure unit is a second root failure unit in the second network domain, the method further includes:

determining a fault recovery policy based on the second root source failure unit;

and sending the fault recovery strategy to the second network function virtualization orchestrator.

With reference to any one of the six possible implementation manners of the first aspect, the fault information of the network service specifically includes:

fault information of the virtualized network function VNF, and/or fault information of the virtual link Vlink.

According to a first possible implementation manner of the second aspect of the present application, the present application provides a method for handling a failure of a network service, where the network service is deployed in at least a first network domain and a second network domain, the first network domain is a network domain managed by a first network function virtualization orchestrator, and the second network domain is a network domain managed by a second network function virtualization orchestrator; the network service is composed of at least a first virtualized network function and a second virtualized network function; the first virtualized network function is deployed in the first network domain and the second virtualized network function is deployed in the second network domain;

the method comprises the following steps:

the second network function virtualization orchestrator acquires second network service fault information; the second network service failure information is used for describing failure information of the network service deployed in the second network domain;

and the second network function virtualization orchestrator sends the second network service fault information to the first network function virtualization orchestrator.

With reference to the second possible implementation manner of the second aspect, after the sending, by the second network function virtualization orchestrator, the second network service failure information to the first network function virtualization orchestrator, the method further includes:

acquiring a fault recovery strategy fed back by the first network function virtualization orchestrator;

and processing a second root source fault unit in the second network domain by adopting the fault recovery strategy.

With reference to any one of the two possible implementation manners of the second aspect, the fault information of the network service specifically includes:

fault information of the virtualized network function VNF, and/or fault information of the virtual link Vlink.

According to a first possible implementation manner of the third aspect of the present application, the present application provides a method for handling a failure of a network service, where the network service is deployed in at least a first network domain and a second network domain, the first network domain is a network domain managed by a first network function virtualization orchestrator, and the second network domain is a network domain managed by a second network function virtualization orchestrator; the network service is composed of at least a first virtualized network function and a second virtualized network function; the first virtualized network function is deployed in the first network domain and the second virtualized network function is deployed in the second network domain;

the method comprises the following steps:

the upper-layer equipment of the first network function virtualization orchestrator and the second network function virtualization orchestrator acquires first network service fault information sent by the first network function virtualization orchestrator; the first network service failure information is used for describing failure information of the network service deployed in the first network domain;

the upper layer equipment acquires second network service fault information sent by the second network function virtualization orchestrator; the second network service failure information is used for describing failure information of the network service deployed in the second network domain;

and the upper layer equipment determines a root fault unit of the network service according to the first network service fault information and the second network service fault information.

With reference to the second possible implementation manner of the third aspect, after the determining the root fault unit of the network service, the method further includes:

and the upper-layer equipment determines a fault recovery strategy based on the root fault unit.

With reference to the third possible implementation manner of the third aspect, the determining a root cause failure unit of the network service specifically includes:

determining that the root cause failure unit is a first root cause failure unit in the first network domain.

With reference to a specific implementation manner of the third possible implementation manner of the third aspect, after determining that the root cause failure unit is the first root cause failure unit in the first network domain, the method further includes:

determining a failure recovery strategy based on the first root source failure unit;

and sending the fault recovery strategy to the first network function virtualization orchestrator.

With reference to any one of the four possible implementation manners of the third aspect, the upper layer device is specifically an operation and service support system OSS/BSS or another network function virtualization orchestrator NFVO.

With reference to any one of the four possible implementation manners of the third aspect, the fault information of the network service specifically includes:

fault information of the virtualized network function VNF, and/or fault information of the virtual link Vlink.

According to a first possible implementation manner of the fourth aspect of the present application, the present application provides a method for handling a failure of a network service, where the network service is deployed in at least a first network domain and a second network domain, the first network domain is a network domain managed by a first network function virtualization orchestrator, and the second network domain is a network domain managed by a second network function virtualization orchestrator; the network service is composed of at least a first virtualized network function and a second virtualized network function; the first virtualized network function is deployed in the first network domain and the second virtualized network function is deployed in the second network domain;

the method comprises the following steps:

the first network function virtualization orchestrator acquires first network service fault information; the first network service failure information is used for describing failure information of the network service deployed in the first network domain;

and the first network function virtualization orchestrator sends the first network service fault information to upper-layer equipment of the first network function virtualization orchestrator and the second network function virtualization orchestrator.

With reference to the second possible implementation manner of the fourth aspect, after the sending, by the first network function virtualization orchestrator, the first network service failure information to the upper device, the method further includes:

acquiring a fault recovery strategy fed back by the upper-layer equipment;

and processing the first root source fault unit in the first network domain by adopting the fault recovery strategy.

With reference to the third possible implementation manner of the fourth aspect, the upper layer device is specifically an operation and service support system OSS/BSS or another network function virtualization orchestrator NFVO.

With reference to any one of the three possible implementation manners of the fourth aspect, the fault information of the network service specifically includes:

fault information of the virtualized network function VNF, and/or fault information of the virtual link Vlink.

According to a first possible implementation manner of the fifth aspect of the present application, the present application provides a fault handling apparatus for a network service, where the network service is deployed in at least a first network domain and a second network domain, the first network domain is a network domain managed by a first network function virtualization orchestrator, and the second network domain is a network domain managed by a second network function virtualization orchestrator; the network service is composed of at least a first virtualized network function and a second virtualized network function; the first virtualized network function is deployed in the first network domain and the second virtualized network function is deployed in the second network domain;

the device comprises:

an obtaining unit, configured to obtain first network service failure information of a first network domain; the first network service failure information is used for describing failure information of the network service deployed in the first network domain;

acquiring second network service fault information sent by the second network function virtualization orchestrator; the second network service failure information is used for describing failure information of the network service deployed in the second network domain;

and the processing unit is used for determining a root fault unit of the network service according to the first network service fault information and the second network service fault information.

With reference to the second possible implementation manner of the fifth aspect, the processing unit is further configured to:

after determining a root cause failure unit of the network service, determining a failure recovery strategy based on the root cause failure unit.

With reference to the third possible implementation manner of the fifth aspect, the processing unit is specifically configured to:

determining that the root cause failure unit is a first root cause failure unit in the first network domain.

With reference to a specific implementation manner of the third possible implementation manner of the fifth aspect, the processing unit is further configured to:

determining a failure recovery policy based on a first root cause failure unit after determining that the root cause failure unit is the first root cause failure unit in the first network domain;

and processing the fault of the first root source fault unit by adopting the fault recovery strategy.

With reference to the fourth possible implementation manner of the fifth aspect, the processing unit is specifically configured to:

determining the root cause failure unit is a second root cause failure unit in the second network domain.

With reference to a specific implementation manner of the fourth possible implementation manner of the fifth aspect, the processing unit is further configured to:

determining a failure recovery policy based on a second root source failure unit in the second network domain after determining that the root source failure unit is the second root source failure unit;

the device further comprises:

a sending unit, configured to send the failure recovery policy to the second network function virtualization orchestrator.

With reference to any one of the six possible implementation manners of the fifth aspect, the fault information of the network service specifically includes:

fault information of the virtualized network function VNF, and/or fault information of the virtual link Vlink.

According to a first possible implementation manner of the sixth aspect of the present application, the present application provides a fault handling apparatus for a network service, where the network service is deployed in at least a first network domain and a second network domain, the first network domain is a network domain managed by a first network function virtualization orchestrator, and the second network domain is a network domain managed by a second network function virtualization orchestrator; the network service is composed of at least a first virtualized network function and a second virtualized network function; the first virtualized network function is deployed in the first network domain and the second virtualized network function is deployed in the second network domain;

the device comprises:

the acquisition unit is used for acquiring the second network service fault information; the second network service failure information is used for describing failure information of the network service deployed in the second network domain;

a sending unit, configured to send the second network service failure information to the first network function virtualization orchestrator by the second network function virtualization orchestrator.

With reference to the second possible implementation manner of the sixth aspect, the obtaining unit is further configured to:

after the second network service fault information is sent to the first network function virtualization orchestrator, a fault recovery strategy fed back by the first network function virtualization orchestrator is obtained;

the device further comprises:

and the processing unit is used for processing a second root source fault unit in the second network domain by adopting the fault recovery strategy.

With reference to any one of the two possible implementation manners of the sixth aspect, the fault information of the network service specifically includes:

fault information of the virtualized network function VNF, and/or fault information of the virtual link Vlink.

According to a first possible implementation manner of the seventh aspect of the present application, the present application provides a fault handling apparatus for a network service, where the network service is deployed in at least a first network domain and a second network domain, the first network domain is a network domain managed by a first network function virtualization orchestrator, and the second network domain is a network domain managed by a second network function virtualization orchestrator; the network service is composed of at least a first virtualized network function and a second virtualized network function; the first virtualized network function is deployed in the first network domain and the second virtualized network function is deployed in the second network domain;

the device comprises:

the acquiring unit is used for acquiring first network service fault information sent by the first network function virtualization orchestrator; the first network service failure information is used for describing failure information of the network service deployed in the first network domain;

acquiring second network service fault information sent by the second network function virtualization orchestrator; the second network service failure information is used for describing failure information of the network service deployed in the second network domain;

and the processing unit is used for determining a root fault unit of the network service according to the first network service fault information and the second network service fault information.

With reference to the second possible implementation manner of the seventh aspect, the processing unit is further configured to:

after determining a root cause failure unit of the network service, determining a failure recovery strategy based on the root cause failure unit.

With reference to the third possible implementation manner of the seventh aspect, the processing unit is specifically configured to:

determining that the root cause failure unit is a first root cause failure unit in the first network domain.

With reference to a specific implementation manner of the third possible implementation manner of the seventh aspect, the processing unit is further configured to:

determining a failure recovery policy based on a first root cause failure unit after determining that the root cause failure unit is the first root cause failure unit in the first network domain;

the device further comprises:

a sending unit, configured to send the failure recovery policy to the first network function virtualization orchestrator.

With reference to any one of the four possible implementation manners of the seventh aspect, the apparatus is specifically an operation and service support system OSS/BSS or another network function virtualization orchestrator NFVO.

With reference to any one of the four possible implementation manners of the seventh aspect, the fault information of the network service specifically includes:

fault information of the virtualized network function VNF, and/or fault information of the virtual link Vlink.

According to a first possible implementation manner of the eighth aspect of the present application, the present application provides a fault handling apparatus for a network service, where the network service is deployed in at least a first network domain and a second network domain, the first network domain is a network domain managed by a first network function virtualization orchestrator, and the second network domain is a network domain managed by a second network function virtualization orchestrator; the network service is composed of at least a first virtualized network function and a second virtualized network function; the first virtualized network function is deployed in the first network domain and the second virtualized network function is deployed in the second network domain;

the device comprises:

the device comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring first network service fault information; the first network service failure information is used for describing failure information of the network service deployed in the first network domain;

and the sending unit is used for sending the first network service fault information to the upper-layer equipment of the first network function virtualization orchestrator and the second network function virtualization orchestrator.

With reference to the second possible implementation manner of the eighth aspect, the obtaining unit is further configured to:

after the first network service fault information is sent to the upper layer equipment, a fault recovery strategy fed back by the upper layer equipment is obtained;

the device further comprises:

and the processing unit is used for processing the first root source fault unit in the first network domain by adopting the fault recovery strategy.

With reference to the second possible implementation manner of the eighth aspect, the obtaining unit is further configured to:

after the first network service fault information is sent to the upper layer equipment, a fault recovery strategy fed back by the upper layer equipment is obtained;

the device further comprises:

and the processing unit is used for processing the first root source fault unit in the first network domain by adopting the fault recovery strategy.

With reference to any one of the two possible implementation manners of the eighth aspect, the upper layer device is specifically an operation and service support system OSS/BSS or another network function virtualization orchestrator NFVO.

With reference to any one of the two possible implementation manners of the eighth aspect, the fault information of the network service specifically includes:

fault information of the virtualized network function VNF, and/or fault information of the virtual link Vlink.

According to the technical scheme, the fault processing method and the fault processing device for the network service acquire the fault information of the first network service of the first network domain; acquiring second network service fault information sent by the second network function virtualization orchestrator; determining a root fault unit of the network service according to the first network service fault information and the second network service fault information; the fault of the NS deployed across domains can be processed through information interaction between the NFVOs.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is a schematic architecture diagram of an NFV system according to the present application;

fig. 2 is a flowchart of a method for handling a fault of a network service according to embodiment 1 of the present application;

fig. 3 is a flowchart of a method for handling a failure of a network service according to embodiment 2 of the present application;

fig. 4 is a flowchart of embodiment 3 of a method for handling a failure of a network service according to the present application;

fig. 5 is a flowchart of a method 4 for handling a failure of a network service according to the present application;

fig. 6 is a block diagram of a fault handling apparatus embodiment 1 of the network service according to the present application;

fig. 7 is a block diagram of a fault handling apparatus embodiment 2 of the network service according to the present application;

fig. 8 is a block diagram of another embodiment 1 of a network service fault handling apparatus according to the present application;

fig. 9 is a block diagram of another embodiment 2 of a network service fault handling apparatus according to the present application;

fig. 10 is a block diagram of an apparatus for performing the fault handling method of the web service of the present application.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Fig. 1 is a schematic architecture diagram of an NFV system according to the present application. As shown in fig. 1, a Network Function Virtualization editor (NFVO) 101 is responsible for managing a domain. This domain includes an Operations Support System (OSS) 1011, a Virtualized Infrastructure Manager (VIM) 1012, and a Virtualized Network Function Manager (VNFM) 1013. The network function virtualization orchestrator 102 is responsible for managing another domain. This domain includes an operation support system 1021, a virtualization infrastructure manager 1022, and a virtualization network function manager 1023.

The network service 01 includes a virtualized network function 1, a virtualized network function 2, a virtualized network function 3, and a virtualized network function 4. The virtualized network function 1, the virtualized network function 2, and the virtualized network function 3 are deployed in a domain managed by the network function virtualization orchestrator 101, and the virtualized network function 4 is deployed in a domain managed by the network function virtualization orchestrator 102.

When the network service 01 fails, the method for processing the network service failure according to the embodiment of the present application may be used to process the network service failure.

Fig. 2 is a flowchart of a method for handling a failure of a network service according to embodiment 1 of the present application. As shown in fig. 2, the method may include:

step 201: the first network function virtualization orchestrator acquires first network service fault information of a first network domain; the first network service failure information is used for describing failure information of the network service deployed in the first network domain;

the failure of the network service is mainly caused by the failure of the unit constituting the network service. The network services typically include at least: a Virtualized Network Function (VNF) and a virtual link (Vlink). Therefore, the fault information of the network service in the embodiment of the present application may specifically include fault information of the VNF and/or fault information of the Vlink.

In general, a plurality of VNFs included in one network service interwork with each other. For example, some data may need to be processed by VNF1, VNF2, and VNF3 to obtain the output result of the network service. When any one of VNF1, VNF2, and VNF3 fails, the network service may be caused to fail. Therefore, in the embodiment of the application, the fault information of the network services in the two network domains is respectively obtained, and the root fault is analyzed and determined according to the fault information of the network services in each network domain.

Step 202: the first network function virtualization orchestrator acquires second network service fault information sent by the second network function virtualization orchestrator; the second network service failure information is used for describing failure information of the network service deployed in the second network domain;

in this embodiment, the second network function virtualization orchestrator may send the second network service fault information acquired by the second network function virtualization orchestrator to the first network function virtualization orchestrator, so that the first network function virtualization orchestrator performs comprehensive analysis on the fault information.

Step 203: and the first network function virtualization orchestrator determines a root fault unit of the network service according to the first network service fault information and the second network service fault information.

The first network service failure information and the second network service failure information may be analyzed according to a preset policy, so as to determine a root cause failure unit of the network service.

For example, when the first network service failure information indicates that neither VNF nor V L deployed in the first network domain has failed, and the second network service failure information indicates that one VNF deployed in the second network domain has failed, it may be determined that the root failure unit is the VNF of the second network domain.

To sum up, in this embodiment, first network service failure information of a first network domain is obtained; acquiring second network service fault information sent by the second network function virtualization orchestrator; determining a root fault unit of the network service according to the first network service fault information and the second network service fault information; the fault of the NS deployed across domains can be processed through information interaction between the NFVOs.

Fig. 3 is a flowchart of a method for handling a failure of a network service according to embodiment 2 of the present application. As shown in fig. 3, the method may include:

step 301: the first network function virtualization orchestrator acquires first network service fault information of a first network domain; the first network service failure information is used for describing failure information of the network service deployed in the first network domain;

step 302: acquiring second network service fault information sent by the second network function virtualization orchestrator; the second network service failure information is used for describing failure information of the network service deployed in the second network domain;

step 303: determining the root fault unit as a first root fault unit in the first network domain according to the first network service fault information and the second network service fault information;

step 304: determining a failure recovery strategy based on the first root source failure unit;

step 305: and processing the fault of the first root source fault unit by adopting the fault recovery strategy.

In this embodiment, the failure of the first root source failure unit in the first network domain may be directly handled by the first network function virtualization orchestrator.

Fig. 4 is a flowchart of a method for handling a failure of a network service according to embodiment 3 of the present application. As shown in fig. 4, the method may include:

step 401: the first network function virtualization orchestrator acquires first network service fault information of a first network domain; the first network service failure information is used for describing failure information of the network service deployed in the first network domain;

step 402: acquiring second network service fault information sent by the second network function virtualization orchestrator; the second network service failure information is used for describing failure information of the network service deployed in the second network domain;

step 403: determining the root fault unit to be a second root fault unit in the second network domain according to the first network service fault information and the second network service fault information;

step 404: determining a fault recovery policy based on the second root source failure unit;

step 405: and sending the fault recovery strategy to the second network function virtualization orchestrator.

In this embodiment, the second network function virtualization orchestrator needs to send the second network service failure information obtained by the second network function virtualization orchestrator to the first network function virtualization orchestrator, and the first network function virtualization orchestrator determines the failure recovery policy, and after receiving the failure recovery policy of the first network function virtualization orchestrator, the second network function virtualization orchestrator may use the failure recovery policy to process the failure of the second root source failure unit.

It should be noted that, in this embodiment of the application, according to the first network service failure information and the second network service failure information, a specific manner of determining a root fault unit of the network service may be as follows:

determining a business logic sequence among all the constituent units in the network service;

determining the component unit which cannot normally work in the network service according to the first network service fault information and the second network service fault information;

and determining the front-end composition unit with the most front service logic sequence in the composition units as the root fault unit.

For example, the business logic sequence in a certain network service is that the business data needs to be processed by VNF1, then by VNF2, and then by VNF3, and finally the output result is the output result of the network service. Then, when it is determined that neither VNF2 nor VNF3 is able to function normally, the VNF2 in the top order may be determined as the root cause fault unit.

Fig. 5 is a flowchart of a method 4 for handling a failure of a network service according to the present application. As shown in fig. 5, the method may include:

step 501: the upper-layer equipment of the first network function virtualization orchestrator and the second network function virtualization orchestrator acquires first network service fault information sent by the first network function virtualization orchestrator; the first network service failure information is used for describing failure information of the network service deployed in the first network domain;

in this embodiment, the upper layer device may specifically be an operation and service support system (OSS/BSS), or another Network Function Virtualization Orchestrator (NFVO).

Step 502: the upper layer equipment acquires second network service fault information sent by the second network function virtualization orchestrator; the second network service failure information is used for describing failure information of the network service deployed in the second network domain;

the fault information of the network service may specifically include:

fault information of the virtualized network function VNF, and/or fault information of the virtual link Vlink.

Step 503: and the upper layer equipment determines a root fault unit of the network service according to the first network service fault information and the second network service fault information.

In this embodiment, the first network function virtualization orchestrator and the second network function virtualization orchestrator respectively report the first network service fault information and the second network service fault information in their respective management domains to upper-layer devices of the first network function virtualization orchestrator and the second network function virtualization orchestrator, and the upper-layer devices determine a root source fault unit of the network service according to the first network service fault information and the second network service fault information.

When the upper layer device determines that the root fault unit is the first root fault unit in the first network domain, the method may further include the following step.

Step 504: determining a failure recovery strategy based on the first root source failure unit;

step 505: and sending the fault recovery strategy to the first network function virtualization orchestrator.

In this embodiment, the upper layer device is responsible for comprehensively analyzing the first network service failure information and the second network service failure information, determining a root cause failure unit, and may also be responsible for determining a failure recovery policy. After determining the failure recovery strategy, the failure recovery strategy may be sent to the network function virtualization orchestrator of the corresponding domain, and the network function virtualization orchestrator that receives the failure recovery strategy may perform failure processing on the root cause failure unit by using the failure recovery strategy.

The application also provides a fault processing device of the network service. The network service is at least deployed in a first network domain and a second network domain, the first network domain is a network domain managed by a first network function virtualization orchestrator, and the second network domain is a network domain managed by a second network function virtualization orchestrator; the network service is composed of at least a first virtualized network function and a second virtualized network function; the first virtualized network function is deployed in the first network domain and the second virtualized network function is deployed in the second network domain.

Fig. 6 is a block diagram of a network service failure processing apparatus according to embodiment 1 of the present invention. The apparatus may be a first network function virtualization orchestrator. As shown in fig. 6, the apparatus may include:

an obtaining unit 601, configured to obtain first network service failure information of a first network domain; the first network service failure information is used for describing failure information of the network service deployed in the first network domain;

acquiring second network service fault information sent by the second network function virtualization orchestrator; the second network service failure information is used for describing failure information of the network service deployed in the second network domain;

a processing unit 602, configured to determine a root cause failure unit of the network service according to the first network service failure information and the second network service failure information.

In the embodiment, first network service fault information of a first network domain is acquired; acquiring second network service fault information sent by the second network function virtualization orchestrator; determining a root fault unit of the network service according to the first network service fault information and the second network service fault information; the fault of the NS deployed across domains can be processed through information interaction between the NFVOs.

In practical applications, the processing unit 602 may further be configured to:

after determining a root cause failure unit of the network service, determining a failure recovery strategy based on the root cause failure unit.

In practical applications, the processing unit 602 may be specifically configured to:

determining that the root cause failure unit is a first root cause failure unit in the first network domain.

In practical applications, the processing unit 602 may further be configured to:

determining a failure recovery policy based on a first root cause failure unit after determining that the root cause failure unit is the first root cause failure unit in the first network domain;

and processing the fault of the first root source fault unit by adopting the fault recovery strategy.

In practical applications, the processing unit 602 may be specifically configured to:

determining the root cause failure unit is a second root cause failure unit in the second network domain.

In practical applications, the processing unit 602 may further be configured to:

determining a failure recovery policy based on a second root source failure unit in the second network domain after determining that the root source failure unit is the second root source failure unit;

the apparatus may further include:

a sending unit, configured to send the failure recovery policy to the second network function virtualization orchestrator.

In practical applications, the fault information of the network service may specifically include:

fault information of the virtualized network function VNF, and/or fault information of the virtual link Vlink.

Fig. 7 is a block diagram of a network service failure processing apparatus according to embodiment 2 of the present invention. The apparatus may be a second network function virtualization orchestrator. As shown in fig. 7, the apparatus may include:

an obtaining unit 701, configured to obtain second network service failure information; the second network service failure information is used for describing failure information of the network service deployed in the second network domain;

a sending unit 702, configured to send the second network service failure information to the first network function virtualization orchestrator by the second network function virtualization orchestrator.

In practical applications, the obtaining unit 701 may further be configured to:

after the second network service fault information is sent to the first network function virtualization orchestrator, a fault recovery strategy fed back by the first network function virtualization orchestrator is obtained;

the apparatus may further include:

and the processing unit is used for processing a second root source fault unit in the second network domain by adopting the fault recovery strategy.

In practical applications, the fault information of the network service may specifically include:

fault information of the virtualized network function VNF, and/or fault information of the virtual link Vlink.

The application also provides another fault processing device for the network service. The network service is at least deployed in a first network domain and a second network domain, the first network domain is a network domain managed by a first network function virtualization orchestrator, and the second network domain is a network domain managed by a second network function virtualization orchestrator; the network service is composed of at least a first virtualized network function and a second virtualized network function; the first virtualized network function is deployed in the first network domain and the second virtualized network function is deployed in the second network domain.

Fig. 8 is a block diagram of another embodiment 1 of a network service fault handling apparatus according to the present application. The apparatus may be an operation and service support system OSS/BSS or a network function virtualization orchestrator NFVO other than the first network function virtualization orchestrator and the second network function virtualization orchestrator. As shown in fig. 8, the apparatus may include:

an obtaining unit 801, configured to obtain first network service failure information sent by the first network function virtualization orchestrator; the first network service failure information is used for describing failure information of the network service deployed in the first network domain;

acquiring second network service fault information sent by the second network function virtualization orchestrator; the second network service failure information is used for describing failure information of the network service deployed in the second network domain;

a processing unit 802, configured to determine a root cause failure unit of the network service according to the first network service failure information and the second network service failure information.

In this embodiment, the upper layer device is responsible for comprehensively analyzing the first network service failure information and the second network service failure information, determining a root cause failure unit, and may also be responsible for determining a failure recovery policy. After determining the failure recovery strategy, the failure recovery strategy may be sent to the network function virtualization orchestrator of the corresponding domain, and the network function virtualization orchestrator that receives the failure recovery strategy may perform failure processing on the root cause failure unit by using the failure recovery strategy.

In practical applications, the processing unit 802 may further be configured to:

after determining a root cause failure unit of the network service, determining a failure recovery strategy based on the root cause failure unit.

In practical applications, the processing unit 802 may be specifically configured to:

determining that the root cause failure unit is a first root cause failure unit in the first network domain.

In practical applications, the processing unit 802 may further be configured to:

determining a failure recovery policy based on a first root cause failure unit after determining that the root cause failure unit is the first root cause failure unit in the first network domain;

the apparatus may further include:

a sending unit, configured to send the failure recovery policy to the first network function virtualization orchestrator.

In practical applications, the fault information of the network service may specifically include:

fault information of the virtualized network function VNF, and/or fault information of the virtual link Vlink.

Fig. 9 is a block diagram of another embodiment 2 of a network service fault handling apparatus according to the present application. The apparatus may be a first network function virtualization orchestrator.

The apparatus may include:

an obtaining unit 901, configured to obtain first network service failure information; the first network service failure information is used for describing failure information of the network service deployed in the first network domain;

a sending unit 902, configured to send the first network service failure information to upper-layer devices of the first network function virtualization orchestrator and the second network function virtualization orchestrator.

In practical applications, the obtaining unit 901 may be further configured to:

after the first network service fault information is sent to the upper layer equipment, a fault recovery strategy fed back by the upper layer equipment is obtained;

the apparatus may further include:

and the processing unit is used for processing the first root source fault unit in the first network domain by adopting the fault recovery strategy.

In practical applications, the upper layer device may be an operation and service support system OSS/BSS or another network function virtualization orchestrator NFVO.

In practical applications, the fault information of the network service may specifically include:

fault information of the virtualized network function VNF, and/or fault information of the virtual link Vlink.

In addition, the embodiment of the present application also provides a computing node, where the computing node may be a host server including computing capability, or a personal computer PC, or a portable computer or a terminal, and the like.

Fig. 10 is a block diagram of an apparatus for performing the fault handling method of the web service of the present application. As shown in fig. 10, the apparatus 1000 includes:

a processor (processor)1010, a communication Interface (Communications Interface)1020, a memory (memory)1030, and a bus 1040.

The processor 1010, the communication interface 1020, and the memory 1030 are in communication with each other via a bus 1040.

A processor 1010 for executing a program 1032.

In particular, the program 1032 may include program code that includes computer operating instructions.

The processor 1010 may be a central processing unit CPU, or an application specific Integrated circuit asic, or one or more Integrated circuits configured to implement embodiments of the present application.

A memory 1030 for storing a program 1032. Memory 1030 may comprise high-speed RAM memory and may also include non-volatile memory (non-volatile memory), such as at least one disk memory. The program 1032 may specifically include corresponding units in the embodiments shown in fig. 6 to fig. 9, which are not described herein again.

The embodiments in the present description are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.

Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of electronic hardware and computer software. To clearly illustrate this interchangeability of parts of hardware and software, various illustrative components and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or a combination of hardware and software depends upon the particular application and design constraints imposed on the technical solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (40)

1. A fault handling method for a network service is characterized in that the network service is deployed in at least a first network domain and a second network domain, the first network domain is a network domain managed by a first network function virtualization orchestrator, and the second network domain is a network domain managed by a second network function virtualization orchestrator; the network service is composed of at least a first virtualized network function and a second virtualized network function; the first virtualized network function is deployed in the first network domain and the second virtualized network function is deployed in the second network domain;

the method comprises the following steps:

the first network function virtualization orchestrator acquires first network service fault information of a first network domain; the first network service failure information is used for describing failure information of the network service deployed in the first network domain;

the first network function virtualization orchestrator acquires second network service fault information sent by the second network function virtualization orchestrator; the second network service failure information is used for describing failure information of the network service deployed in the second network domain;

and the first network function virtualization orchestrator determines a root fault unit of the network service according to the first network service fault information and the second network service fault information.

2. The method of claim 1, wherein after determining the root cause failure unit of the network service, further comprising:

and determining a fault recovery strategy based on the root cause fault unit.

3. The method according to claim 1, wherein the determining a root cause failure unit of the network service specifically includes:

determining that the root cause failure unit is a first root cause failure unit in the first network domain.

4. The method of claim 3, wherein the determining that the root failed unit is after a first root failed unit in the first network domain further comprises:

determining a failure recovery strategy based on the first root source failure unit;

and processing the fault of the first root source fault unit by adopting the fault recovery strategy.

5. The method according to claim 1, wherein the determining a root cause failure unit of the network service specifically includes:

determining the root cause failure unit is a second root cause failure unit in the second network domain.

6. The method of claim 5, wherein the determining the root failure unit is subsequent to a second root failure unit in the second network domain, further comprises:

determining a fault recovery policy based on the second root source failure unit;

and sending the fault recovery strategy to the second network function virtualization orchestrator.

7. The method according to any of claims 1-6, wherein the failure information of the network service specifically comprises:

fault information of the virtualized network function VNF, and/or fault information of the virtual link Vlink.

8. A fault handling method for a network service is characterized in that the network service is deployed in at least a first network domain and a second network domain, the first network domain is a network domain managed by a first network function virtualization orchestrator, and the second network domain is a network domain managed by a second network function virtualization orchestrator; the network service is composed of at least a first virtualized network function and a second virtualized network function; the first virtualized network function is deployed in the first network domain and the second virtualized network function is deployed in the second network domain;

the method comprises the following steps:

the second network function virtualization orchestrator acquires second network service fault information; the second network service failure information is used for describing failure information of the network service deployed in the second network domain;

and the second network function virtualization orchestrator sends the second network service fault information to the first network function virtualization orchestrator.

9. The method of claim 8, wherein after the second network function virtualization orchestrator sends the second network service failure information to the first network function virtualization orchestrator, further comprising:

acquiring a fault recovery strategy fed back by the first network function virtualization orchestrator;

and processing a second root source fault unit in the second network domain by adopting the fault recovery strategy.

10. The method according to any of claims 8-9, wherein the failure information of the network service specifically comprises:

fault information of the virtualized network function VNF, and/or fault information of the virtual link Vlink.

11. A fault handling method for a network service is characterized in that the network service is deployed in at least a first network domain and a second network domain, the first network domain is a network domain managed by a first network function virtualization orchestrator, and the second network domain is a network domain managed by a second network function virtualization orchestrator; the network service is composed of at least a first virtualized network function and a second virtualized network function; the first virtualized network function is deployed in the first network domain and the second virtualized network function is deployed in the second network domain;

the method comprises the following steps:

the upper-layer equipment of the first network function virtualization orchestrator and the second network function virtualization orchestrator acquires first network service fault information sent by the first network function virtualization orchestrator; the first network service failure information is used for describing failure information of the network service deployed in the first network domain;

the upper layer equipment acquires second network service fault information sent by the second network function virtualization orchestrator; the second network service failure information is used for describing failure information of the network service deployed in the second network domain;

and the upper layer equipment determines a root fault unit of the network service according to the first network service fault information and the second network service fault information.

12. The method of claim 11, wherein after determining the root cause failure unit of the network service, further comprising:

and the upper-layer equipment determines a fault recovery strategy based on the root fault unit.

13. The method according to claim 11, wherein the determining a root cause failure unit of the network service specifically includes:

determining that the root cause failure unit is a first root cause failure unit in the first network domain.

14. The method of claim 13, wherein the determining that the root failed unit is after a first root failed unit in the first network domain further comprises:

determining a failure recovery strategy based on the first root source failure unit;

and sending the fault recovery strategy to the first network function virtualization orchestrator.

15. The method according to any of the claims 11-14, characterized in that the upper layer device is in particular an operation and service support system, OSS/BSS, or another network function virtualization orchestrator, NFVO.

16. The method according to any of claims 11-14, wherein the failure information of the network service specifically comprises:

fault information of the virtualized network function VNF, and/or fault information of the virtual link Vlink.

17. A fault handling method for a network service is characterized in that the network service is deployed in at least a first network domain and a second network domain, the first network domain is a network domain managed by a first network function virtualization orchestrator, and the second network domain is a network domain managed by a second network function virtualization orchestrator; the network service is composed of at least a first virtualized network function and a second virtualized network function; the first virtualized network function is deployed in the first network domain and the second virtualized network function is deployed in the second network domain;

the method comprises the following steps:

the first network function virtualization orchestrator acquires first network service fault information; the first network service failure information is used for describing failure information of the network service deployed in the first network domain;

and the first network function virtualization orchestrator sends the first network service fault information to upper-layer equipment of the first network function virtualization orchestrator and the second network function virtualization orchestrator.

18. The method of claim 17, wherein after the first network function virtualization orchestrator sends the first network service failure information to the upper layer device, further comprising:

acquiring a fault recovery strategy fed back by the upper-layer equipment;

and processing the first root source fault unit in the first network domain by adopting the fault recovery strategy.

19. The method according to claim 17, characterized in that said upper layer device is in particular an operation and service support system OSS/BSS or another network function virtualization orchestrator NFVO.

20. The method according to any of claims 17-19, wherein the failure information of the network service specifically comprises:

fault information of the virtualized network function VNF, and/or fault information of the virtual link Vlink.

21. A device for handling a failure of a network service, wherein the network service is deployed in at least a first network domain and a second network domain, the first network domain is a network domain managed by a first network function virtualization orchestrator, and the second network domain is a network domain managed by a second network function virtualization orchestrator; the network service is composed of at least a first virtualized network function and a second virtualized network function; the first virtualized network function is deployed in the first network domain and the second virtualized network function is deployed in the second network domain;

the device comprises:

an obtaining unit, configured to obtain first network service failure information of a first network domain; the first network service failure information is used for describing failure information of the network service deployed in the first network domain;

acquiring second network service fault information sent by the second network function virtualization orchestrator; the second network service failure information is used for describing failure information of the network service deployed in the second network domain;

and the processing unit is used for determining a root fault unit of the network service according to the first network service fault information and the second network service fault information.

22. The apparatus of claim 21, wherein the processing unit is further configured to:

after determining a root cause failure unit of the network service, determining a failure recovery strategy based on the root cause failure unit.

23. The apparatus according to claim 21, wherein the processing unit is specifically configured to:

determining that the root cause failure unit is a first root cause failure unit in the first network domain.

24. The apparatus of claim 23, wherein the processing unit is further configured to:

determining a failure recovery policy based on a first root cause failure unit after determining that the root cause failure unit is the first root cause failure unit in the first network domain;

and processing the fault of the first root source fault unit by adopting the fault recovery strategy.

25. The apparatus according to claim 21, wherein the processing unit is specifically configured to:

determining the root cause failure unit is a second root cause failure unit in the second network domain.

26. The apparatus of claim 25, wherein the processing unit is further configured to:

determining a failure recovery policy based on a second root source failure unit in the second network domain after determining that the root source failure unit is the second root source failure unit;

the device further comprises:

a sending unit, configured to send the failure recovery policy to the second network function virtualization orchestrator.

27. The apparatus according to any of claims 21-26, wherein the failure information of the network service specifically comprises:

fault information of the virtualized network function VNF, and/or fault information of the virtual link Vlink.

28. A device for handling a failure of a network service, wherein the network service is deployed in at least a first network domain and a second network domain, the first network domain is a network domain managed by a first network function virtualization orchestrator, and the second network domain is a network domain managed by a second network function virtualization orchestrator; the network service is composed of at least a first virtualized network function and a second virtualized network function; the first virtualized network function is deployed in the first network domain and the second virtualized network function is deployed in the second network domain;

the device comprises:

the acquisition unit is used for acquiring the second network service fault information; the second network service failure information is used for describing failure information of the network service deployed in the second network domain;

a sending unit, configured to send the second network service failure information to the first network function virtualization orchestrator by the second network function virtualization orchestrator.

29. The apparatus of claim 28, wherein the obtaining unit is further configured to:

after the second network service fault information is sent to the first network function virtualization orchestrator, a fault recovery strategy fed back by the first network function virtualization orchestrator is obtained;

the device further comprises:

and the processing unit is used for processing a second root source fault unit in the second network domain by adopting the fault recovery strategy.

30. The apparatus according to any of claims 28-29, wherein the failure information of the network service specifically comprises:

fault information of the virtualized network function VNF, and/or fault information of the virtual link Vlink.

31. A device for handling a failure of a network service, wherein the network service is deployed in at least a first network domain and a second network domain, the first network domain is a network domain managed by a first network function virtualization orchestrator, and the second network domain is a network domain managed by a second network function virtualization orchestrator; the network service is composed of at least a first virtualized network function and a second virtualized network function; the first virtualized network function is deployed in the first network domain and the second virtualized network function is deployed in the second network domain;

the device comprises:

the acquiring unit is used for acquiring first network service fault information sent by the first network function virtualization orchestrator; the first network service failure information is used for describing failure information of the network service deployed in the first network domain;

acquiring second network service fault information sent by the second network function virtualization orchestrator; the second network service failure information is used for describing failure information of the network service deployed in the second network domain;

and the processing unit is used for determining a root fault unit of the network service according to the first network service fault information and the second network service fault information.

32. The apparatus of claim 31, wherein the processing unit is further configured to:

after determining a root cause failure unit of the network service, determining a failure recovery strategy based on the root cause failure unit.

33. The apparatus according to claim 31, wherein the processing unit is specifically configured to:

determining that the root cause failure unit is a first root cause failure unit in the first network domain.

34. The apparatus of claim 33, wherein the processing unit is further configured to:

determining a failure recovery policy based on a first root cause failure unit after determining that the root cause failure unit is the first root cause failure unit in the first network domain;

the device further comprises:

a sending unit, configured to send the failure recovery policy to the first network function virtualization orchestrator.

35. The arrangement according to any of the claims 31-34, characterized in that the arrangement is in particular an operation and service support system, OSS/BSS, or another network function virtualization orchestrator, NFVO.

36. The apparatus according to any of claims 31-34, wherein the failure information of the network service specifically comprises:

fault information of the virtualized network function VNF, and/or fault information of the virtual link Vlink.

37. A device for handling a failure of a network service, wherein the network service is deployed in at least a first network domain and a second network domain, the first network domain is a network domain managed by a first network function virtualization orchestrator, and the second network domain is a network domain managed by a second network function virtualization orchestrator; the network service is composed of at least a first virtualized network function and a second virtualized network function; the first virtualized network function is deployed in the first network domain and the second virtualized network function is deployed in the second network domain;

the device comprises:

the device comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring first network service fault information; the first network service failure information is used for describing failure information of the network service deployed in the first network domain;

and the sending unit is used for sending the first network service fault information to the upper-layer equipment of the first network function virtualization orchestrator and the second network function virtualization orchestrator.

38. The apparatus of claim 37, wherein the obtaining unit is further configured to:

after the first network service fault information is sent to the upper layer equipment, a fault recovery strategy fed back by the upper layer equipment is obtained;

the device further comprises:

and the processing unit is used for processing the first root source fault unit in the first network domain by adopting the fault recovery strategy.

39. The apparatus according to claim 37, wherein the upper layer device is specifically an operation and service support system OSS/BSS or another network function virtualization orchestrator NFVO.

40. The apparatus according to any of claims 37-39, wherein the failure information of the network service specifically comprises:

fault information of the virtualized network function VNF, and/or fault information of the virtual link Vlink.

Images