CN112104471A

CN112104471A - Fault transmission method and device

Info

Publication number: CN112104471A
Application number: CN201910527745.6A
Authority: CN
Inventors: 孙德胜; 杨春生; 丁力
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-06-18
Filing date: 2019-06-18
Publication date: 2020-12-18
Anticipated expiration: 2039-06-18
Also published as: CN112104471B; WO2020253791A1

Abstract

The embodiment of the present application provides a fault transmission method, which is applied to a fourth node, where a first client layer path includes a first node and a second node, a first service layer path includes a third node and a fourth node, the first client layer path further includes 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 third node are different nodes, and the method includes: acquiring fault information of a first service layer path which has a fault; and sending a first message to a second node through a first client layer path, wherein the first message is used for indicating that the first service layer path fails, and the first message comprises a path identifier of the first service layer path. The nodes on the client layer path can acquire the path identifier of the service layer path with the fault, and further can accurately perform related processing.

Description

Fault transmission method and device

Technical Field

The embodiment of the application relates to the technical field of communication, in particular to a fault transmission method and device.

Background

As shown in fig. 1, a working path of a-Z is a-B-D-E-Z, and a protection path of a B-E region (which may also be referred to as an active domain) is a B-C-E.

If the A-B link fails, an alarm is continuously generated, the protection path switching is triggered, the working path B-D-E and the protection path B-C-E are continuously switched, and path oscillation is formed. If the D-E link fails, an alarm is generated, the working path B-D-E is switched to the protection path B-C-E, and path oscillation cannot be generated.

Disclosure of Invention

The embodiment of the application provides a fault transmission method and device, which can avoid the generation of path oscillation.

In a first aspect, a fault transmission method is applied to a fourth node, where a first client layer path includes a first node and a second node, a first service layer path includes a third node and a fourth node, the first client layer 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 first node and the third node are different nodes, including: acquiring fault information of a first service layer path which has a fault; and sending a first message to a second node through a first client layer path, wherein the first message is used for indicating that the first service layer path fails, and the first message comprises a path identifier of the first service layer path.

In some possible implementations, 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 implementations, 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 number of the first flexible ethernet group.

In some possible implementations, the first message is carried on at least one first MB/NB encoded 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, where the type field is used to indicate that a service layer path fails.

In some possible implementations, the first MB/NB coding block is a control code block carrying local failure information.

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

In a second aspect, a fault transmission method is applied to a fifth node, where a first client layer path includes a first node and a second node, a first service layer path includes a third node and a fourth node, the first client layer path further includes 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 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, and the fault transmission method includes: receiving a first message through a first client layer path, wherein the first message is used for indicating that the first service layer path fails, and the first message comprises a path identifier of the first service layer path; and processing according to the path identifier of the first service layer path.

In some possible implementations, the processing according to the path identifier of the first service layer path includes: and determining whether to switch the protection path according to the path identifier of the first service layer path.

In some possible implementations, the determining whether to perform switching of a 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 path identifier in a preset path identifier table; if the path identifier of the first service layer path belongs to the path identifier in a preset path identifier table, switching a protection path; and if the path identifier of the first service layer path does not belong to the path identifier in the preset path identifier table, not switching the protection path.

In a third aspect, the present application provides a fault transmission apparatus for implementing the method in the first aspect and/or any possible implementation manner thereof. The device may be a network device, a device in the network device, or a device capable of being used in cooperation with the network device. In one design, the apparatus may include a module corresponding to performing the method/operation/step/action described in the first aspect and/or any possible implementation manner thereof, and the module may be a hardware circuit, a software circuit, or a combination of a hardware circuit and a software circuit. In one design, the apparatus may include a processing unit and a transceiver unit.

In a fourth aspect, the present application provides a fault transmission apparatus for implementing the method of the second aspect and/or any possible implementation manner thereof. The device may be a network device, a device in the network device, or a device capable of being used in cooperation with the network device. In one design, the apparatus may include a module corresponding to the method/operation/step/action described in the second aspect and/or any possible implementation manner thereof, and the module may be a hardware circuit, a software circuit, or a combination of a hardware circuit and a software circuit. In one design, the apparatus may include a processing unit and a transceiver unit.

