WO2020007188A1 - 一种告警方法及装置 - Google Patents

一种告警方法及装置 Download PDF

Info

Publication number
WO2020007188A1
WO2020007188A1 PCT/CN2019/091603 CN2019091603W WO2020007188A1 WO 2020007188 A1 WO2020007188 A1 WO 2020007188A1 CN 2019091603 W CN2019091603 W CN 2019091603W WO 2020007188 A1 WO2020007188 A1 WO 2020007188A1
Authority
WO
WIPO (PCT)
Prior art keywords
alarm
status
oamid
reporting
mmg
Prior art date
Application number
PCT/CN2019/091603
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 WO2020007188A1 publication Critical patent/WO2020007188A1/zh

Links

Images

Classifications

    • 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
    • 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
    • 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
    • H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
    • 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/0677—Localisation of faults
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route

Definitions

  • the embodiments of the present application relate to, but are not limited to, the technical field of Packet Transport Network (PTN) -Operation Management and Maintenance (OAM), and in particular, to an alarm method and device.
  • PTN Packet Transport Network
  • OAM Operation Management and Maintenance
  • the Endpoint Maintenance Entity
  • End Point (MEP)
  • MEGID remote maintenance entity endpoint identifier
  • the normal tunnel will generate an incorrect merge alarm (that is, an MMG alarm and an unexpected MEG and Mismerge) and fail to trigger protection switching, which will cause service interruption.
  • field programmable gate arrays can be used in PTN equipment to implement OAM functions.
  • FPGAs Field-Programmable Gate Arrays
  • current FPGAs have limited resources and cannot provide enough resources to store all OAM information at the same time.
  • FPGA logic resources if you change FPGAs with more resources, more funds are needed; if you add peripherals, the hardware design is risky and the stability is not desirable.
  • an embodiment of the present application provides an alarm method, including:
  • OAMID operation management and maintenance identifier
  • An embodiment of the present application further provides an alarm device, including:
  • the reading unit is configured to poll and read the saved OAMID.
  • the read OAMID generates an MMG alarm
  • the read OAMID is written to a designated register, and each OAMID uniquely identifies an OAM information
  • the reading unit is further configured to read the remote MEGID information from the latch register address according to the OAMID stored in the register;
  • the reporting unit is configured to report the MMG alarm and the remote MEGID information.
  • An embodiment of the present application further provides an alarm device, including a memory, a processor, and a computer program stored on the memory and executable on the processor.
  • an alarm device including a memory, a processor, and a computer program stored on the memory and executable on the processor.
  • the computer program is executed by the processor, the foregoing is implemented. Alert method.
  • An embodiment of the present application further provides a computer-readable storage medium.
  • the computer-readable storage medium stores an information processing program, and when the information processing program is executed by a processor, implements the steps of the foregoing alarm method.
  • the alarm method and device provided in the embodiment of the present application, by carrying the remote MEGID information when reporting the MMG alarm, so that the network administrator can quickly find out which damaged tunnel caused the OAM of the normal tunnel to generate the MMG alarm, so that the alarm can be processed quickly,
  • the normal tunnel service is restored, and only the OAMID that generates the MMG alarm is written to the FPGA, instead of writing all the OAMIDs to the FPGA, saving a lot of FPGA logic resources.
  • FIG. 1 is a first schematic flowchart of an alarm method according to an embodiment of the present application
  • FIG. 2 is a schematic structural diagram of an alarm device according to an embodiment of the present application.
  • FIG. 3 is a second schematic flowchart of an alarm method according to an embodiment of the present application.
  • FIG. 4 is a third flowchart of an alarm method according to an embodiment of the present application.
  • FIG. 5 is a fourth flowchart of an alarm method according to an embodiment of the present application.
  • the embodiments of the present application provide an alarm method and device.
  • By reporting the remote MEGID information when reporting an MMG alarm it is convenient for the network administrator to quickly find out which damaged tunnel caused the OAM of the normal tunnel. An MMG alarm is generated, and services of the normal tunnel are quickly restored.
  • FIG. 1 is a first schematic flowchart of an alarm method according to an embodiment of the present application. As shown in Figure 1, the alarm method includes:
  • step 101 the saved OAMID is read by polling, and if the read OAMID generates an MMG alarm, the read OAMID is written into a designated register, and each OAMID uniquely identifies an OAM message;
  • Step 102 Read the remote MEGID information from the latch register address according to the OAMID stored in the register;
  • Step 103 Report the MMG alarm and the remote MEGID information.
  • the read OAMID is written into a register designated by the FPGA, and the remote MEGID information is read from the latch register address of the FPGA according to the OAMID stored in the register.
  • the method before polling and reading the saved OAMID, the method further includes: receiving OAM information, generating a corresponding OAMID according to the OAM information, and saving the OAM information and its corresponding OAM ID.
  • the method further includes: when the MMG alarm is generated for the first time, setting a reporting state of the MMG alarm to a first state.
  • the first state may be a state of “producing an alarm and not applying for reading the remote MEGID”;
  • the writing the read OAMID to a designated register includes writing the read OAMID to the first state when a reported state of the MMG alarm corresponding to the read OAMID is the first state. If the designated register is successfully written, the reported status is changed to the second status.
  • the second state may be a state of “producing an alarm and applying for reading the remote MEGID”;
  • the reporting the MMG alarm and the remote MEGID information includes:
  • the read OAMID is written to a designated register, and if the writing is successful, the reporting status is modified to the first status Two states.
  • the second state may be a state of “producing an alarm and applying for reading the remote MEGID”;
  • the remote MEGID information is read from the latch register address, the MMG alarm and the remote MEGID information are reported, and the reporting status is reported Modified to the third state.
  • the third state may be a state of "alarm reported".
  • the method further includes:
  • the MMG alarm and the remote MEGID information are no longer reported; as an example, the third status may be "reported Alarm "status.
  • the reporting state is modified to a fourth state; as an example, the fourth state may be “reporting After the alarm disappears.
  • the MMG alarm disappears and is reported to a network administrator, and the reporting status is modified to the fourth status; as an example, the The fourth state may be a state in which "alarms reported have disappeared".
  • FIG. 2 is a schematic structural diagram of an alarm device according to an embodiment of the present application. As shown in Figure 2, the alarm device includes:
  • the reading unit is configured to poll and read the saved OAMID.
  • the read OAMID generates an MMG alarm
  • the read OAMID is written to a designated register, and each OAMID uniquely identifies an OAM information
  • the reading unit is further configured to read the remote MEGID information from the latch register address according to the OAMID stored in the register;
  • the reporting unit is configured to report the MMG alarm and the remote MEGID information.
  • the device further includes a configuration unit configured to receive OAM information, generate a corresponding OAMID according to the OAM information, and save the OAM information and its corresponding OAM ID.
  • the configuration unit requests a corresponding OAMID from the resource pool unit according to the OAM information, receives the OAMID generated by the resource pool unit, and saves the OAM information and the corresponding OAM ID to the storage unit.
  • the reading unit is configured to set a reporting state of the MMG alarm to a first state when the MMG alarm is generated for the first time; If the reporting status of the MMG alarm corresponding to the OAMID is the first status, write the read OAMID to a designated register, and if the writing is successful, modify the reporting status to Second state
  • the read OAMID is written to the designated register, and if the writing is successful, the reporting status is modified to the first status.
  • the reporting state is the second state
  • the remote MEGID information is read from the latch register address, and the reporting unit is notified to report the MMG alarm and the remote MEGID information, and The reporting status is modified to a third status.
  • the reading unit is further configured to no longer notify the reporting unit to report the report if the MMG alarm continues to be generated and the reporting state is the third state.
  • MMG alarm and the remote MEGID information are further configured to no longer notify the reporting unit to report the report if the MMG alarm continues to be generated and the reporting state is the third state.
  • the reporting state is modified to a fourth state.
  • the reporting unit When the alarm disappears and the reporting status is the third status, the reporting unit is notified to report the MMG alarm disappearing to the network manager, and the reporting status is modified to the fourth status.
  • the alarm device provided in the foregoing embodiment performs an alarm
  • only the above-mentioned division of the program modules is used as an example.
  • the above processing may be allocated by different program modules according to needs.
  • the internal structure is divided into different program modules to complete all or part of the processing described above.
  • the alarm device and the alarm method embodiment provided by the foregoing embodiments belong to the same concept. For specific implementation processes, refer to the method embodiment, and details are not described herein again.
  • the technical solution provided in the embodiment of the present application includes remote MEGID information when reporting an MMG alarm, so that the network administrator can quickly find out which damaged tunnel caused the OAM of the normal tunnel to generate the MMG alarm, so that the alarm can be processed quickly and normal as soon as possible.
  • Tunnel services and only write the OAMID that generates the MMG alarm to the FPGA, instead of writing all OAMIDs to the FPGA, saving a lot of FPGA logic resources.
  • FIG. 3 is a third flowchart of an alarm method provided by an embodiment of the present application. As shown in Figure 3, the alarm method includes:
  • Step 301 Receive the issued OAM information, generate a corresponding OAMID according to the OAM information, and save the OAM information and the corresponding OAMID.
  • a user may configure OAM information through a network management system or the CLI, and deliver the OAM information.
  • the configuration unit may receive the issued OAM information and save it to the storage unit, and apply for an OAMID from the resource pool unit according to the OAM information.
  • the resource pool unit sets an OAMID corresponding to the OAM information according to at least one of a channel layer (TMC layer), a channel layer (TMP layer), and a segment layer (TMS layer) in the OAM information, and one OAMID is unique Identifies an OAM message.
  • TMC layer channel layer
  • TMP layer channel layer
  • TMS layer segment layer
  • the configuration unit After receiving the OAMID generated by the resource pool unit, the configuration unit also saves the OAMID to the storage unit.
  • the local end and the corresponding remote end send a Continuity Check Message (CCM) to each other.
  • CCM Continuity Check Message
  • the reporting status of the MMG alarm is set to a status of "an alarm is generated and no application for reading the remote MEGID has been applied".
  • Step 302 Polling reads the saved OAMID, and writes the read OAMID when the reported status of the MMG alarm corresponding to the read OAMID is "alarm generated, and no application for reading the remote MEGID" is written. Into the register designated by the FPGA, if the writing is successful, the reported status is modified to the status of "an alarm has been generated and a request has been made to read the remote MEGID".
  • the reading unit can read the OAMID from the storage unit by polling, and write the read OAMID into a register designated by the FPGA.
  • step 303 when the alarm continues to be generated and the reporting status is "alarm generated, no application for reading the remote MEGID" is issued, the read OAMID is written to a register designated by the FPGA, and if the writing is successful Next, the reporting status is modified to a status of "an alarm has been generated and an application has been requested to read the remote MEGID".
  • the alarm continues to be generated and the reporting status is “Alarm generated, no application for reading the remote MEGID” is issued, it indicates that the writing in step 302 has failed.
  • Step 304 In the case where the alarm continues to be generated and the reporting status is "alarm generated, application for reading the remote MEGID" is performed, the remote MEGID information is read from the latch register address of the FPGA, and the MMG is reported Alarm and remote MEGID information, and modify the reported status to the status of "alarm reported".
  • the MMG alarm and remote MEGID information may be reported to a network management or other management unit.
  • Step 305 if the alarm continues to be generated and the reporting status is the status of "reported the alarm", no further reporting is performed;
  • step 306 if the alarm disappears and the reporting status is a status of "alarm generated, no application for reading remote MEGID" or a status of "alarm generated, application for reading remote MEGID" is reported, the reporting is reported. The status is changed to the status of "Reported alarm disappeared".
  • Step 307 In the case that the alarm disappears and the reporting status is "reported alarm”, the MMG alarm is reported to the network administrator, and the report status is changed to "reported alarm disappeared” status .
  • the reading unit can determine whether the alarm continues or disappears, modify the reporting status, and notify the reporting unit to report the alarm and the remote MEGID information when the reporting conditions are met.
  • FIG. 4 is a fourth flowchart of an alarm method provided by an embodiment of the present application. As shown in Figure 4, the alarm method includes:
  • Step 401 The configuration unit stores the OAM information issued by the network manager and the local OAMID applied to the resource pool unit to the storage unit;
  • the OAM information includes configuration information such as a MEG index (megindex), CC / CV enable information, MEP enable information, TMC layer, TMP layer, and TMS layer information.
  • configuration information such as a MEG index (megindex), CC / CV enable information, MEP enable information, TMC layer, TMP layer, and TMS layer information.
  • the configuration unit applies a corresponding OAMID to the resource pool unit according to different OAM information, and each OAMID can uniquely identify one piece of OAM information.
  • the resource pool unit can configure different OAMIDs for different OAM information.
  • an OAMID can be a key value. For example, the KEY value of the TMS layer is sectionId, and the KEY value of the TMC layer is pwid.
  • the applied OAMID information is stored in the storage unit.
  • Step 402 Start a timer, and the reading unit polls the storage unit periodically, and reads the corresponding CC, CV, MEP, OAMID and other OAM information from the storage unit. If the MEP is enabled, continue to step 403, otherwise continue to step 402 At this time, the reading unit reads another piece of OAM information from the storage unit;
  • Step 403 The reading unit reads the OAMID according to step 402, and reads the alarm information corresponding to the OAMID from the FPGA unit.
  • the local end and the corresponding remote end send CCM packets to each other.
  • the local MEGID and the remote MEGID are inconsistent, an MMG alarm is generated.
  • the reporting status of the MMG alarm is set to a state of “generating an alarm and no application for reading the remote MEGID”; when the read OAMID does not generate an alarm, The next OAMID is read, and if an alarm is read, step 404 is performed.
  • Step 404 In the case that the reported status of the MMG alarm corresponding to the OAMID read is "alarm generated, and no application for reading the remote MEGID has been reported", the reading unit writes the read OAMID to the FPGA The specified configuration register sets the reporting status of the alarm information to the status of "an alarm has been generated and an application has been requested to read the remote MEGID".
  • Step 405 The reading unit determines whether the alarm is continuously generated.
  • the reading unit may periodically read the MMG alarm information generated by the OAMID.
  • Su Sohu's judgment of whether the alarm continues to occur refers to checking whether the alarm information corresponding to this OAM has changed, and the alarm may have disappeared at this time; if the alarm corresponding to this OAM continues to occur, step 406 is performed. If the alarm corresponding to the OAM has disappeared, step 407 is performed.
  • Step 406 If the alarm is continuously generated, different processing is performed according to different reporting states.
  • the report status is "Alarm generated, no application for reading the remote MEGID"
  • the read OAMID is written to the configuration register designated by the FPGA, and if the write is successful, the The reporting status was changed to the status of “Alarm generated, application for reading remote MEGID”;
  • report status is "Alarm generated, application for reading remote MEGID" status, it indicates that the write has been successful, then read the remote MEGID from the latch register address of the FPGA according to the OAMID, and notify the reporting unit to report the MMG alarm Read the remote MEGID and change the reporting status to the status of "Reported an alarm”;
  • reporting status is "alarm reported", it means that the alarm has been reported, and it is not necessary to notify the reporting unit to report to the network management again.
  • step 407 the alarm disappears, and different processing is performed according to different reporting states.
  • reporting status is "alarm generated, no application for reading the remote MEGID", it means that the writing has not succeeded, and the alarm disappears, and the reporting status is directly changed to the "reported alarm disappeared" status;
  • reporting status is "Reported an alarm"
  • the first variable identifier, the reporting sequence number, and the reporting structure identifier are configured in advance.
  • FIG. 5 is a schematic flowchart of an alarm method according to an embodiment of the present application. As shown in Figure 5, the alarm method includes:
  • Step 501 Read the stored OAM information and OAMID, and go to the FPGA to read the corresponding MMG alarm according to the read OAMID.
  • the reporting status of the alarm information is set to the status of "an alarm is generated and no application for reading the remote MEGID has been applied".
  • step 502 is performed when the alarm is read.
  • step 502 when the reported status of the MMG alarm corresponding to the read OAMID is "alarm generated, and no application is requested to read the remote MEGID", the read OAMID is written into a configuration register designated by the FPGA.
  • the alarm occurs when the alarm is generated or the alarm disappears.
  • the status at the moment is compared with the status of the previous soft table to determine.
  • Step 503 If the alarm is continuously generated, different processing is performed according to different reporting states.
  • reporting status is “Alarm generated, no application for reading the remote MEGID”
  • the first variable identifier is "yes”. If it is, it means “allow to read the remote MEGID information”. The OAMID of this OAM can be written to the FPGA. If the write is successful , The first variable identification position is "No", which means "reading of remote MEGID information is not allowed”.
  • report status is “Alarm generated, application for reading remote MEGID”, read the remote MEGID information from the FPGA latch register, report the MMG alarm and remote MEGID information, and modify the report status.
  • the status is "Reported an alarm”.
  • reporting structure identification position 1, the reporting sequence number to indicate the number of reporting times, the reporting structure identification position to 1 to indicate that the alarm has been reported, and 0 to indicate that the alarm has not been reported.
  • the position of the first variable identifier needs to be yes, and the first variable identifier is used to indicate whether the remote MEGID information is allowed to be read. If it is, the FPGA is written, otherwise the configuration register of the FPGA is not written.
  • reporting status is "reported an alarm”, you do not need to report it again here, but you need to set the reporting structure identification position to 1.
  • step 504 the alarm disappears, and different processing is performed according to different reporting states.
  • reporting status is "Reported an alarm"
  • the alarm needs to be reported and disappeared.
  • the reporting status must be changed to the "Reported alarm disappeared” status. It is also necessary to set the identification position of the report structure to 1 and increase the sequence number by one.
  • the alarm method and device provided in the foregoing embodiments set corresponding OAMIDs for OAM information.
  • By reporting the remote MEGID when reporting MMG alarms it is convenient for the network administrator to quickly find out which damaged tunnel caused the OAM of the normal tunnel to generate MMG alarms. Restore normal tunnel services.
  • FPGAs can be used in PTN equipment to implement OAM functions. However, for example, if the MEGID is 128 bits (maximum configurable 8KOAM), a total of 8k * 128bit FPGA logic resources are required. The current FPGA resources are limited and cannot provide enough. Resources to store all OAMIDs at the same time, and facilitate reading the MEGID information of each OAM.
  • the alarm method provided in this application saves a lot of FPGA logic resources by writing the OAMID that generates the MMG alarm to the FPGA instead of writing all the OAMIDs to the FPGA.
  • Computer storage medium includes both volatile and nonvolatile implementations in any method or technology used to store information such as computer-readable instructions, data structures, program modules or other data.
  • Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or may Any other medium used to store desired information and which can be accessed by a computer.
  • a communication medium typically contains computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and may include any information delivery medium .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • Cardiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例公开了一种告警方法及装置，包括：轮询读取保存的操作管理和维护标识(OAMID)，在读取到的OAMID产生错误合并告警(MMG告警)的情况下，将读取到的OAMID写入指定的寄存器，每个OAMID唯一标识一条OAM信息；根据所述寄存器中保存的OAMID从锁存寄存器地址读取远端维护联合端点标识(MEGID)信息；上报所述MMG告警和所述远端MEGID信息。

