Method for implementation of segmented monitoring, network node and computer-readable storage medium

Abstract

The present application provides a method for implementation of segmented monitoring, a network node, and a computer-readable storage medium. The method comprises: using segmented monitoring information to perform OAM processing on a segmented monitoring section, the segmented monitoring information being indicated by means of a type value. The method implements segmented and / or layered monitoring and protection.

Description

Implementation method of segmented monitoring, network nodes and computer-readable storage media Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method for implementing segmented monitoring, a network node, and a computer-readable storage medium. Background Technology

[0002] Metro Transport Networks (MTN) / Slicing Packet Networks (SPN) are transport network technologies designed for integrated service delivery, primarily supporting high-quality services such as mobile midhaul / backhaul, leased lines / private networks, etc. Fine Grain MTN (fgMTN) / Fine Granularity SPN (fgSPN) performs fine-grained bandwidth resource slicing on the physical network, thereby providing differentiated service capabilities for various services.

[0003] When using MTN / SPN (including fine-grained MTN / SPN) to carry customer services, in order to perform fault detection and performance management on the service channels carrying customer services, Operation, Administration and Maintenance (OAM) functions for the carrying channels are formulated. The OAM mechanism is used to monitor and manage the connectivity, packet loss rate, bit error rate, latency and other attributes of the channels.

[0004] However, current MTN / SPN (including fine-grained MTN / SPN) can only achieve end-to-end OAM functionality at the channel layer. Summary of the Invention

[0005] This application provides a method for implementing segmented monitoring, a network node, and a computer-readable storage medium.

[0006] In a first aspect, embodiments of this application provide a method for implementing segmented monitoring, including:

[0007] OAM processing for segmented monitoring segments is performed using segmented monitoring information;

[0008] The segmented monitoring information is indicated by a type value.

[0009] Secondly, embodiments of this application provide a method for implementing segmented monitoring, employing at least one of the following methods for fault handling:

[0010] First signal;

[0011] Segmented monitoring information;

[0012] Second signal;

[0013] The first signal is sent when a fault occurs in the segmented monitoring segment, and the second signal is sent when a fault occurs in the non-segmented monitoring segment.

[0014] Thirdly, embodiments of this application provide a network node, including: a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the segmented monitoring implementation method provided in the first and second aspects of embodiments of this application.

[0015] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the segmented monitoring method provided in the first and second aspects of embodiments of this application.

[0016] Further details regarding the above embodiments and other aspects of this application, as well as their implementations, are provided in the accompanying drawings, detailed description, and claims. Attached Figure Description

[0017] Figure 1 is a flowchart illustrating a segmented monitoring implementation method provided in an embodiment of this application;

[0018] Figure 2 is a schematic diagram of a segmented monitoring method provided in an embodiment of this application;

[0019] Figure 3 is a schematic diagram of a single-layer segmented monitoring scenario provided in an embodiment of this application;

[0020] Figure 4 is a schematic diagram of a segmented monitoring information insertion method provided in an embodiment of this application;

[0021] Figure 5 is a schematic diagram of the segmented monitoring information of MTN in a single-layer segmented monitoring scenario provided in an embodiment of this application;

[0022] Figure 6 is a schematic diagram of the segmented monitoring information of SPN in a single-layer segmented monitoring scenario provided in an embodiment of this application;

[0023] Figure 7 is another structural schematic diagram of the segmented monitoring information of MTN in a single-layer segmented monitoring scenario provided in the embodiments of this application;

[0024] Figure 8 is another structural schematic diagram of the segmented monitoring information of SPN in a single-layer segmented monitoring scenario provided in the embodiments of this application;

[0025] Figure 9 is a schematic diagram of a segmented monitoring information block of MTN in a single-layer segmented monitoring scenario provided in an embodiment of this application;

[0026] Figure 10 is a schematic diagram of a segmented monitoring information block of SPN in a single-layer segmented monitoring scenario provided in an embodiment of this application;

[0027] Figure 11 is a schematic diagram of a multi-layer segmented monitoring scenario provided in an embodiment of this application;

[0028] Figure 12 is a schematic diagram of the segmented monitoring information of MTN in a multi-layer segmented monitoring scenario provided in an embodiment of this application;

[0029] Figure 13 is a schematic diagram of the segmented monitoring information of SPN in a multi-layer segmented monitoring scenario provided in an embodiment of this application;

[0030] Figure 14 is a schematic diagram of a segmented monitoring information block of MTN in a multi-layer segmented monitoring scenario provided in an embodiment of this application.

[0031] Figure 15 is a schematic diagram of a segmented monitoring information block of SPN in a multi-layer segmented monitoring scenario provided in an embodiment of this application.

[0032] Figure 16 is a schematic diagram of a fault scenario provided in an embodiment of this application;

[0033] Figure 17 is a schematic diagram of a structure of an LF block provided in an embodiment of this application;

[0034] Figure 18 is a schematic diagram of an Error block and an Idle block provided in an embodiment of this application;

[0035] Figure 19 is a schematic diagram of a segmented monitoring and maintenance block of MTN in a single-layer segmented monitoring scenario provided in an embodiment of this application.

[0036] Figure 20 is a schematic diagram of a segmented monitoring and maintenance block of SPN in a single-layer segmented monitoring scenario provided in an embodiment of this application.

[0037] Figure 21 is a schematic diagram of a second code block in a single-layer segmented monitoring scenario provided in an embodiment of this application;

[0038] Figure 22 is a schematic diagram of a fault handling method in a single-layer segmented monitoring scenario provided in an embodiment of this application;

[0039] Figure 23 is another schematic diagram of a fault handling method in a single-layer segmented monitoring scenario provided in the embodiments of this application;

[0040] Figure 24 is another schematic diagram of a fault handling method in a single-layer segmented monitoring scenario provided in the embodiments of this application;

[0041] Figure 25 is a schematic diagram of another fault scenario provided in an embodiment of this application;

[0042] Figure 26 is a schematic diagram of a segmented monitoring and maintenance block of MTN in a multi-layer segmented monitoring scenario provided in an embodiment of this application;

[0043] Figure 27 is a schematic diagram of a segmented monitoring and maintenance block of SPN in a multi-layer segmented monitoring scenario provided in an embodiment of this application.

[0044] Figure 28 is a schematic diagram of a second code block in a multi-layer segmented monitoring scenario provided in an embodiment of this application;

[0045] Figure 29 is a schematic diagram of a fault handling method in a multi-layer segmented monitoring scenario provided in an embodiment of this application;

[0046] Figure 30 is another schematic diagram of a fault handling method in a multi-layer segmented monitoring scenario provided in the embodiments of this application;

[0047] Figure 31 is another schematic diagram of a fault handling method in a multi-layer segmented monitoring scenario provided by an embodiment of this application;

[0048] Figure 32 is a schematic diagram of a segmented monitoring implementation device provided in an embodiment of this application;

[0049] Figure 33 is a schematic diagram of another structure of the segmented monitoring implementation device provided in the embodiment of this application;

[0050] Figure 34 is a schematic diagram of a network node structure provided in an embodiment of this application. Detailed Implementation

[0051] It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application. The embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0052] Currently, the OAM function of MTN / SPN can achieve end-to-end monitoring of customer services. However, in practical applications, facing scenarios such as large-scale network cross-regional, multi-vendor interconnection, and cross-domain networks, end-to-end OAM monitoring cannot achieve segmented and / or layered monitoring and protection. To address this, the technical solution provided in this application inserts segmented monitoring information (or Tandem Connection Monitoring (TCM)) into the customer's service data stream, and uses the inserted segmented monitoring information to perform segmented monitoring layer (i.e., segmented and / or layered) OAM monitoring and protection.

[0053] Figure 1 is a flowchart illustrating a segmented monitoring implementation method provided in an embodiment of this application. As shown in Figure 1, the method may include:

[0054] S101. Use segmented monitoring information to perform OAM processing for segmented monitoring segments.