In a fifth aspect, the present application provides a fault transmission apparatus comprising a processor configured to implement the method described in the first aspect and/or any possible implementation manner thereof. The apparatus may further comprise a memory, optionally for storing instructions, which when executed by the processor may implement the method described in the above first aspect and/or any possible implementation thereof. The apparatus may also include a communication interface for the apparatus to communicate with other devices, which may be, for example, a transceiver, circuit, bus, module, pin, or other type of communication interface.

In a sixth aspect, the present application provides a fault transmission apparatus comprising a processor configured to implement the method described in the second aspect and/or any possible implementation manner thereof. The apparatus may further comprise a memory, optionally for storing instructions, which when executed by the processor may implement the method described in the second aspect above and/or any possible implementation thereof. The apparatus may also include a communication interface for the apparatus to communicate with other devices.

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

The system comprises 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 having stored thereon computer instructions which, when executed on a computer, cause the computer to perform the method of the above aspects and any possible designs thereof.

In a ninth aspect, the present application provides a chip comprising a processor. The processor is adapted to perform the method of the above aspects and any possible implementation thereof.

Optionally, the chip further comprises a memory, the memory being coupled to the processor.

Further optionally, the chip further comprises a communication interface.

In a tenth aspect, the present application provides a computer program product comprising computer program code which, when run on a computer, causes the computer to perform the method of the above aspects and any possible design thereof.

Drawings

Fig. 1 is a schematic diagram of a network system according to an embodiment of the present application.

Fig. 2 is a schematic diagram of a fault transmission method according to an embodiment of the present application.

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

Fig. 3B is a schematic diagram of another 64B/66B coding block carrying a first message according to an embodiment of the present application.

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

Fig. 4A is a schematic diagram of another network system according to an embodiment of the present application.

Fig. 4B is a schematic diagram of another network system according to an embodiment of the present application.

Fig. 4C is a schematic diagram of another network system according to an embodiment of the present application.

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

Fig. 6 is a schematic block diagram of another fault transmission apparatus provided in an embodiment of the present application.

Fig. 7 is a schematic block diagram of another fault transmission apparatus provided in an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments.

The technical solution provided in the embodiment of the present application may be applied to a flexible ethernet Network, and may also be applied to other types of networks, such as an ethernet Network, an Optical Transport Network (OTN) Network, a Synchronous Digital Hierarchy (SDH) Network, a Metro Transport Network (MTN), and the like.

As shown in fig. 1, a schematic diagram of a network system provided in this embodiment of the present application includes a node A, B, C, D, E, Z, where a working path of a-Z is a-B-D-E-Z, and a protection path of a B-E area (which may also be referred to as an active domain) is B-C-E.

The following explains part of the nouns referred to in the embodiments of the present application

1. A service layer path and a client layer path.

One customer layer path may comprise at least one service layer path, and as shown in FIG. 1, customer layer paths A-B-D-E-Z comprise service layer paths A-B, service layer paths B-D, service layer paths D-E, and service layer paths E-Z.

The service layer path and the client layer path are opposite, and the service layer path is used for carrying the corresponding client layer path. As shown in FIG. 1, path A-B is a service layer path of path A-B-D-E-Z, and service layer path A-B is used to carry client layer path A-B-D-E-Z. In addition, the path A-B can also be used as a client layer path, and a plurality of service layer paths are configured at the lower layer.

2. A path and a link.

A path may include at least one link, as shown in fig. 1, where service layer path a-B, service layer path B-D, service layer path D-E, and service layer path E-Z each include one link, and client layer path a-B-D-E-Z includes 4 links, link a-B, link B-D, link D-E, and link E-Z, respectively.

If node F is also included between service layer paths A-B, service layer path A-B includes two links, link A-F and link F-B, respectively.

For ease of description, service layer paths A-B, service layer paths B-D, service layer paths D-E, and service layer paths E-Z in the following embodiments each comprise a link and may therefore also be referred to as service layer links A-B, service layer links B-D, service layer links D-E, and service layer links E-Z.

3. Operation, Administration and Maintenance (OAM).

Typically including error detection, fault detection, delay measurement, path discovery, etc. mechanisms in the network.

