# US 10,313,183 B2 · Network function virtualization NFV fault management apparatus, device, and method > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,313,183 B2 - Document ID: US10313183B2 - Status: Granted - Kind: B2 - Application number: 15/197,114 - Filed: 2016-06-29 - Published: 2016-10-27 - Granted: 2019-06-04 - Earliest claimed: 2013-12-31 - Assignees: Huawei Technologies Co., Ltd. - Applicants: Huawei Technologies Co., Ltd. - Inventors: Anni Wei; Lei Zhu; Chunshan Xiong; Fang Yu - Web page: https://patentgrep.com/patent/US10313183B2 ## CPC - H04L 41/0686: Additional information in the notification, e.g. enhancement of specific meta-data - H04L 41/40: using virtualisation of network functions or resources, e.g. SDN or NFV entities - H04L 41/06: Management of faults, events, alarms or notifications - H04L 41/069: using logs of notifications; Post-processing of notifications - H04L 45/586: of virtual routers - H04L 67/55: Push-based network services - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## 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. ## Claims ### 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, and wherein 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. ### Claim 2 (depends on 1) The device according to claim 1, wherein the fault publish message comprises a fault type. ### Claim 3 (depends on 1) The device according to claim 1, wherein the step of notifying the fault notification message comprises: successively notifying, according to the fault priority, the fault notification message to a plurality of subscription nodes which comprises the subscription node. ### Claim 4 (depends on 1) The device according to claim 1, wherein the processor further executes the instructions to cause the NFV fault management device to perform the following step: associatively storing at least one of the fault subscription message, the fault publish message, and the fault notification message. ### Claim 5 (depends on 1) The device according to claim 1, wherein the processor further executes the instructions to cause the NFV fault management device to perform the following step: acquiring a correspondence between an identifier of a virtualized network function (VNF) subscription node and an identifier of a fault publish network function virtualization infrastructure (NFVI) from a network function virtualization orchestrator (NFVO). ### Claim 6 (depends on 5) The device according to claim 5, wherein the fault subscription message comprises a first fault subscription message, which is sent by the VNF subscription node, for requesting to subscribe to fault information of the fault publish NFVI, and wherein the fault publish message comprises a first fault publish message sent by the fault publish NFVI. ### Claim 7 (depends on 6) The device according to claim 6, wherein the step of notifying the fault notification message comprises: after the first fault subscription message and the first fault publish message are received, performing matching between the fault information to which the subscription is requested by the VNF subscription node and the first fault publish message according to the correspondence, to generate the fault notification message. ### Claim 8 (depends on 1) The device according to claim 1, wherein the step of generating the fault notification message comprises: performing matching between the fault information to which the subscription is requested by the subscription node and the fault publish message, to generate the fault notification message. ### Claim 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, and wherein 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. ### Claim 10 (depends on 9) The method according to claim 9, wherein the fault publish message comprises a fault type. ### Claim 11 (depends on 9) The method according to claim 9, wherein notifying the fault notification message comprises: successively notifying, according to the fault priority, the fault notification message to a plurality of subscription nodes which comprises the subscription node. ### Claim 12 (depends on 9) The method according to claim 9, further comprising: associatively storing at least one of the fault subscription message, the fault publish message, and the fault notification message. ### Claim 13 (depends on 9) The method according to claim 9, further comprising: acquiring a correspondence between an identifier of a virtualized network function (VNF) subscription node and an identifier of a fault publish network function virtualization infrastructure (NFVI) from a network function virtualization orchestrator (NFVO). ### Claim 14 (depends on 13) The method according to claim 13, wherein the fault subscription message comprises a first fault subscription message, which is sent by the VNF subscription node, for requesting to subscribe to fault information of the fault publish NFVI, and wherein the fault publish message comprises a first fault publish message sent by the fault publish NFVI. ### Claim 15 (depends on 14) The method according to claim 14, wherein notifying the fault notification message comprises: after the first fault subscription message and the first fault publish message are received, performing matching between the fault information to which the subscription is requested by the VNF subscription node and the first fault publish message according to the correspondence, to generate the fault notification message. ### Claim 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, and wherein 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.