WO2014205721A1 - 故障处理方法、装置和系统 - Google Patents

故障处理方法、装置和系统 Download PDF

Info

Publication number
WO2014205721A1
WO2014205721A1 PCT/CN2013/078135 CN2013078135W WO2014205721A1 WO 2014205721 A1 WO2014205721 A1 WO 2014205721A1 CN 2013078135 W CN2013078135 W CN 2013078135W WO 2014205721 A1 WO2014205721 A1 WO 2014205721A1
Authority
WO
WIPO (PCT)
Prior art keywords
fault
level
service
low
management system
Prior art date
Application number
PCT/CN2013/078135
Other languages
English (en)
French (fr)
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 CN201380003385.0A priority Critical patent/CN104521181B/zh
Priority to EP13888106.5A priority patent/EP3001606B1/en
Priority to PCT/CN2013/078135 priority patent/WO2014205721A1/zh
Publication of WO2014205721A1 publication Critical patent/WO2014205721A1/zh
Priority to US14/979,383 priority patent/US10091672B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0604—Management of faults, events, alarms or notifications using filtering, e.g. reduction of information by using priority, element types, position or time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
    • H04L41/065—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis involving logical or physical relationship, e.g. grouping and hierarchies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/30—Network data restoration; Network data reliability; Network data fault tolerance