[0055] Segmented monitoring information is inserted into the customer's business data stream for segmented monitoring segment OAM processing. The segmented monitoring information is indicated by a type value and is the OAM information of the segmented monitoring layer.

[0056] Optionally, the segmented monitoring information may include at least one of the following:

[0057] a) Basic information, such as path status and error monitoring.

[0058] b. Monitoring information, such as remote error indication, remote defect indication, customer signal failure, etc.

[0059] c. Automatic Protection Switching (APS) information, such as protection switching requests / status, protection type, etc.

[0060] d. Delay measurement information, such as one-way delay measurement, two-way delay measurement, etc.

[0061] e. Verification information, such as Cyclic Redundancy Check (CRC) and Bit Interleaved Parity (BIP).

[0062] f. Segmented monitoring segment status: This indicates the status of the segmented monitoring segment / segmented monitoring layer, such as normal status, maintenance signals of the segmented monitoring layer, such as Alarm Indication Signal (AIS) and Open Connection Indication (OCI). AIS indicates a signal fault, while OCI indicates that the output connection point in the uplink connection function is not connected to the input connection point, meaning there is no network connection.

[0063] g. Customer signal status indicator, used to indicate the status of customer signals, such as segmented monitoring AIS, segmented monitoring OCI, etc.

[0064] h, Segmented monitoring sublayer indicator, used to indicate segmented monitoring sublayers.

[0065] Alternatively, different segmented monitoring information can be indicated by different type values.

[0066] Optionally, the above-mentioned segmented monitoring information may also be segmented monitoring information blocks, which are frames or multiframes composed of at least one 66-bit block, and each frame in the multiframe is indicated by the same type value.

[0067] Optionally, the above-mentioned segmented monitoring function can perform layered monitoring and protection. When monitoring non-overlapping segments, one layer of segmented monitoring information can be used; when monitoring overlapping segments, i.e., nested segments, segmented monitoring information from different sub-layers can be used.

[0068] As shown in Figure 2, A and G are the starting points (endpoints) of the service, and B, C, D, E, and F are the intermediate nodes of the service. Segmented monitoring can be performed in each sub-layer. For example, in sub-layer 1, BD and EF are different cross-segment monitoring. Since the segmented monitoring information 1 of sub-layer 1 has ended at point D, it can be used again in the EF segment for monitoring. At this time, if a fault occurs in the BD segment, the segmented monitoring information 1 of sub-layer 1 will trigger an alarm and / or protection switching, without affecting the EF segment. When monitoring BD and BE, because there is an overlapping cross-segment BD, different segmented monitoring sub-layers are used for monitoring, namely segmented monitoring sub-layer 1 and segmented monitoring sub-layer 2. Similarly, when monitoring BD, BE, and AG, because there is an overlapping cross-segment BD, different segmented monitoring sub-layers are used for monitoring, namely segmented monitoring sub-layer 1, segmented monitoring sub-layer 2, and segmented monitoring sub-layer 3.

[0069] The following describes single-segment and multi-segment monitoring scenarios:

[0070] For a segmented monitoring scenario at the first layer, as shown in Figure 3, A and G are the starting points of the service, respectively, and end-to-end OAM monitoring is configured, while segmented monitoring is configured at BD.

[0071] At point A, customer services are 64 / 66 encoded into data blocks. The MTN channel inserts a Path Monitoring (PM) OAM block into the transmitted data block before transmission (the inserted OAM block is not shown in Figure 3). When the data stream reaches point B, point B inserts segmented monitoring information into the data stream and then continues transmission to the next node. The insertion method can be as shown in Figure 4. This embodiment does not limit the insertion method of segmented monitoring information. The segmented monitoring information is a 66-bit block structure, indicated by a type value (Type field value) to distinguish end-to-end OAM monitoring. In MTN, the segmented monitoring information format is shown in Figure 5, for example, indicated by a Type field value; in SPN, the segmented monitoring information format is shown in Figure 6, for example, indicated by a Type field value.

[0072] Optionally, the above-mentioned segmented monitoring information may include at least one of the following:

[0073] Basic information, monitoring information, protection switching information, time delay measurement information, verification information, segmented monitoring segment status, and customer signal status indication.

[0074] The indication of the aforementioned segmented monitoring information may include the following methods:

[0075] Method 1: Different types of monitoring information are indicated by different type values.

[0076] For example, as shown in Figure 7, in MTN, the type value (i.e., the Type field value) "100001" represents the basic information (BAS information) used for segmented monitoring, and the type value "100010" represents the APS information used for segmented monitoring. Both the BAS information and the APS information can include the status information of the segmented monitoring segment.

[0077] For example, as shown in Figure 8, the SPN uses the type value "0x3" to represent BAS information used for segmented monitoring and the type value "0x4" to represent APS information used for segmented monitoring. Both BAS information and APS information can include the status information of the segmented monitoring segment.

[0078] Method 2: The above segmented monitoring information can also be segmented monitoring information blocks, which are frames or multiframes composed of at least one 66-bit block, and each frame in the multiframe is indicated by the same type value.

[0079] For example, as shown in Figure 9, in MTN, the type value "100001" represents a segmented monitoring information block. This segmented monitoring information block is formatted as a multiframe consisting of three 66-bit blocks, including monitoring information, protection switching information (APS information), verification information, and segmented monitoring status. Each frame in the multiframe is represented by the field values ​​of the Start of Message (SOM) and End of Message (EOM) fields. For example, 10 represents the first frame of the multiframe, 00 represents a non-first or final frame (i.e., an intermediate frame), and 01 represents the last frame of the multiframe. The position of the segmented monitoring information in each frame can be adjusted according to actual needs, and the segmented monitoring information in each frame can be expanded based on actual requirements.

[0080] For example, as shown in Figure 10, in SPN, the Type field value "0x3" represents a segmented monitoring information block. This segmented monitoring information block is formatted as a multiframe consisting of two 66-bit blocks, including monitoring information, protection switching information (APS information), verification information, and segmented monitoring segment status. Each frame in the multiframe can be represented by a Seq sequence number; for example, Seq sequence number "0x0" represents the first frame of the multiframe, Seq sequence number "0x1" represents the second frame, and so on. The location of the segmented monitoring information within each frame can be adjusted according to actual needs, and the segmented monitoring information within each frame can be expanded based on actual requirements.

[0081] When the data stream reaches point D, point D serves as the endpoint of segmented monitoring. The segmented monitoring information is identified through the type value. Based on the obtained segmented monitoring information (such as monitoring information, protection switching information, and segmented monitoring status), OAM processing is performed, and the segmented monitoring information is terminated, allowing the data stream to continue to be transmitted to downstream nodes.

[0082] For multi-level segmented monitoring scenarios, as shown in Figure 11, A and G are the starting points of the business, respectively. Segmented monitoring sub-layer 1 is configured in BD, and segmented monitoring sub-layer 2 is configured in AG.

[0083] At point A, customer services are 64 / 66 encoded into data blocks. The MTN channel inserts segment monitoring information 2 (or TCM2; Figure 11 only shows TCM2 as an example, and there are no restrictions on the segment monitoring information here) into the transmitted data blocks before transmission. When the data stream reaches point B, point B inserts segment monitoring information 1 (or TCM1; Figure 11 only shows TCM1 as an example) into the data stream and continues transmission. The insertion method can be shown in Figure 4. The segment monitoring information is a 66-bit block structure, indicated by a type value (Type field value). In MTN, the segment monitoring information format is shown in Figure 5; in SPN, the segment monitoring information format is shown in Figure 6. Based on the aforementioned two methods of indicating segment monitoring information, sub-layer segment monitoring indicators can be added in multi-layer segment monitoring scenarios to indicate the segment monitoring sub-layer.

[0084] Optionally, the above-mentioned segmented monitoring information may include at least one of the following:

[0085] Basic information, monitoring information, protection switching information, delay measurement information, verification information, segmented monitoring segment status, customer signal status indication, and segmented monitoring sub-layer indication.

[0086] The indication of the aforementioned segmented monitoring information may include the following methods:

[0087] Method 1: Different types of monitoring information are indicated by different type values.

[0088] For example, as shown in Figure 12, in MTN, the type values ​​"100001" and "100010" represent BAS information and APS information used for segmented monitoring, respectively. The Sub field value is used to indicate the segmented monitoring sub-layer. For example, the Sub field value "0" represents segmented monitoring sub-layer 1 (or TCM1), and the Sub field value "1" represents segmented monitoring sub-layer 2 (or TCM2). That is, when Type=100001 and Sub=0, it means that this 66B block carries the BAS information of segmented monitoring sub-layer 1; when Type=100010 and Sub=1, it means that this 66B block carries the APS information of segmented monitoring sub-layer 2.

[0089] For example, as shown in Figure 13, in SPN, the type values ​​"0x3" and "0x4" represent BAS information and APS information used for segmented monitoring, respectively. The Sub field value is used to indicate the segmented monitoring sub-layer. For example, the Sub field value "0" represents segmented monitoring sub-layer 1 (or TCM1), and the Sub field value "1" represents segmented monitoring sub-layer 2 (or TCM2). That is, when Type=0x3 and Sub=0, it means that this 66B block carries the BAS information of segmented monitoring sub-layer 1; when Type=0x4 and Sub=1, it means that this 66B block carries the APS information of segmented monitoring sub-layer 2.

[0090] Alternatively, more layers of segmented monitoring can be supported by extending the Type field value or bit value. For example, some bits in the Type field can be used to indicate segmented monitoring sub-layers, such as 2 bits can identify 4 segmented monitoring sub-layers.

[0091] Method 2: The above segmented monitoring information can also be segmented monitoring information blocks, which are frames or multiframes composed of at least one 66-bit block, and each frame in the multiframe is indicated by the same type value.

[0092] For example, as shown in Figure 14, in MTN, the Type value "100001" represents a segmented monitoring information block. This segmented monitoring information block is formatted as a multiframe consisting of three 66-bit blocks, including segmented monitoring sublayer indication, monitoring information, protection switching information, check information, and segmented monitoring segment status. Each frame in the multiframe is represented by field values ​​in the SOM and EOM fields. For example, 10 represents the first frame of the multiframe, 00 represents a non-first or final frame (i.e., an intermediate frame), 01 represents the last frame of the multiframe, Sub=0 indicates that this multiframe is a segmented monitoring information block of segmented monitoring sublayer 1, and Sub=1 indicates that this multiframe is a segmented monitoring information block of segmented monitoring sublayer 2. The position of the segmented monitoring information in each frame can be adjusted according to actual needs, and the segmented monitoring information in each frame can be expanded based on actual requirements.

[0093] For example, as shown in Figure 15, in SPN, the Type value "0x3" represents a segmented monitoring information block. This segmented monitoring information block is formatted as a multiframe consisting of two 66-bit blocks, including segmented monitoring sublayer indication, monitoring information, protection switching information, check information, and segmented monitoring segment status. Each frame in the multiframe can be represented by a Seq sequence number. For example, Seq sequence number "0x0" represents the first frame of the multiframe, Seq sequence number "0x1" represents the second frame, Sub=0 indicates that this multiframe is a segmented monitoring information block of segmented monitoring sublayer 1, and Sub=1 indicates that this multiframe is a segmented monitoring information block of segmented monitoring sublayer 2. The position of the segmented monitoring information contained in each frame can be adjusted according to actual conditions, and the segmented monitoring information contained in each frame can be expanded based on actual needs.

[0094] Alternatively, more layers of segmented monitoring can be supported by extending the Type field value or bit value. For example, some bits in the Type field can be used to indicate segmented monitoring sub-layers, such as 2 bits can identify 4 segmented monitoring sub-layers.

[0095] When the data stream reaches point D, point D, as the end node of segmented monitoring segment 1, identifies the segmented monitoring information block of segmented monitoring sub-layer 1 through the Type value and segmented monitoring sub-layer indication. Based on the obtained segmented monitoring information of segmented monitoring sub-layer 1 (such as monitoring information, protection switching information, segmented monitoring segment status, etc.), it performs OAM processing on segment BD and terminates segmented monitoring information 1 (here, the segmented monitoring information of segmented monitoring sub-layer 1 is referred to as segmented monitoring information 1), and continues to transmit the data stream to downstream nodes.

[0096] When the data stream reaches point G, G, as the terminal node of segmented monitoring segment 2, identifies the segmented monitoring information block of segmented monitoring sublayer 2 through the Type value and segmented monitoring sublayer indication. Based on the obtained segmented monitoring information of segmented monitoring sublayer 2 (such as monitoring information, protection switching information, segmented monitoring segment status, etc.), it performs OAM processing on the AG segment and terminates segmented monitoring information 2 (here, the segmented monitoring information of segmented monitoring sublayer 2 is referred to as segmented monitoring information 2). At the same time, point G, as the service terminal point, processes the service data normally.

[0097] In this embodiment, segmented and / or layered monitoring and protection are achieved by inserting segmented monitoring M information into the customer's business data stream.

[0098] For a single-layer segmented monitoring scenario, the following describes two fault scenarios as examples: non-segmented monitoring segment faults and segmented monitoring segment faults.

[0099] As shown in Figure 16, when a fault occurs in point AB of the non-segmented monitoring segment, point B sends a maintenance signal (such as AIS / OCI). Because point B is the starting node of the segmented monitoring segment, it inserts segmented monitoring information (or TCM; Figure 16 only shows TCM information as an example and does not impose any restrictions) into the AIS / OCI (i.e., replacing the corresponding maintenance signal block with segmented monitoring information). At the end node D of the segmented monitoring segment, point D identifies the segmented monitoring information through the Type value, terminates the segmented monitoring information, and continues to transmit AIS / OCI downstream. Since the fault occurs in the non-segmented monitoring segment, point D should not generate an alarm or operation at the segmented monitoring layer. However, according to the existing MTN / SPN technology, point D will first detect the AIS / OCI, and trigger an alarm upon confirming receipt of the AIS / OCI, but this is not actually a fault in the segmented monitoring segment BD, thus leading to incorrect fault location.

[0100] When a fault occurs in segmented monitoring section BC, point C detects the fault and sends a maintenance signal (such as AIS / OCI) to point D. When point D detects the AIS / OCI, it triggers corresponding operations (such as alarms, protection switching, etc.). However, point D does not know whether the fault occurred in the segmented monitoring section or the upstream non-segmented monitoring section.

[0101] Here, AIS stands for Signal Fault, and its structure is a series of Local Fault (LF) blocks (as shown in Figure 17). At the receiver, the received signal may also include Idle blocks inserted through a rate adaptation process. If the receiver receives more than four LF blocks within a 128-block interval of 66B blocks, it determines that AIS has been detected (dAIS); if no LF blocks are received within a 128-block interval of 66B blocks, dAIS is cleared.

[0102] OCI (Optical Characteristic) indicates that the output connection point in an uplink connection function is not connected to the input connection point, meaning no network connection exists. The structure of OCI is a repeating sequence of 32 66B blocks, consisting of 31 error blocks ( / E / ) and 1 idle block ( / I / ), as shown in Figure 18. At the receiver, due to rate adaptation in adding and removing idle blocks, the received signal may have different combinations. If more than 6144 / E / are received out of 8192 66B blocks, an OCI (dOCI) is detected; if fewer than 128 / E / are received out of 8192 66B blocks, the dOCI is cleared.

[0103] To address the aforementioned fault scenarios, the fault handling method provided in this application embodiment can resolve the problem of fault location errors. Specifically, one of the following methods can be used for fault handling:

[0104] Method 1: First signal.

[0105] The first signal is sent when a fault occurs in the segmented monitoring segment.

[0106] Optionally, the first signal is used as a trigger condition for fault handling in the segmented monitoring segment. Specifically, upon detecting the first signal, fault handling in the segmented monitoring segment is triggered.