4. Flexible Ethernet (flexle Ethernet, FlexE).

The IEEE 802.3-based ethernet defined by the Institute of Electrical and Electronics Engineers (IEEE) is used as a service interface in various occasions and has been applied with great success, but as the technology is developed, the bandwidth granularity is larger, and the larger the difference is, the larger the deviation from the actual application requirement is. The bandwidth required by mainstream applications may not belong to any ethernet standard rate, for example, 50Gbps has resource waste if 100GE is used for transmission, while 200Gbps currently has no corresponding ethernet standard particle to carry. It is desirable to have a flexible bandwidth port (virtual connection) that can share one or several ethernet physical interfaces, for example, 2 40GE ports and 2 10GE ports share one 100G physical interface. The concept of Flexible Ethernet (FlexE) comes from the beginning, and specifically, several Ethernet Physical layer (PHY) devices are bound into a FlexE Group (Group), and the functions of Physical layer channelization (subrate) and the like, so as to meet the port application requirement of Flexible bandwidth. Thus, the Media Access Control (MAC) rate provided by FlexE may be greater than the rate of a single PHY (achieved by bundling) or less than the rate of a single PHY (achieved by channelization). One FlexE Group has one FlexE Group Number.

As shown in fig. 2, a fault transmission method provided in the embodiment of the present application includes:

s201, the fault detection node detects that the first service layer path has a fault.

S202, a fault detection node sends a first message through a first client layer path, wherein the first message is used for indicating that the first service layer path has a fault, and the first message comprises a path identifier of the first service layer path.

S203, the fault receiving node receives the first message through the first client layer path.

And S204, the fault receiving node processes according to the path identifier of the first service layer path.

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

With reference to FIG. 1, the first client layer path A-B-D-E-Z includes 4 service layer paths, which are respectively service layer path A-B, service layer path B-D, service layer path D-E, and service layer path E-Z. Assume that service layer path a-B fails, i.e., service layer path a-B is the first service layer path. The first client layer path comprises a first node (node a) and a second node (node Z), the first service layer path comprises a third node (node a) and a fourth node (node B), the first client layer path further comprises a third node (node a) and a fourth node (node B), and the first service layer path is used for carrying the first client layer path. Wherein the first node and the second node are end nodes of the first client layer path and the third node and the fourth node are 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, and in one possible design, the first node (node a) and the third node (node B) are different nodes, e.g., when the first service layer path includes a third node (node B) and a fourth node (node D). In one possible design, node Z is a first node and node a is a second node. In one possible design, node B is the third node and node a is the fourth node.

A fourth node (node B), acting as a failure detection node, may detect that the first service layer path a-B failed, and send a first message to the second node (node Z) via the first client layer path, the first message indicating that the first service layer path a-B failed, the first message including a path identification of the first service layer path a-B.

The second node (node Z) may act as a fault receiving node and intermediate nodes between the fourth node (node B) and the second node (node Z) may also act as fault receiving nodes, which intermediate nodes are also on the first customer layer path and may therefore act as fault receiving nodes. The failed receiving node may be processed according to the path identifier of the first service layer path.

The first message may be sent through various data formats, may be sent at various network layers, for example, may be sent in an ethernet physical layer, and may also be sent in a link layer, which is illustrated in fig. 3A, 3B and 3C, where fig. 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 on at least one first MB/NB coding block, which is a coding block of an ethernet PCS, e.g. a 64B/66B coding block. As shown in fig. 3A, a 64B/66B coding block carrying a first message provided for the embodiment of the present application is an extension of a control coding block carrying Local Failure (LF) information defined in IEEE802.3, where 0x4B is used to indicate that the coding block is of an O code type, where three fields of D1, D2 and D3 include 24 bits, and the upper 4 bits (20 bits in total) of D1, D2 and D3 may be used as a path identification field for carrying a path identification of a first service layer path, and the two lowest bits of D3 being 01 identify that the coding block carries LF information. As shown in fig. 3B, another 64B/66B encoded block carrying a first message provided in this embodiment of the present application includes fields of Type (Type), Value 1(Value 1), Value 2(Value 2), and Value 3(Value 3), Value 4(Value 4), Value 5(Value 5), sequence number (Seq), and cyclic redundancy check (cyclic redundancy check CRC) -4, where the Type field may be set to indicate that a service layer path fails, and 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 a path identification field to carry a 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 extended based on an AIS data unit defined by ITU-T g.8013. As shown in fig. 3C, a first AIS data unit carrying a first message provided in this embodiment of the present application includes a maintenance entity group level (MEL) field, a Version (Version) field, an operation code (OpCode) field, identification (Flags) fields, type-length-value (TLV) Offset (Offset) fields, a path identification field, a Reserved (Reserved) field, and an End (End) TLV field. Wherein the MEL field is used to identify the level of AIS messages in the network; version can take the value of 0; the OpCode may take on the value 33; the first five bits of the Flags field are reserved, and the last three bits represent the message period; TLV Offset represents an Offset to the End TLV field, and can take a value of 3 since the extended AIS data unit is increased by 3 bytes; in the extended 3 bytes, 20 bits are used as a path identification field, and 4 bits are used as a Reserved field; the End TLV indicates the End of the AIS data element and may take the value 0.

