WO2020253791A1 - Fault transmission method and apparatus - Google Patents

Abstract

Embodiments of the present application provide a fault transmission method, applicable to a fourth node. A first client layer path comprises a first node and a second node; a first service layer path comprises a third node and a fourth node; the first client layer path further comprises the third node and the fourth node; the first service layer path is used for bearing the first client layer path; the first node and the third node are the same nodes, or the first node and the third node are different nodes. The method comprises: obtaining fault information that a fault happens in the first service layer path; sending a first message to the second node by means of the first client layer path, the first message being used for indicating that the fault happens in the first service layer path, and the first message comprising a path identifier of the first service layer path. A node on the client layer path can obtain a path identifier of a faulty service layer path, so that related processing can be accurately carried out.

Description

Method and device for fault transmission Technical field

The embodiments of the present application relate to the field of communication technologies, and in particular, to a fault transmission method and device.

Background technique

Protection switching is one of the important guarantee technologies for the stable operation of the network. As shown in Figure 1, the working path of A-Z is A-B-D-E-Z, and the protection path of the B-E area (also called the effective domain) is B-C-E.

If the A-B link fails, an alarm is continuously generated, and the protection path switch is triggered, which will cause the working path B-D-E and the protection path B-C-E to switch continuously, resulting in path oscillation. If the D-E link fails and an alarm is generated, the working path B-D-E will switch to the protection path B-C-E, and no path oscillation will occur.

Summary of the invention

The embodiments of the present application provide a fault transmission method and device, which can avoid path oscillation.

In the first aspect, a fault transmission method is applied to a fourth node, the first client layer path includes a first node and a second node, the first service layer path includes a third node and a fourth node, and the first client layer The path further includes the third node and the fourth node, the first service layer path is used to carry the first client layer path, and the first node and the third node are the same node or the The first node and the third node are different nodes, including: acquiring failure information of a first service layer path failure; sending a first message to the second node through the first client layer path, the first message being used to indicate The first service layer path fails, and the first message includes the path identifier of the first service layer path.

In some possible implementation manners, the first service layer path is a first service layer link, and the path identifier of the first service layer path is a link identifier of the first service layer link.

In some possible implementation manners, the first service layer link is a link of a first flexible Ethernet group, and the link identifier of the first service layer link is a flexible Ethernet group of the first flexible Ethernet group. Ethernet group number.

In some possible implementation manners, the first message is carried in at least one first MB/NB coding block.

In some possible implementations, the first MB/NB coding block is a first 64B/66B coding block, and the first 64B/66B coding block includes a type field and a path identification field, and the type field is used to indicate The server path failed.

In some possible implementation manners, the first MB/NB code block is a control code block that carries local fault information.

In some possible implementation manners, the first message is carried in at least one first alarm indication signal data unit.

In the second aspect, a fault transmission method is applied to the fifth node, the first client layer path includes a first node and a second node, the first service layer path includes a third node and a fourth node, and the first client layer The path further includes the third node and the fourth node, the first service layer path is used to carry the first client layer path, and the first node and the third node are the same node or the The first node and the third node are different nodes, the fifth node is a node between the fourth node and the second node, or the fifth node is the second node, including: The first client layer path receives a first message, the first message is used to indicate that the first service layer path has failed, and the first message includes the path identifier of the first service layer path; The path identifier of the service layer path is processed.

In some possible implementation manners, the processing according to the path identifier of the first service layer path includes: determining whether to perform protection path switching according to the path identifier of the first service layer path.

In some possible implementations, the determining whether to switch the protection path according to the path identifier of the first service layer path includes: determining whether the path identifier of the first service layer path belongs to a preset path identifier table Path identification; if the path identification of the first service layer path belongs to the path identification in the preset path identification table, switch the protection path; if the path identification of the first service layer path does not belong to the preset path identification table If the path identifier in, the protection path is not switched.

In some possible implementation manners, the first message is carried in at least one first MB/NB coding block.

In some possible implementation manners, the first message is carried in at least one first alarm indication signal data unit.

In the third aspect, the present application provides a fault transmission device for implementing the method in the first aspect and/or any possible implementation manners thereof. The device may be a network device, a device in a network device, or a device that can be matched and used with the network device. In a design, the device may include a module corresponding to the method/operation/step/action described in the first aspect and/or any possible implementation manners thereof. The module may be a hardware circuit, software, or It can be realized by hardware circuit combined with software. In one design, the device may include a processing unit and a transceiver unit.

In the fourth aspect, the present application provides a fault transmission device for implementing the method in the second aspect and/or any possible implementation manners thereof. The device may be a network device, a device in a network device, or a device that can be matched and used with the network device. In one design, the device may include a module corresponding to the method/operation/step/action described in the second aspect and/or any of its possible implementations. The module may be a hardware circuit, software, or It can be realized by hardware circuit combined with software. In one design, the device may include a processing unit and a transceiver unit.