[0107] That is, when a fault occurs in a segmented monitoring segment, a first signal can be sent. If the first signal is detected at the end node of the segmented monitoring segment, fault handling for the segmented monitoring segment is triggered; if the first signal is not detected, fault handling for the segmented monitoring segment is not triggered. In this way, segmented fault location can be achieved.

[0108] Optionally, the fault handling method for the segmented monitoring segment may include:

[0109] If a protection path exists for the segmented monitoring section, protection switching is performed, receiving and sending service data streams from the protection path. If no protection path exists for the segmented monitoring section, an alarm is triggered, and a maintenance signal is sent. The maintenance signal can be AIS / OCI, etc.

[0110] Optionally, the first signal includes one of the following: a repeating sequence of the segmented monitoring and maintenance block, a repeating sequence of the combination of the segmented monitoring and maintenance block and the first code block, and a repeating sequence of the second code block.

[0111] Optionally, the first code block may include at least one of the following: an LF block, an Idle block, and an Error block. The structure of the LF block can be as shown in Figure 17, and the structures of the Idle block and the Error block can be as shown in Figure 18.

[0112] Optionally, the segmented monitoring and maintenance block may include at least one of the following: a type value for identifying the segmented monitoring layer and the signal type of the segmented monitoring layer (e.g., the maintenance signal or fault signal type of the segmented monitoring layer, such as segmented monitoring AIS, segmented monitoring OCI, etc.).

[0113] For example, the first signal can be a repeating sequence of the segmented monitoring and maintenance block, a repeating sequence of the segmented monitoring and maintenance block and the LF block, a repeating sequence of the segmented monitoring and maintenance block and the Idle block, a repeating sequence of the segmented monitoring and maintenance block and the Error block, or a repeating sequence of the segmented monitoring and maintenance block with any combination of the LF block, the Idle block, and the Error block. The segmented monitoring status field in the segmented monitoring and maintenance block can indicate the signal type of the segmented monitoring layer. For example, 2 bits can be used to indicate the signal type of the segmented monitoring layer, such as 01 for segmented monitoring AIS and 10 for segmented monitoring OCI.

[0114] For example, the segmented monitoring and maintenance block of MTN is shown in Figure 19, and the segmented monitoring and maintenance block of SPN is shown in Figure 20. Of course, a single segmented monitoring and maintenance block structure can also be used uniformly.

[0115] Optionally, the second code block can be an LI block or a defined 66-bit block. The defined 66-bit block can be a newly defined 66-bit block or an existing 66-bit block. For example, as shown in Figure 21, a Link Interruption (LI) sequence in Ethernet can be used to represent segmented monitoring AIS, or a new sequence can be added, or an existing sequence can be used to represent segmented monitoring OCI.

[0116] Based on the aforementioned first signal, the fault handling process using the first signal is as follows:

[0117] As shown in Figure 22, when a fault occurs at point AB in the non-segmented monitoring segment, point B sends a maintenance signal (such as AIS / OCI) or a fault signal. Because point B is the starting node of the segmented monitoring segment, it inserts segmented monitoring information (or TCM; Figure 22 only shows TCM as an example of segmented monitoring information and does not impose any restrictions) into the maintenance signal or fault signal. At the end node D of the segmented monitoring segment, although point D detects a maintenance signal (such as AIS / OCI) or a fault signal, segmented monitoring is enabled at point D. Since the first signal is not detected, point D terminates the segmented monitoring information and continues to transmit maintenance signals (such as AIS / OCI) or fault signals downstream. Point D does not generate a segmented monitoring alarm or perform any operation. When point G detects a maintenance signal (such as AIS / OCI) or a fault signal, it will perform corresponding operations (such as alarms, protection switching, etc.).

[0118] When a fault occurs at point BC in the segmented monitoring segment, point C detects the fault and sends a first signal to point D. Point D detects the first signal and triggers corresponding operations (such as alarms, protection switching, etc.):

[0119] In a protected scenario, point D performs protection switching, sending the service data stream received from the protected path downstream. Point G receives the normal service data stream and performs normal data processing.

[0120] In an unprotected scenario (Figure 22 illustrates this scenario as an example), point D sends a maintenance signal (such as AIS / OCI) or a fault signal downstream. When point G detects the maintenance signal (such as AIS / OCI) or the fault signal, it will perform corresponding operations (such as alarms, protection switching, etc.).

[0121] In this embodiment, when there are nested monitoring segments (PM monitoring segments include segmented monitoring segments), a hold-off timer can be set at the end node (i.e., point G) of the PM monitoring segment to wait for the segmented monitoring segment to handle the fault first.

[0122] Method 2: Segmented monitoring information.

[0123] The segmented monitoring information can be the segmented monitoring information provided in any of the above embodiments. The indication method and structure of the segmented monitoring information can be referred to the specific description in the above embodiments, and will not be repeated here.

[0124] The segmented monitoring information is also used as a trigger condition for fault handling in the segmented monitoring segment. Specifically, if no segmented monitoring information is detected, fault handling for the segmented monitoring segment is triggered.

[0125] The starting node of a segmented monitoring segment inserts segmented monitoring information into the signal to be transmitted. If the ending node of the segmented monitoring segment does not detect segmented monitoring information, it indicates that a fault has occurred in the segmented monitoring segment, and fault handling for the segmented monitoring segment is triggered. If segmented monitoring information is detected, it indicates that no fault has occurred in the segmented monitoring segment, and fault handling for the segmented monitoring segment is not triggered. In this way, segmented fault location can be achieved.

[0126] For SPN, there is only one type of maintenance signal (such as AIS). Nodes configured with segment monitoring function can trigger alarm / protection operations of segment monitoring segments by detecting whether there is segment monitoring information.

[0127] Specifically, as shown in Figure 23, when a fault occurs in point AB of the non-segmented monitoring segment, point B sends a maintenance signal (such as AIS) or a fault signal. Because point B is the starting node of the segmented monitoring segment, it inserts segmented monitoring information (or TCM; Figure 23 only shows TCM as an example of segmented monitoring information) into the maintenance signal (such as AIS) or fault signal. At the end node D of the segmented monitoring segment, although point D detects the maintenance signal (such as AIS) or fault signal, it also detects the segmented monitoring information. Detecting the segmented monitoring information indicates that no fault has occurred in the segmented monitoring segment, so point D does not generate an alarm or operation for the segmented monitoring segment; point D terminates the segmented monitoring information and continues to transmit maintenance signals (such as AIS) or fault signals downstream. When point G detects a maintenance signal (such as AIS) or fault signal, it will perform corresponding operations (such as alarms, protection switching, etc.).

[0128] When segment monitoring section BC fails, point C detects the fault and sends a maintenance signal (such as AIS) or fault signal to point D. If point D does not detect segment monitoring information, it indicates that a fault has occurred in the segment monitoring section, and corresponding operations (such as alarms, protection switching, etc.) are triggered:

[0129] In a protected scenario, point D performs protection switching and sends the service data stream received from the protection path downstream. Point G receives the service data stream and performs normal data processing.

[0130] In an unprotected scenario (Figure 23 illustrates this scenario as an example), point D sends a maintenance signal (such as AIS) or a fault signal downstream. Point G detects the maintenance signal (such as AIS) or the fault signal and performs corresponding operations (such as alarms, protection switching, etc.).

[0131] In this embodiment, when there are nested monitoring segments (PM monitoring segments include segmented monitoring segments), a hold-off timer can be set at the end node (i.e., point G) of the PM monitoring segment to wait for the segmented monitoring segment to handle the fault first.

[0132] Method 3: Second signal.

[0133] The second signal is sent when a fault occurs in the non-segmented monitoring segment. Optionally, the second signal is used to replace the maintenance signal or the fault signal. Optionally, fault handling using the second signal includes: not triggering fault handling in the segmented monitoring segment when the second signal is detected.

[0134] That is, when the starting node of a segmented monitoring segment receives a maintenance or fault signal, it can replace the maintenance or fault signal with a second signal and send the second signal to the next node. Thus, if the ending node of the segmented monitoring segment detects the second signal, it will not trigger fault handling for the segmented monitoring segment. This method solves the technical problem of the ending node of a segmented monitoring segment performing unnecessary alarm / protection switching operations when a fault occurs upstream.