Description

一种告警方法及装置
相关申请的交叉引用
本申请基于申请号为201810732500.2、申请日为2018年07月05日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此以引入方式并入本申请。
技术领域
本申请实施例涉及但不限于分组传送网(Package Transport Network，PTN)-操作管理和维护(Operation Administration and Maintenance，OAM)技术领域，具体涉及一种告警方法及装置。
背景技术
随着电信级以太网技术的发展，PTN作为传输网络已经被广泛应用，OAM作为检测网络故障的手段应用也越来越普遍。为了防止某个链路故障就导致业务中断，PTN部署需要配置保护倒换，从而保证某个链路故障业务可以倒换到正常链路工作，然而要保护倒换必然要配置OAM。目前，配置OAM时可能会由于网管配置问题或其它一些异常处理，存在一些残损隧道，而残损隧道恰好与此OAM所在的隧道出标签相同，如此，本端维护联合端点(MEG(MEG为维护实体端点(Maintenance Entity Point))End Point，MEP)收到残损隧道的连续性检查消息(Continuity Check Message，CCM)报文时，其携带的远端维护实体端点标识(MEGID)与本端的MEGID不同，这时就会导致正常隧道产生错误合并告警(即MMG告警，不期望的MEG Mismerge)而无法触发保护倒换，从而导致业务中断。如果隧道数量较少，可以通过网管或命令行界面(Command-Line Interface，CLI)一一排 查，但对于大容量和多跳的隧道而言，需要大量的时间排查相同出标签的隧道，可服务性能不高，无法达到现网业务快速恢复的要求。
另外，目前PTN设备中可以运用现场可编程门阵列(Field－Programmable Gate Array，FPGA)实现OAM功能，但是，目前的FPGA资源有限，尚不能提供足够多的资源来同时存储所有的OAM信息。为了满足足够多的FPGA逻辑资源需求，如果换个资源更多的FPGA，需要的资金也比较多；如果加外设，硬件设计风险大，稳定性差不可取。
发明内容
有鉴于此，本申请实施例提供了一种告警方法，包括：
轮询读取保存的操作管理和维护标识(OAMID)，在读取到的OAMID产生MMG告警的情况下，将读取到的OAMID写入指定的寄存器，每个OAMID唯一标识一条OAM信息；
根据所述寄存器中保存的OAMID从锁存寄存器地址读取远端MEGID信息；
上报所述MMG告警和所述远端MEGID信息。
本申请实施例还提供了一种告警装置，包括：
读取单元，配置为轮询读取保存的OAMID，在读取到的OAMID产生MMG告警的情况下，将读取到的OAMID写入指定的寄存器，每个OAMID唯一标识一条OAM信息；
所述读取单元，还配置为根据所述寄存器中保存的OAMID从锁存寄存器地址读取远端MEGID信息；
上报单元，配置为上报所述MMG告警和所述远端MEGID信息。
本申请实施例还提供了一种告警装置，包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现上述的告警方法。
本申请实施例还提供了一种计算机可读存储介质，所述计算机可读存储介质上存储有信息处理程序，所述信息处理程序被处理器执行时实现上述告警方法的步骤。
本申请实施例提供的告警方法及装置，通过上报MMG告警时携带远端的MEGID信息，如此方便网管快速排查出是哪条残损隧道导致正常隧道的OAM产生了MMG告警，以便快速处理告警，尽快恢复正常隧道的业务，并且只把产生MMG告警的OAMID写到FPGA，而不是把所有的OAMID全写入FPGA，节省了大量的FPGA逻辑资源。
本申请的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本申请而了解。本申请的目的和其他优点可通过在说明书、权利要求书以及附图中所特别指出的结构来实现和获得。
附图说明
附图用来提供对本申请技术方案的进一步理解，并且构成说明书的一部分，与本申请的实施例一起用于解释本申请的技术方案，并不构成对本申请技术方案的限制。
图1为本申请实施例提供的告警方法的流程示意图一；
图2为本申请实施例提供的告警装置的结构示意图；
图3为本申请实施例提供的告警方法的流程示意图二；
图4为本申请实施例提供的告警方法的流程示意图三；
图5为本申请实施例提供的告警方法的流程示意图四。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚明白，下文中将结合附图对本申请的实施例进行详细说明。需要说明的是，在不冲突的情况下， 本申请中的实施例及实施例中的特征可以相互任意组合。
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行。并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
针对背景技术中提出的技术问题，本申请实施例提供了一种告警方法及装置，通过上报MMG告警时携带远端的MEGID信息，如此方便网管快速排查出是哪条残损隧道导致正常隧道的OAM产生了MMG告警，快速恢复正常隧道的业务。
图1为本申请实施例提供的告警方法的流程示意图一。如图1所示，该告警方法，包括：
步骤101，轮询读取保存的OAMID，在读取到的OAMID产生MMG告警的情况下，将读取到的OAMID写入指定的寄存器，每个OAMID唯一标识一条OAM信息；
步骤102，根据所述寄存器中保存的OAMID从锁存寄存器地址读取远端MEGID信息；
步骤103，上报所述MMG告警和所述远端MEGID信息。
本实施例中，作为一种实施方式，将读取到的OAMID写入FPGA指定的寄存器，根据所述寄存器中保存的OAMID从所述FPGA的锁存寄存器地址读取远端MEGID信息。
在本申请的一种可选实施例中，在轮询读取保存的OAMID之前，该方法还包括：接收OAM信息，根据所述OAM信息生成对应的OAMID，并保存所述OAM信息及其对应的OAM ID。
在本申请的一种可选实施例中，该方法还包括：在首次产生所述MMG告警的情况下，将所述MMG告警的上报状态置为第一状态。作为一种示例，所述第一状态可以为“产生告警，未申请读取远端MEGID”的状态；
所述将读到的OAMID写入指定的寄存器，包括：在读取到的所述OAMID对应的所述MMG告警的上报状态为所述第一状态的情况下，将读取到的OAMID写入指定的寄存器，在写入成功的情况下，则将所述上报状态修改为第二状态。作为一种示例，所述第二状态可以为“产生告警，已申请读取远端MEGID”的状态；
所述上报所述MMG告警和所述远端MEGID信息，包括：
在继续产生MMG告警且所述上报状态为所述第一状态的情况下，将读取到的OAMID写入指定的寄存器，在写入成功的情况下，将所述上报状态修改为所述第二状态。作为一种示例，所述第二状态可以为“产生告警，已申请读取远端MEGID”的状态；
在继续产生MMG告警且所述上报状态为所述第二状态的情况下，则从锁存寄存器地址读取远端MEGID信息，上报所述MMG告警和远端MEGID信息，并将所述上报状态修改为第三状态。作为一种示例，所述第三状态可以为“上报过告警”的状态。
在本申请的一种可选实施例中，该方法还包括：
在继续产生MMG告警且所述上报状态为所述第三状态的情况下，不再上报所述MMG告警和所述远端MEGID信息；作为一种示例，所述第三状态可以为“上报过告警”的状态。
在告警消失且所述上报状态为所述第一状态或所述第二状态的情况下，则将所述上报状态修改为第四状态；作为一种示例，所述第四状态可以为“上报过告警消失”的状态。
在告警消失且所述上报状态为所述第三状态的情况下，则将所述MMG告警消失上报给网管，并将所述上报状态修改为所述第四状态；作为一种示例，所述第四状态可以为“上报过告警消失”的状态。
图2为本申请实施例提供的告警装置的结构示意图。如图2所示，该 告警装置，包括：
读取单元，配置为轮询读取保存的OAMID，在读取到的OAMID产生MMG告警的情况下，将读取到的OAMID写入指定的寄存器，每个OAMID唯一标识一条OAM信息；
所述读取单元，还配置为根据所述寄存器中保存的OAMID从锁存寄存器地址读取远端MEGID信息；
上报单元，配置为上报所述MMG告警和所述远端MEGID信息。
在本申请的一种可选实施例中，所述装置还包括：配置单元，配置为接收OAM信息，根据所述OAM信息生成对应的OAMID，并保存所述OAM信息及其对应的OAM ID。
作为一种实施方式，所述配置单元根据所述OAM信息向资源池单元申请对应的OAMID，接收资源池单元生成的OAMID，并将所述OAM信息及其对应的OAM ID保存到存储单元。
在本申请的一种可选实施例中，所述读取单元，配置为在首次产生所述MMG告警的情况下，将所述MMG告警的上报状态置为第一状态；在读取到的所述OAMID对应的所述MMG告警的上报状态为所述第一状态的情况下，将读取到的OAMID写入指定的寄存器，在写入成功的情况下，则将所述上报状态修改为第二状态；
在继续产生MMG告警且所述上报状态为所述第一状态的情况下，将读到的OAMID写入指定的寄存器，在写入成功的情况下，则将所述上报状态修改为所述第二状态；
在继续产生MMG告警且所述上报状态为所述第二状态的情况下，从锁存寄存器地址读取远端MEGID信息，通知所述上报单元上报所述MMG告警和远端MEGID信息，并将所述上报状态修改为第三状态。
在本申请的一种可选实施例，所述读取单元，还配置为在继续产生 MMG告警且所述上报状态为所述第三状态的情况下，不再通知所述上报单元上报所述MMG告警和所述远端MEGID信息；
在告警消失且所述上报状态为所述第一状态或所述第二状态的情况下，则将所述上报状态修改为第四状态。
在告警消失且所述上报状态为所述第三状态的情况下，则通知所述上报单元将所述MMG告警消失上报给网管，并将所述上报状态修改为所述第四状态。
需要说明的是：上述实施例提供的告警装置在进行告警时，仅以上述各程序模块的划分进行举例说明，实际应用中，可以根据需要而将上述处理分配由不同的程序模块完成，即将装置的内部结构划分成不同的程序模块，以完成以上描述的全部或者部分处理。另外，上述实施例提供的告警装置与告警方法实施例属于同一构思，其具体实现过程详见方法实施例，这里不再赘述。
本申请实施例提供的技术方案，通过上报MMG告警时携带远端的MEGID信息，如此方便网管快速排查出是哪条残损隧道导致正常隧道的OAM产生了MMG告警，以便快速处理告警，尽快恢复正常隧道的业务；并且只把产生MMG告警的OAMID写到FPGA，而不是把所有的OAMID全写入FPGA，节省了大量的FPGA逻辑资源。
下面通过具体的实施例对本申请技术方案进行详细说明。
具体示例一
图3为本申请实施例提供的告警方法的流程示意图三。如图3所示，该告警方法，包括：
步骤301，接收下发的OAM信息，根据所述OAM信息生成对应的OAMID，并保存所述OAM信息及对应的OAMID；
作为一种实施方式，用户可以通过网管或CLI配置OAM信息，并下 发OAM信息。
作为一种实施方式，可以由配置单元接收下发的OAM信息并保存到存储单元，并根据所述OAM信息向资源池单元申请OAMID。所述资源池单元根据所述OAM信息中的通路层(TMC层)、通道层(TMP层)和段层(TMS层)中的至少一种信息设置所述OAM信息对应的OAMID，一个OAMID唯一标识一条OAM信息。配置单元接收到资源池单元生成的OAMID后，同样将OAMID保存到存储单元。
其中，当OAM信息中连续性检测/连通性校验(Connectivity Check，CC/Connectivity Verification，CV)、MEP使能时，本端与对应的远端相互发送连续性检查消息(Continuity Check Message，CCM)报文，当本端MEGID与远端MEGID不一致时，产生MMG告警。
另外，在首次产生所述MMG告警的情况下，将所述MMG告警的上报状态置为“产生告警，未申请读取远端MEGID”的状态。
步骤302，轮询读取保存的OAMID，在读取到的OAMID对应的MMG告警的上报状态为“产生告警，未申请读取远端MEGID”的状态的情况下，将读取到的OAMID写入FPGA指定的寄存器，在写入成功的情况下，则将所述上报状态修改为“产生告警，已申请读取远端MEGID”的状态。
实际应用中，可以由读取单元从存储单元轮询读取OAMID，并将读到的OAMID写入FPGA指定的寄存器。
步骤303，在继续产生告警且所述上报状态为“产生告警，未申请读取远端MEGID”的状态的情况下，将读取到的OAMID写入FPGA指定的寄存器，在写入成功的情况下，则将所述上报状态修改为“产生告警，已申请读取远端MEGID”的状态。
在一实施例中，在继续产生告警且所述上报状态为“产生告警，未申请读取远端MEGID”的状态的情况下，则表明步骤302中写入失败。
步骤304，在继续产生告警且所述上报状态为“产生告警，已申请读取远端MEGID”的状态的情况下，则从FPGA的锁存寄存器地址读取远端MEGID信息，上报所述MMG告警和远端MEGID信息，并将所述上报状态修改为“上报过告警”的状态。
作为一种实施方式，可以上报所述MMG告警和远端MEGID信息给网管或其他管理单元。
步骤305，在继续产生告警且所述上报状态为“上报过告警”的状态的情况下，不再上报；
步骤306，在告警消失且所述上报状态为“产生告警，未申请读取远端MEGID”的状态或“产生告警，已申请读取远端MEGID”的状态的情况下，则将所述上报状态修改为“上报过告警消失”的状态。
步骤307，在告警消失且所述上报状态为“上报过告警”的状态的情况下，则将所述MMG告警消失上报给网管，并将所述上报状态修改为“上报过告警消失”的状态。
其中，上述步骤中，可以由读取单元判断是否继续产生告警或告警消失、修改上报状态以及在符合上报条件时，通知上报单元上报告警和远端MEGID信息。
其中，上述各个步骤的顺序仅为示例性说明，并不存在固定的前后顺序。
具体示例二
图4为本申请实施例提供的告警方法的流程示意图四。如图4所示，该告警方法，包括：
步骤401，配置单元把网管下发的OAM信息和向资源池单元申请的本地OAMID存储至存储单元；
其中，OAM信息包括：MEG索引(megindex)、CC/CV使能信息、 MEP使能信息、TMC层、TMP层和TMS层信息等配置信息。
其中，配置单元会根据不同的OAM信息去资源池单元申请对应的OAMID，每个OAMID能唯一标识一条OAM信息。资源池单元可以为不同的OAM信息配置不同的OAMID。另外，一个OAMID可以为一个键值(KEY值)，例如TMS层的KEY值为sectionId，TMC层的KEY值为pwid等，最后把申请到的OAMID信息存储至存储单元。
步骤402，启动定时器，读取单元定时轮询存储单元，从存储单元中读取相应的CC、CV、MEP、OAMID等OAM信息，如果MEP使能则继续执行步骤403，否则继续执行步骤402，此时读取单元从存储单元读取的是另一条OAM信息；
步骤403，读取单元根据步骤402读取到OAMID，从FPGA单元读取OAMID对应的告警信息；
其中，当OAM信息中CC、CV、MEP使能时，本端与对应的远端相互发送CCM报文，当本端MEGID与远端MEGID不一致时，产生MMG告警。
其中，在首次产生所述MMG告警的情况下，将所述MMG告警的上报状态置为“产生告警，未申请读取远端MEGID”的状态；在读取的OAMID没有产生告警的情况下，则读取下一个OAMID，读到告警则执行步骤404。
步骤404，在读取到的所述OAMID对应的所述MMG告警的上报状态为“产生告警，未申请读取远端MEGID”的状态的情况下，读取单元将读取的OAMID写入FPGA指定的配置寄存器，将告警信息的上报状态置为“产生告警，已申请读取远端MEGID”的状态。
步骤405，读取单元判断告警是否持续产生；
在一实施例中，读取单元可以周期性读取所述OAMID产生的MMG告警信息。其中，苏搜狐判断告警是否持续产生是指查看此条OAM对应的 告警信息是否已经发生变化，有可能此时告警已经消失；若此条OAM对应的告警持续产生，则执行步骤406，若此条OAM对应的告警已经消失，则执行步骤407。
步骤406，告警持续产生，则根据不同的上报状态进行不同的处理。
其中，在此上报状态有四种，分别为：
1、产生告警，未申请读取远端MEGID的状态；
2、产生告警，已申请读取远端MEGID的状态；
3、上报过告警的状态；
4、上报过告警消失的状态；
如果上报状态为“产生告警，未申请读取远端MEGID”的状态，则表明还没有写成功，则将读取的OAMID写入FPGA指定的配置寄存器，在写入成功的情况下，则将上报状态修改为“产生告警，已申请读取远端MEGID”的状态；
如果上报状态为“产生告警，已申请读取远端MEGID”的状态，则表明已经写入成功，则根据OAMID从FPGA的锁存寄存器地址读取远端MEGID，将通知上报单元上报MMG告警及读取的远端MEGID，并将上报状态修改为“上报过告警”的状态；
如果上报状态为“上报过告警”，则表明该告警已经上报，则不需要再次通知上报单元上报给网管。
步骤407，告警消失，则根据不同的上报状态进行不同的处理。
1、如果上报状态为“产生告警，未申请读取远端MEGID”的状态，则表明还没有写入成功，且告警消失，直接将所述上报状态修改为“上报过告警消失”的状态；
2、如果上报状态为“产生告警，已申请读取远端MEGID”的状态，则表明已经写入成功，且告警消失，直接将所述上报状态修改为“上报过 告警消失”的状态。
其中，在FPGA写下一条OAMID时，会自动覆盖上一条OAMID。
如果上报状态为“上报过告警”的状态，则表明已经写入成功，且已经上报告警，此时需要通知上报单元将告警消失上报，同时将上报状态修改为“上报过告警消失”的状态。
上述步骤406、步骤407并不存在固定的顺序。
具体示例三
本实施例中，预先配置第一变量标识、上报序列号、上报结构体标识。
图5为本申请实施例提供的告警方法的流程示意图五。如图5所示，该告警方法，包括：
步骤501，读取保存的OAM信息及OAMID，根据读取到的OAMID，去FPGA读取相应的MMG告警；
如何保存OAM信息以及如何申请OAMID等等可以参见前述实施例，在此不再赘述。
其中，首次产生告警的情况下，将告警信息的上报状态置为“产生告警，未申请读取远端MEGID”的状态。
其中，如果没有产生告警，则可以读取下一条OAMID，读到告警则执行步骤502。
步骤502，在读取的OAMID对应的MMG告警的上报状态为“产生告警，未申请读取远端MEGID”的状态的情况下，将读取的OAMID写入FPGA指定的配置寄存器。
需要继续查看此条OAM的告警信息是否发生变化，如果一直是产生状态继续步骤503，在告警消失的情况下则执行步骤504。
其中告警发生的是告警产生或是告警消失的变化，是会把此刻的状态同上次软表的状态作比较来进行判断。
步骤503，告警持续产生，则根据不同的上报状态进行不同的处理。
1、如果上报状态为“产生告警，未申请读取远端MEGID”的状态，则再次将读取的OAMID写入FPGA指定的配置寄存器，在写入成功的情况下，则将所述上报状态修改为“产生告警，已申请读取远端MEGID”的状态。
另外，写操作前，还需要判断第一变量标识是否为“是”，如果是，则表示“允许读远端MEGID信息”，可以向FPGA写入本条OAM的OAMID，在写入成功的情况下，则将第一变量标识位置为“否”，表示“不允许读远端MEGID信息”。
2、如果上报状态为“产生告警，已申请读取远端MEGID”的状态，则从FPGA的锁存寄存器读取远端MEGID信息，将MMG告警和远端MEGID信息上报，同时将上报状态修改为“上报过告警”的状态。
另外，还需要将上报序列号加1、告警每变化一次，序列号发生一次变化，其中奇数表示告警产生，偶数表示告警消失。
另外，还需要将上报结构体标识位置为1，上报序列号表示上报次数，上报结构体标识位置为1表示告警已经上报过，置为0表示告警没有上报。
另外，还需要将第一变量标识位置为是，第一变量标识用来表示是否允许读远端MEGID信息，如果是才会去写FPGA，否则不会写FPGA的配置寄存器。
3、如果上报状态为“上报过告警”的状态，在此不需要再次上报，但是需要将上报结构体标识位置为1。
其中，由于已经上报过告警，为避免中央处理器(CPU)冲高，此步骤不再上报，而主要是为了把相关的标识字段置为正确的值。
步骤504，告警消失，则根据不同的上报状态进行不同的处理。
1、如果上报状态为“产生告警，未申请读取远端MEGID”的状态， 则表明还没有写入成功，将第一变量标识位置为“是”；
2、如果上报状态为“产生告警，已申请读取远端MEGID”的状态，则表明已经写入成功，将第一变量标识位置为“是”；
上述1、2还需要将上报状态修改为“上报过告警消失”的状态。
如果上报状态为“上报过告警”的状态，则表明已经写入成功，且已经上报告警，此时需要将告警消失上报，同时将上报状态修改为“上报过告警消失”的状态；另外，还需要将上报结构体的标识位置为1，同时把序列号加1。
上述步骤503和步骤504并不存在固定的顺序。
上述实施例提供的告警方法及装置，为OAM信息设置对应的OAMID，通过上报MMG告警时携带远端的MEGID，方便网管快速排查出是哪条残损隧道导致正常隧道的OAM产生了MMG告警，快速恢复正常隧道的业务。另外，目前，PTN设备中可以运用FPGA实现OAM功能，但是，例如MEGID为128比特(bit)，最大可配置8KOAM的话，共需要FPGA逻辑资源8k*128bit，目前的FPGA资源有限，尚不能提供足够的资源来同时存储所有的OAMID，并方便读取每条OAM的MEGID信息。为了满足这么多的FPGA逻辑资源需求，如果换个资源更多的FPGA，需要的资金也比较多；如果加外设，硬件设计风险大，稳定性差不可取。为此，本申请提供的告警方法，通过把产生MMG告警的OAMID写到FPGA，而不是把所有的OAMID全写入FPGA，节省了大量的FPGA逻辑资源。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些组件或所有 组件可以被实施为由处理器，如数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
虽然本申请所揭露的实施方式如上，但所述的内容仅为便于理解本申请而采用的实施方式，并非用以限定本申请。任何本申请所属领域内的技术人员，在不脱离本申请所揭露的精神和范围的前提下，可以在实施的形式及细节上进行任何的修改与变化，但本申请的专利保护范围，仍须以所附的权利要求书所界定的范围为准。

Claims (10)

  1. 一种告警方法，包括：
    轮询读取保存的操作管理和维护标识OAMID，在读取到的OAMID产生错误合并告警MMG告警的情况下，将读取到的OAMID写入指定的寄存器，每个OAMID唯一标识一条OAM信息；
    根据所述寄存器中保存的OAMID从锁存寄存器地址读取远端维护联合端点标识MEGID信息；
    上报所述MMG告警和所述远端MEGID信息。
  2. 根据权利要求1所述的告警方法，其中，在轮询读取保存的OAMID之前，该方法还包括：
    接收OAM信息，根据所述OAM信息生成对应的OAMID，并保存所述OAM信息及其对应的OAM ID。
  3. 根据权利要求1所述的告警方法，其中，该方法还包括：
    在首次产生所述MMG告警的情况下，将所述MMG告警的上报状态置为第一状态；
    所述将读取到的OAMID写入指定的寄存器，包括：在读取到的所述OAMID对应的所述MMG告警的上报状态为所述第一状态的情况下，将读取到的OAMID写入指定的寄存器；在写入成功的情况下，则将所述上报状态修改为第二状态；
    所述上报所述MMG告警和所述远端MEGID信息，包括：
    在继续产生MMG告警且所述上报状态为所述第一状态的情况下，将读取到的OAMID写入指定的寄存器，在写入成功的情况下，将所述上报状态修改为所述第二状态；
    在继续产生MMG告警且所述上报状态为所述第二状态的情况下，从锁存寄存器地址读取远端MEGID信息，上报所述MMG告警和远端MEGID 信息，并将所述上报状态修改为第三状态。
  4. 根据权利要求3所述的告警方法，其中，该方法还包括：
    在继续产生告警且所述上报状态为所述第三状态的情况下，不再上报所述MMG告警和所述远端MEGID信息；
    在告警消失且所述上报状态为所述第一状态或所述第二状态的情况下，则将所述上报状态修改为第四状态；
    在告警消失且所述上报状态为所述第三状态的情况下，将所述MMG告警消失上报给网管，并将所述上报状态修改为所述第四状态。
  5. 一种告警装置，包括：
    读取单元，配置为轮询读取保存的OAMID，在读取到的OAMID产生MMG告警的情况下，将读取到的OAMID写入指定的寄存器，每个OAMID唯一标识一条OAM信息；
    所述读取单元，还配置为根据所述寄存器中保存的OAMID从锁存寄存器地址读取远端MEGID信息；
    上报单元，配置为上报所述MMG告警和所述远端MEGID信息。
  6. 根据权利要求5所述的告警装置，其中，所述装置还包括：
    配置单元，配置为接收OAM信息，根据所述OAM信息生成对应的OAMID，并保存所述OAM信息及其对应的OAM ID。
  7. 根据权利要求5所述的告警装置，其中，
    所述读取单元，配置为在首次产生所述MMG告警的情况下，将所述MMG告警的上报状态置为第一状态；在读取到的所述OAMID对应的所述MMG告警的上报状态为所述第一状态的情况下，将读取到的OAMID写入指定的寄存器；在写入成功的情况下，则将所述上报状态修改为第二状态；
    在继续产生MMG告警且所述上报状态为所述第一状态的情况下，将读取到的OAMID写入指定的寄存器，在写入成功的情况下，将所述上报状 态修改为所述第二状态；
    在继续产生MMG告警且所述上报状态为所述第二状态的情况下，从锁存寄存器地址读取远端MEGID信息，通知所述上报单元上报所述MMG告警和远端MEGID信息，并将所述上报状态修改为第三状态。
  8. 根据权利要求7所述的告警装置，其中，
    所述读取单元，还配置为在继续产生MMG告警且所述上报状态为所述第三状态的情况下，不再通知所述上报单元上报所述MMG告警和所述远端MEGID信息；
    在告警消失且所述上报状态为所述第一状态或所述第二状态的情况下，则将所述上报状态修改为第四状态；
    在告警消失且所述上报状态为所述第三状态的情况下，则通知所述上报单元将所述MMG告警消失上报给网管，并将所述上报状态修改为所述第四状态。
  9. 一种告警装置，包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求1至4中任一项所述的告警方法。
  10. 一种计算机可读存储介质，所述计算机可读存储介质上存储有信息处理程序，所述信息处理程序被处理器执行时实现如权利要求1至4中任一项所述告警方法的步骤。
PCT/CN2019/091603 2018-07-05 2019-06-17 一种告警方法及装置 WO2020007188A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810732500.2A CN110690983B (zh) 2018-07-05 2018-07-05 一种告警方法、装置及计算机可读存储介质
CN201810732500.2 2018-07-05

Publications (1)

Publication Number Publication Date
WO2020007188A1 true WO2020007188A1 (zh) 2020-01-09

Family

ID=69060573

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/091603 WO2020007188A1 (zh) 2018-07-05 2019-06-17 一种告警方法及装置

Country Status (2)

Country Link
CN (1) CN110690983B (zh)
WO (1) WO2020007188A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113965452A (zh) * 2021-11-02 2022-01-21 烽火通信科技股份有限公司 一种设备倒换状态获取方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110173492A1 (en) * 2008-09-16 2011-07-14 France Telecom Technique for protecting leaf nodes of a point-to-multipoint tree in a communications network in connected mode
WO2012167667A1 (zh) * 2011-06-08 2012-12-13 中兴通讯股份有限公司 一种信号劣化处理方法、装置及节点设备
CN103368849A (zh) * 2013-07-05 2013-10-23 盛科网络（苏州）有限公司 Oam报文的处理方法和装置
CN103580886A (zh) * 2012-07-25 2014-02-12 中兴通讯股份有限公司 分组传送网络保护倒换装置和方法
CN105471599A (zh) * 2014-08-15 2016-04-06 中兴通讯股份有限公司 一种保护倒换方法及网络设备

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090168663A1 (en) * 2007-12-26 2009-07-02 Nortel Netowrks Limited Reducing Configuration of OAM Signalling Data
CN102143005B (zh) * 2011-04-14 2015-01-28 中兴通讯股份有限公司 一种基于oam协议确定故障消除的方法及装置
CN104660431B (zh) * 2013-11-21 2019-01-15 中兴通讯股份有限公司 一种网络告警方法、设备及终端
CN107800559A (zh) * 2016-09-07 2018-03-13 中兴通讯股份有限公司 一种软件定义网络sdn的告警处理方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110173492A1 (en) * 2008-09-16 2011-07-14 France Telecom Technique for protecting leaf nodes of a point-to-multipoint tree in a communications network in connected mode
WO2012167667A1 (zh) * 2011-06-08 2012-12-13 中兴通讯股份有限公司 一种信号劣化处理方法、装置及节点设备
CN103580886A (zh) * 2012-07-25 2014-02-12 中兴通讯股份有限公司 分组传送网络保护倒换装置和方法
CN103368849A (zh) * 2013-07-05 2013-10-23 盛科网络（苏州）有限公司 Oam报文的处理方法和装置
CN105471599A (zh) * 2014-08-15 2016-04-06 中兴通讯股份有限公司 一种保护倒换方法及网络设备

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113965452A (zh) * 2021-11-02 2022-01-21 烽火通信科技股份有限公司 一种设备倒换状态获取方法及装置
CN113965452B (zh) * 2021-11-02 2023-11-03 烽火通信科技股份有限公司 一种设备倒换状态获取方法及装置

Also Published As

Publication number Publication date
CN110690983B (zh) 2022-04-08
CN110690983A (zh) 2020-01-14

Similar Documents

Publication Publication Date Title
US10904137B2 (en) Loop avoidance for event-driven virtual link aggregation
US20200267069A1 (en) Link switching method, link switching device, network communication system, and computer-readable storage medium
US10313380B2 (en) System and method for centralized virtual interface card driver logging in a network environment
US11907561B2 (en) Data backup method and apparatus
ES2854286T3 (es) Método, dispositivo y sistema de gestión de la estrategia
CN110825698B (zh) 元数据管理方法及相关装置
US20160098327A1 (en) Bypassing failed hub devices in hub-and-spoke telecommunication networks
US9729389B2 (en) Methods and systems for switching network traffic in a communications network
US10909009B2 (en) System and method to create a highly available quorum for clustered solutions
WO2020030000A1 (zh) 容灾切换方法、相关设备及计算机存储介质
US20210326211A1 (en) Data backup method, apparatus, and system
WO2020007188A1 (zh) 一种告警方法及装置
WO2021114774A1 (zh) 聚合链路的处理方法及装置
CN113590049A (zh) 一种存储卷跨节点克隆的方法、装置、设备及可读介质
WO2024113894A1 (zh) 一种远程复制关系的建立方法及相关装置
WO2017092539A1 (zh) 虚拟机修复方法、虚拟机装置、系统及业务功能网元
CN103414591A (zh) 一种端口故障恢复时的快速收敛方法和系统
CN106776107B (zh) 一种奇偶校验纠错方法及网络设备
US20140223123A1 (en) Storage system based host computer monitoring
US8775609B2 (en) Serial attached SCSI expander management and alarm reporting using SNMP
US9104562B2 (en) Enabling communication over cross-coupled links between independently managed compute and storage networks
US10972343B2 (en) System and method for device configuration update
WO2017101016A1 (zh) 用于存储节点同步业务请求的方法和装置
US11949597B2 (en) Platform independent on demand network management and monitoring
US20240214315A1 (en) Platform independent on demand network management and monitoring

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

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

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 22/06/2021)

122 Ep: pct application non-entry in european phase

Ref document number: 19831349

Country of ref document: EP

Kind code of ref document: A1