In a fifth aspect, the present application provides a fault transmission device, which includes a processor, configured to implement the method described in the first aspect and/or any possible implementation manner thereof. The device may further include a memory. Optionally, the memory is used to store instructions. When the processor executes the instructions stored in the memory, the first aspect and/or any possible implementation manners thereof may be implemented. Described method. The device may further include a communication interface for communicating with other devices. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, pin, or other types of communication interfaces.

In a sixth aspect, the present application provides a fault transmission device, which includes a processor, configured to implement the method described in the second aspect and/or any possible implementation manner thereof. The device may further include a memory. Optionally, the memory is used to store instructions. When the processor executes the instructions stored in the memory, the above second aspect and/or any possible implementation manners thereof may be implemented Described method. The device may also include a communication interface, which is used for the device to communicate with other devices.

In a seventh aspect, this application provides a fault transmission system, which includes the device provided in the third aspect and the device provided in the fourth aspect; or

The system includes the device provided by the fifth aspect and the device provided by the sixth aspect;

In an eighth aspect, the present application provides a computer-readable storage medium in which computer instructions are stored. When the computer instructions are executed on the computer, the computer executes the above aspects and any possible design methods.

In a ninth aspect, this application provides a chip including a processor. The processor is used to execute the above aspects and methods in any possible implementation manners.

Optionally, the chip further includes a memory, and the memory is coupled with the processor.

Further optionally, the chip further includes a communication interface.

In a tenth aspect, the present application provides a computer program product, the computer program product includes computer program code, when the computer program code runs on a computer, the computer executes the above aspects and any possible design methods.

Description of the drawings

FIG. 1 is a schematic diagram of a network system provided by an embodiment of this application.

Fig. 2 is a schematic diagram of a fault transmission method provided by an embodiment of the application.

FIG. 3A is a schematic diagram of a 64B/66B encoding block carrying a first message according to an embodiment of the application.

FIG. 3B is a schematic diagram of another 64B/66B encoding block that carries the first message according to an embodiment of the application.

3C is a schematic diagram of a first AIS data unit carrying a first message according to an embodiment of this application.

FIG. 4A is a schematic diagram of another network system provided by an embodiment of this application.

FIG. 4B is a schematic diagram of still another network system provided by an embodiment of this application.

FIG. 4C is a schematic diagram of still another network system provided by an embodiment of the application.

Fig. 5 is a schematic block diagram of a fault transmission device provided by an embodiment of the present application.

FIG. 6 is a schematic block diagram of another fault transmission device provided by an embodiment of the present application.

FIG. 7 is a schematic block diagram of another fault transmission device provided by an embodiment of the present application.

Detailed ways

In order to make the purpose, technical solutions, and advantages of this application clearer, the following further describes this application in detail with reference to the accompanying drawings and embodiments.

The technical solutions provided by the embodiments of this application can be applied to flexible Ethernet, and can also be applied to other types of networks, such as Ethernet, Optical Transport Network (OTN) network, and Synchronous Digital Hierarchy, SDH) network, Metro Transport Network (MTN), etc.

As shown in Figure 1, a schematic diagram of a network system provided by an embodiment of this application. The network system includes nodes A, B, C, D, E, and Z. The working path of AZ is ABDEZ and BE zone (also can The protection path called effective domain is BCE.

The following explains some of the terms involved in the embodiments of this application

1. Service layer path and customer layer path.

A customer-level path may include at least one service-level path. As shown in FIG. 1, the customer-level path A-B-D-E-Z includes a service-level path A-B, a service-level path B-D, a service-level path D-E, and a service-level path E-Z.

The service layer path and the client layer path are relative, and the service layer path is used to carry the corresponding client layer path. As shown in Figure 1, the path A-B is the service layer path of the path A-B-D-E-Z, and the service layer path A-B is used to carry the client layer path A-B-D-E-Z. In addition, path A-B can also be used as a client-level path, with multiple service-level paths configured in the lower layer.

2. Path and link.

A path may include at least one link. As shown in FIG. 1, the service layer path AB, the service layer path BD, the service layer path DE, and the service layer path EZ all include one link, and the client layer path ABDEZ includes 4 links. They are link AB, link BD, link DE, and link EZ.

If the service layer path A-B also includes node F, then the service layer path A-B includes two links, namely link A-F and link F-B.

For the convenience of description, the service layer path AB, the service layer path BD, the service layer path DE, and the service layer path EZ in the following embodiments all include one link, so they can also be referred to as the service layer link AB and the service layer link BD. , The service layer link DE and the service layer link EZ.

3. Operation management and maintenance (Operation, Administration and Maintenance, OAM).

It usually includes mechanisms such as error detection, fault detection, delay measurement, and path discovery in the network.

4. Flexible Ethernet (Flexible Ethernet, FlexE).

The 802.3-based Ethernet defined by the Institute of Electrical and Electronics Engineers (IEEE) as a service interface is used in various occasions and has achieved great success. However, as the technology develops, the bandwidth particles are different The larger the value, the more likely it is to have excessive deviations from the actual application requirements. The bandwidth required by mainstream applications may not belong to any Ethernet standard rate. For example, 50Gbps is a waste of resources if 100GE is used for transmission, while there is currently no corresponding Ethernet standard particle that can carry 200Gbps. People expect a flexible bandwidth port (virtual connection) that can share one or several Ethernet physical interfaces, for example, two 40GE ports and two 10GE ports share one 100G physical interface. The concept of Flexible Ethernet (Flexible Ethernet, FlexE) came into being, specifically by binding several Ethernet physical layer (PHY) devices into a FlexE group (Group), and physical layer channelization (sub-rate) ) And other functions to meet the requirements of flexible bandwidth port applications. Therefore, the Media Access Control (MAC) rate provided by FlexE can be greater than the rate of a single PHY (implemented through bonding), or less than the rate of a single PHY (implemented through channelization). A FlexE Group has a FlexE Group Number.