As shown in fig. 4A, a schematic diagram of a network system provided in this embodiment of the present application includes a node A, B, C, D, E, Z, where a working path of a-Z is a-B-D-E-Z, a protection path of a B-E area (which may also be referred to as an active domain) is B-C-E, and end nodes of the protection path are node B and node E, that is, node B and node E may perform protection switching operation. Wherein the paths A-B, B-D, D-E, E-Z, B-C and C-E are Flexe links, and the path identifications are 1, 3, 5, 6, 2 and 4 respectively. The client layer paths A-B-D-E-Z include 4 service layer paths, service layer paths A-B, B-D, D-E and E-Z, respectively.

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 scheme may be adopted:

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

2. The node B sends a first message to the node Z through the first client layer path, which may specifically be to insert LF alarm information (a coding block shown in fig. 3 a) into the first client layer path carried by the first service layer path a-B, where the alarm information carries a FlexE link identifier "1" of the node B.

3. And the node E detects the LF alarm information of the first client layer path, extracts the identifier '1' and determines the position of the failed link. When the method is applied to a protection switching scene, the node E compares the identifier '1' with each link identifier related to the protection domain of the current segment, finds that the failed link does not belong to the protection domain, and does not perform protection switching operation. If the failed link is B-D or D-E, the LF alarm detected by the node E carries the identifier '3' or '5', and belongs to the link in the protection domain, and protection switching is performed.

In one possible design, step 2 above may also be: the node B inserts AIS alarm information (the coding block shown in fig. 3B) in all the client layer paths carried by the service layer paths a-B and carries an a-B link identifier "1"; in step 3, the node E detects the client layer path alarm, and further can detect the AIS alarm information and extract the link identifier '1' therein.

In one possible design, the first service layer path a-B may also carry other client layer paths, and if the first service layer path a-B fails, the node B may send the first message through other client layer paths in addition to sending the first message through the first client layer path, for example, the first message may be sent through all of the client layer paths of the bearer.

In one possible design, node a may also send the first message in the other direction via the first client layer path.

In the embodiment of the application, the nodes on the client layer path can acquire the path identifier of the service layer path with the fault, and further can accurately perform related processing. That is, after receiving the LF alarm information of the first client layer path, the alarm monitoring point on the client layer can accurately determine the location of the failed service layer path (or service layer link), and if the application is applied to the protection switching process, the problem of path oscillation caused by frequent switching of the protection path can be avoided.

As shown in fig. 4B, a schematic diagram of a network system provided in this embodiment of the present application includes a node A, B, C, D, E, Z, where a working path of a-Z is a-B-D-E-Z, a protection path of a B-E area (which may also be referred to as an active domain) is B-C-E, and end nodes of the protection path are node B and node E, that is, node B and node E may perform protection switching operation. Where paths A-B, B-D, D-E, E-Z, B-C and C-E are standard Ethernet links with

path designations

1, 3, 5, 6, 2, and 4, respectively. The client layer paths A-B-D-E-Z include 4 service layer paths, service layer paths A-B, B-D, D-E and E-Z, respectively. .

