WO2023197770A1

WO2023197770A1 - Fault notification method and apparatus

Info

Publication number: WO2023197770A1
Application number: PCT/CN2023/079288
Authority: WO
Inventors: 余伟伟; 李日欣; 周勇波
Original assignee: 华为技术有限公司
Priority date: 2022-04-15
Filing date: 2023-03-02
Publication date: 2023-10-19

Abstract

Disclosed in the embodiments of the present application is a fault notification method. After a first communication apparatus determines that an FGU layer works abnormally, the first communication apparatus can send fault indication information to an upstream node, wherein the fault indication information is used for indicating a far-end fault. It can be seen therefrom that by using the present solution, after the first communication apparatus determines that the FGU layer works abnormally, the first communication apparatus can notify the upstream node of the far-end fault. In this way, the upstream node can quickly determine the far-end fault on the basis of the fault indication information which is sent by the first communication apparatus. Compared with the prior art, the present solution involves a mechanism of notifying an upstream node of a far-end fault. Compared with the fact in the prior art that only an edge node that bears a fine granularity service can sense a fault, an upstream node of a first communication apparatus, which senses an FGU layer fault, can learn of a far-end fault. The fact that an upstream node of a first communication apparatus learns of a far-end fault helps to quickly register the reason for the far-end fault, and reduces the influence, on a fine granularity service, of an FGU layer fault of the first communication apparatus.

Description

A fault notification method and device

This application claims priority from the following patent applications, the entire contents of which are incorporated herein by reference.

1. Submit a Chinese patent application to the China Patent Office on April 15, 2022, with the application number 202210399017.3 and the invention title "A communication method and equipment";

2. Submit a Chinese patent application to the China Patent Office on May 20, 2022, with the application number 202210552411.6 and the invention title "A fault notification method and device".

Technical field

The present application relates to the field of communications, and in particular, to a fault notification method and device.

Background technique

Flexible Ethernet (FlexE) technology has the advantage of flexibly allocating bandwidth on demand, which can meet the needs of mobile bearer, home broadband, dedicated line access and other network scenarios. Therefore, the application of FlexE technology is becoming more and more widespread.

FlexE technology can support fine-grained services. In one example, the time slot (slot) corresponding to the FlexE large bandwidth can be further divided into multiple sub-slots (sub-slots) for carrying fine-grained services. Among them: the services carried by the time slots corresponding to the FlexE large bandwidth can also be called large-granularity services, and the fine-grained services can also be called small-granularity services. In the following description, "small particles" and "fine-grained" may be used interchangeably.

Currently, when a certain communication device detects a small particle fault, other communication devices cannot quickly determine the fault.

Contents of the invention

Embodiments of the present application provide a fault notification method, which can enable some other communication devices carrying small-granularity services to quickly determine remote faults.

In a first aspect, embodiments of the present application provide a fault notification method. In one example, the fault notification method can be executed by a first communication device, and the first communication device can determine a fine granularity unit (FGU). If the FGU layer works abnormally, after the first communication device determines that the FGU layer works abnormally, it can send fault indication information to the upstream node, where the fault indication information is used to indicate a remote fault. It can be seen that with this solution, after determining that the FGU layer is working abnormally, the first communication device can notify the upstream node of the remote fault. In this way, the upstream node can quickly determine the fault based on the fault indication information sent by the first communication device. Remote failure. Compared with traditional technology, this solution includes a mechanism to notify upstream nodes of remote faults. Correspondingly, compared with edge nodes that only carry small-granularity services in traditional technologies, which can sense faults, the first communication device that senses FGU layer faults The upstream node of the first communication device can learn about the remote fault. Correspondingly, the upstream node of the first communication device learns about the remote fault, which is also conducive to quickly locating the cause of the remote fault and reducing the impact on small-granular services due to the FGU layer failure of the first communication device. Influence. For example, the upstream node of the first communication device may perform fault location-related measures, and so on.

In a possible implementation manner, in order to allow the upstream node to determine the specific situation of the remote fault, the remote fault may be specifically a remote FGU layer fault.

In a possible implementation, the first communication device can carry the fault indication information in a base frame overhead and send it to the upstream node. In this way, the upstream node can obtain the information by parsing the base frame overhead. Describe the fault indication information.

In a possible implementation manner, the fault indication information may be carried in a reserved field of the base frame overhead. In this way, there is no need to add a new field in the base frame overhead to carry the fault indication information.

In a possible implementation, considering that the flag field of the base frame overhead has not been used, therefore, The fault indication information may be carried in the flag field of the base frame overhead. In this way, there is no need to add a new field in the base frame overhead to carry the fault indication information.

In a possible implementation, the fault indication information can be carried through operations administration maintenance (OAM) code blocks of the metro transport network (metro transport network, MTN) channel layer. In this way, the first communication device can send the fault indication information to the upstream node through the OAM code block of the MTN channel layer. Correspondingly, the upstream node can parse the OAM code block of the MTN channel layer. Obtain the fault indication information.

In a possible implementation, a new OAM code block of the MTN channel layer can be extended to carry the fault indication information. For this case, the type field in the OAM code block of the MTN channel layer can be used to indicate that the OAM code block carries the fault indication information.

In a possible implementation manner, the OAM code block of the MTN channel layer may be an existing basic OAM code block. For this method, the existing basic OAM code blocks of the MTN channel layer can be used to carry the fault indication information, and there is no need to expand the OAM code blocks of the new MTN channel layer. For this situation, in one example, the reserved field in the basic OAM code block can be used to carry the fault indication information. In another example, the remote defect indication (remote defect indication) in the basic OAM code block can be used. defect indication (RDI) to carry the fault indication information.

In a possible implementation, considering that loss of multiframe (LOM), loss of frame (LOF), and service layer anomalies of the FGU layer can all reflect FGU layer anomalies, therefore, the first A communication device may determine that the FGU layer is working abnormally when one or more of LOM, LOF, and service layer anomalies of the FGU layer are detected. Further, the first communication device may determine that the FGU layer is working abnormally. When it is determined that the FGU layer is working abnormally, fault indication information is sent to the upstream node.

In a possible implementation, the service layer of the FGU layer is an MTN channel layer or an Ethernet physical layer.

In a possible implementation, the first communication device is an intermediate node in an end-to-end path of small-granule services carried by the FGU layer. For this situation, when the intermediate node of the end-to-end path determines that the FGU layer is working abnormally, it can notify the upstream node of the remote fault, so that the upstream node can quickly determine the remote fault based on the fault indication information notified by the first communication device. Fault.

In a possible implementation manner, the upstream node is an intermediate node in the end-to-end path of the small-granule service carried by the FGU layer. For this situation, when the FGU layer of the downstream node of the intermediate node works abnormally, the intermediate node can learn the remote fault information. Furthermore, the intermediate node can further perform corresponding measures to minimize the impact on small particles due to remote faults. Impact on business packet transmission.

In a possible implementation, the first communication device can continuously detect the working status of the FGU layer. When the first communication device determines that the FGU layer is working normally, it can send fault recovery information to the upstream node. Failure recovery information is used to indicate that the remote end is normal. In this way, after receiving the fault recovery information, the upstream node can further perform corresponding processing measures, such as performing time slot synchronization with the first communication device, so as to resume normal transmission of small-granularity services as soon as possible.

In a possible implementation manner, the remote end being normal may be embodied as the remote end FGU layer being normal.

In a second aspect, embodiments of the present application provide a fault notification method. In one example, the method can be applied to the second communication device. Both the second communication device and the first communication device are nodes on the path carrying small-granularity services. The second communication device is an upstream node of the first communication device. The second communication device may receive the fault indication information sent by the first communication device. The fault indication information is used to indicate a remote fault. Then, the second communication device may determine that the first communication device is connected based on the fault indication information. The device has malfunctioned. It can be seen that using this solution, the second communication device as the upstream node of the first communication device can receive the fault indication information sent by the first communication device. In this way, the second communication device can quickly send the fault indication information based on the first communication device. fault indication information to determine the remote fault. Compared with traditional technology, this solution includes a mechanism for the downstream node to notify the upstream node of the remote fault. Correspondingly, the upstream node of the first communication device learns the remote fault, which is also conducive to quickly locating the cause of the remote fault and reducing the risk of remote faults. The impact of the FGU layer failure of the first communication device on small-granule services. For example, the second communication device, which is an upstream node of the first communication device, may perform measures related to fault location, and so on.

In a possible implementation manner, the remote fault includes: a remote fine-grained basic unit FGU layer fault.

In a possible implementation manner, the fault indication information is carried through base frame overhead.

In a possible implementation manner, the fault indication information is carried in a reserved field of the base frame overhead.

In a possible implementation manner, the fault indication information is carried through an identification flag field of the base frame overhead.

In a possible implementation manner, the fault indication information is carried through the operation and maintenance management OAM code block of the MTN channel layer of the metropolitan area transmission network.

In a possible implementation, the type field in the OAM code block is used to indicate that the OAM code block carries the fault indication information.

In a possible implementation, the OAM code block is a basic OAM code block.

In a possible implementation manner, the fault indication information is remote fault indication information RDI.

In a possible implementation manner, the fault indication information includes remote fault indication information RDI.

In a possible implementation manner, the fault indication information includes remote fault indication information RDI and indication information used to indicate that the remote fault is a remote FGU layer fault.

In a possible implementation, the fault indication information is carried through a reserved field in the basic OAM code block.

In a possible implementation, after receiving the fault indication information, the second communication device may also send alarm information to the control management device, where the alarm information is used to indicate that the first communication device is working abnormally. Notifying the alarm information to the control and management equipment can cause the control and management equipment to determine that the first communication device is working abnormally, and accordingly, cause the control and management equipment to perform corresponding processing measures. For example, notify other nodes on the end-to-end path carrying the small-granularity service that the first communication device is working abnormally, etc.

In a possible implementation manner, the first communication device working abnormally includes: the FGU layer of the first communication device working abnormally.

In a possible implementation, the method further includes: receiving fault recovery information sent by the first communication device, where the fault recovery information is used to indicate that the remote end is normal.

In a possible implementation, after the second communication device receives the fault recovery information sent by the first communication device, the second communication device can perform time slot synchronization with the first communication device, so that after the time slot synchronization is performed, , transmitting small-grain services based on the time slots after synchronization.

In a possible implementation, the first communication device is an intermediate node in an end-to-end path of small-granule services carried by the FGU layer.

In a possible implementation manner, the upstream node is an intermediate node in the end-to-end path of the small-granule service carried by the FGU layer.

In a third aspect, embodiments of the present application provide a status notification method, which can be applied to the first communication device. In one example, the first communication device may determine the working status of the FGU layer, and then send status indication information to the upstream node, where the status indication information is used to indicate the working status of the FGU layer. It can be seen that using this solution, the first communication device can notify the working status of the FGU layer to the upstream node, so that the upstream node can quickly determine the working status of the FGU layer of the first communication device. Compared with the traditional technology, this solution includes a mechanism to notify the upstream node of the remote FGU layer status. Accordingly, the upstream node of the first communication device can perform corresponding processing measures based on the status indication information. For example, in one example, the status indication information indicates a remote fault, then the upstream node can learn about the remote fault, and perform related measures to locate the fault, and so on. For another example, in one example, if the status indication information indicates that the FGU layer is working normally, then the upstream node can send service data to the downstream node normally, or send information related to small-granule time slot negotiation.

In a possible implementation manner, the working status of the FGU layer may specifically be that the FGU layer is working normally. In this case, the upstream node can determine that the FGU layer of the first communication device is working normally based on the status indication information.

In a possible implementation manner, the status indication information is carried through base frame overhead.

In a possible implementation manner, the status indication information is carried in a reserved field of the base frame overhead.

In a possible implementation manner, the status indication information is carried through an identification flag field of the base frame overhead.

In a possible implementation manner, the status indication information may be carried through the operation and maintenance management OAM code block of the MTN channel layer. In this way, the first communication device can send the status indication information to the upstream node through the OAM code block of the MTN channel layer. Correspondingly, the upstream node can parse the OAM code block of the MTN channel layer. Obtain the status indication information.