[0135] Optionally, the second signal may include one of the following: a segmented monitoring and maintenance block and a third code block. Optionally, the third code block may be an L1 block or a defined 66-bit block. The defined 66-bit block may be a newly defined 66-bit block or an existing 66-bit block. The structure of the segmented monitoring and maintenance block can be referred to the description in the above embodiments, and will not be repeated here.

[0136] For example, if the second signal is a segmented monitoring and maintenance block, when AIS is received, the second signal can be used to replace AIS, and the LF block of AIS can be replaced with the segmented monitoring and maintenance block; when OCI is received, the second signal can be used to replace OCI, and the Error block of OCI can be replaced with the segmented monitoring and maintenance block.

[0137] If the second signal is the third code block, when AIS is received, the second signal can be used to replace AIS, replacing the LF block of AIS with the third code block, for example, replacing the LF block of AIS with the LI block; when OCI is received, the second signal can be used to replace OCI, replacing the Error block of OCI with the third code block, for example, replacing the Error block of OCI with a newly defined sequence block, such as the newly defined sequence block being 0x00 0x00 0x04 0x00 0x00 0x00 0x00.

[0138] Optionally, when the first signal and the second signal are applied simultaneously, the sequences of the first signal and the second signal are not the same.

[0139] Optionally, when defining the second signal using a third code block, a customer signal status indication can also be added to the segment monitoring information. For example, upon receiving an AIS, the second signal can be used to replace the AIS, replacing the AIS's LF block with the third code block, and the customer signal status indication field in the segment monitoring information can be used to indicate that the customer signal is faulty; upon receiving an OCI, the second signal can be used to replace the OCI, and the customer signal status indication field in the segment monitoring information can be used to indicate that the customer signal connection is open.

[0140] Based on the aforementioned second signal, the fault handling process using the second signal is as follows:

[0141] Specifically, as shown in Figure 24, when the non-segmented monitoring segment AB fails, point B, as the starting node of the segmented monitoring segment, sends a second signal (using the second signal to replace the maintenance signal (including replacing the LF block in AIS, or replacing the Error block in OCI), and inserts segmented monitoring information (or TCM, Figure 24 only shows TCM as an example of segmented monitoring information) into the second signal). At the end node D of the segmented monitoring segment, point D detects the second signal, terminates the segmented monitoring information, and restores the maintenance signal (such as AIS / OCI) or fault signal (including restoring the replaced code block to an LF block or / E / block) according to the detected second signal and continues to transmit downstream. Point D does not generate segmented monitoring alarms or operations. When point G detects a maintenance signal (such as AIS / OCI) or fault signal, it will perform corresponding operations (such as alarms, protection switching, etc.).

[0142] When a fault occurs in segment monitoring section BC, point C detects the fault and sends a maintenance signal (such as AIS / OCI), a fault signal, or a first signal (if the first signal is used) to point D. Point D detects the maintenance signal (such as AIS / OCI), the fault signal, or the first signal, triggering corresponding operations (such as alarms, protection switching, etc.):

[0143] In a protected scenario, point D performs protection switching and sends the service data stream received from the protection path downstream. Point G receives the service data stream and performs normal data processing.

[0144] In an unprotected scenario (Figure 24 illustrates this scenario as an example), point D sends a maintenance signal (such as AIS / OCI) or a fault signal downstream. Point G detects the maintenance signal (such as AIS / OCI) or the fault signal and performs corresponding operations (such as alarms, protection switching, etc.).

[0145] In this embodiment, when there are nested monitoring segments (PM monitoring segments include segmented monitoring segments), a hold-off timer can be set at the end node (i.e., point G) of the PM monitoring segment to wait for the segmented monitoring segment to handle the fault first.

[0146] For multi-level segmented monitoring scenarios, the following describes two fault scenarios as examples: fault in segmented monitoring segment 1 and fault in segmented monitoring segment 2.

[0147] As shown in Figure 25, when a fault occurs in AB of segmented monitoring segment 2, point B sends a maintenance signal (such as AIS / OCI). Because point B is the starting node of segmented monitoring segment 1, it inserts segmented monitoring information 1 (here, the segmented monitoring information of segmented monitoring segment 1 is referred to as segmented monitoring information 1, and TCM1 in Figure 25 is TCM segmented monitoring information 1) into AIS / OCI (i.e., replaces the corresponding maintenance signal block). At the end node D of segmented monitoring segment 1, point D identifies segmented monitoring information 1 through the Type value and segmented monitoring sublayer indication, terminates segmented monitoring information 1, and continues to transmit AIS / OCI downstream. Point D should not generate alarms or operations in the segmented monitoring layer. However, according to the existing MTN / SPN technology, point D will first detect AIS / OCI, and trigger an alarm after confirming receipt of AIS / OCI, but this is not actually a fault in segmented monitoring segment 1 "BD", thus leading to incorrect fault location.

[0148] When a fault occurs in segment BC of segment monitoring segment 1, point C detects the fault and sends a maintenance signal (such as AIS / OCI) to point D. When point D detects the AIS / OCI, it triggers corresponding operations (such as alarms, protection switching, etc.). However, point D does not know whether the fault occurred in segment monitoring segment 1 or the upstream segment monitoring segment 2.

[0149] To address the aforementioned fault scenarios, the fault handling method provided in this application embodiment can resolve the problem of fault location errors. Specifically, one of the following methods can be used for fault handling:

[0150] Method 1: First signal.

[0151] The first signal is sent when a fault occurs in the segmented monitoring segment.

[0152] Optionally, the first signal is used as a trigger condition for fault handling in the segmented monitoring segment. Specifically, if the first signal is detected, fault handling in the segmented monitoring segment is triggered; if the first signal is not detected, fault handling in the segmented monitoring segment is not triggered.

[0153] That is, when a fault occurs in a segmented monitoring segment, a first signal can be sent. If the first signal is detected by the end node of the segmented monitoring segment, it indicates that a fault has occurred in the segmented monitoring segment, thus triggering fault handling for the segmented monitoring segment. In this way, fault location of segments can be achieved.

[0154] Optionally, the fault handling method for the segmented monitoring segment may include:

[0155] If a protection path exists for the segmented monitoring section, protection switching is performed, receiving and sending service data streams from the protection path. If no protection path exists for the segmented monitoring section, an alarm is triggered, and a maintenance signal is sent. The maintenance signal can be AIS / OCI, etc.

[0156] Optionally, the first signal includes one of the following: a repeating sequence of the segmented monitoring and maintenance block, a repeating sequence of the combination of the segmented monitoring and maintenance block and the first code block, and a repeating sequence of the second code block.

[0157] Optionally, the first code block may include at least one of the following: an LF block, an Idle block, and an Error block. The structure of the LF block can be as shown in Figure 17, and the structures of the Idle block and the Error block can be as shown in Figure 18.

[0158] Optionally, the segmented monitoring and maintenance block may include at least one of the following: a type value for identifying the segmented monitoring layer, segmented monitoring sub-layer indication information (for indicating the segmented monitoring sub-layer), and the signal type of the segmented monitoring layer (e.g., the maintenance signal type of the segmented monitoring layer, such as segmented monitoring AIS, segmented monitoring OCI, etc.).

[0159] For example, the first signal can be a repeating sequence of the segmented monitoring and maintenance block, a repeating sequence of the segmented monitoring and maintenance block and the LF block, a repeating sequence of the segmented monitoring and maintenance block and the Idle block, a repeating sequence of the segmented monitoring and maintenance block and the Error block, or a repeating sequence of the segmented monitoring and maintenance block with any combination of the LF block, the Idle block, and the Error block. The segmented monitoring segment status field in the segmented monitoring and maintenance block can indicate the signal type of the segmented monitoring layer. For example, 2 bits can be used to indicate the signal type of the segmented monitoring layer, such as 01 representing segmented monitoring AIS and 10 representing segmented monitoring OCI. The Sub field in the segmented monitoring and maintenance block is used to indicate the segmented monitoring sub-layer. For example, if there are two segmented monitoring sub-layers, Sub=0 can represent segmented monitoring sub-layer 1, and Sub=1 can represent segmented monitoring sub-layer 2.