Definitions

  • the present invention relates to the field of communications, and in particular, to a fault processing method, apparatus, and system. Background technique
  • the fault management system is one of the important components in the mobile communication system, and mainly provides fault location and fault handling for the mobile communication system.
  • a specific mobile communication system is usually operated by a single operator, so the fault management system is also designed in the architecture of a carrier.
  • a mobile communication system usually includes an infrastructure component, a transmission component, and a wireless service component. Since these components are all managed by the same operator, the fault management system is also applied to these components simultaneously, regardless of Whether it is fault location or fault handling, it is completed internally by the operator. When the fault management system locates the fault, it will generate a corresponding dispatch ticket to be sent to the operator's maintenance personnel.
  • a fault processing method for a low-level fault management system in a communication fault management system, the communication fault management system comprising at least one low-level fault management system and at least one high-level fault management system, the method comprising :
  • the service dependency relationship table is a correspondence between a low-level service and a high-level service that depends on the operation of the low-level service.
  • the sending a fault notification to the high-level fault management system corresponding to the affected high-level service including:
  • the fault generating message carries a high-level affected service identifier, where the high-level affected service identifier is used to indicate a low-level fault alarm
  • the high-level service affected by the service the high-level fault management system receives and saves the fault-generating message sent by the low-level fault management system; and detects the fault-generated message during the saving of the fault-generating message Whether the high-level service indicated by the high-level affected service identifier is faulty; if the detection result is a fault, the fault of the high-level service is not processed temporarily.
  • the method is characterized in that, if the fault alarm condition is that a fault of a low-level service has been recovered, the The high-level fault management system corresponding to the high-level service sends a fault notification message, including:
  • the fault recovery message carries a high-level affected service identifier, where the high-level affected service identifier is used to indicate a low-level fault alarm
  • the high-level service affected by the service the high-level fault management system receives the fault recovery message sent by the low-level fault management system; and detects the high-level service indicated by the high-level affected service identifier carried by the fault recovery message Whether the fault has been recovered; if the detection result is that the fault has not been recovered, the fault of the high-level service is processed.
  • the fault generating message and the fault recovery message both carry a low layer service fault identifier and a fault type, where the low layer service
  • the fault identifier is used to indicate the low-level service of the fault alarm; so that the high-level fault management system searches for a fault-generating message that matches the fault recovery message, and the matching is
  • the low-level service fault identifier and the fault type respectively included in the two messages are the same; when the fault-generating message matching the fault recovery message is found, the fault-generating message is deleted.
  • a fault processing method for a high-level fault management system in a communication fault management system, where the communication fault management system includes at least one low-level fault management system and at least one high-level fault management system, Methods include:
  • the service dependency relationship table is a correspondence between a low-level service and a high-level service that depends on the operation of the low-level service.
  • the receiving the fault notification message sent by the low-level fault management system includes:
  • Determining, according to the fault notification message, whether the faulty high-level service needs to be processed including:
  • the detection result is a failure, the fault of the high-level service is not processed temporarily.
  • the detecting, by the fault generating message, the high-level affected service identifier carried in the fault generating message Whether the indicated high-level business has failed including:
  • the high-level fault service identifier After receiving the fault generating message, detecting whether any one of the high-level affected service identifier carried in the fault-generating message and the currently-stored at least one high-level fault service identifier is the same, and the high-level fault service identifier is used for Indicates a high-level business that has failed;
  • the detecting, by the fault generating message, the high-level affected service identifier carried in the fault generating message Whether the indicated high-level business has failed including:
  • the high-level service indicated by the high-level affected service identifier carried in the same fault-generating message is determined to be faulty.
  • the detecting the obtained high-level fault service identifier and the pre-stored at least one of the high-level affected service identifiers After any one is the same also includes:
  • the result of the detection is that the obtained high-level fault service identifier is different from the current high-level service identifier, the fault of the high-level service indicated by the high-level fault service identifier is processed.
  • the receiving the fault notification message sent by the low-level fault management system Includes:
  • Determining, according to the fault notification message, whether the faulty high-level service needs to be processed including:
  • the fault generating message and the fault recovery message both carrying a low-layer service fault identifier and a fault type, where the low-layer service is The fault identifier is used to indicate the low-level service of the fault alarm;
  • the method further includes: searching for a fault generation message that matches the fault recovery message, where the matching refers to two messages The low-level service fault identifier and the fault type are the same;
  • a fault processing apparatus for a low-level fault management system in a communication fault management system, the communication fault management system including at least one low-level fault management system and at least one high-level fault management system, the apparatus including :
  • An alarm detection module is configured to detect a fault alarm in a low-level service.
  • the relationship query module is configured to query, according to the fault alarm situation and the service dependency relationship table stored in the system, the affected high-level service;
  • a message sending module configured to send a fault notification message to the high-level fault management system corresponding to the affected high-level service, so that the high-level fault management system receives the fault notification message sent by the low-level fault management system; Determining, according to the fault notification message, whether a faulty high-level service needs to be processed;
  • the service dependency relationship table is a correspondence between a low-level service and a high-level service that depends on the operation of the low-level service.
  • the shell is:
  • the message sending module is configured to send a fault generating message to the high-level fault management system corresponding to the affected high-level service, where the fault generating message carries a high-level affected service identifier, and the high-level affected service identifier a high-level service affected by a low-level service for indicating a fault alarm; wherein the high-level fault management system receives and saves the fault-generating message sent by the low-level fault management system; during the saving of the fault-generating message, detecting Whether the high-level service indicated by the high-level affected service identifier carried in the fault-generating message is faulty; if the detection result is a fault, the fault of the high-level service is not processed temporarily.
  • the message sending module is configured to send a fault recovery message to the high-level fault management system corresponding to the affected high-level service, where the fault recovery message carries a high-level affected service identifier, and the high-level affected service identifier a high-level service affected by a low-level service for indicating a fault alarm; wherein the high-level fault management system receives the fault recovery sent by the low-level fault management system And detecting a failure of the high-level service indicated by the high-level service identifier that is carried by the fault recovery message, and detecting that the fault of the high-level service is not recovered.
  • the fault generating message and the fault recovery message both carry a low-layer service fault identifier and a fault type, where the low-layer service
  • the fault identifier is used to indicate the low-level service of the fault alarm; and the high-level fault management system searches for a fault-generating message that matches the fault recovery message, where the matching refers to the low-level service included in each of the two messages.
  • the fault identifier and the fault type are the same; when the fault generation message matching the fault recovery message is found, the fault generation message is deleted.
  • a fault processing apparatus for a high-level fault management system in a communication fault management system, where the communication fault management system includes at least one low-level fault management system and at least one high-level fault management system,
  • the device includes:
  • a message receiving module configured to receive a fault notification message sent by the low-level fault management system, where the fault notification message is that the low-level fault management system detects a fault alarm situation in a low-level service, according to the fault alarm situation and the system storage
  • the service dependency table query is sent to the high-level service that is affected, and then sent to the high-level fault management system corresponding to the affected high-level service;
  • the fault processing module is configured to determine, according to the fault notification message, a faulty high-level Whether the business needs to be processed;
  • the service dependency relationship table is a correspondence between a low-level service and a high-level service that depends on the operation of the low-level service.
  • the message receiving module is configured to receive and save a fault generating message that is sent by the low-level fault management system, where the fault generating message carries a high-level affected service identifier.
  • the high-level affected service identifier is used to indicate a high-level service affected by a low-level service in which a fault alarm occurs;
  • the fault processing module is configured to detect, during the saving of the fault generating message, whether a high-level service indicated by the high-level affected service identifier carried in the fault generating message is faulty; if the detection result is a fault, temporarily Failure to handle the high-level business.
  • the fault processing module includes: a first detecting unit and a first determining unit;
  • the first detecting unit is configured to: after receiving the fault generating message, detecting the high-level affected service identifier carried by the fault generating message and the currently saved at least one high-level fault service Whether any one of the identifiers is the same, and the high-level fault service identifier is used to indicate that a high-level service has failed;
  • the first determining unit is configured to: if the detection result is that the received high-level affected service identifier is the same as the currently stored high-level fault service identifier, determine the high-level affected service identifier carried in the fault generating message The indicated high-level business has failed.
  • the fault processing module includes: an identifier acquiring unit, a second detecting unit, and a second determining unit;
  • the high-level fault service identifier is used to indicate a faulty high-level service after detecting a fault of a high-level service, and the second detecting unit is configured to detect the acquired high-level service. Whether the high-level fault service identifier and any one of the currently stored high-level affected service identifiers are the same;
  • the second determining unit is configured to determine, if the detection result is that the obtained high-level fault service identifier is the same as the currently saved high-level affected service identifier, determine the high-level affected service carried in the same fault generating message.
  • the high-level service indicated by the identifier is faulty.
  • the fault processing module further includes: a third determining unit;
  • the third determining unit is configured to: if the detection result is that the obtained high-level fault service identifier is different from the current high-level affected service identifier, the processed high-level fault service identifier is processed. The failure of high-level business.
  • the message receiving module is further configured to receive the low-level fault management a failure recovery message sent by the system, where the failure recovery message carries the high-level affected service identifier; the fault processing module is further configured to detect a high-level indicated by the high-level affected service identifier carried in the fault recovery message. Whether the fault of the service has been restored; if the test result is that the fault has not been recovered, the fault of the high-level service is processed.
  • the fault generating message and the fault recovery message both carrying a low-layer service fault identifier and a fault type, where the low-layer service is The fault identifier is used to indicate the low-level service of the fault alarm;
  • the device further includes: a message matching module and a message deleting module;
  • the message matching module is configured to search for a fault generating message that matches the fault recovery message, where the matching refers to the low-level service fault identifier and the fault type included in each of the two messages. All the same;
  • the message deleting module is configured to delete the fault generating message when a fault generating message matching the fault recovery message is found.
  • a communication fault management system comprising at least one low-level fault management system and at least one high-level fault management system;
  • the low-level fault management system includes the fault handling apparatus of any of the various possible implementations of the third aspect and the third aspect;
  • the high level fault management system includes the fault handling apparatus of any of the various possible implementations of the fourth aspect and the fourth aspect.
  • a fault management system for implementing a low-level fault management system in a communication fault management system, where the communication fault management system includes at least one low-level fault management system and at least one high-level fault management system.
  • the system includes: a processor, a memory, and a transmitter; the processor is configured to detect a fault alarm situation in a low-level service;
  • the processor is further configured to query, according to the fault alarm situation and the service dependency relationship table stored in the system in the memory, the affected high-level service;
  • the processor is further configured to control the sender to send a fault notification message to the high-level fault management system corresponding to the affected high-level service, so that the high-level fault management system receives the low-level fault management system to send The fault notification message; determining, according to the fault notification message, whether a faulty high-level service needs to be processed;
  • the service dependency relationship table is a correspondence between a low-level service and a high-level service that depends on the operation of the low-level service.
  • the shell is:
  • the processor is further configured to: send, by the sender, a fault generating message to the high-level fault management system corresponding to the affected high-level service, where the fault generating message carries a high-level affected service identifier, where The high-level affected service identifier is used to indicate the high-level service affected by the low-level service in which the fault alarm occurs; so that the high-level fault management system receives and saves the fault-generating message sent by the low-level fault management system; During the period of the message, it is detected whether the high-level service indicated by the high-level affected service identifier carried in the fault-generating message is faulty; if the detection result is a fault, the fault of the high-level service is not processed temporarily.
  • the fault alarm condition is that the fault of a low-level service has been restored, and the shell 'J:
  • the processor is further configured to: send, by the sender, a fault recovery message to the high-level fault management system corresponding to the affected high-level service, where the fault recovery message carries a high-level affected service identifier, where The high-level affected service identifier is used to indicate the high-level service affected by the low-level service in which the fault alarm occurs; so that the high-level fault management system receives the fault recovery message sent by the low-level fault management system; and detects the fault recovery message Whether the fault of the high-level service indicated by the high-level affected service identifier has been restored; if the detection result is that the fault has not been recovered, the fault of the high-level service is processed.
  • the fault generating message and the fault recovery message both carry a low-layer service fault identifier and a fault type, where the low-layer service
  • the fault identifier is used to indicate the low-level service of the fault alarm; and the high-level fault management system searches for a fault-generating message that matches the fault recovery message, where the matching refers to the low-level service included in each of the two messages.
  • the fault identifier and the fault type are the same; when the fault generation message matching the fault recovery message is found, the fault generation message is deleted.
  • a fault processing system for implementing a high-level fault management system in a communication fault management system, where the communication fault management system includes at least one low-level fault management system and at least one high-level fault management system.
  • the system includes: a receiver, a processor, and a memory; the processor, configured to control the receiver to receive a fault notification message sent by the low-level fault management system, where the fault notification message is the low-level fault management system Detecting the fault alarm situation in the low-level service, querying the affected high-level service according to the fault alarm situation and the service dependency relationship table stored in the system, and then sending the high-level service to the high-level fault management system corresponding to the affected high-level service of;
  • the processor is further configured to determine, according to the fault notification message, whether a faulty high-level service needs to be processed;
  • the service dependency relationship table is a correspondence between a low-level service and a high-level service that depends on the operation of the low-level service.
  • the processor is further configured to control the receiver to receive a fault generation message sent by the low-level fault management system, and save the fault to the memory, where the fault
  • the generated message carries a high-level affected service identifier, where the high-level affected service identifier is used to indicate a high-level service affected by a low-level service in which a fault alarm occurs;
  • the processor is further configured to detect the location during the saving of the fault generating message by the memory Whether the high-level service indicated by the high-level affected service identifier carried in the fault-generating message is faulty;
  • the processor is further configured to temporarily not process the fault of the high-level service if the detection result is a fault.
  • the processor is further configured to detect the fault after controlling the receiver to receive the fault generating message And generating, by the high-level fault service identifier, the high-level fault service identifier is used to indicate that the faulty high-level service is faulty;
  • the processor is further configured to: if the detection result is that the received high-level affected service identifier is the same as the currently saved high-level fault service identifier, determining that the high-level affected service identifier carried in the fault-generating message is The high-level business has failed.
  • the processor is further configured to: after detecting a fault of a high-level service, obtain a corresponding high-level fault service identifier, where The high-level fault service identifier is used to indicate that a high-level service has failed;
  • the processor is further configured to detect whether the acquired high-level fault service identifier and any one of the at least one high-level affected service identifier currently saved by the memory are the same;
  • the processor is further configured to: if the detection result is that the obtained high-level fault service identifier is the same as the currently-supplied high-level affected service identifier, determine the high-level affected service identifier carried in the same fault occurrence message. The indicated high-level business has failed.
  • the processor is further configured to: if the detection result is the obtained high-level fault service identifier and all currently saved high-level If the affected service identifiers are different, the fault of the high-level service indicated by the obtained high-level fault service identifier is processed.
  • the processor is further configured to control the receiver receiving a fault recovery message sent by the low-level fault management system, where the fault recovery message carries the high-level affected service identifier;
  • the processor is further configured to detect whether a fault of the high-level service indicated by the high-level affected service identifier carried in the fault recovery message has been restored;
  • the processor is further configured to process a fault of the high-level service if the detection result is that the recovery is not yet completed.
  • the fault generating message and the fault recovery message both carry a low-layer service fault identifier and a fault type, where the low-layer service The fault identifier is used to indicate the low-level service of the fault alarm;
  • the processor is further configured to search for a fault-generating message that matches the fault recovery message, where the matching is that the low-level service fault identifier and the fault type respectively included in the two messages are the same;
  • the processor is further configured to delete the fault generation message when a fault generation message matching the fault recovery message is found.
  • a communication fault management system comprising at least one low-level fault management system and at least one high-level fault management system;
  • the low-level fault management system is the fault management system of any of the various possible embodiments of the sixth aspect and the sixth aspect;
  • the high-level fault management system is the fault management system of any of the various possible embodiments of the seventh aspect and the seventh aspect.
  • the affected high-level services are obtained according to the fault alarm situation and the service dependency table stored in the system;
  • the high-level fault management system corresponding to the high-level service sends a fault notification message, so that the high-level fault management system determines whether the faulty high-level service needs to be processed according to the fault notification message; and solves the scenario in which different operators simultaneously operate the same mobile communication system.
  • the existing fault management system may cause some operators to waste manpower or material resources during the fault maintenance process.
  • the high-level fault management system can determine the faulty high-level service according to the fault notification message. Whether the faulty high-level business needs to be processed, thereby reducing the unnecessary waste of maintenance resources.
  • FIG. 1 is a schematic structural diagram of an implementation environment according to an embodiment of the present invention
  • 2 is a flowchart of a method for processing a fault according to an embodiment of the present invention
  • FIG. 3 is a flowchart of a method for processing a fault according to another embodiment of the present invention
  • FIG. 3B is a sub-step flow chart of step 305 in the fault processing method provided in FIG. 3A
  • FIG. 3C is a sub-step flow chart of step 305 in the fault processing method provided in FIG. 3A
  • FIG. 4 is a flowchart of an embodiment of the present invention.
  • FIG. 5 is a block diagram showing the structure of a communication fault management system according to another embodiment of the present invention
  • FIG. 6 is a block diagram showing the structure of a fault management system according to an embodiment of the present invention.
  • FIG. 7 is a block diagram showing the structure of a fault management system according to another embodiment of the present invention.
  • FIG. 8 is a structural block diagram of a communication fault management system according to an embodiment of the present invention. detailed description
  • FIG. 1 is a schematic structural diagram of an implementation environment according to an embodiment of the present invention.
  • the implementation environment is a mobile communication system that includes an infrastructure component 120, a transmission component 140, and a wireless service component 160.
  • the wireless service component 160 is at the highest level, and the normal operation of the traffic on the wireless service component 160 depends on the normal operation of the traffic on the transport component 140 or the services on the infrastructure component 120.
  • the service provided by the wireless service component 160 includes the cell 1 and the cell 2.
  • the service provided on the transmission component 140 includes the transmission link 1.
  • the services provided on the infrastructure component 120 include the transmission board 1 and the baseband single. Board 1.
  • the normal operation of the cell 1 depends on the normal operation of the transmission link 1 and the transmission board 1; the normal operation of the cell 2 depends on the normal operation of the baseband board 1.
  • the normal operation of the traffic on the transport component 140 depends on the normal operation of the traffic on the infrastructure component 120.
  • the normal operation of the transmission link 1 depends on the normal operation of the transmission board 1.
  • the normal operation of such high-level services needs to depend on the normal operation of low-level services, which can be called business dependencies.
  • the fault management system corresponding to each component is also divided into multiple layers. Among them, in every two-layer fault management system, the fault management system located in the lower layer is called the low-level fault management system, and the fault management system located in the upper layer is called the high-level fault management system.
  • the fault management system corresponding to the wireless service component 160 is a high-level fault management system, and the fault management system corresponding to the transmission component 140 is a low-level fault management system;
  • the fault management system corresponding to the transmission component 140 is a high-level fault management system, and the fault management system corresponding to the infrastructure component 120 is a low-level fault management system;
  • the fault management system corresponding to the wireless service component 160 is a high-level fault management system
  • the fault management system corresponding to the infrastructure component 120 is a low-level fault management system.
  • the above-mentioned hierarchical division of the mobile communication system is only an example. In different embodiments, the division structure of the mobile communication system may be different, which is not specifically limited.
  • the term "service” as used herein refers to components such as physical facilities, resources, services, and services in a mobile communication system, such as a cell, a base station, a transmission link, and a transmission board. , baseband boards, etc. are collectively referred to as services.
  • FIG. 2 a flow chart of a method for processing a fault according to an embodiment of the present invention is shown.
  • the fault handling method is used in a communication fault management system that includes at least one low level fault management system and at least one high level fault management system.
  • the fault processing method includes: Step 201: The low-level fault management system detects a fault alarm condition in a low-level service;
  • the low-level fault management system detects fault alarms in low-level services. There are two types of fault alarms: one low-level service fails; or one low-level service has been recovered.
  • the low-level fault management system detects that the low-level service A has failed, or the low-level fault management system detects that the fault of the lower-layer service A has been restored.
  • Step 202 The low-level fault management system queries and obtains the affected high-level service according to the fault alarm situation and the service dependency relationship table stored in the system;
  • the low-level fault management system is pre-configured to store a service dependency relationship table, where the service dependency relationship table is a correspondence between a low-level service and a high-level service that depends on the operation of the low-level service.
  • the service dependency table stored in the low-level fault management system can be dynamically generated according to the running conditions between the services.
  • the low-level service A has a service dependency relationship with the high-level service B, that is, the operation of the high-level service B depends on the low-level service A.
  • the affected high-level service is obtained according to the fault alarm situation and the service dependency table stored in the system.
  • the low-level fault management system queries the affected high-level service as B.
  • Step 203 The low-level fault management system sends a fault notification message to the high-level fault management system corresponding to the affected high-level service.
  • the low-level fault management system sends a fault notification message to the high-level fault management system corresponding to the affected high-level service B.
  • fault notification messages There are two types of fault notification messages: fault generation messages and fault recovery messages.
  • Step 204 The high-level fault management system receives the fault notification message sent by the low-level fault management system.
  • Step 205 The high-level fault management system determines, according to the fault notification message, whether the faulty high-level service needs to be processed.
  • the high-level fault management system determines, according to the fault notification message, whether the faulty high-level service may be caused by a fault of the low-level service;
  • the fault processing method provided in this embodiment is configured by setting at least two layers of fault management systems, and when the low-level fault management system detects the fault alarm condition of the low-level service, according to the fault alarm situation and the service dependence of the system storage.
  • the relationship table query obtains the affected high-level service; sends a fault notification message to the high-level fault management system corresponding to the affected high-level service, so that the high-level fault management system determines whether the faulty high-level service needs to be processed according to the fault notification message;
  • the existing fault management system may cause some operators to waste manpower or material resources during the fault maintenance process.
  • the low-level service fails, the high-level fault occurs.
  • the management system can determine whether the faulty high-level service needs to be processed according to the fault notification message to the faulty high-level service, thereby reducing the unnecessary waste of maintenance resources.
  • FIG. 3A illustrates a method flow of a fault processing method according to another embodiment of the present invention. Cheng Tu.
  • the fault handling method is used in a communication fault management system that includes at least one low level fault management system and at least one high level fault management system.
  • the fault processing method includes:
  • Step 301 The low-level fault management system detects a fault alarm condition in the low-level service.
  • the low-level fault management system detects fault alarms in low-level services.
  • the fault alarm detection process can be performed by using the existing fault detection technology, and will not be described again.
  • fault alarms There are two types of fault alarms: one low-level service fails; or one low-level service has been recovered. In this step, it is assumed that the fault alarm condition is the former type. For example, the low-level fault management system detects that the low-level service A has failed.
  • Step 302 The low-level fault management system queries and obtains the affected high-level service according to the fault alarm situation and the service dependency relationship table stored in the system;
  • the low-level fault management system first obtains a low-level service fault identifier according to the fault alarm condition, and the low-level service fault identifier is used to indicate a low-level service in which a fault alarm occurs; and then, the low-level fault management system system is stored in the system through a low-level fault information identifier.
  • the service dependency table is used to query the high-level affected service identifier, and the high-level affected service identifier is used to indicate the high-level service affected by the low-level service with the fault alarm.
  • the fault alarm situation is as follows: If the low-level service A fails, the low-level fault management system obtains the low-level service fault identifier A, and then queries the high-level affected service identifier B according to the service dependency relationship table stored in the system. The low-level service A used by the identifier B to indicate that the fault alarm is generated affects the high-level service B.
  • Step 303 If the fault alarm condition is that a low-level service fails, the low-level fault management system sends a fault generation message to the high-level fault management system corresponding to the affected high-level service.
  • the low-level fault management system sends a fault-generating message to the high-level fault management system corresponding to the affected high-level service, and the fault-generating message carries at least the high-level affected service identifier.
  • the high-level affected service identifier carried in the fault generation message can be used for fault demarcation of the high-level fault management system.
  • the fault generation message further carries a low layer service fault identifier and a fault type.
  • the format of a fault-generating message is as follows:
  • the low-level service fault identifier has two representation modes: 1. Low-level service name; 2. Low-level service type + service ID. There are two ways to express high-level affected service identifiers: 1. High-level business name; 2. High-level business type + business ID.
  • Step 304 The high-level fault management system receives and saves a fault generating message sent by the low-level fault management system.
  • the high-level fault management system receives and saves the fault generation message sent by the low-level fault management system.
  • the high-level fault management system can store all received fault-generating messages in a list of low-level fault information, which can come from the same or different low-level fault management systems.
  • Step 305 The high-level fault management system detects whether the high-level service indicated by the high-level affected service identifier carried in the fault-generating message is faulty during the period of saving the fault-generating message;
  • the high-level fault management system detects whether the high-level service indicated by the high-level affected service identifier carried in the fault-generating message is faulty during the period of saving the fault-generating message. For example, if the high-level affected service identifier indicates high-level service B, the high-level fault management system needs to detect whether the high-level service B has failed. Because the high-level fault management system detects that the high-level service fails and the time when the fault is generated is not necessarily the same, it may be in the same order. Therefore, the detection process in this step can be triggered in two ways. In a trigger mode, this step includes the following sub-steps, as shown in Figure 3B:
  • the high-level fault management system may have detected that one or more high-level services have failed, and the high-level fault management system saves at least one high-level fault service identifier, where the high-level fault service identifier is used to indicate that the fault occurs.
  • High-level business Specifically, the high-level fault management system can store at least one high-level fault service identifier in the high-level fault information list.
  • the high-level fault management system After receiving the fault occurrence message, the high-level fault management system detects whether any one of the high-level affected service identifier carried in the fault-generating message and the currently-stored at least one high-level fault service identifier is the same.
  • the high-level fault management system traverses the high-level fault information list to see whether the same high-level fault service identifier exists.
  • the detection result is that the received high-level affected service identifier is the same as the currently saved high-level fault service identifier, determining that the high-level affected service identifier carried in the fault-generating message is indicated by The high-level business has failed.
  • this step includes the following sub-steps, as shown in Figure 3C:
  • the high-level fault management system detects a fault alarm of the high-level service at the local layer, and after detecting that a high-level service fails, obtains a corresponding high-level
  • the fault service identifier is used to indicate the faulty high-level service.
  • the high-level fault management system traverses the same high-level affected service identifier in the low-level fault information list.
  • the detection result is that the obtained high-level fault service identifier is the same as the currently stored high-level affected service identifier, the high-level service indicated by the high-level affected service identifier carried in the same fault-generating message is determined to be faulty.
  • the fault of the high-level service indicated by the obtained high-level fault service identifier is processed.
  • Step 306 If the detection result is that a fault occurs, the fault of the high-level service is not processed temporarily.
  • the high-level fault management system temporarily does not handle the failure of the high-level service. Because the low-level service on which the high-level service depends is faulty, the high-level service may fail to operate normally. In this case, the fault of the high-level service may not be caused by its own cause, so the high-level fault management system may not process the high-level service temporarily. Failure to reduce unnecessary dispatch, dispatching refers to the fault management system automatically generating dispatch orders to dispatch engineers for maintenance and construction.
  • step 305 if the result of the detection in step 305 is that no failure has occurred, no processing is required.
  • Step 307 The low-level fault management system detects a fault alarm situation in the low-level service.
  • the low-level fault management system detects fault alarms in low-level services.
  • the fault alarm detection process can be performed by using the existing fault detection technology, and will not be described again.
  • fault alarms There are two types of fault alarms: one low-level service fails; or one low-level service has been recovered. In this step, it is assumed that the fault alarm condition is the latter type. For example, the fault that the low-level fault management system detects that the low-level service A has occurred has been restored.
  • Step 308 The low-level fault management system queries and obtains the affected high-level service according to the fault alarm situation and the service dependency relationship table stored in the system; Specifically, the low-level fault management system first obtains a low-level service fault identifier according to the fault alarm condition, and the low-level service fault identifier is used to indicate a low-level service in which a fault alarm occurs; and then, the low-level fault management system system is stored in the system through a low-level fault information identifier.
  • the service dependency table is used to query the high-level affected service identifier, and the high-level affected service identifier is used to indicate the high-level service affected by the low-level service with the fault alarm.
  • the fault alarm situation is as follows: The fault of the low-level service A has been restored, and the low-level fault management system obtains the low-level service fault identifier A, and then queries the high-level affected service identifier B according to the service dependency table stored in the system.
  • the service identifier B is used to indicate that the low-level service A that has a fault alarm affects the high-level service B.
  • Step 309 If the fault alarm condition is that the fault of a low-level service has been restored, the low-level fault management system sends a fault recovery message to the high-level fault management system corresponding to the affected high-level service; if the fault alarm condition is a fault of the low-level service, After the recovery, the low-level fault management system sends a fault recovery message to the high-level fault management system corresponding to the affected high-level service, and the fault recovery message carries at least the high-level affected service identifier.
  • the high-level affected service identifier carried in the fault recovery message can be used for fault demarcation of the high-level fault management system.
  • the fault recovery message further carries a low layer service fault identifier and a fault type.
  • the format of a fault recovery message is as follows:
  • Low-level service fault identification There are two ways to indicate low-level service fault identification: 1. Low-level service name; 2. Low-level service type + service ID.
  • High-level affected service identifiers There are two ways to express high-level affected service identifiers: 1. High-level business name; 2. High-level business type + business ID.
  • the high-level fault management system receives the fault recovery message sent by the low-level fault management system.
  • Step 310 The high-level fault management system searches for a fault-generating message that matches the fault recovery message, and the matching refers to the low-level service fault identifier included in each of the two messages. Same as the fault type;
  • the high-level fault management system upon receiving the fault recovery message, finds a fault-generating message that matches the fault recovery message.
  • Matching means that the low-level service fault identification and fault type included in each of the at least two messages are the same. Because the same low-level service may have different types of faults; different low-level services may also have the same type of faults. Only when these two parameters are the same, can the two messages be the same fault for the same low-level service.
  • Step 311 Delete the faulty product when the fault generation message matching the fault recovery message is found. Health news.
  • the high-level fault management system may delete the matched fault-generating message from the locally saved low-level fault information list when the fault-generating message matching the fault-recovery message is found.
  • Step 312 The high-level fault management system detects whether the fault of the high-level service indicated by the high-level affected service identifier carried in the fault recovery message has been restored.
  • the high-level fault management system locally detects whether the fault of the high-level service B has been restored.
  • Step 313 If the detection result is that the recovery is not yet completed, the high-level fault management system processes the fault of the high-level service.
  • the fault management system needs to handle the fault of the high-level service B.
  • the result of the detection is that the fault of the upper layer B is also restored, it can be determined that the fault of the upper layer B is caused by the fault of the lower layer service A, and the fault management system of the upper layer does not need to handle the fault of the upper layer B. If the test result is that the high-level service B has not failed, the high-level fault management system does not need to perform any processing.
  • the fault processing method provided in this embodiment detects, by the high-level fault management system, whether the high-level service indicated by the high-level affected service identifier carried in the fault-generating message is faulty during the period of saving the fault-generating message; As a result, if a fault occurs, the fault of the high-level service is not processed temporarily, so that it is possible to reduce unnecessary dispatching in the scenario where multiple operators operate the same mobile communication system at the same time, so as to avoid waste of material resources and human resources in the maintenance process. Effect.
  • the fault processing method provided by the embodiment further detects whether the fault of the high-level service indicated by the high-level affected service identifier carried in the fault recovery message has been recovered by the high-level fault management system; if the detection result is that the fault has not been recovered, the high-level service is processed.
  • the fault can be used to accurately locate the fault source of the high-level service between different operators in the scenario where multiple operators operate the same mobile communication system at the same time, and reasonably allocate the fault repair task.
  • FIG. 4 is a schematic structural diagram of a communication fault management system according to an embodiment of the present invention.
  • the communication fault management system includes at least one low level fault management system 400 and at least one high level fault management system 500.
  • the low-level fault management system 400 includes a fault handling device that can be implemented as part of the low-level fault management system 400 by software, hardware, or a combination of both.
  • the fault processing device includes: an alarm detection module 420, a relationship query module 440, and a message sending module 460;
  • the alarm detection module 420 is configured to detect a fault alarm situation in a low-level service.
  • the relationship query module 440 is configured to query, according to the fault alarm situation and the service dependency relationship table stored in the system, the affected high-level service;
  • a message sending module 460 configured to send a fault notification message to the high-level fault management system corresponding to the affected high-level service, so that the high-level fault management system receives the fault notification message sent by the low-level fault management system Determining, according to the fault notification message, whether the faulty high-level service needs to be processed;
  • the service dependency relationship table is a correspondence between a low-level service and a high-level service that depends on the operation of the low-level service.
  • the high level fault management system 500 includes a fault handling device that can be implemented as part of the high level fault management system 500 by software, hardware, or a combination of both.
  • the fault handling device includes: a message receiving module 520 and a fault handling module 540.
  • the message receiving module 520 is configured to receive a fault notification message sent by the low-level fault management system, where the fault notification message is that the low-level fault management system detects a fault alarm situation in a low-level service, according to the fault alarm situation and system storage.
  • the service dependency table query is sent to the high-level service that is affected, and then sent to the high-level fault management system corresponding to the affected high-level service;
  • the fault processing module 540 is configured to determine that the fault occurs according to the fault notification message. Whether the high-level business needs to be handled;
  • the service dependency relationship table is a correspondence between a low-level service and a high-level service that depends on the operation of the low-level service.
  • the communication fault processing system is configured by setting at least two layers of fault management systems, and when the low-level fault management system detects a fault alarm of a low-level service, according to the fault alarm situation and the service stored by the system.
  • the dependency table query obtains the affected high-level service; sends a fault notification message to the high-level fault management system corresponding to the affected high-level service, so that the high-level fault management system determines whether the faulty high-level service needs to be processed according to the fault notification message; Not In the scenario where the same mobile communication system is operated at the same time as the carrier, the existing fault management system may cause some operators to waste manpower or material resources during the fault maintenance process.
  • the low-level service fails, the high-level fault occurs.
  • the management system can determine whether the faulty high-level service needs to be processed according to the fault notification message to the faulty high-level service, thereby reducing the unnecessary waste of maintenance resources.
  • FIG. 5 is a schematic structural diagram of a communication fault management system according to another embodiment of the present invention.
  • the communication fault management system includes at least one low level fault management system 400 and at least one high level fault management system 500.
  • the low-level fault management system 400 includes a fault handling device that can be implemented as part of the low-level fault management system 400 by software, hardware, or a combination of both.
  • the fault processing device includes: an alarm detection module 420, a relationship query module 440, and a message sending module 460;
  • the alarm detection module 420 is configured to detect a fault alarm situation in a low-level service.
  • the relationship query module 440 is configured to query, according to the fault alarm situation and the service dependency relationship table stored in the system, the affected high-level service;
  • a message sending module 460 configured to send a fault notification message to the high-level fault management system corresponding to the affected high-level service, so that the high-level fault management system receives the fault notification message sent by the low-level fault management system Determining, according to the fault notification message, whether the faulty high-level service needs to be processed;
  • the service dependency relationship table is a correspondence between a low-level service and a high-level service that depends on the operation of the low-level service.
  • the fault alarm condition is a fault of a low-level service, B'J:
  • the message sending module 460 is configured to send a fault generating message to the high-level fault management system corresponding to the affected high-level service, where the fault generating message carries a high-level affected service identifier, and the high-level affected service Identifying a high-level service that is affected by a low-level service that indicates a fault alarm; and the high-level fault management system receives and saves the fault-generating message sent by the low-level fault management system; during the saving of the fault-generating message, And detecting whether the high-level service indicated by the high-level affected service identifier carried in the fault-generating message is faulty; if the detection result is a fault, the fault of the high-level service is not processed temporarily.
  • the message sending module 460 is configured to send the high level corresponding to the affected high-level service
  • the fault management system sends a fault recovery message, where the fault recovery message carries a high-level affected service identifier, where the high-level affected service identifier is used to indicate a high-level service affected by a low-level service in which a fault alarm occurs; Receiving the fault recovery message sent by the low-level fault management system; detecting whether the fault of the high-level service indicated by the high-level affected service identifier carried in the fault recovery message has been restored; if the detection result is that the fault has not been recovered, Handling the failure of the high-level business.
  • the fault generating message and the fault recovery message both carry a low-level service fault identifier and a fault type, where the low-layer service fault identifier is used to indicate the low-level service in which the fault alarm occurs;
  • the system searches for a fault-generating message that matches the fault-recovery message, where the matching means that the low-level service fault identifier and the fault type respectively included in the two messages are the same;
  • the fault occurrence message is deleted.
  • the high level fault management system 500 includes a fault handling device that can be implemented as part of the high level fault management system 500 by software, hardware, or a combination of both.
  • the fault handling device includes: a message receiving module 520, a fault handling module 540, a message matching module 562, and a message deleting module 564.
  • the message receiving module 520 is configured to receive a fault notification message sent by the low-level fault management system, where the fault notification message is that the low-level fault management system detects a fault alarm situation in a low-level service, according to the fault alarm situation and system storage.
  • the service dependency table query is sent to the high-level service that is affected, and then sent to the high-level fault management system corresponding to the affected high-level service;
  • the fault processing module 540 is configured to determine that the fault occurs according to the fault notification message. Whether the high-level business needs to be handled;
  • the service dependency relationship table is a correspondence between a low-level service and a high-level service that depends on the operation of the low-level service.
  • the message receiving module 520 is configured to receive and save a fault generating message sent by the low-level fault management system, where the fault generating message carries a high-level affected service identifier, where the high-level affected service identifier is used to indicate High-level services affected by low-level services with fault alarms;
  • the fault processing module 540 is configured to detect, during the saving of the fault generation message, whether a high-level service indicated by the high-level affected service identifier carried in the fault-generating message is faulty; if the detection result is a fault, The failure of the high-level business is not handled temporarily.
  • the fault processing module 540 includes: a first detecting unit and a first determining unit;
  • the first detecting unit is configured to: after receiving the fault generating message, detecting whether any one of the high-level affected service identifier carried in the fault generating message and the currently saved at least one high-level fault service identifier is the same
  • the high-level fault service identifier is used to indicate that a high-level service has failed;
  • the first determining unit is configured to: if the detection result is that the received high-level affected service identifier is the same as the currently stored high-level fault service identifier, determine the high-level affected service identifier carried in the fault generating message The indicated high-level business has failed.
  • the fault processing module 540 includes: an identifier obtaining unit, a second detecting unit, and a second determining unit;
  • the identifier obtaining unit is configured to: after detecting that a high-level service is faulty, obtain a corresponding high-level fault service identifier, where the high-level fault service identifier is used to indicate that a faulty high-level service is generated; and the second detecting unit is configured to use Detecting whether the obtained high-level fault service identifier and any one of the currently stored high-level affected service identifiers are the same;
  • the second determining unit is configured to determine, if the detection result is that the obtained high-level fault service identifier is the same as the currently saved high-level affected service identifier, determine the high-level affected service carried in the same fault generating message.
  • the high-level service indicated by the identifier is faulty.
  • the fault processing module 540 further includes: a third determining unit;
  • the third determining unit is configured to: if the detection result is that the obtained high-level fault service identifier is different from the current high-level affected service identifier, the processed high-level fault service identifier is processed. The failure of high-level business.
  • the message receiving module 520 is further configured to receive a fault recovery message sent by the low-level fault management system, where the fault recovery message carries the high-level affected service identifier;
  • the fault processing module 540 is further configured to detect whether a fault of the high-level service indicated by the high-level affected service identifier carried in the fault recovery message has been restored; if the detection result is that the fault has not been recovered, processing the high-level service failure.
  • the fault generating message and the fault recovery message both carry a low-level service fault identifier and a fault type, where the low-layer service fault identifier is used to indicate the low-level service in which the fault alarm occurs;
  • the device further includes: a message matching module 562 and a message deleting module 564;
  • the message matching module 562 is configured to search for a fault generating message that matches the fault recovery message, where the matching refers to the low-level service fault identifier and the fault class included in each of the two messages. The same type;
  • the message deletion module 564 is configured to delete the fault generation message when a fault occurrence message matching the fault recovery message is found.
  • the communication fault management system detects, by the high-level fault management system, whether the high-level service indicated by the high-level affected service identifier carried in the fault-generating message is faulty during the period of saving the fault-generating message; If the detection result is a fault, the fault of the high-level service will not be processed temporarily, so that it is possible to reduce unnecessary dispatching in the scenario where multiple operators operate the same mobile communication system at the same time, so as to avoid the physical resources and human resources of the maintenance process. The effect of wasting.
  • the communication fault management system provided by the embodiment further detects whether the fault of the high-level service indicated by the high-level affected service identifier carried in the fault recovery message has been recovered by the high-level fault management system; if the detection result is that the fault has not been recovered, the high-level service is processed.
  • the fault can be achieved in the scenario that multiple operators operate the same mobile communication system at the same time, accurately locate the fault source of the high-level service between different operators, and reasonably allocate the fault repair task.
  • FIG. 6 is a schematic structural diagram of a fault management system according to an embodiment of the present invention.
  • the fault management system is implemented as a low-level fault management system in a communication fault management system, and the system includes: a processor 620 , a memory 640 and a transmitter 660;
  • the processor 620 is configured to detect a fault alarm situation in a low-level service.
  • the processor 620 is further configured to query, according to the fault alarm situation and the service dependency table stored in the system in the memory 640, the affected high-level service;
  • the processor 620 is further configured to control the transmitter 660 to send a fault notification message to the high-level fault management system corresponding to the affected high-level service, so that the high-level fault management system receives the low-level fault management.
  • the fault notification message sent by the system determining, according to the fault notification message, whether the faulty high-level service needs to be processed;
  • the service dependency relationship table is a correspondence between a low-level service and a high-level service that depends on the operation of the low-level service.
  • the fault alarm condition is a low-level service failure
  • the processor 620 is further configured to: the transmitter 660 is configured to send a fault generating message to the high-level fault management system corresponding to the affected high-level service, where the fault generating message carries a high-level affected service identifier.
  • the high-level affected service identifier is used to indicate a low-level industry in which a fault alarm occurs.
  • the high-level service affected by the service; the high-level fault management system receives and saves the fault-generating message sent by the low-level fault management system; and during the saving of the fault-generating message, detects the fault-generated message Whether the high-level service indicated by the high-level affected service identifier is faulty; if the detection result is a fault, the fault of the high-level service is not processed temporarily.
  • the fault alarm condition is that the fault of a lower layer service has been recovered, then:
  • the processor 620 is further configured to control the transmitter 640 to send a fault recovery message to the high-level fault management system corresponding to the affected high-level service, where the fault recovery message carries a high-level affected service identifier.
  • the high-level affected service identifier is used to indicate a high-level service affected by a low-level service in which a fault alarm occurs; so that the high-level fault management system receives the fault recovery message sent by the low-level fault management system; and detects the fault recovery message. Whether the fault of the high-level service indicated by the high-level affected service identifier is recovered; if the detection result is that the fault has not been recovered, the fault of the high-level service is processed.
  • the fault generating message and the fault recovery message both carry a low-level service fault identifier and a fault type, where the low-layer service fault identifier is used to indicate the low-level service in which the fault alarm occurs;
  • the high-level fault management system searches for a fault-generating message that matches the fault-recovery message, where the matching means that the low-level service fault identifier and the fault type respectively included in the two messages are the same;
  • the fault recovery message matches the fault generation message, the fault generation message is deleted.
  • the fault management system detects, by the high-level fault management system, whether the high-level service indicated by the high-level affected service identifier carried in the fault-generating message is faulty during the period of saving the fault-generating message; As a result, if a fault occurs, the fault of the high-level service is not processed temporarily, so that it is possible to reduce unnecessary dispatching in the scenario where multiple operators operate the same mobile communication system at the same time, so as to avoid waste of material resources and human resources in the maintenance process. Effect.
  • the fault management system provided by the embodiment further detects whether the fault of the high-level service indicated by the high-level affected service identifier carried in the fault recovery message has been recovered by the high-level fault management system; if the detection result is that the fault has not been recovered, the high-level service is processed.
  • the fault can be used to accurately locate the fault source of the high-level service between different operators in the scenario where multiple operators operate the same mobile communication system at the same time, and reasonably allocate the fault repair task.
  • FIG. 7, shows a schematic structural diagram of a fault management system according to an embodiment of the present invention.
  • the fault management system is implemented as a high-level fault management system in a communication fault management system, and the system includes: a receiver 720, a processor 740, and a memory 760;
  • the processor 740 is configured to control the receiver 720 to receive a fault notification message sent by the low-level fault management system, where the fault notification message is that the low-level fault management system detects a fault alarm situation in a low-level service, according to the The fault alarm situation and the service dependency table stored by the system are queried to obtain the affected high-level service, and then sent to the high-level fault management system corresponding to the affected high-level service;
  • the processor 740 is further configured to determine, according to the fault notification message, whether a faulty high-level service needs to be processed;
  • the service dependency relationship table is a correspondence between a low-level service and a high-level service that depends on the operation of the low-level service.
  • the processor 740 is further configured to control the receiver 720 to receive a fault generation message sent by the low-level fault management system, and save the message to the memory 760, where the fault is generated. Carrying a high-level affected service identifier, where the high-level affected service identifier is used to indicate a high-level service affected by a low-level service in which a fault alarm occurs;
  • the processor 740 is further configured to: when the memory saves the fault generating message, detecting whether a high-level service indicated by the high-level affected service identifier carried in the fault generating message is faulty;
  • the processor 740 is further configured to temporarily not process the fault of the high-level service if the detection result is a fault.
  • the processor 740 is further configured to: after controlling the receiver 720 to receive the fault generating message, detecting the high-level affected service identifier carried by the fault generating message and Whether any one of the at least one high-level fault service identifiers currently stored by the memory 760 is the same, and the high-level fault service identifier is used to indicate that a faulty high-level service occurs;
  • the processor 740 is further configured to: if the detection result is that the received high-level affected service identifier is the same as the currently stored high-level fault service identifier, determine the high-level affected service identifier carried in the fault generating message. The indicated high-level business has failed.
  • the processor 740 is further configured to: after detecting a fault of a high-level service, obtain a corresponding high-level fault service identifier, where the high-level fault service identifier is used to indicate that a fault has occurred.
  • the processor 740 is further configured to detect the obtained high-level fault service identifier and the storage The processor 740 is further configured to: if the detection result is the acquired high-level fault service identifier and a currently saved high-level If the affected service identifiers are the same, the high-level service indicated by the high-level affected service identifier carried in the same fault-generating message is determined to be faulty.
  • the processor 740 is further configured to: if the detection result is that the obtained high-level fault service identifier is different from all currently stored high-level affected service identifiers, the processed The fault of the high-level service indicated by the high-level fault service identifier.
  • the processor 740 is further configured to control the receiver to receive a fault recovery message sent by the low-level fault management system, where the fault recovery message carries the high-level affected service identifier. ;
  • the processor 740 is further configured to detect whether a fault of the high-level service indicated by the high-level affected service identifier carried in the fault recovery message has been restored;
  • the processor 740 is further configured to process the fault of the high-level service if the detection result is that the recovery is not yet completed.
  • the fault generating message and the fault recovery message both carry a low-level service fault identifier and a fault type, where the low-layer service fault identifier is used to indicate the low-level service in which the fault alarm occurs;
  • the processor 740 is further configured to search for a fault-generating message that is matched with the fault recovery message, where the matching is that the low-level service fault identifier and the fault type that are respectively included in the two messages are the same;
  • the processor 740 is further configured to delete the fault generation message when a fault occurrence message matching the fault recovery message is found.
  • the fault management system detects, by the high-level fault management system, whether the high-level service indicated by the high-level affected service identifier carried in the fault-generating message is faulty during the period of saving the fault-generating message; As a result, if a fault occurs, the fault of the high-level service is not processed temporarily, so that it is possible to reduce unnecessary dispatching in the scenario where multiple operators operate the same mobile communication system at the same time, so as to avoid waste of material resources and human resources in the maintenance process. Effect.
  • the fault management system provided by the embodiment further detects whether the fault of the high-level service indicated by the high-level affected service identifier carried in the fault recovery message has been recovered by the high-level fault management system; if the detection result is that the fault has not been recovered, the high-level service is processed. Trouble, so that it is possible to accurately locate high-level services between different operators in a scenario where multiple operators operate the same mobile communication system at the same time.
  • the obstacle source, the effect of properly allocating the fault repair task please refer to FIG. 8, which shows a block diagram of the structure of the communication fault management system provided by one embodiment of the present invention.
  • the system includes at least one low level fault management system 820 and at least one high level fault management system 840;
  • the low-level fault management system 820 is a fault management system as described in the more preferred embodiment of the embodiment shown in FIG. 6 and the embodiment shown in FIG. 6;
  • the high-level fault management system 840 is a fault management system as described in the more preferred embodiment of the embodiment shown in FIG. 7 and the embodiment shown in FIG.
  • Computer readable media includes both computer storage media and communication media, including communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a storage medium may be any available media that can be accessed by a computer.
  • computer readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage media or other magnetic storage device, or can be used for carrying or storing in the form of an instruction or data structure.
  • the desired program code and any other medium that can be accessed by the computer may suitably be a computer readable medium.
  • the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable , fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, wireless, and microwaves are included in the fixing of the associated media.
  • coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, wireless, and microwaves are included in the fixing of the associated media.
  • a disk and a disc include a compact disc (CD), a laser disc, a disc, a digital versatile disc (DVD), a floppy disk, and a Blu-ray disc, wherein the disc is usually magnetically copied, and the disc is The laser is used to optically replicate the data. Combinations of the above should also be included within the scope of protection of computer readable media.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Telephonic Communication Services (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Maintenance And Management Of Digital Transmission (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明实施例提供了一种故障处理方法、装置和系统，涉及通信领域，所述方法包括：低层故障管理系统检测低层业务中的故障告警情况；低层故障管理系统根据故障告警情况和系统存储的业务依赖关系表查询得到受影响的高层业务；低层故障管理系统向受影响的高层业务所对应的高层故障管理系统发送故障通知消息；高层故障管理系统根据故障通知消息确定发生故障的高层业务是否需要处理。本发明达到了当低层业务发生故障时，高层故障管理系统可以根据故障通知消息对发生故障的高层业务确定发生故障的高层业务是否需要处理，从而减少不必要的维护资源浪费的效果。

Description

说 明 书 故障处理方法、 装置和系统 技术领域
本发明涉及通信领域， 特别涉及一种故障处理方法、 装置和系统。 背景技术
故障管理系统是移动通信系统中的重要组成部分之一，主要提供针对移动 通信系统的故障定位和故障处理。
目前， 不同的运营商往往运营不同的移动通信系统， 一个具体的移动通信 系统通常都是由单独的一个运营商来运营， 所以故障管理系统也 ^^于一个运 营商的架构设计的。 具体来讲， 移动通信系统通常包括有基础设施组成部分、 传输组成部分和无线业务组成部分， 由于这些组成部分都是由同一个运营商管 理， 所以故障管理系统也是同时应用于这些组成部分， 不论是故障定位还是故 障处理， 均在该运营商内部完成。 当故障管理系统定位到故障后， 会产生相应 的派工单发送到运营商的维护人员。
但是随着云计算技术的发展， 同一个移动通信系统逐渐细分由多个运营商 管理。 也即， 移动通信系统中的不同组成部分可以由不同运营商运营。 此时， 故障管理系统在检测到一个业务故障时， 可能需要向不同运营商都发送故障告 警， 但实际故障原因可能仅出现在一个运营商所运营的组成部分， 导致了其它 运营商在故障维护过程对人力或者物力的浪费。 发明内容
为了解决在不同运营商同时运营同一个移动通信系统的场景下， 现有的故 障管理系统可能会导致一些运营商在故障维护过程对人力或者物力造成浪费 的问题， 本发明实施例提供了一种故障处理方法、 装置和系统。 所述技术方案 ：¾口下：
第一方面， 提供了一种故障处理方法， 用于通信故障管理系统中的低层故 障管理系统， 所述通信故障管理系统包括至少一个低层故障管理系统和至少一 个高层故障管理系统， 所述方法包括：
检测低层业务中的故障告警情况； 根据所述故障告警情况和系统存储的业务依赖关系表查询得到受影响的 高层业务；
向所述受影响的高层业务所对应的所述高层故障管理系统发送故障通知 消息， 以便所述高层故障管理系统接收所述低层故障管理系统发送的所述故障 通知消息； 根据所述故障通知消息确定发生故障的高层业务是否需要处理； 其中， 所述业务依赖关系表是低层业务与依赖所述低层业务运行的高层业 务之间的对应关系。
在第一方面的第一种可能的实施方式中， 若所述故障告警情况为一个低层 业务发生故障， 则所述向所述受影响的高层业务所对应的所述高层故障管理系 统发送故障通知消息， 包括：
向所述受影响的高层业务所对应的所述高层故障管理系统发送故障产生 消息， 所述故障产生消息携带有高层受影响业务标识， 所述高层受影响业务标 识用于指示发生故障告警的低层业务所影响的高层业务； 以便所述高层故障管 理系统接收并保存所述低层故障管理系统发送的所述故障产生消息； 在保存所 述故障产生消息的期间，检测所述故障产生消息中携带的高层受影响业务标识 所指示的高层业务是否发生故障； 若检测结果为发生故障， 则暂不处理所述高 层业务的故障。
结合第一方面的第一种可能的实施方式， 在第二种可能的实施方式中， 其 特征在于， 若所述故障告警情况为一个低层业务的故障已经恢复， 则所述向所 述受影响的高层业务所对应的所述高层故障管理系统发送故障通知消息， 包 括：
向所述受影响的高层业务所对应的所述高层故障管理系统发送故障恢复 消息， 所述故障恢复消息携带有高层受影响业务标识， 所述高层受影响业务标 识用于指示发生故障告警的低层业务所影响的高层业务； 以便所述高层故障管 理系统接收所述低层故障管理系统发送的所述故障恢复消息； 检测所述故障恢 复消息携带的所述高层受影响业务标识所指示的高层业务的故障是否已经恢 复； 若检测结果为还未恢复， 则处理所述高层业务的故障。
结合第一方面的第二种可能的实施方式， 在第三种可能的实施方式中， 所 述故障产生消息和所述故障恢复消息都还携带有低层业务故障标识和故障类 型， 所述低层业务故障标识用于指示所述发生故障告警的低层业务； 以便所述 高层故障管理系统查找与所述故障恢复消息匹配的故障产生消息， 所述匹配是 指两个消息各自所包括的所述低层业务故障标识和所述故障类型均相同； 在查 找到与所述故障恢复消息匹配的故障产生消息时， 删除所述故障产生消息。
第二方面， 提供了一种故障处理方法， 用于通信故障管理系统中的高层故 障管理系统， 所述通信故障管理系统包括至少一层低层故障管理系统和至少一 层高层故障管理系统， 所述方法包括：
接收所述低层故障管理系统发送的故障通知消息， 所述故障通知消息是所 述低层故障管理系统检测低层业务中的故障告警情况，根据所述故障告警情况 和系统存储的业务依赖关系表查询得到受影响的高层业务， 然后向所述受影响 的高层业务所对应的所述高层故障管理系统发送的；
根据所述故障通知消息确定发生故障的高层业务是否需要处理； 其中， 所述业务依赖关系表是低层业务与依赖所述低层业务运行的高层业 务之间的对应关系。
在第二方面的第一种可能的实施方式中， 所述接收所述低层故障管理系统 发送的故障通知消息， 包括：
接收并保存所述低层故障管理系统发送的故障产生消息， 所述故障产生消 息携带有高层受影响业务标识， 所述高层受影响业务标识用于指示发生故障告 警的低层业务所影响的高层业务；
所述根据所述故障通知消息确定发生故障的高层业务是否需要处理， 包 括：
在保存所述故障产生消息的期间，检测所述故障产生消息中携带的高层受 影响业务标识所指示的高层业务是否发生故障；
若检测结果为发生故障， 则暂不处理所述高层业务的故障。
结合第二方面的第一种可能的实施方式， 在第二种可能的实施方式中， 所 述在保存所述故障产生消息的期间，检测所述故障产生消息中携带的高层受影 响业务标识所指示的高层业务是否发生故障， 包括：
在接收到所述故障产生消息后，检测所述故障产生消息携带的所述高层受 影响业务标识和当前保存的至少一个高层故障业务标识中的任意一个是否相 同， 所述高层故障业务标识用于指示发生了故障的高层业务；
若检测结果为接收到的所述高层受影响业务标识和当前保存的一个高层 故障业务标识相同， 则确定所述故障产生消息中携带的高层受影响业务标识所 指示的高层业务发生故障。 结合第二方面的第一种可能的实施方式， 在第三种可能的实施方式中， 所 述在保存所述故障产生消息的期间，检测所述故障产生消息中携带的高层受影 响业务标识所指示的高层业务是否发生故障， 包括：
在检测到一个高层业务发生故障后， 获取对应的高层故障业务标识， 所述 高层故障业务标识用于指示发生了故障的高层业务；
检测获取到的所述高层故障业务标识和当前保存的至少一个所述高层受 影响业务标识中的任意一个是否相同；
若检测结果为获取到的所述高层故障业务标识和当前保存的一个高层受 影响业务标识相同， 则确定相同的所述故障产生消息中携带的高层受影响业务 标识所指示的高层业务发生故障。
结合第二方面的第三种可能的实施方式， 在第四种可能的实施方式中， 所 述检测获取到的所述高层故障业务标识和预先保存的至少一个所述高层受影 响业务标识中的任意一个是否相同之后， 还包括：
若检测结果为获取到的所述高层故障业务标识和当前保存的所有高层受 影响业务标识均不相同， 则处理获取到的所述高层故障业务标识所指示的高层 业务的故障。
结合第二方面的第一种、 第二种、 第三种和第四种可能的实施方式， 在第 五种可能的实施方式中， 所述接收所述低层故障管理系统发送的故障通知消 息， 包括：
接收所述低层故障管理系统发送的故障恢复消息， 所述故障恢复消息携带 有所述高层受影响业务标识；
所述根据所述故障通知消息确定发生故障的高层业务是否需要处理， 包 括：
检测所述故障恢复消息携带的所述高层受影响业务标识所指示的高层业 务的故障是否已经恢复；
若检测结果为还未恢复， 则处理所述高层业务的故障。
结合第二方面的第五种可能的实施方式， 在第六种可能的实施方式中， 所 述故障产生消息和所述故障恢复消息都还携带有低层业务故障标识和故障类 型， 所述低层业务故障标识用于指示所述发生故障告警的低层业务；
所述接收所述低层故障管理系统发送的故障恢复消息之后， 还包括： 查找与所述故障恢复消息匹配的故障产生消息， 所述匹配是指两个消息各 自所包括的所述低层业务故障标识和所述故障类型均相同；
在查找到与所述故障恢复消息匹配的故障产生消息时， 删除所述故障产生 消息。 第三方面， 提供了一种故障处理装置， 用于通信故障管理系统中的低层故 障管理系统， 所述通信故障管理系统包括至少一个低层故障管理系统和至少一 个高层故障管理系统， 所述装置包括：
告警检测模块， 用于检测低层业务中的故障告警情况；
关系查询模块， 用于根据所述故障告警情况和系统存储的业务依赖关系表 查询得到受影响的高层业务；
消息发送模块， 用于向所述受影响的高层业务所对应的所述高层故障管理 系统发送故障通知消息， 以便所述高层故障管理系统接收所述低层故障管理系 统发送的所述故障通知消息； 根据所述故障通知消息确定发生故障的高层业务 是否需要处理；
其中， 所述业务依赖关系表是低层业务与依赖所述低层业务运行的高层业 务之间的对应关系。
在第三方面的第一种可能的实施方式中， 若所述故障告警情况为一个低层 业务发生故障， 贝' J :
所述消息发送模块， 用于向所述受影响的高层业务所对应的所述高层故障 管理系统发送故障产生消息， 所述故障产生消息携带有高层受影响业务标识， 所述高层受影响业务标识用于指示发生故障告警的低层业务所影响的高层业 务； 以便所述高层故障管理系统接收并保存所述低层故障管理系统发送的所述 故障产生消息； 在保存所述故障产生消息的期间， 检测所述故障产生消息中携 带的高层受影响业务标识所指示的高层业务是否发生故障； 若检测结果为发生 故障， 则暂不处理所述高层业务的故障。
结合第三方面的第二种可能的实施方式， 在第三种可能的实施方式中， 若 所述故障告警情况为一个低层业务的故障已经恢复， 贝' J :
所述消息发送模块， 用于向所述受影响的高层业务所对应的所述高层故障 管理系统发送故障恢复消息， 所述故障恢复消息携带有高层受影响业务标识， 所述高层受影响业务标识用于指示发生故障告警的低层业务所影响的高层业 务； 以便所述高层故障管理系统接收所述低层故障管理系统发送的所述故障恢 复消息；检测所述故障恢复消息携带的所述高层受影响业务标识所指示的高层 业务的故障是否已经恢复； 若检测结果为还未恢复， 则处理所述高层业务的故 障。
结合第三方面的第三种可能的实施方式， 在第四种可能的实施方式中， 所 述故障产生消息和所述故障恢复消息都还携带有低层业务故障标识和故障类 型， 所述低层业务故障标识用于指示所述发生故障告警的低层业务； 以便所述 高层故障管理系统查找与所述故障恢复消息匹配的故障产生消息， 所述匹配是 指两个消息各自所包括的所述低层业务故障标识和所述故障类型均相同； 在查 找到与所述故障恢复消息匹配的故障产生消息时， 删除所述故障产生消息。
第四方面， 提供了一种故障处理装置， 用于通信故障管理系统中的高层故 障管理系统， 所述通信故障管理系统包括至少一层低层故障管理系统和至少一 层高层故障管理系统， 所述装置包括：
消息接收模块， 用于接收所述低层故障管理系统发送的故障通知消息， 所 述故障通知消息是所述低层故障管理系统检测低层业务中的故障告警情况，根 据所述故障告警情况和系统存储的业务依赖关系表查询得到受影响的高层业 务， 然后向所述受影响的高层业务所对应的所述高层故障管理系统发送的； 故障处理模块， 用于根据所述故障通知消息确定发生故障的高层业务是否 需要处理；
其中， 所述业务依赖关系表是低层业务与依赖所述低层业务运行的高层业 务之间的对应关系。
在第四方面的第一种可能的实施方式中， 所述消息接收模块， 用于接收并 保存所述低层故障管理系统发送的故障产生消息， 所述故障产生消息携带有高 层受影响业务标识， 所述高层受影响业务标识用于指示发生故障告警的低层业 务所影响的高层业务；
所述故障处理模块， 用于在保存所述故障产生消息的期间， 检测所述故障 产生消息中携带的高层受影响业务标识所指示的高层业务是否发生故障； 若检 测结果为发生故障， 则暂不处理所述高层业务的故障。
结合第四方面的第一种可能的实施方式， 在第二种可能的实施方式中， 所 述故障处理模块， 包括： 第一检测单元和第一确定单元；
所述第一检测单元， 用于在接收到所述故障产生消息后， 检测所述故障产 生消息携带的所述高层受影响业务标识和当前保存的至少一个高层故障业务 标识中的任意一个是否相同， 所述高层故障业务标识用于指示发生了故障的高 层业务；
所述第一确定单元， 用于若检测结果为接收到的所述高层受影响业务标识 和当前保存的一个高层故障业务标识相同， 则确定所述故障产生消息中携带的 高层受影响业务标识所指示的高层业务发生故障。
结合第四方面的第一种可能的实施方式， 在第三种可能的实施方式中， 所 述故障处理模块， 包括： 标识获取单元、 第二检测单元和第二确定单元； 所述标识获取单元， 用于在检测到一个高层业务发生故障后， 获取对应的 高层故障业务标识， 所述高层故障业务标识用于指示发生了故障的高层业务； 所述第二检测单元， 用于检测获取到的所述高层故障业务标识和当前保存 的至少一个所述高层受影响业务标识中的任意一个是否相同；
所述第二确定单元， 用于若检测结果为获取到的所述高层故障业务标识和 当前保存的一个高层受影响业务标识相同， 则确定相同的所述故障产生消息中 携带的高层受影响业务标识所指示的高层业务发生故障。
结合第四方面的第三种可能的实施方式， 在第四种可能的实施方式中， 所 述故障处理模块， 还包括： 第三确定单元；
所述第三确定单元， 用于若检测结果为获取到的所述高层故障业务标识和 当前保存的所有高层受影响业务标识均不相同， 则处理获取到的所述高层故障 业务标识所指示的高层业务的故障。
结合第四方面的第一种、 第二种、 第三种和第四种可能的实施方式， 在第 五种可能的实施方式中， 所述消息接收模块， 还用于接收所述低层故障管理系 统发送的故障恢复消息， 所述故障恢复消息携带有所述高层受影响业务标识； 所述故障处理模块，还用于检测所述故障恢复消息携带的所述高层受影响 业务标识所指示的高层业务的故障是否已经恢复； 若检测结果为还未恢复， 则 处理所述高层业务的故障。
结合第四方面的第五种可能的实施方式， 在第六种可能的实施方式中， 所 述故障产生消息和所述故障恢复消息都还携带有低层业务故障标识和故障类 型， 所述低层业务故障标识用于指示所述发生故障告警的低层业务；
所述装置， 还包括： 消息匹配模块和消息删除模块；
所述消息匹配模块， 用于查找与所述故障恢复消息匹配的故障产生消息， 所述匹配是指两个消息各自所包括的所述低层业务故障标识和所述故障类型 均相同；
所述消息删除模块， 用于在查找到与所述故障恢复消息匹配的故障产生消 息时， 删除所述故障产生消息。
第五方面， 提供了一种通信故障管理系统， 所述系统包括至少一个低层故 障管理系统和至少一个高层故障管理系统；
所述低层故障管理系统包括如第三方面和第三方面的各种可能的实施方 式中任一所述的故障处理装置；
所述高层故障管理系统包括如第四方面和第四方面的各种可能的实施方 式中任一所述的故障处理装置。
第六方面， 提供了一种故障管理系统， 用于实现为通信故障管理系统中的 低层故障管理系统， 所述通信故障管理系统包括至少一层低层故障管理系统和 至少一层高层故障管理系统， 所述系统包括： 处理器、 存储器和发送器； 所述处理器， 用于检测低层业务中的故障告警情况；
所述处理器，还用于根据所述故障告警情况和所述存储器中系统存储的业 务依赖关系表查询得到受影响的高层业务；
所述处理器，还用于控制所述发送器向所述受影响的高层业务所对应的所 述高层故障管理系统发送故障通知消息， 以便所述高层故障管理系统接收所述 低层故障管理系统发送的所述故障通知消息； 根据所述故障通知消息确定发生 故障的高层业务是否需要处理；
其中， 所述业务依赖关系表是低层业务与依赖所述低层业务运行的高层业 务之间的对应关系。
在第六方面的第一种可能的实施方式中， 若所述故障告警情况为一个低层 业务发生故障， 贝' J :
所述处理器，还用于控制所述发送器向所述受影响的高层业务所对应的所 述高层故障管理系统发送故障产生消息， 所述故障产生消息携带有高层受影响 业务标识， 所述高层受影响业务标识用于指示发生故障告警的低层业务所影响 的高层业务； 以便所述高层故障管理系统接收并保存所述低层故障管理系统发 送的所述故障产生消息； 在保存所述故障产生消息的期间， 检测所述故障产生 消息中携带的高层受影响业务标识所指示的高层业务是否发生故障； 若检测结 果为发生故障， 则暂不处理所述高层业务的故障。
结合第六方面的第一种可能的实施方式， 在第二种可能的实施方式中， 若 所述故障告警情况为一个低层业务的故障已经恢复， 贝' J :
所述处理器，还用于控制所述发送器向所述受影响的高层业务所对应的所 述高层故障管理系统发送故障恢复消息， 所述故障恢复消息携带有高层受影响 业务标识， 所述高层受影响业务标识用于指示发生故障告警的低层业务所影响 的高层业务； 以便所述高层故障管理系统接收所述低层故障管理系统发送的所 述故障恢复消息； 检测所述故障恢复消息携带的所述高层受影响业务标识所指 示的高层业务的故障是否已经恢复； 若检测结果为还未恢复， 则处理所述高层 业务的故障。
结合第六方面的第二种可能的实施方式， 在第三种可能的实施方式中， 所 述故障产生消息和所述故障恢复消息都还携带有低层业务故障标识和故障类 型， 所述低层业务故障标识用于指示所述发生故障告警的低层业务； 以便所述 高层故障管理系统查找与所述故障恢复消息匹配的故障产生消息， 所述匹配是 指两个消息各自所包括的所述低层业务故障标识和所述故障类型均相同； 在查 找到与所述故障恢复消息匹配的故障产生消息时， 删除所述故障产生消息。
第七方面， 提供了一种故障处理系统， 用于实现为通信故障管理系统中的 高层故障管理系统， 所述通信故障管理系统包括至少一层低层故障管理系统和 至少一层高层故障管理系统， 所述系统包括： 接收器、 处理器和存储器； 所述处理器， 用于控制所述接收器接收所述低层故障管理系统发送的故障 通知消息， 所述故障通知消息是所述低层故障管理系统检测低层业务中的故障 告警情况，根据所述故障告警情况和系统存储的业务依赖关系表查询得到受影 响的高层业务， 然后向所述受影响的高层业务所对应的所述高层故障管理系统 发送的；
所述处理器，还用于根据所述故障通知消息确定发生故障的高层业务是否 需要处理；
其中， 所述业务依赖关系表是低层业务与依赖所述低层业务运行的高层业 务之间的对应关系。
在第七方面的第一种可能的实施方式中， 所述处理器， 还用于控制所述接 收器接收所述低层故障管理系统发送的故障产生消息， 并保存至所述存储器， 所述故障产生消息携带有高层受影响业务标识， 所述高层受影响业务标识用于 指示发生故障告警的低层业务所影响的高层业务；
所述处理器， 还用于在所述存储器保存所述故障产生消息的期间， 检测所 述故障产生消息中携带的高层受影响业务标识所指示的高层业务是否发生故 障；
所述处理器， 还用于若检测结果为发生故障， 则暂不处理所述高层业务的 故障。
结合第七方面的第一种可能的实施方式， 在第二种可能的实施方式中， 所 述处理器， 还用于在控制所述接收器接收到所述故障产生消息后， 检测所述故 障产生消息携带的所述高层受影响业务标识和所述存储器当前保存的至少一 个高层故障业务标识中的任意一个是否相同， 所述高层故障业务标识用于指示 发生了故障的高层业务；
所述处理器，还用于若检测结果为接收到的所述高层受影响业务标识和当 前保存的一个高层故障业务标识相同， 则确定所述故障产生消息中携带的高层 受影响业务标识所指示的高层业务发生故障。
结合第七方面的第一种可能的实施方式， 在第三种可能的实施方式中， 所 述处理器， 还用于在检测到一个高层业务发生故障后， 获取对应的高层故障业 务标识， 所述高层故障业务标识用于指示发生了故障的高层业务；
所述处理器，还用于检测获取到的所述高层故障业务标识和所述存储器当 前保存的至少一个所述高层受影响业务标识中的任意一个是否相同；
所述处理器，还用于若检测结果为获取到的所述高层故障业务标识和当前 保存的一个高层受影响业务标识相同， 则确定相同的所述故障产生消息中携带 的高层受影响业务标识所指示的高层业务发生故障。
结合第七方面的第三种可能的实施方式， 在第四种可能的实施方式中， 所 述处理器，还用于若检测结果为获取到的所述高层故障业务标识和当前保存的 所有高层受影响业务标识均不相同， 则处理获取到的所述高层故障业务标识所 指示的高层业务的故障。
结合第七方面的第一种、 第二种、 第三种和第四种可能的实施方式， 在第 五种可能的实施方式中， 所述处理器， 还用于控制所述接收器接收所述低层故 障管理系统发送的故障恢复消息， 所述故障恢复消息携带有所述高层受影响业 务标识；
所述处理器，还用于检测所述故障恢复消息携带的所述高层受影响业务标 识所指示的高层业务的故障是否已经恢复；
所述处理器，还用于若检测结果为还未恢复，则处理所述高层业务的故障。 结合第七方面的第五种可能的实施方式， 在第六种可能的实施方式中， 所 述故障产生消息和所述故障恢复消息都还携带有低层业务故障标识和故障类 型， 所述低层业务故障标识用于指示所述发生故障告警的低层业务；
所述处理器， 还用于查找与所述故障恢复消息匹配的故障产生消息， 所述 匹配是指两个消息各自所包括的所述低层业务故障标识和所述故障类型均相 同；
所述处理器， 还用于在查找到与所述故障恢复消息匹配的故障产生消息 时， 删除所述故障产生消息。
第八方面， 提供了一种通信故障管理系统， 所述系统包括至少一个低层故 障管理系统和至少一个高层故障管理系统；
所述低层故障管理系统是如第六方面和第六方面的各种可能的实施方式 中任一所述的故障管理系统；
所述高层故障管理系统是如第七方面和第七方面的各种可能的实施方式 中任一所述的故障管理系统。
本发明实施例提供的技术方案的有益效果是：
通过设置至少两层故障管理系统， 并由低层故障管理系统在检测到低层业 务的故障告警情况时，根据故障告警情况和系统存储的业务依赖关系表查询得 到受影响的高层业务； 向受影响的高层业务所对应的高层故障管理系统发送故 障通知消息，使得高层故障管理系统根据故障通知消息确定发生故障的高层业 务是否需要处理； 解决了在不同运营商同时运营同一个移动通信系统的场景 下， 现有的故障管理系统可能会导致一些运营商在故障维护过程对人力或者物 力造成浪费的问题； 达到了当低层业务发生故障时， 高层故障管理系统可以根 据故障通知消息对发生故障的高层业务确定发生故障的高层业务是否需要处 理， 从而减少不必要的维护资源浪费的效果。 附图说明
为了更清楚地说明本发明实施例中的技术方案， 下面将对实施例描述中所 需要使用的附图作筒单地介绍， 显而易见地， 下面描述中的附图仅仅是本发明 的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下， 还可以根据这些附图获得其他的附图。
图 1是本发明实施例所涉及的一种实施环境的结构示意图； 图 2是本发明一个实施例提供的故障处理方法的方法流程图； 图 3A是本发明另一实施例提供的故障处理方法的方法流程图；
图 3B是图 3A提供的故障处理方法中的步骤 305的子步骤流程图； 图 3C是图 3A提供的故障处理方法中的步骤 305的子步骤流程图； 图 4是本发明一个实施例提供的通信故障管理系统的结构方框图； 图 5是本发明另一实施例提供的通信故障管理系统的结构方框图； 图 6是本发明一个实施例提供的故障管理系统的结构方框图；
图 7是本发明另一实施例提供的故障管理系统的结构方框图； 和
图 8是本发明一个实施例提供的通信故障管理系统的结构方框图。 具体实施方式
为使本发明的目的、 技术方案和优点更加清楚， 下面将结合附图对本发明 实施方式作进一步地详细描述。
请参考图 1 ,其示出了本发明实施例所涉及的一种实施环境的结构示意图。 该实施环境是移动通信系统， 该移动通信系统包括有基础设备组成部分 120、 传输组成部分 140和无线业务组成部分 160。
不同的组成部分之间存在上下层级的关系， 所以在业务承载上存在相互影 响和相互依赖的关系。 具体来讲：
无线业务组成部分 160位于最高层， 则无线业务组成部分 160上的业务的 正常运行，依赖于传输组成部分 140上的业务或者基础设备组成部分 120上的 业务的正常运行。 比如， 假设无线业务组成部分 160上提供的业务包括小区 1 和小区 2, 传输组成部分 140上提供的业务包括传输链路 1 , 基础设备组成部 分 120上提供的业务包括传输单板 1和基带单板 1。 该小区 1的正常运行依赖 于传输链路 1和传输单板 1的正常运行； 小区 2的正常运行依赖于基带单板 1 的正常运行。
而传输组成部分 140位于基础设备组成部分 120的上层， 则传输组成部分 140上的业务的正常运行，依赖于基础设备组成部分 120上的业务的正常运行。 比如， 传输链路 1的正常运行依赖于传输单板 1的正常运行。 这种高层业务的 正常运行需要依赖低层业务的正常运行的对应关系， 可以称之为业务依赖关 系。
当移动通信系统中的不同组成部分由不同运营商运营时， 可以分别为不同 运营商设置不同的故障管理系统。 对应于不同组成部分的上下层级关系， 各个 组成部分所对应的故障管理系统也分为多层。 其中， 每两层故障管理系统中， 位于下层的故障管理系统称之为低层故障管理系统，位于上层的故障管理系统 称之为高层故障管理系统。比如，在无线业务组成部分 160与传输组成部分 140 之间， 无线业务组成部分 160所对应的故障管理系统是高层故障管理系统， 传 输组成部分 140所对应的故障管理系统是低层故障管理系统； 又比如， 在传输 组成部分 140和基础设备组成部分 120之间，传输组成部分 140所对应的故障 管理系统是高层故障管理系统，基础设备组成部分 120所对应的故障管理系统 是低层故障管理系统；再比如，无线业务组成部分 160和基础设备组成部分 120 之间， 无线业务组成部分 160所对应的故障管理系统是高层故障管理系统， 基 础设备组成部分 120所对应的故障管理系统是低层故障管理系统。
上述的移动通信系统的层级划分仅为举例说明， 在不同的实施例中， 对移 动通信系统的划分结构可能各不相同，对此不作具体限定。另外需要说明的是， 为例便于描述， 本文中所述的 "业务"泛指移动通信系统中的物理设施、 资源、 服务和业务等组成部分， 比如小区、 基站、 传输链路、 传输单板、 基带单板等 等均统称为业务。 请参考图 2, 其示出了本发明一个实施例提供的故障处理方法的方法流程 图。 该故障处理方法用于通信故障管理系统中， 该通信故障管理系统包括至少 一个低层故障管理系统和至少一个高层故障管理系统。该故障处理方法，包括： 步骤 201 , 低层故障管理系统检测低层业务中的故障告警情况；
低层故障管理系统检测低层业务中的故障告警情况。故障告警情况分为两 种： 一个低层业务发生故障； 或者， 一个低层业务的故障已经恢复。
比如， 低层故障管理系统检测到低层业务 A发生了故障， 或者， 低层故障 管理系统检测到低层业务 A发生的故障已经恢复。
步骤 202, 低层故障管理系统根据故障告警情况和系统存储的业务依赖关 系表查询得到受影响的高层业务；
一种实现方式下， 低层故障管理系统预先配置存储有业务依赖关系表， 业 务依赖关系表是低层业务与依赖该低层业务运行的高层业务之间的对应关系。 另一种实现方式下，低层故障管理系统中存储的业务依赖关系表可以根据业务 之间的运行情况而动态生成。 比如， 低层业务 A与高层业务 B存在业务依赖关系， 也即高层业务 B的 运行依赖于低层业务 A。
当低层故障管理系统检测到故障告警情况时，根据故障告警情况和系统存 储的业务依赖关系表查询得到受影响的高层业务。
比如， 低层故障管理系统查询到受影响的高层业务为 B。
步骤 203 , 低层故障管理系统向受影响的高层业务所对应的高层故障管理 系统发送故障通知消息；
低层故障管理系统向受影响的高层业务 B 所对应的高层故障管理系统发 送故障通知消息。 故障通知消息分为两种： 故障产生消息和故障恢复消息。
若故障告警情况是低层业务发生故障， 则发送故障产生消息；
若故障告警情况是低层业务的故障已经恢复， 则发送故障恢复消息。
步骤 204,高层故障管理系统接收低层故障管理系统发送的故障通知消息； 步骤 205 , 高层故障管理系统根据故障通知消息确定发生故障的高层业务 是否需要处理。
高层故障管理系统根据故障通知消息确定发生故障的高层业务是否可能 由低层业务的故障所导致；
若可能由低层业务的故障所导致， 则暂不处理该高层业务的故障， 以减少 不必要的维修资源浪费；
若不可能由低层业务的故障所导致， 则处理该高层业务的故障。
综上所述， 本实施例提供的故障处理方法， 通过设置至少两层故障管理系 统， 并由低层故障管理系统在检测到低层业务的故障告警情况时， 根据故障告 警情况和系统存储的业务依赖关系表查询得到受影响的高层业务； 向受影响的 高层业务所对应的高层故障管理系统发送故障通知消息，使得高层故障管理系 统根据故障通知消息确定发生故障的高层业务是否需要处理； 解决了在不同运 营商同时运营同一个移动通信系统的场景下， 现有的故障管理系统可能会导致 一些运营商在故障维护过程对人力或者物力造成浪费的问题； 达到了当低层业 务发生故障时， 高层故障管理系统可以根据故障通知消息对发生故障的高层业 务确定发生故障的高层业务是否需要处理，从而减少不必要的维护资源浪费的 效果。 请参考图 3A, 其示出了本发明另一实施例提供的故障处理方法的方法流 程图。 该故障处理方法用于通信故障管理系统中， 该通信故障管理系统包括至 少一个低层故障管理系统和至少一个高层故障管理系统。 该故障处理方法， 包 括：
步骤 301 , 低层故障管理系统检测低层业务中的故障告警情况；
低层故障管理系统检测低层业务中的故障告警情况。故障告警的检测过程 可以采用已有的故障检测技术进行， 不再赘述。
故障告警情况分为两种： 一个低层业务发生故障； 或者， 一个低层业务的 故障已经恢复。 在本步骤中， 假设故障告警情况为前一种， 比如， 低层故障管 理系统检测到低层业务 A发生了故障。
步骤 302, 低层故障管理系统根据故障告警情况和系统存储的业务依赖关 系表查询得到受影响的高层业务；
具体来讲，低层故障管理系统首先根据故障告警情况获取低层业务故障标 识， 该低层业务故障标识用于指示发生故障告警的低层业务； 然后， 低层故障 管理系统系统通过低层业务故障标识在系统存储的业务依赖关系表中查询高 层受影响业务标识， 高层受影响业务标识用于指示发生故障告警的低层业务所 影响的高层业务。
比如， 故障告警情况为： 低层业务 A发生了故障， 则低层故障管理系统获 取到低层业务故障标识 A, 然后根据系统存储的业务依赖关系表查询到高层受 影响业务标识 B,该高层受影响业务标识 B用于指示发生故障告警的低层业务 A所影响的是高层业务 B。
步骤 303, 若故障告警情况为一个低层业务发生故障， 则低层故障管理系 统向受影响的高层业务所对应的高层故障管理系统发送故障产生消息；
若故障告警情况为一个低层业务发生故障， 则低层故障管理系统向受影响 的高层业务所对应的高层故障管理系统发送故障产生消息， 该故障产生消息至 少携带有高层受影响业务标识。故障产生消息中携带的高层受影响业务标识可 以用于高层故障管理系统进行故障定界。
优选地， 该故障产生消息还携带有低层业务故障标识和故障类型。 一种故 障产生消息的格式如下：
Figure imgf000017_0001
低层业务故障标识有两种表示方式： 1、 低层业务名称； 2、 低层业务类 型 +业务 ID。 高层受影响业务标识有两种表示方式： 1、 高层业务名称； 2、 高层业务类 型 +业务 ID。
步骤 304, 高层故障管理系统接收并保存低层故障管理系统发送的故障产 生消息；
高层故障管理系统接收并保存低层故障管理系统发送的故障产生消息。 具 体来讲， 高层故障管理系统可以将接收到的所有故障产生消息保存在低层故障 信息列表中， 这些故障产生消息可以来自相同或者不同的低层故障管理系统。
步骤 305, 高层故障管理系统在保存故障产生消息的期间， 检测故障产生 消息中携带的高层受影响业务标识所指示的高层业务是否发生故障；
高层故障管理系统在保存故障产生消息的期间，检测故障产生消息中携带 的高层受影响业务标识所指示的高层业务是否发生故障。 比如， 高层受影响业 务标识所指示的是高层业务 B,则高层故障管理系统需要检测高层业务 B是否 发生了故障。 由于高层故障管理系统检测高层业务是否发生故障的时刻和接收 故障产生消息的时刻并不一定是同时的， 可能互有先后， 所以本步骤的检测过 程可以有两种触发方式。 在一种触发方式下， 本步骤包括如下几个子步骤， 如 图 3B所示：
305a, 在接收到故障产生消息后， 检测故障产生消息携带的高层受影响业 务标识和当前保存的至少一个高层故障业务标识中的任意一个是否相同， 高层 故障业务标识用于指示发生了故障的高层业务；
在接收故障产生消息之前， 高层故障管理系统可能已经检测到一个或者一 个以上的高层业务发生了故障， 则高层故障管理系统会保存至少一个高层故障 业务标识， 该高层故障业务标识用于指示发生故障的高层业务。 具体来讲， 高 层故障管理系统可以将至少一个高层故障业务标识保存在高层故障信息列表 中。
在接收到故障产生消息后， 高层故障管理系统检测故障产生消息携带的高 层受影响业务标识和当前保存的至少一个高层故障业务标识中的任意一个是 否相同。
比如， 高层故障管理系统在新接收到的高层受影响业务标识为 "高层业务 B" 时， 遍历高层故障信息列表中是否存在相同的高层故障业务标识。
305b, 若检测结果为接收到的高层受影响业务标识和当前保存的一个高层 故障业务标识相同， 则确定故障产生消息中携带的高层受影响业务标识所指示 的高层业务发生故障。
在另一种触发方式下， 本步骤包括如下子步骤， 如图 3C所示：
305A,在检测到一个高层业务发生故障后，获取对应的高层故障业务标识； 高层故障管理系统检测位于本层的高层业务的故障告警情况， 在检测到一 个高层业务发生故障后， 获取对应的高层故障业务标识， 高层故障业务标识用 于指示发生了故障的高层业务。
305B ,检测获取到的高层故障业务标识和当前保存的至少一个所述高层受 影响业务标识中的任意一个是否相同；
比如，高层故障管理系统在新获取到的高层故障业务标识为 "高层业务 B" 时， 遍历低层故障信息列表中是否存在相同的高层受影响业务标识。
305C,若检测结果为获取到的高层故障业务标识和当前保存的一个高层受 影响业务标识相同， 则确定相同的故障产生消息中携带的高层受影响业务标识 所指示的高层业务发生故障。
优选地， 若检测结果为获取到的高层故障业务标识和当前保存的所有高层 受影响业务标识均不相同， 则处理获取到的高层故障业务标识所指示的高层业 务的故障。
步骤 306, 若检测结果为发生故障， 则暂不处理该高层业务的故障。
若步骤 305的检测结果为发生故障， 则高层故障管理系统暂不处理该高层 业务的故障。 因为该高层业务所依赖的低层业务发生故障时， 该高层业务可能 会相应地无法正常运行， 此时高层业务的故障可能并非由自身原因造成， 所以 高层故障管理系统可以暂不处理该高层业务的故障， 以减少不必要的派工， 派 工是指故障管理系统自动生成派工单， 以派出工程师进行维修施工。
当然， 若步骤 305的检测结果为未发生故障， 则无需处理。
步骤 307, 低层故障管理系统检测低层业务中的故障告警情况；
低层故障管理系统检测低层业务中的故障告警情况。故障告警的检测过程 可以采用已有的故障检测技术进行， 不再赘述。
故障告警情况分为两种： 一个低层业务发生故障； 或者， 一个低层业务的 故障已经恢复。 在本步骤中， 假设故障告警情况为后一种， 比如， 低层故障管 理系统检测到低层业务 A发生的故障已经恢复。
步骤 308, 低层故障管理系统根据故障告警情况和系统存储的业务依赖关 系表查询得到受影响的高层业务； 具体来讲，低层故障管理系统首先根据故障告警情况获取低层业务故障标 识， 该低层业务故障标识用于指示发生故障告警的低层业务； 然后， 低层故障 管理系统系统通过低层业务故障标识在系统存储的业务依赖关系表中查询高 层受影响业务标识， 高层受影响业务标识用于指示发生故障告警的低层业务所 影响的高层业务。
比如， 故障告警情况为： 低层业务 A的故障已经恢复， 则低层故障管理系 统获取到低层业务故障标识 A, 然后根据系统存储的业务依赖关系表查询到高 层受影响业务标识 B,该高层受影响业务标识 B用于指示发生故障告警的低层 业务 A所影响的是高层业务 B。
步骤 309, 若故障告警情况为一个低层业务的故障已经恢复， 则低层故障 管理系统向受影响的高层业务所对应的高层故障管理系统发送故障恢复消息； 若故障告警情况为一个低层业务的故障已经恢复， 则低层故障管理系统向 受影响的高层业务所对应的高层故障管理系统发送故障恢复消息， 该故障恢复 消息至少携带有高层受影响业务标识。故障恢复消息中携带的高层受影响业务 标识可以用于高层故障管理系统进行故障定界。
优选地， 该故障恢复消息还携带有低层业务故障标识和故障类型。 一种故 障恢复消息的格式如下：
Figure imgf000020_0001
低层业务故障标识有两种表示方式： 1、 低层业务名称； 2、 低层业务类 型 +业务 ID。
高层受影响业务标识有两种表示方式： 1、 高层业务名称； 2、 高层业务类 型 +业务 ID。
相应地， 高层故障管理系统接收低层故障管理系统发送的故障恢复消息； 步骤 310, 高层故障管理系统查找与故障恢复消息匹配的故障产生消息， 匹配是指两个消息各自所包括的低层业务故障标识和故障类型均相同；
优选地， 高层故障管理系统在接收到故障恢复消息时， 查找与故障恢复消 息匹配的故障产生消息。 匹配是指至少两个消息各自所包括的低层业务故障标 识和故障类型均相同。 因为同一个低层业务可能出现不同类型的故障； 不同的 低层业务也可能出现相同类型的故障， 只有这两个参数均相同时， 才能表明两 个消息都是针对同一个低层业务的同一个故障。
步骤 311 , 在查找到与故障恢复消息匹配的故障产生消息时， 删除故障产 生消息。
具体来讲， 高层故障管理系统在查找到与故障恢复消息匹配的故障产生消 息时， 可以从本地保存的低层故障信息列表中删除匹配的故障产生消息。
步骤 312, 高层故障管理系统检测故障恢复消息携带的高层受影响业务标 识所指示的高层业务的故障是否已经恢复；
比如， 故障恢复消息携带的高层受影响业务标识所指示的是高层业务 B, 则高层故障管理系统在本地检测高层业务 B的故障是否已经恢复。
步骤 313, 若检测结果为还未恢复， 则高层故障管理系统处理高层业务的 故障。
若检测结果为高层业务 B的故障还未恢复， 由于高层业务 B所依赖的低 层业务 A的故障已经恢复了， 所以能够确定高层业务 B的故障不是由低层业 务 A的故障所导致的， 则高层故障管理系统需要对高层业务 B的故障进行处 理。
另外， 若检测结果为高层业务 B的故障也同时恢复， 则能够确定高层业务 B的故障是由低层业务 A的故障所导致的，则高层故障管理系统不需要对高层 业务 B的故障进行处理。 若检测结果为高层业务 B并未发生故障， 则高层故 障管理系统也不需要进行任何处理。
综上所述， 本实施例提供的故障处理方法， 通过高层故障管理系统在保存 故障产生消息的期间，检测故障产生消息中携带的高层受影响业务标识所指示 的高层业务是否发生故障； 若检测结果为发生故障， 则暂不处理高层业务的故 障， 从而可以达到在多运营商同时运营同一个移动通信系统的场景下， 减少不 必要的派工， 以免维修过程的物力资源及人力资源的浪费的效果。
本实施例提供的故障处理方法，还通过高层故障管理系统检测故障恢复消 息携带的高层受影响业务标识所指示的高层业务的故障是否已经恢复； 若检测 结果为还未恢复， 则处理高层业务的故障， 从而可以达到在多运营商同时运营 同一个移动通信系统的场景下， 准确地在不同的运营商之间定位高层业务的故 障源， 合理地分配故障维修任务的效果。
实施例。 以下为本发明的装置实施例， 对于装置实施例中未详尽描述的细节， 可以结合参考上述对应的方法实施例。 请参考图 4, 其示出了本发明一个实施例提供的通信故障管理系统的结构 示意图。该通信故障管理系统包括至少一个低层故障管理系统 400和至少一个 高层故障管理系统 500。
低层故障管理系统 400包括故障处理装置，该故障处理装置可以通过软件、 硬件或者两者的结合实现成为低层故障管理系统 400的一部分。 该故障处理装 置包括： 告警检测模块 420、 关系查询模块 440和消息发送模块 460;
告警检测模块 420, 用于检测低层业务中的故障告警情况；
关系查询模块 440, 用于根据所述故障告警情况和系统存储的业务依赖关 系表查询得到受影响的高层业务；
消息发送模块 460, 用于向所述受影响的高层业务所对应的所述高层故障 管理系统发送故障通知消息， 以便所述高层故障管理系统接收所述低层故障管 理系统发送的所述故障通知消息； 根据所述故障通知消息确定发生故障的高层 业务是否需要处理；
其中， 所述业务依赖关系表是低层业务与依赖所述低层业务运行的高层业 务之间的对应关系。
高层故障管理系统 500包括故障处理装置，该故障处理装置可以通过软件、 硬件或者两者的结合实现成为高层故障管理系统 500的一部分。 该故障处理装 置包括： 消息接收模块 520和故障处理模块 540。
消息接收模块 520,用于接收所述低层故障管理系统发送的故障通知消息， 所述故障通知消息是所述低层故障管理系统检测低层业务中的故障告警情况， 根据所述故障告警情况和系统存储的业务依赖关系表查询得到受影响的高层 业务， 然后向所述受影响的高层业务所对应的所述高层故障管理系统发送的； 故障处理模块 540, 用于根据所述故障通知消息确定发生故障的高层业务 是否需要处理；
其中， 所述业务依赖关系表是低层业务与依赖所述低层业务运行的高层业 务之间的对应关系。
综上所述， 本实施例提供的通信故障处理系统， 通过设置至少两层故障管 理系统， 并由低层故障管理系统在检测到低层业务的故障告警情况时， 根据故 障告警情况和系统存储的业务依赖关系表查询得到受影响的高层业务； 向受影 响的高层业务所对应的高层故障管理系统发送故障通知消息，使得高层故障管 理系统根据故障通知消息确定发生故障的高层业务是否需要处理； 解决了在不 同运营商同时运营同一个移动通信系统的场景下，现有的故障管理系统可能会 导致一些运营商在故障维护过程对人力或者物力造成浪费的问题； 达到了当低 层业务发生故障时， 高层故障管理系统可以根据故障通知消息对发生故障的高 层业务确定发生故障的高层业务是否需要处理，从而减少不必要的维护资源浪 费的效果。 请参考图 5 , 其示出了本发明另一个实施例提供的通信故障管理系统的结 构示意图。 该通信故障管理系统包括至少一个低层故障管理系统 400和至少一 个高层故障管理系统 500。
低层故障管理系统 400包括故障处理装置，该故障处理装置可以通过软件、 硬件或者两者的结合实现成为低层故障管理系统 400的一部分。 该故障处理装 置包括： 告警检测模块 420、 关系查询模块 440和消息发送模块 460;
告警检测模块 420, 用于检测低层业务中的故障告警情况；
关系查询模块 440, 用于根据所述故障告警情况和系统存储的业务依赖关 系表查询得到受影响的高层业务；
消息发送模块 460, 用于向所述受影响的高层业务所对应的所述高层故障 管理系统发送故障通知消息， 以便所述高层故障管理系统接收所述低层故障管 理系统发送的所述故障通知消息； 根据所述故障通知消息确定发生故障的高层 业务是否需要处理；
其中， 所述业务依赖关系表是低层业务与依赖所述低层业务运行的高层业 务之间的对应关系。
优选地， 若所述故障告警情况为一个低层业务发生故障， 贝' J :
所述消息发送模块 460, 用于向所述受影响的高层业务所对应的所述高层 故障管理系统发送故障产生消息， 所述故障产生消息携带有高层受影响业务标 识， 所述高层受影响业务标识用于指示发生故障告警的低层业务所影响的高层 业务； 以便所述高层故障管理系统接收并保存所述低层故障管理系统发送的所 述故障产生消息； 在保存所述故障产生消息的期间， 检测所述故障产生消息中 携带的高层受影响业务标识所指示的高层业务是否发生故障； 若检测结果为发 生故障， 则暂不处理所述高层业务的故障。
优选地， 若所述故障告警情况为一个低层业务的故障已经恢复， 贝' J :
所述消息发送模块 460, 用于向所述受影响的高层业务所对应的所述高层 故障管理系统发送故障恢复消息， 所述故障恢复消息携带有高层受影响业务标 识， 所述高层受影响业务标识用于指示发生故障告警的低层业务所影响的高层 业务； 以便所述高层故障管理系统接收所述低层故障管理系统发送的所述故障 恢复消息； 检测所述故障恢复消息携带的所述高层受影响业务标识所指示的高 层业务的故障是否已经恢复； 若检测结果为还未恢复， 则处理所述高层业务的 故障。
优选地， 所述故障产生消息和所述故障恢复消息都还携带有低层业务故障 标识和故障类型， 所述低层业务故障标识用于指示所述发生故障告警的低层业 务； 以便所述高层故障管理系统查找与所述故障恢复消息匹配的故障产生消 息， 所述匹配是指两个消息各自所包括的所述低层业务故障标识和所述故障类 型均相同； 在查找到与所述故障恢复消息匹配的故障产生消息时， 删除所述故 障产生消息。
高层故障管理系统 500包括故障处理装置，该故障处理装置可以通过软件、 硬件或者两者的结合实现成为高层故障管理系统 500的一部分。 该故障处理装 置包括： 消息接收模块 520、 故障处理模块 540、 消息匹配模块 562和消息删 除模块 564。
消息接收模块 520 ,用于接收所述低层故障管理系统发送的故障通知消息， 所述故障通知消息是所述低层故障管理系统检测低层业务中的故障告警情况， 根据所述故障告警情况和系统存储的业务依赖关系表查询得到受影响的高层 业务， 然后向所述受影响的高层业务所对应的所述高层故障管理系统发送的； 故障处理模块 540, 用于根据所述故障通知消息确定发生故障的高层业务 是否需要处理；
其中， 所述业务依赖关系表是低层业务与依赖所述低层业务运行的高层业 务之间的对应关系。
优选地， 所述消息接收模块 520, 用于接收并保存所述低层故障管理系统 发送的故障产生消息， 所述故障产生消息携带有高层受影响业务标识， 所述高 层受影响业务标识用于指示发生故障告警的低层业务所影响的高层业务；
所述故障处理模块 540, 用于在保存所述故障产生消息的期间， 检测所述 故障产生消息中携带的高层受影响业务标识所指示的高层业务是否发生故障； 若检测结果为发生故障， 则暂不处理所述高层业务的故障。
优选地， 所述故障处理模块 540, 包括： 第一检测单元和第一确定单元； 所述第一检测单元， 用于在接收到所述故障产生消息后， 检测所述故障产 生消息携带的所述高层受影响业务标识和当前保存的至少一个高层故障业务 标识中的任意一个是否相同， 所述高层故障业务标识用于指示发生了故障的高 层业务；
所述第一确定单元， 用于若检测结果为接收到的所述高层受影响业务标识 和当前保存的一个高层故障业务标识相同， 则确定所述故障产生消息中携带的 高层受影响业务标识所指示的高层业务发生故障。
优选地， 所述故障处理模块 540, 包括： 标识获取单元、 第二检测单元和 第二确定单元；
所述标识获取单元， 用于在检测到一个高层业务发生故障后， 获取对应的 高层故障业务标识， 所述高层故障业务标识用于指示发生了故障的高层业务； 所述第二检测单元， 用于检测获取到的所述高层故障业务标识和当前保存 的至少一个所述高层受影响业务标识中的任意一个是否相同；
所述第二确定单元， 用于若检测结果为获取到的所述高层故障业务标识和 当前保存的一个高层受影响业务标识相同， 则确定相同的所述故障产生消息中 携带的高层受影响业务标识所指示的高层业务发生故障。
优选地， 所述故障处理模块 540, 还包括： 第三确定单元；
所述第三确定单元， 用于若检测结果为获取到的所述高层故障业务标识和 当前保存的所有高层受影响业务标识均不相同， 则处理获取到的所述高层故障 业务标识所指示的高层业务的故障。
优选地， 所述消息接收模块 520, 还用于接收所述低层故障管理系统发送 的故障恢复消息， 所述故障恢复消息携带有所述高层受影响业务标识；
所述故障处理模块 540, 还用于检测所述故障恢复消息携带的所述高层受 影响业务标识所指示的高层业务的故障是否已经恢复； 若检测结果为还未恢 复， 则处理所述高层业务的故障。
优选地， 所述故障产生消息和所述故障恢复消息都还携带有低层业务故障 标识和故障类型， 所述低层业务故障标识用于指示所述发生故障告警的低层业 务；
所述装置， 还包括： 消息匹配模块 562和消息删除模块 564;
所述消息匹配模块 562, 用于查找与所述故障恢复消息匹配的故障产生消 息， 所述匹配是指两个消息各自所包括的所述低层业务故障标识和所述故障类 型均相同；
所述消息删除模块 564, 用于在查找到与所述故障恢复消息匹配的故障产 生消息时， 删除所述故障产生消息。
综上所述， 本实施例提供的通信故障管理系统， 通过高层故障管理系统在 保存故障产生消息的期间，检测故障产生消息中携带的高层受影响业务标识所 指示的高层业务是否发生故障； 若检测结果为发生故障， 则暂不处理高层业务 的故障， 从而可以达到在多运营商同时运营同一个移动通信系统的场景下， 减 少不必要的派工， 以免维修过程的物力资源及人力资源的浪费的效果。
本实施例提供的通信故障管理系统，还通过高层故障管理系统检测故障恢 复消息携带的高层受影响业务标识所指示的高层业务的故障是否已经恢复； 若 检测结果为还未恢复， 则处理高层业务的故障， 从而可以达到在多运营商同时 运营同一个移动通信系统的场景下， 准确地在不同的运营商之间定位高层业务 的故障源， 合理地分配故障维修任务的效果。 请参考图 6, 其示出了本发明一个实施例提供的故障管理系统的结构示意 图， 该故障管理系统用于实现为通信故障管理系统中的低层故障管理系统， 所 述系统包括： 处理器 620、 存储器 640和发送器 660;
所述处理器 620, 用于检测低层业务中的故障告警情况；
所述处理器 620, 还用于根据所述故障告警情况和所述存储器 640中系统 存储的业务依赖关系表查询得到受影响的高层业务；
所述处理器 620, 还用于控制所述发送器 660向所述受影响的高层业务所 对应的所述高层故障管理系统发送故障通知消息， 以便所述高层故障管理系统 接收所述低层故障管理系统发送的所述故障通知消息； 根据所述故障通知消息 确定发生故障的高层业务是否需要处理；
其中， 所述业务依赖关系表是低层业务与依赖所述低层业务运行的高层业 务之间的对应关系。
在更为优选的实施例中， 若所述故障告警情况为一个低层业务发生故障， 则：
所述处理器 620, 还用于控制所述发送器 660向所述受影响的高层业务所 对应的所述高层故障管理系统发送故障产生消息， 所述故障产生消息携带有高 层受影响业务标识， 所述高层受影响业务标识用于指示发生故障告警的低层业 务所影响的高层业务； 以便所述高层故障管理系统接收并保存所述低层故障管 理系统发送的所述故障产生消息； 在保存所述故障产生消息的期间， 检测所述 故障产生消息中携带的高层受影响业务标识所指示的高层业务是否发生故障； 若检测结果为发生故障， 则暂不处理所述高层业务的故障。
在更为优选的实施例中， 若所述故障告警情况为一个低层业务的故障已经 恢复， 则：
所述处理器 620, 还用于控制所述发送器 640向所述受影响的高层业务所 对应的所述高层故障管理系统发送故障恢复消息， 所述故障恢复消息携带有高 层受影响业务标识， 所述高层受影响业务标识用于指示发生故障告警的低层业 务所影响的高层业务； 以便所述高层故障管理系统接收所述低层故障管理系统 发送的所述故障恢复消息； 检测所述故障恢复消息携带的所述高层受影响业务 标识所指示的高层业务的故障是否已经恢复； 若检测结果为还未恢复， 则处理 所述高层业务的故障。
在更为优选的实施例中，所述故障产生消息和所述故障恢复消息都还携带 有低层业务故障标识和故障类型， 所述低层业务故障标识用于指示所述发生故 障告警的低层业务； 以便所述高层故障管理系统查找与所述故障恢复消息匹配 的故障产生消息， 所述匹配是指两个消息各自所包括的所述低层业务故障标识 和所述故障类型均相同； 在查找到与所述故障恢复消息匹配的故障产生消息 时， 删除所述故障产生消息。
综上所述， 本实施例提供的故障管理系统， 通过高层故障管理系统在保存 故障产生消息的期间，检测故障产生消息中携带的高层受影响业务标识所指示 的高层业务是否发生故障； 若检测结果为发生故障， 则暂不处理高层业务的故 障， 从而可以达到在多运营商同时运营同一个移动通信系统的场景下， 减少不 必要的派工， 以免维修过程的物力资源及人力资源的浪费的效果。
本实施例提供的故障管理系统，还通过高层故障管理系统检测故障恢复消 息携带的高层受影响业务标识所指示的高层业务的故障是否已经恢复； 若检测 结果为还未恢复， 则处理高层业务的故障， 从而可以达到在多运营商同时运营 同一个移动通信系统的场景下， 准确地在不同的运营商之间定位高层业务的故 障源， 合理地分配故障维修任务的效果。 请参考图 7, 其示出了本发明一个实施例提供的故障管理系统的结构示意 图， 该故障管理系统用于实现为通信故障管理系统中的高层故障管理系统， 所 述系统包括： 接收器 720、 处理器 740和存储器 760;
所述处理器 740, 用于控制所述接收器 720接收所述低层故障管理系统发 送的故障通知消息， 所述故障通知消息是所述低层故障管理系统检测低层业务 中的故障告警情况，根据所述故障告警情况和系统存储的业务依赖关系表查询 得到受影响的高层业务， 然后向所述受影响的高层业务所对应的所述高层故障 管理系统发送的；
所述处理器 740, 还用于根据所述故障通知消息确定发生故障的高层业务 是否需要处理；
其中， 所述业务依赖关系表是低层业务与依赖所述低层业务运行的高层业 务之间的对应关系。
在更为优选的实施例中， 所述处理器 740, 还用于控制所述接收器 720接 收所述低层故障管理系统发送的故障产生消息， 并保存至所述存储器 760, 所 述故障产生消息携带有高层受影响业务标识， 所述高层受影响业务标识用于指 示发生故障告警的低层业务所影响的高层业务；
所述处理器 740, 还用于在所述存储器保存所述故障产生消息的期间， 检 测所述故障产生消息中携带的高层受影响业务标识所指示的高层业务是否发 生故障；
所述处理器 740, 还用于若检测结果为发生故障， 则暂不处理所述高层业 务的故障。
在更为优选的实施例中， 所述处理器 740, 还用于在控制所述接收器 720 接收到所述故障产生消息后，检测所述故障产生消息携带的所述高层受影响业 务标识和所述存储器 760当前保存的至少一个高层故障业务标识中的任意一个 是否相同， 所述高层故障业务标识用于指示发生了故障的高层业务；
所述处理器 740, 还用于若检测结果为接收到的所述高层受影响业务标识 和当前保存的一个高层故障业务标识相同， 则确定所述故障产生消息中携带的 高层受影响业务标识所指示的高层业务发生故障。
在更为优选的实施例中， 所述处理器 740, 还用于在检测到一个高层业务 发生故障后， 获取对应的高层故障业务标识， 所述高层故障业务标识用于指示 发生了故障的高层业务；
所述处理器 740, 还用于检测获取到的所述高层故障业务标识和所述存储 器 760当前保存的至少一个所述高层受影响业务标识中的任意一个是否相同； 所述处理器 740, 还用于若检测结果为获取到的所述高层故障业务标识和 当前保存的一个高层受影响业务标识相同， 则确定相同的所述故障产生消息中 携带的高层受影响业务标识所指示的高层业务发生故障。
在更为优选的实施例中， 所述处理器 740, 还用于若检测结果为获取到的 所述高层故障业务标识和当前保存的所有高层受影响业务标识均不相同， 则处 理获取到的所述高层故障业务标识所指示的高层业务的故障。
在更为优选的实施例中， 所述处理器 740, 还用于控制所述接收器接收所 述低层故障管理系统发送的故障恢复消息， 所述故障恢复消息携带有所述高层 受影响业务标识；
所述处理器 740, 还用于检测所述故障恢复消息携带的所述高层受影响业 务标识所指示的高层业务的故障是否已经恢复；
所述处理器 740, 还用于若检测结果为还未恢复， 则处理所述高层业务的 故障。
在更为优选的实施例中，所述故障产生消息和所述故障恢复消息都还携带 有低层业务故障标识和故障类型， 所述低层业务故障标识用于指示所述发生故 障告警的低层业务；
所述处理器 740, 还用于查找与所述故障恢复消息匹配的故障产生消息， 所述匹配是指两个消息各自所包括的所述低层业务故障标识和所述故障类型 均相同；
所述处理器 740, 还用于在查找到与所述故障恢复消息匹配的故障产生消 息时， 删除所述故障产生消息。
综上所述， 本实施例提供的故障管理系统， 通过高层故障管理系统在保存 故障产生消息的期间，检测故障产生消息中携带的高层受影响业务标识所指示 的高层业务是否发生故障； 若检测结果为发生故障， 则暂不处理高层业务的故 障， 从而可以达到在多运营商同时运营同一个移动通信系统的场景下， 减少不 必要的派工， 以免维修过程的物力资源及人力资源的浪费的效果。
本实施例提供的故障管理系统，还通过高层故障管理系统检测故障恢复消 息携带的高层受影响业务标识所指示的高层业务的故障是否已经恢复； 若检测 结果为还未恢复， 则处理高层业务的故障， 从而可以达到在多运营商同时运营 同一个移动通信系统的场景下， 准确地在不同的运营商之间定位高层业务的故 障源， 合理地分配故障维修任务的效果 请参考图 8, 其示出了本发明一个实施例所提供的通信故障管理系统的结 构方框图。 该系统包括至少一个低层故障管理系统 820和至少一个高层故障管 理系统 840;
所述低层故障管理系统 820是如图 6所示实施例及图 6所示实施例的更为 优选的实施例中所述的故障管理系统；
所述高层故障管理系统 840是如图 7所示实施例及图 7所示实施例的更为 优选的实施例中所述的故障管理系统。
通过以上的实施方式的描述， 所属领域的技术人员可以清楚地了解到本发 明可以用硬件实现， 或固件实现， 或它们的组合方式来实现。 当使用软件实现 时， 可以将上述功能存储在计算机可读介质中或作为计算机可读介质上的一个 或多个指令或代码进行传输。 计算机可读介质包括计算机存储介质和通信介 质， 其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介 质。 存储介质可以是计算机能够存取的任何可用介质。 以此为例但不限于： 计 算机可读介质可以包括 RAM、 ROM, EEPROM、 CD-ROM或其他光盘存储、 磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据 结构形式的期望的程序代码并能够由计算机存取的任何其他介质。 此外。 任何 连接可以适当的成为计算机可读介质。 例如， 如果软件是使用同轴电缆、 光纤 光缆、 双绞线、 数字用户线（DSL )或者诸如红外线、 无线电和微波之类的无 线技术从网站、 服务器或者其他远程源传输的， 那么同轴电缆、 光纤光缆、 双 绞线、 DSL或者诸如红外线、 无线和微波之类的无线技术包括在所属介质的定 影中。 如本发明所使用的， 盘（Disk )和碟（disc ) 包括压缩光碟（CD )、 激 光碟、 光碟、 数字通用光碟（DVD )、 软盘和蓝光光碟， 其中盘通常磁性的复 制数据， 而碟则用激光来光学的复制数据。 上面的组合也应当包括在计算机可 读介质的保护范围之内。
总之， 以上所述仅为本发明技术方案的较佳实施例而已， 并非用于限定本 发明的保护范围。凡在本发明的精神和原则之内，所作的任何修改、等同替换、 改进等， 均应包含在本发明的保护范围之内。