In a possible implementation, a new OAM code block of the MTN channel layer can be extended to carry the status indication information. For this case, the type field in the OAM code block of the MTN channel layer can be used to indicate that the OAM code block carries the status indication information.

In a possible implementation manner, the OAM code block of the MTN channel layer may be an existing basic OAM code block. For this method, the existing basic OAM code blocks of the MTN channel layer can be used to carry the status indication information, and there is no need to expand the OAM code blocks of the new MTN channel layer. For this situation, in one example, the reserved field in the basic OAM code block can be used to carry the status indication information.

In the fourth aspect, the embodiment of the present application provides a status notification method. In an example, the method can be applied on the second communication device. Both the second communication device and the first communication device are nodes on a path carrying small-granularity services, and the second communication device is an upstream node of the first communication device. The second communication device may receive the status indication information sent by the first communication device, and the status indication information is used to indicate the working status of the remote FGU layer; and then, the second communication device may determine the third communication device based on the status indication information. The working status of the FGU layer of a communication device. Compared with the traditional technology, this solution includes a mechanism to notify the upstream node of the remote FGU layer status. Accordingly, the second communication device, which is the upstream node of the first communication device, can perform corresponding processing measures based on the status indication information. For example, in one example, the status indication information indicates a remote fault, then the second communication device can learn about the remote fault, and perform related measures to locate the fault, and so on. For another example, in one example, the status indication information indicates that the FGU layer is working normally, then the second communication device can normally send service data to the downstream node, or send information related to small-granularity time slot negotiation.

In a possible implementation manner, the working status of the FGU layer includes: the FGU layer is working normally.

In a possible implementation manner, the status indication information is carried through the operation and maintenance management OAM code block of the MTN channel layer of the metropolitan area transmission network.

In a possible implementation, the type field in the OAM code block is used to indicate that the OAM code block carries the status indication information.

In a possible implementation, the OAM code block is a basic OAM code block.

In a possible implementation, the status indication information is carried through a reserved field in the basic OAM code block.

In a fifth aspect, embodiments of the present application provide a first communication device, where the first communication device includes a transceiver unit and a processing unit. The transceiver unit is configured to perform reception and/or transmission-related operations performed by the first communication device in the above-mentioned first aspect and various possible implementations of the first aspect; the processing unit is configured to perform the above-mentioned third aspect. Operations other than reception and/or transmission related operations performed by the first communication device in one aspect and various possible implementations of the first aspect. In a specific implementation, the transceiver unit may include a receiving unit and/or a sending unit, the receiving unit is used to perform reception-related operations, and the sending unit is used to perform sending-related operations.

In a specific example, the first communication device may include a processing unit and a sending unit.

The processing unit is used to determine the working abnormality of the fine-grained unit FGU layer; the sending unit is used to send fault indication information to the upstream node, and the fault indication information is used to indicate a remote fault.

In a possible implementation manner, the remote fault includes: a remote FGU layer fault.

In a possible implementation, the OAM code block is a basic OAM code block.

In a possible implementation, the processing unit is configured to: detect one or more of multiframe loss LOM, frame loss LOF, and FGU service layer abnormality detection.

In a possible implementation, the processing unit is also used to: determine that the FGU layer is working normally; the sending unit is also used to send fault recovery information to the upstream node, and the fault recovery information is It is normal to indicate the remote end.

In a possible implementation manner, the remote end being normal includes: the remote FGU layer is normal.

In a sixth aspect, embodiments of the present application provide a second communication device, where the second communication device includes a transceiver unit and a processing unit. The transceiver unit is configured to perform reception and/or transmission-related operations performed by the second communication device in the above-mentioned second aspect and various possible implementations of the second aspect; the processing unit is configured to perform the above-mentioned third aspect. Operations other than receiving and/or sending related operations performed by the second communication device in the second aspect and various possible implementations of the second aspect. In a specific implementation, the transceiver unit may include a receiving unit and/or a sending unit, the receiving unit is used to perform reception-related operations, and the sending unit is used to perform sending-related operations.

In a specific example, the second communication device may include a receiving unit and a processing unit.

The receiving unit is configured to receive fault indication information sent by the first communication device, where the fault indication information is used to indicate a remote fault; the processing unit is configured to determine that the first communication device is connected based on the fault indication information. The device has malfunctioned.

In a possible implementation, the OAM code block is a basic OAM code block.

In a possible implementation, the device further includes:

A sending unit, configured to send alarm information to the control management device, where the alarm information is used to indicate abnormal operation of the first communication device.

In a possible implementation, the receiving unit is further configured to receive fault recovery information sent by the first communication device, where the fault recovery information is used to indicate that the remote end is normal.

In a possible implementation, the processing unit is further configured to perform time slot synchronization with the first communication device.

In a seventh aspect, embodiments of the present application provide a first communication device, where the first communication device includes a transceiver unit and a processing unit. The transceiver unit is configured to perform reception and/or transmission-related operations performed by the first communication device in the above-mentioned third aspect and various possible implementations of the third aspect; the processing unit is configured to perform the above-mentioned third aspect. Operations other than receiving and/or sending related operations performed by the first communication device in the third aspect and various possible implementations of the third aspect. In a specific implementation, the transceiver unit may include a receiving unit and/or a sending unit, the receiving unit is used to perform reception-related operations, and the sending unit is used to perform sending-related operations.

The processing unit is used to determine the working status of the fine-grained unit FGU layer; the sending unit is used to send status indication information to the upstream node, and the status indication information is used to indicate the working status of the FGU layer.

In a possible implementation, the OAM code block is a basic OAM code block.

In an eighth aspect, an embodiment of the present application provides a second communication device, where the second communication device includes a transceiver unit and a processing unit. The transceiver unit is configured to perform reception and/or transmission-related operations performed by the second communication device in the above-mentioned fourth aspect and various possible implementations of the fourth aspect; the processing unit is configured to perform the above-mentioned third aspect. Operations other than receiving and/or sending related operations performed by the second communication device in the fourth aspect and various possible implementations of the fourth aspect. In a specific implementation, the transceiver unit may include a receiving unit and/or a sending unit, the receiving unit is used to perform reception-related operations, and the sending unit is used to perform sending-related operations.

The receiving unit is configured to receive status indication information sent by the first communication device, and the status indication information is used to indicate the working status of the remote fine-grained unit FGU layer; the processing unit is configured to based on the status indication information , determine the working status of the FGU layer of the first communication device.

In a possible implementation, the OAM code block is a basic OAM code block.

In a ninth aspect, the present application provides a communication device, the communication device includes a memory and a processor; the memory is used to store program code; the processor is used to run instructions in the program code, so that The communication device performs the above first aspect and the method described in any one of the first aspects, or causes the communication device to perform the above second aspect and the method described in any one of the second aspects, or causes the The communication device performs the above third aspect and the method described in any one of the third aspects, or causes the communication device to perform the above fourth aspect and the method described in any one of the fourth aspects.

In a tenth aspect, the present application provides a communication device. The communication device includes a communication interface and a processor. Through the communication interface and the processor, the communication device is caused to execute the method described in any of the preceding aspects and Part or all of the operations of any implementation of the method described in any aspect. In a specific implementation manner, the communication interface is used to perform the sending and receiving operations performed by the communication device described in any one of the above first aspect and the first aspect, and the processor is used to perform the above first aspect and the first aspect. Other operations other than the transceiver operation performed by the communication device described in any one of the above; or, the communication interface is used to perform the transceiver operation performed by the communication device according to any one of the above second aspect and the second aspect, so The processor is used to perform other operations other than the sending and receiving operations performed by the communication device described in any one of the above second aspect and the second aspect; or, the communication interface is used to perform the above third aspect and any one of the third aspects. A transceiver operation performed by the communication device described in one of the above, the processor is configured to perform other operations other than the transceiver operation performed by the communication device described in any one of the above third aspect and the third aspect; or, the communication The interface is used to perform the transceiver operation performed by the communication device described in any one of the fourth aspect and the fourth aspect, and the processor is used to perform the except operation performed by the communication device described in any one of the fourth aspect and the fourth aspect. Operations other than sending and receiving operations.

In an eleventh aspect, embodiments of the present application provide a computer-readable storage medium, including instructions or computer programs that, when run on a processor, execute any of the methods described in the first aspect above, or execute the above The method described in any one of the second aspects, or the method described in any one of the third aspects, or the method described in any one of the fourth aspects.

In a twelfth aspect, embodiments of the present application provide a computer program product, including a computer program product that, when run on a processor, executes the above first aspect and the method described in any one of the first aspects, or executes The method described in any one of the above second aspect and the second aspect, or performing the method described in any one of the above third aspect and the third aspect, or performing the method described in any one of the above fourth aspect and the fourth aspect. method.

In a thirteenth aspect, embodiments of the present application provide a communication system. The communication system includes: a communication device that performs the above first aspect and the method described in any one of the above first aspects; and a communication device that performs the above second aspect and the above method. A communication device that performs the method according to any one of the second aspects; or a communication device that performs the above third aspect and any one of the above third aspect methods and performs any one of the above fourth aspects and any one of the above fourth aspects. Communication device according to the method.

Description of the drawings

In order to explain the technical solutions in the embodiments of the present application or the prior art more clearly, the following will describe the embodiments or the prior art. The drawings required for the technical description are briefly introduced. Obviously, the drawings in the following description are only some embodiments recorded in this application. For those of ordinary skill in the art, without exerting creative efforts, Other drawings can also be obtained from these drawings.

Figure 1a is a schematic diagram of an SPN architecture supporting small particle technology provided by an embodiment of the present application;

Figure 1b is a schematic diagram of a network architecture provided by an embodiment of the present application;

Figure 1c is a schematic diagram of OAM insertion of an MTNP provided by an embodiment of the present application;

Figure 1d is a schematic structural diagram of an fg-BU provided by an embodiment of the present application;

Figure 1e is a schematic structural diagram of another FGU base frame provided by an embodiment of the present application;

Figure 1f is a schematic structural diagram of another FGU base frame overhead provided by an embodiment of the present application;

Figure 1g is a schematic diagram of an exemplary application scenario provided by the embodiment of the present application;

Figure 2 is a signaling interaction diagram of a fault notification method provided by an embodiment of the present application;

Figure 3 is a schematic structural diagram of an OAM code block provided by an embodiment of the present application;

Figure 4 is a schematic flow chart of a fault notification method provided by an embodiment of the present application;

Figure 5 is a signaling interaction diagram of a status notification method provided by an embodiment of the present application;

Figure 6 is a schematic flow chart of a fault notification method provided by an embodiment of the present application;

Figure 7 is a schematic flow chart of a fault notification method provided by an embodiment of the present application;

Figure 8 is a schematic flow chart of a status notification method provided by an embodiment of the present application;

Figure 9 is a schematic flowchart of a status notification method provided by an embodiment of the present application;

Figure 10 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

Figure 11 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

Figure 12 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

Figure 13 is a schematic structural diagram of a communication device provided by an embodiment of the present application.

Detailed ways

Embodiments of the present application provide a fault notification method and device, which can enable some other communication devices carrying small-granularity services to quickly determine remote faults.

The embodiment of the present application provides a time slot negotiation method for small-granularity services in FlexE, which can make the small-granularity time slots between two network devices transmitting small-granularity services consistent.

To facilitate understanding, the relevant content of FlexE is first introduced.

FlexE group: One or more PHYs included in each FlexE group. When multiple PHYs are included, the multiple PHYs are physically independent. Network equipment that applies FlexE technology can use PHY numbers to identify which PHYs are included in a FlexE group to achieve logical bundling of multiple PHYs. For example, each PHY number can be identified by a number between 1 and 254, with 0 and 255 being reserved numbers. A PHY number can correspond to an interface on the network device. Two adjacent network devices need to use the same number to identify the same PHY. The number of each PHY included in a FlexE group does not need to be consecutive. Normally, there is one FlexE group between two network devices, but this application does not limit the existence of only one FlexE group between two network devices, that is, there can also be multiple FlexE groups between two network devices. One PHY can be used to carry at least one client, and one client can transmit on at least one PHY. FlexE can support the mapping and transmission of any number of different FlexE Clients on any set of PHYs, thereby realizing functions such as PHY bundling, channelization, and sub-rates.