[0160] For example, the segmented monitoring and maintenance block of MTN is shown in Figure 26. For instance, in MTN, Type=100001, Sub=0, and segmented monitoring segment status=01 indicates that this signal is the AIS of segmented monitoring sublayer 11. The segmented monitoring and maintenance block of SPN is shown in Figure 27. For instance, in SPN, Type=0x3, Sub=0, and segmented monitoring segment status=01 indicates that this signal is the AIS of segmented monitoring sublayer 1. Of course, a single segmented monitoring and maintenance block structure can also be used uniformly.

[0161] Optionally, the second code block can be an LI block or a defined 66-bit block. The defined 66-bit block can be a newly defined 66-bit block or an existing 66-bit block. For example, as shown in Figure 28, the AIS of segmented monitoring sublayer 1 can be represented using an Ethernet Link Interruption (LI) sequence, or a new sequence can be added, or an existing sequence can be used to represent the OCI of segmented monitoring sublayer 1. For segmented monitoring sublayer 2, two sequences can be defined to identify the AIS and OCI of segmented monitoring sublayer 2, respectively. For each additional segmented monitoring sublayer, two sequences need to be defined to represent the maintenance signals of the corresponding segmented monitoring sublayer.

[0162] Based on the aforementioned first signal, the fault handling process using the first signal is as follows:

[0163] As shown in Figure 29, when AB in segmented monitoring segment 2 fails, point B, as an intermediate node of segmented monitoring segment 2, sends the first signal (such as TCM2 AIS / OCI) or fault signal of segmented monitoring sublayer 2. Because point B is also the starting node of segmented monitoring segment 1, it inserts the segmented monitoring information of segmented monitoring segment 1 (or TCM1, only TCM1 is shown as an example in Figure 29) into the first signal or fault signal of segmented monitoring sublayer 2. At the end node D of segmented monitoring segment 1, point D identifies segmented monitoring information 1 (or TCM1) through the Type value and segmented monitoring sublayer indication. Because no first signal of segmented monitoring sublayer 1 is detected, segmented monitoring information 1 is terminated and the first signal (such as TCM2 AIS / OCI) or fault signal of segmented monitoring sublayer 2 is transmitted downstream, without generating an alarm or operation for segmented monitoring segment 1. At the end point G of segmented monitoring segment 2, if the first signal (such as TCM2 AIS / OCI) or fault signal of segmented monitoring sub-layer 2 is detected at point G, corresponding operations (such as alarm, protection switching, etc.) will be performed.

[0164] When a fault occurs in segment BC of segment monitoring segment 1, point C, as an intermediate node between segment monitoring segment 1 and segment monitoring segment 2, sends a segment monitoring layer maintenance signal with a smaller monitoring range to reduce the impact area. In this scenario, point C sends the first signal (such as TCM1 AIS / OCI) or fault signal of segment monitoring sub-layer 1 to point D. At the end node D of segment monitoring segment 1, when point D detects the first signal (such as TCM1 AIS / OCI) or fault signal of segment monitoring sub-layer 1, it triggers corresponding operations (such as alarm, protection switching, etc.).

[0165] In a protected scenario, point D performs protection switching, sending the service data stream received from the protection path downstream (i.e., D+TCM2, where TCM2 is the segmented monitoring information of segmented monitoring segment 2 / segmented monitoring sublayer 2). At the end node G of segmented monitoring segment 2, point G receives the service data stream, terminates segmented monitoring information 2, and performs normal data processing.

[0166] In an unprotected scenario (Figure 29 illustrates this scenario as an example), point D, as an intermediate node of segmented monitoring segment 2, will send the first signal (such as TCM2 AIS / OCI) or fault signal of segmented monitoring sub-layer 2 downstream. At the terminal node G of segmented monitoring segment 2, point G detects the first signal (such as TCM2 AIS / OCI) or fault signal of segmented monitoring sub-layer 2 and will perform corresponding operations (such as alarm, protection switching, etc.).

[0167] In this embodiment, when there is nested monitoring segments (segmented monitoring segment 2 includes segmented monitoring segment 1), a hold-off timer can be set at the end node (i.e., point G) of segmented monitoring segment 2 to wait for segmented monitoring segment 1 to handle the fault first.

[0168] Method 2: Segmented monitoring information.

[0169] The segmented monitoring information can be the segmented monitoring information provided in any of the above embodiments. The indication method and structure of the segmented monitoring information can be referred to the specific description in the above embodiments, and will not be repeated here.

[0170] The segmented monitoring information serves as the trigger condition for fault handling in each segmented monitoring segment. Specifically, fault handling for a segmented monitoring segment is triggered if no segmented monitoring information is detected, but not if segmented monitoring information is detected.

[0171] The starting node of a segmented monitoring segment inserts segmented monitoring information into the signal to be transmitted. If the ending node of the segmented monitoring segment does not detect segmented monitoring information, it indicates a fault in the segmented monitoring segment, triggering fault handling for that segment. This method enables fault location within segments.

[0172] For SPN, there is only one type of maintenance signal (such as AIS). Nodes configured with segment monitoring function can trigger alarm / protection operations of segment monitoring segments by detecting whether there is segment monitoring information.

[0173] Specifically, as shown in Figure 30, when a fault occurs at AB in segmented monitoring segment 2, point B sends a maintenance signal (such as AIS) or a fault signal. Because point B is the starting node of segmented monitoring segment 1, it inserts segmented monitoring information 1 (or TCM1, as shown in Figure 30, where TCM1 is used as an example) of segmented monitoring segment 1 into the maintenance signal (such as AIS) or fault signal. At the end node D of segmented monitoring segment 1, although point D detects the maintenance signal (such as AIS) or fault signal, it also detects segmented monitoring information 1. Point D does not generate an alarm or operation for segmented monitoring segment 1. D terminates segmented monitoring information 1 and continues to transmit maintenance signals (such as AIS) or fault signals downstream. At the end node G of segmented monitoring segment 2, point G detects the maintenance signal (such as AIS) or fault signal and performs corresponding operations (such as alarms, protection switching, etc.).

[0174] When a fault occurs at point BC in segment monitoring segment 1, point C detects the fault and sends a maintenance signal (such as AIS) or a fault signal to point D. At the end node D of segment monitoring segment 1, if segment monitoring information 1 is not detected at point D, corresponding operations (such as alarms, protection switching, etc.) are triggered:

[0175] In a protected scenario, point D performs protection switching, sending the service data stream received from the protection path downstream (i.e., D+TCM2, where TCM2 is the segmented monitoring information of segmented monitoring segment 2, or segmented monitoring information 2). At the end node G of segmented monitoring segment 2, point G receives the service data stream, terminates segmented monitoring information 2, and performs normal data processing.

[0176] In an unprotected scenario (Figure 30 illustrates this scenario as an example), point D sends a maintenance signal (such as AIS) or a fault signal downstream. At the end node G of segmented monitoring segment 2, point G detects the maintenance signal (such as AIS) or the fault signal and performs corresponding operations (such as alarms, protection switching, etc.).

[0177] In this embodiment, when there is nested monitoring segments (segmented monitoring segment 2 includes segmented monitoring segment 1), a hold-off timer can be set at the end node (i.e., point G) of segmented monitoring segment 2 to wait for segmented monitoring segment 1 to handle the fault first.

[0178] Method 3: Second signal.

[0179] The second signal is sent when a fault occurs in the non-segmented monitoring segment. Optionally, the second signal is used to replace the maintenance signal or the fault signal. Optionally, fault handling using the second signal includes: not triggering fault handling in the segmented monitoring segment when the second signal is detected.