Claims

权 利 要 求 书
1、 一种故障处理方法， 其特征在于， 用于通信故障管理系统中的低层故障 管理系统， 所述通信故障管理系统包括至少一个低层故障管理系统和至少一个 高层故障管理系统， 所述方法包括：
检测低层业务中的故障告警情况；
根据所述故障告警情况和系统存储的业务依赖关系表查询得到受影响的高 层业务；
向所述受影响的高层业务所对应的所述高层故障管理系统发送故障通知消 息， 以便所述高层故障管理系统接收所述低层故障管理系统发送的所述故障通 知消息； 根据所述故障通知消息确定发生故障的高层业务是否需要处理；
其中， 所述业务依赖关系表是低层业务与依赖所述低层业务运行的高层业 务之间的对应关系。
2、 根据权利要求 1所述的故障处理方法， 其特征在于， 若所述故障告警情 况为一个低层业务发生故障， 则所述向所述受影响的高层业务所对应的所述高 层故障管理系统发送故障通知消息， 包括：
向所述受影响的高层业务所对应的所述高层故障管理系统发送故障产生消 息， 所述故障产生消息携带有高层受影响业务标识， 所述高层受影响业务标识 用于指示发生故障告警的低层业务所影响的高层业务； 以便所述高层故障管理 系统接收并保存所述低层故障管理系统发送的所述故障产生消息； 在保存所述 故障产生消息的期间， 检测所述故障产生消息中携带的高层受影响业务标识所 指示的高层业务是否发生故障； 若检测结果为发生故障， 则暂不处理所述高层 业务的故障。
3、 根据权利要求 2所述的故障处理方法， 其特征在于， 若所述故障告警情 况为一个低层业务的故障已经恢复， 则所述向所述受影响的高层业务所对应的 所述高层故障管理系统发送故障通知消息， 包括：
向所述受影响的高层业务所对应的所述高层故障管理系统发送故障恢复消 息， 所述故障恢复消息携带有高层受影响业务标识， 所述高层受影响业务标识 用于指示发生故障告警的低层业务所影响的高层业务； 以便所述高层故障管理 系统接收所述低层故障管理系统发送的所述故障恢复消息； 检测所述故障恢复 消息携带的所述高层受影响业务标识所指示的高层业务的故障是否已经恢复； 若检测结果为还未恢复， 则处理所述高层业务的故障。
4、 根据权利要求 3所述的故障处理方法， 其特征在于， 所述故障产生消息 和所述故障恢复消息都还携带有低层业务故障标识和故障类型， 所述低层业务 故障标识用于指示所述发生故障告警的低层业务； 以便所述高层故障管理系统 查找与所述故障恢复消息匹配的故障产生消息， 所述匹配是指两个消息各自所 包括的所述低层业务故障标识和所述故障类型均相同； 在查找到与所述故障恢 复消息匹配的故障产生消息时， 删除所述故障产生消息。
5、 一种故障处理方法， 其特征在于， 用于通信故障管理系统中的高层故障 管理系统， 所述通信故障管理系统包括至少一层低层故障管理系统和至少一层 高层故障管理系统， 所述方法包括：
接收所述低层故障管理系统发送的故障通知消息， 所述故障通知消息是所 述低层故障管理系统检测低层业务中的故障告警情况， 根据所述故障告警情况 和系统存储的业务依赖关系表查询得到受影响的高层业务， 然后向所述受影响 的高层业务所对应的所述高层故障管理系统发送的；
根据所述故障通知消息确定发生故障的高层业务是否需要处理；
其中， 所述业务依赖关系表是低层业务与依赖所述低层业务运行的高层业 务之间的对应关系。
6、 根据权利要求 5所述的故障处理方法， 其特征在于， 所述接收所述低层 故障管理系统发送的故障通知消息， 包括：
接收并保存所述低层故障管理系统发送的故障产生消息， 所述故障产生消 息携带有高层受影响业务标识， 所述高层受影响业务标识用于指示发生故障告 警的低层业务所影响的高层业务；
所述根据所述故障通知消息确定发生故障的高层业务是否需要处理， 包括： 在保存所述故障产生消息的期间， 检测所述故障产生消息中携带的高层受 影响业务标识所指示的高层业务是否发生故障；
若检测结果为发生故障， 则暂不处理所述高层业务的故障。
7、 根据权利要求 6所述的故障处理方法， 其特征在于， 所述在保存所述故 障产生消息的期间， 检测所述故障产生消息中携带的高层受影响业务标识所指 示的高层业务是否发生故障， 包括：
在接收到所述故障产生消息后， 检测所述故障产生消息携带的所述高层受 影响业务标识和当前保存的至少一个高层故障业务标识中的任意一个是否相 同， 所述高层故障业务标识用于指示发生了故障的高层业务；
若检测结果为接收到的所述高层受影响业务标识和当前保存的一个高层故 障业务标识相同， 则确定所述故障产生消息中携带的高层受影响业务标识所指 示的高层业务发生故障。
8、 根据权利要求 6所述的故障处理方法， 其特征在于， 所述在保存所述故 障产生消息的期间， 检测所述故障产生消息中携带的高层受影响业务标识所指 示的高层业务是否发生故障， 包括：
在检测到一个高层业务发生故障后， 获取对应的高层故障业务标识， 所述 高层故障业务标识用于指示发生了故障的高层业务；
检测获取到的所述高层故障业务标识和当前保存的至少一个所述高层受影 响业务标识中的任意一个是否相同；
若检测结果为获取到的所述高层故障业务标识和当前保存的一个高层受影 响业务标识相同， 则确定相同的所述故障产生消息中携带的高层受影响业务标 识所指示的高层业务发生故障。
9、 根据权利要求 8所述的故障处理方法， 其特征在于， 所述检测获取到的 所述高层故障业务标识和预先保存的至少一个所述高层受影响业务标识中的任 意一个是否相同之后， 还包括：
若检测结果为获取到的所述高层故障业务标识和当前保存的所有高层受影 响业务标识均不相同， 则处理获取到的所述高层故障业务标识所指示的高层业 务的故障。
10、 根据权利要求 6至 9任一所述的故障处理方法， 其特征在于， 所述接 收所述低层故障管理系统发送的故障通知消息， 包括： 接收所述低层故障管理系统发送的故障恢复消息， 所述故障恢复消息携带 有所述高层受影响业务标识；
所述根据所述故障通知消息确定发生故障的高层业务是否需要处理， 包括： 检测所述故障恢复消息携带的所述高层受影响业务标识所指示的高层业务 的故障是否已经恢复；
若检测结果为还未恢复， 则处理所述高层业务的故障。
11、 根据权利要求 10所述的故障处理方法， 其特征在于， 所述故障产生消 息和所述故障恢复消息都还携带有低层业务故障标识和故障类型， 所述低层业 务故障标识用于指示所述发生故障告警的低层业务；
所述接收所述低层故障管理系统发送的故障恢复消息之后， 还包括： 查找与所述故障恢复消息匹配的故障产生消息， 所述匹配是指两个消息各 自所包括的所述低层业务故障标识和所述故障类型均相同；
在查找到与所述故障恢复消息匹配的故障产生消息时， 删除所述故障产生 消息。
12、 一种故障处理装置， 其特征在于， 用于通信故障管理系统中的低层故 障管理系统， 所述通信故障管理系统包括至少一个低层故障管理系统和至少一 个高层故障管理系统， 所述装置包括：
告警检测模块， 用于检测低层业务中的故障告警情况；
关系查询模块， 用于根据所述故障告警情况和系统存储的业务依赖关系表 查询得到受影响的高层业务；
消息发送模块， 用于向所述受影响的高层业务所对应的所述高层故障管理 系统发送故障通知消息， 以便所述高层故障管理系统接收所述低层故障管理系 统发送的所述故障通知消息； 根据所述故障通知消息确定发生故障的高层业务 是否需要处理；
其中， 所述业务依赖关系表是低层业务与依赖所述低层业务运行的高层业 务之间的对应关系。
13、 根据权利要求 12所述的故障处理装置， 其特征在于， 若所述故障告警 情况为一个低层业务发生故障， 贝' J : 所述消息发送模块， 用于向所述受影响的高层业务所对应的所述高层故障 管理系统发送故障产生消息， 所述故障产生消息携带有高层受影响业务标识， 所述高层受影响业务标识用于指示发生故障告警的低层业务所影响的高层业 务； 以便所述高层故障管理系统接收并保存所述低层故障管理系统发送的所述 故障产生消息； 在保存所述故障产生消息的期间， 检测所述故障产生消息中携 带的高层受影响业务标识所指示的高层业务是否发生故障； 若检测结果为发生 故障， 则暂不处理所述高层业务的故障。
14、 根据权利要求 13所述的故障处理装置， 其特征在于， 若所述故障告警 情况为一个低层业务的故障已经恢复， 贝' J :
所述消息发送模块， 用于向所述受影响的高层业务所对应的所述高层故障 管理系统发送故障恢复消息， 所述故障恢复消息携带有高层受影响业务标识， 所述高层受影响业务标识用于指示发生故障告警的低层业务所影响的高层业 务； 以便所述高层故障管理系统接收所述低层故障管理系统发送的所述故障恢 复消息； 检测所述故障恢复消息携带的所述高层受影响业务标识所指示的高层 业务的故障是否已经恢复； 若检测结果为还未恢复， 则处理所述高层业务的故 障。
15、 根据权利要求 14所述的故障处理装置， 其特征在于， 所述故障产生消 息和所述故障恢复消息都还携带有低层业务故障标识和故障类型， 所述低层业 务故障标识用于指示所述发生故障告警的低层业务； 以便所述高层故障管理系 统查找与所述故障恢复消息匹配的故障产生消息， 所述匹配是指两个消息各自 所包括的所述低层业务故障标识和所述故障类型均相同； 在查找到与所述故障 恢复消息匹配的故障产生消息时， 删除所述故障产生消息。
16、 一种故障处理装置， 其特征在于， 用于通信故障管理系统中的高层故 障管理系统， 所述通信故障管理系统包括至少一层低层故障管理系统和至少一 层高层故障管理系统， 所述装置包括：
消息接收模块， 用于接收所述低层故障管理系统发送的故障通知消息， 所 述故障通知消息是所述低层故障管理系统检测低层业务中的故障告警情况， 根 据所述故障告警情况和系统存储的业务依赖关系表查询得到受影响的高层业 务， 然后向所述受影响的高层业务所对应的所述高层故障管理系统发送的； 故障处理模块， 用于根据所述故障通知消息确定发生故障的高层业务是否 需要处理；
其中， 所述业务依赖关系表是低层业务与依赖所述低层业务运行的高层业 务之间的对应关系。
17、 根据权利要求 16所述的故障处理装置， 其特征在于：
所述消息接收模块， 用于接收并保存所述低层故障管理系统发送的故障产 生消息， 所述故障产生消息携带有高层受影响业务标识， 所述高层受影响业务 标识用于指示发生故障告警的低层业务所影响的高层业务；
所述故障处理模块， 用于在保存所述故障产生消息的期间， 检测所述故障 产生消息中携带的高层受影响业务标识所指示的高层业务是否发生故障； 若检 测结果为发生故障， 则暂不处理所述高层业务的故障。
18、 根据权利要求 17所述的故障处理装置， 其特征在于， 所述故障处理模 块， 包括： 第一检测单元和第一确定单元；
所述第一检测单元， 用于在接收到所述故障产生消息后， 检测所述故障产 生消息携带的所述高层受影响业务标识和当前保存的至少一个高层故障业务标 识中的任意一个是否相同， 所述高层故障业务标识用于指示发生了故障的高层 业务；
所述第一确定单元， 用于若检测结果为接收到的所述高层受影响业务标识 和当前保存的一个高层故障业务标识相同， 则确定所述故障产生消息中携带的 高层受影响业务标识所指示的高层业务发生故障。
19、 根据权利要求 17所述的故障处理装置， 其特征在于， 所述故障处理模 块， 包括： 标识获取单元、 第二检测单元和第二确定单元；
所述标识获取单元， 用于在检测到一个高层业务发生故障后， 获取对应的 高层故障业务标识， 所述高层故障业务标识用于指示发生了故障的高层业务； 所述第二检测单元， 用于检测获取到的所述高层故障业务标识和当前保存 的至少一个所述高层受影响业务标识中的任意一个是否相同；
所述第二确定单元， 用于若检测结果为获取到的所述高层故障业务标识和 当前保存的一个高层受影响业务标识相同， 则确定相同的所述故障产生消息中 携带的高层受影响业务标识所指示的高层业务发生故障。
20、 根据权利要求 19所述的故障处理装置， 其特征在于， 所述故障处理模 块， 还包括： 第三确定单元；
所述第三确定单元， 用于若检测结果为获取到的所述高层故障业务标识和 当前保存的所有高层受影响业务标识均不相同， 则处理获取到的所述高层故障 业务标识所指示的高层业务的故障。
21、 根据权利要求 17至 20任一所述的故障处理装置， 其特征在于， 所述 消息接收模块， 还用于接收所述低层故障管理系统发送的故障恢复消息， 所述 故障恢复消息携带有所述高层受影响业务标识；
所述故障处理模块， 还用于检测所述故障恢复消息携带的所述高层受影响 业务标识所指示的高层业务的故障是否已经恢复； 若检测结果为还未恢复， 则 处理所述高层业务的故障。
22、 根据权利要求 21所述的故障处理装置， 其特征在于， 所述故障产生消 息和所述故障恢复消息都还携带有低层业务故障标识和故障类型， 所述低层业 务故障标识用于指示所述发生故障告警的低层业务；
所述装置， 还包括： 消息匹配模块和消息删除模块；
所述消息匹配模块， 用于查找与所述故障恢复消息匹配的故障产生消息， 所述匹配是指两个消息各自所包括的所述低层业务故障标识和所述故障类型均 相同；
所述消息删除模块， 用于在查找到与所述故障恢复消息匹配的故障产生消 息时， 删除所述故障产生消息。
23、 一种通信故障管理系统， 其特征在于， 所述系统包括至少一个低层故 障管理系统和至少一个高层故障管理系统；
所述低层故障管理系统包括如权利要求 12至 15任一所述的故障处理装置； 所述高层故障管理系统包括如权利要求 16至 22任一所述的故障处理装置。
24、 一种故障管理系统， 其特征在于， 用于实现为通信故障管理系统中的 低层故障管理系统， 所述通信故障管理系统包括至少一层低层故障管理系统和 至少一层高层故障管理系统， 所述系统包括： 处理器、 存储器和发送器；
所述处理器， 用于检测低层业务中的故障告警情况；
所述处理器， 还用于根据所述故障告警情况和所述存储器中系统存储的业 务依赖关系表查询得到受影响的高层业务；
所述处理器， 还用于控制所述发送器向所述受影响的高层业务所对应的所 述高层故障管理系统发送故障通知消息， 以便所述高层故障管理系统接收所述 低层故障管理系统发送的所述故障通知消息； 根据所述故障通知消息确定发生 故障的高层业务是否需要处理；
其中， 所述业务依赖关系表是低层业务与依赖所述低层业务运行的高层业 务之间的对应关系。
25、 根据权利要求 24所述的故障处理系统， 其特征在于， 若所述故障告警 情况为一个低层业务发生故障， 贝' J :
所述处理器， 还用于控制所述发送器向所述受影响的高层业务所对应的所 述高层故障管理系统发送故障产生消息， 所述故障产生消息携带有高层受影响 业务标识， 所述高层受影响业务标识用于指示发生故障告警的低层业务所影响 的高层业务； 以便所述高层故障管理系统接收并保存所述低层故障管理系统发 送的所述故障产生消息； 在保存所述故障产生消息的期间， 检测所述故障产生 消息中携带的高层受影响业务标识所指示的高层业务是否发生故障； 若检测结 果为发生故障， 则暂不处理所述高层业务的故障。
26、 根据权利要求 25所述的故障处理系统， 其特征在于， 若所述故障告警 情况为一个低层业务的故障已经恢复， 贝' J :
所述处理器， 还用于控制所述发送器向所述受影响的高层业务所对应的所 述高层故障管理系统发送故障恢复消息， 所述故障恢复消息携带有高层受影响 业务标识， 所述高层受影响业务标识用于指示发生故障告警的低层业务所影响 的高层业务； 以便所述高层故障管理系统接收所述低层故障管理系统发送的所 述故障恢复消息； 检测所述故障恢复消息携带的所述高层受影响业务标识所指 示的高层业务的故障是否已经恢复； 若检测结果为还未恢复， 则处理所述高层 业务的故障。
27、 根据权利要求 26所述的故障处理系统， 其特征在于， 所述故障产生消 息和所述故障恢复消息都还携带有低层业务故障标识和故障类型， 所述低层业 务故障标识用于指示所述发生故障告警的低层业务； 以便所述高层故障管理系 统查找与所述故障恢复消息匹配的故障产生消息， 所述匹配是指两个消息各自 所包括的所述低层业务故障标识和所述故障类型均相同； 在查找到与所述故障 恢复消息匹配的故障产生消息时， 删除所述故障产生消息。
28、 一种故障处理系统， 其特征在于， 用于实现为通信故障管理系统中的 高层故障管理系统， 所述通信故障管理系统包括至少一层低层故障管理系统和 至少一层高层故障管理系统， 所述系统包括： 接收器、 处理器和存储器；
所述处理器， 用于控制所述接收器接收所述低层故障管理系统发送的故障 通知消息， 所述故障通知消息是所述低层故障管理系统检测低层业务中的故障 告警情况， 根据所述故障告警情况和系统存储的业务依赖关系表查询得到受影 响的高层业务， 然后向所述受影响的高层业务所对应的所述高层故障管理系统 发送的；
所述处理器， 还用于根据所述故障通知消息确定发生故障的高层业务是否 需要处理；
其中， 所述业务依赖关系表是低层业务与依赖所述低层业务运行的高层业 务之间的对应关系。
29、 根据权利要求 28所述的故障处理系统， 其特征在于：
所述处理器， 还用于控制所述接收器接收所述低层故障管理系统发送的故 障产生消息， 并保存至所述存储器， 所述故障产生消息携带有高层受影响业务 标识， 所述高层受影响业务标识用于指示发生故障告警的低层业务所影响的高 层业务；
所述处理器， 还用于在所述存储器保存所述故障产生消息的期间， 检测所 述故障产生消息中携带的高层受影响业务标识所指示的高层业务是否发生故 障；
所述处理器， 还用于若检测结果为发生故障， 则暂不处理所述高层业务的 故障。
30、 根据权利要求 29所述的故障处理系统， 其特征在于：
所述处理器， 还用于在控制所述接收器接收到所述故障产生消息后， 检测 所述故障产生消息携带的所述高层受影响业务标识和所述存储器当前保存的至 少一个高层故障业务标识中的任意一个是否相同， 所述高层故障业务标识用于 指示发生了故障的高层业务；
所述处理器， 还用于若检测结果为接收到的所述高层受影响业务标识和当 前保存的一个高层故障业务标识相同， 则确定所述故障产生消息中携带的高层 受影响业务标识所指示的高层业务发生故障。
31、 根据权利要求 29所述的故障处理系统， 其特征在于：
所述处理器， 还用于在检测到一个高层业务发生故障后， 获取对应的高层 故障业务标识， 所述高层故障业务标识用于指示发生了故障的高层业务；
所述处理器， 还用于检测获取到的所述高层故障业务标识和所述存储器当 前保存的至少一个所述高层受影响业务标识中的任意一个是否相同；
所述处理器， 还用于若检测结果为获取到的所述高层故障业务标识和当前 保存的一个高层受影响业务标识相同， 则确定相同的所述故障产生消息中携带 的高层受影响业务标识所指示的高层业务发生故障。
32、 根据权利要求 31所述的故障处理系统， 其特征在于：
所述处理器， 还用于若检测结果为获取到的所述高层故障业务标识和当前 保存的所有高层受影响业务标识均不相同， 则处理获取到的所述高层故障业务 标识所指示的高层业务的故障。
33、 根据权利要求 29至 32任一所述的故障处理系统， 其特征在于： 所述处理器， 还用于控制所述接收器接收所述低层故障管理系统发送的故 障恢复消息， 所述故障恢复消息携带有所述高层受影响业务标识；
所述处理器， 还用于检测所述故障恢复消息携带的所述高层受影响业务标 识所指示的高层业务的故障是否已经恢复；
所述处理器， 还用于若检测结果为还未恢复， 则处理所述高层业务的故障。
34、 根据权利要求 33所述的故障处理系统， 其特征在于， 所述故障产生消 息和所述故障恢复消息都还携带有低层业务故障标识和故障类型， 所述低层业 务故障标识用于指示所述发生故障告警的低层业务；
所述处理器， 还用于查找与所述故障恢复消息匹配的故障产生消息， 所述 匹配是指两个消息各自所包括的所述低层业务故障标识和所述故障类型均相 同；
所述处理器， 还用于在查找到与所述故障恢复消息匹配的故障产生消息时， 删除所述故障产生消息。
35、 一种通信故障管理系统， 其特征在于， 所述系统包括至少一个低层故 障管理系统和至少一个高层故障管理系统；
所述低层故障管理系统是如权利要求 24至 27任一所述的故障管理系统； 所述高层故障管理系统是如权利要求 28至 34任一所述的故障管理系统。
PCT/CN2013/078135 2013-06-27 2013-06-27 故障处理方法、装置和系统 WO2014205721A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CN201380003385.0A CN104521181B (zh) 2013-06-27 2013-06-27 故障处理方法、装置和系统
EP13888106.5A EP3001606B1 (en) 2013-06-27 2013-06-27 Fault processing method, device and system
PCT/CN2013/078135 WO2014205721A1 (zh) 2013-06-27 2013-06-27 故障处理方法、装置和系统
US14/979,383 US10091672B2 (en) 2013-06-27 2015-12-27 Fault handling method, apparatus and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2013/078135 WO2014205721A1 (zh) 2013-06-27 2013-06-27 故障处理方法、装置和系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/979,383 Continuation US10091672B2 (en) 2013-06-27 2015-12-27 Fault handling method, apparatus and system