FlexE Client: Corresponds to various user interfaces or bandwidth of the network. FlexE Client represents the customer data flow transmitted in the specified time slot (one time slot or multiple time slots) on FlexE Group. One FlexE Group can carry multiple FlexE Clients, and one FlexE Client can correspond to one to multiple user business data flows. (Also known as MAC Client). FlexE client can be flexibly configured according to bandwidth requirements and supports Ethernet media access control (MAC) data flows at various rates (such as 10G, 40G, n*25G data flows, and even non-standard rate data flows), such as The data stream can be passed to the FlexE shim layer through 64B/66B encoding. Clients sent through the same FlexE group need to share the same clock, and these clients need to be adapted according to the allocated time slot rate. In this application, the FlexE client (also known as the FlexE client interface) can be used to transmit the corresponding FlexE client's business data flow. FlexE client interface is a logical interface. Each FlexE interface can be logically divided into one or more FlexE client interfaces. Each FlexE interface can be divided into multiple time slots in the time domain. Each FlexE client interface occupies at least one of the multiple time slots. time slot. Among them: 64/66B refers to the data code block including 66 bits. The first two bits of the 66 bits are synchronization bits, and the last 64 bits are data bits. At the PCS layer, 64/66B can be extracted through the first two synchronization bits. .

FlexE shim: As an additional logical layer inserted between the MAC and PHY (PCS sublayer) of the traditional Ethernet architecture, it is the core architecture of FlexE technology based on the time slot distribution mechanism. For the sender, the main function of FlexE shim is to encapsulate data into pre-divided time slots. Then, according to the FlexE time slot table, each divided time slot is mapped to the PHY in the FlexE group for transmission. Among them, each time slot is mapped to a PHY in the FlexE group. Taking 100GE PHY as an example, the FlexE Shim layer can divide each 100GE PHY in the FlexE Group into 20 time slots (slots) data carrying channels, and the corresponding bandwidth of each slot is 5Gbps. Every time the PHY sends 1023*20Slot of 64/66B data, an overhead FlexE (Overhead, OH) will be inserted to inform the receiving end how to parse the received data.

Small-granularity services: In some embodiments, slots corresponding to large bandwidths can be further divided into multiple sub-slots for carrying customer services with smaller bandwidth requirements. The above-mentioned services are also called small-granularity services. Particle business. For example, the above-mentioned large bandwidth can be understood as the bandwidth corresponding to the service layer of small-granularity services. For example, when the service layer of the small-granularity service is the MTN channel layer, and the bandwidth of the MTN channel layer is 5Gbps, the slot corresponding to the large bandwidth of 5Gbps is further divided according to the granularity of 10Mbps, and divided into 480 sub-slots. These 480 sub-slots -slot is used to carry small-granule services. For example, the first sub-slot, the third sub-slot, and the fifth sub-slot among the 480 sub-slots are used to carry small-granule services 1. For another example, when the service layer of small-granularity services is the 10GE Ethernet physical layer, the corresponding large bandwidth is further divided into multiple sub-slots according to finer granularity for carrying small-granularity services. It can be seen that the bandwidth granularity of small particles is finer, and small particle services refer to services that have relatively small bandwidth requirements. For example, the bandwidth requirement of the power dedicated line service is 10Mbps. At this time, small particle technology can be used to allocate designated bandwidth to the power dedicated line service to carry the business traffic of the power dedicated line service. The above-mentioned power dedicated line service is a small Particle business.

When transmitting small-granule services, for the sending end, in one example, FlexE shim can encapsulate the data into pre-divided sub-slots for transmission according to the time slot configuration of the small-granule. For the receiving end, FlexE shim can restore the data received through the slot with a corresponding bandwidth of 5Gbps into the original small-granule service data according to the time slot configuration of the small-granule and continue transmission. In another example, for the sender, the MTN path adaptation function can be used to encapsulate the data into the corresponding sub-slot for transmission. For the receiver, the MTN path adaptation function can be used. The configuration function will restore the data received through the slot corresponding to the bandwidth of 5Gbps to the original Small granular business data and continue to transmit. In one example, fine granularity service data may be carried in a fine granularity unit (FGU) base frame. In one example, the fine granularity unit may also be called a fine granularity basic unit (fg-BU). In the following description, the two may be used interchangeably.

Regarding the FlexE OH insertion method and the structure of the overhead frame, for a specific implementation method, you can refer to the relevant description of FlexE in the Electrical and Optical Internet Forum (OIF), which will not be detailed here.

Next, we introduce a possible Slicing Packet Network (SPN) architecture that supports small particle technology. Refer to Figure 1a, which is a schematic diagram of an SPN architecture supporting small particle technology provided by an embodiment of the present application.

As shown in Figure 1a, the SPN architecture includes:

Slicing packet layer (SPL), slicing channel layer (SCL), slicing transport layer (STL), integrated management and control software defined network (SDN) slicing control plane and Ultra-high-precision event frequency synchronization technology. in:

SCL includes FGU layer, MTN path (MTN path, MTNP) layer and MTN section (MTN Section, MTNS) layer. Among them: the FGU layer provides end-to-end deterministic low-latency N*10Mbps granular hard slicing channels for small-granularity services. The FGU layer is an independent sub-layer and can be flexibly carried on the MTN channel layer or the Ethernet physical layer as needed. In other words, the service layer of the FGU layer can be the MTN channel layer or the Ethernet physical layer.

STL adds a 10GE Ethernet physical layer interface based on the original high-speed Ethernet physical layer interface. The 10GE Ethernet physical layer can be used in customer-premises equipment (CPE) scenarios to directly carry the FGU layer.

Next, taking the MTN channel layer carrying small-granule services as an example, the MTNS and MTNP are introduced from the perspectives of transmitting side behavior and receiving side behavior.

First, the sending side behavior and receiving side behavior of MTNS are introduced.

In one example, taking 100GBASE-R PHY as an example, MTNS provides point-to-point connections, is responsible for slotting adjacent nodes connected with Ethernet PHY, and provides bonding, sub-rate, channelization Function. MTNS is bidirectionally symmetrical. Here we take one data transmission direction as an example.

On the sending side, MTNS inserts a special O code block into the 66B code block sequence. A D code block is inserted after every 1023*20 66B code blocks, and a D code block is inserted after every 1023*20 66B code blocks. , a total of 7 D code blocks need to be inserted. After inserting the 7th D code block, and after an interval of 1023*20 code blocks, a special O code block is inserted. In this way, a total of 8*(1023*20+1) code blocks constitute an MTNS frame.

The O code block plus the aforementioned 7 D code blocks constitute the overhead of the MTNS frame. The overhead carries some point-to-point link configuration information indicating MTNS, such as time slot configuration information, segment layer group configuration information, etc.

MTNS continuously sends data to the receiving end according to the above frame structure. The continuous MTNS frame is equivalent to a 66B code block stream, which is converted into bits, optical signals, or other analog signals such as electrical pulses according to the lower PHY layer protocol defined by Ethernet IEEE 802.3, and is sent out from the transmitting side device.

On the receiving side, first according to the protocol of the Ethernet lower PHY layer, the received signal (such as bits, optical signals, or other analog signals such as electrical pulses) is identified by the O code block, and the MTNS frame is locked. Frame header, according to the fixed count, you can know that the next overhead code block appears after 1023*20 code blocks. Correspondingly, the receiving side can determine the position of the data corresponding to each time slot in the received signal based on the O code block.

MTNS can only provide point-to-point connections, while MTNP is responsible for providing "end-to-end channel connections" from network entrance to network exit. MTNP provides end-to-end rigid hard pipe connections and provides management, maintenance and protection (OAM and protection, OAMP )Function. A typical networking for MTNP can be referred to as shown in Figure 1b. Figure 1b is a schematic diagram of a network architecture provided by an embodiment of the present application.

Next, the sending side behavior and receiving side behavior of MTNP are introduced in conjunction with Figure 1b.

As shown in Figure 1b, end-to-end MTNP is included between provider edge (PE) 1 and PE2, and point-to-point MTNS is included between PE1 and PE2.

On the network to network interface (NNI) side of PE1, the MTNP layer obtains the client signal from the MAC layer, and the client signal can be a MAC frame. The MAC mentioned here may be a processing module of the MAC layer. After the MTNP layer obtains the MAC frame, it encodes the MAC frame into a sequence of 64/66B code blocks. Specifically, each MAC frame will be encoded into a series of 66B code block sequences defined by a start code block (S code block) and an end code block (i.e. T code block), and a series of MAC frame sequences will be encoded. into a series of 66B code block sequences. If there is no valid MAC frame waiting to be sent, then MTNP will fill the 66B code block with an idle (idle, I) code block, thereby ensuring that MTNP's hard pipeline has data sent at all times. The OAM&P function provided by MTNP can be introduced with reference to Figure 1c. Figure 1c is a schematic diagram of OAM insertion of an MTNP provided by an embodiment of the present application.

As shown in Figure 1c, OAM&P is implemented by inserting special O code blocks into the 66B code block sequence. The above special O code blocks can also be called OAM code blocks. OAM uses special encoding to load OAM information to implement OAM functions, including connectivity detection, error monitoring, protection switching, etc.

MTNP OAM code blocks can only be inserted at the source end and extracted at the sink end. Currently, the intermediate node between the source end and the sink end does not support modifying and parsing the information carried in the OAM code blocks. In other words, after PE1 completes the MTNP OAM insertion in MTNP, it maps the 66B code block sequence containing the OAM code block to the MTNS time slot specified according to the pre-configuration. Subsequently, the NNI sending side of PE1 sends the data according to the behavior of the MTNS sending side described above.

The receiving side of the P node first identifies the MTNS frame according to the above-mentioned receiving side behavior of MTNS. Subsequently, the MTNP data is restored from the designated MTNS time slot according to the pre-configured configuration. The P node next performs MTNP forwarding. It should be noted here that the essential difference between MTNP forwarding, IP forwarding and MAC bridge forwarding is that MTNP forwarding exclusively occupies the device forwarding resources and does not support statistical multiplexing. The entrance and exit of the network node (such as P node) need to be configured the same Number of MTNS slots.

As mentioned above, in some embodiments, the slot corresponding to the large bandwidth can be further divided into multiple sub-slots for carrying small-granularity services. For example, a slot corresponding to a bandwidth of 5Gbps is further divided according to a granularity of 10Mbps and divided into 480 sub-slots. These 480 sub-slots are used to carry small-granularity services. For this situation, MTN FGU can further divide 480 10Mbps time slots into 5Gbps MTNP in a hierarchical manner. In this scenario, MTNP and MTN FGU can be decoupled. At this time, MTNP serves as the service layer of MTN FGU. In one example, the structure of the fg-BU may be as shown in Figure 1d. Figure 1d is a schematic structural diagram of an fg-BU provided by an embodiment of the present application.

As shown in Figure 1d, the fg-BU includes an FGU base frame overhead 110 and an FGU base frame payload 120. The FGU base frame overhead 110 may be used to carry time slot information of small particles, and the FGU base frame payload 120 may be used to carry the small particle service data. Among them, the small-granular time slot information can be the mapping relationship between sub-slot and sub-client. Among them, sub-client is similar to FlexE Client and also corresponds to various user interfaces or bandwidths of the network. and The difference between FlexE Client is that sub-client represents the customer data stream transmitted on sub-slot, and one sub-client can correspond to one or more sub-slots.