[0180] That is, when the starting node of a segmented monitoring section receives a maintenance or fault signal, it can replace the maintenance or fault signal with a second signal and send the second signal to the next node. Thus, if the ending node of the segmented monitoring section detects the second signal, it will not trigger fault handling for the segmented monitoring section. This method solves the technical problem of unnecessary alarm / protection switching operations by the ending node of the segmented monitoring section when a fault occurs upstream.

[0181] Optionally, the second signal may include one of the following: a segmented monitoring and maintenance block and a third code block. Optionally, the third code block may be an LI block or a defined 66-bit block. The defined 66-bit block may be a newly defined 66-bit block or an existing 66-bit block.

[0182] The aforementioned segmented monitoring and maintenance block may include a type value for indicating the segmented monitoring layer, segmented monitoring sub-layer indication information (for indicating the segmented monitoring sub-layer), and the signal type of the segmented monitoring layer.

[0183] For example, continuing to refer to Figure 28, for the third code block, the AIS of segmented monitoring sublayer 1 can be represented by the LI sequence in Ethernet, or a new sequence can be added, or an existing sequence can be used to represent the OCI of segmented monitoring sublayer 1. For segmented monitoring sublayer 2, two sequences can be defined to identify the AIS and OCI of segmented monitoring sublayer 2 respectively. For each additional segmented monitoring sublayer, two sequences need to be defined to represent the maintenance signal of the corresponding segmented monitoring sublayer.

[0184] For example, if the second signal is a segmented monitoring and maintenance block, when AIS is received, the second signal can be used to replace AIS, and the LF block of AIS can be replaced with the segmented monitoring and maintenance block of the corresponding segmented monitoring sublayer; when OCI is received, the second signal can be used to replace OCI, and the Error block of OCI can be replaced with the segmented monitoring and maintenance block of the corresponding segmented monitoring sublayer.

[0185] If the second signal is the third code block, when AIS is received, the second signal can be used to replace AIS, replacing the LF block of AIS with the third code block of the corresponding segmented monitoring sublayer, for example, replacing the LF code block of AIS with the LI block; when OCI is received, the second signal can be used to replace OCI, replacing the Error block of OCI with the third code block of the corresponding segmented monitoring sublayer, for example, replacing the Error block of OCI with a newly defined sequence block of the corresponding segmented monitoring sublayer, such as the newly defined sequence being 0x00 0x00 0x04 0x00 0x00 0x00 0x00.

[0186] Optionally, when the first signal and the second signal are applied simultaneously, the sequences of the first signal and the second signal are not the same.

[0187] Optionally, when defining the second signal using a third code block, a customer signal status indication can also be added to the segmented monitoring information. For example, upon receiving an AIS, the second signal can be used to replace the AIS, replacing the AIS's LF block with the third code block of the corresponding segmented monitoring sublayer, and indicating customer signal failure through the customer signal status indication field in the segmented monitoring information; upon receiving an OCI, the second signal can be used to replace the OCI, replacing the OCI's Error block with the third code block of the corresponding segmented monitoring sublayer, and indicating customer signal connection open through the customer signal status indication field in the segmented monitoring information.

[0188] Based on the aforementioned second signal, the fault handling process using the second signal is as follows:

[0189] Specifically, as shown in Figure 31, when an AB fault occurs in segmented monitoring segment 2, point B, as the starting node of segmented monitoring segment 1, sends the second signal of segmented monitoring sub-layer 1 (using the second signal of segmented monitoring sub-layer 1 to replace the maintenance signal of segmented monitoring sub-layer 2 (e.g., including replacing the LF block in TCM2 AIS, or replacing TCM2)). The Error block in OCI will also insert Segment Monitoring Information 1 (or TCM1, as shown in Figure 31, only TCM1 is used as an example for Segment Monitoring Information 1) into the second signal of Segment Monitoring Sublayer 1. At the end node D of Segment Monitoring Segment 1, point D identifies Segment Monitoring Information 1 through the Type value and the Segment Monitoring Sublayer indicator. Because point D detects the second signal of Segment Monitoring Sublayer 1, it terminates Segment Monitoring Information 1 and restores the maintenance signal (such as AIS / OCI) or fault signal or the first signal of Segment Monitoring Sublayer 2 (including restoring the replaced code block to an LF block or / E / block) according to the detected second signal of Segment Monitoring Sublayer 1 and continues to transmit downstream. Point D does not generate an alarm or operation for Segment Monitoring Segment 1. When point G detects the maintenance signal (such as AIS / OCI) or fault signal or the first signal of Segment Monitoring Sublayer 2, it will perform corresponding operations (such as alarm, protection switching, etc.).

[0190] When a fault occurs at point BC in segment monitoring segment 1, point C detects the fault and sends a maintenance signal (such as AIS / OCI), a fault signal, or the first signal of segment monitoring sub-layer 1 (if the first signal is used) to point D. Point D detects the maintenance signal (such as AIS / OCI), the fault signal, or the first signal of segment monitoring sub-layer 1, triggering corresponding operations (such as alarms, protection switching, etc.):

[0191] In a protected scenario, point D performs protection switching and sends the service data stream received from the protection path (i.e., D+TCM2) downstream. At the end node G of segmented monitoring segment 2, point G receives the service data stream, terminates segmented monitoring information 2, and performs normal data processing.

[0192] In an unprotected scenario (Figure 31 illustrates this scenario), point D sends a maintenance signal (such as AIS / OCI), a fault signal, or the first signal of segmented monitoring sublayer 2 downstream. (If the first signal is used, point D, as an intermediate node of segmented monitoring sublayer 2, can send the first signal of segmented monitoring sublayer 2.) At the terminal node G of segmented monitoring sublayer 2, if point G detects a maintenance signal (such as AIS / OCI), a fault signal, or the first signal of segmented monitoring sublayer 2, it will perform corresponding operations (such as alarms, protection switching, etc.).

[0193] In this embodiment, when there is nested monitoring segments (segmented monitoring segment 2 includes segmented monitoring segment 1), a hold-off timer can be set at the end node (i.e., point G) of segmented monitoring segment 2 to wait for segmented monitoring segment 1 to handle the fault first.

[0194] Figure 32 is a schematic diagram of a segmented monitoring implementation device provided in an embodiment of this application. As shown in Figure 32, the device may include a processing module 3201.

[0195] The processing module 3201 is used to perform OAM processing on the segmented monitoring segments using segmented monitoring information.

[0196] The segmented monitoring information is indicated by a type value.

[0197] Optionally, the segmented monitoring information includes at least one of the following:

[0198] Basic information;

[0199] Monitoring information;

[0200] Protect and replace information;

[0201] Delay measurement information;

[0202] Verification information;

[0203] Segmented monitoring of segment status;

[0204] Customer signal status indication;

[0205] Segmented monitoring of sub-layer indicators.

[0206] Optionally, different segment monitoring information can be indicated by different type values.

[0207] Optionally, the segmented monitoring information is a segmented monitoring information block, which is a frame or multiframe consisting of at least one 66-bit block, and each frame in the multiframe is indicated by the same type value.

[0208] Figure 33 is another structural schematic diagram of the segmented monitoring implementation device provided in the embodiment of this application. As shown in Figure 33, the device may include a processing module 3301.

[0209] Specifically, the processing module 3301 performs fault handling using at least one of the following methods:

[0210] First signal;

[0211] Segmented monitoring information;

[0212] Second signal;

[0213] The first signal is sent when a fault occurs in the segmented monitoring segment, and the second signal is sent when a fault occurs in the non-segmented monitoring segment.

[0214] Optionally, the first signal is used as a trigger condition for fault handling of the segmented monitoring segment.

[0215] Optionally, the processing module 3301 is specifically used to trigger fault handling of the segmented monitoring segment when the first signal is detected.

[0216] Optionally, the second signal is used to replace the maintenance signal or the fault signal.

[0217] Optionally, the processing module 3301 is further configured to not trigger the fault handling of the segmented monitoring segment when the second signal is detected.

[0218] Optionally, the segmented monitoring information is used as a trigger condition for fault handling of the segmented monitoring segment.

