Network function virtualization NFV fault management apparatus, device, and method
First Claim
1. A network function virtualization (NFV) fault management device, comprising:
- a non-transitory memory storing instructions; and
a processor in communication with the memory, wherein the processor executes the instructions to cause the NFV fault management device to perform the following steps;
receiving a fault subscription message from a subscription node in an NFV system, wherein the fault subscription message comprises fault information to which a subscription is requested by the subscription node;
receiving a fault publish message from a fault publish node in the NFV system;
generating a fault notification message according to the fault subscription message and the fault publish message; and
notifying the fault notification message to the subscription nod;
wherein the fault information to which the subscription is requested comprises at least one of;
a grouping identifier of the fault publish node, a node identifier of the fault publish node, a fault type, fault content, and a fault priority, andwherein the step of notifying the fault notification message comprises;
when at least one of fault types and fault content to which a subscription is requested by at least two subscription nodes is the same, simultaneously notifying the fault notification message to the at least two subscription nodes.
1 Assignment
0 Petitions
Accused Products
Abstract
A network function virtualization NFV fault management apparatus, device, and method are disclosed. The apparatus includes: a receiver, configured to receive a fault subscription message sent by at least one subscription node in an NFV system and a fault publish message sent by at least one fault publish node in the NFV system, where the fault subscription message includes fault information to which a subscription is requested; a processor, configured to perform matching between the fault information to which a subscription is requested and the fault publish message, and generate a fault notification message; and a transmitter, configured to notify the fault notification message to the at least one subscription node. According to the present invention, real-time and quick location and notification of node fault information can be implemented.
13 Citations
16 Claims
-
1. A network function virtualization (NFV) fault management device, comprising:
-
a non-transitory memory storing instructions; and a processor in communication with the memory, wherein the processor executes the instructions to cause the NFV fault management device to perform the following steps; receiving a fault subscription message from a subscription node in an NFV system, wherein the fault subscription message comprises fault information to which a subscription is requested by the subscription node; receiving a fault publish message from a fault publish node in the NFV system; generating a fault notification message according to the fault subscription message and the fault publish message; and notifying the fault notification message to the subscription nod; wherein the fault information to which the subscription is requested comprises at least one of;
a grouping identifier of the fault publish node, a node identifier of the fault publish node, a fault type, fault content, and a fault priority, andwherein the step of notifying the fault notification message comprises; when at least one of fault types and fault content to which a subscription is requested by at least two subscription nodes is the same, simultaneously notifying the fault notification message to the at least two subscription nodes. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. A network function virtualization (NFV) fault management method, comprising:
-
receiving a fault subscription message from a subscription node in an NFV system, wherein the fault subscription message comprises fault information to which a subscription is requested by the subscription node; receiving a fault publish message from a fault publish node in the NFV system; generating a fault notification message according to the fault subscription message and the fault publish message; and notifying the fault notification message to the subscription node, wherein the fault information to which the subscription is requested comprises at least one of;
a grouping identifier of the fault publish node, a node identifier of the fault publish node, a fault type, fault content, and a fault priority, andwherein notifying the fault notification message comprises; when at least one of fault types and fault content to which a subscription is requested by at least two subscription nodes is the same, simultaneously notifying the fault notification message to the at least two subscription nodes. - View Dependent Claims (10, 11, 12, 13, 14, 15)
-
-
16. A non-transitory computer readable medium, comprising:
-
a computer program code comprising one or more executable instructions, which, when executed by a network function virtualization (NFV) fault management device, cause the NFV fault management device to perform a method comprising; receiving a fault subscription message from a subscription node in an NFV system, wherein the fault subscription message comprises fault information to which a subscription is requested by the subscription node; receiving a fault publish message from a fault publish node in the NFV system; generating a fault notification message according to the fault subscription message and the fault publish message; and notifying the fault notification message to the subscription node, wherein the fault information to which the subscription is requested comprises at least one of;
a grouping identifier of the fault publish node, a node identifier of the fault publish node, a fault type, fault content, and a fault priority, andwherein notifying the fault notification message comprises; when at least one of fault types and fault content to which a subscription is requested by at least two subscription nodes is the same, simultaneously notifying the fault notification message to the at least two subscription nodes.
-
Specification