For the scenario where the slot corresponding to the bandwidth of 5Gbps is further divided according to the granularity of 10Mbps, in one example, an FGU base frame can include 24 sub-slots, each sub-slot includes 65 bytes, and each sub-slot can carry 8 65-bit code block. In other words, the aforementioned base frame payload 120 may include 65*24=1560 bytes. 20 FGU base frames form a multiframe, and 24×20=480 sub-time slots are provided within the multiframe. In an example, after the fg-BU shown in Figure 1d is 64/66B encoded, 1 S0 code block, 196 D code blocks and 1 T code block can be obtained.

For the NNI sending side of PE1, the MTN FGU layer is the same as MTNP. It first encodes the MAC frame client signal into a 66B code block sequence, and then inserts the OAM code block. It should be noted at this time that the OAM code blocks of small granular MTNP (fgMTNP) are inserted into the MTN FGU layer, not the OAM code blocks of MTNP. Subsequently, a series of 66B code block sequences containing fgMTNP OAM code blocks are mapped into the 10Mbps time slot specified in the fg-BU according to the pre-configuration.

The fg-BU sequence itself is actually a series of 66B code blocks, which can be equivalent to the client signal of MTNP. After inserting the MTNP OAM code block, it is mapped into the time slot designated by MTNS according to the behavior of the MTNS sending side described above.

The receiving side of the P node restores the MTNP signal according to the behavior of the receiving side of the MTNP described above, and then extracts the OAM code block in the MTNP. After the receiving side of the P node recovers the MTNP signal, it can complete the framing of the fg-BU by searching for S code blocks.

The P node performs fgMTNP forwarding. fgMTNP forwarding is the same as MTNP forwarding. It is TDM forwarding. It occupies the device forwarding resources exclusively and does not support statistical multiplexing. The P node will not terminate the OAM code block of fgMTNP.

The sending side behavior of P node is the reverse process of the receiving side behavior of P node, which will not be described in detail here. In addition, the receiving side behavior of the PE2 node is the reverse process of the sending side behavior of the PE1 node, and will not be explained in detail this time.

Next, the FGU base frame overhead 110 in the FGU base frame will be described.

Refer to Figure 1e, which is a schematic structural diagram of an FGU base frame overhead. The FGU base frame overhead shown in Figure 1e includes 56 bits, where:

Bit 0 and bit 1 are reserved fields.

Bits 2 to 7 are the multiframe indication (MFI) field, which is used to indicate the number of each FGU base frame in the multiframe. In the scenario where the above 20 FGU base frames form a multiframe, MFI The value range of the field is 0-19. For the first FGU base frame in the multiframe, the value of the MFI field is 0. For the second FGU base frame in the multiframe, the value of the MFI field is 1, and so on. By analogy, for the last FGU base frame in the multiframe, the value of the MFI field is 19.

The 8th to 9th bits are a flag field, and the flag field is used to indicate the content carried by the 16th to 48th bits of the base frame overhead. In one example, the 16th to 48th bits of the base frame overhead are used to carry a general communications channel (GCC) field; in another example, the 16th to 48th bits of the base frame overhead 48 bits are used to carry client identifier (identifier, ID), sub-slot ID and other information. In the embodiment of this application, the client ID carried in the FGU base frame overhead refers to the sub-client ID. For example, client ID 1 mentioned below refers to sub-client ID 1.

The 10th bit is a reserved field.

Bits 11 to 55 are used to carry base frame overhead information.

In one example, the China Mobile enterprise standard defines bits 11 to 15 of the base frame overhead.

See Figure 1f, which is a schematic structural diagram of another FGU base frame overhead provided by an embodiment of the present application. As described in Figure 1f:

The 11th bit is a reserved field.

The 12th bit is the downstream done (DD) indication bit. The DD indication bit is the time slot increase adjustment notification indication bit. It is used by the downstream to notify the upstream to trigger time slot negotiation when the time slot needs to be increased. The DD indicator bit may also be called the S indicator bit.

The 13th bit is the configuration commit (CMT) indicator bit. The CMT indicator bit is used to indicate that the time slot configuration takes effect. The CMT indicator bit may also be called the C indicator bit.

The 14th bit is the configuration request (CR) indication bit. The CR indication bit is used to indicate the time slot adjustment request.

The 15th bit is the configuration acknowledgment (CA) indication bit. The CA indication bit is used to indicate the time slot adjustment response. After receiving the time slot adjustment request, the receiving device sends the time slot adjustment response to the sending device.

The content carried by bits 16 to 48 is indicated by the flag field; for example, it can carry the GCC field, or it can carry the client ID, sub-slot ID, and reserved fields.

Bits 49 to 55 are cyclic redundancy check (CRC) fields. In one example, the CRC field is used to carry the CRC value of the data carried in bits 8 to 48.

For other contents in the SPN architecture shown in Figure 1a, you can refer to the relevant descriptions in China Mobile's SPN small particle white paper, which will not be described in detail here. Next, the application scenarios of the embodiments of the present application will be introduced with reference to Figure 1g. Figure 1g is a schematic diagram of an exemplary application scenario provided by the embodiment of the present application.

As shown in Figure 1g, an end-to-end transmission path for carrying small-granularity services is established between PE1 and PE2. Among them: PE1 and PE2 also include equipment P1, equipment P2 and equipment P3. Although not shown in Figure 1g, other devices may also be included between PE1 and device P1. Correspondingly, there are also connections between device P1 and device P2, between device P2 and device P3, and between device P3 and PE2. Other devices may be included.

Currently, when a node carrying small-granularity services detects a small-granule fault, it can transmit a local fault (LF) signal to the downstream node. The node that receives the LF signal does not parse the LF signal, but sends the LF signal to the downstream node. The signal continues to be transmitted to the downstream node until the tail node of the end-to-end transmission path receives the LF signal and analyzes the LF signal. After the tail node parses the LF signal, it sends a small-granule basic OAM message carrying RDI to the head node of the end-to-end transmission path. When the tail node sends a small-granular basic OAM message carrying RDI to the head node, the intermediate node does not parse the small-granular basic OAM message. After receiving the small-granule basic OAM message, the head node parses the small-granule basic OAM message to determine that a small-granule fault has occurred.

However, using this method, the intermediate node cannot quickly determine that the node where the small particle failure occurred has failed. Correspondingly, the normal transmission of the small particle service will be affected.

for example:

When device P2 determines that a small particle fault has occurred, device P2 sends an LF signal to device P3, and the LF signal is further forwarded by device P3 to PE2. After PE2 parses the LF signal, it sends a small-granule basic OAM message carrying RDI to PE1. After PE1 receives the small-granule basic OAM message carrying RDI, it determines that a small-granule failure has occurred. For example, if the FGU layer is working abnormally, PE1 can further perform corresponding measures, such as fault location measures to locate the specific node where the fault occurred. However, the intermediate node such as P1 cannot be determined to be faulty, and accordingly, the transmission of service messages corresponding to small-granularity services will be affected. For example, before device P2 determines that a small particle failure occurs, device P1 and device P2 conduct time slot negotiation, and device P1 sends time slot validation indication information to device P2. However, device P2 did not successfully receive the time slot validation indication information due to a fault. Therefore, when subsequently transmitting the service message of the small-granularity service, device P1 uses the negotiated time slot configuration to send the service message to device P2, and However, device P2 uses the time slot configuration before negotiation to parse the received service packets. That is, the time slot configuration used by device P1 to send service messages is inconsistent with the time slot configuration used by device P2 to receive service messages, causing the service message to fail to be transmitted.

In view of this, embodiments of the present application provide a fault notification method. Next, the method is introduced with reference to the attached figure.

It should be noted that the "small granular faults" mentioned in the embodiments of this application refer to faults related to small granular services, and small granular faults include but are not limited to FGU layer faults.

In the embodiment of this application, the "FGU" layer refers to the small-granularity layer, which is used to process small-granularity services. Through the FGU layer, related operations such as time slot mapping and demapping can be performed on small-granularity services. "FGU layer failure" can also be expressed as "FGU layer working abnormality" or "small particle layer working failure", which can be used interchangeably. With the evolution of technology and the progress of relevant standards, those skilled in the art can understand that the small particle layer and small particle technology may have different names in different standards. Refer to Figure 2, which is a signaling diagram of a fault notification method provided by an embodiment of the present application. The communication device 1 and the communication device 2 in the fault notification method 100 shown in Figure 2 are both nodes in the end-to-end transmission path carrying small-granularity services. Communication device 2 is an upstream node of communication device 1 . The communication device 1 may be a tail node or an intermediate node, and the communication device 2 may be an intermediate node or a head node. For example, in the end-to-end transmission path with PE1 as the head node and PE2 as the tail node shown in Figure 1e: communication device 1 can be PE1, and communication device 2 can be device P3; or communication device 1 can be device P3, The communication device 2 may be the device P2; or the communication device 1 may be the device P2, and the communication device 2 may be the device P1; or the communication device 1 may be the device P1, and the communication device 2 may be PE1.

The communication device mentioned in the embodiments of this application may be a network device such as a switch or a router, or may be a part of the network device, such as a single board or line card on the network device, or may be a component on the network device. The functional module may also be a chip used to implement the method of the present application, which is not specifically limited in the embodiment of the present application. The communication devices may be directly connected through, but not limited to, Ethernet cables or optical cables.

The method 100 may include, for example, the following S101-S104.

S101: The communication device 1 determines that the FGU layer is working abnormally.

In one example, the FGU layer mentioned in the embodiment of this application may be the FGU layer located in SCL as shown in Figure 1d. In this case, according to the above description of Figure 1d, it can be known that the service layer of the FGU layer can be an MTN channel layer or an Ethernet physical layer.

In the embodiment of the present application, the communication device 1 can detect the working status of the FGU layer. In one example, when the communication device 1 detects one or more of LOM, when the communication device 1 detects LOF, and when the communication device 1 detects a service layer abnormality of the FGU layer, it may be determined that the FGU layer is working abnormally. . in:

When the communication device 1 detects the LOM, the communication device 1 may determine that the fg-BU framing fails. Among them: fg-BU framing needs to search and identify the correct S0 code block carried by one or several consecutive fg-BUs, and then the overhead information in the fg-BU and the data contained in the time slot can be extracted. When the communication device 1 does not search and identify the correct S0 code block carried by one or several consecutive fg-BUs, the fg-BU cannot determine the frame.

When the communication device 1 detects LOF, it may be that the numbers of the multiple fg-BUs received by the communication device 1 are not consecutive. Among them, the fg-BU number can be carried through the MFI field in the FGU base frame overhead.

When the communication device 1 detects an abnormality in the service layer of the FGU layer, it may be that the service layer of the FGU layer of the communication device 1 itself detects an abnormality. For example, when the service layer of the FGU layer is the MTN channel layer, the MTN channel layer sink can determine whether the MTN channel layer is faulty by detecting whether it receives basic OAM code blocks within a fixed period. For another example, whether the MTN channel layer is faulty can be determined through the detection means of the service layer of the MTN channel layer, such as the MTN segment layer. The detection means of the MTN segment layer include but are not limited to detecting FlexE LOF and/or FlexE LOM.

The embodiments of this application do not specifically limit the reasons for the abnormal working of the FGU layer. The reasons for the abnormal working of the FGU layer include but are not limited to: faults of large-granular channels carrying small-granular services, optical fiber faults, etc., which are not mentioned here. List and explain one by one.

S102: Communication device 1 sends fault indication information to communication device 2, where the fault indication information is used to indicate a remote fault.

After determining that the FGU layer is working abnormally, the communication device 1 may send fault indication information to its upstream node (ie, the communication device 2). This fault indication information is used to indicate a remote fault. In one example, the remote fault may be a remote small particle fault or a large particle channel fault carrying the small particles. In one example, in order to enable the upstream node to determine the specific situation of the remote fault, the fault indication information may be used to indicate the remote FGU layer fault.

In some embodiments, the communication device 1 may carry the fault indication information in base frame overhead and send it to the communication device 2.