Publications (1)

Publication Number Publication Date
WO2014205721A1 true WO2014205721A1 (zh) 2014-12-31

Family

ID=52140820

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/078135 WO2014205721A1 (zh) 2013-06-27 2013-06-27 故障处理方法、装置和系统

Country Status (4)

Country Link
US (1) US10091672B2 (zh)
EP (1) EP3001606B1 (zh)
CN (1) CN104521181B (zh)
WO (1) WO2014205721A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108632053A (zh) * 2017-03-16 2018-10-09 中兴通讯股份有限公司 业务信息的处理方法及装置

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106789354A (zh) * 2017-02-09 2017-05-31 北京市天元网络技术股份有限公司 一种基于铁路通信的故障诊断方法及装置
JP7032640B2 (ja) * 2017-12-28 2022-03-09 富士通株式会社 影響範囲特定プログラム、影響範囲特定方法、および影響範囲特定装置
CN109873719B (zh) * 2019-02-03 2019-12-31 华为技术有限公司 一种故障检测方法及装置
CN110120146A (zh) * 2019-04-25 2019-08-13 新浪网技术(中国)有限公司 一种基于报警中台系统的报警方法及报警中台系统
US11455202B2 (en) * 2020-09-03 2022-09-27 International Business Machines Corporation Real-time fault localization detection and notification
CN112579356B (zh) * 2020-12-21 2022-09-16 上海金仕达软件科技有限公司 一种故障处理方法及服务器

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101039498A (zh) * 2007-05-09 2007-09-19 中兴通讯股份有限公司 带有分布式告警处理的基站系统及其告警处理方法
CN101800675A (zh) * 2010-02-25 2010-08-11 华为技术有限公司 故障监控方法、监控设备及通信系统
CN101860802A (zh) * 2010-05-21 2010-10-13 中兴通讯股份有限公司 故障处理方法及系统
CN101917288A (zh) * 2010-08-04 2010-12-15 中兴通讯股份有限公司 告警处理方法及网管系统