1. the first service layer path A-B is a standard Ethernet link, the standard Ethernet link has a fault, and the node B detects the link fault alarm information;

2. node B sends a first message to node Z through the first client layer path, which may specifically be to insert AIS information (data unit shown in fig. 3C) in the first client layer path carried by service layer path a-B, where the AIS information carries link identifier "1";

3. node E receives the first message, detects the AIS information, and extracts the link identification "1" therein. When the method is applied to a protection switching scene, the node E compares the link identifier '1' with the link identifier in the local protection domain, 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 the node E carries the identifier '3' or '5', and belongs to the link in the protection domain, corresponding protection switching operation is immediately carried out.

As shown in fig. 4C, a schematic diagram of a network system provided in this embodiment of the present application includes a node A, B, C, D, E, Z, where a working path of a-Z is a-B-D-E-Z, a protection path of a-Z is a-B-C-E-Z, a B-E path is an effective area, end nodes of the protection path are node a and node Z, that is, node a and node Z may perform protection switching operation. The paths A-B and E-Z are standard Ethernet links, and the path identifiers are respectively 1 and 6; paths B-D, D-E, B-C and C-E are Flexe links, and path identifications are 3, 5, 2 and 4 respectively; the path identification of path B-D-E is 7; the path identification of path B-C-E is 8. The working customer layer paths A-B-D-E-Z include 3 service layer paths, service layer paths A-B, B-D-E and E-Z, respectively. The protection client layer path a-B-C-E-Z includes 3 service layer paths, service layer paths a-B, B-C-E and E-Z, respectively. The paths B-D-E are client layer paths and comprise 2 service layer paths, namely service layer paths B-D and D-E. The path B-C-E is used as a client layer path and comprises 2 service layer paths which are respectively a service layer path B-C and a service layer path 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 taken as the service layer path, and the corresponding second client layer path is A-B-D-E-Z, the following scheme can be adopted

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

2. The node D sends a first message to the node E through the first client layer path, which may specifically be to insert LF alarm information (a coding block shown in fig. 3 a) into the first client layer path carried by the service layer path B-D, where the alarm information carries a FlexE link identifier "3" of the service layer path B-D.

3. The node E detects LF alarm information of the first client layer path, extracts the identifier "3", determines that the failed link is located in the path B-D-E, determines that the path B-D-E fails, and sends a second message to the node Z through the second client layer path, which may specifically be inserting AIS information (a data unit shown in fig. 3C) into the second client layer path carried by the service layer path B-D-E, and carrying the link identifier "7".

4. And the node Z receives the second message, detects the AIS information and extracts a link identifier '7'. When the method is applied to a protection switching scene, the node Z compares the identifier 7 with a link identifier in a local protection domain, belongs to the protection domain, and immediately performs protection switching operation; if the failed link is A-B or E-Z, the AIS information detected by the node Z carries the identifier '1' or '6', and belongs to the link outside the protection domain, the protection switching operation is not performed.

In one possible design, step 3 above may also be: the node E detects LF alarm information of the first client layer path channel, extracts the identifier "3", determines that the failed link is located in the path B-D-E, determines that the path B-D-E fails, and sends a second OAM message to the node Z through the second client layer path, which may specifically be inserting an AIS data unit (the data unit shown in fig. 3C) in the second client layer path carried by the service layer path B-D-E, and carrying the link identifiers "7" and "3" in a stack form.

The embodiment of the application can be applied to a multilayer network, wherein the first client layer path comprises a first node (node B) and a second node (node E), the first service layer path comprises a third node (node B) and a fourth node (node D), the first client layer path further comprises a third node (node B) and a fourth node (node D), the first service layer path is used for bearing the first client layer path, the first node and the second node are end nodes of the first client layer path, and the third node and the fourth node are end nodes of the first service layer path. A fourth node (node D) sends a first message to the second node over the first client layer path, the first message indicating that the first service layer path failed, the first message comprising a path identification of the first service layer path.