In one example, considering that the reserved field in the base frame overhead has not been used, the reserved field in the base frame overhead can be used to carry the above fault indication information. For example, a certain bit in the reserved field is used to carry the foregoing fault indication information. When the value of this bit is 1, it indicates that the base frame overhead carries the foregoing fault indication information. When the value of this bit is 0, this field has no special meaning or indicates that the remote end is normal (for example, indicating that the remote FGU layer is normal). In one example, when the fault indication information is used to indicate a remote FGU layer fault:

In one example, the reserved field may be used to indicate a remote FGU layer failure. In another example, the reserved field is used to indicate a remote fault, and another field in the base frame overhead indicates that the remote fault is specifically a remote FGU layer fault. The embodiment of the present application does not specifically limit the other field. The other field may be any unused field different from the reserved field. For example, the other field may be the flag field in the base frame overhead.

In yet another example, considering that the flag field in the base frame overhead has not been used, the flag field in the base frame overhead can be used to carry the above fault indication information. For example, for the base frame overhead shown in Figure 1b or Figure 1c, the flag field includes 2 bits, and one or two bits in the flag field can be used to carry the foregoing fault indication information. For example, one bit is used to carry the foregoing fault indication information. When the value of this bit is 1, it indicates that the base frame overhead carries the fault indication information. When the value of this bit is 0, this field has no special meaning or indicates that the remote end is normal (for example, indicating that the remote FGU layer is normal). In one example, when the fault indication information is used to indicate a remote FGU layer fault:

In one example, the flag field may be used to indicate a remote FGU layer failure. In another example, the flag field is used to indicate a remote fault, and another field in the base frame overhead indicates that the remote fault is specifically a remote FGU layer fault. The embodiment of the present application does not specifically limit the other field. The other field may be any Any unused field that is the same as the flag field. For example, the other field may be a reserved field in the base frame overhead.

In other embodiments, the communication device 1 may use the OAM code block of the MTN channel layer to carry the fault indication information, and send the fault indication information to the communication device 2 by sending the OAM code block of the MTN channel layer to the communication device 2. Communication device 2.

In an implementation manner, a new OAM code block can be extended to carry the fault indication information. In this case, the type field in the OAM code block may be used to indicate that the OAM code block carries the fault indication information. In one example, when the fault indication information is used to indicate a remote FGU layer fault:

In one example, the type field of the OAM code block may be used to indicate a remote FGU layer failure. In another example, the type field is used to indicate a remote fault, and another field in the OAM code block indicates that the remote fault is specifically a remote FGU layer fault. The embodiment of the present application does not specifically limit the other field. The other field may be any unused field different from the type field. For example, the other field may be a reserved field in the OAM code block.

In yet another implementation manner, the OAM code block may be an existing basic OAM code block. For this method, the existing basic OAM code block of the MTN channel layer can be used to carry the fault indication information. In one example, the reserved field in the basic OAM code block can be used to carry the fault indication information. In another example, the RDI in the basic OAM code block can be used to carry the fault indication information. In one example, when the fault indication information is used to indicate a remote FGU layer fault:

In one example, the reserved field of the basic OAM code block can be used to indicate a remote FGU layer failure. In another example, a reserved field in the basic OAM code block is used to indicate a remote fault, and another field in the basic OAM code block indicates that the remote fault is specifically a remote FGU layer fault. The embodiment of the present application does not specifically limit the other field. The other field may be any unused field different from the reserved field.

In yet another example, the RDI of the basic OAM code block may be used to indicate a remote FGU layer failure. In another example, the RDI in the basic OAM code block is used to indicate a remote fault, and another field in the basic OAM code block indicates that the remote fault is specifically a remote FGU layer fault. The embodiment of the present application does not specifically limit the other field. The other field may be any unused field different from the RDI. For example, the other field may be a reserved field in the basic OAM code block.

Regarding the structure of the basic OAM code block, the embodiment of the present application does not specifically limit it. In one example, the structure of the basic OAM code block can be shown in Figure 3. Figure 3 is an example provided by the embodiment of the present application. Structural diagram of an OAM code block. As shown in Figure 3, the OAM code block includes 66 bits, the first two bits are synchronization header bits, and their value is 01. The last 64 bits include: type (type) field, reserved (RES) field, value (value) field, C code field, sequence number (sequence, seq) field, and cyclic redundancy check (cyclic redundancy check) , CRC)4 fields.

in:

The reserved field includes 3 bits;

The type field is used to indicate the OAM message type carried by the OAM code block, including 8 bits. MTN channel layer OAM message types include the following:

Basic, connectivity verification (CV), delay measurement (DM), automatic protection switching (APS), client signal type (CS). When the value of the type field is 1, the OAM code block is a basic OAM code block.

The value field, including 32 bits, indicates the specific value of the OAM message carried by this OAM code block.

C code: Use a 4-bit fixed 0xC value to indicate that the 0x4B type control code block is an OAM code block of the MTN channel layer. Through the difference in C code, the MTNP OAM code block and the MTNS overhead code block can be distinguished.

seq: uses 4 bits to indicate the sequence number of this OAM code block in the OAM message composed of multiple code blocks. Typical applications are connectivity check and delay measurement.

The CRC4 field is the CRC4 value of the first 62 bits of the OAM code block.

In another example, the basic OAM code block may also be an MTN path basic OAM block, and its structure may refer to Chapter 8 of the International Telecommunication Union Telecommunication Standardization Sector (ITU-T) G.8312 The relevant description part will not be described in detail here.

S103: The communication device 2 receives the fault indication information sent by the communication device 1.

S104: The communication device 2 determines that a fault occurs in the communication device 1 based on the fault indication information.

After the communication device 1 sends the fault indication information to the communication device 2, the communication device 2 can receive the fault indication information sent by the communication device 1. Furthermore, the communication device 2 may determine that the communication device 1 is faulty based on the fault indication information. As mentioned above, in one example, the fault indication information may be used to indicate a remote FGU layer fault. For this situation, the notification device 2 may determine that the remote FGU layer is faulty based on the fault indication information.

In one example, after receiving the fault indication information, the communication device 2 can send alarm information to the control management device, and the alarm information is used to indicate that the communication device 1 is working abnormally. In one example, if the foregoing fault indication information is used to indicate a remote FGU layer fault, the alarm information may be used to indicate that the FGU layer of the communication device 1 is working abnormally. Notifying the alarm information to the control and management equipment can cause the control and management equipment to determine that the communication device 1 is working abnormally, and accordingly, the control and management equipment can perform corresponding processing measures. For example, the abnormal operation of the communication device 1 is notified to other nodes on the end-to-end path carrying the small-granule service, and so on.

The control management device mentioned in the embodiment of this application may be, for example, a device running a network management system (network management system, NMS), or may be a controller.

The communication device 1 can continuously detect the working status of the FGU layer. In one example, if the FGU layer fault is not recovered, the communication device 1 may continuously or periodically send the aforementioned fault indication information to the communication device 2.

In one example, after the communication device 1 determines that the FGU layer is working normally, it may no longer send the fault indication information to the communication device 2. Correspondingly, if the communication device 2 does not receive the fault indication information, it may determine that the communication device 2 1 works fine.

In another example, after the communication device 1 determines that the FGU layer is working normally, it may send fault recovery information to the communication device 2, where the fault recovery information is used to indicate that the remote end is normal. In one example, the remote end is normal, which may include the remote FGU layer being normal. That is, after the communication device 1 determines that the FGU layer is working normally, it can send fault recovery information indicating that the remote FGU layer is normal to the communication device 2 . In one example, the communication device 1 may determine that the FGU layer is working normally when the LOM and LOF cannot be detected.

In some embodiments, the communication device 1 may carry the fault recovery information in base frame overhead and send it to the communication device 2.

In one example, considering that the reserved field in the base frame overhead has not been used, the reserved field in the base frame overhead can be used to carry the above fault recovery information. For example, a certain bit in the reserved field is used to carry the foregoing fault recovery information. When the value of this bit is 0, it indicates that the base frame overhead carries the foregoing fault recovery information. When the value of this bit is 1, this field has no special meaning or indicates a remote fault (for example, indicating a remote FGU layer fault). In one example, when the fault recovery information is used to indicate that the remote FGU layer is working normally:

In one example, the reserved field may be used to indicate that the remote FGU layer is working normally. In another example, the reserved field is used to indicate that the remote end is normal, and another field in the base frame overhead indicates that the remote end is normal, specifically that the remote FGU layer is working properly. The embodiment of the present application does not specifically limit the other field. The other field may be any unused field different from the reserved field. For example, the other field may be the flag field in the base frame overhead.

In yet another example, considering that the flag field in the base frame overhead has not been used, the flag field in the base frame overhead can be used to carry the above fault recovery information. For example, for the base frame overhead shown in Figure 1b or Figure 1c, the flag field includes 2 bits, and one or two bits in the flag field can be used to carry the aforementioned fault recovery information. For example, one bit is used to carry the aforementioned fault recovery information. When the value of this bit is 0, it indicates that the base frame overhead carries the fault recovery information. When the value of this bit is 1, this field has no special meaning or indicates a remote fault (for example, indicating a remote FGU layer fault). In one example, when the fault recovery information is used to indicate that the remote FGU layer is working normally:

In one example, the flag field may be used to indicate that the remote FGU layer is working normally. In another example, the flag field is used to indicate that the remote end is normal, and another field in the base frame overhead indicates that the remote end is normal, specifically that the remote FGU layer is working properly. The embodiment of the present application does not specifically limit the other field. The other field may be any unused field different from the flag field. For example, the other field may be a reserved field in the base frame overhead.

In other embodiments, the communication device 1 may use the OAM code block of the MTN channel layer to carry the fault recovery information, and send the fault recovery information to the communication device 2 by sending the OAM code block of the MTN channel layer to the communication device 2. Communication device 2.

In an implementation manner, a new OAM code block can be extended to carry the fault recovery information. In this case, the type field in the OAM code block may be used to indicate that the OAM code block carries the fault recovery information. In one example, when the fault recovery information is used to indicate that the remote FGU layer is working normally:

In one example, the type field of the OAM code block may be used to indicate that the remote FGU layer is working normally. In another example, the type field is used to indicate that the remote end is normal, and another field in the OAM code block indicates that the remote end is normal, specifically that the remote FGU layer is working properly. The embodiment of the present application does not specifically limit the other field. The other field may be any unused field different from the type field. For example, the other field may be a reserved field in the OAM code block.

In another implementation manner, the OAM code block may be an existing basic OAM code block. For this method, the existing basic OAM code blocks of the MTN channel layer can be used to carry the fault recovery information. In one example, a reserved field in the basic OAM code block can be used to carry the fault recovery information. In one example, when The fault recovery information is used to indicate that the remote FGU layer is working normally:

In one example, the reserved field in the basic OAM code block can be used to indicate that the remote FGU layer is working normally. For example, when the value of the reserved field in the basic OAM code block is 0, it indicates that the remote FGU layer is working. normal. In another example, the reserved field in the basic OAM code block is used to indicate that the remote end is normal, and another field in the basic OAM code block is used to indicate that the remote end is normal, specifically that the remote FGU layer is working properly. The embodiment of the present application does not specifically limit the other field. The other field may be any unused field different from the reserved field.

Regarding the structure of the basic OAM code block, you can refer to the relevant description above, which will not be repeated this time.

After the communication device 2 receives the fault recovery information, it can be determined that the communication device 1 is working normally. In one example, if the fault recovery information is used to indicate that the remote FGU layer is normal, the communication device 2 can determine that the FGU layer of the communication device 1 is working normally based on the fault recovery information.

In one example, it is considered that the time slot between the communication device 1 and the communication device 2 may be out of synchronization due to abnormal operation of the communication device 2 . Therefore, in one example, after receiving the fault recovery information, the communication device 2 can perform time slot synchronization with the first communication device. The embodiment of the present application does not specifically limit the specific implementation of time slot synchronization between the communication device 2 and the communication device 1. In one example, the communication device 2 and the communication device 1 can perform full time slot synchronization for small-granularity services.

