WO2017066940A1 - Procédé de surveillance et dispositif de surveillance en environnement de virtualisation de réseau, et nœud de réseau - Google Patents

Procédé de surveillance et dispositif de surveillance en environnement de virtualisation de réseau, et nœud de réseau Download PDF

Info

Publication number
WO2017066940A1
WO2017066940A1 PCT/CN2015/092431 CN2015092431W WO2017066940A1 WO 2017066940 A1 WO2017066940 A1 WO 2017066940A1 CN 2015092431 W CN2015092431 W CN 2015092431W WO 2017066940 A1 WO2017066940 A1 WO 2017066940A1
Authority
WO
WIPO (PCT)
Prior art keywords
monitoring
vnf
virtualization
infrastructure management
policy
Prior art date
Application number
PCT/CN2015/092431
Other languages
English (en)
Chinese (zh)
Inventor
杨旭
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2015/092431 priority Critical patent/WO2017066940A1/fr
Priority to CN201580079532.1A priority patent/CN107534575B/zh
Publication of WO2017066940A1 publication Critical patent/WO2017066940A1/fr

Links

Images

Definitions

  • the present application relates to the field of network communications, and in particular, to a monitoring method, a monitoring device, and a network node in a network virtualization environment.
  • Network Function Virtualization refers to the implementation of some network functions in software by using industry-standard server, storage and switching equipment and virtualization technology, while automatically instantiating and flexing as needed. Operations such as migration replace the dedicated network element equipment in the traditional communication network, thereby reducing the cost of expensive equipment in network construction and operation.
  • FIG. 1 is a schematic diagram of the NFV architecture in the prior art.
  • the NFV end-to-end architecture defined in the current standard mainly includes three parts: a virtualized network function (VNF), and an NFV infrastructure (NFV).
  • VNF refers to the virtualized network function, which corresponds to the physical network function in the traditional network.
  • NFVI provides hardware and virtual resources for the entire system, consisting of hardware resources (including computing, networking, and storage), virtualization layers (virtualizing hardware resources into resource pools), and virtual resources (also divided into computing, networking, and storage). )composition.
  • MANO includes: NFV Orchestrator (NFVO), VNF Manager (VNFM) and Virtualized Infrastructure Manager (VIM).
  • NFVO is responsible for lifecycle management of network services (NS, service units composed of multiple VNFs), and orchestrate and manage resources (including hardware resources and software resources) of the entire NFV system.
  • VNFM is responsible for lifecycle management of VNF.
  • VIM is responsible for managing NFVI.
  • the Operation Support System (OSS) can manage the entire NFV system through NFVO.
  • the VNF is equipped with an Element Management System (EMS) to manage it.
  • EMS Element Management System
  • the application provides a monitoring method, a monitoring device and a network node in a network virtualization environment, which are used for solving
  • the EMS provides the service running state of the VNF
  • the overall processing time of the VNF fault is long.
  • the first aspect of the present application provides a monitoring method in a network virtualization environment, where the monitoring method includes: the network function virtualization supervision terminal acquires a monitoring policy, and the monitoring policy includes resource usage information and fault processing of the virtual network function VNF to be monitored.
  • the correspondence between the methods the network function virtualization supervision terminal forms the monitoring requirement according to the monitoring strategy, and sends the monitoring requirement to the virtualization infrastructure management terminal; the network function virtualization supervision terminal receives the virtualized infrastructure management terminal to respond to the monitoring requirement and monitors
  • the abnormality information of the VNF is sent; the network function virtualization supervision end sends a fault processing method corresponding to the abnormal information to the virtualization infrastructure management terminal or the VNF for fault processing.
  • the network function virtualization supervisory end is a network function virtualization orchestrator NFVO; the network function virtualization supervisory end is used to the virtualization infrastructure management end or
  • the fault handling method corresponding to the faulty VNF sending abnormal information includes: NFVO sends a fault processing method corresponding to the abnormal information to the virtual infrastructure management terminal or the virtual network function manager VNFM to the VNF for fault processing.
  • the network function virtualization supervision terminal includes VNFM and NFVO, and the monitoring policy further includes a number;
  • the network function virtualization supervision terminal acquires the monitoring policy, including: VNFM acquisition monitoring
  • the monitoring strategy in the policy, the processing strategy in the NFVO acquisition monitoring strategy, the monitoring strategy includes the correspondence between the number and the resource usage information of the VNF to be monitored, and the processing strategy includes the correspondence between the number and the fault handling method;
  • the virtualization supervision terminal forms monitoring requirements according to the monitoring strategy, and sends monitoring requirements to the virtualization infrastructure management terminal, including: VNFM forms monitoring requirements according to the monitoring strategy, and sends monitoring requirements to the virtualization infrastructure management terminal;
  • network function virtualization supervision terminal The abnormal information of the VNF monitored by the virtual infrastructure management terminal in response to the monitoring requirement includes: the NFVO receives the abnormal information from the VNFM, and the abnormal information is the abnormality of the VNF that is transmitted to the VNFM by the virtualized infrastructure management end response monitoring requirement.
  • the fault processing method corresponding to sending the abnormal information to the virtual infrastructure management terminal or the VNF for fault processing includes: the fault processing method corresponding to the NFVO sending the abnormal information to the virtual infrastructure management terminal or the VNF through the VNFM .
  • the network function virtualization supervision terminal is a VNFM;
  • the network function virtualization supervision terminal acquisition monitoring policy includes: the VNFM acquires a monitoring policy from the NFVO;
  • the fault handling method corresponding to the abnormality information sent by the supervisory end to the virtualization infrastructure management terminal or the VNF for fault processing includes: the VNFM sends the abnormal information corresponding to the virtual infrastructure management terminal or directly to the VNF for fault processing through the NFVO. Troubleshooting method.
  • the monitoring requirement is based on the VNF monitored in the monitoring policy
  • the resource usage information is formed.
  • the network function virtualization monitoring terminal acquiring the monitoring policy includes: network function The virtualization supervisor receives the monitoring policy delivered by the OSS; or the network function virtualization supervisor reads the monitoring policy from the network service descriptor NSD and/or the virtual network function descriptor VNFD, wherein the NSD and the VNFD are stored in the NFVO.
  • the resource usage information of the VNF that needs to be monitored includes: used by the VNF The resource indicator and the corresponding threshold and the requirement for determining the abnormality, wherein the indicator is the CPU usage, the memory usage rate, the hard disk read/write rate of the computer used by the VNF, and at least the link continuity, delay, and bandwidth occupancy of the link used by the VNF.
  • the indicator is the CPU usage, the memory usage rate, the hard disk read/write rate of the computer used by the VNF, and at least the link continuity, delay, and bandwidth occupancy of the link used by the VNF.
  • the fault processing method includes: notifying the virtualization infrastructure management end Update the network forwarding path NFP and/or notify the VNF for troubleshooting to modify its business logic.
  • the monitoring policy further includes an identification and/or a fault description of the VNF.
  • the network function virtualization supervision terminal forms a monitoring requirement according to the monitoring policy
  • sending monitoring requirements to the virtualization infrastructure management terminal includes: the network function virtualization supervision terminal forms a monitoring requirement according to the monitoring policy, and repeatedly sends the monitoring requirement to the virtualization infrastructure management terminal within a specified time.
  • the network function virtualization supervision end forms a monitoring requirement according to the monitoring policy
  • sending monitoring requirements to the virtualization infrastructure management terminal includes: the network function virtualization supervision terminal forms a monitoring requirement according to the monitoring policy, and sends a subscription request to the virtualization infrastructure management terminal, and the subscription request includes monitoring demand, monitoring time, and monitoring frequency.
  • the network function virtualization supervisor receives the abnormal information of the VNF monitored by the virtualization infrastructure management terminal in response to the monitoring requirement: the network function virtualization supervisor receives the virtualized infrastructure management terminal to respond to the subscription request, and uses the VNF to be monitored. The resource is monitored and the abnormal information of the VNF sent when the monitored information meets the requirements.
  • the network function virtualization supervision terminal forms a monitoring requirement according to the monitoring policy
  • the network function virtualization supervision terminal forms the monitoring requirement according to the monitoring strategy, and sends the monitoring requirement to the virtualization infrastructure management terminal
  • the network function virtualization supervision terminal sends the virtualization infrastructure management terminal to the virtualization infrastructure management terminal.
  • the subscription request of the association monitoring request; the abnormal information of the VNF monitored by the network function virtualization supervision terminal receiving the response of the virtualization infrastructure management terminal to the monitoring requirement includes: the network function virtualization supervision terminal receives the virtualized infrastructure management terminal to respond to the subscription request,
  • the VNF used for monitoring needs to monitor the abnormal information of the VNF sent when the monitored information meets the requirements.
  • the second aspect of the present application provides a monitoring device in an NFV environment, where the monitoring device includes: a processor and a network interface, the processor is coupled to the network interface; the processor is configured to acquire a monitoring policy, and the monitoring policy includes resources of the VNF to be monitored. The correspondence between the information and the fault handling method is used; the processor is further configured to form a monitoring requirement according to the monitoring policy, and send the monitoring requirement to the virtualization infrastructure management terminal; the processor is further configured to receive the virtualized infrastructure management end response monitoring The abnormality information of the VNF monitored is required; the processor is further configured to send a fault processing method to the virtual infrastructure management terminal or through the network interface to the VNF for fault processing.
  • the monitoring device is NFVO.
  • the monitoring device is a VNFM.
  • the monitoring requirement is based on the VNF monitored in the monitoring policy
  • the resource usage information is formed.
  • the processor configured to acquire the monitoring policy, includes: the processor is configured to use the network The interface receives the monitoring policy delivered by the OSS; or is used to read the monitoring policy from the NSD and/or the VNFD, wherein the NSD and the VNFD are stored in the NFVO.
  • the resource usage information of the VNF that needs to be monitored includes: the VNF usage resource The indicator and the corresponding threshold and the requirement for determining the abnormality, wherein the indicator is at least one of the CPU usage rate, the memory usage rate, the hard disk read/write rate, and the on/off, delay, and bandwidth occupancy of the link used by the VNF.
  • the indicator is at least one of the CPU usage rate, the memory usage rate, the hard disk read/write rate, and the on/off, delay, and bandwidth occupancy of the link used by the VNF.
  • the fault processing method includes: notifying the virtualization infrastructure management end Update the NFP and/or notify the VNF for troubleshooting to modify its business logic.
  • the third aspect of the present application provides a network node, where the network node includes: a processor, a memory, and a network interface bus, where the memory and the network interface are respectively coupled to the processor; and the memory is configured to store an operation instruction included in the supervisory program;
  • the processor is configured to invoke an operation instruction to run a monitoring program to obtain a monitoring policy, where the monitoring strategy includes a correspondence between resource usage information of the VNF to be monitored and a fault processing method; forming a monitoring requirement according to the monitoring policy, and implementing the monitoring infrastructure to the virtualized infrastructure
  • the management terminal sends the monitoring request; receives the abnormal information of the VNF detected by the virtualization infrastructure management end in response to the monitoring requirement; and sends the abnormality information corresponding to the abnormality information to the VNF for the fault processing to the virtualization infrastructure management terminal or through the network interface.
  • the supervisory program is NFVO; the processor is configured to invoke the operation instruction to run the NFVO to obtain the monitoring policy, and the monitoring policy includes the resource usage information of the VNF to be monitored.
  • the monitoring policy includes the resource usage information of the VNF to be monitored.
  • the facility management terminal sends a fault handling method corresponding to the abnormal information to the VNF for fault processing through the VNFM.
  • the monitoring program is specifically a VNFM; the processor is configured to run the VNFM to obtain a monitoring policy from the NFVO, and the monitoring policy includes a number, a resource usage of the VNF to be monitored. Correspondence between information and fault handling methods; forming monitoring requirements according to monitoring strategies, and sending monitoring requirements to the virtualization infrastructure management terminal; receiving abnormal information monitored by the virtualization infrastructure management terminal in response to monitoring requirements; The virtualization infrastructure management terminal sends a fault handling method corresponding to the abnormal information directly to the VNF for fault processing through the network interface.
  • the network function virtualization supervision end obtains the resource usage information of the VNF when the VNF may be in a service failure, and the monitoring policy of the fault processing method for solving the service failure, and notifies the virtualization infrastructure management terminal to the VNF according to the monitoring policy.
  • the resources used are monitored; when abnormal information is detected, the corresponding fault handling method is processed, so that the detection and processing of the VNF service fault can be completed without reporting the OSS without the EMS, and the fault processing efficiency is improved. Reduce the business impact of failures.
  • FIG. 1 is an architectural diagram of an NFV in the prior art
  • FIG. 2 is a flow chart of a first embodiment of a monitoring method of the present application
  • FIG. 3 is a structural timing diagram of a second embodiment of the monitoring method of the present application.
  • FIG. 4 is a structural timing diagram of a third embodiment of the monitoring method of the present application.
  • FIG. 5 is a structural timing diagram of a fourth embodiment of the monitoring method of the present application.
  • FIG. 6 is a schematic diagram of processing a fault by updating an NFP in an embodiment of a monitoring method of the present application
  • FIG. 7 is a schematic diagram of processing a fault in a manner of notifying a VNF for fault handling to modify its business logic in one embodiment of the monitoring method of the present application;
  • FIG. 8 is a flowchart of sending a monitoring requirement to a VIM in an active acquisition manner in an embodiment of the monitoring method of the present application
  • FIG. 9 is a flowchart of sending a monitoring requirement to a VIM in a subscription notification manner in an embodiment of the monitoring method of the present application.
  • FIG. 10 is a flowchart of sending a monitoring requirement to a VIM in a subscription notification manner in another embodiment of the monitoring method of the present application;
  • FIG. 11 is a schematic structural diagram of a first embodiment of a monitoring apparatus of the present application.
  • Figure 12 is a schematic structural view of a second embodiment of the monitoring device of the present application.
  • Figure 13 is a schematic structural view of a third embodiment of the monitoring device of the present application.
  • Figure 14 is a schematic structural view of a fourth embodiment of the monitoring device of the present application.
  • Figure 15 is a schematic structural view of a fifth embodiment of the monitoring device of the present application.
  • Figure 16 is a schematic structural view of a sixth embodiment of the monitoring device of the present application.
  • FIG. 17 is a schematic structural diagram of a first embodiment of a network node according to the present application.
  • FIG. 18 is a schematic structural diagram of a second embodiment of a network node according to the present application.
  • FIG. 19 is a schematic structural diagram of a third embodiment of a network node according to the present application.
  • FIG. 2 is a flowchart of a first embodiment of a monitoring method of the present application.
  • the first embodiment of the monitoring method of the present application is described from the perspective of a network function virtualization supervision terminal, and the monitoring method includes the following steps:
  • the network function virtualization supervisor acquires a pre-configured monitoring policy.
  • the monitoring strategy includes the correspondence between the resource usage information of the VNF to be monitored and the fault handling method.
  • the resource usage information of the VNF includes: an operation indicator of the resource used by the VNF and an indicator threshold when a service failure may occur, and the fault processing method is a method for solving the service failure.
  • the network function virtualization supervision terminal may be dedicated hardware or a management program, which is not limited herein.
  • S202 Form a monitoring requirement according to the monitoring policy, and send a monitoring requirement to the virtualization infrastructure management end.
  • the virtualization infrastructure management terminal refers to a VIM.
  • monitoring requirements are based on resource usage information of VNFs that need to be monitored in the monitoring strategy.
  • a VNF can run on a virtual machine; or a VNF includes at least two virtual network function components (VNF Components, VNFC), each running on a virtual machine.
  • VNF Components VNFC
  • the resources used by the VNF may refer to virtual resources used by the VNF or VNFC, or may refer to corresponding hardware resources.
  • the resources used by the VNF are monitored by VIM.
  • the VIM responds to the monitoring requirements and monitors the resources used by the VNF.
  • the abnormal information is sent to the network function virtualization supervision terminal.
  • S204 Send a fault processing method corresponding to the abnormal information to the virtualization infrastructure management terminal or the VNF for fault processing.
  • the VNF used for fault handling is not an abnormal VNF.
  • the service fault that may occur in the VNF and the resource abnormality used in the fault are associated in advance, and the corresponding service fault processing method is given, and the resource information used in the VNF may be faulty and the corresponding fault processing method is performed.
  • the association is stored in the monitoring policy.
  • the network function virtualization supervisor acquires the monitoring policy and notifies the virtualization infrastructure management terminal to monitor the resources used by the VNF according to the monitoring policy; when the abnormal information is detected, the corresponding fault processing method is processed, so that there is no EMS.
  • the VNF service fault monitoring and processing can be completed without reporting the OSS, improving the fault handling efficiency and reducing the business impact caused by the fault.
  • FIG. 3 is a structural timing diagram of a second embodiment of the monitoring method of the present application.
  • the second embodiment of the monitoring method of the present application is based on the first embodiment of the monitoring method of the present application, and is implemented by NFVO31.
  • the network function virtualization supervision terminal is responsible for monitoring and processing VNF faults.
  • the NFVO 31 can receive and save the monitoring policy delivered by the OSS 30, or read the monitoring policy from the Network Service Descriptor (NSD) 311 and/or the Virtualized Network Function Descriptor (VNFD) 312.
  • the NSD311 includes information such as VNF information and link information constituting the network service, dependencies between the VNFs, parameters to be monitored by the VNF runtime, and monitoring policies of the VNF.
  • VNFD312 includes information such as VNF composition, monitoring parameters, deployment specifications, and VNF monitoring policies.
  • NSD311 and VNFD 312 are stored in NFVO31.
  • VNFD312 is open to VNFM32 and can be read by VNFM32.
  • NFVO31 forms monitoring requirements according to the monitoring strategy and sends the monitoring requirements to VIM33; VIM33 responds to the monitoring requirements and sends the detected abnormal information to NFVO31; NFVO31 checks the monitoring strategy after receiving the abnormal information. Find the fault handling method corresponding to the exception information. Since the NFVO31 cannot directly connect to the NFV34 in the existing NFV architecture, the NFVO31 needs to send a fault handling method to the VNF34 for fault handling through the VNFM32 to solve the abnormality, or directly send a fault handling method to the VIM33 to solve the abnormality.
  • FIG. 4 is a structural timing diagram of a third embodiment of the monitoring method of the present application.
  • the third embodiment of the monitoring method of the present application is based on the first embodiment of the monitoring method of the present application, and is based on NFVO41 and
  • the VNFM42 is combined as a network function virtualization supervisor to monitor and process VNF faults. Among them, VNFM42 is responsible for fault monitoring, and NFVO41 is responsible for fault handling.
  • NFVO41 can receive the monitoring policy delivered by OSS40, and then forward the monitoring policy in the monitoring policy to VNFM42, which only saves the processing policy, VNFM42 saves the received monitoring policy; or NFVO41 reads the monitoring policy from NSD411, and then monitors the policy.
  • the monitoring policy is forwarded to VNFM42, which stores the received monitoring strategy; or NFVO41 reads the processing strategy from NSD411 and/or VNFD412, and VNFM42 reads the monitoring policy from VNFD412.
  • the monitoring strategy further includes a numbering, the monitoring strategy includes a number and a corresponding resource usage information of the VNF to be monitored, and the processing strategy includes a number and a corresponding fault handling method.
  • the VNFM42 generates monitoring requirements based on the monitoring strategy and sends monitoring requirements to the VIM 43; the VIM 43 responds to the monitoring request to send the detected abnormal information to the VNFM 42; the VNFM 42 forwards the abnormal information to the NFVO 41.
  • the NFVO 41 receives the abnormal information forwarded by the VNFM 42 and searches for a corresponding fault processing method in the processing strategy.
  • the NFVO 41 directly sends a fault processing method to the VIM 43 or sends a fault processing method to the VNF 44 through the VNFM 42 to resolve the abnormality.
  • FIG. 5 is a structural sequence diagram of a fourth embodiment of the monitoring method of the present application.
  • the fourth embodiment of the monitoring method of the present application is based on the first embodiment of the monitoring method of the present application, and is implemented by VNFM52.
  • the network function virtualization supervision terminal is responsible for monitoring and processing VNF faults.
  • the VNFM52 can receive the monitoring policy forwarded by the NFVO51 and save the monitoring policy sent by the NFVO 51 by receiving the monitoring policy delivered by the OSS 50 or the monitoring policy read from the NSD 511.
  • the VNFM 52 can also read the monitoring policy from the VNFD 512.
  • the VNFM52 generates monitoring requirements according to the monitoring policy and sends the monitoring requirements to the VIM53.
  • the VIM53 responds to the monitoring requirements and sends the detected abnormal information to the VNFM52.
  • the VNFM52 searches for the fault handling method corresponding to the abnormal information in the monitoring policy.
  • the VNFM 52 can send a fault handling method to the VIM 53 via the NFVO 51, or directly send a fault handling method to the VNF 54 for fault handling.
  • the second embodiment to the fourth embodiment respectively describe the combination of NFVO, NFVO, and VNFM, and the VNFM serves as a virtualization function of the network function virtualization, and is responsible for monitoring and processing the VNF fault.
  • NFVO, VNFM, VIM points Not an integral part of MANO. It can be seen that MANOs including NFVO, VNFM, and VIM can perform closed-loop processing of VNF faults, including fault discovery, correlation, and processing.
  • the resource usage information of the VNF to be monitored includes: an indicator of the VNF usage resource, a corresponding threshold, and a requirement for determining an abnormality.
  • the VNF resource usage indicator is at least one of the CPU usage rate, the memory usage rate, the hard disk read/write rate, and the on/off, delay, and bandwidth occupancy of the link used by the VNF.
  • the CPU usage, memory usage, and hard disk read/write rate of the computer used by the VNF may be the operational indicators of the virtual machine used by the VNF or VNFC, or may be the operational indicators of the actual computer corresponding to the virtual machine.
  • the on/off, delay, and bandwidth usage of the link used by the VNF may be an operation indicator of a link between the current VNF and other VNFs, or may be an operation indicator of a link between different VNFCs within the current VNF.
  • the threshold is a threshold for determining the corresponding indicator of the monitored VNF failure.
  • the value of the indicator can be defined as 1 and 0, 1 for connectivity, 0 for disconnection, or vice versa, threshold is also 1 or 0.
  • the requirement for determining the abnormality refers to the relationship between the value of the monitored indicator and the corresponding threshold, and determines that the VNF has a service failure.
  • the given monitoring indicator is the CPU occupancy rate
  • the threshold is 80%
  • the requirement is greater than
  • the number of indicators to be monitored is at least two
  • the requirement to determine the anomaly also includes the logical relationship (and, or, and) between the different indicators. This embodiment can be combined with any of the above embodiments.
  • the fault processing method includes: notifying the virtualization infrastructure management terminal to update a Network Forwarding Path (NFP) and/or notifying the VNF for fault processing to modify its business logic.
  • NTP Network Forwarding Path
  • the NS is composed of multiple VNFs.
  • One service of the NS can be completed by using several VNFs.
  • the VNFs are linked by virtual links (VL links), and each VNF has several connection points (Connection Point, CP) is used to link with other VNFs.
  • VL links virtual links
  • CP Connection Point
  • NFP specifies the characteristics of a certain traffic flow (such as the value of the packet header) and its forwarding path. In the present application, the primary concern is the forwarding path defined by the NFP, that is, the forwarding path actually passed by the data flow during the service running, and the forwarding path is described by the passed CP.
  • FIG. 6 is a schematic diagram of processing a fault by updating an NFP in an embodiment of the monitoring method of the present application.
  • the NFP2 in the figure is the alternate path of the NFP1
  • the fault of the VNF2 can be solved by migrating the service flow of the NFP1 to the NFP2. This can be done by updating NFP. Since NFP is part of NS, updating NFP requires NFVO to modify the NFP description in NS and notify VIM to modify the underlying logic to implement the actual NFP update.
  • NFVO modifies NFP1: CP11, CP13, CP21, CP22, CP41, CP43 to NFP2: CP11, CP12, CP31, CP32, CP41, CP43, and then notifies VIM to update NFP, and completes switching backup VNF.
  • FIG. 7 is a schematic diagram of processing a fault in a manner of notifying a VNF for fault handling to modify its business logic in one embodiment of the monitoring method of the present application.
  • the VNF5 for fault handling is a virtual network element with similar packet distribution function, it can determine the direction of the data packet flowing through it. Then, the VNF5 can be solved by notifying the VNF5 to modify the service logic. That is, VNF5 is notified to migrate the data forwarding path from the failed VNF6 to the backup VNF7, and the data forwarding path is changed from VNF5->VNF6->VNF 8 to VNF 5->VNF 7->VNF 8.
  • NFVO cannot directly connect to VNF5, so it is necessary to notify VNF5 through VNFM.
  • the monitoring policy further includes a corresponding VNF identification and/or fault description.
  • the VNF identification and fault description can facilitate the viewing and management of the monitoring strategy, and its presence does not affect the monitoring and processing of VNF faults.
  • the monitoring requirements formed according to the monitoring policy may further include a corresponding VNF identifier and/or fault description in addition to the resource usage information including the number and the VNF to be monitored. This embodiment can be combined with any of the above embodiments.
  • the monitoring strategy can also include a number.
  • Table 1 is an example table of monitoring policies in an embodiment of the monitoring method of the present application.
  • the content of the monitoring policy in Table 1 is only an indication, and is not necessarily related to the actual monitoring strategy that may exist.
  • the monitoring policy in Table 1 includes the number, corresponding VNF identifier, and fault description, and may include only one or none of them.
  • FIG. 8 is a flowchart of sending a monitoring requirement to a VIM in an active manner in an embodiment of the monitoring method of the present application.
  • the network function virtualization supervision terminal takes the initiative.
  • the way of obtaining sends monitoring requirements to VIM includes the following steps: S801: forming a monitoring requirement according to the monitoring policy; and S802: repeatedly transmitting the monitoring requirement to the virtualization infrastructure management end within a specified time.
  • the VIM monitors the VNF resource to be monitored, and sends the abnormal information to the network function virtualization supervision terminal when the abnormality is detected. When no abnormality is detected, only the abnormal information is sent. It is also possible to directly send the monitored information to the network function virtualization supervision terminal, and the network function virtualization supervision terminal determines whether it is different. Frequent information.
  • This embodiment can be combined with any of the above embodiments.
  • FIG. 9 is a flowchart of sending a monitoring requirement to a VIM in a subscription notification manner in an embodiment of the monitoring method of the present application.
  • the network function virtualization supervision terminal subscribes The way the notification is sent to the VIM to monitor the demand. Specifically, the following steps are included:
  • S902 Send a subscription request to the virtualization infrastructure management terminal, where the subscription request includes monitoring requirements, monitoring time, and monitoring frequency.
  • S903 Receive an exception information of the VNF actively sent by the virtualization infrastructure management terminal in response to the subscription request to detect an abnormality.
  • the VIM responds to the subscription request and monitors the resources used by the VNF to be monitored according to the monitoring frequency during the monitoring time.
  • the monitored information meets the requirements, that is, when the VNF is abnormal, the virtual function is actively activated to the network function by means of notification.
  • the supervisor sends the abnormal information of the VNF, and the network function virtualization supervisor receives the abnormal information.
  • the abnormal information includes resource usage information of the VNF to be monitored.
  • FIG. 10 is a flowchart of sending a monitoring requirement to a VIM in a subscription notification manner in another embodiment of the monitoring method of the present application.
  • a network function virtualization supervision terminal is provided. Send monitoring requests to VIM in the form of subscription notifications. Specifically, the following steps are included:
  • S1001 Form monitoring requirements according to the monitoring strategy, and send monitoring requirements to the proposed infrastructure management terminal
  • Monitoring requirements can further include monitoring frequency.
  • the subscription request is used to select the notification that you want to subscribe to, including at least one of the resource object to be subscribed to, the notification type, and the notification parameters.
  • the subscription request can be associated with the monitoring requirement by associating the resource object with the VNF usage resource that needs to be monitored in the monitoring requirement, and/or associating the notification parameter with the VNF usage resource information in the monitoring requirement that needs to be monitored. .
  • S1003 Receive the abnormal information of the VNF actively sent by the virtualization infrastructure management terminal in response to the subscription request to detect an abnormality
  • the VIM responds to the subscription request and monitors the resources used by the VNF to be monitored according to the monitoring frequency during the monitoring time.
  • the monitored information meets the requirements, that is, when the VNF is abnormal, the virtual function is actively activated to the network function by means of notification.
  • the supervisor sends the abnormal information of the VNF, and the network function virtualization supervisor receives the abnormal information.
  • the abnormal information includes resource usage information of the VNF to be monitored.
  • FIG. 11 is a schematic structural diagram of a first embodiment of a monitoring apparatus of the present application.
  • the first embodiment of the monitoring apparatus of the present application may be used to implement the first embodiment of the monitoring method of the present application.
  • An embodiment includes:
  • the obtaining module 101 is configured to obtain a pre-configured monitoring policy.
  • the monitoring strategy includes the correspondence between the resource usage information of the VNF to be monitored and the fault handling method.
  • the resource usage information of the VNF includes: an operation indicator of the resource used by the VNF and an indicator threshold when a service failure may occur, and the fault processing method is a method for solving the service failure.
  • the monitoring policy issued by the OSS can be received and saved by the NFVO, and the monitoring policy can also be read from the NSD and/or VNFD in the NFVO.
  • the monitoring module 102 is configured to form a monitoring requirement according to the monitoring policy, and send the monitoring requirement to the virtualization infrastructure management end.
  • the monitoring requirements are formed based on the resource usage information of the VNFs that need to be monitored in the monitoring strategy.
  • the virtualization infrastructure management side refers to the VIM110.
  • the resources used by the VNF refer to the virtual resources or corresponding hardware resources used by the VNF.
  • the resources used by the VNF are monitored by the VIM 110.
  • the receiving module 103 is configured to receive the abnormal information of the VNF detected by the virtualization infrastructure management end in response to the monitoring requirement.
  • the solution module 104 is configured to send a fault processing method to the virtualization infrastructure management terminal or the VNF 120 for fault processing.
  • the fault processing method corresponding to the abnormal information is searched in the monitoring policy, the fault processing method is sent to the VIM 110 or the VNF 120 for fault processing.
  • the abnormality is solved by switching backups and skipping the abnormal VNF.
  • the VNF 120 used for fault handling is not an abnormal VNF.
  • the service fault that may occur in the VNF and the resource abnormality used in the fault are associated in advance, and the corresponding service fault processing method is given, and the resource information used in the VNF may be faulty and the corresponding fault processing method is performed.
  • the association is stored in the monitoring policy.
  • the monitoring device acquires the monitoring policy and notifies the virtualization infrastructure management terminal to monitor the resources used by the VNF according to the monitoring policy.
  • the processing is performed according to the corresponding fault processing method, so that the OSS need not be reported without the EMS.
  • the VNF service faults can be monitored and processed to improve fault handling efficiency and reduce the business impact of faults.
  • the second embodiment of the monitoring device of the present application is based on the first embodiment of the monitoring device of the present application, and the NFVO is used as the monitoring device.
  • the second embodiment of the monitoring device of the present application can be used to implement the second embodiment of the monitoring method of the present application.
  • FIG. 12 is a schematic structural diagram of a second embodiment of the monitoring apparatus of the present application, and NFVO is used as a monitoring
  • the device is configured to receive the monitoring policy delivered by the OSS 200 or read the monitoring policy from the NSD and/or the VNFD. Since the NFVO cannot communicate directly with the VNF in the current standard, the solution module 204 is configured to send a fault handling method directly to the VIM 210 or through the VNFM 230 to the VNF 220 for fault handling.
  • FIG. 13 is a schematic structural diagram of a third embodiment of a monitoring apparatus of the present application.
  • the acquiring module 301 is specifically configured to acquire a monitoring policy from the NFVO 310, including directly reading a monitoring policy from the VNFD 312 in the NFVO 310.
  • the resolution module 304 is configured to send a fault handling method to the VIM 320 via the NFVO 310 or directly to the VNF 330 for fault handling.
  • a system formed by a combination of NVFO and VNFM can also be used as a monitoring device, in which case NVFO is responsible for processing the VNFM for monitoring.
  • NFVO, VNFM, and VIM are an integral part of MANO. It can be seen that MANOs including NFVO, VNFM, and VIM can perform closed-loop processing of VNF faults, including fault discovery, correlation, and processing.
  • FIG. 14 is a schematic structural diagram of a fourth embodiment of a monitoring apparatus of the present application.
  • the fourth embodiment of the monitoring apparatus of the present application may be used to implement the first embodiment of the monitoring method of the present application.
  • Four embodiments include:
  • the processor 410 is coupled to the network interface 420, and the processor 410 is coupled to the network interface 420.
  • the processor 410 controls the operation of the monitoring device.
  • Processor 410 may be an integrated circuit chip with signal processing capabilities.
  • the processor 410 can also be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA off-the-shelf programmable gate array
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the processor 410 is configured to obtain a pre-configured monitoring policy, where the monitoring policy includes a correspondence between resource usage information of the VNF to be monitored and a fault processing method.
  • the resource usage information of the VNF includes: an operation indicator of the resource used by the VNF and an indicator threshold when a service failure may occur, and the fault processing method is a method for solving the service failure.
  • the monitoring policy issued by the OSS can be received and saved by the NFVO, and the monitoring policy can also be read from the NSD and/or VNFD in the NFVO.
  • the processor 410 is further configured to form a monitoring requirement according to the monitoring policy, and send the monitoring requirement to the virtualization infrastructure management terminal through the network interface 420.
  • the monitoring requirements are formed based on the resource usage information of the VNFs that need to be monitored in the monitoring strategy.
  • the virtualization infrastructure management side refers to VIM.
  • the resources used by VNF refer to the VNF used. Virtual resources or corresponding hardware resources, the resources used by the VNF are monitored by VIM.
  • the processor 410 is further configured to receive the abnormal information of the VNF monitored by the virtualization infrastructure management end in response to the monitoring requirement.
  • the processor 410 is also configured to send a fault handling method to the virtualization infrastructure management terminal or to the VNF for fault handling. After the fault handling method corresponding to the abnormal information is found in the monitoring policy, the fault processing method is sent to the VIM or the VNF for fault processing. Generally, the exception is solved by switching backups and skipping the abnormal VNF.
  • the VNF used for fault handling is not an abnormal VNF.
  • the VIM can be run on other network nodes as shown in the figure, or it can be integrated with the device. When the VIM and the device are integrated, communication through the network interface 420 is no longer required between the processor 410 and the VIM.
  • the service fault that may occur in the VNF and the resource abnormality used in the fault are associated in advance, and the corresponding service fault processing method is given, and the resource information used in the VNF may be faulty and the corresponding fault processing method is performed.
  • the association is stored in the monitoring policy.
  • the monitoring device acquires the monitoring policy and notifies the virtualization infrastructure management terminal to monitor the resources used by the VNF according to the monitoring policy.
  • the processing is performed according to the corresponding fault processing method, so that the OSS need not be reported without the EMS.
  • the VNF service faults can be monitored and processed to improve fault handling efficiency and reduce the business impact of faults.
  • the fifth embodiment of the monitoring device of the present application is based on the fourth embodiment of the monitoring device of the present application, and the NFVO is used as the monitoring device.
  • the fifth embodiment of the monitoring device of the present application can be used to implement the second embodiment of the monitoring method of the present application.
  • FIG. 15 is a schematic structural diagram of a fifth embodiment of a monitoring apparatus of the present application.
  • the NFVO When used as a monitoring device, it further includes a memory 530 coupled to the processor 510, and the NSD and VNFD are stored in the memory 530.
  • the processor 510 is configured to receive the monitoring policy delivered by the OSS through the network interface 520, or read the monitoring policy from the NSD and/or the VNFD.
  • the processor 510 is also used to send a fault handling method directly to the VIM or through the VNFM to the VNF for fault handling.
  • VIM and VNFM can be run on other network nodes as shown in the figure, or they can be integrated with the device.
  • the sixth embodiment of the monitoring device of the present application is based on the fourth embodiment of the monitoring device of the present application, and the VNFM is used as the monitoring device.
  • the sixth embodiment of the monitoring device of the present application can be used to implement the fourth embodiment of the monitoring method of the present application.
  • FIG. 16 is a schematic structural diagram of a third embodiment of the monitoring apparatus of the present application.
  • the processor 610 is configured to acquire a monitoring policy from the NFVO, including directly reading a monitoring policy from the VNFD in the NFVO, or receiving a monitoring policy of the NFVO forwarding, wherein the forwarding monitoring policy is that the NFVO is read from the NSD or Received by the OSS.
  • the processor 610 is further configured to send a fault processing method directly to the VIM through the NFVO or through the network interface 620 to the VNF for fault processing.
  • VIM and NFVO can be run on other network nodes as shown in the figure, or they can be integrated with the device.
  • NVFO NVFO-in-VNFM
  • VNFM NVFO-in-VNFM
  • NFVO and VNFM are respectively independent hardware
  • NVFO is responsible for processing VNFM for monitoring.
  • the resource usage information of the VNF to be monitored includes: an indicator of the VNF usage resource, a corresponding threshold, and a requirement for determining an abnormality.
  • the VNF resource usage indicator is at least one of the CPU usage rate, the memory usage rate, the hard disk read/write rate, and the on/off, delay, and bandwidth occupancy of the link used by the VNF.
  • the CPU usage, memory usage, and hard disk read/write rate of the computer used by the VNF may be the operational indicators of the virtual machine used by the VNF or VNFC, or may be the operational indicators of the actual computer corresponding to the virtual machine.
  • the on/off, delay, and bandwidth usage of the link used by the VNF may be an operation indicator of a link between the current VNF and other VNFs, or may be an operation indicator of a link between different VNFCs within the current VNF.
  • the threshold is a threshold for determining the corresponding indicator of the monitored VNF failure.
  • the value of the indicator can be defined as 1 and 0, 1 for connectivity, 0 for disconnection, or vice versa, threshold is also 1 or 0.
  • the requirement for determining the abnormality refers to the relationship between the value of the monitored indicator and the corresponding threshold, and determines that the VNF has a service failure.
  • the given monitoring indicator is the CPU occupancy rate
  • the threshold is 80%
  • the requirement is greater than
  • the number of indicators to be monitored is at least two
  • the requirement to determine the anomaly also includes the logical relationship (and, or, and) between the different indicators. This embodiment can be combined with any of the embodiments of the monitoring device of the present application.
  • the fault handling method includes notifying the virtualization infrastructure manager to update the NFP and/or notify the VNF for fault handling to modify its business logic.
  • the fault handling method includes notifying the virtualization infrastructure manager to update the NFP and/or notify the VNF for fault handling to modify its business logic.
  • FIG. 17 is a schematic structural diagram of a first embodiment of a network node according to the present application.
  • the first embodiment of the network node of the present application includes:
  • the processor 710 the memory 720, the network interface 730, and the bus 740.
  • the processor 710 controls the operation of the network node, and the processor 710 may also be referred to as a CPU (Central Processing Unit).
  • Processor 710 may be an integrated circuit chip with signal processing capabilities.
  • the processor 710 can also be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • Memory 720 can include read only memory and random access memory and provides instructions and data to processor 710. A portion of the memory may also include non-volatile random access memory (NVRAM).
  • NVRAM non-volatile random access memory
  • Network interface 730 is used for network communication with other devices.
  • bus 740 which may include, in addition to the data bus, a power bus, a control bus, a status signal bus, and the like. However, for clarity of description, various buses are labeled as bus 740 in the figure.
  • the memory stores the following elements, executable modules or data structures, or a subset of them, or their extended set:
  • Operation instructions include various operation instructions for implementing various operations.
  • the processor 710 performs the following operations by calling an operation instruction stored in the memory, which is stored in the supervisory program:
  • the processor 710 is configured to run a monitoring program to obtain a monitoring policy, where the monitoring policy includes a correspondence between the resource usage information of the VNF to be monitored and the fault processing method, and the monitoring requirement is formed according to the monitoring policy, and the virtualization infrastructure management terminal is configured. Sending the monitoring request; receiving the abnormal information monitored by the virtualization infrastructure management end in response to the monitoring request; and transmitting a fault processing method corresponding to the abnormal information to the virtual infrastructure management terminal or through the network interface 730 to the VNF for fault processing.
  • the virtualization infrastructure management terminal that is, the VIM, can run on other network devices as shown in the figure, communicate with the network node through the network interface 730, or run on the network node.
  • the service fault that may occur in the VNF and the resource abnormality used in the fault are associated in advance, and the corresponding service fault processing method is given, and the resource information used in the VNF may be faulty and the corresponding fault processing method is performed.
  • the association is stored in the monitoring policy.
  • the supervisory program running on the network node acquires the monitoring policy and notifies the virtualization infrastructure management terminal to monitor the resources used by the VNF according to the monitoring policy; when the abnormal information is detected, the corresponding fault processing method is processed, so that there is no EMS. In this case, the monitoring and processing of VNF service faults can be completed without reporting to the OSS.
  • FIG. 18 is a schematic structural diagram of a second embodiment of a network node according to the present application.
  • the processor 810 is configured to run the NFVO to obtain a monitoring policy, where the monitoring policy includes a correspondence between the resource usage information of the VNF to be monitored and the fault processing method; the monitoring requirement is formed according to the monitoring policy, and the monitoring requirement is sent to the VIM;
  • the VIM responds to the abnormal information monitored by the demand; sends a fault handling method corresponding to the abnormal information to the VNF or the VNF through the VNFM.
  • the VIM and VNFM may operate on other network devices as shown in the figure, communicate with the local network node through the network interface 830, or may operate on the local network node.
  • FIG. 19 is a schematic structural diagram of a third embodiment of a network node according to the present application.
  • the processor 930 is configured to run the VNFM to obtain a monitoring policy from the NFVO.
  • the monitoring policy includes a correspondence between the resource usage information of the VNF to be monitored and the fault processing method.
  • the monitoring requirement is formed according to the monitoring policy, and the monitoring requirement is sent to the VIM.
  • VIM and NFVO may operate on other network devices as shown in the figure, communicate with the network node through network interface 830, or may operate on the network node.
  • NFVO and VNFM can be combined as a supervisory program, NFVO is responsible for fault handling, and VNFM is responsible for fault monitoring.
  • the disclosed methods, apparatus, and network nodes may be implemented in other manners.
  • the device implementations described above are merely illustrative.
  • the division of the modules or units is only a logical function division.
  • there may be another division manner for example, multiple units or components may be used. Combinations can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • a computer readable storage medium A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) or a processor to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), and a random access memory (RAM, Random Access).
  • a variety of media that can store program code such as a memory, a disk, or an optical disk.

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente invention concerne un procédé de surveillance et un dispositif de surveillance dans un environnement de virtualisation de réseau, et un nœud de réseau. Le procédé de surveillance comprend les étapes suivantes : une extrémité de surveillance de virtualisation de fonction de réseau obtient une stratégie de surveillance, la stratégie de surveillance comprenant une correspondance entre des informations d'utilisation de ressources d'une VNF à surveiller et un procédé de gestion de défauts; l'extrémité de surveillance de virtualisation de fonction de réseau génère un besoin de surveillance conformément à la stratégie de surveillance et transmet le besoin de surveillance à une extrémité de gestion d'infrastructure de virtualisation; l'extrémité de surveillance de virtualisation de fonction de réseau reçoit des informations d'exception de VNF détectées par l'extrémité de gestion d'infrastructure de virtualisation en réponse au besoin de surveillance; l'extrémité de surveillance de virtualisation de fonction de réseau transmet le procédé de gestion de défauts correspondant aux informations d'exception à l'extrémité de gestion d'infrastructure de virtualisation ou à la VNF utilisée pour la gestion d'un défaut.
PCT/CN2015/092431 2015-10-21 2015-10-21 Procédé de surveillance et dispositif de surveillance en environnement de virtualisation de réseau, et nœud de réseau WO2017066940A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2015/092431 WO2017066940A1 (fr) 2015-10-21 2015-10-21 Procédé de surveillance et dispositif de surveillance en environnement de virtualisation de réseau, et nœud de réseau
CN201580079532.1A CN107534575B (zh) 2015-10-21 2015-10-21 一种网络虚拟化环境下的监控方法、监控装置和网络节点

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/092431 WO2017066940A1 (fr) 2015-10-21 2015-10-21 Procédé de surveillance et dispositif de surveillance en environnement de virtualisation de réseau, et nœud de réseau