The first client layer path is used as a second service layer path, the corresponding second client layer path comprises a sixth node (node A), a first node (node B), a second node (node E) and a seventh node (node Z), the second service layer path comprises the first node (node B) and the second node (node E), and the second service layer path is used for bearing the second client layer path. The sixth node and the seventh node are end nodes of the second client layer path, the first node and the second node are intermediate nodes of the second client layer path, and the first node and the second node are 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, where the second message is used to indicate that the second service layer path fails, and the second message includes a path identifier of the second service layer path, and in addition, the second message may also include a path identifier of the first service layer path.

Fig. 5 shows a schematic block diagram of a fault transmission apparatus 500 provided in this embodiment of the application, where the apparatus 500 may correspond to a fault detection node described in the foregoing method, and may also correspond to a chip or a component of the fault detection node, and each module or unit in the apparatus 500 may be respectively configured to execute each action or process performed by the fault detection node in the foregoing method, as shown in fig. 5, and the fault transmission apparatus 500 may include a processing unit 510 and a transceiver unit 520.

A processing unit 510, configured to obtain failure information that a first service layer path fails;

a transceiving unit 520, configured to send a first message to a second node through a first client layer path, where the first message is used to indicate that the first service layer path fails, and the first message includes a path identifier of the first service 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 alternative embodiment, the first message is carried on at least one first MB/NB encoded block.

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

As an alternative 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 sake of brevity, detailed descriptions of the method embodiments above for the specific processes of the units in the apparatus 500 to perform the corresponding steps are omitted here.

Fig. 6 shows a schematic block diagram of a fault transmission apparatus 600 provided in this embodiment of the present application, where the apparatus 600 may correspond to the fault receiving node described in the above method, and may also correspond to a chip or a component of the fault receiving node, and each module or unit in the apparatus 600 may be respectively configured to execute each action or process performed by the fault receiving node in the above method, as shown in fig. 6, and the fault transmission apparatus 600 may include a transceiver unit 610 and a processing unit 620.

A transceiver unit 610, configured to receive a first message through a first client layer path, where the first message is used to indicate that the first service layer path fails, and the first message includes a path identifier of the first service layer path;

a processing unit 620, 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 perform switching of a protection path according to a path identifier of the first service layer path.

As an alternative embodiment, the processing unit 620 is configured to: determining whether the path identifier of the first service layer path belongs to a path identifier in a preset path identifier table; if the path identifier of the first service layer path belongs to the path identifier in a preset path identifier table, switching a protection path; and if the path identifier of the first service layer path does not belong to the path identifier in the preset path identifier table, not switching the protection path.

It should be understood that, for the sake of brevity, detailed descriptions of the method embodiments above for the specific processes of the units in the apparatus 600 to execute the corresponding steps are omitted here.

The apparatus 500 of each of the above aspects has a function of implementing the corresponding steps performed by the failure detection node in the above method, and the apparatus 600 of each of the above aspects has a function of implementing the corresponding steps performed by the failure reception node in the above method; the functions can be realized by hardware or software, and the corresponding software can be executed by hardware. The hardware or software comprises one or more modules corresponding to the functions; for example, the transceiver unit may be replaced by a communication interface, and the processing unit may be replaced by a processor, which performs the transceiver operation and the related processing operation in the respective method embodiments, respectively. In an embodiment of the present application, a communication interface of an apparatus is used for the apparatus to communicate with other devices. For example, the communication interface may be a transmitter, a receiver, a transceiver, a circuit, a bus, a module, a pin, or other types of communication interfaces, and the embodiments of the present application are not limited thereto.

In particular implementations, the processor may be configured to perform, for example and without limitation, baseband-related processing, and the communication interface may be configured to perform, for example and without limitation, information exchange. The above devices may be respectively disposed on separate chips, or at least a part or all of the devices may be disposed on the same chip. For example, the processor may be further divided into an analog baseband processor and a digital baseband processor, wherein the analog baseband processor may be integrated with the communication interface on the same chip, and the digital baseband processor may be disposed on a separate chip. With the development of integrated circuit technology, more and more devices can be integrated on the same chip, for example, a digital baseband processor can be integrated on the same chip with various application processors (such as, but not limited to, a graphics processor, a multimedia processor, etc.). Such a chip may be referred to as a System On Chip (SOC). Whether each device is separately located on a different chip or integrated on one or more chips often depends on the specific needs of the product design. The embodiment of the present application does not limit the specific implementation form of the above device.