As can be seen from the above description, using the method 100 provided by the embodiment of the present application, compared with the traditional technology, the method 100 includes a mechanism to notify the upstream node of a remote fault. Correspondingly, compared with the traditional technology, the edge node that only carries small-granularity services can Compared with sensing the fault, the upstream node of the communication device 1 that senses the FGU layer fault can learn the remote fault. Correspondingly, the upstream node of the communication device 1 learns the remote fault, which is also conducive to quickly locating the cause of the remote fault. For example, the upstream node of the communication device 1 can perform measures related to fault location, and so on. Correspondingly, the impact on small-granule service transmission can be reduced.

When the communication device 2 is an intermediate node in the end-to-end transmission path carrying small-granularity services, using the above method 100, when the FGU layer of the downstream node of the intermediate node works abnormally, the intermediate node can learn the remote fault information. Further, The intermediate node can further implement corresponding measures to minimize the impact of remote failure on the transmission of small-granular service messages. For example, the intermediate node can determine whether to perform time slot synchronization before determining the remote failure. If the time slot synchronization was performed with the downstream node before the failure, further determine whether the time slot synchronization is successful.

Refer to Figure 4, which is a schematic flowchart of a fault notification method provided by an embodiment of the present application. The fault notification method 200 shown in Figure 4 can be executed by the communication device 1, and the communication device 1 can include the following steps S201-S202.

S201: The communication device 1 determines that the FGU layer is working abnormally.

Regarding S201, please refer to the relevant description of S101 above, which will not be described in detail here.

S202: The communication device 1 sends alarm information to the control management device, where the alarm information is used to indicate a local fault.

In one example, the local fault is a local FGU layer fault.

After receiving the alarm information, the control management device may determine that the communication device 1 is faulty. In one example, if the local fault is a local FGU layer fault, the control management device may determine that the communication device 1 is faulty at the FGU layer. Correspondingly, the control management device can perform corresponding processing measures. For example, notify other nodes on the end-to-end path carrying the small particle service that the communication device 1 is working abnormally, or notify other nodes on the end-to-end path carrying the small particle service that the communication device 1 is working abnormally at the FGU layer. .

Using the method 200, when the local FGU layer works abnormally, the communication device 1 can send alarm information to the control management device, so that the control management device can further implement corresponding measures, thereby improving the efficiency of fault location or fault recovery as much as possible, thereby reducing Due to the impact of abnormal working of the 1FGU layer of the communication device on small-granule services.

The embodiment of the present application also provides a status notification method, which can enable the upstream node to learn the working status of the FGU layer of the downstream node.

Refer to Figure 5, which is a signaling interaction diagram of a status notification method provided by an embodiment of the present application. Regarding the communication device 1 and the communication device 2 shown in FIG. 5 , reference may be made to the relevant description of the method 100 above, which will not be described in detail here.

The method 300 shown in Figure 5 may include the following S301-S304.

S301: The communication device 1 determines the working status of the FGU layer.

The working status of the FGU layer can include two situations: the FGU layer is working normally and the FGU layer is working abnormally.

Regarding the specific implementation of the communication device 1 determining that the FGU layer is working abnormally, reference may be made to the relevant description part of the method 100, which will not be described in detail here.

Regarding the specific implementation of the communication device 1 determining that the FGU layer is working properly, reference may be made to the relevant description part of the method 100, which will not be described in detail here.

S302: The communication device 1 sends status indication information to the communication device 2, where the status indication information is used to indicate the working status of the FGU layer.

When the FGU layer works abnormally, the status indication information is fault indication information indicating that the remote FGU layer works abnormally. Regarding the specific implementation of the communication device 1 sending the fault indication information indicating that the remote FGU layer is working abnormally to the communication device 2, please refer to the relevant description part in the method 100, and the description will not be repeated here.

When the FGU layer works normally, the status indication information indicates that the remote FGU layer works normally. Regarding the specific implementation of the communication device 1 sending the status indication information indicating that the remote FGU layer is working normally to the communication device 2, please refer to the relevant description part about "the communication device 1 sends the fault recovery information to the communication device 2" in the method 100, here The description will not be repeated.

S303: The communication device 2 receives the status indication information sent by the communication device 1.

S304: The communication device 2 determines the working status of the FGU layer of the communication device 1 based on the status indication information.

When the FGU layer works abnormally, the status indication information is fault indication information indicating that the remote FGU layer works abnormally. In this case, the communication device 2 may determine that the FGU layer of the communication device 1 is working abnormally based on the status indication information.

When the FGU layer works normally, the status indication information indicates that the remote FGU layer works normally. In this case, the communication device 2 may determine that the FGU layer of the communication device 1 is working abnormally based on the status indication information.

This embodiment of the present application also provides a fault notification method. See Figure 6 , which is a schematic flowchart of a fault notification method provided by this embodiment of the present application. The fault notification method 400 shown in Figure 6 can be executed by the first communication device.

The fault notification method may be applied to the method 100 mentioned in the above embodiment, and accordingly, the first communication device may correspond to the communication device 1 in the method 100.

The method 400 may include the following S401-S402.

S401: It is determined that the fine-grained unit FGU layer is working abnormally.

S402: Send fault indication information to the upstream node, where the fault indication information is used to indicate a remote fault.

In a possible implementation, the OAM code block is a basic OAM code block.

In a possible implementation, determining that the FGU layer is working abnormally includes:

One or more of multiframe loss LOM is detected, frame loss LOF is detected, and service layer exception of the FGU layer is detected.

In a possible implementation, the method further includes: determining that the FGU layer is working normally; and sending fault recovery information to the upstream node, where the fault recovery information is used to indicate that the remote end is normal.

Regarding the specific implementation of the method 400, please refer to the relevant description of the method 100 above, and the description will not be repeated here.

This embodiment of the present application also provides a fault notification method. See Figure 7 , which is a schematic flow chart of a fault notification method provided by this embodiment of the present application. The fault notification method 500 shown in Figure 7 can be executed by the second communication device.

The fault notification method may be applied to the method 100 mentioned in the above embodiment, and accordingly, the second communication device may correspond to the communication device 2 in the method 100.

The method 500 may include the following S501-S502.

S501: Receive fault indication information sent by the first communication device, where the fault indication information is used to indicate a remote fault.

S502: Based on the fault indication information, determine that a fault occurs in the first communication device.

In a possible implementation, the OAM code block is a basic OAM code block.

In a possible implementation, the method further includes:

Send alarm information to the control management device, where the alarm information is used to indicate abnormal operation of the first communication device.

In a possible implementation, the method further includes: performing time slot synchronization with the first communication device.

Regarding the specific implementation of the method 500, you may refer to the relevant description of the method 100 above, and the description will not be repeated here.

This embodiment of the present application also provides a status notification method. See Figure 8 , which is a schematic flowchart of a status notification method provided by this embodiment of the present application. The status notification method 600 shown in Figure 8 can be executed by the first communication device.

The status notification method may be applied to the method 300 mentioned in the above embodiment, and accordingly, the first communication device may correspond to the communication device 1 in the method 300.

The method 600 may include, for example, the following S601-S602.

S601: Determine the working status of the fine-grained unit FGU layer.

S602: Send status indication information to the upstream node, where the status indication information is used to indicate the working status of the FGU layer.

In a possible implementation, the OAM code block is a basic OAM code block.

Regarding the specific implementation of the method 600, you may refer to the relevant description of the method 300 above, and the description will not be repeated here.

This embodiment of the present application also provides a status notification method. See Figure 9 , which is a schematic flowchart of a status notification method provided by this embodiment of the present application. The status notification method 700 shown in Figure 9 can be executed by the second communication device.

The status notification method may be applied to the method 300 mentioned in the above embodiment, and accordingly, the second communication device may correspond to the communication device 2 in the method 300.

The method 700 may include, for example, the following S701-S702.

S701: Receive status indication information sent by the first communication device, where the status indication information is used to indicate the working status of the remote fine-grained unit FGU layer.

S702: Based on the status indication information, determine the working status of the FGU layer of the first communication device.

In a possible implementation, the status indication information is carried through the identification flag field of the base frame overhead. bring.

In a possible implementation, the OAM code block is a basic OAM code block.

Regarding the specific implementation of the method 700, you may refer to the relevant description of the method 300 above, and the description will not be repeated here.

An embodiment of the present application also provides a first communication device. See FIG. 10 , which is a schematic structural diagram of a communication device provided by an embodiment of the present application. The first communication device 1000 shown in Figure 10. The fault notification device may include a processing unit 1001 and a sending unit 1002.

In one example, the first communication device may be used to perform the steps performed by the communication device 1 in the above method 100, or to perform the steps performed by the first communication device in the above method 400. In this case:

The processing unit 1001 is used to determine abnormal working of the fine-grained unit FGU layer;

The sending unit 1002 is configured to send fault indication information to an upstream node, where the fault indication information is used to indicate a remote fault.

In a possible implementation, the OAM code block is a basic OAM code block.

In a possible implementation, the processing unit 1001 is used to:

In a possible implementation, the processing unit 1001 is also used to: determine that the FGU layer is working normally; the sending unit is also used to send fault recovery information to the upstream node. The fault recovery information Used to indicate that the remote end is normal.

In yet another example, the first communication device may be used to perform the steps performed by the communication device 1 in the above method 300, or to perform the steps performed by the first communication device in the above method 600. In this case:

The processing unit 1001 is used to determine the working status of the fine-grained unit FGU layer;

The sending unit 1002 is configured to send status indication information to an upstream node, where the status indication information is used to indicate the working status of the FGU layer.

In a possible implementation, the OAM code block is a basic OAM code block.

This embodiment of the present application also provides a second communication device. See FIG. 11 , which is a schematic structural diagram of a communication device provided by an embodiment of the present application. The second communication device 1100 shown in Figure 11 may include a receiving unit 1101 and a processing unit 1101. management unit 1102.

In one example, the second communication device may be used to perform the steps performed by the communication device 2 in the above method 100, or to perform the steps performed by the second communication device in the above method 500. In this case:

The receiving unit 1101 is configured to receive fault indication information sent by the first communication device, where the fault indication information is used to indicate a remote fault;

The processing unit 1102 is configured to determine that a fault occurs in the first communication device based on the fault indication information.

In a possible implementation, the OAM code block is a basic OAM code block.

In a possible implementation, the device further includes: a sending unit configured to send alarm information to the control management device, where the alarm information is used to indicate abnormal operation of the first communication device.

In a possible implementation, the receiving unit 1101 is further configured to receive fault recovery information sent by the first communication device, where the fault recovery information is used to indicate that the remote end is normal.

In a possible implementation, the processing unit 1102 is further configured to perform time slot synchronization with the first communication device.

In yet another example, the second communication device may be used to perform the steps performed by the communication device 2 in the above method 300, or to perform the steps performed by the second communication device in the above method 700. In this case:

The receiving unit 1101 is configured to receive status indication information sent by the first communication device. The status indication information Used to indicate the working status of the remote fine-grained unit FGU layer;

The processing unit 1102 is configured to determine the working status of the FGU layer of the first communication device based on the status indication information.

In a possible implementation, the OAM code block is a basic OAM code block.

In addition, the embodiment of the present application also provides a communication device 1200, as shown in FIG. 12. FIG. 12 is a schematic structural diagram of a communication device provided by the embodiment of the present application. The communication device 1200 includes a communication interface 1201 and a processor 1202 connected to the communication interface 1201. The communication device 1400 may be used to perform method 100, method 200, method 300, method 400, method 500, method 600 or method 700 in the above embodiments.

In one example, the communication device 1200 can perform the method 100 in the above embodiment. When the communication device 1200 is used to perform the method 100 in the above embodiment, the communication device 1200 is equivalent to the communication device 1 in the method 100. The communication interface 1201 is used to perform the sending and receiving operations performed by the communication device 1 in the method 100. The processor 1202 is configured to perform operations other than the sending and receiving operations performed by the communication device 1 in the method 100 . For example: the processor 1202 is used to determine that the FGU layer is working abnormally; the communication interface 1201 is used to send fault indication information to the communication device 2, and the fault indication information is used to indicate a remote fault.

