WO2012083740A1 - 告警检测方法及装置 - Google Patents

告警检测方法及装置 Download PDF

Info

Publication number
WO2012083740A1
WO2012083740A1 PCT/CN2011/080014 CN2011080014W WO2012083740A1 WO 2012083740 A1 WO2012083740 A1 WO 2012083740A1 CN 2011080014 W CN2011080014 W CN 2011080014W WO 2012083740 A1 WO2012083740 A1 WO 2012083740A1
Authority
WO
WIPO (PCT)
Prior art keywords
alarm
alarm detection
priority
detection point
detection
Prior art date
Application number
PCT/CN2011/080014
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 中兴通讯股份有限公司
Publication of WO2012083740A1 publication Critical patent/WO2012083740A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06Management of faults, events, alarms or notifications

Definitions

  • the present invention relates to the field of communications, and in particular to an alarm detection method and apparatus.
  • BACKGROUND With the growth of networks and the development of communication technologies, network and mobile terminal users continue to grow, and the related bearer transmission services have also been rapidly developed.
  • the network management or maintenance operation device is required to collect and filter related performance and alarm information during the transmission process, and the final result is fed back to the management interface. Since the alarm is generally caused by abnormality of the communication module, power supply, clock, fan, circuit, etc. of the device, this information undoubtedly requires special attention of the user.
  • the filtering method used in the alarm reporting is generally to establish an alarm-related matching domain, and the generated alarm is matched with the alarm in the alarm domain to determine whether the alarm is reported or the alarm relationship model tree is established to enable a high-level alarm. In the root direction, the low-level alarm is placed in the direction of the leaf, and each alarm suppresses the sub-alarm below it.
  • the method can suppress the derivative alarm to a certain extent and reduce the number of alarms reported, the method of suppressing the alarm by the alarm association can only be adapted to the scenario where the alarm rules are relatively fixed. Or the dynamic change of the alarm item will result in the re-construction of the entire model structure, which will affect the alarm processing and reporting, which will greatly reduce the alarm processing efficiency.
  • the present invention provides an alarm detection method and apparatus for the problem that the alarm suppression rule or the alarm item dynamically changes when the alarm processing efficiency is not high.
  • an alarm detection method including: constructing an alarm detection tree according to a position of each alarm detection point in a service architecture, wherein each alarm detection point is set with a detected alarm type; The alarm is detected according to an alarm detection tree.
  • the method further includes: setting an alarm reporting priority of each alarm detection point; and detecting the alarm by using the alarm detection tree, including: The alarm detection tree performs alarm detection on each alarm detection point and reports an alarm with a higher priority than the alarm reporting priority.
  • the step of setting an alarm reporting priority of each alarm detection point includes: setting an alarm alarm detection point to set a priority of the reported alarm to a current alarm reporting priority of the alarm detection point, and reporting the alarm The priority is set to the alarm reporting priority of all its child nodes.
  • the step of setting the priority of the alarm reporting of each alarm detection point further includes: if the alarm detection point has no reported alarm, the alarm reporting priority of the parent node of the alarm detection point is used as the alarm detection point. The current alarm is reported to the priority.
  • the alarm carries the service source point information.
  • the method further includes: setting service configuration information in the at least one alarm detection point in the alarm detection tree, where the service configuration information includes the alarm detection point.
  • each alarm detection point is further provided with an alarm processing priority, and each alarm detection point detects the alarm received according to the alarm processing priority.
  • the method further includes: setting an alarm processing parameter of each alarm detection point, where the alarm processing parameter includes at least one of the following: an alarm generation/disappear confirmation time, whether to block, whether to participate Priority filtering.
  • an alarm detection apparatus including: a service model module, configured to construct an alarm detection tree according to a position of each alarm detection point in a service architecture, wherein each alarm detection point is The detected alarm type is set; the detecting module is configured to detect the alarm according to the alarm detection tree.
  • the method further includes: setting a module, configured to set an alarm reporting priority for each alarm detection point; the detecting module is configured to traverse the alarm detection tree from a root node of the alarm detection tree, and perform alarm detection on each alarm detection point, An alarm with a higher priority than the alarm reporting priority is reported.
  • the alarm carries the service source point information; at least one alarm detection point in the alarm detection tree is provided with service configuration information, and the service configuration information includes a correspondence between the alarm detection point and the service source point.
  • the alarm detection tree is constructed according to the position of each alarm detection point in the service architecture, and there is no absolute alarm suppression relationship between the alarm detection points at all levels.
  • FIG. 2 is a flowchart of an alarm detecting method according to a second embodiment of the present invention
  • FIG. 3 is a flowchart according to the present invention.
  • FIG. 4 is a flowchart of an alarm detection method according to Embodiment 3 of the present invention
  • FIG. 5 is a schematic diagram of a service flow in a Synchronous Digital Hierarchy (SDH) device
  • FIG. 6 is a schematic diagram of a correspondence between an alarm and a status bit in the embodiment shown in FIG. 5
  • FIG. 7 is a schematic diagram of an alarm detection according to Embodiment 5 of the present invention
  • FIG. 8 is a structural block diagram of an alarm detecting apparatus according to Embodiment 6 of the present invention.
  • Embodiment 1 Referring to FIG. 1, a flowchart of an alarm detecting method according to Embodiment 1 of the present invention is shown, which includes steps S102 to S104. Step S102: Construct an alarm detection tree according to the location of each alarm detection point in the service architecture.
  • An alarm detection point is a location on the device that detects an alarm. It can be an actual physical port or a service channel or a virtual point.
  • the location where the alarm needs to be detected can be considered as an alarm detection point. Because different services have their own business hierarchy, the location of the alarm detection point in the business architecture is determined by its business hierarchy. When it is necessary to perform alarm detection on each branch in the architecture, it is necessary to set a detection point in each level of the service in the architecture.
  • the SDH multiplexing mapping structure is a signal adaptation to a virtual container (Virtual Container, referred to as In the VC), a plurality of VC channels are multiplexed into the Synchronous Transport Module Level N (STM-N) in multiple stages and transmitted in the optical port. At this time, it is necessary to monitor the STM-N and set the detection points at all levels of the signal.
  • STM-N Synchronous Transport Module Level N
  • the other optical transport network (OTN) or Packet Transport Network (PTN) has another service architecture layer.
  • the location of the detection point is at the parent node or the child node.
  • the sub-node of the port node in the SDH is a regenerator section (Regenerator Section, abbreviated as RS).
  • the RS is a multiplexing section (MS).
  • the MS is an access unit (AU).
  • the structure determines the location of the alarm detection point.
  • the type of the alarm that can be detected by the alarm detection point is set in each alarm detection point.
  • Step S104 detecting an alarm according to the alarm detection tree. In this step, the alarm can be detected step by step from the root node of the alarm detection tree.
  • the alarms received by the alarm detection point may be detected according to the set alarm type, and then the corresponding alarm processing may be performed according to the setting, for example, reporting an alarm higher than a certain alarm level.
  • a person skilled in the art may also set a method for detecting an alarm of the alarm detection tree according to actual needs, such as starting detection from a certain level or a certain node, or starting detection from a leaf node, etc., the present invention There is no limit to this.
  • the high-level alarm is placed in the root direction, and the low-level alarm is placed in the direction of the leaf. Each alarm suppresses the sub-alarm below it.
  • the alarm detection tree is constructed according to the location of each alarm detection point in the service architecture. There is no absolute alarm suppression relationship between the alarm detection points at all levels. When the alarm suppression rule or alarm item dynamically changes, it is not necessary. The alarm detection tree is reconstructed to solve the problem that the alarm processing efficiency is not high when the alarm suppression rule or the alarm item is dynamically changed, thereby improving the efficiency of the alarm processing.
  • Embodiment 2 Referring to FIG.
  • Step S202 Construct an alarm detection tree according to the location of each alarm detection point in the service architecture. The type of the detected alarm is set in each alarm detection point.
  • Step S204 Set an alarm reporting priority of each alarm detection point.
  • the alarm reporting priority indicates the priority of the alarm reporting, which is related to the service supported by the specific device, the location of the detection point where the alarm is located, and the type of alarm. Initially, an initial value of the alarm reporting priority is set for each alarm detection point, and may be 0 or any other suitable value, which can be appropriately set by a person skilled in the art according to actual conditions.
  • Step S206 Set alarm processing parameters of each alarm detection point.
  • the alarm processing parameter may include at least one of the following: an alarm generation/disappearment confirmation time, whether to mask, or whether to participate in priority filtering.
  • Each alarm detection point processes the received alarm according to the set alarm processing parameters. It should be noted that, when the parameters are set, step S206 and step S204 may be performed simultaneously, or may be performed sequentially.
  • the service configuration information includes the correspondence between the alarm detection point and the service source point.
  • the service configuration information may be set in all the alarm detection points of the alarm detection tree, or may be set in some alarm detection points according to actual needs by those skilled in the art.
  • the alarm detection point that sets the service configuration information can obtain the corresponding relationship between the alarm detection point and the service source point.
  • the corresponding relationship between the alarm detection point and the service source point can also be provided to other alarm detection points through a certain contact or path.
  • the source point is the location of the service access seen from the user's perspective for the specific business.
  • the detection point is seen from the perspective of the device, and the location is detected on the traffic flow.
  • the source point is mainly used in some concurrency, protection and cross-business scenarios in communication devices. As shown in Figure 3, taking the service flow in the SDH as an example, the detection point 1 is the access point of the service entering the device. From the user's point of view, that is, the source point, the points inside other devices are detection points, such as Check points 2, 3, 4, 5, 6.
  • Step S208 traverse the alarm detection tree from the root node of the alarm detection tree, and perform alarm detection on each alarm detection point.
  • each alarm detection point in the alarm detection tree detects the alarm received by itself.
  • each alarm detection point detects an alarm received by itself according to a preset alarm processing parameter.
  • the alarm carries information of a service source point.
  • each alarm detection point is set with an alarm processing priority, which is used to indicate the sequence in which the alarm detection point processes the received alarm. After receiving the alarm reported to it, each alarm detection point uses the alarm processing priority to detect and process the received alarm.
  • Step S212 Each alarm detection point determines whether there is an alarm with a higher priority than the alarm priority. If yes, step S214 is performed, and if no, step S216 is performed.
  • each alarm detection point detects the alarm that is received by itself, and determines whether there is an alarm with a higher priority than the alarm of the current node.
  • Step S214 The alarm detection point reports an alarm with a higher priority than the alarm reporting priority, and uses the priority of the reported alarm to update the current alarm reporting priority of the node; and simultaneously transmits to all of the child nodes.
  • the current alarm reporting priority of all the child nodes is updated to the priority level, and the current alarm detection process of the alarm detection point ends.
  • the alarm detection point of the alarm can be reported separately.
  • the system can uniformly report and report the alarms to be reported by each alarm detection point.
  • the alarm carries the information of the service source point.
  • Step S216 The alarm reporting priority of the parent node of the alarm detection point is used as the current alarm reporting priority of the alarm detection point. If the alarm detection point does not detect the alarm that needs to be reported, the alarm is reported to the parent node as the current alarm reporting priority.
  • Embodiment 3 Referring to FIG. 4, a flowchart of an alarm detection method according to Embodiment 3 of the present invention is shown, which includes steps S402 to S408.
  • Step S402 According to the location of each alarm detection point in the service architecture, construct a detection point service model tree, that is, an alarm detection tree, register the alarm items to be detected at each detection point, and according to the association relationship between the specific alarms and the location The location in the service, for which an alarm reporting priority is set.
  • the creation or modification of the service model tree (that is, the alarm detection tree) can be performed dynamically at any time. For example, when the PTN device changes its service configuration, the corresponding alarm detection points need to be modified simultaneously;
  • the business model is basically static, and generally does not accompany the change of the business. It only needs to construct the detection point model at the initial time.
  • Step S404 Set service configuration information in at least one alarm detection point, and parse the corresponding relationship between the alarm detection point and the source point and save. In this step, the extraction of the relationship between the detection point and the source point is associated with the change of the service configuration.
  • Step S406 Set alarm processing parameters in each alarm detection point.
  • the alarm processing parameters include at least one of the following: an alarm generation/disappearment confirmation time, whether to mask, and whether to participate in priority filtering.
  • Step S408 Timing period alarm detection processing. Specifically, step S408 includes steps S4082 to S4086.
  • Step S4082 The current cycle state of the alarm is uniformly collected. The alarm current period status refers to the alarm status acquired from the driver during this detection period.
  • Step S4084 The alarms of the respective detection points are processed step by step from the root detection point of the service model, and the alarm items of each detection point are processed according to the alarm processing parameters, and the alarms are processed according to the priority of the alarm processing, and the alarms with higher priority than the set alarms are reported.
  • the alarm of the priority is set to the priority of the alarm to be reported as the priority of the detection point, and is transmitted to the downstream sub-detection point. If no alarm is generated, the alarm of the parent node is reported to the priority.
  • Step S4086 Obtain the information of the alarms that need to be reported at all the detection points, and find the service configuration information according to the location information of the detection points, determine the corresponding source point, and package the alarm information together with the detection point and the source point to report to the upper-layer network management system or the console. Output interface.
  • the processing of step S408 is performed according to the new service model tree and configuration. With the present embodiment, the following effects are achieved: (1) The alarm detection tree is constructed based on the location of the detection point, and the alarm is effectively filtered by the priority transmission between the parent and child detection points.
  • the specific suppression rules are as follows: High-priority alarms suppress downstream low-priority alarms, and high-priority alarms of the same level suppress low-priority alarms. Upstream low-priority alarms do not suppress downstream high-priority alarms.
  • This relatively flexible alarm filtering rule can effectively reduce the reporting of invalid alarms and meet the alarm reporting requirements in more fields.
  • the information of the source is added to the source point location information, so that the user can directly learn the alarm that the accessed service has an alarm.
  • Embodiment 4 Referring to FIG. 5, a schematic diagram of an SDH optical board service detection point model according to Embodiment 4 of the present invention is shown.
  • the optical board service detection point model of the SDH is constructed by using the optical board of the SDH device as an example, that is, the SDH optical board service alarm detection tree is used for alarm detection processing.
  • Step S502 According to the layer structure of the path of the multiplexed mapping of the SDH, customize a set of alarm reporting priority reported by the alarm for all the alarms to be detected, and construct an SDH detection point service model tree, that is, an SDH alarm detection tree, at each layer. The detection point installs the detected alarm item.
  • the built-in alarm detection tree is traversed from the root node, and the buffer of the alarm status is constructed and formatted so that each alarm item corresponds to the alarm status bit, as shown in FIG. 6 .
  • the buffer of the alarm status is constructed and formatted so that each alarm item corresponds to the alarm status bit, as shown in FIG. 6 .
  • four types of alarms A, B, C, and D are included, and the corresponding alarm status bits are VI, V2, and V3.
  • Step S504 Configure an alarm processing parameter, and the alarm detection point processes the alarm according to the alarm processing parameter.
  • the specific alarm processing parameters may include: alarm reporting/disappearing confirmation time, shielding of the alarm, and participation in priority filtering.
  • the alarm acknowledgement time that is, the alarm is generated after the N cycles are continuously generated, which can effectively prevent the alarm from being shaken. The alarms that are set to be blocked by the alarm are not reported.
  • Step S506 Enter the timing processing, collect the alarm status of the current period of all the alarm items, fill it into the constructed buffer, and correspond one-to-one with the alarm items.
  • Step S508 The alarm is processed in order. Step S508 includes steps S5082 through S5086.
  • Step S5082 First set the priority of the alarm generated by the detection point to all the sub-detection points, and if it is the root detection point, set the alarm priority of the root node to 0.
  • Step S5084 The alarm item is processed from the highest priority alarm, and the priority of the detection point alarm is initially the priority of the parent detection point. (1. The order of processing alarms at each detection point is to start processing from high-priority alarms to ensure that if high-priority alarms are generated, the subsequent low-priority alarms are suppressed. 2. The initial priority of this detection point For the priority of the parent detection point, only the priority higher than the parent detection point can be reported, and the priority of the detection point is raised to the priority of the alarm.
  • step S5084 includes steps A to J.
  • Step A Read the alarm status collected in the current period from the corresponding buffer. If the status is generated, go to step B; otherwise, go to step G.
  • Step B If the current alarm generation status is true, clear the counter to be generated, and go to step C. If the current alarm generation status is false, generate a counter plus 1, and go to step E. Among them, the counter is set to count the detection period.
  • Step C If the alarm reporting status is true, go to step D; otherwise, go to step F.
  • Step D Compare the priority of the alarms reported by the detection point with the priority of the alarm.
  • Step E If the generated count is greater than the set confirmation time, set the alarm generation status to true, go to step F; otherwise, go to step J.
  • Step F Compare the priority of the alarms reported by the detection point with the priority of the alarm. If the alarm is reported to have a small priority or the alarm does not participate in the filtering, the alarm needs to be reported, the reported status is set to true, and the detection is performed.
  • Point alarm reporting priority refers to the priority of this alarm (not required when not participating in filtering), and go to step J.
  • Step G If the current alarm generation state is true, go to step H; if the current alarm generation state is false, go to step J.
  • Step H Add the disappearing counter. If the disappearing count is greater than the configured disappearing confirmation time, set the alarm generating state to false, and go to step I.
  • Step I If the alarm reporting status is true, you need to clear the reported alarm. The status of the report is changed to false. Go to step J.
  • Step J Determine whether the alarm information needs to be reported or the report disappears. If the current time stamp needs to be recorded, the information is saved. Go to Step A to process the next alarm item.
  • Step S5086 If the detection point alarm is not processed, the process proceeds to step S5084, and the next alarm item is processed. If all the alarms of the detection point are processed, if there is another detection point, the process goes to step S5082; if the detection point is the last one The detection point completes the processing of the entire step S508.
  • Embodiment 5 Referring to FIG. 7, a block diagram of a structure of an alarm detecting apparatus according to Embodiment 5 of the present invention is shown.
  • the apparatus includes: The service model module 702 is configured to construct an alarm detection tree according to the location of each alarm detection point in the service architecture, where each alarm detection point is set with a detected alarm type; and the detection module 704 is configured to detect according to the alarm detection tree.
  • Alarm Preferably, the alarm detecting apparatus of this embodiment further includes: a setting module 706, configured to set an alarm reporting priority for each alarm detecting point; the detecting module 704 is configured to traverse the alarm detecting tree from a root node of the alarm detecting tree, Each alarm detection point performs alarm detection and reports an alarm with a higher priority than the alarm reporting priority.
  • the alarm carries the service source point information; at least one alarm detection point in the alarm detection tree is provided with service configuration information, where the service configuration information includes a correspondence between the alarm detection point and the service source point.
  • the setting module 706 is further configured to set the priority of the reported alarm to the current alarm reporting priority of the alarm detection point when the alarm is reported on the alarm detection point, and set the alarm reporting priority to all of the alarms. The alarm reporting priority of the child node is reported. If the alarm is not reported, the alarm reporting priority of the parent node of the alarm detection point is used as the current alarm reporting priority of the alarm detection point.
  • the setting module 706 is further configured to set an alarm processing priority in each alarm detection point, and each alarm detection point detects the alarm received according to the alarm processing priority.
  • the setting module 706 is further configured to set an alarm processing parameter of each alarm detection point, and the alarm processing parameter includes at least one of the following: an alarm generation/disappear confirmation time, whether to mask, or whether to participate in priority filtering.
  • Embodiment 6 Referring to FIG. 8, a block diagram of a structure of an alarm detecting apparatus according to Embodiment 6 of the present invention is shown.
  • the apparatus includes: a service model module 802: is set to be a place where an alarm needs to be detected in a service structure configured by the device.
  • the alarm collection module 804 is configured to obtain a status of generating the current alarm.
  • the alarm processing module 806 is configured to traverse the detection point of the alarm detection tree from the root node, and process each alarm point in a sequence according to the registered alarm processing priority order, and set the alarm to be reported in the report state.
  • the source point detection point configuration module 808 is set to set the service flow information in the module, and parses out the corresponding information table of the detection point and the source point.
  • the alarm reporting module 810 is configured to uniformly report and report the alarms to be reported to the upper-layer network management system or the console interface.
  • the alarm collection module 804, the alarm processing module 806, and the alarm reporting module 810 are equivalent to the detection module 704 in the embodiment shown in FIG.
  • the method for performing alarm detection by using the alarm detecting apparatus of this embodiment includes: a step of modifying a service model, a step of setting a source point detection point association relationship, and a step of reporting an alarm on a timing processing.
  • Step S902-904 shows a flow of steps for applying the alarm detection device of the present embodiment to create a modified service model
  • step S906 shows a flow of steps for applying the alarm detection device of the present embodiment to set a source point detection point association relationship.
  • S908-912 shows a flow of steps for applying the alarm detection device of the present embodiment to periodically report the alarm.
  • the method for performing alarm detection by using the alarm detecting apparatus of this embodiment includes the following steps S902 to
  • Step S902 Set a detection point in the service model module according to the user requirement, create a service model tree, and install an alarm that needs to be detected.
  • Step S904 Traverse the service model tree, and format the corresponding data table of the alarm item and the alarm status bit.
  • Step S906 Receive a service configuration command, parse the source point and the detection point correspondence table, and save the source point detection point configuration module.
  • Step S908 Collect and acquire the status of all the alarms, and fill the alarm status into the corresponding status bits according to the formatted structure.
  • step S910 the formatted data is traversed, and all the alarms on all the detection points are processed in sequence, and the alarm information to be generated/cancelled is saved in the detection point.
  • Step S912 Obtain the alarm information that needs to be reported, and obtain the source point information according to the location information of the detection point, and package and report it together with the report alarm information.
  • the dynamic addition and deletion of the alarm item, the filtering report, and the source location of the alarm are quickly determined, so that the alarm reporting information is more effectively utilized to complete the device fault location.
  • the alarm detection method and device provided by the present invention are applicable to various communication fields, and are particularly applicable to alarm processing of transmission devices such as SDH, OTN, and PTN in the transmission bearer field. Compared with the solution provided by the prior art, it can better adapt to various bearer transmission services and report the source alarms more effectively.
  • modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明公开了一种告警检测方法及装置,其中,告警检测方法包括:按照每个告警检测点在业务架构中的位置,构建告警检测树,其中,每个告警检测点中设置有检测的告警类型;根据告警检测树检测所述告警。通过本发明,解决了告警抑制规则或者告警项动态变化时,告警处理效率不高的问题,进而达到了提高告警处理效率的效果。

Description

告警检测方法及装置 技术领域 本发明涉及通信领域, 具体而言, 涉及一种告警检测方法及装置。 背景技术 随着网络的增长和通讯的技术的发展, 网络及手机终端用户不断增长, 与之相关 的承载传输业务也得到迅猛的发展。 在承载业务的传输过程中, 需要依赖网管或者维 护操作设备对传输过程中的相关性能、 告警信息进行采集过滤, 并将最终得结果反馈 到管理界面。 由于告警一般是由设备的通信模块、 电源、 时钟、 风扇、 电路等部件的 不正常引起, 因此, 这些信息无疑需要用户特别的关注。 近年来, 随着多业务承载地 逐步发展, 传输网络结构的复杂度和灵活度不断增加, 告警信息的数量猛增, 相互的 关联关系也更复杂。 如何对海量的告警进行快速有效的分析, 并尽可能将告警产生的 各种信息上报, 成为快速定位故障的关键。 目前, 告警上报时采用的过滤方法一般都是建立告警关联匹配域, 将产生的告警 与所属告警域里面的告警进行匹配, 决定本告警是否上报, 或者建立告警关系模型树, 使高等级的告警放在根方向, 低等级告警放在叶子方向, 每个告警都抑制其下方的子 告警。 通过这些方式虽然能够在一定程度上达到抑制衍生告警, 减少上报告警数量的 目的, 但是, 单纯通过告警关联抑制告警的方式大都只能适应于告警规则比较固定的 场景下,一旦告警的抑制规则或者告警项动态变化,将会导致整个模型结构重新构建, 从而对告警处理和上报产生影响, 使得告警处理效率大大降低。 发明内容 针对上述的告警抑制规则或者告警项动态变化时, 告警处理效率不高的问题, 本 发明提供了一种告警检测方法及装置。 根据本发明的一个方面, 提供了一种告警检测方法, 包括: 按照每个告警检测点 在业务架构中的位置, 构建告警检测树, 其中, 每个告警检测点中设置有检测的告警 类型; 根据告警检测树检测所述告警。 优选地, 在构建告警检测树的步骤之后, 上述方法还包括: 设置每个告警检测点 的告警上报优先级; 使用告警检测树检测告警的步骤包括: 从告警检测树的根结点遍 历告警检测树, 对每个告警检测点进行告警检测, 并上报优先级高于告警上报优先级 的告警。 优选地, 设置每个告警检测点的告警上报优先级的步骤包括: 上报告警的告警检 测点将上报的告警的优先级设置为本告警检测点的当前告警上报优先级, 并将该告警 上报优先级设置为其所有的子结点的告警上报优先级。 优选地, 设置每个告警检测点的告警上报优先级的步骤还包括: 若本告警检测点 无上报的告警, 则使用本告警检测点的父结点的告警上报优先级作为本告警检测点的 当前告警上报优先级。 优选地, 告警中携带有业务来源点信息; 在构建告警检测树的步骤之后, 上述方 法还包括: 在告警检测树中的至少一个告警检测点中设置业务配置信息, 业务配置信 息包括告警检测点与业务来源点的对应关系。 优选地, 每个告警检测点中还设置有告警处理优先级, 每个告警检测点根据告警 处理优先级对其接收的告警进行检测。 优选地, 在构建告警检测树的步骤之后, 上述方法还包括: 设置每个告警检测点 的告警处理参数, 告警处理参数包括以下至少之一: 告警的产生 /消失确认时间、 是否 屏蔽、 是否参与优先级过滤。 根据本发明的另一方面, 提供了一种告警检测装置, 包括: 业务模型模块, 设置 为按照每个告警检测点在业务架构中的位置, 构建告警检测树, 其中, 每个告警检测 点中设置有检测的告警类型; 检测模块, 设置为根据告警检测树检测所述告警。 优选地, 还包括: 设置模块, 设置为为每个告警检测点设置告警上报优先级; 检 测模块设置为从告警检测树的根结点遍历告警检测树, 对每个告警检测点进行告警检 测, 并上报优先级高于告警上报优先级的告警。 优选地, 告警中携带有业务来源点信息; 告警检测树中的至少一个告警检测点中 设置有业务配置信息, 业务配置信息包括告警检测点与业务来源点的对应关系。 通过本发明, 采用根据各个告警检测点在业务架构中的位置构建告警检测树, 各 级告警检测点之间并无绝对的告警抑制关系, 当告警的抑制规则或者告警项动态变化 时, 无须对整个告警检测树进行重新构建, 从而解决了告警抑制规则或者告警项动态 变化时, 告警处理效率不高的问题, 进而达到了提高告警处理效率的效果。 附图说明 此处所说明的附图用来提供对本发明的进一步理解, 构成本申请的一部分, 本发 明的示意性实施例及其说明用于解释本发明, 并不构成对本发明的不当限定。 在附图 中: 图 1是根据本发明实施例一的一种告警检测方法的流程图; 图 2是根据本发明实施例二的一种告警检测方法的流程图; 图 3 是根据本发明实施例的一种传输同步数字系统 (Synchronous Digital Hierarchy, 简称为 SDH) 设备内的业务流的示意图; 图 4是根据本发明实施例三的一种告警检测方法的流程图; 图 5是根据本发明实施例四的一种 SDH的光板业务检测点模型的示意图; 图 6是图 5所示实施例中告警与状态位的对应关系的示意图; 图 7是根据本发明实施例五的一种告警检测装置的结构框图; 图 8是根据本发明实施例六的一种告警检测装置的结构框图; 图 9是应用图 8所示告警检测装置进行告警检测的流程图。 具体实施方式 下文中将参考附图并结合实施例来详细说明本发明。 需要说明的是, 在不冲突的 情况下, 本申请中的实施例及实施例中的特征可以相互组合。 实施例一 参照图 1, 示出了根据本发明实施例一的一种告警检测方法的流程图, 该方法包 括步骤 S102至步骤 S104。 步骤 S102: 按照每个告警检测点在业务架构中的位置, 构建告警检测树。 告警检测点即为设备上检测告警的某个位置, 可以是实际物理上的一个端口, 也 可以是一个业务通道或者一个虚拟点, 总之需要检测告警的位置就可以认为是一个告 警检测点。 因不同的业务都有各自的业务层次架构, 告警检测点在业务架构中的位置由其业 务层次架构决定。 当需要对架构中的每一个分支进行告警检测时, 就需要在架构中每 一级别的业务中设定检测点, 比如, SDH复用映射结构是信号适配到虚容器 (Virtual Container, 简称为 VC ) 中, 再多个 VC 通道通过多级复用到同步传输模块 N 级 ( Synchronous Transport Module level N, 简称为 STM-N)中, 在光端口中传输。这时, 需要对 STM-N监控, 就在信号内各级业务设定检测点。其他的业务光传送网(Optical Transport Network, 简称为 OTN)或者分组传送网 (Packet Transport Network, 简称为 PTN) 有另外的业务架构层, 根据架构层决定检测点的位置是在父节点还是子节点。 SDH中端口节点的子节点是再生段 (Regenerator Section, 简称为 RS), RS下面是复 用段(Multiplexing Section, 简称为 MS), MS下面是通道(Access Unit, 简称为 AU), 这种业务结构决定了告警检测点的位置。 其中, 每个告警检测点中设置有该告警检测点能够检测的告警类型。 步骤 S104: 根据告警检测树检测告警。 本步骤中, 可以从告警检测树的根结点起, 逐级检测告警。 具体实施时, 可以由 每个告警检测点对本结点接收的告警, 根据设置的告警类型进行检测, 进而根据设置 进行相应的告警处理, 如对高于某一告警级别的告警进行上报等。 当然, 本领域技术 人员也可以根据实际需要, 设置告警检测树的检测告警的方法, 如从设定的某一级或 某一个结点开始检测, 或者从叶结点开始检测等等, 本发明对此不作限制。 相关技术中, 建立告警关系模型树时, 高等级的告警放在根方向, 低等级告警放 在叶子方向, 每个告警都抑制其下方的子告警, 一旦告警的抑制规则或者告警项动态 变化, 将会导致整个模型结构重新构建, 从而对告警处理和上报产生影响, 使得告警 处理效率大大降低。 通过本实施例, 采用根据各个告警检测点在业务架构中的位置构 建告警检测树, 各级告警检测点之间并无绝对的告警抑制关系, 当告警的抑制规则或 者告警项动态变化时, 无须对整个告警检测树进行重新构建, 从而解决了告警抑制规 则或者告警项动态变化时, 告警处理效率不高的问题, 进而达到了提高告警处理效率 的效果。 实施例二 参照图 2, 示出了根据本发明实施例二的一种告警检测方法的流程图, 该方法包 括步骤 S202至步骤 S216。 步骤 S202: 按照每个告警检测点在业务架构中的位置, 构建告警检测树。 其中, 每个告警检测点中设置有检测的告警类型。 步骤 S204: 设置每个告警检测点的告警上报优先级。 告警上报优先级表示告警上报的优先等级, 与具体设备支持的业务, 告警所在的 检测点位置以及告警类型相关。 初始时, 为每个告警检测点设置一个告警上报优先级的初始值, 如可以为 0, 也 可以为其它任意适当的值, 本领域技术人员可以根据实际情况适当设置。 步骤 S206: 设置每个告警检测点的告警处理参数。 告警处理参数可以包括以下至少之一: 告警的产生 /消失确认时间、 是否屏蔽、 是 否参与优先级过滤。 每个告警检测点根据设置的告警处理参数为接收到的告警进行相应地处理。 需要说明的是, 在设置参数时, 步骤 S206和步骤 S204可以同时进行, 也可以不 分先后顺序地进行。 步骤 S208: 在告警检测树中的至少一个告警检测点中设置业务配置信息。 业务配置信息包括告警检测点与业务来源点的对应关系。 可以在告警检测树的全部结点即全部告警检测点中设置业务配置信息, 也可以由 本领域技术人员根据实际需求在部分告警检测点中设置。 设置了业务配置信息的告警 检测点可以自身获取告警检测点与业务来源点的对应关系, 也可以通过一定的联系或 路径向其它告警检测点提供告警检测点与业务来源点的对应关系。 来源点是针对具体业务来说, 从用户的角度看到的业务接入的位置。 检测点是从 设备的角度看到的, 业务流上检测位置。 来源点主要应用在通讯设备中的一些并发、 保护以及交叉业务场景中。 如图 3 中所示, 以传输 SDH中的业务流为例, 检测点 1 是业务进入设备的接入点, 从用户角度看, 也就是来源点, 其他设备内部的点都是检 测点, 如检测点 2、 3、 4、 5、 6。 如果在检测点处检测到了告警上报, 对于用户来说 并不清楚这个告警是自己接入的那条业务出了问题,如果上报告警信息中增加来源点, 就能根据告警检测点中的业务配置信息, 直接将告警跟业务接入点关联起来。 优选的, 一个告警检测点中仅设置反映本告警检测点与业务来源点的对应关系的 业务配置信息。 需要说明的是, 步骤 S208也可以和步骤 S204、 S206同时进行, 或不分先后顺序 地进行。 步骤 S210: 从告警检测树的根结点遍历告警检测树, 对每个告警检测点进行告警 检测。 本步骤中, 从告警检测树的根结点开始, 遍历告警检测树, 告警检测树中的每个 告警检测点检测其自身接收到的告警。 优选的, 每个告警检测点根据预先设置的告警 处理参数检测其自身收到的告警。 另外, 本实施例中, 告警携带有业务来源点的信息。 优选的, 每个告警检测点中设置有告警处理优先级, 用于指示告警检测点处理接 收到的告警的先后顺序。 每个告警检测点在接收到向其报告的告警后, 使用该告警处 理优先级对其接收到的告警进行检测处理。 步骤 S212: 每个告警检测点判断是否有优先级高于告警优先级的告警, 若是, 则 执行步骤 S214, 若否, 则执行步骤 S216。 本步骤中, 每个告警检测点检测其自身接收到的告警, 并判断接收到的告警中, 是否有优先级高于本结点的告警上报优先级的告警。 步骤 S214: 本告警检测点上报优先级高于告警上报优先级的告警, 并使用该上报 的告警的优先级更新本结点的当前的告警上报优先级; 同时, 向其所有子结点透传该 优先级, 更新其所有子结点的当前的告警上报优先级为该优先级, 本告警检测点的本 次告警检测流程结束。 上报告警的告警检测点可以单独上报该告警, 优选的, 也可以由系统在遍历完告 警检测树后, 统一打包上报各告警检测点需上报的告警。 本实施例中, 因告警携带有业务来源点信息, 所以一旦告警上报, 可以使系统快 速地确定出现故障的业务, 从而快速定位导致告警上报和故障。 步骤 S216: 使用本告警检测点的父结点的告警上报优先级作为本告警检测点的当 前告警上报优先级。 若告警检测点未检测到需要上报的告警, 则使用其父结点的告警上报优先级, 作 为其自身的当前告警上报优先级。 实施例三 参照图 4, 示出了根据本发明实施例三的一种告警检测方法的流程图, 该方法包 括步骤 S402至步骤 S408。 步骤 S402: 按照各个告警检测点在业务架构中的位置, 构建检测点业务模型树, 即告警检测树, 在每个检测点上注册需要检测的告警项, 并根据具体告警之间关联关 系和所在业务中的位置, 为其设定一个告警上报优先等级。 本步骤中, 创建或者修改业务模型树 (即告警检测树) 可以动态地, 在任何时刻 进行, 比如, 在 PTN设备, 业务配置改变时, 对应的告警检测点的也需要同步修改; 对于 SDH设备业务模型基本是静态的,一般不会伴随业务该配变化, 只需要初始时构 建一次检测点模型。 步骤 S404: 在至少一个告警检测点中设置业务配置信息, 解析出告警检测点和来 源点的对应关系并保存。 本步骤中, 检测点与来源点关系的提取跟业务配置的改变关联进行。 步骤 S406: 在每个告警检测点中设置告警处理参数。 告警处理参数包括以下至少之一: 告警的产生 /消失确认时间、 是否屏蔽以及是否 参与优先级过滤。 步骤 S408: 定时周期告警检测处理。 具体地, 步骤 S408包括步骤 S4082至步骤 S4086。 步骤 S4082: 告警当前周期状态统一采集。 告警当前周期状态是指, 在本检测周期从驱动获取的告警状态。 如果设定了确认 周期数是 5, 表示连续 5个周期从驱动获取的状态都是有告警, 则此告警产生并根据 优先级决定是否上报。 告警当前周期状态也可以从硬件中获取。 步骤 S4084: 从业务模型的根检测点开始逐级处理各个检测点的告警, 每个检测 点告警项根据告警处理参数, 按照告警处理优先级顺序处理告警, 上报优先级高于设 定的告警上报优选级的告警, 将需要上报的告警的优先级设定为本检测点的优先级, 并向下游子检测点传递, 如果没有产生上报的告警, 则透传父节点的告警上报优先级。 步骤 S4086: 获取所有检测点需要上报的告警的信息, 同时根据检测点的位置信 息查找业务配置信息, 确定对应的来源点, 将告警信息和检测点、 来源点一起打包上 报给上层网管或者控制台输出界面。 上述步骤中, 步骤 S402和步骤 S404完成后的第一个定时检测告警处理周期里, 根据新的业务模型树和配置进行步骤 S408的处理。 通过本实施例, 达到了以下效果: (1 ) 基于检测点位置构建告警检测树, 通过父 子检测点间传递优先级的方式实现告警的有效过滤, 在告警检测树中, 具体抑制规则 如下: 上游高优先级告警抑制下游低优先级告警, 同等级高优先级告警抑制低优先级 告警, 上游低优先级告警不抑制下游高优先级告警。 这种相对灵活的告警过滤规则, 既有效的减少了无效告警的上报, 又能够满足更多领域的告警上报需求。 (2) 上报的 信息除了告警项信息、 告警检测点位置还增加了来源点位置信息, 使用户直接了解到 接入的业务出现了告警, 同时有助于快速定位导致告警上报的故障。 (3 ) 以告警检测 树的方式组织告警, 动态的增删检测点或者检测点上面的告警项时, 不会影响整个检 测点模型的架构, 使其能够适应几乎所有通信领域的告警处理。 另外, 检测点本身定 位告警的位置, 不需要每个告警再保存, 减少了数据量。 实施例四 参照图 5, 示出了根据本发明实施例四的一种 SDH的光板业务检测点模型的示意 图。本实施例中, 以 SDH类的设备的光板为例, 构建 SDH的光板业务检测点模型图, 即, SDH的光板业务告警检测树, 进行告警检测处理。 图 5中, Board表示主板, Port 表示端口, RS表示再生段, MS表示复用段, AU表示通道。 其中, Board检测点设置 的告警检测类型为 A和 B, Port一级的检测点设置的告警检测类型均为 C和 D。 本实施例的告警检测方法包括步骤 S502至步骤 S510。 步骤 S502: 根据 SDH的复用映射的路径的层结构, 为所有需要检测的告警定制 一套告警上报的告警上报优先级, 并构建 SDH检测点业务模型树, 即 SDH告警检测 树, 在各层的检测点安装检测的告警项。 构建完成告警检测树后, 从根节点遍历构建 的告警检测树, 构建告警状态的缓冲区, 并进行格式化, 使每个告警项与本告警状态 位对应, 如图 6所示。 图 6中, 包括四类告警 A、 B、 C、 D, 对应的告警状态位分别为 VI、 V2、 V3、
V4。 告警采集时, 直接将告警状态写入告警对应的 V域中即可。 如, 告警采集时, 直 接将告警 A的状态写入其对应的 VI域中, 将告警 B的状态写入其对应的 V2域中, 等。 步骤 S504: 配置告警处理参数, 告警检测点根据告警处理参数处理告警。 具体告警处理参数可以包括: 告警上报 /消失确认时间、 告警的屏蔽、 是否参与优 先级过滤。 告警确认时间, 即连续产生 N个周期后方上报告警, 这样可以有效的防止 告警抖动; 设置了告警屏蔽的告警则不再上报; 是否参与优先级过滤, 即是否被高优 先级的告警抑制, 如果设置不参与过滤, 则认为是一个单独的告警, 不受高优先级告 警的影响, 产生则上报, 不产生则主动消失。 步骤 S506: 进入定时处理, 采集所有告警项的当前周期的告警状态, 将其填入构 建的缓冲区中, 与告警项一一对应。 步骤 S508: 按照顺序处理告警。 步骤 S508包括步骤 S5082至步骤 S5086。 步骤 S5082: 先将本检测点产生的告警的优先级设置到所有子检测点, 如果是根 检测点, 将根节点的告警优先级设置为 0。 步骤 S5084: 从最高优先级的告警开始处理告警项, 本检测点告警的优先级初始 为父检测点优先级。(1.在每个检测点处理告警的顺序是,从高优先级的告警开始处理, 保证如果高优先级的告警产生了, 抑制后面的低优先级告警。 2.本检测点的优先级初 始为父检测点的优先级, 只有高于父检测点的优先级才可能上报, 同时将本检测点的 优先级升高到此上报告警的优先级。 如果是根节点, 没有父节点, 本检测点的优先级 初始为 0。) 具体地, 步骤 S5084包括步骤 A至步骤 J。 步骤 A: 从对应的缓冲区读取当前周期采集的告警状态, 如果状态为产生, 转步 骤 B; 否则, 转步骤 G。 步骤 B: 如果当前告警产生状态为 true, 清空产生计数器, 转步骤 C; 如果当前 告警的产生状态 false, 产生计数器加 1, 转步骤 E。 其中, 计数器设置为对检测周期进行计数。 步骤 C: 如果告警的上报状态为 true, 转步骤 D; 否则, 转步骤 F。 步骤 D: 比较本检测点告警上报优先级和本告警的优先级, 如果本检测点告警上 报优先级高且参与过滤, 则告警需要上报消失, 设置上报状态为 false; 否则, 将本检 测点的告警上报优先级设置为当前告警的优先级(非参与过滤不需要设置)。转步骤 J。 步骤 E:如果产生计数大于设定的确认时间,设置告警产生状态为 true,转步骤 F; 否则, 转步骤 J。 步骤 F: 比较本检测点告警上报优先级和本告警的优先级, 如果本检测点告警上 报优先级小或者告警不参与过滤, 则告警需要上报, 将上报装态设置为 true, 并将本 检测点告警上报优先级提到本告警的优先级 (未参与过滤时不需要), 转步骤 J。 步骤 G: 如果当前的告警的产生状态为 true, 转步骤 H; 如果当前的告警的产生 状态为 false, 转步骤 J。 步骤 H: 增加消失计数器, 如果消失计数大于配置的消失确认时间, 设置告警产 生状态为 false, 转步骤 I。 步骤 I:如果告警的上报状态为 true,需要消失上报的告警,上报状态修改为 false, 转步骤 J。 步骤 J: 判断告警信息是否需要上报产生或者上报消失, 如果需要记录当前时间 戳, 并将信息保存。 转步骤 A处理下一个告警项。 步骤 S5086: 如果检测点告警没有处理完继续转步骤 S5084, 处理下一个告警项, 如果处理完本检测点所有的告警, 如果还有下一个检测点则转步骤 S5082; 如果本检 测点是最后一个检测点完成整个步骤 S508的处理。 步骤 S510: 上报告警。 在告警处理完之后, 获取需要上报的告警, 根据告警检测点信息查询对应的来源 点信息后, 将告警项信息, 检测点和来源点位置一起打包上报。 实施例五 参照图 7, 示出了根据本发明实施例五的一种告警检测装置的结构框图, 该装置 包括: 业务模型模块 702, 设置为按照各个告警检测点在业务架构中的位置, 构建告警 检测树, 其中, 每个告警检测点中设置有检测的告警类型; 检测模块 704, 设置为根 据告警检测树检测告警。 优选地, 本实施例的告警检测装置还包括: 设置模块 706, 设置为为每个告警检 测点设置告警上报优先级; 检测模块 704设置为从告警检测树的根结点遍历告警检测 树, 对每个告警检测点进行告警检测, 并上报优先级高于告警上报优先级的告警。 优选地, 告警中携带有业务来源点信息; 告警检测树中的至少一个告警检测点中 设置有业务配置信息, 该业务配置信息包括告警检测点与业务来源点的对应关系。 优选地, 设置模块 706还设置为当告警检测点上报告警时, 将上报的告警的优先 级设置为本告警检测点的当前告警上报优先级, 并将该告警上报优先级设置为其所有 的子结点的告警上报优先级; 当本告警检测点无上报的告警, 则使用本告警检测点的 父结点的告警上报优先级作为本告警检测点的当前告警上报优先级。 优选地, 设置模块 706还设置为设置每个告警检测点中的告警处理优先级, 每个 告警检测点根据告警处理优先级对其接收的告警进行检测。 优选地, 设置模块 706还设置为设置每个告警检测点的告警处理参数, 告警处理 参数包括以下至少之一:告警的产生 /消失确认时间、是否屏蔽、是否参与优先级过滤。 实施例六 参照图 8, 示出了根据本发明实施例六的一种告警检测装置的结构框图, 该装置 包括: 业务模型模块 802: 设置为在设备配置的业务结构中为需要检测告警的地方创建 告警检测点,将这些检测点按照在业务架构中的位置连接起来组成的树状检测点模型, 即告警检测树; 每个检测点注册需要检测的告警类型并设定告警上报优先级。 告警采集模块 804: 设置为获取当前告警的产生状态。 告警处理模块 806: 设置为从根节点遍历告警检测树的检测点, 对每一个检测点 按照注册的告警处理优先级大小顺序处理单个告警, 对于需要上报的告警设置为上报 状态。 来源点检测点配置模块 808: 设置为将业务流信息设置在此模块, 解析出检测点 和来源点的对应信息表。 告警上报模块 810: 设置为将需要上报的告警统一打包上报到上层网管系统或者 控制台界面。 其中, 上述告警采集模块 804、告警处理模块 806和告警上报模块 810相当于图 7 所示实施例中的检测模块 704。 如图 9所示, 使用本实施例的告警检测装置进行告警检测时的方法包括: 创建修 改业务模型的步骤、设置来源点检测点关联关系的步骤、和定时处理上报告警的步骤。 其中,步骤 S902-904示出了应用本实施例的告警检测装置创建修改业务模型的步 骤流程,步骤 S906示出了应用本实施例的告警检测装置设置来源点检测点关联关系的 步骤流程,步骤 S908-912示出了应用本实施例的告警检测装置定时处理上报告警的步 骤流程。 使用本实施例的告警检测装置进行告警检测的方法包括以下步骤 S902 至步骤
步骤 S902: 根据用户需求, 在业务模型模块中设定检测点, 创建业务模型树, 安 装需要检测点告警。 步骤 S904: 遍历业务模型树, 格式化告警项与告警状态位的对应数据表。 步骤 S906: 收到业务配置命令, 解析来源点和检测点对应关系表, 保存在来源点 检测点配置模块。 步骤 S908: 采集获取所有告警的状态, 按照格式化后的结构, 将告警状态填入对 应的状态位。 步骤 S910: 遍历格式化后数据, 对所有检测点上的所有告警顺序处理, 将需要上 报产生 /取消的告警信息保存检测点中。 步骤 S912: 获取需要上报的告警信息, 并根据检测点位置信息获取来源点信息, 跟上报告警信息一起打包上报。 通过本实施例, 实现了告警项的动态增删、 过滤上报以及快速确定告警的来源位 置, 从而更加有效的利用告警上报信息完成设备故障定位。 需要说明的是, 本发明提供的告警检测方法和装置, 适用于多种通讯领域, 尤其 适用于传输承载领域 SDH、 OTN以及 PTN等传输设备的告警处理。 与现有技术提供 的方案相比, 能够更好的适应各种承载传输业务, 以及更有效的上报源生告警。 显然, 本领域的技术人员应该明白, 上述的本发明的各模块或各步骤可以用通用 的计算装置来实现, 它们可以集中在单个的计算装置上, 或者分布在多个计算装置所 组成的网络上, 可选地, 它们可以用计算装置可执行的程序代码来实现, 从而, 可以 将它们存储在存储装置中由计算装置来执行, 并且在某些情况下, 可以以不同于此处 的顺序执行所示出或描述的步骤, 或者将它们分别制作成各个集成电路模块, 或者将 它们中的多个模块或步骤制作成单个集成电路模块来实现。 这样, 本发明不限制于任 何特定的硬件和软件结合。 以上所述仅为本发明的优选实施例而已, 并不用于限制本发明, 对于本领域的技 术人员来说, 本发明可以有各种更改和变化。 凡在本发明的精神和原则之内, 所作的 任何修改、 等同替换、 改进等, 均应包含在本发明的保护范围之内。

Claims

权 利 要 求 书
1. 一种告警检测方法, 包括:
按照每个告警检测点在业务架构中的位置, 构建告警检测树, 其中, 所 述每个告警检测点中设置有检测的告警类型; 根据所述告警检测树检测所述告警。
2. 根据权利要求 1所述的方法, 其中,
在所述构建告警检测树的步骤之后, 所述方法还包括: 设置所述每个告 警检测点的告警上报优先级;
所述使用所述告警检测树检测所述告警的步骤包括: 从所述告警检测树 的根结点遍历所述告警检测树, 对所述每个告警检测点进行告警检测, 并上 报优先级高于所述告警上报优先级的告警。
3. 根据权利要求 2所述的方法, 其中, 所述设置所述每个告警检测点的告警上 报优先级的步骤包括:
所述上报告警的告警检测点将所述上报的告警的优先级设置为本告警检 测点的当前告警上报优先级, 并将该告警上报优先级设置为其所有的子结点 的告警上报优先级。
4. 根据权利要求 3所述的方法, 其中, 所述设置所述每个告警检测点的告警上 报优先级的步骤还包括:
若本告警检测点无上报的告警, 则使用本告警检测点的父结点的告警上 报优先级作为本告警检测点的当前告警上报优先级。
5. 根据权利要求 1所述的方法, 其中, 所述告警中携带有业务来源点信息; 在所述构建告警检测树的步骤之后, 所述方法还包括: 在所述告警检测 树中的至少一个所述告警检测点中设置业务配置信息, 所述业务配置信息包 括所述告警检测点与所述业务来源点的对应关系。
6. 根据权利要求 1所述的方法, 其中, 所述每个告警检测点中还设置有告警处 理优先级, 所述每个告警检测点根据所述告警处理优先级对其接收的告警进 行检测。 根据权利要求 1所述的方法, 其中, 在所述构建告警检测树的步骤之后, 所 述方法还包括:
设置所述每个告警检测点的告警处理参数, 所述告警处理参数包括以下 至少之一: 告警的产生 /消失确认时间、 是否屏蔽、 是否参与优先级过滤。 一种告警检测装置, 包括:
业务模型模块, 设置为按照每个告警检测点在业务架构中的位置, 构建 告警检测树, 其中, 所述每个告警检测点中设置有检测的告警类型;
检测模块, 设置为根据所述告警检测树检测所述告警。 根据权利要求 8所述的装置, 其中, 所述装置还包括: 设置模块, 设置为为 所述每个告警检测点设置告警上报优先级;
所述检测模块设置为从所述告警检测树的根结点遍历所述告警检测树, 对所述每个告警检测点进行告警检测, 并上报优先级高于所述告警上报优先 级的告警。 根据权利要求 8或 9所述的装置,其中,所述告警中携带有业务来源点信息; 所述告警检测树中的至少一个所述告警检测点中设置有业务配置信息, 所述 业务配置信息包括所述告警检测点与所述业务来源点的对应关系。
PCT/CN2011/080014 2010-12-20 2011-09-22 告警检测方法及装置 WO2012083740A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2010105968773A CN102546275A (zh) 2010-12-20 2010-12-20 告警检测方法及装置
CN201010596877.3 2010-12-20

Publications (1)

Publication Number Publication Date
WO2012083740A1 true WO2012083740A1 (zh) 2012-06-28

Family

ID=46313118

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/080014 WO2012083740A1 (zh) 2010-12-20 2011-09-22 告警检测方法及装置

Country Status (2)

Country Link
CN (1) CN102546275A (zh)
WO (1) WO2012083740A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105634775B (zh) * 2014-10-31 2020-01-03 中兴通讯股份有限公司 一种告警信息派单方法及装置
CN104767648B (zh) * 2015-04-24 2018-02-13 烽火通信科技股份有限公司 一种基于告警回溯的根源告警定位功能实现方法及系统
CN106326262A (zh) * 2015-06-29 2017-01-11 中兴通讯股份有限公司 告警查询方法及装置、光传输网络管理系统
CN106411584B (zh) * 2016-09-21 2019-10-22 武汉众邦领创技术有限公司 一种基于加权距离的通信业务告警分析方法及系统
CN112527253A (zh) * 2020-12-04 2021-03-19 中国航空工业集团公司成都飞机设计研究所 一种告警及应急处置程序设计方法
CN114500248B (zh) * 2022-04-01 2022-08-05 北京锐融天下科技股份有限公司 一种针对互联网软件系统中业务的监控与告警方法及系统

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1635551A (zh) * 2003-12-30 2005-07-06 上海贝尔阿尔卡特股份有限公司 通用多层次告警处理方法
CN101145841A (zh) * 2007-06-27 2008-03-19 中兴通讯股份有限公司 一种光传输网络处理告警信息上报的方法

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101145944B (zh) * 2007-07-04 2011-01-05 中兴通讯股份有限公司 一种实现告警处理的方法
KR100922582B1 (ko) * 2007-07-20 2009-10-21 한국전자통신연구원 중심점 분할 기법을 이용한 로그 기반의 역추적 시스템 및방법

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1635551A (zh) * 2003-12-30 2005-07-06 上海贝尔阿尔卡特股份有限公司 通用多层次告警处理方法
CN101145841A (zh) * 2007-06-27 2008-03-19 中兴通讯股份有限公司 一种光传输网络处理告警信息上报的方法

Also Published As

Publication number Publication date
CN102546275A (zh) 2012-07-04

Similar Documents

Publication Publication Date Title
WO2012083740A1 (zh) 告警检测方法及装置
Mas et al. An efficient algorithm for locating soft and hard failures in WDM networks
CN1855784B (zh) 基于分组的网络内的线路定时
CN101286835B (zh) 一种时钟跟踪的方法、装置及网元设备
CN102724086B (zh) 检测传输链路质量的方法及装置
JP4764420B2 (ja) イーサネット(登録商標)oamネットワークにおけるアラーム指示および抑制(ais)機構
CN102833061B (zh) 基于无缝冗余环网的提高时钟精度的方法及节点
EP3687088A1 (en) Method for transmitting data in optical network and optical network device
KR102268902B1 (ko) 비트 블록 스트림에 대한 코드 에러 검출 방법 및 디바이스
WO1998039870A2 (en) System and method for managing network resources using distributed intelligence and state management
ES2688527T3 (es) Método y aparato de despliegue de servicio y dispositivo de red
CN107276818B (zh) 一种应用于光传输设备的增强型告警抑制方法
CN101390339A (zh) 网络通信量监控设备
CN111052632A (zh) 一种光传送网中时延测量的方法、装置和系统
WO1998044666A9 (en) Integration of a path verification message within a signal
WO1998044666A2 (en) Integration of a path verification message within a signal
JP5060057B2 (ja) 通信回線監視システム、中継装置、及び通信回線監視方法
US20140204778A1 (en) Communication system, communication device, and communication method
US20110149752A1 (en) Tracing support in a router
CN106936510A (zh) 调节光功率的方法、网络设备和网管设备
US7843838B1 (en) Communication network route tracing
JP7163256B2 (ja) 光トランシーバおよびネットワークシステム
CN102546204B (zh) Tdm电路仿真业务远端告警信息的传递方法及系统
WO2006015526A1 (fr) Procede de mise en oeuvre et dispositif de protocole de commutation de protection faisant intervenir un mode de communication ip
CN102804651B (zh) 网络中断期间通过伪线连接保持时分复用

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11851293

Country of ref document: EP

Kind code of ref document: A1