It is understood that, for the processors referred to in the foregoing embodiments, the functions referred to in any design of the foregoing embodiments of the present application may be implemented by executing program instructions through a hardware platform having the processors and a communication interface, respectively, and based on this, as shown in fig. 7, the present application embodiment provides a schematic block diagram of an apparatus 700, where the apparatus 700 includes: processor 710, communication interface 720, and memory 730. Wherein processor 710, communication interface 720, and memory 730 are coupled to communicate with each other, memory 730 is configured to store instructions, and processor 710 is configured to execute instructions stored by memory 730 to control communication interface 720 to send signals and/or receive signals. The coupling in the embodiments of the present application is an indirect coupling or a communication connection between devices, units or modules, and may be an electrical, mechanical or other form for information interaction between the devices, units or modules.

In a possible implementation manner, if the apparatus 700 is a failure detection node, the processor 710 is configured to obtain failure information that a first service layer path fails; communication interface 720 is configured to send a first message to a second node via a first client layer path, the first message indicating that the first service layer path failed, the first message including a path identification of the first service layer path.

In a possible implementation manner, if the apparatus 700 is a failure receiving node, the communication interface 720 is configured to receive a first message through a first client layer path, where the first message is used to indicate that the first service layer path fails, and the first message includes a 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 apparatus in fig. 5 or the apparatus in fig. 6 in the embodiment of the present application may be implemented by the apparatus 700 in fig. 7, and may be configured to perform various steps and/or flows corresponding to the failure detection node and the failure receiving node in the above-described method embodiments.

It should be understood that the various design-related methods, procedures, operations, or steps described in the embodiments of this 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. Whether the functions are executed in a hardware or software manner depends on specific applications and design constraints of the technical scheme, for example, aspects such as software and hardware decoupling with good universality and low cost are considered, the functions can be realized in a manner of executing program instructions, and aspects such as system performance and reliability are considered, and special circuits can be adopted for realization. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

According to the method provided by the embodiment of the present application, the present application further provides a computer program product, which includes: computer program code which, when run on a computer, causes the computer to perform the method in the above-described embodiments. The various embodiments in this application may also be combined with each other.

According to the method provided by the embodiment of the present application, the present application also provides a computer readable medium, the computer readable medium stores program code, and when the program code runs on a computer, the computer is caused to execute the method in the above embodiment.

In the embodiment of the present application, it should be noted that the above method embodiments of the embodiment of the present application may be applied to a processor, or implemented by a processor. The processor may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The processor may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, or discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or any conventional processor or the like.

It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. There are many different types of RAM, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM), and direct bus RAM (DR RAM).

It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

The appearances of the phrases "first," "second," and the like in this application are only for purposes of distinguishing between different items and the phrases "first," "second," and the like do not by themselves limit the actual order or function of the items so modified. Any embodiment or design described herein as "exemplary," e.g., "optionally" or "in certain implementations" is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of these words is intended to present relevant concepts in a concrete fashion.

Various objects such as various messages/information/devices/network elements/systems/devices/operations/etc. that may appear in the present application are named, it is understood that these specific names do not constitute limitations on related objects, and the named names may vary with factors such as scenes, contexts, or usage habits, and the understanding of the technical meaning of the technical terms in the present application should be mainly determined from the functions and technical effects embodied/performed in the technical solutions.

The above embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product may include one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, a network appliance, a terminal device or other programmable apparatus. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic disk), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again. In the embodiments of the present application, the embodiments may refer to each other, for example, methods and/or terms between the embodiments of the method may refer to each other, for example, functions and/or terms between the embodiments of the apparatus and the embodiments of the method may refer to each other, without logical contradiction.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

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

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A fault transmission method applied to a fourth node, where a first client layer path includes a first node and a second node, a first service layer path includes a third node and a fourth node, the first client layer 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 first node and the third node are different nodes, the method comprising:

acquiring fault information of a first service layer path which has a fault;

and sending a first message to a second node through a first client layer path, wherein the first message is used for indicating that the first service layer path fails, and the first message comprises a path identifier of the first service layer path.

2. The method of claim 1, wherein the first service layer path is a first service layer link, and wherein the path identifier of the first service layer path is a link identifier of the first service layer link.