In one example, the communication device 1200 can perform the method 100 in the above embodiment. When the communication device 1200 is used to perform the method 100 in the above embodiment, the communication device 1200 is equivalent to the communication device 2 in the method 100. The communication interface 1201 is used to perform the sending and receiving operations performed by the communication device 2 in the method 100. The processor 1202 is configured to perform operations other than the sending and receiving operations performed by the communication device 2 in the method 100 . For example: the communication interface 1201 is used to receive fault indication information sent by the communication device 1, and the fault indication information is used to indicate a remote fault; the processor 1202 is used to determine that the communication device 1 is faulty.

In one example, the communication device 1200 can perform the method 200 in the above embodiment. When the communication device 1200 When 1200 is used to execute the method 200 in the above embodiment, the communication device 1200 is equivalent to the communication device 1 in the method 200. The communication interface 1201 is used to perform the sending and receiving operations performed by the communication device 1 in the method 200. The processor 1202 is configured to perform operations other than the sending and receiving operations performed by the communication device 1 in the method 200. For example: the processor 1202 is used to determine that the FGU layer is working abnormally; the communication interface 1201 is used to send alarm information to the control management device, and the alarm information is used to indicate a local fault.

In one example, the communication device 1200 can perform the method 300 in the above embodiment. When the communication device 1200 is used to perform the method 300 in the above embodiment, the communication device 1200 is equivalent to the communication device 1 in the method 300. The communication interface 1201 is used to perform the sending and receiving operations performed by the communication device 1 in the method 300. The processor 1202 is configured to perform operations other than the sending and receiving operations performed by the communication device 1 in the method 300. For example: the processor 1202 is used to determine the working status of the FGU layer; the communication interface 1201 is used to send status indication information to the communication device 2, and the status indication information is used to indicate the working status of the FGU layer.

In one example, the communication device 1200 can perform the method 300 in the above embodiment. When the communication device 1200 is used to perform the method 300 in the above embodiment, the communication device 1200 is equivalent to the communication device 2 in the method 300. The communication interface 1201 is used to perform the sending and receiving operations performed by the communication device 2 in the method 300. The processor 1202 is configured to perform operations other than the sending and receiving operations performed by the communication device 2 in the method 300. For example: the communication interface 1201 is used to receive status indication information sent by the communication device 1, and the status indication information is used to indicate the working status of the FGU layer; the processor 1202 is used to determine the working status of the FGU layer of the communication device 1 .

In one example, the communication device 1200 can perform the method 400 in the above embodiment. When the communication device 1200 is used to perform the method 400 in the above embodiment, the communication device 1200 is equivalent to the first communication device in the method 400. The communication interface 1201 is used to perform the sending and receiving operations performed by the first communication device in the method 400. The processor 1202 is configured to perform operations other than the sending and receiving operations performed by the first communication device in the method 400. For example: the processor 1202 is used to determine that the FGU layer is working abnormally; the communication interface 1201 is used to send fault indication information to the upstream node, and the fault indication information is used to indicate a remote fault.

In one example, the communication device 1200 can perform the method 500 in the above embodiment. When the communication device 1200 is used to perform the method 500 in the above embodiment, the communication device 1200 is equivalent to the second communication device in the method 500. The communication interface 1201 is used to perform the sending and receiving operations performed by the second communication device in the method 500. The processor 1202 is configured to perform operations other than the sending and receiving operations performed by the second communication device in the method 500. For example: the communication interface 1201 is configured to receive fault indication information sent by the first communication device, the fault indication information is used to indicate a remote fault; the processor 1202 is configured to determine that the first communication device is faulty based on the fault indication information. .

In one example, the communication device 1200 can perform the method 600 in the above embodiment. When the communication device 1200 is used to perform the method 600 in the above embodiment, the communication device 1200 is equivalent to the first communication device in the method 600. The communication interface 1201 is used to perform the sending and receiving operations performed by the first communication device in the method 600. The processor 1202 is configured to perform operations other than the sending and receiving operations performed by the first communication device in the method 600. For example: the processor 1202 is used to determine the working status of the fine-grained unit FGU layer; the communication interface 1201 is used to send status indication information to the upstream node, and the status indication information is used to indicate the working status of the FGU layer.

In one example, the communication device 1200 can perform the method 700 in the above embodiment. When the communication device 1200 is used to perform the method 700 in the above embodiment, the communication device 1200 is equivalent to the second communication device in the method 700. The communication interface 1201 is used to perform the sending and receiving operations performed by the second communication device in the method 700. For processor 1202 In the execution method 700, the second communication device performs operations other than the sending and receiving operations. For example: the communication interface 1201 is used to receive status indication information sent by the first communication device. The status indication information is used to indicate the remote fine-grained unit FGU layer working status; the processor 1202 is used to determine the status indication information based on the status indication information. The working state of the FGU layer of the first communication device.

In addition, the embodiment of the present application also provides a communication device 1300, as shown in FIG. 13. FIG. 13 is a schematic structural diagram of a communication device provided by the embodiment of the present application. The communication device 1300 may be used to perform method 100, method 200, method 300, method 400, method 500, method 600 or method 700 in the above embodiments.

As shown in Figure 13, the communication device 1300 may include a processor 1310, a memory 1320 coupled to the processor 1310, and a transceiver 1330. The transceiver 1330 may be, for example, a communication interface, an optical module, etc. The processor 1310 may be a central processing unit (English: central processing unit, abbreviation: CPU), a network processor (English: network processor, abbreviation: NP) or a combination of CPU and NP. The processor can also be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof. The above-mentioned PLD can be a complex programmable logic device (English: complex programmable logic device, abbreviation: CPLD), a field-programmable logic gate array (English: field-programmable gate array, abbreviation: FPGA), a general array logic (English: generic array logic, abbreviation: GAL) or any combination thereof. The processor 1310 may refer to one processor or may include multiple processors. The memory 1320 may include volatile memory (English: volatile memory), such as random access memory (English: random-access memory, abbreviation: RAM); the memory may also include non-volatile memory (English: non-volatile memory) , such as read-only memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory), hard disk (English: hard disk drive, abbreviation: HDD) or solid-state drive (English: solid-state drive , abbreviation: SSD); the memory 1320 may also include a combination of the above types of memories. The memory 1320 may refer to one memory or may include multiple memories. In one embodiment, computer-readable instructions are stored in the memory 1320, and the computer-readable instructions include a plurality of software modules, such as a sending module 1321, a processing module 1322, and a receiving module 1323. After executing each software module, the processor 1310 can perform corresponding operations according to the instructions of each software module. In this embodiment, the operations performed by a software module actually refer to operations performed by the processor 1310 according to the instructions of the software module.

In one example, the communication device 1300 can perform the method 100 in the above embodiment. When the communication device 1300 is used to perform the method 100 in the above embodiment, the communication device 1300 is equivalent to the communication device 1 in the method 100. The transceiver 1330 is used to perform the sending and receiving operations performed by the communication device 1 in the method 100. The processor 1310 is configured to perform operations other than the sending and receiving operations performed by the communication device 1 in the method 100. For example: the processor 1310 is used to determine that the FGU layer is working abnormally; the transceiver 1330 is used to send fault indication information to the communication device 2, and the fault indication information is used to indicate a remote fault.

In one example, the communication device 1300 can perform the method 100 in the above embodiment. When the communication device 1300 is used to perform the method 100 in the above embodiment, the communication device 1300 is equivalent to the communication device 2 in the method 100. The transceiver 1330 is used to perform the sending and receiving operations performed by the communication device 2 in the method 100. The processor 1310 is configured to perform operations other than the sending and receiving operations performed by the communication device 2 in the method 100 . For example: the transceiver 1330 is used to receive the fault indication information sent by the communication device 1, and the fault indication information is used to indicate a remote fault; the processor 1310 is used to determine the communication Device 1 has failed.

In one example, the communication device 1300 can perform the method 200 in the above embodiment. When the communication device 1300 is used to perform the method 200 in the above embodiment, the communication device 1300 is equivalent to the communication device 1 in the method 200. The transceiver 1330 is used to perform the sending and receiving operations performed by the communication device 1 in the method 200. The processor 1310 is configured to perform operations other than the sending and receiving operations performed by the communication device 1 in the method 200. For example: the processor 1310 is used to determine that the FGU layer is working abnormally; the transceiver 1330 is used to send alarm information to the control management device, and the alarm information is used to indicate a local fault.

In one example, the communication device 1300 can perform the method 300 in the above embodiment. When the communication device 1300 is used to perform the method 300 in the above embodiment, the communication device 1300 is equivalent to the communication device 1 in the method 300. The transceiver 1330 is used to perform the sending and receiving operations performed by the communication device 1 in the method 300. The processor 1310 is configured to perform operations other than the sending and receiving operations performed by the communication device 1 in the method 300. For example: the processor 1310 is used to determine the working status of the FGU layer; the transceiver 1330 is used to send status indication information to the communication device 2, and the status indication information is used to indicate the working status of the FGU layer.

In one example, the communication device 1300 can perform the method 300 in the above embodiment. When the communication device 1300 is used to perform the method 300 in the above embodiment, the communication device 1300 is equivalent to the communication device 2 in the method 300. The transceiver 1330 is used to perform the sending and receiving operations performed by the communication device 2 in the method 300. The processor 1310 is configured to perform operations other than the sending and receiving operations performed by the communication device 2 in the method 300. For example: the transceiver 1330 is used to receive status indication information sent by the communication device 1, and the status indication information is used to indicate the working status of the FGU layer; the processor 1310 is used to determine the working status of the FGU layer of the communication device 1 .

In one example, the communication device 1300 can perform the method 400 in the above embodiment. When the communication device 1300 is used to perform the method 400 in the above embodiment, the communication device 1300 is equivalent to the first communication device in the method 400. The transceiver 1330 is used to perform the transceiver operation performed by the first communication device in the method 400. The processor 1310 is configured to perform operations other than the sending and receiving operations performed by the first communication device in the method 400. For example: the processor 1310 is used to determine that the FGU layer is working abnormally; the transceiver 1330 is used to send fault indication information to the upstream node, and the fault indication information is used to indicate a remote fault.

In one example, the communication device 1300 can perform the method 500 in the above embodiment. When the communication device 1300 is used to perform the method 500 in the above embodiment, the communication device 1300 is equivalent to the second communication device in the method 500. The transceiver 1330 is used to perform the transceiver operation performed by the second communication device in the method 500. The processor 1310 is configured to perform operations other than the sending and receiving operations performed by the second communication device in the method 500. For example: the transceiver 1330 is configured to receive fault indication information sent by the first communication device, the fault indication information is used to indicate a remote fault; the processor 1310 is configured to determine that the first communication device is faulty based on the fault indication information. .

In one example, the communication device 1300 can perform the method 600 in the above embodiment. When the communication device 1300 is used to perform the method 600 in the above embodiment, the communication device 1300 is equivalent to the first communication device in the method 600. The transceiver 1330 is used to perform the transceiver operation performed by the first communication device in the method 600. The processor 1310 is configured to perform operations other than the sending and receiving operations performed by the first communication device in the method 600. For example: the processor 1310 is used to determine the working status of the fine-grained unit FGU layer; the transceiver 1330 is used to send status indication information to the upstream node, and the status indication information is used to indicate the working status of the FGU layer.

In one example, the communication device 1300 can perform the method 700 in the above embodiment. When the communication device 1300 When 1300 is used to execute the method 700 in the above embodiment, the communication device 1300 is equivalent to the second communication device in the method 700. The transceiver 1330 is used to perform the transceiver operation performed by the second communication device in the method 700. The processor 1310 is configured to perform operations other than the sending and receiving operations performed by the second communication device in the method 700. For example: the transceiver 1330 is configured to receive status indication information sent by the first communication device. The status indication information is used to indicate the remote fine-grained unit FGU layer working status; the processor 1310 is configured to determine the status indication information based on the status indication information. The working state of the FGU layer of the first communication device.

The present application also provides a computer-readable storage medium that stores instructions that, when run on a computer, cause the computer to execute the method described in the foregoing embodiments (for example, method 100 , method 200, method 300, method 400, method 500, method 600 or method 700) any one or more operations.

The present application also provides a computer program product, including a computer program that, when run on a computer, causes the computer to perform the methods described in the aforementioned embodiments (for example, method 100, method 200, method 300, method 400, Any one or more operations in method 500, method 600, or method 700).

This application also provides a communication system, including the communication device 1 and the communication device 2 mentioned in the method 100 of the above embodiment.

This application also provides a communication system, including the communication device 1 and the communication device 2 mentioned in the method 300 of the above embodiment.

The present application also provides a communication system, including the first communication device mentioned in the method 400 of the above embodiment and the second communication device mentioned in the method 500 above.

The present application also provides a communication system, including the first communication device mentioned in the method 600 of the above embodiment and the second communication device mentioned in the method 700 of the above embodiment.

This application also provides a communication system, including at least one memory and at least one processor. The at least one memory stores instructions, and the at least one processor executes the instructions, so that the communication system executes the aforementioned embodiments of the application. Any one or more operations in the method described in any embodiment (for example, method 100, method 200, method 300, method 400, method 500, method 600, or method 700).

The terms "first", "second", "third", "fourth", etc. (if present) in the description and claims of this application and the above-mentioned drawings are used to distinguish similar objects without necessarily using Used to describe a specific order or sequence. It is to be understood that the data so used are interchangeable under appropriate circumstances so that the embodiments described herein can be practiced in sequences other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, e.g., a process, method, system, product, or apparatus that encompasses a series of steps or units and need not be limited to those explicitly listed. Those steps or elements may instead include other steps or elements not expressly listed or inherent to the process, method, product or apparatus.

Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, devices and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be described again here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of units is only a logical service division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented. Another point, shown or discussed The mutual coupling or direct coupling or communication connection may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

A unit described as a separate component may or may not be physically separate. A component shown as a unit may or may not be a physical unit, that is, it may be located in one place, or it may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each business unit in various embodiments of this application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above integrated units can be implemented in the form of hardware or software business units.

Integrated units may be stored in a computer-readable storage medium when implemented in the form of software business units and sold or used as independent products. Based on this understanding, the technical solution of the present application is essentially or contributes to the existing technology, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods of various embodiments of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program code. .

Those skilled in the art should realize that in one or more of the above examples, the services described in the present invention can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these services may be stored on or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. Storage media can be any available media that can be accessed by a general purpose or special purpose computer.

The above specific embodiments further describe the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above are only specific embodiments of the present invention.

Above, the above embodiments are only used to illustrate the technical solution of the present application, but not to limit it. Although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still implement the above-mentioned implementations. The technical solutions described in the examples are modified, or some of the technical features are equivalently replaced; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions in the embodiments of the present application.

Claims

A fault notification method, characterized in that it is applied to a first communication device, and the method includes:

Determine whether the fine-grained unit FGU layer is working abnormally;

Send fault indication information to the upstream node, where the fault indication information is used to indicate a remote fault.
The method according to claim 1, characterized in that the remote fault includes:

The remote FGU layer is faulty.
The method according to claim 1 or 2, characterized in that the fault indication information is carried through base frame overhead.
The method according to claim 3, characterized in that the fault indication information is carried through a reserved field of the base frame overhead.
The method according to claim 3, characterized in that the fault indication information is carried by an identification flag field of the base frame overhead.
The method according to claim 1 or 2, characterized in that the fault indication information is carried through the operation and maintenance management OAM code block of the MTN channel layer of the metropolitan area transmission network.
The method according to claim 6, characterized in that the type field in the OAM code block is used to indicate that the OAM code block carries the fault indication information.
The method according to claim 6, characterized in that the OAM code block is a basic OAM code block.
The method according to any one of claims 6 to 8, characterized in that the fault indication information includes remote fault indication information RDI.
The method according to claim 8, wherein the fault indication information further includes indication information indicating that the remote fault is a remote FGU layer fault.
The method according to any one of claims 1-10, characterized in that determining that the FGU layer is working abnormally includes:

One or more of multiframe loss LOM is detected, frame loss LOF is detected, and service layer exception of the FGU layer is detected.
The method according to any one of claims 1-11, characterized in that the service layer of the FGU layer is an MTN channel layer or an Ethernet physical layer.
The method according to any one of claims 1 to 12, characterized in that the first communication device is an intermediate node in the end-to-end path of the small-granule service carried by the FGU layer.
The method according to any one of claims 1-13, characterized in that the upstream node is an intermediate node in the end-to-end path of the small-granule service carried by the FGU layer.
The method of claim 1, further comprising:

Determine that the FGU layer is working properly;

Send fault recovery information to the upstream node, where the fault recovery information is used to indicate that the remote end is normal.
The method according to claim 15, characterized in that the remote normal includes:

The remote FGU layer is normal.
A fault notification method, characterized in that it is applied to a second communication device, and the method includes:

Receive fault indication information sent by the first communication device, where the fault indication information is used to indicate a remote fault;

Based on the fault indication information, it is determined that a fault occurs in the first communication device.
The method according to claim 17, characterized in that the remote fault includes: a remote fine-grained basic unit FGU layer fault.
The method according to claim 17 or 18, characterized in that the fault indication information is carried through base frame overhead.
The method according to claim 19, characterized in that the fault indication information is carried through a reserved field of the base frame overhead.
The method according to claim 19, characterized in that the fault indication information is carried through an identification flag field of the base frame overhead.
The method according to claim 17 or 18, characterized in that the fault indication information is carried through the operation and maintenance management OAM code block of the MTN channel layer of the metropolitan area transmission network.
The method according to claim 22, characterized in that the type field in the OAM code block is used to indicate that the OAM code block carries the fault indication information.
The method according to claim 22, characterized in that the OAM code block is a basic OAM code block.
The method according to claim 24, characterized in that the fault indication information includes remote fault indication information RDI.
The method according to claim 24, characterized in that the fault indication information is carried through a reserved field in the basic OAM code block.
The method according to any one of claims 17-26, characterized in that the service layer of the FGU layer is an MTN channel layer or an Ethernet physical layer.
The method of claim 18, further comprising:

Send alarm information to the control management device, where the alarm information is used to indicate abnormal operation of the first communication device.
The method according to claim 28, characterized in that the first communication device works abnormally, including:

The FGU layer of the first communication device works abnormally.
The method according to any one of claims 17-29, characterized in that the method further includes:

Receive fault recovery information sent by the first communication device, where the fault recovery information is used to indicate that the remote end is normal.
The method of claim 30, further comprising:

Perform time slot synchronization with the first communication device.
The method according to any one of claims 17-31, characterized in that the first communication device is an intermediate node in the end-to-end path of the small-granule service carried by the FGU layer.
The method according to any one of claims 17 to 32, characterized in that the upstream node is an intermediate node in the end-to-end path of the small-granule service carried by the FGU layer.
A status notification method, characterized in that it is applied to a first communication device, and the method includes:

Determine the working status of the fine-grained unit FGU layer;

Send status indication information to the upstream node, where the status indication information is used to indicate the working status of the FGU layer.
The method according to claim 34, characterized in that the working status of the FGU layer includes:

The FGU layer works fine.
The method according to claim 34 or 35, characterized in that the status indication information is carried through base frame overhead.
The method according to claim 36, characterized in that the status indication information is carried through a reserved field of the base frame overhead.
The method according to claim 36, characterized in that the status indication information is carried through an identification flag field of the base frame overhead.
The method according to claim 34 or 35, characterized in that the status indication information is carried through the operation and maintenance management OAM code block of the MTN channel layer of the metropolitan area transmission network.
The method according to claim 39, characterized in that the type field in the OAM code block is used to indicate that the OAM code block carries the status indication information.
The method according to claim 39, characterized in that the OAM code block is a basic OAM code block.
The method according to claim 41, characterized in that the status indication information is carried through a reserved field in the basic OAM code block.
The method according to any one of claims 34 to 42, characterized in that the service layer of the FGU layer is an MTN channel layer or an Ethernet physical layer.
The method according to any one of claims 34 to 43, characterized in that the first communication device is an intermediate node in the end-to-end path of the small-granule service carried by the FGU layer.
The method according to any one of claims 34-44, characterized in that the upstream node is an intermediate node in the end-to-end path of the small-granule service carried by the FGU layer.
A status notification method, characterized in that it is applied to a second communication device, and the method includes:

Receive status indication information sent by the first communication device, where the status indication information is used to indicate the working status of the remote fine-grained unit FGU layer;

Based on the status indication information, the working status of the FGU layer of the first communication device is determined.
The method according to claim 46, characterized in that the working status of the FGU layer includes:

The FGU layer works fine.
The method according to claim 46 or 47, characterized in that the status indication information is carried through base frame overhead.
The method according to claim 48, characterized in that the status indication information is carried through a reserved field of the base frame overhead.
The method according to claim 48, characterized in that the status indication information is carried through an identification flag field of the base frame overhead.
The method according to claim 46 or 47, characterized in that the status indication information is carried through the operation, maintenance and management OAM code block of the MTN channel layer of the metropolitan area transmission network.
The method according to claim 51, characterized in that the type field in the OAM code block is used to indicate that the OAM code block carries the status indication information.
The method according to claim 51, characterized in that the OAM code block is a basic OAM code block.
The method according to claim 53, characterized in that the status indication information is carried through a reserved field in the basic OAM code block.
The method according to any one of claims 46 to 54, characterized in that the service layer of the FGU layer is an MTN channel layer or an Ethernet physical layer.
The method according to any one of claims 46-55, characterized in that the first communication device is an intermediate node in the end-to-end path of the small-granule service carried by the FGU layer.
The method according to any one of claims 46-56, characterized in that the upstream node is an intermediate node in the end-to-end path of the small-granule service carried by the FGU layer.
A first communication device, characterized in that the device includes:

transceiver unit and processing unit;

The transceiver unit is used to perform the receiving and/or transmitting operations performed by the first communication device according to any one of claims 1-16;

The processing unit is configured to perform operations other than the receiving and/or sending operations performed by the first communication device according to any one of claims 1-16.
A second communication device, characterized in that the device includes:

transceiver unit and processing unit;

The transceiver unit is used to perform the receiving and/or transmitting operations performed by the second communication device according to any one of claims 17-33;

The processing unit is configured to perform operations other than the receiving and/or sending operations performed by the second communication device according to any one of claims 17-33.
A first communication device, characterized in that the device includes:

transceiver unit and processing unit;

The transceiver unit is used to perform the receiving and/or transmitting operations performed by the first communication device according to any one of claims 34-45;

The processing unit is configured to perform operations other than the receiving and/or transmitting operations performed by the first communication device according to any one of claims 34-45.
A second communication device, characterized in that the device includes:

transceiver unit and processing unit;

The transceiver unit is used to perform the receiving and/or transmitting operations performed by the second communication device according to any one of claims 46-57;

The processing unit is configured to perform operations other than the receiving and/or transmitting operations performed by the second communication device according to any one of claims 46-57.
A communication device, characterized by including: a processor and a memory;

The memory is used to store instructions;

The processor is configured to execute the instructions so that the communication device executes the method described in any one of claims 1-57.
A computer-readable storage medium, characterized by comprising instructions that, when executed on a processor, implement the method described in any one of claims 1-57.
A communication system, characterized in that the communication system includes:

A first communication device that performs the method described in any one of claims 1-16 and a second communication device that performs the method described in any one of claims 17-33; or,

A first communication device performing the method of any one of claims 34-45 above and a second communication device performing the method of any one of claims 46-57.
A computer program product, characterized by comprising a computer program that implements the method described in any one of claims 1-57 when the computer program is run on a processor.