Family Cites Families (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5768501A (en) * 1996-05-28 1998-06-16 Cabletron Systems Method and apparatus for inter-domain alarm correlation
US6253339B1 (en) * 1998-10-28 2001-06-26 Telefonaktiebolaget Lm Ericsson (Publ) Alarm correlation in a large communications network
US7237138B2 (en) * 2000-05-05 2007-06-26 Computer Associates Think, Inc. Systems and methods for diagnosing faults in computer networks
JP2002033767A (ja) * 2000-07-18 2002-01-31 Fujitsu Ltd ネットワーク管理システム
US20020171886A1 (en) * 2001-03-07 2002-11-21 Quansheng Wu Automatic control plane recovery for agile optical networks
US6965775B2 (en) * 2002-05-15 2005-11-15 Nokia Corporation Service-oriented protection scheme for a radio access network
EP1499049B1 (en) * 2003-07-18 2008-02-20 Alcatel Lucent Network restoration
US7346277B2 (en) * 2003-09-08 2008-03-18 Lucent Technologies Inc. Joint-layer restoration in packet-over-optical networks
JP4523444B2 (ja) * 2005-02-10 2010-08-11 富士通株式会社 通信ネットワークにおける障害の原因を特定する障害管理装置および方法
JP4847541B2 (ja) * 2005-12-23 2011-12-28 テレフオンアクチーボラゲット エル エム エリクソン（パブル） データパケットトラフィック輻輳を解決する方法及び装置
JP4758259B2 (ja) * 2006-01-31 2011-08-24 株式会社クラウド・スコープ・テクノロジーズ ネットワーク監視装置及び方法
US7830784B2 (en) * 2007-06-29 2010-11-09 Verizon Patent And Licensing Inc. Intelligent network restoration
US8913481B2 (en) * 2007-06-30 2014-12-16 Alcatel Lucent Method and system for efficient provisioning of multiple services for multiple failure restoration in multi-layer mesh networks
CN101159617B (zh) * 2007-11-22 2010-06-16 中国电信股份有限公司 一种融合全网全业务的二维故障管理方法和系统
WO2009087556A1 (en) * 2008-01-07 2009-07-16 Tejas Networks Limited A method for fast connectivity fault management [cfm] of a service -network
CN101335643B (zh) * 2008-08-06 2010-12-08 烽火通信科技股份有限公司 用于sdh设备告警相关性分析的方法及装置
US7865593B2 (en) * 2008-08-07 2011-01-04 At&T Intellectual Property I, L.P. Apparatus and method for managing a network
JP5631330B2 (ja) * 2008-12-23 2014-11-26 テレフオンアクチーボラゲット エル エム エリクソン（パブル） 大規模通信ネットワークシステムにおいて障害情報を配信する方法及び装置
US9753455B2 (en) * 2009-06-22 2017-09-05 Johnson Controls Technology Company Building management system with fault analysis
CN102484819A (zh) * 2009-08-25 2012-05-30 瑞典爱立信有限公司 使用ecn机制以直接向基站发信号通知拥塞
CN102238144A (zh) * 2010-04-30 2011-11-09 电子科技大学 多层网络中实现层间资源共享的方法、装置及系统
US20130159510A1 (en) * 2010-06-17 2013-06-20 Aware, Inc. Event Correlation Between Protocol Layers in a Network Device
US8406134B2 (en) * 2010-06-25 2013-03-26 At&T Intellectual Property I, L.P. Scaling content communicated over a network
CN104272680B (zh) * 2012-03-09 2017-05-17 英国电讯有限公司 用信号通知拥塞
US10143012B2 (en) * 2013-05-21 2018-11-27 Telefonaktiebolaget Lm Ericsson (Publ) Random access procedure in wireless device, radio base station and methods therein

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101039498A (zh) * 2007-05-09 2007-09-19 中兴通讯股份有限公司 带有分布式告警处理的基站系统及其告警处理方法
CN101800675A (zh) * 2010-02-25 2010-08-11 华为技术有限公司 故障监控方法、监控设备及通信系统
CN101860802A (zh) * 2010-05-21 2010-10-13 中兴通讯股份有限公司 故障处理方法及系统
CN101917288A (zh) * 2010-08-04 2010-12-15 中兴通讯股份有限公司 告警处理方法及网管系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3001606A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108632053A (zh) * 2017-03-16 2018-10-09 中兴通讯股份有限公司 业务信息的处理方法及装置

Also Published As

Publication number Publication date
US10091672B2 (en) 2018-10-02
EP3001606A4 (en) 2016-06-01
US20160135065A1 (en) 2016-05-12
CN104521181B (zh) 2018-01-16
EP3001606B1 (en) 2018-12-19
CN104521181A (zh) 2015-04-15
EP3001606A1 (en) 2016-03-30

Similar Documents

Publication Publication Date Title
WO2014205721A1 (zh) 故障处理方法、装置和系统
EP3386150B1 (en) Terminal failure processing method, device and system
WO2014166265A1 (en) Method, terminal, cache server and system for updating webpage data
CN107517110B (zh) 一种分布式系统中单板配置自恢复方法及装置
CN109347705B (zh) 一种环路检测方法及装置
WO2022127504A1 (zh) 网元管理方法、装置及存储介质
US9596313B2 (en) Method, terminal, cache server and system for updating webpage data
CN113328872A (zh) 故障修复方法、装置和存储介质
CN104065526A (zh) 一种服务器故障报警的方法和装置
CN104168126A (zh) 一种无人值守智能设备自维护管理系统及方法
CN102143011B (zh) 一种实现网络保护的装置及方法
WO2017220013A1 (zh) 业务处理方法及装置、存储介质
WO2014166218A1 (zh) 故障管理方法和装置
CN106533790A (zh) 部署存储服务器的方法、装置及系统、存储服务器
CN115102838B (zh) 服务器宕机风险的应急处理方法和装置、电子设备
US9594622B2 (en) Contacting remote support (call home) and reporting a catastrophic event with supporting documentation
US11271798B2 (en) Automated network link repair
KR102296903B1 (ko) 클라우드 스트리밍 서비스 시스템의 에러 복구 장치 및 방법
CN109039822B (zh) 一种bfd协议报文过滤方法及系统
CN107615708A (zh) 告警信息上报方法及装置
CN108920164A (zh) 云计算系统中主机的管理方法和装置
WO2024098938A1 (zh) 网络存储功能故障检测及容灾方法及相关设备
CN203414754U (zh) 一种物联网系统
US20210281642A1 (en) Moving storage volumes across network boundaries
CN109542643B (zh) 一种OpenStack系统中消息的恢复方法及装置

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: 13888106

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2013888106

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE