WO2021244390A1 - 一种告警处理方法及装置 - Google Patents

一种告警处理方法及装置 Download PDF

Info

Publication number
WO2021244390A1
WO2021244390A1 PCT/CN2021/096367 CN2021096367W WO2021244390A1 WO 2021244390 A1 WO2021244390 A1 WO 2021244390A1 CN 2021096367 W CN2021096367 W CN 2021096367W WO 2021244390 A1 WO2021244390 A1 WO 2021244390A1
Authority
WO
WIPO (PCT)
Prior art keywords
network device
node
alarm
lof
maintenance signal
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2021/096367
Other languages
English (en)
French (fr)
Inventor
孙亮
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to KR1020227045362A priority Critical patent/KR102728462B1/ko
Priority to BR112022024367A priority patent/BR112022024367A2/pt
Priority to EP21818908.2A priority patent/EP4152694B1/en
Priority to CA3185692A priority patent/CA3185692A1/en
Publication of WO2021244390A1 publication Critical patent/WO2021244390A1/zh
Priority to US18/060,913 priority patent/US12375173B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • 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/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0823—Errors, e.g. transmission errors
    • H04L43/0829—Packet loss
    • H04L43/0835—One way packet loss
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B10/00—Transmission systems employing electromagnetic waves other than radio-waves, e.g. infrared, visible or ultraviolet light, or employing corpuscular radiation, e.g. quantum communication
    • H04B10/03—Arrangements for fault recovery
    • H04B10/032—Arrangements for fault recovery using working and protection systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B10/00—Transmission systems employing electromagnetic waves other than radio-waves, e.g. infrared, visible or ultraviolet light, or employing corpuscular radiation, e.g. quantum communication
    • H04B10/07—Arrangements for monitoring or testing transmission systems; Arrangements for fault measurement of transmission systems
    • H04B10/075—Arrangements for monitoring or testing transmission systems; Arrangements for fault measurement of transmission systems using an in-service signal
    • H04B10/079—Arrangements for monitoring or testing transmission systems; Arrangements for fault measurement of transmission systems using an in-service signal using measurements of the data signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B10/00—Transmission systems employing electromagnetic waves other than radio-waves, e.g. infrared, visible or ultraviolet light, or employing corpuscular radiation, e.g. quantum communication
    • H04B10/07—Arrangements for monitoring or testing transmission systems; Arrangements for fault measurement of transmission systems
    • H04B10/075—Arrangements for monitoring or testing transmission systems; Arrangements for fault measurement of transmission systems using an in-service signal
    • H04B10/079—Arrangements for monitoring or testing transmission systems; Arrangements for fault measurement of transmission systems using an in-service signal using measurements of the data signal
    • H04B10/0795—Performance monitoring; Measurement of transmission parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/02—Details
    • H04J3/06—Synchronising arrangements
    • H04J3/0602—Systems characterised by the synchronising information used
    • H04J3/0605—Special codes used as synchronising signal
    • H04J3/0608—Detectors therefor, e.g. correlators, state machines
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/02—Details
    • H04J3/14—Monitoring arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/16—Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
    • H04J3/1605—Fixed allocated frame structures
    • H04J3/1652—Optical Transport Network [OTN]
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0604—Management of faults, events, alarms or notifications using filtering, e.g. reduction of information by using priority, element types, position or time
    • H04L41/0618—Management of faults, events, alarms or notifications using filtering, e.g. reduction of information by using priority, element types, position or time based on the physical or logical position
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J2203/00—Aspects of optical multiplex systems other than those covered by H04J14/05 and H04J14/07
    • H04J2203/0001—Provisions for broadband connections in integrated services digital network using frames of the Optical Transport Network [OTN] or using synchronous transfer mode [STM], e.g. SONET, SDH
    • H04J2203/0051—Network Node Interface, e.g. tandem connections, transit switching
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J2203/00—Aspects of optical multiplex systems other than those covered by H04J14/05 and H04J14/07
    • H04J2203/0001—Provisions for broadband connections in integrated services digital network using frames of the Optical Transport Network [OTN] or using synchronous transfer mode [STM], e.g. SONET, SDH
    • H04J2203/0057—Operations, administration and maintenance [OAM]
    • H04J2203/006—Fault tolerance and recovery

Definitions

  • the embodiments of the present application relate to the field of communication technologies, and in particular, to an alarm processing method and device.
  • the loss of frame (LOF) alarm refers to the loss of frame on the receiving side of the line.
  • OTN optical transport network
  • the first network device will detect the LOF alarm.
  • the next hop network device may also detect the frame loss and generate and report the LOF alarm, so the next hop network device.
  • the embodiment of the present application provides an alarm processing method to solve the problem of resource waste caused by false detection of LOF alarms.
  • an embodiment of the present application provides an alarm processing method.
  • the method includes: a second network device detects that a LOF pre-alarm occurs on a first working channel; the first working channel is used to connect the second network device and the first network device; wherein the detection condition of the LOF pre-alarm In order to perform framing failure of the data frame from the first network device for a first duration, the first duration is less than a second duration, and the second duration is the duration of the framing failure in the LOF alarm detection condition;
  • the second network device inserts a first maintenance signal frame at the entrance end, the entrance end is used to receive a data frame from the first network device through a first working channel, and the first maintenance signal frame is used for framing.
  • the framing duration in the LOF pre-alarm detection condition is less than the framing failure duration in the LOF alarm detection condition. Therefore, the second network device detects the LOF pre-alarm on the first working channel before detecting the LOF alarm on the first working channel.
  • the second network device detects the LOF pre-alarm, it inserts the first maintenance signal frame into the next hop network device (that is, the third network device), so that the third network device can correctly frame the frame. Therefore, the third network device will not falsely report the LOF alarm due to the failure of the working channel between the first network device and the second network device. Since reporting the LOF alarm needs to occupy the transmission resources of the third network device, and the management device needs to perform subsequent processing on the LOF alarm reported by the third network device, which in turn occupies the processing resources of the management device, therefore, the third network device reports the alarm by mistake Produce a waste of resources.
  • the above method may further include: when the second network device detects that a LOF alarm occurs on the first working channel, terminating the insertion of the first maintenance signal frame at the ingress end, and The alarm indication signal AIS frame is inserted at the entry end.
  • the first maintenance signal frame is replaced with an AIS frame, so that the AIS frame is sent to the next hop, so that the next hop reports the AIS alarm in time.
  • the first network device and the second network device are both configured with a subnet connection protection group
  • the method may further include: the second network device detects the first job A LOF alarm occurs on the channel, triggering the switching of the subnet connection protection group of the second network device, and continuously inserting the first maintenance signal frame at the ingress end for a third period of time.
  • the third duration is the duration of delay in inserting the AIS frame after the LOF alarm is detected.
  • the third time duration is greater than or equal to the time duration for the second network device to complete the switching of the subnet connection protection group.
  • the duration of inserting the first maintenance signal frame at the ingress end reaches the third duration without receiving it.
  • the insertion of the first maintenance signal frame at the ingress end is terminated, and the AIS frame is inserted at the ingress end.
  • the first network device when the first network device detects the LOF alarm, it does not immediately insert the AIS. In order to prevent the network device on the subsequent path from accidentally switching, the next hop network is delayed The device sends an AIS frame, and during the period when the second network device completes the switch, it sends the first maintenance signal frame to the next hop, so that the network device on the subsequent path can perform normal framing without detecting frame loss. A LOF alarm is generated, and the first network device delays sending the AIS frame for this period of time. After the first network device completes the switch, it can normally receive the data frame of the previous hop, so that the network device on the subsequent path can also receive the data frame normally. , No LOF alarm or AIS alarm will be generated, and no false switching will occur.
  • the overhead of the first maintenance signal frame includes a first value; the first value is used to indicate that the first maintenance signal frame is a NULL type maintenance signal.
  • the overhead is the channel monitoring PM section overhead or the serial connection monitoring TCM section overhead.
  • the indication field included in the overhead of the first maintenance signal frame is the first value.
  • the indication field may be the state identifier field in the PM section overhead or the state identifier field in the TCM section overhead.
  • an embodiment of the present application provides an alarm processing method.
  • the method includes: a third network device detects that a LOF pre-alarm occurs on a second working channel; the second working channel is used to connect the third network device and The second network device; wherein the detection condition of the LOF pre-alarm is that the framing of the data frame from the second network device fails for the first time period; the third network device detects that the LOF occurs on the second working channel Before the alarm, the first maintenance signal frame from the second network device is received through the second working channel; wherein, the first maintenance signal frame is used for framing; the detection condition of the LOF alarm is The framing failure of the data frame of the second network device continues for a second period of time, and the second period of time is greater than the first period of time.
  • the third network device performs framing processing on the first maintenance signal frame.
  • the third network device sends the first maintenance signal frame to the next hop network device.
  • the third network device receives the first maintenance signal frame that supports normal framing after detecting the occurrence of the LOF pre-alarm and before generating the LOF alarm. If there is no failure with the previous hop network device, It can perform normal framing processing, so as not to misdetect and report LOF alarms to cause waste of resources.
  • the above method may further include: after the third network device receives the first maintenance signal frame from the second network device through the second working channel, passing the second working channel The channel receives the alarm indication signal AIS frame from the second network device; the third network device reports an AIS alarm.
  • the third network device After receiving the AIS frame, the third network device reports the AIS alarm in time.
  • the second network device and the third network device are both configured with a subnet connection protection group, and the method further includes: the third network device receives from the third network device through the second working channel After the first maintenance signal frame of the second network device, the AIS frame from the second network device is received through the second working channel; the third network device triggers the switching of the subnet connection protection group and reports it AIS alarm.
  • the third network device immediately triggers the SNCP switch after receiving the AIS frame, without waiting for a certain delay before triggering.
  • the overhead of the first maintenance signal frame includes a first value; the first value is used to indicate that the first maintenance signal frame is a NULL type maintenance signal.
  • the overhead is the channel monitoring PM section overhead or the serial connection monitoring TCM section overhead.
  • the indication field included in the overhead of the first maintenance signal frame is the first value.
  • the indication field may be the state identifier field in the PM section overhead or the state identifier field in the TCM section overhead.
  • an embodiment of the present application provides an alarm processing device.
  • the alarm processing apparatus is applied to a network device, such as a second network device or a third network device.
  • the device includes a processor and a memory.
  • the memory is used to store program code; the processor is used to read and execute the program code stored in the memory to implement the method as described in the first aspect or any one of the first aspects, or to implement the method as described in the second aspect
  • the method described in any one of the aspect or the second aspect is designed.
  • an embodiment of the present application provides a computer-readable storage medium in which a software program is stored, and the software program can implement the first or second aspect when read and executed by one or more processors Any of the methods provided by the design.
  • the embodiments of the present application provide a computer program product containing instructions. When it runs on a computer, it makes the computer execute the method provided by any design of the first aspect or the second aspect described above.
  • an embodiment of the present application provides a chip.
  • the chip is connected to the memory, and is used to read and execute the software program stored in the memory to implement the method provided by any one of the designs of the first aspect or the second aspect.
  • Figure 1 is a schematic diagram of an OTN network architecture in an embodiment of the application
  • FIG. 2 is a schematic diagram of the structure of an OTN device in an embodiment of the application
  • FIG. 3 is a schematic diagram of a possible end-to-end networking in an embodiment of this application.
  • FIG. 5 is a schematic diagram of a possible alarm processing flow provided in scenario 1 of an embodiment of the application.
  • FIG. 6 is a schematic diagram of another possible alarm processing flow provided in scenario 1 of an embodiment of the application.
  • FIG. 7 is a schematic flowchart of another possible alarm processing method provided by an embodiment of the application.
  • Figure 8 is a schematic diagram of an alarm processing flow in an SNCP/S TCM cascaded networking provided by an embodiment of the application;
  • Fig. 9 is a schematic diagram of an alarm processing flow in an SNCP/N TCM cascade network provided by an embodiment of the application.
  • FIG. 10 is a schematic structural diagram of a possible alarm processing device in an embodiment of this application.
  • FIG. 11 is a schematic structural diagram of another possible alarm processing apparatus according to an embodiment of the application.
  • OTN optical networks
  • An OTN is usually formed by connecting multiple OTN devices through optical fibers, and can be composed of different topological types such as linear, ring, and mesh according to specific needs.
  • the OTN shown in Figure 1 is composed of two OTN networks.
  • Each OTN network consists of a certain number of OTN devices (N1 to N7).
  • OTN device may have different functions.
  • OTN equipment is divided into optical layer equipment, electrical layer equipment, and photoelectric hybrid equipment.
  • Optical layer equipment refers to equipment capable of processing optical layer signals, such as optical amplifier (optical amplifier, OA).
  • Electrical layer equipment refers to equipment capable of processing electrical layer signals, for example: equipment capable of processing OTN signals.
  • Optoelectronic hybrid equipment refers to equipment capable of processing optical layer signals and electrical layer signals. It should be noted that, according to specific integration needs, one OTN device can integrate multiple different functions. The technical solution provided in this application is applicable to OTN equipment of different forms and integration levels.
  • the network devices involved in the embodiments of the present application may be OTN devices, and the network devices may also be referred to as network nodes, or simply referred to as nodes.
  • FIG. 2 is a schematic diagram of a possible OTN device structure.
  • the OTN device here can refer to the OTN nodes (N1 to N7) in FIG. 1.
  • an OTN device includes power supplies, fans, auxiliary boards, and may also include tributary boards, circuit boards, crossover boards, optical layer processing boards, and system control and communication boards.
  • the power supply is used to supply power for OTN equipment, and may include main and backup power supplies.
  • the fan is used to dissipate heat for the device.
  • Auxiliary boards are used to provide auxiliary functions such as external alarms or access to external clocks.
  • Tributary boards, crossover boards and circuit boards are mainly used to process the electrical layer signals of the OTN.
  • the tributary board is used to realize the reception and transmission of various customer services, such as SDH services, packet services, Ethernet services, and fronthaul services. Furthermore, the tributary board can be divided into a client-side optical module and a signal processor. Among them, the client-side optical module may be an optical transceiver for receiving and/or sending service data.
  • the signal processor is used to implement the mapping and de-mapping processing of the service data to the data frame.
  • the cross-connect board is used to implement the exchange of data frames and complete the exchange of one or more types of data frames.
  • the circuit board mainly realizes the processing of the data frame on the line side. Specifically, the circuit board can be divided into a line-side optical module and a signal processor.
  • the line-side optical module may be a line-side optical transceiver for receiving and/or sending data frames.
  • the signal processor is used to implement multiplexing and demultiplexing, or mapping and demapping processing of data frames on the line side.
  • System control and communication boards are used to implement system control and communication. Specifically, information can be collected from different boards through the backplane, or control instructions can be sent to the corresponding boards. It should be noted that, unless otherwise specified, there may be one or more specific components (for example: signal processor), and this application does not make any restrictions. It should also be noted that the embodiments of the present application do not impose any restrictions on the types of boards included in the device, and the specific functional design and number of boards.
  • each device may be different.
  • the network equipment as the core node may not have tributary boards.
  • a network device as an edge node may have multiple tributary boards.
  • LOF alarm refers to the loss of frames on the receiving side of the line. Generally, when errors in the reception of the A1 and A2 bytes are detected, the LOF alarm is detected.
  • the A1 and A2 bytes are frame synchronization bytes.
  • the alarm indication signal (alarm indication signal, AIS) is a maintenance signal in the OTN network.
  • the role of AIS is to transmit alarm information, that is, to transmit the signal of service failure of the upstream node to the downstream node or transmit the information of the service layer signal failure to the client layer.
  • Data frame It can be an OTN frame or a flexible Ethernet (Flex Ethernet, FlexE) frame, which is used to carry various business data, and can realize the management and monitoring of the business data.
  • the OTN frame can be an optical data unit (ODU)k, ODUCn, ODUflex, or an optical transport unit (OTU)k, OTUCn, or an optical payload unit (optical payload unit, OPU), or flexible OTN (flexible OTN, FlexO) frame, or flexible optical service unit (flexible optical service unit, OSUflex), etc.
  • the data frame can also be other frame structures suitable for optical networks.
  • PM Path monitoring
  • TCM tandem connection monitoring
  • the OTN includes the overhead of the 6-level TCM (overhead, OH).
  • TCM includes trail trace identifier (TTI), bit interleaved parity 8, BIP8, backward defect indication (BDI), backward error indication (backward error indication) , BEI), status indicator (states, STAT), backward incoming alignment error (BIAE).
  • TCM function configuration can be performed for nodes that require TCM functions. For each node, the TCM in the source direction (or called the sending direction) and the TCM in the sink direction (or called the receiving direction) can be configured in different modes or the same mode.
  • the sending direction has an operational mode and a transparent mode.
  • the TCM mode of a certain level adopted by the network equipment is the operational mode, and the network equipment regenerates the TCM of this level, such as inserting BIP-8, BEI, BIAE, BDI, TTI, etc.
  • the TCM mode of a certain level adopted by the network device is the transparent mode, and the network device does not process the TCM of this level.
  • the receiving direction has operational mode, transparent mode or monitoring mode.
  • the TCM mode of a certain level adopted by the network device is the operational mode, and the network device monitors the TCM of this level. For example, it includes monitoring the overheads of BIP-8, BEI, BIAE, BDI, TTI, etc., generating corresponding defects, and performing subsequent processing, such as inserting AIS or generating trail signal failure (TSF) as follows.
  • the TCM mode of a certain level adopted by the network equipment is the monitoring mode, and the network equipment monitors the TCM of this level. For example, it includes monitoring the overhead of BIP8, BEI, BIAE, BDI, TTI, etc., and corresponding defects are generated, but the follow-up actions of AIS and TSF are not processed.
  • the TCM mode of a certain level adopted by the network device is the transparent mode, and the network device does not process the TCM of this level.
  • Sub-network connection protection refers to the pre-arrangement of a dedicated protection route for a certain subnet connection. Once the subnet fails, the dedicated protection route will replace the subnet to assume the transmission task in the entire network .
  • the protection channel in each transmission direction of SNCP takes a different route from the working channel. For example, nodes A and B transfer services through SNCP, that is, node A transfers services to node B through subnet 1 (working SNC, that is, working channel) and subnet 2 (protection SNC, that is, protection channel) through bridging. , And Node B uses a switching switch to select a channel of business information from two directions according to the switching criterion. Node B performs subnet connection protection group switching, that is, switching from receiving services from node A from subnet 1 to receiving services from node A from subnet 2.
  • SNCP adopts the working mode of dual sending and selective receiving. Under normal circumstances, it chooses to receive services through the working SNC. When the working SNC fails, it chooses to receive services through the protected SNC.
  • SNCP includes non-intrusively monitored sub-network connection protection (SNCP/N) and sub-network connection protection (SNCP with sublayer monitoring, SNCP/S).
  • the monitoring method adopted by SNCP/N is to detect end-to-end or sub-layer overhead or operation management and maintenance (OAM) information in the signal.
  • SNCP/S detects service layer defects, continuity/connectivity defects in the layer network, and error degradation conditions in the layer network, and realizes monitoring by using sub-layer overhead/OAM.
  • SNCP/S regards the SF alarm of the PM section of the service layer and the SF alarm of the TCM section of this layer as the switching conditions.
  • the overhead can be PM or TCM, for example.
  • the first maintenance signal frame provided by the embodiment of the present application is different from the above three maintenance signal frames. AIS, LCK and OCI do not support normal framing.
  • the first maintenance signal frame provided in the embodiment of the present application is used for normal framing.
  • the first maintenance signal frame may be a NULL type maintenance signal.
  • the frame format adopted by the first maintenance signal frame is the same as the frame format of the data frame.
  • the data frame is ODUk
  • the format of the first maintenance signal frame is the same as that of ODUk.
  • the overhead of the first maintenance signal frame includes an indication field.
  • the value of the indication field is used to indicate whether the first maintenance signal frame belongs to the NULL type maintenance signal.
  • the value of the indication field is a first value
  • the first value indicates that the first maintenance signal frame is a NULL type maintenance signal.
  • the indication field may be a newly defined field in the overhead.
  • the indication field included in the overhead of the first maintenance signal frame may be the STAT field in the PM section overhead or the STAT field in the TCM section overhead. Table 1 shows the meaning of different values of STAT in the PM segment overhead.
  • the indication field included in the overhead of the first maintenance signal frame may be the STAT field in the PM section overhead
  • the first value may be one of "000", "010", "011", or "100".
  • One is a value, and the first value indicates that the first maintenance signal frame belongs to the NULL type maintenance signal.
  • the value of the indication field is a first value
  • the first value indicates that the first maintenance signal frame is a NULL type
  • PM STAT value meaning 000 Reserved for future international standards 001 Normal channel signal 010 Reserved for future international standards 011 Reserved for future international standards 100 Reserved for future international standards 101 Maintenance signal: LCK 110 Maintenance signal: OCI 111 Maintenance signal: AIS
  • Table 2 shows the meaning of different values of STAT in the overhead of the TCM section.
  • the indication field included in the overhead of the first maintenance signal frame may be the STAT field of the TCM section overhead
  • the first value may be "011" or "100”.
  • TCM STAT value meaning 000 No serial connection monitoring at the source 001 There is serial connection monitoring at the source, no IAE (normal signal) 010 There is serial connection monitoring at the source, with IAE 011 Reserved for future international standards 100 Reserved for future international standards 101 Maintenance signal: LCK 110 Maintenance signal: OCI 111 Maintenance signal: AIS
  • the SNCP group can be configured in the end-to-end networking, or it is not necessary to configure the SNCP group.
  • FIG. 3 is a schematic diagram of a possible end-to-end networking provided by an embodiment of this application.
  • the end-to-end path is node A-B-C-D.
  • Node A sends data frames to node D through node B and node C.
  • the nodes A and B are connected through channel 1
  • the nodes B and C are connected through channel 2, and the nodes C and D are connected through channel 3.
  • failures such as fiber breakage occur on channel 1
  • Node B detects frame loss (or framing failure) for X ms (milliseconds), and then determines that a LOF alarm is generated, and AIS is inserted in the receiving direction.
  • the channels involved in the embodiments of the present application may also be referred to as links.
  • node B When node B detects the LOF alarm, the data frame has already been lost, causing node C and node D to not receive the data frame. Therefore, node C and node D will continue to detect frame loss for X ms and generate and report the LOF alarm. That is, node C mistakenly detects that channel 2 is faulty, node D mistakenly detects that channel 3 is faulty, and further causes node C and node D to report LOF alarms to the management device due to misdetection, and the management device is required to perform channel 2 and channel 3 Fault detection generates waste of resources.
  • nodes A-D are configured with SNCP protection groups, when node B detects a LOF alarm, it will perform SNCP group switching. Similarly, when nodes C and D detect LOF alarms, they will also perform SNCP group switching. When only channel 1 fails, nodes C and D will perform false switching and waste resources.
  • embodiments of the present application provide an alarm processing method and device, and specifically provide a mechanism for configuring and detecting LOF pre-alarms.
  • the detection condition of the LOF pre-warning is to detect the failure of framing for the first period of time.
  • the detection condition of the LOF alarm is to detect the failure of framing for the second period of time.
  • the second duration is less than the first duration.
  • the network device that receives the first maintenance signal frame can perform normal framing, so that it will not report an alarm, for example, it will not trigger a LOF alarm. Therefore, the network device that receives the first maintenance signal frame will not erroneously generate a LOF alarm because the framing failure lasts for the second period of time, and will not perform false reporting of the LOF alarm or false switching, thereby avoiding resource waste.
  • the embodiments of the present application are applicable to a scenario where an SNCP group is configured or a scenario where an SNCP group is not configured. In the following, in combination with these two scenarios, the solutions provided in the embodiments of the present application will be described in detail.
  • the first network device, the second network device, and the third network device are not configured with an SNCP group.
  • the first network device, the second network device, and the third network device all include an ingress port and an egress port.
  • the ingress port can also be called a receiving port, which is used to receive a signal sent by a network device on the previous hop, and the egress port can also be referred to as a sending port, which is used to send a signal to a next hop network device.
  • Fig. 4 is a schematic flowchart of a possible alarm processing method provided by an embodiment of the application.
  • the alarm processing method includes S401-S405.
  • the second network device detects that a LOF pre-alarm occurs on the first working channel; the first working channel is used to connect the second network device and the first network device.
  • the detection condition of the LOF pre-alarm is that the framing failure of the data frame from the first network device lasts for the first duration, the first duration is less than the second duration, and the second duration is the duration of the framing failure in the detection condition of the LOF alarm duration.
  • the second network device detects the LOF pre-alarm on the first working channel before detecting the LOF alarm on the first working channel.
  • the second network device fails to frame the data frame received through the first working channel for the first period of time, it detects that the LOF pre-alarm occurs on the first working channel. If the framing failure continues for the second time period, it is detected that the LOF alarm occurs on the first working channel. Of course, if the LOF pre-alarm is detected on the first working channel, and before the LOF alarm is detected, if a data frame is detected, it can be determined that the first working channel is a normal channel. Further, the second network device terminates the insertion of the first maintenance signal frame.
  • the second network device determines that the data frame is detected, which can be determined by the following method 1 or 2.
  • Manner 2 After detecting the LOF pre-alarm on the first working channel and before detecting the LOF alarm, if the number of data frames received from the first network device reaches the threshold 1, it is determined that the data frame is detected.
  • a data frame is sent out instantaneously on the channel due to jitter, and the second network device detects the data frame. This may cause the second network device to misjudge that the channel is not faulty, thereby failing to start the fault recovery process in time, resulting in prolonged service interruption.
  • the second network device will not continuously detect the data frame or the number of detected data frames will not reach the threshold for the duration 1, so that it will not be misjudged that the channel is not faulty .
  • the second network device inserts the first maintenance signal frame at the ingress end.
  • the entry port is used to receive the data frame from the first network device through the first working channel.
  • the second network device sends the first maintenance signal frame to the third network device through the second working channel.
  • the second working channel is used to connect the second network device and the third network device, and the first maintenance signal frame is used for framing.
  • the egress end of the second network device modifies the TCM segment overhead of the first maintenance signal frame and sends it to the third network device.
  • the modified first maintenance signal frame has the same function as the first maintenance signal frame, and both support normal framing and will not trigger an alarm.
  • the third network device detects that the LOF pre-alarm occurs on the second working channel; the second working channel is used to connect the third network device and the second network device.
  • the second network device sends the first maintenance signal frame to the third network device through the second working channel. If there is no failure in the second working channel, the third network device can normally receive the first maintenance signal frame. If the third network device receives the first maintenance signal frame from the second network device through the second working channel before detecting that the LOF alarm occurs on the second working channel; then the third network device can perform the maintenance signal frame on the first maintenance signal frame. Fixed frame processing. Go to S405.
  • the third network device sends the first maintenance signal frame. Specifically, the third network device sends the first maintenance signal frame to the next hop network device of the third network device.
  • the third network device may perform framing processing on the first maintenance signal frame. Therefore, when the working channel between the first network device and the second network device fails, the framing failure lasting for the second duration will not cause the LOF alarm to be falsely detected, and the LOF alarm is reported to cause a waste of resources.
  • the third network device cancels the LOF pre-alarm if it receives the first maintenance signal frame or the normal signal frame sent from the second network device.
  • the second network device when the second network device detects that the LOF alarm occurs on the first working channel, it terminates the insertion of the first maintenance signal frame at the ingress end, and inserts the alarm indication signal AIS frame at the ingress end . Furthermore, after the second network device continuously receives the first maintenance signal frame and receives the AIS frame from the second network device, the third network device may report an AIS alarm.
  • the end-to-end path includes node A-node D.
  • Node A sends data frames to node D through node B and node C.
  • the exit end of node A and the entrance end of node B are connected through channel 1
  • the exit end of node B and the entrance end of node C are connected through channel 2, and the exit end of node C and the entrance end of node D pass through Channel 3 is connected.
  • No SNCP group is configured for node A-node D.
  • FIG. 5 is a schematic diagram of a possible alarm processing flow provided in scenario 1 of an embodiment of the application.
  • the failure of channel 1 between the exit end of node A and the entry end of node B is taken as an example, and both channels 2 and 3 are normal channels.
  • channel 1 fails, the ingress end of node B cannot receive the data frame from node A, that is, it lasts Y ms from the failure, and the framing failure is detected, and the LOF pre-alarm is detected on channel 1.
  • the entry end of node C also cannot receive the data frame from node B. Therefore, node C will also detect the occurrence of LOF pre-alarm, and node D will also detect the occurrence of LOF pre-alarm.
  • Node B When Node B detects that a LOF pre-alarm occurs on channel 1, it will continue to insert the first maintenance signal frame at its ingress end. The egress end of node B forwards the first maintenance signal frame to node C. After node C receives the first maintenance signal frame, it can perform normal framing on the first maintenance signal frame. If node B detects framing failure for X ms from the beginning of the failure, it detects that a LOF alarm has occurred on channel 1. Node B terminates the insertion of the first maintenance signal at the ingress end, and inserts the AIS frame at the ingress end. Therefore, the node C will continue to receive the first maintenance signal frame before receiving the AIS frame, and will not detect the LOF alarm. In the same way, node D will not detect the LOF alarm before receiving the AIS.
  • FIG. 6 is a schematic diagram of another possible alarm processing flow provided in scenario 1 of an embodiment of the application.
  • the channel 1 between nodes A and B fails as an example.
  • Node B detects LOF pre-alarm on channel 1, and will continue to insert the first maintenance signal frame at the ingress end. However, because the ingress end of node B and the egress end of node B belong to different TCM path segments, the egress end of node B will modify the TCM overhead of the first maintenance signal frame and change the modified first maintenance signal frame Sent to node C.
  • the modified first maintenance signal frame and the first maintenance signal frame play the same role at each node, and both are used for normal framing and are processed according to the normal signal frame. After node C receives the modified first maintenance signal frame, it can perform normal framing on the modified first maintenance signal frame.
  • the first maintenance signal frame modified by node B is referred to as signal frame 1
  • the first maintenance signal frame modified by node C is referred to as signal frame 2.
  • node B detects framing failure for X ms from the beginning of the failure, it detects that a LOF alarm has occurred on channel 1.
  • Node B terminates the insertion of the first maintenance signal frame at the ingress end, and inserts the AIS frame at the ingress end. Therefore, after the node C detects the LOF pre-alarm, it can receive the signal frame 1 that can be framed normally, and will not detect the LOF alarm. In the same way, node D will not detect the LOF alarm.
  • the network devices on the transmission path are configured with SNCP groups. Specifically, a first working channel and a first protection channel are deployed between the first network device and the second network device; a second working channel and a second protection channel are deployed between the second network device and the third network device.
  • the first network device, the second network device, and the third network device all include an ingress port and an egress port.
  • the ingress port is also called the receiving port, which is used to receive the signal sent by the previous hop network device, and the egress port is also called the sending port, which is used to send the signal to the next hop network device.
  • FIG. 7 is a schematic flowchart of another possible alarm processing method provided by an embodiment of the application.
  • Alarm processing methods include S701-S703.
  • the second network device detects that a LOF pre-alarm occurs on the first working channel.
  • S702 The second network device inserts the first maintenance signal frame at the ingress end.
  • S703 When the second network device detects that the LOF alarm occurs on the first working channel, it triggers the switching of the subnet connection protection group of the second network device. Specifically, the second network device switches the receiving channel from the first working channel to the first protection channel.
  • the detection condition of the LOF pre-alarm is that the framing failure of the data frame from the second network device continues for the first time; the detection condition of the LOF alarm is that the framing failure of the data frame from the second network device continues for the first time. Two hours, the second period is greater than the first period.
  • the foregoing method may further include:
  • the second network device continuously inserts the first maintenance signal frame at the ingress end within the third time period.
  • the third duration is the duration of delay in inserting the AIS frame after the LOF alarm is detected.
  • the third time duration is greater than or equal to the time duration for the second network device to complete the switching of the subnet connection protection group.
  • the second network device detects the LOF pre-alarm
  • the first maintenance signal frame is inserted into the next hop network device (that is, the third network device), and the third The network device may perform framing processing on the first maintenance signal frame. Therefore, when the upstream link fails, the duration of the undetected data frame reaches the second duration and the LOF alarm is not detected by mistake, and the LOF alarm is reported to cause waste of resources.
  • the receiving channel of the second network device is switched from the first working channel to the first protection channel.
  • the first protection channel has also failed.
  • the second network device cannot receive the data frame from the first network device through the first protection channel.
  • the second network device terminates the insertion of the first network device at the entrance corresponding to the first working channel Maintain the signal frame, and insert the AIS frame at the entry end corresponding to the first working channel.
  • the SNCP/S TCM cascade mode, the SNCP/N TCM cascade mode, or the SNCP/N PM cascade mode can be used for networking.
  • Fig. 8 is a schematic diagram of an alarm processing flow in an SNCP/S TCM cascaded networking provided by an embodiment of the application. Taking the first duration as Y ms and the second duration as X ms as an example, the above solution will be described in detail.
  • the end-to-end path includes node A-node D configured with an SNCP group, and node A sends data frames to node D through node B and node C.
  • Both the node A and the node D are configured with the PM function and the TCM function, and the node B and the node C are configured with the TCM function.
  • TCM mode Take the TCM mode as the operation mode as an example.
  • node A and node B, node B and node C, and node C and node D belong to the same PM segment, but belong to different TCM path segments.
  • the path between node A and node B is TCM path segment 1
  • the path between node B and node C is TCM path segment 2
  • the path between node C and node D is TCM path segment 3.
  • Two channels are configured between node A and node B, namely working channel 1 and protection channel 1.
  • Node A sends data frames to node B through working channel 1 and protection channel 1
  • node B chooses to receive data frames through working channel 1 or protection channel 1.
  • Two channels are configured between node B and node C, namely working channel 2 and protection channel 2.
  • Node B sends data frames to node C through working channel 2 and protection channel 2
  • node C chooses to use working channel 2 or protection Channel 2 receives the data frame.
  • Two channels are configured between node C and node D, working channel 3 and protection channel 3 respectively.
  • Node C sends data frames to node D through working channel 3 and protection channel 3, and node D chooses to receive data frames through working channel 3 or protection channel 3.
  • the node B detects that the LOF pre-alarm occurs in the working channel 1, and the node B continues to insert the first maintenance signal frame at the ingress end. However, because the ingress end of node B and the egress end of node B belong to different TCM path segments, the egress end of node B will modify the TCM overhead of the first maintenance signal frame and pass the working channel 2 and protection channel 2 to Node C sends the modified first maintenance signal frame.
  • the modified first maintenance signal frame and the first maintenance signal frame play the same role at each node, and both support normal framing and are processed according to the normal signal frame. After node C receives the modified first maintenance signal frame through working channel 2, it can perform normal framing on the modified first maintenance signal frame.
  • the first maintenance signal frame modified by node B is referred to as signal frame 1
  • the first maintenance signal frame modified by node C is referred to as signal frame 2.
  • node B detects framing failure for X ms from the beginning of the failure, it detects that a LOF alarm occurs on working channel 1.
  • Node B terminates the insertion of the first maintenance signal frame at the ingress end, and inserts the AIS frame at the ingress end. Therefore, after the node C detects the LOF pre-alarm, it can receive the signal frame 1 used for normal framing, and will not detect the LOF alarm. In the same way, node D will not detect the LOF alarm.
  • the node A-node D adopts the SNCP/S TCM cascade mode for networking
  • the egress end will modify the TCM overhead of the AIS, and the modified AIS is normal Signal frame, therefore, the next hop will not mistakenly trigger SNCP group switching due to receiving AIS. Therefore, when the node B detects that the LOF alarm occurs on the working channel 1, it can insert the AIS frame without delay, and insert the AIS frame in time.
  • Figure 9 is a schematic diagram of the alarm processing flow in the SNCP/N TCM cascade networking. Take the end-to-end path including node A-node D configured with an SNCP group as an example. Node A sends data frames to node D through node B and node C. Node A, Node B, Node C, and Node D are all configured with TCM functions. For example, the TCM mode configured by the node A and the node D is the operation mode, and the TCM mode configured by the node B and the node C is the monitoring mode or the transparent mode.
  • the difference between Fig. 9 and Fig. 8 is that in Fig.
  • node A and node B, node B and node C, and node C and node D constitute three different TCM path segments.
  • node A-node D belongs to the same TCM path segment.
  • the path between node A and node B in Figure 9 is called path segment 1
  • the path between node B and node C is called path segment 2
  • the path between node C and node D is called Path segment 3.
  • the existing method when adopted, when a failure occurs between node A and node B, node C and node D continue to detect frame loss for X ms and generate and report a LOF alarm.
  • C and node D will also trigger the execution of SNCP group switching, which will lead to false switching of node C and node D.
  • the node B detects that the LOF pre-alarm occurs in the working channel 1, and the node B continues to insert the first maintenance signal frame at the ingress end.
  • the egress end of node B forwards the first maintenance signal frame to node C.
  • node C After node C receives the first maintenance signal frame, it can perform normal framing of the first maintenance signal frame, so that node C will not mistakenly detect the LOF alarm, nor will it mistakenly trigger the execution of the SNCP group switch due to the mistaken detection of the LOF alarm .
  • After node C receives the first maintenance signal frame it sends the first maintenance signal frame to node D, so that node D can frame the first maintenance signal frame normally, and node D will not mistakenly detect the LOF alarm.
  • the SNCP group switching will not be triggered by mistake due to the false detection of the LOF alarm.
  • node B Since the link between node B and node C, and the link between node C and node D belong to the same TCM path segment, if the working channel 1 has a fiber failure, it will cause node B to detect frame loss continuously for X ms Resulting in LOF alarm, node B will insert AIS at the ingress end, and node B will not modify the TCM overhead in the AIS at the ingress end and send it directly to node C. Similarly, after node C receives the AIS from node B, The TCM overhead in the AIS will not be modified, and the AIS will be transparently transmitted to the node D directly. After the node C and the node D receive the AIS, they will trigger the SNCP group switching, causing the node C and the node D to switch incorrectly.
  • the node C receives the AIS and starts timing. If the AIS is received for Z ms, the switching is performed. After node C receives the AIS from node B each time, it sends the received AIS to node D. In order to prevent the fault of path segment 3 from accidentally switching, node D starts timing after receiving the AIS, and needs to receive the AIS for 2*Z ms before performing the switching.
  • node D cannot determine whether the AIS was issued by node B or node C after receiving the AIS, it cannot determine whether path segment 2 is faulty or path segment 3 is faulty or path segment 2 and path segment 3 are faulty. All failures, so for the trigger time for node D to perform the switch, it is necessary to delay the time for node B to complete the switch plus the time for node C to complete the switch, that is, 2*Z ms. It can be seen from the above that starting from the second node, each node of the subsequent path, as the distance from the second node gets farther and farther, the delay switching time becomes longer and longer.
  • the second network device After the second network device detects the LOF alarm, it delays the insertion of the AIS frame. Specifically, referring to FIG. 9, if the node B detects that the framing fails for X ms from the beginning of the failure, it detects that the LOF alarm has occurred on the channel 1. Node B inserts the AIS frame under the ingress port delay of working channel 1, and the specific delay time is Z ms. Continues to insert the first maintenance signal frame on the ingress port of working channel 1, and sends it to node C through working channel 2 and protection channel 2. Send the first maintenance signal frame.
  • the node B detects the occurrence of the LOF alarm, it triggers the execution of the switching of the subnet connection protection group, and switches the receiving channel from the working channel 1 to the protection channel 1.
  • the switching of the subnet connection protection group performed by the node B is less than or equal to Z ms.
  • the node B receives the data frame from the node A through the protection channel 1, and the node B terminates the insertion of the first maintenance signal frame at the entry end of the working channel 1.
  • Node B sends data frames to node C through working channel 2 and protection channel 2.
  • node B delays the insertion of the AIS frame
  • the node C will not mistakenly detect the occurrence of the AIS alarm due to the receipt of the AIS frame, and the node C will not cause the subnet connection protection group to switch incorrectly due to the false detection of the AIS alarm.
  • node D will not mistakenly detect the occurrence of an AIS alarm because of receiving the AIS frame, and will not cause the subnet connection protection group to switch incorrectly due to the false detection of the AIS alarm.
  • the above solution only delays the insertion of the AIS frame, and does not affect the detection of the AIS alarm and the trigger timing of the switching of the subnet connection protection group.
  • the node C can detect the AIS alarm in time, and can determine the path 2 failure, and can trigger the switching of the subnet connection protection group in time, and there is no need to delay Z ms before switching.
  • node D can detect the AIS alarm in time, and can determine the path 3 failure, which can trigger the subnet connection protection group switching in time, and there is no need to delay the switching after 2*Z ms.
  • the embodiments of this application can also be applied to the scenario of SNCP/N PM cascaded networking.
  • the difference between SNCP/N PM cascade networking and SNCP/N TCM cascade networking is: SNCP/N TCM cascade networking, node A, node B, node C, and node D are all configured with TCM functions , And in the SNCP/N PM cascade network, node A, node B, node C, and node D are not configured with TCM function.
  • the SNCP/N PM cascading networking scenario there are also the following technical problems: Node C and Node D also fail to receive data frames, causing Node C and Node D to continue to detect frame loss for X ms.
  • node C and node D When a failure occurs between node A and node B, when node C and node D detect frame loss for X ms and generate and report a LOF alarm, node C and node D will trigger the execution of SNCP group switching, which will cause node C and node D to perform SNCP group switching. Node D has a false switching. In addition, because the node B and the node C, and the node C and the node D belong to the same PM path segment, and the TCM function is not configured, and each node will not modify the PM overhead of the AIS.
  • node C and node D After node C and node D receive the AIS, they will trigger the SNCP group switching, causing node C and node D to switch incorrectly.
  • the SNCP/N PM cascaded networking adopts the same delay switching time method as the SNCP/N PM cascaded networking.
  • the node C and the node D will not mistakenly detect the LOF alarm.
  • node C can detect the AIS alarm in time, and can determine that the link between node B and node C has failed, and trigger the subnet connection protection group switch in time, without delaying Z ms. Perform a switchover.
  • node D can detect the AIS alarm in time, and can determine the path 3 failure, and trigger the subnet connection protection group switch in time, without delaying 2*Z ms. Perform a switchover.
  • an embodiment of the present application also provides an alarm processing device.
  • the method, device, and system are based on the same inventive concept. Since the method, device, and system have similar principles for solving problems, the implementation of the device and method can be referred to each other, and the repetitions will not be repeated.
  • the device can be used in a network device (such as a first network device, a second network device, or a third network device), and the device can specifically be a processor, a chip, a chip system, or a processor used to perform network device functions A module and so on.
  • the device can be realized by the circuit board in Figure 2.
  • FIG. 10 is a schematic structural diagram of a possible alarm processing device in an embodiment of this application. As shown in FIG. 10, the device includes a detection unit 1001 and a processing unit 1002. Optionally, the device further includes a sending unit 1003.
  • the apparatus is applied to a second network device, the detection unit 1001 is used to perform S401, the processing unit 1002 is used to perform S402, and the sending unit 1003 is used to perform S403.
  • the apparatus is applied to a third network device, the detection unit 1001 is used to perform S404, and the sending unit 1003 is used to perform S405.
  • the apparatus is applied to a second network device, the detection unit 1001 is used to perform S701, and the processing unit 1002 is used to perform S702, S703, and S704.
  • the above three units may also perform other relevant optional steps performed by the first network device, the second network device, or the third network device mentioned in any of the foregoing embodiments, which will not be repeated here.
  • the division of units in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • the functional units in the various embodiments of the present application may be integrated in one processor, or may exist alone physically, or two or more units may be integrated in one unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.
  • FIG. 11 is a schematic structural diagram of another possible alarm processing device according to an embodiment of the application.
  • the apparatus 1100 includes a communication interface 1110, a processor 1120, and a memory 1130.
  • the device can be applied to the first network device, the second network device, or the third network device.
  • the detection unit 1001, the processing unit 1002, and the sending unit 1003 shown in FIG. 11 may all be implemented by the processor 1120.
  • the processor 1102 may be a signal processor in the circuit board shown in FIG. 2.
  • the processor 1120 receives the data frame through the communication interface 1110, and is used to implement the method executed by the first network device, the second network device, or the third network device in FIG. 4 or FIG. 7. In the implementation process, each step of the processing flow can be completed by the hardware integrated logic circuit or software instructions in the processor 1120.
  • the communication interface 1110 may be a circuit, a bus, a transceiver, or any other device that can be used for information exchange.
  • the other device may be a device connected to the device 1100, for example, the other device may be a receiving end or an intermediate node.
  • the processor 1120 may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component.
  • the general-purpose processor may be a microprocessor or any conventional processor or the like.
  • the steps of the method disclosed in combination with the embodiments of the present application may be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software units in the processor.
  • the program code executed by the processor 1120 for implementing the foregoing method may be stored in the memory 1130.
  • the memory 1130 and the processor 1120 are coupled.
  • the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, and may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • the processor 1120 may operate in cooperation with the memory 1130.
  • the memory 1130 may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., and may also be a volatile memory (volatile memory), such as random access memory (random access memory). -access memory, RAM).
  • the memory 1130 is any other medium that can be used to carry or store program codes in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • connection medium between the aforementioned communication interface 1110, the processor 1120, and the memory 1130 is not limited in the embodiment of the present application.
  • the memory 1130, the processor 1120, and the communication interface 1110 are connected by a bus.
  • the bus is represented by a thick line in FIG. 11, and the connection mode between other components is only for schematic illustration, and is not to be taken as a limitation.
  • the bus can be divided into an address bus, a data bus, a control bus, and so on. For ease of presentation, only one thick line is used to represent in FIG. 11, but it does not mean that there is only one bus or one type of bus.
  • the embodiments of the present application also provide a computer storage medium, the storage medium stores a software program, and when the software program is read and executed by one or more processors, any one or more of the above The method provided by the embodiment.
  • the computer storage medium may include: U disk, mobile hard disk, read-only memory, random access memory and other media that can store program codes.
  • an embodiment of the present application also provides a chip.
  • the chip includes a processor, which is used to implement the functions involved in any one or more of the foregoing embodiments, such as acquiring or processing the data frames involved in the foregoing methods.
  • the chip further includes a memory, and the memory is used for necessary program instructions and data to be executed by the processor.
  • the chip can be composed of a chip, or it can include a chip and other discrete devices.
  • These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • these computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so that the computer or other programmable equipment
  • the executed instructions provide steps for implementing functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Electromagnetism (AREA)
  • Environmental & Geological Engineering (AREA)
  • Maintenance And Management Of Digital Transmission (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本申请公开了一种告警处理方法及装置，以解决误检LOF告警产生资源浪费的问题。具体提供配置检测LOF预告警的机制。LOF预告警的检测条件是检测到定帧失败持续第一时长。LOF告警的检测条件是检测到定帧失败持续第二时长。第二时长小于第一时长。网络设备在检测到LOF预告警的情况下，执行第一维护信号帧的下插。第一维护信号帧支持定帧。即接收到第一维护信号帧的网络设备可以进行正常定帧，并且不会上报告警，比如不会触发LOF告警。因此，接收到第一维护信号帧的网络设备并不会因为定帧失败持续第二时长而误产生LOF告警，进而不会执行上报LOF告警或者误倒换，避免产生资源浪费。

Description

一种告警处理方法及装置
本申请要求于2020年6月2日提交中国国家知识产权局、申请号为202010488897.2、申请名称为“一种告警处理方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信技术领域，尤其涉及一种告警处理方法及装置。
背景技术
帧丢失(loss of frame，LOF)告警是指线路接收侧帧丢失。在光传送网络(optical transport network，OTN)中，第一网络设备与上一跳网络设备之间发生断纤等故障时，第一网络设备会检测到LOF告警。在第一网络设备检测到LOF告警时，由于数据帧在第一网络设备就已经出现丢失，导致下一跳网络设备也可能会检测到帧丢失而产生并上报LOF告警，因此下一跳网络设备产生误检LOF告警的情况，导致由于误检执行后续动作而产生资源浪费。
发明内容
本申请实施例提供一种告警处理方法，以解决误检LOF告警产生资源浪费的问题。
第一方面，本申请实施例提供一种告警处理方法。该方法包括：第二网络设备检测到第一工作通道出现LOF预告警；所述第一工作通道用于连通所述第二网络设备和第一网络设备；其中，所述LOF预告警的检测条件为对来自所述第一网络设备的数据帧进行定帧失败持续第一时长，所述第一时长小于第二时长，所述第二时长为LOF告警的检测条件中的定帧失败持续时长；所述第二网络设备在入口端下插第一维护信号帧，所述入口端用于通过第一工作通道接收来自第一网络设备的数据帧，所述第一维护信号帧用于定帧。
需要说明的是，LOF预告警的检测条件中的定帧持续时长小于LOF告警的检测条件中的定帧失败持续时长。因此，第二网络设备检测到第一工作通道出现LOF预告警是在检测到第一工作通道出现LOF告警之前。
通过上述方案，第二网络设备在检测到LOF预告警的时，向下一跳网络设备(即上述第三网络设备)下插第一维护信号帧，使得第三网络设备可以正确地定帧。因此，不会因为第一网络设备与第二网络设备之间的工作通道出现故障而导致第三网络设备并误上报LOF告警。由于上报LOF告警需要占用第三网络设备的发送资源，并且管理设备需要对第三网络设备上报的LOF告警进行后续处理，进而占用管理设备的处理资源，因此，第三网络设备误上报告警会产生资源浪费。
在一种可能的设计中，上述方法还可以包括：所述第二网络设备检测到所述第一工作通道出现LOF告警时，终止在所述入口端下插所述第一维护信号帧，并在所述入口端下插告警指示信号AIS帧。上述设计中，在第二网络设备检测到LOF告警时候，将第一维护信号帧替换为AIS帧，从而向下一跳发送该AIS帧，使得下一跳及时上报AIS告警。
在一种可能的设计中，所述第一网络设备和所述第二网络设备均配置有子网连接保护组，所述方法还可以包括：所述第二网络设备检测到所述第一工作通道出现LOF告警，触发所述第二网络设备的子网连接保护组倒换，并在第三时长内持续在所述入口端下插所述第一维护信号帧。第三时长为检测到LOF告警后延迟下插AIS帧的时长。第三时长大于或者等于第二网络设备完成子网连接保护组倒换的时长。
在一种可能的设计中，第二网络设备检测到所述第一工作通道出现LOF告警后，在所述入口端下插第一维护信号帧的持续时长达到所述第三时长且未接收到来自第一网络设备的数据帧时，终止在所述入口端下插所述第一维护信号帧，并在所述入口端下插AIS帧。
上述设计中，针对存在子网连接保护组的情况，在第一网络设备检测到LOF告警的时候，不立即下插AIS，为了防止后续路径上的网络设备发生误倒换，延迟向下一跳网络设备发送AIS帧，在第二网络设备完成倒换的这段时间内，向下一跳发送第一维护信号帧，从而后续路径上的网络设备可以进行正常定帧，不会因为检测到帧丢失而产生LOF告警，并且第一网络设备延迟发送AIS帧的这段时间，第一网络设备完成倒换后，能够正常接收上一跳的数据帧，从而后续路径上的网络设备也能正常接收到数据帧，不会产生LOF告警或AIS告警也不会发生误倒换。
在一种可能的设计中，所述第一维护信号帧的开销包括第一值；所述第一值用于指示所述第一维护信号帧为空NULL类型维护信号。
在一种可能的设计中，所述开销为通道监控PM段开销或者串联连接监控TCM段开销。示例性的，第一维护信号帧的开销包括的指示字段为第一值。比如，指示字段可以是PM段开销中的状态标识符字段或者TCM段开销中的状态标识符字段。
第二方面，本申请实施例提供一种告警处理方法，该方法包括：第三网络设备检测到第二工作通道出现LOF预告警；所述第二工作通道用于连通所述第三网络设备和第二网络设备；其中，所述LOF预告警的检测条件为对来自所述第二网络设备的数据帧进行定帧失败持续第一时长；所述第三网络设备检测到第二工作通道出现LOF告警之前，通过所述第二工作通道接收到来自第二网络设备的第一维护信号帧；其中，所述第一维护信号帧用于定帧；所述LOF告警的检测条件为对来自所述第二网络设备的数据帧进行定帧失败持续第二时长，所述第二时长大于所述第一时长。所述第三网络设备对第一维护信号帧进行定帧处理。可选地，第三网络设备向下一跳网络设备发送第一维护信号帧。
通过上述设计，第三网络设备在检测到出现LOF预告警后，产生LOF告警前接收到支持正常定帧的第一维护信号帧，在与上一跳网络设备之间未发生故障的情况下，能够进行正常定帧处理，从而不会误检并上报LOF告警产生资源浪费。
在一种可能的设计中，上述方法还可以包括：所述第三网络设备通过所述第二工作通道接收到来自所述第二网络设备的第一维护信号帧后，通过所述第二工作通道接收到来自所述第二网络设备的告警指示信号AIS帧；所述第三网络设备上报AIS告警。
通过上述设计，第三网络设备接收到AIS帧后，及时上报AIS告警。
在一种可能的设计中，第二网络设备和所述第三网络设备均配置有子网连接保护组，所述方法还包括：所述第三网络设备通过所述第二工作通道接收到来自所述第二网络设备的第一维护信号帧后，通过所述第二工作通道接收到来自所述第二网络设备的AIS帧；所述第三网络设备触发子网连接保护组倒换，并上报AIS告警。
通过上述设计，第三网络设备接收到AIS帧后，立即触发SNCP倒换，无需等待延迟一定时间后再触发。
在一种可能的设计中，所述第一维护信号帧的开销包括第一值；所述第一值用于指示所述第一维护信号帧为空NULL类型维护信号。
在一种可能的设计中，所述开销为通道监控PM段开销或者串联连接监控TCM段开销。示例性的，第一维护信号帧的开销包括的指示字段为第一值。比如，指示字段可以是PM段开销中的状态标识符字段或者TCM段开销中的状态标识符字段。
第三方面，本申请实施例提供一种告警处理装置。该告警处理装置应用于网络设备，比如第二网络设备或者第三网络设备。该装置包括处理器以及存储器。所述存储器用于存储程序代码；所述处理器用于读取并执行所述存储器存储的程序代码，以实现如第一方面或者第一方面的任一设计所述的方法，或者实现如第二方面或第二方面的任一设计所述的方法。
第四方面，本申请实施例提供了一种计算机可读存储介质，该存储介质中存储软件程序，该软件程序在被一个或多个处理器读取并执行时可实现第一或者第二方面的任意一种设计提供的方法。
第五方面，本申请实施例提供了一种包含指令的计算机程序产品。当其在计算机上运行时，使得计算机执行上述第一方面或第二方面的任一设计提供的方法。
第六方面，本申请实施例提供了一种芯片。所述芯片与存储器相连，用于读取并执行所述存储器中存储的软件程序，以实现第一方面或第二方面的任意一种设计提供的方法。
附图说明
图1为本申请实施例中OTN网络架构示意图；
图2为本申请实施例中OTN设备结构示意图；
图3为本申请实施例中一种可能的端到端的组网示意图；
图4为本申请实施例提供的一种可能的告警处理方法的流程示意图；
图5为本申请实施例的场景一提供的一种可能的告警处理流程示意图；
图6为本申请实施例的场景一提供的另一种可能的告警处理流程示意图；
图7为本申请实施例提供的另一种可能的告警处理方法的流程示意图；
图8为本申请实施例提供的SNCP/S TCM级联组网下告警处理流程示意图；
图9为本申请实施例提供的SNCP/N TCM级联组网下告警处理流程示意图；
图10为本申请实施例中一种可能的告警处理装置的结构示意图；
图11为本申请实施例的另一种可能的告警处理装置的结构示意图。
具体实施方式
本申请实施例适用于光网络，例如：OTN。一个OTN通常由多个OTN设备通过光纤连接而成，可以根据具体需要组成如线型、环形和网状等不同的拓扑类型。如图1所示的OTN是两个OTN网络组成。每一个OTN网络由一定数量的OTN设备(N1～N7)组成。根据实际的需要，一个OTN设备可能具备不同的功能。一般地来说，OTN设备分为光层 设备、电层设备，以及光电混合设备。光层设备指的是能够处理光层信号的设备，例如：光放大器(optical amplifier，OA)。电层设备指的是能够处理电层信号的设备，例如：能够处理OTN信号的设备。光电混合设备指的是具备处理光层信号和电层信号能力的设备。需要说明的是，根据具体的集成需要，一台OTN设备可以集合多种不同的功能。本申请提供的技术方案适用于不同形态和集成度的OTN设备。本申请实施例中涉及到的网络设备可以是OTN设备，网络设备也可以称为网络节点，或者简称为节点。
图2为一种可能的OTN设备结构示意图。这里的OTN设备可以指图1中的OTN节点(N1～N7)。具体地，一个OTN设备包括电源、风扇、辅助类单板，还可能包括支路板、线路板、交叉板、光层处理单板，以及系统控制和通信类单板。其中，电源用于为OTN设备供电，可能包括主用和备用电源。风扇用于为设备散热。辅助类单板用于提供外部告警或者接入外部时钟等辅助功能。支路板、交叉板和线路板主要是用于处理OTN的电层信号。其中，支路板用于实现各种客户业务的接收和发送，例如SDH业务、分组业务、以太网业务和前传业务等。更进一步地，支路板可以划分为客户侧光模块和信号处理器。其中，客户侧光模块可以为光收发器，用于接收和/或发送业务数据。信号处理器用于实现对业务数据到数据帧的映射和解映射处理。交叉板用于实现数据帧的交换，完成一种或多种类型的数据帧的交换。线路板主要实现线路侧数据帧的处理。具体地，线路板可以划分为线路侧光模块和信号处理器。其中，线路侧光模块可以为线路侧光收发器，用于接收和/或发送数据帧。信号处理器用于实现对线路侧的数据帧的复用和解复用，或者映射和解映射处理。系统控制和通信类单板用于实现系统控制和通信。具体地，可以通过背板从不同的单板收集信息，或者将控制指令发送到对应的单板上去。需要说明的是，除非特殊说明，具体的组件(例如：信号处理器)可以是一个或多个，本申请不做任何限制。还需要说明的是，本申请实施例不对设备包含的单板类型，以及单板具体的功能设计和数量做任何限制。
需要说明的是，每个设备具体包含的单板类型和数量可能不相同。例如：作为核心节点的网络设备可能没有支路板。作为边缘节点的网络设备可能有多个支路板。
下面先对本申请实施例中涉及到的技术概念进行说明。
1)帧丢失(loss of frame，LOF)告警。LOF告警是指线路接收侧帧丢失。一般情况下在检测到A1、A2字节接收有误时，则检测到LOF告警。A1、A2字节是帧同步字节。
2)告警指示信号(alarm indication signal，AIS)是OTN网络中的一种维护信号。AIS的作用是传递告警信息，即将上游节点业务失效的信号传递给下游节点或者将服务层信号失效的信息传递给客户层。
3)数据帧：可以为OTN帧或者灵活以太网(Flex Ethernet，FlexE)帧，用于承载各种业务数据，能够实现对业务数据的管理和监控。OTN帧可以是光数据单元(optical data unit，ODU)k、ODUCn、ODUflex，或者光传输单元(optical transport unit，OTU)k，OTUCn，或者光净荷单元(optical payload unit，OPU)，或者灵活OTN(flexible OTN，FlexO)帧，或者灵活光服务单元(flexible optical service unit，OSUflex)等。数据帧还可以是其它适用于光网络的帧结构。
4)通道监控(path monitoring，PM)提供一种端到端的通道监控功能。串联连接监控(tandem connection monitoring，TCM)的监控范围是PM范围监控范围中的一部分。
在OTN中包括6级TCM的开销(overhead，OH)。TCM包括路径跟踪标识(trail trace identifier，TTI)、比特间差奇偶性校验(bit interleaved parity 8，BIP8)、后向缺陷指示(backward defect indication，BDI)、后向误码指示(backward error indication，BEI)、状态指示符(states，STAT)，后向进入定位错误(backward incoming alignment error，BIAE)。针对需要TCM功能的节点可以进行TCM功能配置。对于每个节点，源方向(或称为发送方向)的TCM和宿方向(或称为接收方向)的TCM可以配置为不同的模式或者相同的模式。
其中，发送方向有操作(operational)模式和透明(transparent)模式。网络设备采用的某个级别TCM的模式为operational模式，则网络设备对这个级别的TCM进行再生处理，比如包括插入BIP-8、BEI、BIAE、BDI、TTI等。网络设备采用的某个级别TCM的模式为transparent模式，则网络设备对这个级别的TCM不进行处理。
接收方向有operational模式、transparent模式或监控模式。网络设备采用的某个级别TCM的模式为operational模式，则网络设备对该级别的TCM进行监视。比如包括监视BIP-8、BEI、BIAE、BDI、TTI等开销，产生相应缺陷，并进行后续的处理，如下插AIS或产生路径信号失效(Trail signal fail，TSF)。网络设备采用的某个级别TCM的模式为监控模式，则网络设备对这个级别的TCM进行监视处理。比如包括监视BIP8、BEI、BIAE、BDI、TTI等开销，产生相应缺陷，但不进行AIS和TSF后续行动的处理。网络设备采用的某个级别TCM的模式为transparent模式，则网络设备对这个级别的TCM不进行处理。
5)子网连接保护(sub-network connection protection，SNCP)指对某一子网连接预先安排专用的保护路由，一旦子网发生故障，专用保护路由便取代子网承担在整个网络中的传送任务。SNCP每个传输方向的保护通道都与工作通道走不同的路由。比如，节点A和B之间通过SNCP传送业务，即节点A通过桥接的方式分别通过子网1(工作SNC，即工作通道)和子网2(保护SNC，即保护通道)将业务传向节点B，而节点B则通过一个倒换开关按照倒换准则从两个方向选取一路业务信息。节点B执行子网连接保护组倒换，即从子网1接收来自节点A的业务倒换到从子网2接收来自节点A的业务。
SNCP采用的是双发选收的工作方式，正常情况下，选择通过工作SNC接收业务，当工作SNC出现故障时，选择通过保护SNC接收业务。
SNCP包括使用非介入式监视的子网连接保护(non-intrusively monitored sub-network connection protection，SNCP/N)和使用子层监视的子网连接保护(SNCP with sublayer monitoring，SNCP/S)。SNCP/N采用的监控方法是在信号中通过对端到端或者子层的开销或操作管理和维护(operation administration and maintenance，OAM)信息进行探测。SNCP/S检测服务层缺陷情况、层网络内连续性/连通性缺陷状况、以及层网络内的误码劣化状况，通过使用子层开销/OAM实现监测。SNCP/S将服务层的PM段的SF告警以及本层的TCM段的SF告警作为倒换条件。开销比如可以是PM或者TCM等。
6)维护信号。OTN网络中目前存在三种维护信号帧，分别为AIS、锁定指示信号(locked，LCK)以及开放连接指示(open connection indication，OCI)。
本申请实施例提供的第一维护信号帧，不同于以上三种维护信号帧。AIS、LCK以及OCI不支持正常定帧。本申请实施例提供的第一维护信号帧用于正常定帧。第一维护信号帧可以为NULL类型的维护信号。第一维护信号帧采用的帧格式与数据帧的帧格式相同。 比如，数据帧为ODUk，第一维护信号帧采用的格式与ODUk的格式相同。
第一维护信号帧的开销包括指示字段。通过指示字段的取值来指示该第一维护信号帧是否属于NULL类型维护信号。比如指示字段的取值为第一值，第一值指示第一维护信号帧为NULL类型维护信号。一种示例中，指示字段可以是开销中新定义的一个字段。另一种示例中，所述第一维护信号帧的开销包括的指示字段可以为PM段开销中的STAT字段或者TCM段开销中的STAT字段。表1为PM段开销中STAT不同取值的含义。示例性地，当第一维护信号帧的开销包括的指示字段可以为PM段开销中的STAT字段时，第一值可以为“000”、“010”、“011”或“100”中的其中一个。
表1
PM STAT取值 含义
000 预留作未来国际标准使用
001 正常的通道信号
010 预留作未来国际标准使用
011 预留作未来国际标准使用
100 预留作未来国际标准使用
101 维护信号：LCK
110 维护信号：OCI
111 维护信号：AIS
表2为TCM段开销中STAT不同取值的含义。示例性地，当第一维护信号帧的开销包括的指示字段可以为TCM段开销的STAT字段时，第一值可以为“011”或“100”。
表2
TCM STAT取值 含义
000 源端无串联连接监视
001 源端有串联连接监视，无IAE(正常信号)
010 源端有串联连接监视，有IAE
011 预留作未来国际标准使用
100 预留作未来国际标准使用
101 维护信号：LCK
110 维护信号：OCI
111 维护信号：AIS
7)本申请实施例中“多个”指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，需要理解的是，在本申请的描述中，“第一”、“第二”等词汇，仅用于区分描述的目的，而不能理解为指示或暗示相对重要性，也不能理解为指示或暗示顺序。
本申请可以应用于端到端的组网方式中。端到端的组网中可以配置SNCP组，也可以 不配置SNCP组。
图3为本申请实施例提供的一种可能的端到端的组网示意图。端到端的路径为节点A-B-C-D。节点A通过节点B和节点C向节点D发送数据帧。节点A与B之间通过通道1连通，节点B和C之间通过通道2连通，节点C和D之间通过通道3连通。当在通道1发生断纤等故障时，节点B持续X ms(毫秒)检测到出现帧丢失(或定帧失败)，则确定产生LOF告警，并在接收方向下插AIS。本申请实施例涉及的通道也可以称为链路。
节点B在检测到LOF告警时，数据帧已经发生丢失，导致节点C和节点D接收不到数据帧，因此节点C和节点D也会持续X ms检测到出现帧丢失而产生并上报LOF告警，即节点C误检测到通道2出现故障，节点D误检测到通道3出现故障，进一步导致节点C和节点D由于误检并向管理设备上报LOF告警，进而需要管理设备对通道2和通道3进行故障检测产生资源浪费。在节点A-D均配置有SNCP保护组的情况下，节点B检测到LOF告警时，会执行SNCP组倒换。同样地，节点C和D检测到LOF告警时，也会执行SNCP组倒换。在仅通道1发生故障时，节点C和D会执行误倒换产生资源浪费。
为了避免网络设备由于误检上报LOF告警或者误倒换而产生资源浪费的问题，本申请实施例提供一种告警处理方法及装置，具体提供配置检测LOF预告警的机制。LOF预告警的检测条件是检测到定帧失败持续第一时长。LOF告警的检测条件是检测到定帧失败持续第二时长。第二时长小于第一时长。网络设备在检测到LOF预告警时，执行第一维护信号帧的下插。第一维护信号帧用于定帧。即接收到第一维护信号帧的网络设备可以进行正常定帧，从而不会上报告警，比如不会触发LOF告警。因此，接收到第一维护信号帧的网络设备并不会因为定帧失败持续第二时长而误产生LOF告警，进而不会执行误上报LOF告警或者误倒换，避免产生资源浪费。
本申请实施例适用于配置SNCP组的场景或未配置SNCP组的场景。下面结合这两种场景，对本申请实施例提供的方案进行详细说明。
场景一
以传输路径上包括第一网络设备、第二网络设备、第三网络设备为例，第一网络设备、第二网络设备以及第三网络设备均未配置SNCP组。第一网络设备、第二网络设备以及第三网络设备均包括入口端和出口端。入口端也可以称为接收端口，用于接收上一跳网络设备发送的信号，出口端也可以称为发送端口，用于向下一跳网络设备发送信号。
图4为本申请实施例提供的一种可能的告警处理方法的流程示意图。告警处理方法包括S401-S405。
S401，第二网络设备检测到第一工作通道出现LOF预告警；第一工作通道用于连通第二网络设备和第一网络设备。
其中，LOF预告警的检测条件为对来自第一网络设备的数据帧进行定帧失败持续第一时长，第一时长小于第二时长，第二时长为LOF告警的检测条件中的定帧失败持续时长。
由于，LOF预告警的检测条件中的定帧持续时长小于LOF告警的检测条件中的定帧失败持续时长。因此，第二网络设备检测到第一工作通道出现LOF预告警是在检测到第一工作通道出现LOF告警之前。
第二网络设备对通过第一工作通道接收的数据帧进行定帧失败持续第一时长，则检测到第一工作通道出现LOF预告警。如果定帧失败继续持续到第二时长，则检测到第一工作 通道出现LOF告警。当然如果检测到第一工作通道出现LOF预告警后，在检测到出现LOF告警之前，如果检测到数据帧，即能够确定第一工作通道为正常通道。进一步的，第二网络设备终止第一维护信号帧的下插。
示例性地，第二网络设备在检测到出现LOF告警之前，确定检测到数据帧，可以通过如下方式1或方式2来确定。
方式1、持续时长1接收到来自第一网络设备的数据帧，则确定检测到数据帧。时长1小于第二时长与第一时长的差。
方式2、在检测到第一工作通道出现LOF预告警后，且在未检测到出现LOF告警之前，接收到来自第一网络设备的数据帧的数量达到阈值1，则确定检测到数据帧。
通道由于抖动导致瞬时有数据帧发出，第二网络设备检测到数据帧。这可能会导致第二网络设备误判通道无故障，进而无法及时启动故障恢复流程，导致业务中断时长延长。通过上述方式，即使由于抖动导致瞬时有数据帧发出，但是第二网络设备在时长1不会持续检测到数据帧或者检测到的数据帧的数量不会达到阈值，从而不会误判通道无故障。
S402，第二网络设备在入口端下插第一维护信号帧。
其中，所述入口端用于通过第一工作通道接收来自第一网络设备的数据帧。
可选地，S403，第二网络设备通过第二工作通道向第三网络设备发送第一维护信号帧。
第二工作通道用于连通第二网络设备和第三网络设备，第一维护信号帧用于定帧。
需要说明的是，当第二工作通道与第一工作通道属于不同的TCM段时，第二网络设备的出口端对第一维护信号帧的TCM段开销进行修改后，再发送给第三网络设备。修改后的第一维护信号帧与第一维护信号帧的作用相同，均支持正常定帧，并且不会触发告警。
S404，第三网络设备检测到第二工作通道出现LOF预告警；所述第二工作通道用于连通第三网络设备和第二网络设备。
第二网络设备通过第二工作通道向第三网络设备发送第一维护信号帧，如果在第二工作通道未出现故障，第三网络设备能够正常接收到第一维护信号帧。如果第三网络设备检测到第二工作通道出现LOF告警之前，通过所述第二工作通道接收到来自第二网络设备的第一维护信号帧；则第三网络设备可以对第一维护信号帧进行定帧处理。执行S405。
S405，所述第三网络设备发送所述第一维护信号帧。具体的，第三网络设备向第三网络设备的下一跳网络设备发送第一维护信号帧。
本申请实施例提供的方案，第二网络设备在检测到LOF预告警的时候，此时还未检测到LOF告警，向下一跳网络设备(即上述第三网络设备)下插第一维护信号帧，第三网络设备可以对该第一维护信号帧进行定帧处理。因此，不会因为第一网络设备与第二网络设备之间的工作通道出现故障时，导致定帧失败持续时长达到第二时长而导致误检测到LOF告警，并上报LOF告警导致资源浪费。
作为一种示例，第三网络设备检测到LOF预告警后，若接收到来自第二网络设备发送的第一维护信号帧或者正常信号帧，则取消LOF预告警。
在一种可能的实施方式中，第二网络设备检测到第一工作通道出现LOF告警时，则终止在入口端下插所述第一维护信号帧，并在入口端下插告警指示信号AIS帧。进而，第二网络设备接收到持续接收到第一维护信号帧后，接收到来自第二网络设备的AIS帧，第三网络设备可以上报AIS告警。
下面以第一时长为Y ms，第二时长为X ms为例对上述方案进行详细说明。以图3所示的组网方式为例。端到端的路径中包括节点A-节点D。节点A通过节点B和节点C向节点D发送数据帧。节点A的出口端与节点B的入口端之间通过通道1连通，节点B的出口端和节点C的入口端之间通过通道2连通，节点C的出口端和节点D的入口端之间通过通道3连通。节点A-节点D均未配置SNCP组。
示例1，节点A与节点B、节点B与节点C，以及节点C与节点D，属于相同的PM路径分段，但是未配置TCM功能。图5为本申请实施例的场景一提供的一种可能的告警处理流程示意图。图5中以节点A的出口端与节点B的入口端之间的通道1出现故障为例，通道2和通道3均属于正常通道。在通道1出现故障时，节点B的入口端接收不到来自节点A的数据帧，即从故障开始持续Y ms，检测到定帧失败，则检测到通道1出现了LOF预告警。节点C的入口端也接收不到来自节点B的数据帧，因此，节点C也会检测到出现LOF预告警，同样节点D也会检测到出现LOF预告警。
节点B检测到通道1出现LOF预告警时，会在其入口端持续下插第一维护信号帧。节点B的出口端将第一维护信号帧转发给节点C。节点C收到第一维护信号帧后，能够对第一维护信号帧进行正常定帧。如果节点B从故障开始持续X ms检测到定帧失败，则检测到通道1出现了LOF告警。节点B在入口端终止第一维护信号的下插，并在入口端下插AIS帧。因此，节点C接收到AIS帧之前会持续接收到第一维护信号帧，不会检测到LOF告警。同理，节点D接收到AIS之前也不会检测到LOF告警。
示例2，节点A与节点B、节点B与节点C以及节点C与节点D属于相同的PM路径分段，但属于不同的TCM路径分段。图6为本申请实施例的场景一提供的另一种可能的告警处理流程示意图。图6中节点A和B之间的通道1出现故障为例。
节点B检测到通道1出现LOF预告警，会在入口端持续下插第一维护信号帧。但是由于节点B的入口端和节点B的出口端属于不同的TCM路径分段，因此节点B的出口端会对第一维护信号帧的TCM开销进行修改，并将修改后的第一维护信号帧发送给节点C。修改后的第一维护信号帧与第一维护信号帧在各个节点所起的作用相同，均用于正常定帧，按照正常信号帧处理。节点C收到修改后的第一维护信号帧后，能够对修改后的第一维护信号帧进行正常定帧。为了描述方便将节点B修改后的第一维护信号帧称为信号帧1，将节点C修改后的第一维护信号帧称为信号帧2。如果节点B从故障开始持续X ms检测到定帧失败，则检测到通道1出现了LOF告警。节点B在入口端终止第一维护信号帧的下插，并在入口端下插AIS帧。因此，节点C检测到LOF预告警后，能够接收到能够正常定帧的信号帧1，不会检测到LOF告警。同理，节点D也不会检测到LOF告警。
场景二
以传输路径上网络设备均配置SNCP组为例。具体地，第一网络设备与第二网络设备之间部署有第一工作通道和第一保护通道；第二网络设备与第三网络设备之间部署有第二工作通道和第二保护通道。第一网络设备、第二网络设备以及第三网络设备均包括入口端和出口端。入口端也称为接收端口，用于接收上一跳网络设备发送的信号，出口端也称为发送端口，用于向下一跳网络设备发送信号。
图7为本申请实施例提供的另一种可能的告警处理方法的流程示意图。告警处理方法包括S701-S703。
S701，第二网络设备检测到第一工作通道出现LOF预告警。
S702，第二网络设备在入口端下插第一维护信号帧。
S703，第二网络设备检测到第一工作通道出现LOF告警时，触发第二网络设备的子网连接保护组倒换。具体的，第二网络设备将接收通道从第一工作通道切换到第一保护通道。
LOF预告警的检测条件为对来自所述第二网络设备的数据帧进行定帧失败持续第一时长；LOF告警的检测条件为对来自所述第二网络设备的数据帧进行定帧失败持续第二时长，所述第二时长大于所述第一时长。
可选地，上述方法还可以包括：
S704，第二网络设备在第三时长内持续在入口端下插第一维护信号帧。第三时长为检测到LOF告警后延迟下插AIS帧的时长。第三时长大于或者等于第二网络设备完成子网连接保护组倒换的时长。
上述方案中，第二网络设备在检测到LOF预告警的时候，此时还未检测到LOF告警，向下一跳网络设备(即上述第三网络设备)下插第一维护信号帧，第三网络设备可以对该第一维护信号帧进行定帧处理。因此，不会因为上游链路出现故障时，导致检测不到数据帧持续时长达到第二时长而导致误检测到LOF告警，并上报LOF告警导致资源浪费。
示例性地，如果第二网络设备在第三时长内完成了子网连接保护组倒换，第二网络设备接收通道由第一工作通道切换到第一保护通道。但是第一保护通道也出现了故障，第二网络设备通过第一保护通道也无法接收到来自第一网络设备的数据帧，第二网络设备在第一工作通道对应的入口端终止下插第一维护信号帧，并在第一工作通道对应的入口端下插AIS帧。
在本申请实施例中，可以采用SNCP/S TCM级联方式、SNCP/N TCM级联方式或者采用SNCP/N PM级联方式进行组网。
图8为本申请实施例提供的SNCP/S TCM级联组网下告警处理流程示意图。以第一时长为Y ms，第二时长为X ms为例对上述方案进行详细说明。
图8中以端到端的路径中包括配置有SNCP组的节点A-节点D，节点A通过节点B和节点C向节点D发送数据帧。节点A和节点D均配置有PM功能和TCM功能，节点B和节点C配置有TCM功能，以TCM的模式为操作模式为例。图8中，节点A与节点B、节点B与节点C，以及节点C与节点D，属于相同的PM分段，但是属于不同的TCM路径分段。节点A与节点B之间的路径为TCM路径分段1，节点B与节点C之间的路径为TCM路径分段2，节点C与节点D之间的路径为TCM路径分段3。节点A与节点B之间配置有两个通道，分别为工作通道1和保护通道1。节点A通过工作通道1和保护通道1向节点B发送数据帧，而节点B选择通过工作通道1或保护通道1接收数据帧。节点B和节点C之间配置有两个通道，分别为工作通道2和保护通道2，节点B通过工作通道2和保护通道2向节点C发送数据帧，而节点C选择通过工作通道2或保护通道2接收数据帧。节点C和节点D之间配置有两个通道，分别为工作通道3和保护通道3。节点C通过工作通道3和保护通道3向节点D发送数据帧，而节点D选择通过工作通道3或保护通道3接收数据帧。
节点B检测到工作通道1出现了LOF预告警，节点B在入口端持续进行第一维护信号帧的下插。但是由于节点B的入口端和节点B的出口端属于不同的TCM路径分段，因 此节点B的出口端会对第一维护信号帧的TCM开销进行修改，并通过工作通道2和保护通道2向节点C发送修改后的第一维护信号帧。修改后的第一维护信号帧与第一维护信号帧在各个节点所起的作用相同，均支持正常定帧，按照正常信号帧处理。节点C通过工作通道2收到修改后的第一维护信号帧后，能够对修改后的第一维护信号帧进行正常定帧。为了描述方便将节点B修改后的第一维护信号帧称为信号帧1，将节点C修改后的第一维护信号帧称为信号帧2。如果节点B从故障开始持续X ms检测到定帧失败，则检测到工作通道1出现了LOF告警。节点B在入口端终止第一维护信号帧的下插，并在入口端下插AIS帧。因此，节点C检测到LOF预告警后，能够接收到用于正常定帧的信号帧1，不会检测到LOF告警。同理，节点D也不会检测到LOF告警。
可选地，在节点A-节点D采用SNCP/S TCM级联方式进行组网时，由于节点B入口端下插AIS后，出口端会对AIS的TCM开销进行修改，修改后的AIS属于正常信号帧，因此，下一跳不会因为接收AIS而误触发SNCP组倒换。因此，节点B在检测到工作通道1出现LOF告警，可以不延迟下插AIS帧，及时下插AIS帧即可。
另一种示例中，以图9为例。图9为SNCP/N TCM级联组网下告警处理流程示意图。以端到端的路径中包括配置有SNCP组的节点A-节点D为例。节点A通过节点B和节点C向节点D发送数据帧。节点A、节点B、节点C以及节点D均配置有TCM功能。节点A和节点D配置的TCM的模式为操作模式为例，节点B和节点C配置的TCM模式为监控模式或者透明模式。图9与图8不同的是：在图8中节点A与节点B、节点B与节点C，以及节点C与节点D，构成三个不同的TCM路径分段，在图9中节点A-节点D属于同一个TCM路径分段。为了区分，将图9中节点A与节点B之间的路径称为路径分段1，节点B与节点C之间的路径称为路径分段2，节点C与接点D之间的路径称为路径分段3。在图9对应的组网中，采用现有的方式时，在节点A与节点B之间发生故障时，节点C和节点D持续X ms检测到出现帧丢失而产生并上报LOF告警时，节点C和节点D也会触发执行SNCP组倒换，从而导致节点C和节点D产生误倒换的情况。
以节点A与节点B的工作通道1出现故障，但工作通道2和工作通道3均正常为例。采用本申请实施例提供的方案，参见图9所示，在工作通道1出现故障时，节点B的入口端接收不到来自节点A的数据帧，即从故障开始持续Y ms，检测到定帧失败，则检测到工作通道1出现了LOF预告警。节点C的入口端也接收不到来自节点B的数据帧，因此，节点C也会检测到出现LOF预告警，同样节点D也会检测到出现LOF预告警。节点B检测到工作通道1出现了LOF预告警，节点B在入口端持续进行第一维护信号帧的下插。节点B的出口端将第一维护信号帧转发给节点C。节点C收到第一维护信号帧后，能够对第一维护信号帧进行正常定帧，进而节点C不会误检测到LOF告警，也不会因为误检测到LOF告警而误触发执行SNCP组倒换。节点C收到第一维护信号帧后，将第一维护信号帧发送给节点D，从而节点D能够对第一维护信号帧进行正常定帧，进而节点D也不会误检测到LOF告警，也不会因为误检测到LOF告警而误触发执行SNCP组倒换。
由于节点B和节点C之间的链路，以及节点C和节点D之间地链路属于相同的TCM路径段，如果工作通道1出现断纤故障时，导致节点B持续X ms检测到帧丢失导致产生LOF告警，节点B会在入口端下插AIS，节点B在入口端上不会修改AIS中的TCM开销，并直接发送给节点C，同样节点C在接收到来自节点B的AIS后，不会修改AIS中的TCM 开销，直接将透传该AIS给节点D。节点C和节点D接收到AIS后，会触发SNCP组倒换，导致节点C和节点D产生误倒换。
为了防止节点C和节点D发生误倒换，一种可行的方式是：对节点C和节点D的倒换时间进行延长处理。为防止路径分段2故障而发生误倒换，节点C接收AIS开始计时，如果持续Z ms接收到AIS，再执行倒换。节点C每次接收到来自节点B的AIS后，将接收到的AIS发送给节点D。为了防止路径分段3故障而发生误倒换，节点D从接收到AIS开始计时，需要持续2*Z ms接收到AIS，再执行倒换。由于节点D接收到AIS后，无法判断该AIS是由节点B发出的，还是由节点C发出的，因此无法判断路径分段2故障或者路径分段3故障或者路径分段2和路径分段3均故障，因此针对节点D执行倒换的触发时间，需要延迟节点B完成倒换的时间加上节点C完成倒换的时间，即2*Z ms。从上可以看出，从第二个节点开始，后续路径的各个节点，随着与第二个节点的距离越来越远，延迟倒换的时间也越来越长。
为了减少倒换延迟的时长，可以采用上述图7所示的方案，第二网络设备检测到LOF告警后延迟下插AIS帧。具体的，参见图9所示，如果节点B从故障开始持续X ms检测到定帧失败，则检测到通道1出现了LOF告警。节点B在工作通道1的入端口延迟下插AIS帧，具体延迟时长为Z ms，在工作通道1的入端口继续下插第一维护信号帧，并通过工作通道2和保护通道2向节点C发送第一维护信号帧。另外，节点B检测到出现LOF告警后，触发执行子网连接保护组的倒换，将接收通道从工作通道1切换到保护通道1。节点B执行子网连接保护组的倒换小于或者等于Z ms。经过倒换后，节点B通过保护通道1接收到来自节点A的数据帧，节点B在工作通道1入口端终止下插第一维护信号帧。节点B通过工作通道2和保护通道2向节点C发送数据帧。由于节点B延迟下插AIS帧，节点C并不会因为接收到AIS帧而误检测到出现AIS告警，进而节点C不会由于误检AIS告警而产生子网连接保护组误倒换。同样，节点D并不会因为接收到AIS帧而误检测到出现AIS告警，进而不会由于误检AIS告警而产生子网连接保护组误倒换。
上述方案，仅对AIS帧的下插进行了延迟处理，不影响AIS告警的检测以及子网连接保护组倒换的触发时机。在路径分段2故障时，节点C能够及时检测到AIS告警，并且能够确定路径2故障，能够及时触发子网连接保护组倒换，无需再延迟Z ms后再进行倒换。同样，路径分段3故障时，节点D能够及时检测到AIS告警，并且能够确定路径3故障，能够及时触发子网连接保护组倒换，无需再延迟2*Z ms后再进行倒换。
本申请实施例中还可以应用到SNCP/N PM级联组网的场景中。结合图9，SNCP/N PM级联组网与SNCP/N TCM级联组网不同的是：SNCP/N TCM级联组网，节点A、节点B、节点C以及节点D均配置有TCM功能，而SNCP/N PM级联组网中，节点A、节点B、节点C以及节点D均未配置有TCM功能。SNCP/N PM级联组网的场景中，也同样存在如下技术问题：节点C和节点D也同样由于接收不到数据帧，导致节点C和节点D会持续X ms检测到出现帧丢失而产生并上报LOF告警，进而导致资源浪费。在节点A与节点B之间发生故障时，节点C和节点D持续X ms检测到出现帧丢失而产生并上报LOF告警时，节点C和节点D会触发执行SNCP组倒换，从而导致节点C和节点D产生误倒换。另外，由于节点B和节点C之间，以及节点C和节点D之间属于相同的PM路径段，且未配置TCM功能，并且各个节点不会修改AIS的PM开销。因此，节点C和节点D接收 到AIS后，会触发SNCP组倒换，导致节点C和节点D产生误倒换。为了防止节点C和节点D发生误倒换，SNCP/N PM级联组网中采用了与SNCP/N PM级联组网相同的延迟倒换时间的方式。采用本申请实施例提供的方案，节点C和节点D也不会误检测到LOF告警。并且在路径分段2故障时，节点C能够及时检测到AIS告警，并且能够确定节点B和节点C之间的链路发生故障，及时触发子网连接保护组倒换，无需再延迟Z ms后再进行倒换。同样，节点C和节点D之间的链路发生故障时，节点D能够及时检测到AIS告警，并且能够确定路径3故障，及时触发子网连接保护组倒换，无需再延迟2*Z ms后再进行倒换。
基于与上述实施例同样的发明构思，本申请实施例还提供了一种告警处理装置。方法、装置及系统是基于同一发明构思的，由于方法及装置、系统解决问题的原理相似，因此装置与方法的实施可以相互参见，重复之处不再赘述。
该装置可以用于网络设备(比如第一网络设备、第二网络设备或者第三网络设备)，该装置具体可以是处理器、芯片、芯片系统，或是处理器中用于执行网络设备功能的一个模块等。该装置可以由图2中的线路板实现。图10为本申请实施例中一种可能的告警处理装置的结构示意图。如图10所示，装置包括检测单元1001、处理单元1002。可选地，装置还包括发送单元1003。
在一种示例中，该装置应用于第二网络设备，检测单元1001用于执行S401，处理单元1002用于执行S402，发送单元1003用于执行S403。在另一种示例中，该装置应用于第三网络设备，检测单元1001用于执行S404，发送单元1003用于执行S405。在又一种示例中，该装置应用于第二网络设备，检测单元1001用于执行S701，处理单元1002用于执行S702、S703、S704。
可选地，上述三个单元还可以执行前述任一实施例提及的第一网络设备、第二网络设备或第三网络设备执行的其他相关可选步骤，此处不再赘述。
本申请实施例中对单元的划分是示意性的，仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。另外，在本申请各个实施例中的各功能单元可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
图11为本申请实施例的另一种可能的告警处理装置的结构示意图。如图11所示，装置1100包括通信接口1110、处理器1120以及存储器1130。该设备可以应用于第一网络设备、第二网络设备或者第三网络设备。
图11所示的检测单元1001、处理单元1002和发送单元1003均可以由处理器1120实现。示例性地，处理器1102可以为图2所示的线路板中的信号处理器。处理器1120通过通信接口1110接收数据帧，用于实现图4或图7中的第一网络设备、第二网络设备或者第三网络设备执行的方法。在实现过程中，处理流程的各步骤可以通过处理器1120中的硬件的集成逻辑电路或软件形式的指令完成图4或图7中的第一网络设备、第二网络设备或者第三网络设备所执行的方法。
通信接口1110可以是电路、总线、收发器或其它任意可以用于进行信息交互的装置。其中，示例性地，该其它装置可以是与该装置1100相连的设备，比如其它装置可以是接收端或中间节点。
处理器1120可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或其他可编程逻辑器件、分立门或晶体管逻辑器件、分立硬件组件。通用处理器可以是微处理器或任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或用处理器中的硬件及软件单元组合执行完成。处理器1120用于实现上述方法所执行的程序代码可以存储在存储器1130中。存储器1130和处理器1120耦合。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性、机械或其它的形式，用于装置、单元或模块之间的信息交互。处理器1120可能和存储器1130协同操作。存储器1130可以是非易失性存储器，比如硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)等，还可以是易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)。存储器1130是能够用于携带或存储具有指令或数据结构形式的程序代码并能够由计算机存取的任何其他介质，但不限于此。
本申请实施例中不限定上述通信接口1110、处理器1120以及存储器1130之间的具体连接介质。本申请实施例在图11中以存储器1130、处理器1120以及通信接口1110之间通过总线连接。总线在图11中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图11中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
基于以上实施例，本申请实施例还提供了一种计算机存储介质，该存储介质中存储软件程序，该软件程序在被一个或多个处理器读取并执行时可实现上述任意一个或多个实施例提供的方法。所述计算机存储介质可以包括：U盘、移动硬盘、只读存储器、随机存取存储器等各种可以存储程序代码的介质。
基于以上实施例，本申请实施例还提供了一种芯片。该芯片包括处理器，用于实现上述任意一个或多个实施例所涉及的功能，例如获取或处理上述方法中所涉及的数据帧。可选地，所述芯片还包括存储器，所述存储器，用于处理器所执行必要的程序指令和数据。该芯片，可以由芯片构成，也可以包含芯片和其他分立器件。
本领域内的技术人员应明白，本申请的实施例可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。或者，这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流 程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请实施例的范围。这样，倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (12)

  1. 一种告警处理方法，其特征在于，包括：
    第二网络设备检测到第一工作通道出现LOF预告警；所述第一工作通道用于连通所述第二网络设备和第一网络设备；
    其中，所述LOF预告警的检测条件为对来自所述第一网络设备的数据帧进行定帧失败持续第一时长，所述第一时长小于LOF告警的检测条件中的定帧失败持续时长；
    所述第二网络设备在入口端下插第一维护信号帧，所述入口端用于通过第一工作通道接收来自所述第一网络设备的数据帧，所述第一维护信号帧用于定帧。
  2. 如权利要求1所述的方法，其特征在于，还包括：
    所述第二网络设备检测到所述第一工作通道出现LOF告警时，终止在所述入口端下插所述第一维护信号帧，并在所述入口端下插告警指示信号AIS帧。
  3. 如权利要求1所述的方法，其特征在于，所述第一网络设备和所述第二网络设备均配置有子网连接保护组，所述方法还包括：
    所述第二网络设备检测到所述第一工作通道出现LOF告警，触发所述第二网络设备的子网连接保护组倒换，并在第三时长内在入口端下插所述第一维护信号帧；所述第三时长为检测到LOF告警后延迟下插AIS帧的时长，所述第三时长大于或者等于第二网络设备完成子网连接保护组倒换的时长。
  4. 如权利要求1-3任一项所述的方法，其特征在于，所述第一维护信号帧为空NULL类型维护信号，所述第一维护信号帧的开销包括第一值；所述第一值用于指示所述第一维护信号帧为空NULL类型维护信号。
  5. 如权利要求4所述的方法，其特征在于，所述开销为通道监控PM段开销或者串联连接监控TCM段开销。
  6. 一种告警处理方法，其特征在于，包括：
    第三网络设备检测到第二工作通道出现LOF预告警；所述第二工作通道用于连通所述第三网络设备和第二网络设备；
    其中，所述LOF预告警的检测条件为对来自所述第二网络设备的数据帧进行定帧失败持续第一时长；
    所述第三网络设备检测到第二工作通道出现LOF告警之前，通过所述第二工作通道接收到来自第二网络设备的第一维护信号帧；
    其中，所述第一维护信号帧用于定帧；所述LOF告警的检测条件为对来自所述第二网络设备的数据帧进行定帧失败持续第二时长，所述第二时长大于所述第一时长。
  7. 如权利要求6所述的方法，其特征在于，还包括：
    所述第三网络设备通过所述第二工作通道接收到来自所述第二网络设备的第一维护信号帧后，通过所述第二工作通道接收到来自所述第二网络设备的告警指示信号AIS帧；
    所述第三网络设备上报AIS告警。
  8. 如权利要求6所述的方法，其特征在于，第二网络设备和所述第三网络设备均配置有子网连接保护组，所述方法还包括：
    所述第三网络设备通过所述第二工作通道接收到来自所述第二网络设备的第一维护 信号帧后，通过所述第二工作通道接收到来自所述第二网络设备的AIS帧；
    所述第三网络设备触发子网连接保护组倒换，并上报AIS告警。
  9. 如权利要求6-8任一项所述的方法，其特征在于，所述第一维护信号帧为空NULL类型维护信号，所述第一维护信号帧的开销包括第一值；所述第一值指示所述第一维护信号帧为NULL类型维护信号。
  10. 如权利要求9所述的方法，其特征在于，所述开销为PM段开销或者TCM段开销。
  11. 一种告警处理装置，其特征在于，包括处理器以及存储器，其中：
    所述存储器，用于存储程序代码；
    所述处理器，用于读取并执行所述存储器存储的程序代码，以实现如权利要求1～10任一项所述的方法。
  12. 一种芯片，其特征在于，所述芯片与存储器相连，用于读取并执行所述存储器中存储的程序代码，以实现如权利要求1至10任一项所述的方法。
PCT/CN2021/096367 2020-06-02 2021-05-27 一种告警处理方法及装置 Ceased WO2021244390A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
KR1020227045362A KR102728462B1 (ko) 2020-06-02 2021-05-27 경보 처리 방법 및 장치
BR112022024367A BR112022024367A2 (pt) 2020-06-02 2021-05-27 Método e aparelho de processamento de alarme
EP21818908.2A EP4152694B1 (en) 2020-06-02 2021-05-27 Alarm processing method and apparatus
CA3185692A CA3185692A1 (en) 2020-06-02 2021-05-27 Alarm processing method and apparatus
US18/060,913 US12375173B2 (en) 2020-06-02 2022-12-01 Alarm processing method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010488897.2 2020-06-02
CN202010488897.2A CN113765725A (zh) 2020-06-02 2020-06-02 一种告警处理方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/060,913 Continuation US12375173B2 (en) 2020-06-02 2022-12-01 Alarm processing method and apparatus

Publications (1)

Publication Number Publication Date
WO2021244390A1 true WO2021244390A1 (zh) 2021-12-09

Family

ID=78782741

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/096367 Ceased WO2021244390A1 (zh) 2020-06-02 2021-05-27 一种告警处理方法及装置

Country Status (7)

Country Link
US (1) US12375173B2 (zh)
EP (1) EP4152694B1 (zh)
KR (1) KR102728462B1 (zh)
CN (1) CN113765725A (zh)
BR (1) BR112022024367A2 (zh)
CA (1) CA3185692A1 (zh)
WO (1) WO2021244390A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115499862B (zh) * 2022-09-08 2025-01-28 重庆长安汽车股份有限公司 一种数据异常识别方法、装置、设备及存储介质
CN115526489A (zh) * 2022-09-28 2022-12-27 中国电信股份有限公司 一种信息处理方法、装置、电子设备及存储介质
CN120512617A (zh) * 2024-02-18 2025-08-19 华为技术有限公司 一种光传送网的保护倒换的方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6892336B1 (en) * 2000-03-17 2005-05-10 Applied Micro Circuits Corporation Gigabit ethernet performance monitoring
US20070058572A1 (en) * 2004-06-21 2007-03-15 Rolf Clauberg Multi-ring resilient packet ring add/drop device
CN102158354A (zh) * 2011-03-04 2011-08-17 烽火通信科技股份有限公司 防止同步数字体系设备段层缺陷透传的方法
CN102480780A (zh) * 2010-11-26 2012-05-30 上海贝尔股份有限公司 毫微微基站路由器的时间同步方法及系统
CN104580031A (zh) * 2015-01-28 2015-04-29 中国人民解放军国防科学技术大学 基于多协议链路封装技术的pos解帧成帧装置及方法

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH07264223A (ja) * 1994-03-18 1995-10-13 Fujitsu Ltd ネットワークの信号救済方法および装置
IT1289816B1 (it) * 1996-12-30 1998-10-16 Sip Dispositivo di interfacciamento per reti di tipo atm
US20010046074A1 (en) * 2000-05-25 2001-11-29 Sunao Kakizaki Protection switching apparatus for 1 + 1 optical transmission lines
US6839871B2 (en) * 2001-02-08 2005-01-04 Sycamore Networks, Inc. Method for transparent multiplexing of SONET/ SDH streams
JP3825674B2 (ja) * 2001-10-24 2006-09-27 富士通株式会社 伝送装置，ｓｏｎｅｔ／ｓｄｈ伝送装置および伝送システム
US6999480B2 (en) * 2001-11-26 2006-02-14 Applied Micro Circuits Corporation Method and apparatus for improving data integrity and desynchronizer recovery time after a loss of signal
US7826345B2 (en) * 2003-07-08 2010-11-02 Sycamore Networks, Inc. Network span protection using span identifiers
WO2006081150A2 (en) * 2005-01-21 2006-08-03 Raza Microelectronics, Inc. System and method for performing concatenation of diversely routed channels
US9071361B2 (en) * 2006-10-13 2015-06-30 Menara Networks, Inc. Extended reach XFP transceiver with integrated forward error correction
CN101345700B (zh) * 2007-07-10 2011-12-07 华为技术有限公司 将以太网编码块映射到光传输网络传输的方法及装置
CN101414932B (zh) * 2007-10-15 2012-09-05 华为技术有限公司 长距离无源光网络系统中告警管理的方法、系统及装置
JP2009141616A (ja) * 2007-12-05 2009-06-25 Oki Electric Ind Co Ltd 符号分割多重送受信システム
US8934769B2 (en) * 2009-11-25 2015-01-13 Telefonaktiebolaget L M Ericsson (Publ) Optical transport network alarms
US8356233B2 (en) * 2010-05-19 2013-01-15 Ciena Corporation Pseudo-noise insertion on unacceptable input data sequence in optical networks
JP2013038578A (ja) * 2011-08-08 2013-02-21 Fujitsu Ltd 光ネットワーク装置
US10044457B2 (en) * 2013-04-23 2018-08-07 Ciena Corporation Preventing invalid defect detection during OTN out-of-frame states
US20160226578A1 (en) * 2015-02-04 2016-08-04 Catherine H. Yuan Management of frame alignment events in optical transport networks
EP3429138B1 (en) * 2016-04-08 2024-11-27 Huawei Technologies Co., Ltd. Fault detection method and apparatus
US10193765B2 (en) * 2016-05-19 2019-01-29 Ciena Corporation Protection switching systems and methods in a packet network based on signal degrade
US10097262B2 (en) * 2016-11-30 2018-10-09 Ciena Corporation Client protection switch in optical pluggable transceivers activated through fast electrical data squelch

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6892336B1 (en) * 2000-03-17 2005-05-10 Applied Micro Circuits Corporation Gigabit ethernet performance monitoring
US20070058572A1 (en) * 2004-06-21 2007-03-15 Rolf Clauberg Multi-ring resilient packet ring add/drop device
CN102480780A (zh) * 2010-11-26 2012-05-30 上海贝尔股份有限公司 毫微微基站路由器的时间同步方法及系统
CN102158354A (zh) * 2011-03-04 2011-08-17 烽火通信科技股份有限公司 防止同步数字体系设备段层缺陷透传的方法
CN104580031A (zh) * 2015-01-28 2015-04-29 中国人民解放军国防科学技术大学 基于多协议链路封装技术的pos解帧成帧装置及方法

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
EP4152694B1 (en) 2026-03-25
CN113765725A (zh) 2021-12-07
US20230096052A1 (en) 2023-03-30
CA3185692A1 (en) 2021-12-09
BR112022024367A2 (pt) 2022-12-27
KR102728462B1 (ko) 2024-11-13
KR20230015990A (ko) 2023-01-31
US12375173B2 (en) 2025-07-29
EP4152694A4 (en) 2023-11-08
EP4152694A1 (en) 2023-03-22

Similar Documents

Publication Publication Date Title
US10826604B2 (en) Fault localization using tandem connection monitors in optical transport network
US10601537B2 (en) Fault propagation in segmented protection
JP5073812B2 (ja) 分散型イーサネットシステムおよび該システムに基づいて障害を検出する方法
US9237092B2 (en) Method, apparatus, and system for updating ring network topology information
US12375173B2 (en) Alarm processing method and apparatus
KR102582988B1 (ko) 플렉시블 이더넷 통신 방법 및 네트워크 장치
CN101499820B (zh) 业务传输的保护方法和网络设备
US10091023B2 (en) Systems and methods to detect and recover from a loop in an Ethernet ring protected network
EP2466785B1 (en) Method, optical communication device and system for processing information in optical network
US7710864B2 (en) Recovery mechanism for 10 GE optical transport network wavelength division multiplexing ring
WO2020199421A1 (zh) 一种双归保护方法、接入节点、设备及通信网络
CN104158586B (zh) 一种倒换实现方法、站点及系统
WO2016197881A1 (zh) 一种网络保护的方法、网络节点及系统
JP7163508B2 (ja) フレキシブルイーサネット通信方法とネットワークデバイス
US20100128596A1 (en) Transmission apparatus
CN100377506C (zh) 防错连的方法
EP4601219A1 (en) Device, method, apparatus and medium for optical channel protection
US11881890B2 (en) Electrical layer subnetwork connection protection method, apparatus, and system
WO2025171726A1 (zh) 一种光传送网的保护倒换的方法及装置
CN120390165A (zh) 光通信系统、sncp倒换方法及相关设备
CN121056071A (zh) 一种通信方法、通信装置以及计算机可读存储介质
US8712235B2 (en) Transmission apparatus and network protection method

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 3185692

Country of ref document: CA

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112022024367

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 20227045362

Country of ref document: KR

Kind code of ref document: A

Ref document number: 2021818908

Country of ref document: EP

Effective date: 20221213

ENP Entry into the national phase

Ref document number: 112022024367

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20221129

NENP Non-entry into the national phase

Ref country code: DE

WWG Wipo information: grant in national office

Ref document number: 2021818908

Country of ref document: EP