Publications (1)

Publication Number Publication Date
WO2017066940A1 true WO2017066940A1 (fr) 2017-04-27

Family

ID=58556566

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/092431 WO2017066940A1 (fr) 2015-10-21 2015-10-21 Procédé de surveillance et dispositif de surveillance en environnement de virtualisation de réseau, et nœud de réseau

Country Status (2)

Country Link
CN (1) CN107534575B (fr)
WO (1) WO2017066940A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112565008A (zh) * 2020-11-26 2021-03-26 深信服科技股份有限公司 一种网路监控方法、装置及相关设备
CN115865644A (zh) * 2022-11-09 2023-03-28 浪潮通信信息系统有限公司 业务故障处理方法、装置、设备及存储介质

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110061853B (zh) * 2018-01-17 2023-03-14 中兴通讯股份有限公司 策略处理方法、装置及存储介质
CN112838942A (zh) * 2019-11-25 2021-05-25 中兴通讯股份有限公司 网络运维方法、电子设备以及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014009160A1 (fr) * 2012-06-29 2014-01-16 Mpstor Limited Stockage de données comprenant des appareils virtuels
CN104170323A (zh) * 2014-04-09 2014-11-26 华为技术有限公司 基于网络功能虚拟化的故障处理方法及装置、系统
CN104468181A (zh) * 2013-09-23 2015-03-25 英特尔公司 虚拟网络设备故障的检测和处理
CN104506337A (zh) * 2014-11-20 2015-04-08 北京邮电大学 基于区域性故障预测的虚拟网络映射方法及装置
CN104579732A (zh) * 2013-10-21 2015-04-29 华为技术有限公司 虚拟化网络功能网元的管理方法、装置和系统

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104685830B (zh) * 2013-09-30 2018-03-06 华为技术有限公司 故障管理的方法、实体和系统
BR112016016656A2 (pt) * 2014-01-21 2017-08-08 Huawei Tech Co Ltd Método de manuseio de falha de serviço de rede, sistema de gerenciamento de serviço e módulo de gerenciamento de sistema

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014009160A1 (fr) * 2012-06-29 2014-01-16 Mpstor Limited Stockage de données comprenant des appareils virtuels
CN104468181A (zh) * 2013-09-23 2015-03-25 英特尔公司 虚拟网络设备故障的检测和处理
CN104579732A (zh) * 2013-10-21 2015-04-29 华为技术有限公司 虚拟化网络功能网元的管理方法、装置和系统
CN104170323A (zh) * 2014-04-09 2014-11-26 华为技术有限公司 基于网络功能虚拟化的故障处理方法及装置、系统
CN104506337A (zh) * 2014-11-20 2015-04-08 北京邮电大学 基于区域性故障预测的虚拟网络映射方法及装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112565008A (zh) * 2020-11-26 2021-03-26 深信服科技股份有限公司 一种网路监控方法、装置及相关设备
CN115865644A (zh) * 2022-11-09 2023-03-28 浪潮通信信息系统有限公司 业务故障处理方法、装置、设备及存储介质