[0219] Optionally, the above-mentioned processing module 3301 is also specifically used to trigger fault handling of the segmented monitoring segment when the segmented monitoring information is not detected.

[0220] Optionally, the first signal includes one of the following:

[0221] Repeated sequences of segmented monitoring and maintenance blocks;

[0222] The repeating sequence of segmented monitoring and maintenance blocks and the first code block;

[0223] The repeating sequence of the second code block.

[0224] Optionally, the second code block is an L1 block or a defined 66-bit block.

[0225] Optionally, the second signal includes one of the following:

[0226] Segmented monitoring and maintenance blocks;

[0227] Third code block.

[0228] Optionally, the third code block is an L1 block or a defined 66-bit block.

[0229] Optionally, when the first signal and the second signal are applied simultaneously, the sequences of the first signal and the second signal are not the same.

[0230] Optionally, the segmented monitoring and maintenance block includes at least one of the following:

[0231] Used to identify the type of monitoring in the segmented monitoring layer;

[0232] Segmented monitoring of sub-layer indication information;

[0233] Signal types of segmented monitoring layers.

[0234] Optionally, the first code block includes at least one of the following:

[0235] LF block, Idle block, Error block.

[0236] Optionally, the device may further include a receiving module and a transmitting module.

[0237] Specifically, the processing module 3301 is also used to perform protection switching when there is a protection path in the segmented monitoring segment;

[0238] The receiving module is used to receive the service data stream from the protection path after the processing module 3301 performs the protection switching;

[0239] The sending module is used to send the business data stream received by the receiving module;

[0240] The processing module 3301 is also used to trigger an alarm when there is no protection path in the segmented monitoring segment;

[0241] The sending module is also used to send maintenance signals when the processing module 3301 triggers an alarm.

[0242] In one embodiment, a network node is also provided, the internal structure of which can be shown in Figure 34. The network node includes a processor, memory, network interface, and database connected via a system bus. The processor of the network node provides computing and control capabilities. The memory of the network node includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The database of the network node stores data generated during the implementation of segmented monitoring. The network interface of the network node is used to communicate with external terminals via a network connection. When the computer program is executed by the processor, it implements the segmented monitoring implementation method provided in any of the above embodiments.

[0243] Those skilled in the art will understand that the structure shown in Figure 34 is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the network nodes to which the present application is applied. Specific network nodes may include more or fewer components than those shown in the figure, or may combine certain components, or may have different component arrangements.

[0244] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the following steps:

[0245] OAM processing for segmented monitoring segments is performed using segmented monitoring information;

[0246] The segmented monitoring information is indicated by a type value.

[0247] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the following steps:

[0248] Troubleshooting should be performed using at least one of the following methods:

[0249] First signal;

[0250] Segmented monitoring information;

[0251] Second signal;

[0252] The first signal is sent when a fault occurs in the segmented monitoring segment, and the second signal is sent when a fault occurs in the non-segmented monitoring segment.

[0253] The computer storage medium in this application embodiment can be any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. For example, a computer-readable storage medium can be, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. Computer-readable storage media include (a non-exhaustive list): electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), electrically erasable, programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this application, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0254] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, the data signals carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit programs for use by or in conjunction with an instruction execution system, apparatus, or device.

[0255] Program code contained on a computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wire, optical fiber, radio frequency (RF), or any suitable combination thereof.

[0256] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination of programming languages, including object-oriented programming languages ​​(such as Java, Smalltalk, C++, Ruby, and Go) and conventional procedural programming languages ​​(such as the "C" language or similar programming languages). The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network (including a Local Area Network (LAN) or a Wide Area Network (WAN)), or it can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0257] Those skilled in the art will understand that the term user terminal encompasses any suitable type of wireless user equipment, such as mobile phones, portable data processing devices, portable web browsers, or vehicle-mounted mobile stations.

[0258] Generally, the various embodiments of this application can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although this application is not limited thereto.

[0259] Embodiments of this application can be implemented by executing computer program instructions through the data processor of a mobile device, for example, in a processor entity, or through hardware, or through a combination of software and hardware. The computer program instructions can be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages.

[0260] Any block diagram of logical flow in the accompanying drawings of this application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program may be stored on memory. Memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, read-only memory (ROM), random access memory (RAM), optical storage devices and systems (Digital Video Disc (DVD) or Compact Disc (CD)), etc. Computer-readable media may include non-transitory storage media. The data processor may be of any type suitable to the local technical environment, such as, but not limited to, general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and processors based on multi-core processor architectures.

Claims

1. A method for implementing segmented monitoring, comprising: Segmented monitoring information is used for the operation, management, and maintenance of segmented monitoring segments (OAM processing). The segmented monitoring information is indicated by a type value.

2. The method according to claim 1, wherein, The segmented monitoring information includes at least one of the following: Basic information; Monitoring information; Protect and replace information; Delay measurement information; Verification information; Segmented monitoring of segment status; Customer signal status indication; Segmented monitoring of sub-layer indicators.

3. The method according to claim 1, wherein, Different segments of monitoring information are indicated by different type values.

4. The method according to claim 1, wherein, The segmented monitoring information is a segmented monitoring information block, which is a frame or multiframe consisting of at least one 66-bit block, and each frame in the multiframe is indicated by the same type value.

5. A method for implementing segmented monitoring, comprising fault handling using at least one of the following methods: First signal; Segmented monitoring information; Second signal; in, The first signal is sent when a fault occurs in the segmented monitoring segment, and the second signal is sent when a fault occurs in the non-segmented monitoring segment.

6. The method according to claim 5, wherein, The first signal is used as a trigger condition for fault handling of the segmented monitoring segment.

7. The method according to claim 6, wherein, The first signal is used as a trigger condition for fault handling of the segmented monitoring segment, including: Upon detecting the first signal, fault handling of the segmented monitoring segment is triggered.

8. The method according to claim 5, wherein, The second signal is used to replace the maintenance signal or the fault signal.

9. The method according to claim 8, further comprising: If the second signal is detected, the fault handling of the segmented monitoring segment is not triggered.

10. The method according to claim 5, wherein, The segmented monitoring information is used as a trigger condition for fault handling of the segmented monitoring segment.

11. The method according to claim 10, wherein, The segmented monitoring information is used as a trigger condition for fault handling of the segmented monitoring segment, including: If the segmented monitoring information is not detected, the fault handling of the segmented monitoring segment is triggered.

12. The method according to claim 5, wherein, The first signal includes one of the following: Repeated sequences of segmented monitoring and maintenance blocks; The repeating sequence of segmented monitoring and maintenance blocks and the first code block; The repeating sequence of the second code block.

13. The method according to claim 12, wherein, The second code block is either a link interruption LI block or a defined 66-bit block.

14. The method according to claim 5, wherein, The second signal includes one of the following: Segmented monitoring and maintenance blocks; Third code block.

15. The method according to claim 14, wherein, The third code block is either an LI block or a defined 66-bit block.

16. The method according to claim 5, wherein, When the first signal and the second signal are applied simultaneously, the sequences of the first signal and the second signal are not the same.

17. The method according to claim 12 or 14, wherein, The segmented monitoring and maintenance block includes at least one of the following: Used to identify the type of monitoring in the segmented monitoring layer; Segmented monitoring of sub-layer indication information; Signal types of segmented monitoring layers.

18. The method according to claim 12, wherein, The first code block includes at least one of the following: Local error LF block, idle block, error block.

19. The method according to claim 5, wherein, The fault handling methods for the segmented monitoring segment include: If the segmented monitoring segment has a protection path, protection switching is performed, service data streams are received from the protection path, and the service data streams are sent. If there is no protected path in the segmented monitoring segment, an alarm is triggered and a maintenance signal is sent.

20. A network node, comprising: A memory and a processor, the memory storing a computer program, the processor executing the computer program to implement the method of any one of claims 1-19.

21. A computer-readable storage medium storing a computer program that, when executed by a processor, implements the method of any one of claims 1-19.

Images