As shown in FIG. 2, a fault transmission method provided by an embodiment of this application includes:

S201. The fault detection node detects that the path of the first service layer is faulty.

S202. The fault detection node sends a first message through the first client layer path, where the first message is used to indicate that the first service layer path fails, and the first message includes the path identifier of the first service layer path. .

S203. The faulty receiving node receives the first message through the first client layer path.

S204. The fault receiving node performs processing according to the path identifier of the first service layer path.

The first message may also be referred to as the first message, and the processing performed by the failure receiving node according to the path identifier may also be referred to as OAM processing, such as protection switching and other related processing.

With reference to Figure 1, the first client-level path A-B-D-E-Z includes four service-level paths, namely, service-level path A-B, service-level path B-D, service-level path D-E, and service-level path E-Z. Assume that the service layer path A-B fails, that is, the service layer path A-B is the first service layer path. The first client layer path includes a first node (node A) and a second node (node Z). The first service layer path includes a third node (node A) and a fourth node (node B). The first client layer path also Including the third node (Node A) and the fourth node (Node B), the first service layer path is used to carry the first client layer path. The first node and the second node are the end nodes of the first client layer path, and the third node and the fourth node are the end nodes of the first service layer path. In this embodiment, the first node (node A) and the third node (node A) are the same node. In a possible design, for example, the first service layer path includes the third node (node B) and the fourth node. In the case of node (node D), the first node (node A) and the third node (node B) are different nodes. In one possible design, node Z is the first node and node A is the second node. In one possible design, node B is the third node and node A is the fourth node.

The fourth node (Node B) serves as a fault detection node and can detect that the first service layer path AB has failed. The fourth node (Node B) sends the first message to the second node (Node Z) through the first client layer path. The first message is used to indicate that the first service layer path AB has failed, and the first message includes the path identifier of the first service layer path AB.

The second node (node Z) can be used as a fault receiving node, and the intermediate node between the fourth node (node B) and the second node (node Z) can also be used as a fault receiving node, which is also the first client Layer path, so it can be used as a fault receiving node. The fault receiving node may perform processing according to the path identifier of the first service layer path.

The first message can be sent in various data formats, and can be sent at various network levels. For example, it can be sent at the Ethernet physical layer or at the link layer. The following uses Figure 3A, Figure 3B and Figure 3 3C is an example, where FIGS. 3A and 3B are examples of the Ethernet physical layer, and FIG. 3C is an example of the link layer.

The first message may be carried in at least one first MB/NB encoding block. The first MB/NB encoding block is an Ethernet PCS encoding block, for example, a 64B/66B encoding block. As shown in FIG. 3A, a 64B/66B encoding block for carrying the first message provided by this embodiment of the application is a control encoding for carrying local fault (LF) information defined in IEEE802.3 The extension of the block, where 0x4B is used to indicate that the code block is of the O code type. The three fields of D1, D2 and D3 include 24 bits, and the upper 4 bits of D1, D2 and D3 (20 bits in total) As the path identifier field, it is used to carry the path identifier of the first service layer path. The two least significant bits of D3 are 01 to indicate that the code block carries LF information. As shown in Fig. 3B, another 64B/66B coding block that carries the first message provided in this embodiment of the application includes Type, Value 1, Value 2, and Value 3 ( Value 3), Value 4 (Value 4), Value 5 (Value 5), Sequence Number (Seq) and Cyclic Redundancy Check (CRC)-4 fields, the type field can be set to indicate the occurrence of the service layer path For faults, the upper 4 bits (20 bits in total) of the value 1 field, the value 2 field, and the value 3 field are used as the path identification field to carry the path identification of the first service layer path.