3. The method of claim 2, wherein the first service layer link is a link of a first flexible Ethernet group, and wherein the link identification of the first service layer link is a flexible Ethernet group number of the first flexible Ethernet group.

4. The method of claim 1, wherein the first message is carried on at least one first MB/NB encoded block.

5. The method of claim 4, wherein the first MB/NB coding block is a first 64B/66B coding block, and wherein the first 64B/66B coding block comprises a type field and a path identification field, and wherein the type field is used for indicating that the first service layer path has failed.

6. The method of claim 4, wherein the first MB/NB encoded block is a control code block carrying local failure information.

7. The method of claim 1, wherein the first message is carried in at least one first alarm indication signal data unit.

8. A fault transmission method applied to a fifth node, where a first client layer path includes a first node and a second node, a first service layer path includes a third node and a fourth node, the first client layer path further includes 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 third node are different nodes, and the fifth node is a node between the fourth node and the second node or the fifth node is the second node, the fault transmission method comprising:

receiving a first message through a first client layer path, wherein the first message is used for indicating that the first service layer path fails, and the first message comprises a path identifier of the first service layer path;

and processing according to the path identifier of the first service layer path.

9. The method of claim 8, wherein the processing according to the path identifier of the first service layer path comprises:

and determining whether to switch the protection path according to the path identifier of the first service layer path.

10. The method of 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 a path identifier in a preset path identifier table;

if the path identifier of the first service layer path belongs to the path identifier in a preset path identifier table, switching a protection path;

and if the path identifier of the first service layer path does not belong to the path identifier in the preset path identifier table, not switching the protection path.

11. The method of claim 8, wherein the first message is carried on at least one first MB/NB encoded block.

12. The method of claim 8, wherein the first message is carried in at least one first alarm indication signal data unit.

13. A fault transmission apparatus applied to a fourth node, wherein a first client layer path includes a first node and a second node, a first service layer path includes a third node and a fourth node, the first client layer path further includes the third node and the fourth node, the first service layer path is used for carrying the first client layer path, the first node and the third node are the same node or the first node and the third node are different nodes, the apparatus comprising:

the processing unit is used for acquiring fault information of a fault of a first service layer path;

a transceiving unit, configured to send a first message to a second node through a first client layer path, where the first message is used to indicate that the first service layer path fails, and the first message includes a path identifier of the first service layer path.

14. The apparatus of claim 13, wherein the first service layer path is a first service layer link, and wherein the path identifier of the first service layer path is a link identifier of the first service layer link.

15. The apparatus of claim 14, wherein the first service layer link is a link of a first flexible ethernet group, and wherein the link identification of the first service layer link is a flexible ethernet group number of the first flexible ethernet group.

16. The apparatus of claim 13, wherein the first message is carried on at least one first MB/NB encoded block.

17. The apparatus of claim 16, wherein the first MB/NB coding block is a first 64B/66B coding block, wherein the first 64B/66B coding block comprises a type field and a path identification field, and wherein the type field is used to indicate a service layer path failure.

18. The apparatus of claim 16, wherein the first MB/NB code block is a control code block carrying local failure information.

19. The apparatus of claim 13, wherein the first message is carried in at least one first alarm indication signal data unit.

20. A fault transmission apparatus applied to a fifth node, where a first client layer path includes a first node and a second node, a first service layer path includes a third node and a fourth node, the first client layer path further includes 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 third node are different nodes, and the fifth node is a node between the fourth node and the second node or the fifth node is the second node, the fault transmission apparatus comprising:

a transceiver unit, configured to receive a first message through a first client layer path, where the first message is used to indicate that the first service layer path fails, and the first message includes a path identifier of the first service layer path;

and the processing unit is used for processing according to the path identifier of the first service layer path.

21. The apparatus of claim 20, wherein the processing unit is configured to determine whether to perform protection path switching according to a path identifier of the first service layer path.

22. The apparatus of claim 21, wherein the processing unit is configured to:

23. The apparatus of claim 20, wherein the first message is carried on at least one first MB/NB encoded block.

24. The apparatus of claim 20, wherein the first message is carried in at least one first alarm indication signal data unit.