Also Published As

Publication number Publication date
CN107534575B (zh) 2020-07-10
CN107534575A (zh) 2018-01-02

Similar Documents

Publication Publication Date Title
US10560360B2 (en) Diagnostic heartbeat throttling
US8756453B2 (en) Communication system with diagnostic capabilities
CN112534776B (zh) 用于在网络环境中检测网络功能失败和重启的方法及装置
US10764939B2 (en) Network function processing method and related device
US8769089B2 (en) Distributed application using diagnostic heartbeating
US8874974B2 (en) Synchronizing a distributed communication system using diagnostic heartbeating
CN107526659B (zh) 用于失效备援的方法和设备
US20180191561A1 (en) Network element upgrade method and device
JP6466003B2 (ja) Ｖｎｆフェイルオーバの方法及び装置
US9231826B2 (en) Zero configuration of a virtual distributed device
WO2016029749A1 (fr) Procédé, dispositif et système de détection d'échec de communication
CN109344014B (zh) 一种主备切换方法、装置及通信设备
US9838245B2 (en) Systems and methods for improved fault tolerance in solicited information handling systems
US20130124607A1 (en) Diagnostic heartbeating in a distributed data processing environment
WO2017050254A1 (fr) Procédé, dispositif et système de copie de sécurité à chaud
CN102710457B (zh) 一种跨网段的n+1备份方法及装置
WO2017066940A1 (fr) Procédé de surveillance et dispositif de surveillance en environnement de virtualisation de réseau, et nœud de réseau
US8903960B2 (en) Activate attribute for service profiles in unified computing system
WO2018090386A1 (fr) Procédé, dispositif et système de traitement d'anomalies de modules nf
US20160373530A1 (en) Method and system for sharing state between network elements
US9634885B2 (en) Control target flow specifying method and control target flow specifying device
US10498581B2 (en) Event processing in a network management system
US20160205033A1 (en) Pool element status information synchronization method, pool register, and pool element
AU2011229566B2 (en) Load sharing method and apparatus
US20200336368A1 (en) Notification and transfer of lag control pending a primary node reboot

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15906458

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15906458

Country of ref document: EP

Kind code of ref document: A1