The first message may also be carried in at least one first alarm indication signal (AIS) data unit, and the first AIS data unit may be an AIS data unit based on the AIS data unit defined in ITU-T G.8013. . As shown in Figure 3C, the first AIS data unit carrying the first message provided in this embodiment of the application includes a maintenance entity group level (MEL) field, a version (Version) field, and an operation code ( Operation code, OpCode field, flags field, type-length-value (TLV) offset (Offset) field, path identification field, reserved (Reserved) field and end (End) TLV field. The MEL field is used to identify the level of the AIS message in the network; Version can take the value 0; OpCode can take the value 33; the first five digits of the Flags field are reserved, and the last three digits indicate the message period; TLV Offset means to the End TLV field Since the extended AIS data unit adds 3 bytes, the TLV Offset can be set to 3; in the extended 3 bytes, 20 bits are used as the path identification field, and 4 bits are used as Reserved Field; End TLV indicates the end of the AIS data unit, and can take the value 0.

As shown in Figure 4A, it is a schematic diagram of a network system provided by an embodiment of this application. The network system includes nodes A, B, C, D, E, and Z, where the working path of AZ is ABDEZ, BE area (or The protection path called the effective domain is BCE, and the end nodes of the protection path are node B and node E, that is, node B and node E can perform protection switching operations. The paths A-B, B-D, D-E, E-Z, B-C, and C-E are all FlexE links, and the path identifiers are 1, 3, 5, 6, 2, and 4, respectively. The customer-level path A-B-D-E-Z includes 4 service-level paths, which are service-level paths A-B, B-D, D-E, and E-Z.

If the path A-B fails, the first service layer path is A-B and the first client layer path is A-B-D-E-Z, the following solutions can be adopted:

1. The first service layer path A-B is a FlexE link, the FlexE link fails, and node B detects link failure alarm information.

2. Node B sends the first message to node Z through the first client layer path. Specifically, it can be inserted into the first client layer path carried by the first service layer path AB (the coding block shown in Figure 3A) , The alarm information carries the FlexE link identifier "1" of AB.

3. Node E detects the LF alarm information of the first client layer path, extracts the identifier "1", and determines the location of the failed link. When applied to the protection switching scenario, the node E compares the identifier "1" with the link identifiers related to the protection domain in this section, and finds that the faulty link does not belong to the protection domain, and no protection switching operation is performed. If the failed link is B-D or D-E, the LF alarm detected by node E carries the identifier "3" or "5" and belongs to the link in the protection domain, and protection switching is performed.

In a possible design, the above step 2 can also be: Node B inserts AIS alarm information (code block shown in Figure 3B) in all client layer paths carried by the service layer path AB, and carries the AB link identifier "1"; In step 3, the node E detects the client-layer path alarm, and then can detect the AIS alarm information and extract the link identifier "1".

In a possible design, the first service layer path AB can also carry other client layer paths. If the first service layer path AB fails, then node B will not only send the first message through the first client layer path, but also The first message may be sent through other client layer paths, for example, the first message may be sent through all client layer paths carried.

In a possible design, node A can also send the first message in another direction through the first client layer path.

In the embodiment of the present application, the node on the client-level path can learn the path identifier of the failed service-level path, and then can accurately perform related processing. In other words, after the alarm monitoring point on the client layer receives the LF alarm information of the first client layer path, it can accurately determine the location of the faulty service layer path (or service layer link). If it is applied to the protection switching process, it can be Avoid path oscillation caused by frequent switching of protection paths.

As shown in Figure 4B, a schematic diagram of a network system provided by an embodiment of this application. The network system includes nodes A, B, C, D, E, and Z, where the working path of AZ is ABDEZ, BE area (or The protection path called the effective domain is BCE, and the end nodes of the protection path are node B and node E, that is, node B and node E can perform protection switching operations. The paths A-B, B-D, D-E, E-Z, B-C, and C-E are all standard Ethernet links, and the path identifiers are 1, 3, 5, 6, 2, and 4, respectively. The customer-level path A-B-D-E-Z includes 4 service-level paths, which are service-level paths A-B, B-D, D-E, and E-Z. .

If the path A-B fails, the first service layer path is A-B and the first client layer path is A-B-D-E-Z, the following solutions can be adopted:

1. The first service layer path A-B is a standard Ethernet link. If the standard Ethernet link fails, node B detects the link failure alarm information;

2. Node B sends the first message to node Z through the first client layer path. Specifically, it can be inserted into the first client layer path carried by the service layer path AB. AIS information (data unit shown in FIG. 3C), which carries Link ID "1";

3. Node E receives the first message, detects the AIS information, and extracts the link identifier "1" in it. When applied to the protection switching scenario, the node E compares the link identifier "1" with the link identifier in the local protection domain. It does not belong to the link in the protection domain and does not perform any operation. If the failed link is B-D or D-E, the AIS information detected by node E carries the identifier "3" or "5" and belongs to the link in the protection domain, and the corresponding protection switching operation is performed immediately.

As shown in Figure 4C, a schematic diagram of a network system provided by an embodiment of this application. The network system includes nodes A, B, C, D, E, and Z, where the working path of AZ is ABDEZ, and the protection path of AZ is ABCEZ, BE path is the effective area, and the end nodes of the protection path are node A and node Z, that is, node A and node Z can perform protection switching operations. Paths AB and EZ are standard Ethernet links, and the path identifiers are 1 and 6, respectively; paths BD, DE, BC, and CE are FlexE links, and the path identifiers are 3, 5, 2 and 4, respectively; the path identifier of the path BDE is 7; The path identifier of the path BCE is 8. The working client layer path A-B-D-E-Z includes three service layer paths, which are service layer paths A-B, B-D-E, and E-Z. The protection client layer path A-B-C-E-Z includes three service layer paths, namely service layer paths A-B, B-C-E and E-Z. Path B-D-E as a client-level path includes two service-level paths, namely service-level paths B-D and D-E. Path B-C-E as a client-level path includes two service-level paths, namely service-level paths B-C and C-E.

If the path B-D fails, the first service layer path is B-D, the first client layer path is B-D-E, the first client layer path B-D-E is the service layer path, and the corresponding second client layer path is A-B-D-E-Z. The following solutions can be used

1. The first service layer path B-D is a FlexE link. The FlexE link fails, and node D detects link failure alarm information.

2. The node D sends the first message to the node E through the first client layer path. Specifically, it can be inserted into the first client layer path carried by the service layer path BD to insert LF warning information (the coding block shown in FIG. 3A), The alarm information carries the FlexE link identifier "3" of the BD.

3. Node E detects the LF alarm information of the first client layer path, extracts the identifier "3", determines that the failed link is located in the path BDE, node E determines that the path BDE is faulty, and node E goes to the node through the second client layer path Z sends the second message, which may specifically be to insert AIS information (the data unit shown in FIG. 3C) into the second client layer path carried by the service layer path BDE, and carry the link identifier "7".

4. Node Z receives the second message, detects the AIS information, and extracts the link identifier "7". Applied in the protection switching scenario, node Z compares the identifier "7" with the link identifier in the local protection domain. If it belongs to the protection domain, node Z will perform protection switching immediately; if the link that fails is AB or EZ, the node The AIS information detected by Z carries the identifier "1" or "6" and belongs to a link outside the protection domain, so no protection switching operation is performed.

In a possible design, the above step 3 can also be: node E detects the LF alarm information of the first client layer path channel, extracts the identifier "3", determines that the failed link is located in the path BDE, and node E determines the path When the BDE fails, node E sends a second OAM message to node Z through the second client layer path. Specifically, it can be inserted into the second client layer path carried by the service layer path BDE (data unit shown in Figure 3C). ), and carry link identifiers "7" and "3" in the form of a stack.

The embodiments of this application can be applied to a multi-layer network. The first client layer path includes a first node (Node B) and a second node (Node E), and the first service layer path includes a third node (Node B) and a fourth node. Node (node D), the first client layer path further includes a third node (node B) and a fourth node (node D), the first service layer path is used to carry the first client layer path, the first node The second node and the second node are the end nodes of the first client layer path, and the third node and the fourth node are the end nodes of the first service layer path. The fourth node (node D) sends a first message to the second node through the first client layer path. The first message is used to indicate that the first service layer path has failed. The first message includes the information of the first service layer path. Path identification.

The first client layer path is used as the second service layer path, and the corresponding second client layer path includes the sixth node (node A), the first node (node B), the second node (node E) and the seventh node (node Z). ), the second service layer path includes a first node (node B) and a second node (node E), and the second service layer path is used to carry the second client layer path. The sixth node and the seventh node are the end nodes of the second client layer path, the first node and the second node are the intermediate nodes of the second client layer path, and the first node and the second node are the end nodes of the second service layer path . The second node (Node E) sends a second message to the seventh node through the second client layer path. The second message is used to indicate the failure of the second service layer path. The second message includes the information of the second service layer path. Path identifier. In addition, the second message may also include the path identifier of the first service layer path.

FIG. 5 shows a schematic block diagram of a fault transmission device 500 provided by an embodiment of the present application. The device 500 may correspond to the fault detection node described in the foregoing method, or may correspond to the chip or component of the fault detection node, and the device 500 Each module or unit in the above method may be used to execute each action or processing procedure performed by the fault detection node in the above method. As shown in FIG. 5, the fault transmission device 500 may include a processing unit 510 and a transceiver unit 520.

The processing unit 510 is configured to obtain failure information of a first service layer path failure;

The transceiver unit 520 is configured to send a first message to a second node through a first client layer path, the first message is used to indicate that the first service layer path has failed, and the first message includes the first service The path ID of the layer path.

As an optional embodiment, the first service layer path is a first service layer link, and the path identifier of the first service layer path is a link identifier of the first service layer link.

As an optional embodiment, the first service layer link is a link of a first FlexE group, and the link identifier of the first service layer link is a FlexE group Number of the first FlexE group.

As an optional embodiment, the first message is carried in at least one first MB/NB coding block.

As an optional embodiment, the first MB/NB encoding block is a first 64B/66B encoding block, and the first 64B/66B encoding block includes a type field and a path identification field, and the type field is used to indicate service When the layer path fails, the first message is carried in at least one first AIS data unit.

As an optional embodiment, the first MB/NB coding block is a control code block carrying LF information.

As an optional embodiment, the first message is carried in at least one first AIS data unit.

It should be understood that, for the specific process of each unit in the device 500 performing the foregoing corresponding steps, please refer to the description of the method embodiment in the foregoing, and for the sake of brevity, details are not repeated here.

FIG. 6 shows a schematic block diagram of a fault transmission device 600 provided by an embodiment of the present application. The device 600 may correspond to the fault receiving node described in the foregoing method, or may correspond to the chip or component of the fault receiving node, and the device 600 is Each module or unit may be used to execute each action or processing procedure performed by the fault receiving node in the foregoing method. As shown in FIG. 6, the fault transmission device 600 may include a transceiver unit 610 and a processing unit 620.

The transceiver unit 610 is configured to receive a first message through a first client layer path, the first message is used to indicate that the first service layer path has failed, and the first message includes the path of the first service layer path Logo

The processing unit 620 is configured to perform processing according to the path identifier of the first service layer path.

As an optional embodiment, the processing unit is configured to determine whether to switch the protection path according to the path identifier of the first service layer path.

As an optional embodiment, the processing unit 620 is configured to determine whether the path identifier of the first service layer path belongs to the path identifier in the preset path identifier table; if the path identifier of the first service layer path belongs to If the path identifier in the preset path identifier table is switched, the protection path is switched; if the path identifier of the first service layer path does not belong to the path identifier in the preset path identifier table, the protection path is not switched.

As an optional embodiment, the first message is carried in at least one first MB/NB coding block.

As an optional embodiment, the first message is carried in at least one first AIS data unit.

It should be understood that, for the specific process of each unit in the device 600 executing the above-mentioned corresponding steps, please refer to the description of the method embodiment in the foregoing, and for the sake of brevity, it is not repeated here.

The apparatus 500 of each of the above solutions has the function of implementing the corresponding steps performed by the fault detection node in the foregoing method, and the apparatus 600 of each of the foregoing solutions has the function of implementing the corresponding steps performed by the fault receiving node in the foregoing method; the functions can be implemented by hardware or software, It can also be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions; for example, the transceiver unit can be replaced by a communication interface, and the processing unit can be replaced by a processor to perform the transceiver operations and related processing operations in each method embodiment respectively. In the embodiment of the present application, the communication interface of a device is used for the device to communicate with other devices. Exemplarily, the communication interface may be a transmitter, a receiver, a transceiver, a circuit, a bus, a module, a pin, or another type of communication interface, which is not limited in the embodiment of the present application.

In a specific implementation process, the processor can be used to perform, for example, but not limited to, baseband related processing, and the communication interface can be used to perform, for example, but not limited to, information exchange. The above-mentioned devices may be respectively arranged on independent chips, or at least partly or fully arranged on the same chip. For example, the processor can be further divided into an analog baseband processor and a digital baseband processor, where the analog baseband processor and the communication interface can be integrated on the same chip, and the digital baseband processor can be set on a separate chip. With the continuous development of integrated circuit technology, more and more devices can be integrated on the same chip. For example, a digital baseband processor can be combined with a variety of application processors (such as but not limited to graphics processors, multimedia processors, etc.) Integrated on the same chip. Such a chip may be called a system on chip (SOC). Whether each device is independently arranged on different chips or integrated on one or more chips often depends on the specific needs of product design. The embodiment of the present application does not limit the specific implementation form of the foregoing device.

It can be understood that the processor involved in the foregoing embodiments can execute program instructions through a hardware platform with a processor and a communication interface to implement the functions involved in any design of the foregoing embodiments of this application, based on this As shown in FIG. 7, an embodiment of the present application provides a schematic block diagram of an apparatus 700. The apparatus 700 includes a processor 710, a communication interface 720, and a memory 730. The processor 710, the communication interface 720, and the memory 730 are coupled to communicate with each other. The memory 730 is used to store instructions, and the processor 710 is used to execute instructions stored in the memory 730 to control the communication interface 720 to send signals and/or receive signal. 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.

Wherein, in a possible implementation manner, if the device 700 is a fault detection node, the processor 710 is used to obtain fault information that the first service layer path fails; the communication interface 720 is used to route the first client layer path to the first server layer. The two nodes send a first message, where the first message is used to indicate that the first service layer path fails, and the first message includes the path identifier of the first service layer path.

In a possible implementation manner, if the device 700 is a faulty receiving node, the communication interface 720 is used to receive a first message through the first client layer path, and the first message is used to indicate that the first server layer path occurs. In case of failure, the first message includes the path identifier of the first service layer path; the processor 710 is configured to perform processing according to the path identifier of the first service layer path.

It should be understood that the device in FIG. 5 or the device in FIG. 6 in the embodiment of the present application can be implemented by the device 700 in FIG. 7, and can be used to execute the steps corresponding to the fault detection node and the fault receiving node in the foregoing method embodiment. And/or process.

It can be understood that the methods, processes, operations, or steps involved in the various designs described in the embodiments of the present application can be implemented in a one-to-one correspondence manner through computer software, electronic hardware, or a combination of computer software and electronic hardware. Corresponding realization. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. For example, considering the good versatility, low cost, software and hardware decoupling, etc., they can be implemented by executing program instructions, for example , Considering system performance and reliability, etc., it can be realized by using a dedicated circuit. Ordinary technicians can use different methods for each specific application to implement the described functions, which are not limited here.

According to the method provided in the embodiments of the present application, the present application also provides a computer program product, the computer program product includes: computer program code, when the computer program code runs on a computer, the computer executes the method in the above embodiment . The various embodiments in this application can also be combined with each other.

According to the method provided in the embodiments of the present application, the present application also provides a computer-readable medium with a program code stored in the computer-readable interpretation, and when the program code runs on a computer, the computer executes the method in the foregoing embodiment .

In the embodiments of the present application, it should be noted that the foregoing method embodiments in the embodiments of the present application may be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, the steps of the foregoing method embodiments may be completed by hardware integrated logic circuits in the processor or instructions in the form of software. The above-mentioned processor may be a general-purpose processor, a digital signal processor (digital signal processor, DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field programmable gate array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor may be a microprocessor or any conventional processor.

It can be understood that the memory in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electronic Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory. The volatile memory may be random access memory (RAM), which is used as an external cache. There are many different types of RAM, such as static RAM (SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate Synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (synchlink DRAM, SLDRAM) and direct memory bus random memory Take memory (direct rambus RAM, DR RAM).

It should be understood that, in the various embodiments of the present application, the size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, rather than corresponding to the embodiments of the present application. The implementation process constitutes any limitation.

The terms "first" and "second" appearing in this application are only used to distinguish different objects, and "first" and "second" themselves do not limit the actual order or function of the objects they modify. Any embodiment or design solution described as "exemplary", "example", "for example", "optionally" or "in certain implementations" in this application should not be construed as being better than other implementations. Examples or design solutions are more preferred or more advantageous. To be precise, these words are used to present related concepts in a concrete way.

Various messages/information/equipment/network elements/systems/devices/operations that may appear in this application have been assigned names. It is understandable that these specific names do not constitute a reference to related objects. Limited, the assigned name can be changed according to factors such as the scene, context, or usage habits. The understanding of the technical meaning of the technical terms in this application should be determined mainly from the functions and technical effects embodied/implemented in the technical solution .

In the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by software, it can be implemented in the form of a computer program product in whole or in part. The computer program product may include one or more computer instructions. When the computer program instructions are loaded and executed on the computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, network equipment, terminal equipment, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center. Transmission to another website, computer, server or data center via wired (such as coaxial cable, optical fiber, digital subscriber (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic disk), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

A person of ordinary skill in the art may be aware that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and conciseness of description, the specific working process of the above-described system, device, and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here. In the embodiments of the present application, provided that there is no logical contradiction, the embodiments can be mutually cited. For example, methods and/or terms between method embodiments can be mutually cited, such as functions and/or functions between device embodiments. Or terms may refer to each other, for example, functions and/or terms between the device embodiment and the method embodiment may refer to each other.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or It can be integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

In addition, the functional units in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.

The above are only specific implementations of this application, but the protection scope of this application is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this application. Should be covered within the scope of protection of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims (24)

A fault transmission method is applied to a fourth node, the first client layer path includes a first node and a second node, the first service layer path includes a third node and a fourth node, and the first client layer path also includes all nodes. The third node and the fourth node, the first service layer path is used to carry the first client layer path, the first node and the third node are the same node or the first node and the The third node is a different node, and is characterized in that it includes: Obtain failure information of the first service layer path failure; A first message is sent to the second node through the first client layer path, the first message is used to indicate that the first service layer path has failed, and the first message includes the path identifier of the first service layer path. The method according to claim 1, wherein the first service layer path is a first service layer link, and the path identifier of the first service layer path is a link of the first service layer link Logo. The method according to claim 2, wherein the first service layer link is a link of a first flexible Ethernet group, and the link identifier of the first service layer link is the first flexible Ethernet group. The flexible Ethernet group number of the Ethernet group. The method according to claim 1, wherein the first message is carried in at least one first MB/NB coding block. The method according to claim 4, wherein the first MB/NB encoding block is a first 64B/66B encoding block, and the first 64B/66B encoding block includes a type field and a path identification field, and the The type field is used to indicate that the first service layer path has failed. The method according to claim 4, wherein the first MB/NB code block is a control code block that carries local fault information. The method according to claim 1, wherein the first message is carried in at least one first alarm indication signal data unit. A fault transmission method, applied to a fifth node, the first client layer path includes a first node and a second node, the first service layer path includes a third node and a fourth node, and the first client layer path also includes all The third node and the fourth node, the first service layer path is used to carry the first client layer path, the first node and the third node are the same node or the first node and the The third node is a different node, the fifth node is a node between the fourth node and the second node, or the fifth node is the second node, characterized in that it includes: Receiving a first message through a first client layer path, the first message being used to indicate a failure of the first service layer path, the first message including a path identifier of the first service layer path; Process according to the path identifier of the first service layer path. The method according to claim 8, wherein the processing according to the path identifier of the first service layer path comprises: Determine whether to switch the protection path according to the path identifier of the first service layer path. The method according to claim 9, wherein the determining whether to switch the protection path according to the path identifier of the first service layer path comprises: Determining whether the path identifier of the first service layer path belongs to the path identifier in the preset path identifier table; If the path identifier of the first service layer path belongs to the path identifier in the preset path identifier table, switch the protection path; If the path identifier of the first service layer path does not belong to the path identifier in the preset path identifier table, the protection path is not switched. The method according to claim 8, wherein the first message is carried in at least one first MB/NB coding block. The method according to claim 8, wherein the first message is carried in at least one first alarm indication signal data unit. A fault transmission device, applied to a fourth node, a first client layer path includes a first node and a second node, the first service layer path includes a third node and a fourth node, and the first client layer path also includes all The third node and the fourth node, the first service layer path is used to carry the first client layer path, the first node and the third node are the same node or the first node and the The third node is a different node, and is characterized in that it includes: The processing unit is used to obtain the failure information of the first service layer path failure; The transceiver unit is configured to send a first message to a second node through a first client layer path, the first message is used to indicate that the first service layer path has failed, and the first message includes the first service layer The path ID of the path. The apparatus according to claim 13, wherein the first service layer path is a first service layer link, and the path identifier of the first service layer path is a link of the first service layer link Logo. The apparatus according to claim 14, wherein the first service layer link is a link of a first flexible Ethernet group, and the link identifier of the first service layer link is the first flexible Ethernet group. The flexible Ethernet group number of the Ethernet group. The apparatus according to claim 13, wherein the first message is carried in at least one first MB/NB coding block. The apparatus according to claim 16, wherein the first MB/NB encoding block is a first 64B/66B encoding block, and the first 64B/66B encoding block includes a type field and a path identification field, and The type field is used to indicate that the service layer path has failed. The apparatus according to claim 16, wherein the first MB/NB coding block is a control code block carrying local fault information. The apparatus according to claim 13, wherein the first message is carried in at least one first alarm indication signal data unit. A fault transmission device, applied to a fifth node, a first client layer path includes a first node and a second node, the first service layer path includes a third node and a fourth node, and the first client layer path also includes all The third node and the fourth node, the first service layer path is used to carry the first client layer path, the first node and the third node are the same node or the first node and the The third node is a different node, the fifth node is a node between the fourth node and the second node, or the fifth node is the second node, characterized in that it includes: The transceiver unit is configured to receive a first message through a first client layer path, the first message is used to indicate a failure of the first service layer path, and the first message includes the path identifier of the first service layer path ； The processing unit is configured to perform processing according to the path identifier of the first service layer path. The apparatus according to claim 20, wherein the processing unit is configured to determine whether to switch the protection path according to the path identifier of the first service layer path. The device according to claim 21, wherein the processing unit is configured to: Determining whether the path identifier of the first service layer path belongs to the path identifier in the preset path identifier table; If the path identifier of the first service layer path belongs to the path identifier in the preset path identifier table, switch the protection path; If the path identifier of the first service layer path does not belong to the path identifier in the preset path identifier table, the protection path is not switched. The device according to claim 20, wherein the first message is carried in at least one first MB/NB coding block. The device according to claim 20, wherein the first message is carried in at least one first alarm indication signal data unit.

Images